Requirement Specifications |
 |
 |
 |
| Written by Graham Stoney | |
|
Requirement Specifications are documents that contain in-bound requirements; that is, requirements that a system or subcomponent needs to meet. They should be as free of design decisions as possible. Requirements are generally described in the future tense, since these documents are mostly written before the system in question exists; but they remain in the future tense even at the end of the project when they are used as the basis for verification protocols and acceptance testing. Requirements generally use the words “shall” or “must” to state mandatory intentions, and “should” to state desirable ones. For example: “The circuitry shall not be damaged, but need not function, with the batteries inserted backwards.” Special examples of requirements documents common to many projects include the User Needs document which is essentially requirements written in user-speak developed in coordination with marketing, the System Requirements Specification which outlines what the system must do to meet these user needs, and the Software Requirements Specification which outlines what the software's contribution to meeting the system requirements will be. Social Bookmark this page:         
|