HKSM
Requirements Traceability Matrix
A structured table that connects each product requirement to its original source and to the deliverables that fulfill it.
Key Points
- Enables bidirectional traceability: from requirements to deliverables and tests, and back again.
- Supports impact analysis during changes by showing all related artifacts, owners, and status.
- Tracks attributes such as ID, source, priority, acceptance criteria, and verification method.
- Helps verify complete scope coverage and prevents missing or gold-plated work.
Example
On a healthcare software project, the requirement "System must mask patient IDs" is traced to its source (HIPAA clause), linked to design spec DS-08, code module SEC-03, test cases TC-45 and TC-46, and the release note RN-02. When the regulation changes, the project manager uses the matrix to identify all affected deliverables, tests, and stakeholders for updates.
PMP Example Question
During a requirements change, the project manager needs to see which deliverables and test cases must be updated. Which artifact should they consult first?
- WBS Dictionary
- Requirements Traceability Matrix
- Issue Log
- Milestone List
Correct Answer: B - Requirements Traceability Matrix
Explanation: The requirements traceability matrix links each requirement to its source and to the deliverables and verification activities that satisfy it, making impact analysis straightforward.
