Requirements Traceability Matrix
DE: Anforderungsrueckverfolgbarkeitsmatrix
A grid linking requirements from origin to deliverables that satisfy them.
Detailed Explanation
The Requirements Traceability Matrix (RTM) links product requirements from their origin (business need, stakeholder request) to the deliverables that satisfy them. It provides forward traceability (requirement to deliverable) and backward traceability (deliverable to requirement).
Each row in the RTM contains: requirement ID, requirement description, source/origin, priority, WBS element, acceptance criteria, test case, current status, and validation method. This comprehensive tracking ensures no requirement is lost or overlooked during the project.
The RTM is essential for scope verification and validation. It ensures every requirement has a corresponding deliverable and test, and every deliverable traces back to a business need. This prevents building things nobody asked for and ensures nothing requested is forgotten.
Key Points
- Links requirements to deliverables bidirectionally
- Forward trace: requirement to deliverable
- Backward trace: deliverable to requirement
- Tracks requirement status throughout the lifecycle
- Essential for scope verification and validation
- Prevents requirements from being lost or orphaned
Practical Example
An ERP project RTM tracks 150 requirements. Requirement R-042 'System must generate monthly financial reports' traces to: WBS element 3.2.4, Test Case TC-087, Acceptance Criteria AC-042, and is assigned to the Reporting module. At scope verification, the PM confirms every requirement has a passing test and an accepted deliverable.
Tips for Learning and Applying
Create the RTM early and maintain it throughout the project
Link requirements to test cases for complete traceability
Use the RTM during scope verification to confirm completeness
Automate RTM maintenance using requirements management tools
Want to Master These Concepts?
Our courses cover all these terms in depth with practical examples and exercises.