Available under Creative Commons-ShareAlike 4.0 International License.
These are suggestions only and will vary based on organizational and project requirements.
- A unique identification number containing the general category of the requirement (e.g., SYSADM) and a number assigned in ascending order (e.g., 1.0, 1.1, 1.2)
- Requirement statement
- Requirement source (conference, configuration control board, task assignment, etc.)
- Software requirements specification/functional requirements document paragraph number containing the requirement
- Design specification paragraph number containing the requirement
- Program module containing the requirement
- Test specification containing the requirement test
- Test case number(s) where requirement is to be tested (optional)
- Verification of successful testing of requirements
- Modification field (If a requirement was changed, eliminated, or replaced, indicate disposition and authority for modification.)
- Remarks
Requirements Traceability Matrix by DHWiki licensed under Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 United States License.
- 1142 reads
