1. Refine the Supplementary Specifications
The Supplementary Specifications are refined and augmented based on evaluation feedback and continued work on the
Use-Case Model (in allocating non-functional requirements, such as performance requirements, to use cases and use-case
black-box steps). If requirements are traced or otherwise formally managed, make sure that each requirement is clearly
identified and labeled and updated.
2. Generate Supporting Reports
Requirements are often stored and managed using one or more tools. For example, tools for the following purposes:
-
graphical use-case modeling.
-
traceability and requirements management.
-
other textual and graphical documentation.
This step generates documentation from these tools so that the information can be easily reviewed. If specialized
tools are not used for capturing the requirements, then this step is not applicable (all software requirements would be
written directly in the documentation).
3. Package the Requirements for Review
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, a Systems 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 and combining these with the Supplementary
Specifications.
|
