Requirements are central to the entire systems engineering process. The concept of operations details including user needs and operational scenarios, inform and spawn detailed requirements.
Requirements emerge from the user needs. Requirements are used to guide the design and determine that the design is complete and correct. Later we will use the requirements after system implementation to demonstrate the system functions correctly. The requirements are referenced during the testing stages and the system acceptance is predicated on the testing against the requirements being successful. Well written requirements are necessary, if not, the end system may not meet the user needs and expectations. The requirements also serve as the basis for procurement from selection to final acceptance.
Included in this topic is the need to have well formed requirements, namely are they:
· Necessary
· Clear
· Complete
· Correct
· Feasible
· Verifiable
It is critical to document your requirements. They need to be sequentially numbered and frequently in a hierarchy so they can be referred to in traceability tables.
For More Information:
Visit Process View and Deliverable View for more information on the process of developing requirements and documenting them:
