Requirements Traceability Matrix (RTM)
A document mapping requirements to test cases, ensuring every requirement has corresponding tests.
Full definition
A Requirements Traceability Matrix (RTM) maps requirements to the test cases that verify them. It ensures complete test coverage — every requirement is tested, and every test traces back to a requirement.
RTM structure: | Req ID | Requirement | Test Cases | Status | |---|---|---|---| | REQ-001 | User can login with email | TC-001, TC-002, TC-003 | Covered | | REQ-002 | Password reset via email | TC-010, TC-011 | Covered | | REQ-003 | Two-factor authentication | (none) | Gap! |
Types of traceability:
- Forward traceability: Requirements → Test cases (are all requirements tested?)
- Backward traceability: Test cases → Requirements (does every test serve a purpose?)
- Bidirectional: Both directions (gold standard)
Benefits:
- Identifies untested requirements (gaps)
- Identifies tests without requirements (waste)
- Supports impact analysis (requirement changed → which tests to update?)
- Required for compliance (medical, financial, aerospace)
In Agile, traceability often happens through user stories linked to test cases in tools like Jira + TestRail/Zephyr, rather than formal RTM documents.