Accepts BC-001, SA-001, PP-001 and MIL-001 to MIL-003 with review records RC-001 to RC-005 (autonomous mode, AI as stand-in for S01).
2.3 KiB
2.3 KiB
Traceability Matrix
Metadata
| Key | Value |
|---|---|
| ID | TM-001 |
| CrossReference | BC-001 |
Version History
| Date | Status | Author | Reviewer | Change | Commit |
|---|---|---|---|---|---|
| 2026-10-13 | Accepted | Jens Tirsvad Nielsen | AI as stand-in for S01 | Initial version | pending |
Purpose
Tracks backward/forward links between artifact instances so that the Business Case's cross-artifact traceability success criterion is measurable. A row is added or updated whenever an artifact instance is created or reviewed.
Purpose
Tracks backward and forward links between artifact instances so that the cross-artifact traceability can be checked. A row is added or updated whenever an artifact instance is created or reviewed.
Traceability Table
| Artifact Instance | Type | Language | Domain | Upstream (Backward Link) | Downstream (Forward Link) | Last Reviewed (RC-ID) |
|---|---|---|---|---|---|---|
| BC-001 | Business Case | en | it | - | SA-001, PP-001, MIL-001, MIL-002, MIL-003 | RC-001 |
| SA-001 | Stakeholder Analysis | en | it | BC-001 | PP-001 | RC-002 |
| PP-001 | Project Plan | en | it | BC-001, SA-001 | MIL-001, MIL-002, MIL-003 | - |
| MIL-001 | Milestone | en | it | BC-001, PP-001 | MIL-002 | RC-003 |
| MIL-002 | Milestone | en | it | BC-001, MIL-001 | MIL-003 | RC-004 |
| MIL-003 | Milestone | en | it | BC-001, MIL-002 | - | RC-005 |
Coverage Notes
-in Upstream means foundational; in Downstream it means nothing is built on it yet; in Last Reviewed it means no review record exists.- PP-001 has no QC checklist yet; it is accepted by the Product Owner's stand-in.
- Use cases, user stories and design artifacts are added in MIL-002.