Artifact: Requirements Attributes
| A repository of project requirements, attributes and dependencies to assist managing change from a requirements perspective. | |
| Role: | System Analyst |
| Optionality/Occurrence: | Optional. Late in the Inception phase; evolving throughout the whole development cycle. |
| Templates and Reports: | |
| Examples: | |
| UML Representation: | Not applicable. |
| More Information: | - Concept: Requirements - Checklist: Requirements Attributes - Concept: Requirements Management - Guideline: Requirements Management Plan - Concept: Traceability - Concept: Types of Requirements |
| Input to Activities: - Manage Dependencies - Prioritize Use Cases | Output from Activities: - Develop Vision - Manage Dependencies |
Purpose
The Requirements Attributes artifact provides a repository of the requirement text, attributes and traceability for all requirements. It should be accessible by everyone in the development organization.
Brief Outline
The following views should be available for viewing the current status of the artifact:
1. Requirement Attribute Matrices
1.1 <type of requirement> For each type of requirement, present a matrix that lists the requirements on one axis, and all attributes on the other axis. For each requirement, show the state of its respective attributes.
2. Requirement Traceability Matrices
2.1 <type of requirement>
2.1.1 <type of requirement traced to> For each type of requirement, present a matrix that lists the requirements on one axis, and all items traced to on the other axis. For each trace, show its state (OK or [suspect](../disciplines/requirements/co_trace.md#Purpose of Traceability)).
3. Requirement Traceability Tree
3.1 <type of requirement>
3.1.1 <type of requirement traced to> A traceability tree provides a graphical view of traceability relationships to or from requirements of a specific requirements type (the root).
Timing
The configuration of this repository is defined in the Requirements Management Plan. The repository should be set up and begin to be populated in late inception phase. The contents will evolve throughout the whole development cycle.
Responsibility
A System Analyst is responsible for the integrity of the Requirements Attributes artifact, ensuring that:
- The repository contents are updated and distributed.
- Input from all concerned parties is considered.
Tailoring
If you are using a requirements management tool, such as Rational RequisitePro, you can maintain the repository information directly in saved views in the requirements management database.