Traceability matrix
Requirements-to-tests mapping with coverage gaps highlighted. Markdown table format.
180 wordsCoverageRequirementsAudit
Requirements Traceability Matrix ā Product Name / Release
Version: 1.0 Author: Name Date: YYYY-MM-DD Release: v0.0
Coverage Summary
| Metric | Value |
|---|---|
| Total requirements | X |
| Requirements with ā„ 1 test case | X |
| Requirements with 0 test cases (gap) | X |
| Total test cases | X |
| Test cases linked to a requirement | X |
| Orphan test cases (no requirement) | X |
| Overall requirement coverage | X% |
Matrix
Each row is a requirement. Columns are test case IDs. Mark with ā where a test case covers the requirement.
| Req ID | Requirement Description | TC-001 | TC-002 | TC-003 | ... | Coverage |
|---|---|---|---|---|---|---|
| REQ-001 | Description | X/Y tests | ||||
| REQ-002 | Description | X/Y tests | ||||
| REQ-003 | Description | X/Y tests | ||||
| REQ-004 | Description (gap ā no tests) | ā 0 tests |
Coverage Gaps
List requirements with no test case coverage and the reason / plan to address.
| Req ID | Requirement | Reason for Gap | Plan |
|---|---|---|---|
| REQ-XXX | Description | Not yet implemented / deferred / out of scope | Action |
Orphan Test Cases
Test cases not linked to any requirement. Review and either link or remove.
| Test Case ID | Title | Action |
|---|---|---|
| TC-XXX | Title | Link to REQ-XXX / Remove / Raise requirement |
Notes
Any caveats about the matrix ā e.g., requirements that map to many test cases, or test cases that partially cover multiple requirements.
Requirements Traceability Matrix ā Novu Bank v3.2 Open Banking Feature
Version: 1.0 Author: Marcus Obi Date: 2024-03-05 Release: v3.2.0
Coverage Summary
| Metric | Value |
|---|---|
| Total requirements | 5 |
| Requirements with ā„ 1 test case | 4 |
| Requirements with 0 test cases (gap) | 1 |
| Total test cases | 12 |
| Test cases linked to a requirement | 11 |
| Orphan test cases (no requirement) | 1 |
| Overall requirement coverage | 80% |
Matrix
| Req ID | Requirement Description | TC-1080 | TC-1081 | TC-1082 | TC-1083 | TC-1084 | TC-1085 | TC-1086 | TC-1087 | TC-1088 | TC-1089 | TC-1090 | TC-1091 | Coverage |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| OB-001 | User can link an external bank account via Open Banking consent flow (all three providers) | ā | ā | ā | 3 / 12 | |||||||||
| OB-002 | Linked account balance and transactions are visible within 5 seconds of successful consent | ā | ā | 2 / 12 | ||||||||||
| OB-003 | User can revoke Open Banking consent and the linked account is removed within 10 seconds | ā | ā | 2 / 12 | ||||||||||
| OB-004 | If the provider redirect exceeds 30 seconds, a timeout message is shown and no partial state is persisted | ā | ā | 2 / 12 | ||||||||||
| OB-005 | A user who has previously linked an account can re-link after revoking consent without data loss | ā 0 tests |
Coverage Gaps
| Req ID | Requirement | Reason for Gap | Plan |
|---|---|---|---|
| OB-005 | Re-link after revoking consent without data loss | Test case not written at planning; discovered during triage 2024-03-07 | TC-1092 created and scheduled for execution 2024-03-10 (added to regression suite) |
Orphan Test Cases
| Test Case ID | Title | Action |
|---|---|---|
| TC-1091 | Verify Open Banking consent page meets WCAG 2.1 AA colour contrast | Link to OB-ACC-001 once accessibility requirements are formalised for v3.3. Orphan for this release. |
Notes
- OB-001 is covered by three separate test cases (one per provider: GreenPay TC-1080, ClearLedger TC-1081, OpenRoute TC-1082) because provider-specific behaviour differs.
- OB-004 maps to two test cases: TC-1088 covers the UI timeout message, TC-1089 verifies that no partial account state is written to the database after a timeout.
- TC-1092 (OB-005 gap) was added after the matrix was drafted. It was executed on 2024-03-10 and passed ā matrix will be updated in v1.1.
// Related templates
// Learn more