What is Requirements Traceability Matrix (RTM)?

A requirements traceability matrix (RTM) is a document that maps each requirement to the test cases that verify it, proving every requirement is covered and showing the impact of any change.

Start a Free Mock Interview

Free to start · 7-day trial on paid plans

IN DEPTH

In depth.

An RTM is a table linking requirements (or user stories) to their design, test cases, and sometimes defects. Its core job is bidirectional traceability: forward, from a requirement to the tests that cover it, so you can prove nothing is untested; and backward, from a test to its requirement, so you can prove no test is orphaned (testing something nobody asked for).

The practical value shows up in two moments. During planning, the RTM surfaces requirements with no test coverage, the gaps that ship as production bugs. During change, it answers "if this requirement changes, which tests must I update?" in seconds instead of a guess. In regulated industries (medical, finance, aviation) an RTM is often a compliance requirement, not just good practice.

The trade-off is maintenance. A heavyweight RTM kept in a spreadsheet rots fast; modern teams lean on test-management tools that link requirements, tests, and runs automatically. Interviewers want to know you understand the coverage and impact-analysis value, not that you can format a spreadsheet.

WHY IT MATTERS

Why interviewers ask about this.

RTM questions appear in QA process and test-management interviews. The signal is whether you understand traceability as coverage proof and impact analysis, not just as a document you fill in because the process says so.

EXAMPLE

Example scenario.

Before a release, a team builds an RTM and finds requirement R-14 ("users can export to CSV") has no linked test case. It was implemented but never tested. Without the matrix, the gap ships; with it, QA adds the missing coverage before release.

TIP

Interview tip.

Define forward and backward traceability and give the two use cases: finding coverage gaps and doing impact analysis when a requirement changes. Mentioning compliance contexts (medical, finance) adds depth.

FAQ

Frequently asked questions.

What is the purpose of a requirements traceability matrix?

To prove every requirement is covered by at least one test (forward traceability) and that no test exists without a requirement (backward traceability), and to make impact analysis fast when a requirement changes.

Is an RTM still relevant with modern test tools?

Yes, though the spreadsheet form is fading. Test-management tools provide the same traceability automatically by linking requirements, tests, and runs, which is the maintainable way to get RTM value.