Tirsvad-Udemy-100_days_of_code/014-higher_lower

Files

T

Tirsvad a1ff73580f Accept BC, SA, PP and MIL-001 after review

Review BC-001, SA-001, PP-001 and MIL-001 and record the results as
RC-001 to RC-004. All four verdicts are Go, so their Version History
rows become Accepted and the previous rows Deprecated. MIL-002 to
MIL-004 stay Proposed.

BC-001 failed criterion 1 (cost-benefit not justified as qualitative).
Add the justification and a target-completion constraint (2026-10-14)
that PP-001 and MIL-001 are checked against.

Add the Traceability Matrix (TM-001) and register RC and TM in the
artifact registry. PP has no QC checklist, so RC-003 checks the plan
against BC-001 and the milestones instead. Author and reviewer are
both S01, a deviation noted in each record.

Refs #5

2026-10-04 23:23:12 +08:00

1.8 KiB

Raw Blame History

Traceability Matrix

Metadata

Key	Value
ID	TM-001
CrossReference	BC-001

Version History

Date	Status	Author	Reviewer	Change	Commit
2026-10-04	Proposed	Jens Tirsvad Nielsen	S01	Initial version	pending

Purpose

Tracks backward/forward links between artifact instances so that the Business Case traceability target is measurable. A row is added or updated whenever an artifact instance is created or reviewed.

Traceability Table

Artifact Instance	Type	Upstream (Backward Link)	Downstream (Forward Link)	Last Reviewed (RC-ID)
BC-001	BC	-	SA-001, PP-001	RC-001
SA-001	SA	BC-001	PP-001	RC-002
PP-001	PP	BC-001, SA-001	MIL-001, MIL-002, MIL-003, MIL-004	RC-003
MIL-001	MIL	BC-001, PP-001	-	RC-004
MIL-002	MIL	BC-001, PP-001	-	-
MIL-003	MIL	BC-001, PP-001	-	-
MIL-004	MIL	BC-001, PP-001	-	-

Coverage Notes

No use cases, user stories or design artifacts exist yet (UC-001 is planned for MIL-003).
- in Upstream means foundational; in Downstream, nothing is built on it yet; in Last Reviewed, no RC-* exists yet.

1.8 KiB Raw Blame History