Traceability matrix
The map linking requirements to risks to tests, proving every requirement was verified and nothing was tested into the void.
The matrix answers two audit questions at once: show me that every requirement was tested, and show me why every test exists. Requirements trace forward to verification; tests trace backward to purpose.
Tooling matters more than format. A matrix maintained by hand in a spreadsheet goes stale by the second change request; one generated from a requirements tool stays honest. The artifact is only as good as its last update.
Related terms
Go deeper
All CSVCSV/Jun 2, 2026/8 min
CSA is not the end of CSV. It is CSV finally done right.
FDA's Computer Software Assurance guidance was read by half the industry as permission to stop validating. The other half read it correctly.
CSV/May 21, 2026/7 min
The GAMP 5 software categories, explained like a human
Category 3, 4 or 5 decides how much validation work you are signing up for. Here is how to call it correctly, with a tool that does the asking.