This work product does not imply one physical document to capture all requirement types. To manage the communication of
the information, it can make more sense to separate out the information into separate physical documents or to use the
work items list.
The following are recommendation and options for representing the Supporting Requirements.
Recommendation: Use the Supporting Requirements Specification Template.
The Template: Supporting Requirements Specification provides a means to capture,
structure, and organize the supporting requirements.
Even in a small project, a requirements management tool, a database, or a spreadsheet, are recommended for prioritizing
and managing requirements. If stakeholders are comfortable with accessing requirements directly from the tool, or with
accessing a report automatically generated from the tool, then no separate document is required.
Option: Use the Work Items List.
Consider capturing supporting requirements in the Artifact: Work Items List which can be used for prioritizing and managing
requirements. If stakeholders are comfortable with it, or with accessing a report automatically generated from it, then
no separate document is required.
Option: Include as Part of the Vision Document
Consider including some supporting requirements types in the Artifact: Vision. In order to keep the Vision stable, follow this option for the requirements types that will need less
refinement such as Product Qualities, Documentation or Compliance.
|