genichin
4919b1d130
git-subtree-dir: .vendor/myagent-kit git-subtree-split: 3e45f3fb102e71d5127366f2fc675eaadc3927da
29 lines
1.2 KiB
Markdown
29 lines
1.2 KiB
Markdown
# SRS Traceability Matrix
|
|
|
|
<!--
|
|
Usage:
|
|
1. Copy this file to docs/SRS/traceability-matrix.md in your target repository.
|
|
2. Keep one row per requirement.
|
|
3. Update Issue/PR, Test Evidence, and Status whenever implementation progresses.
|
|
-->
|
|
|
|
## 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 | docs/SRS/<Type>/REQ-001_<slug>.md | #123 | #456 | tests/... , CI run link | Approved | Planned | YYYY-MM-DD |
|
|
|
|
## 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: test file path, CI job, or manual verification note.
|
|
- Last Updated uses YYYY-MM-DD.
|
|
- If there is no value yet, use `TBD`.
|