App-Requirement-Arch
2 results

 view release on metacpan or  search on metacpan

lib/App/Requirement/Arch.pm  view on Meta::CPAN 


Goals:

	- keep things as simple if possible
	- Adapt to the requirement process you use and propose one if you don't have any
	- the UI is provided by your platform
	- power users like the command line
	- handle small to middle sized projects ( wich are the most common)
	- try to make it appealing to developers

The set of applications should be usable by anyone but having a development background does help. If the people writing  requirements
have little or no knowledge of requirements handling, someone with the knowledge should help them. This is true for any requirement 
gathering process wether they use this application or a multi million dollar commercial framework.

=head1 DOCUMENTATION

=head2 Physical representation of the requirements:

=head2 Decisions

	- Each requirements are gathered in a text file

lib/App/Requirement/Arch/HTML/Flat.pm  view on Meta::CPAN 

 
	<head>
		<!-- $comment -->
		<title>$title</title>
		<style type="text/css">
			body,form{
				margin: 0;
				margin-right: 15%;
			}
			pre {
				background-color: #FFFFFF;
				font-family: monospace;
				font-size: 9pt;
				color: #000000;
			}
			body {
				background-color: #FFFFFF;
				font-family: verdana,arial,helvetica,sans-serif;
				font-size: 10pt;
				color: #000000;
			}
			select {
				font-size: 10pt;
				font-family: Verdana,sans-serif;
			}
			h1{
				font-size: 14pt;



( run in 0.783 second using v1.01-cache-2.11-cpan-d8267643d1d )