RVTM
The Requirements Verification Traceability Matrix (RVTM) is the allocation table that maps every requirement to how it will be verified. It is often a contractual deliverable on regulated projects.
Open it from the sidebar under Verify → RVTM, at /projects/:projectId/verification/rvtm.
What an RVTM row contains
| Column | Meaning |
|---|---|
| Requirement | The requirement code and statement. |
| Method | The verification method allocation — Test, Analysis, Inspection, Demonstration (TAID), plus Review or Other. |
| Personnel | The assigned engineer responsible for the verification. |
| Linked procedures / cases | The test procedures and test cases that close the requirement. |
| Status | Not Started, In Progress, Verified, or Failed. |
| Dates | Planned and actual verification dates. |
Walkthrough
- Open Verify → RVTM. The table lists every requirement in the project.
- Edit a cell inline — pick the Method from the dropdown, assign personnel, or set dates directly on the row.
- Use the filter bar to narrow by status or method, or search by requirement ID/title.
- Click Export to download the current (filtered) matrix as a CSV for your deliverable template.
Status auto-rollup
The Status column is auto-derived from the latest test execution for each linked test case — you don't flip the verdict by hand:
- No linked test cases → Not Started.
- Any latest result is failed → Failed (failure trumps pass).
- Every linked case has an execution and every latest result is passed → Verified.
- Otherwise (missing executions, latest is blocked or skipped) → In Progress.
If you set the status explicitly (for example, to record an approved workaround), the row holds your override and the auto-rollup leaves it alone until you clear it.
Archived requirements
Requirements use soft-delete (archive). Archived requirements are excluded from the RVTM — they don't count toward coverage and don't appear as gaps. Restore an archived requirement and it re-enters the matrix on the next refresh.
RVTM vs. Coverage
The RVTM is the allocation table — the row-by-row deliverable that answers "which requirements are verified, by what method, by whom?" The Coverage page is the visual gap heatmap built from the same data — it answers "where are my holes?" at a glance. Use the RVTM to manage and export the formal matrix; use Coverage to spot uncovered requirements quickly.
Tips
- Verified means linked AND passing. A requirement is not verified until a linked case has at least one passing run.
- Sweep before reviews. Filter by Not Started to surface rows that still need a method or a procedure.
- Use the matrix in retrospectives. Patterns of late or fragile verifications often point to under-specified requirements.