Project Name
Requirements Traceability Matrix
|
Unique No.
|
Requirement |
Source of Requirement |
Software Reqs. Spec / Functional Req. Doc. |
Design Spec.
|
Program Module
|
Test Spec.
|
Test Case(s) |
Successful Test Verification |
Modification of Requirement |
Remarks |
|
Objective 1: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Description of Matrix Fields
Develop a matrix to trace the requirements back to the project objectives identified in the Project Plan and forward through the remainder of the project life cycle stages. Place a copy of the matrix in the Project File. Expand the matrix in each stage to show traceability of work products to the requirements and vice versa. The requirements traceability matrix should contain the following fields:
-
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).
-
The 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 requirement was changed, eliminated, or replaced, indicate disposition and authority for modification.
-
Remarks.