|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (1)
View Page History
...
h4. {color:#000000}Tools that take planned actions inside a repository and prevent files from becoming rotten or decayed. A regular checksum process using a tool like : {color}[http://checksumchecker.sourceforge.net/ and|http://checksumchecker.sourceforge.net/%C2%A0and]{color:#000000} and planned process for opening and saving files that are not used so often.{color}
<Project Name>
System-Wide Requirements Specification
Usage note: There is procedural guidance within this template that appears in a style named InfoBlue. This style has a hidden font attribute allowing you to toggle whether it is visible or hidden in this template. Use the Word menu ToolsàOptionsàViewàHidden Text checkbox to toggle this setting. A similar option exists for printing ToolsàOptionsàPrint.
1. Introduction
2. System-Wide Functional Requirements
\[Statement of system-wide functional requirements, not expressed as use cases. Examples include auditing, authentication, printing, reporting.\]
3. System Qualities
\[Qualities represent the URPS in FURPS\+ classification of supporting requirements.\]
3.1 Usability
\[Describe requirements for qualities such as easy of use, easy of learning, usability standards and localization.\]
3.2 Reliability
\[Reliability includes the product and/or system's ability to keep running under stress and adverse conditions. Specify requirements for reliability acceptance levels, and how they will be measured and evaluated. Suggested topics are availability, frequency of severity of failures and recoverability.\]
3.3 Performance
\[The performance characteristics of the system should be outlined in this section. Examples are response time, throughput, capacity and startup or shutdown times.\]
3.4 Supportability
\[This section indicates any requirements that will enhance the supportability or maintainability of the system being built, including adaptability and upgrading, compatibility, configurability, scalability and requirements regarding system installation, level of support and maintenance.\]
\\
4. System Interfaces
\[Interface Requirements are part of the + in the FURPS\+ classification of supporting requirements. Define the interfaces that must be supported by the application. It should contain adequate specificity, protocols, ports and logical addresses, and so forth, so that the software can be developed and verified against the interface requirements.\]