CI / checks (pull_request) Successful in 1m3s
Replace pending in the Version History of the traceability matrix with the link to the commit that added the RC-018 row.
5.6 KiB
5.6 KiB
Traceability Matrix: Turtle Challenges
Metadata
| Key | Value |
|---|---|
| ID | TM-001 |
| CrossReference | BC-001 |
Version History
| Date | Status | Author | Reviewer | Change | Commit |
|---|---|---|---|---|---|
| 2026-10-08 | Proposed | Jens Tirsvad Nielsen | S01 | Added the rows for the code of each milestone, with RC-014 to RC-017 | 4d7cc33 |
| 2026-10-08 | Proposed | Jens Tirsvad Nielsen | S01 | Added the row for the check of the success criteria of BC-001, with RC-018 | 88aee40 |
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.
Traceability Table
| Artifact Instance | Type | Language | Domain | Upstream (Backward Link) | Downstream (Forward Link) | Last Reviewed (RC-ID) |
|---|---|---|---|---|---|---|
| BC-001 | BC | en | it | SA-001 | PP-001, MIL-001, MIL-002, MIL-003, MIL-004, DICT-001 | RC-008 (draft re-review of RC-001, Go) |
| SA-001 | SA | en | it | - | BC-001, DICT-001 | RC-009 (draft re-review of RC-002, Go) |
| PP-001 | PP | en | it | BC-001, SA-001 | MIL-001, MIL-002, MIL-003, MIL-004 | - |
| DICT-001 | DICT | en | it | BC-001, SA-001 | - | RC-007 (Go) |
| MIL-001 | MIL | en | it | BC-001, PP-001 | MIL-002 | RC-010 (draft re-review of RC-003, Go) |
| MIL-002 | MIL | en | it | BC-001, MIL-001 | MIL-003 | RC-011 (draft re-review of RC-004, Go) |
| MIL-003 | MIL | en | it | BC-001, MIL-002 | MIL-004 | RC-012 (draft re-review of RC-005, Go) |
| MIL-004 | MIL | en | it | BC-001, MIL-003 | - | RC-013 (draft re-review of RC-006, Go) |
Python source code of milestone 001 (src/, tests/, branch mil-001-project-foundation) |
PY | - | - | MIL-001 | - | RC-014 (Go) |
Python source code of milestone 002 (src/, tests/, branch mil-002-square-and-dashed-line) |
PY | - | - | MIL-002 | - | RC-015 (Go) |
Python source code of milestone 003 (src/, tests/, branch mil-003-shapes-and-random-color) |
PY | - | - | MIL-003 | - | RC-016 (Go) |
Python source code of milestone 004 (src/, tests/, branch mil-004-random-walk-and-spirograph) |
PY | - | - | MIL-004 | - | RC-017 (Go) |
| Success criteria of BC-001, checked against the delivered repository for the gate of MIL-004 | BC | en | it | BC-001, MIL-004 | - | RC-018 (draft, no verdict) |
Coverage Notes
-in Upstream means foundational (SA-001 is the foundation of the stakeholder IDs); in Downstream it means nothing is built on it yet (MIL-004 is the last gateway; the source code is listed per milestone in thePYrows); in Last Reviewed it means noRC-*exists.- PP-001 has no
RC-*because the Project Plan has no QC checklist; the Product Owner accepted it directly on 2026-10-08. - The
PYrows list the Python code each milestone added or changed, reviewed againstQC-PY-001. Their records, RC-014 to RC-017, ended inGoon 2026-10-08; a-in Language and Domain is right for source code, a technical type. - RC-018 checks the seven success criteria of BC-001 against the delivered repository, as the evidence for the gate of MIL-004. It is a draft with the verdict
Pending(proposed: Go-with-conditions, because criterion 5 is not met until the code is onmainand on GitHub), so its row saysdraft, no verdict. - Each artifact lists its latest review record: the delta re-review (RC-008 to RC-013) of the first review (RC-001 to RC-006), or RC-007 for DICT-001. All of them ended in
Goon 2026-10-07. - S01 is the author and also the reviewer of every artifact. The review process does not allow this; S01 accepted the deviation in chat on 2026-10-07 because the project has one person and no governance document (
GOV) exists. - No instance exists yet for the types KPI, RA, BMC, BPMN, UCD, US, UC, DM, SSD, OC, SD, DCD, ERD, ADR, GOV or TRR. One of them matters for the open reviews: GOV (the rule that the reviewer is not the author).