A requirements traceability matrix (RTM) puts requirements down the side and tests across the top, with a mark where a test proves a requirement. It answers questions nobody can answer from memory:
- Is every requirement tested? A row with no mark is a requirement nobody will check before go-live.
- Does every test have a purpose? A column with no mark is a test of something nobody asked for, or a requirement missing from the list.
- What does a change affect? When R4 changes, the matrix shows which tests to rerun.
Traceability can run further in both directions: back to the business requirement and the stakeholder who asked, forward to the design and the code. Keep it at the level your project needs; for most BAs, requirement to test is the part that pays off every week.