For less formal projects, this step consists of bundling the relevant reports and hand-generated documentation, with
sufficient supporting material so requirements can be effectively reviewed.
On more formal projects, the Work Product: System Requirements Specification collects and
organizes all requirements for the project. The System Requirements Specification is simply a composition of the
Use-Case Model (representing the functional capabilities) and the Supplementary Specifications (capturing all other
requirements). If the project is required to deliver a System Requirements Specification as a single artifact in true
document form, then this can be done by extracting reports from the Use-Case Model and individual use cases (see Report: Use-Case Model Survey and Report: Use-Case Specification ) and combining these with the Supplementary
Specifications.
The template provided with the Work Product: System Requirements Specification serves as a checklist
when the Supplementary Specifications and Use-Case Model artifacts are produced, because these component artifacts
actually contain all of the needed content. If the project decides not to produce Supplementary Specifications or a
Use-Case Model (or decides not to present system requirements to the customer in this way), then the System
Requirements Specification template can be used to guide content production.
|