21 lines
1.0 KiB
Markdown
21 lines
1.0 KiB
Markdown
# SRS Traceability Matrix
|
|
|
|
## Status Definition
|
|
- Planned: Requirement is defined but not yet implemented.
|
|
- In Progress: Implementation issue/PR exists and work is ongoing.
|
|
- Implemented: Code is merged and mapped acceptance criteria are complete.
|
|
- Verified: Required tests and manual checks are completed.
|
|
- Released: Included in a released version.
|
|
|
|
## Matrix
|
|
|
|
| REQ ID | AC Mapping | Requirement File | Implementation Issue | PR | Test Evidence | Requirement Status | Delivery Status | Last Updated |
|
|
|---|---|---|---|---|---|---|---|---|
|
|
| REQ-001 | AC1, AC2, AC3, AC4, AC5, AC6, AC7 | `docs/SRS/Interface/REQ-001_portfolio-comment-history.md` | #2 | TBD | TBD | Approved | In Progress | 2026-04-10 |
|
|
|
|
## Update Rules
|
|
- REQ ID must exactly match the SRS requirement file prefix.
|
|
- AC Mapping should reference concrete IDs such as `AC1`, `AC2`.
|
|
- Test Evidence should point to executable artifacts such as test file paths, CI runs, or manual verification notes.
|
|
- Use `TBD` where implementation or verification evidence does not yet exist.
|