diff --git a/docs/artifact-registry.md b/docs/artifact-registry.md index 221262c..a1afe20 100644 --- a/docs/artifact-registry.md +++ b/docs/artifact-registry.md @@ -11,7 +11,8 @@ each document lives in *this* project and the next version to use. | SA | Stakeholder Analysis | docs/stakeholder-analysis.md | 002 | | PP | Project Plan | docs/project-plan.md | 002 | | MIL | Milestone / Gateway | docs/milestones/*.md | 005 | -| RC | SQA Review Record | docs/sqa/reviews/rc-*.md | 004 | +| RC | SQA Review Record | docs/sqa/reviews/rc-*.md | 008 | +| TM | Traceability Matrix | docs/sqa/traceability-matrix.md | 002 | ## Languages diff --git a/docs/sqa/reviews/rc-004-stakeholder-analysis.md b/docs/sqa/reviews/rc-004-stakeholder-analysis.md new file mode 100644 index 0000000..2c37282 --- /dev/null +++ b/docs/sqa/reviews/rc-004-stakeholder-analysis.md @@ -0,0 +1,48 @@ +# Review Record: SA-001 Stakeholder Analysis + +## Metadata +| Key | Value | +| --- | --- | +| ID | RC-004 | +| CrossReference | [SA-001], [QC-SA-001] | + +## Version History +| Date | Status | Author | Reviewer | Change | Commit | +| --- | --- | --- | --- | --- | --- | +| 2026-10-10 | Proposed | Jens Tirsvad Nielsen | S05 | Initial version | pending | + +--- + +## Artifact Under Review + +- Instance reviewed: [SA-001] +- Checklist used: [QC-SA-001] + +## Checklist Results + +| # | Criterion | Status | Evidence/Notes | +| --- | --- | --- | --- | +| 1 | Power/Interest grid is filled for every stakeholder, with no gaps or unclassified entries | Pass | S01 to S05 each have Power, Interest and Quadrant. | +| 2 | Each stakeholder is assigned a unique, stable ID reusable for RACI assignments in other artifacts | Pass | IDs S01 to S05 are used by BC-001, PP-001 and the milestones. | +| 3 | Roles and organizational context are defined with explicit Power and Interest levels, not just narrative description | Pass | Role, organization and HIGH/MEDIUM/LOW levels per stakeholder, with a rationale section. | +| 4 | Communication needs (channel, frequency, deliverable type) are mapped to project phases or milestones | Pass | Communication Requirements table maps each stakeholder to a milestone. | +| 5 | Conflicting stakeholder interests are identified with documented mitigation or resolution strategies | Pass | Four conflicts, each with stakeholders and a mitigation. | +| 6 | Stakeholder concerns are explicitly traced to Business Case objectives | Pass | Business Goal Alignment maps each concern to O1 to O4 of BC-001. | +| 7 | Primary concerns are expressed in both business language and a recognized quality-attribute mapping (e.g. FURPS+) | Pass | Primary Concern column plus a FURPS+ mapping table. | +| 8 | Document is understandable and navigable by non-technical stakeholders reviewing their own entry | Pass | Plain-language summary table and one section per topic. | + +## Overall Verdict + +Go — all eight criteria pass, with two follow-ups that do not affect the criteria. Retrospective review prepared 2026-10-10 at the request of S01; the instance has been `Accepted` since 2026-10-03 and this record confirms it against the checklist. The author and the approving reviewer are the same person (S01); independent review by S05 is recorded in RC-001 and applies here too. + +## Action Items + +| Action | Owner | Due | +| --- | --- | --- | +| Update the Sign-Off section, which still says 'Pending review by S01 and S05', with a Version History row | S01 | 2026-10-17 | +| Identify the holders of the S03 role (listed as 'holders to be confirmed') | S01 | 2026-10-17 | + +--- + +[SA-001]: ../../stakeholder-analysis.md +[QC-SA-001]: ../../../framework/qc/qc-stakeholder-analysis.md diff --git a/docs/sqa/reviews/rc-005-mil-002.md b/docs/sqa/reviews/rc-005-mil-002.md new file mode 100644 index 0000000..86c2893 --- /dev/null +++ b/docs/sqa/reviews/rc-005-mil-002.md @@ -0,0 +1,45 @@ +# Review Record: MIL-002 + +## Metadata +| Key | Value | +| --- | --- | +| ID | RC-005 | +| CrossReference | [MIL-002], [QC-MIL-001] | + +## Version History +| Date | Status | Author | Reviewer | Change | Commit | +| --- | --- | --- | --- | --- | --- | +| 2026-10-10 | Proposed | Jens Tirsvad Nielsen | S05 | Initial version | pending | + +--- + +## Artifact Under Review + +- Instance reviewed: [MIL-002] +- Checklist used: [QC-MIL-001] + +## Checklist Results + +| # | Criterion | Status | Evidence/Notes | +| --- | --- | --- | --- | +| 1 | A concrete deliverable is defined for every gate | Pass | Deliverable: verified onboarding and operations guide, credential validation step and categorized failure messages. | +| 2 | Explicit Go/No-Go criteria are stated for each gate | Pass | Five criteria, each with an objectively checkable Go and No-Go column. | +| 3 | Dependencies on other milestones are explicitly mapped | Pass | Dependencies: depends on MIL-001, with the reason stated. | +| 4 | Each milestone is traceable to a Business Case objective or KPI | Pass | Traceability maps MIL-002 to O2 and O3 of BC-001. | +| 5 | Milestone owner and approving reviewer are identified | Pass | Owner S05 and approving reviewer S01. | +| 6 | Milestone has a defined target date consistent with project constraints | Pass | Target date 2026-10-31, marked proposed; the Business Case sets no deadline, so nothing contradicts it. | + +## Overall Verdict + +Go — all six criteria pass. Retrospective review prepared 2026-10-10 at the request of S01; the instance has been `Accepted` since 2026-10-03 and this record confirms it against the checklist. The author and the approving reviewer are the same person (S01); independent review by S05 is recorded in RC-001 and applies here too. + +## Action Items + +| Action | Owner | Due | +| --- | --- | --- | +| Confirm the proposed target date with S01 and S05 (the date is still marked proposed) | S05 | 2026-10-17 | + +--- + +[MIL-002]: ../../milestones/mil-002-onboarding-and-operations.md +[QC-MIL-001]: ../../../framework/qc/qc-milestones-gateways.md diff --git a/docs/sqa/reviews/rc-006-mil-003.md b/docs/sqa/reviews/rc-006-mil-003.md new file mode 100644 index 0000000..a43ea57 --- /dev/null +++ b/docs/sqa/reviews/rc-006-mil-003.md @@ -0,0 +1,45 @@ +# Review Record: MIL-003 + +## Metadata +| Key | Value | +| --- | --- | +| ID | RC-006 | +| CrossReference | [MIL-003], [QC-MIL-001] | + +## Version History +| Date | Status | Author | Reviewer | Change | Commit | +| --- | --- | --- | --- | --- | --- | +| 2026-10-10 | Proposed | Jens Tirsvad Nielsen | S05 | Initial version | pending | + +--- + +## Artifact Under Review + +- Instance reviewed: [MIL-003] +- Checklist used: [QC-MIL-001] + +## Checklist Results + +| # | Criterion | Status | Evidence/Notes | +| --- | --- | --- | --- | +| 1 | A concrete deliverable is defined for every gate | Pass | Deliverable: a reusable quality-check workflow used by one other repository, and a results guide. | +| 2 | Explicit Go/No-Go criteria are stated for each gate | Pass | Four criteria, each with an objectively checkable Go and No-Go column. | +| 3 | Dependencies on other milestones are explicitly mapped | Pass | Dependencies: depends on MIL-002, with the reason stated. | +| 4 | Each milestone is traceable to a Business Case objective or KPI | Pass | Traceability maps MIL-003 to O4 of BC-001. | +| 5 | Milestone owner and approving reviewer are identified | Pass | Owner S05 and approving reviewer S01. | +| 6 | Milestone has a defined target date consistent with project constraints | Pass | Target date 2026-11-14, marked proposed; the Business Case sets no deadline, so nothing contradicts it. | + +## Overall Verdict + +Go — all six criteria pass. Retrospective review prepared 2026-10-10 at the request of S01; the instance has been `Accepted` since 2026-10-03 and this record confirms it against the checklist. The author and the approving reviewer are the same person (S01); independent review by S05 is recorded in RC-001 and applies here too. + +## Action Items + +| Action | Owner | Due | +| --- | --- | --- | +| Confirm the proposed target date with S01 and S05 (the date is still marked proposed) | S05 | 2026-10-17 | + +--- + +[MIL-003]: ../../milestones/mil-003-quality-checks.md +[QC-MIL-001]: ../../../framework/qc/qc-milestones-gateways.md diff --git a/docs/sqa/reviews/rc-007-mil-004.md b/docs/sqa/reviews/rc-007-mil-004.md new file mode 100644 index 0000000..ff20b21 --- /dev/null +++ b/docs/sqa/reviews/rc-007-mil-004.md @@ -0,0 +1,45 @@ +# Review Record: MIL-004 + +## Metadata +| Key | Value | +| --- | --- | +| ID | RC-007 | +| CrossReference | [MIL-004], [QC-MIL-001] | + +## Version History +| Date | Status | Author | Reviewer | Change | Commit | +| --- | --- | --- | --- | --- | --- | +| 2026-10-10 | Proposed | Jens Tirsvad Nielsen | S05 | Initial version | pending | + +--- + +## Artifact Under Review + +- Instance reviewed: [MIL-004] +- Checklist used: [QC-MIL-001] + +## Checklist Results + +| # | Criterion | Status | Evidence/Notes | +| --- | --- | --- | --- | +| 1 | A concrete deliverable is defined for every gate | Pass | Deliverable: documented release process, consumer upgrade guide and a reusable release workflow. | +| 2 | Explicit Go/No-Go criteria are stated for each gate | Pass | Four criteria, each with an objectively checkable Go and No-Go column. | +| 3 | Dependencies on other milestones are explicitly mapped | Pass | Dependencies: depends on MIL-003, with the reason stated. | +| 4 | Each milestone is traceable to a Business Case objective or KPI | Pass | Traceability maps MIL-004 to O4 of BC-001. | +| 5 | Milestone owner and approving reviewer are identified | Pass | Owner S05 and approving reviewer S01. | +| 6 | Milestone has a defined target date consistent with project constraints | Pass | Target date 2026-11-28, marked proposed; the Business Case sets no deadline, so nothing contradicts it. | + +## Overall Verdict + +Go — all six criteria pass. Retrospective review prepared 2026-10-10 at the request of S01; the instance has been `Accepted` since 2026-10-03 and this record confirms it against the checklist. The author and the approving reviewer are the same person (S01); independent review by S05 is recorded in RC-001 and applies here too. + +## Action Items + +| Action | Owner | Due | +| --- | --- | --- | +| Confirm the proposed target date with S01 and S05 (the date is still marked proposed) | S05 | 2026-10-17 | + +--- + +[MIL-004]: ../../milestones/mil-004-versioned-release.md +[QC-MIL-001]: ../../../framework/qc/qc-milestones-gateways.md diff --git a/docs/sqa/traceability-matrix.md b/docs/sqa/traceability-matrix.md new file mode 100644 index 0000000..a2b2f11 --- /dev/null +++ b/docs/sqa/traceability-matrix.md @@ -0,0 +1,63 @@ +# Traceability Matrix + +## Metadata +| Key | Value | +| --- | --- | +| ID | TM-001 | +| CrossReference | [BC-001], [SA-001], [PP-001], [MIL-001], [MIL-002], [MIL-003], [MIL-004], [RC-001], [RC-002], [RC-003], [RC-004], [RC-005], [RC-006], [RC-007] | + +## Version History +| Date | Status | Author | Reviewer | Change | Commit | +| --- | --- | --- | --- | --- | --- | +| 2026-10-10 | Proposed | Jens Tirsvad Nielsen | S05 | 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. + +## Traceability Table + +| Artifact Instance | Type | Upstream (Backward Link) | Downstream (Forward Link) | Last Reviewed (RC-ID) | +| --- | --- | --- | --- | --- | +| [SA-001] | SA | - | [BC-001] | [RC-004] | +| [BC-001] | BC | [SA-001] | [PP-001], [MIL-001], [MIL-002], [MIL-003], [MIL-004] | [RC-001] | +| [PP-001] | PP | [BC-001], [SA-001] | [MIL-001], [MIL-002], [MIL-003], [MIL-004] | [RC-002] | +| [MIL-001] | MIL | [BC-001], [PP-001] | [MIL-002] | [RC-003] | +| [MIL-002] | MIL | [BC-001], [PP-001], [MIL-001] | [MIL-003] | [RC-005] | +| [MIL-003] | MIL | [BC-001], [PP-001], [MIL-002] | [MIL-004] | [RC-006] | +| [MIL-004] | MIL | [BC-001], [PP-001], [MIL-003] | - | [RC-007] | +| [RC-001] | RC | [BC-001] | - | - | +| [RC-002] | RC | [PP-001] | - | - | +| [RC-003] | RC | [MIL-001] | - | - | +| [RC-004] | RC | [SA-001] | - | - | +| [RC-005] | RC | [MIL-002] | - | - | +| [RC-006] | RC | [MIL-003] | - | - | +| [RC-007] | RC | [MIL-004] | - | - | + +## Coverage Notes + +- `-` in Upstream means foundational (SA-001 has no prerequisite). In Downstream it means nothing is built on the instance yet. In Last Reviewed it means no `RC-*` exists (review records are not themselves reviewed). +- Types with no instance yet: KPI, BMC, BPMN, UCD, US, UC, SSD, DM, OC, SD, DCD, ERD, ADR, GOV, DICT. The Project Plan lists use case candidates, but the formal use cases wait for a use case diagram and user stories. +- PP-001 and TM-001 have no QC checklist; RC-002 validated PP-001 against its Business Case constraints and the milestone Go / No-Go criteria. TM-001 has no review record. +- All review records are `Proposed`; the author and S01 are the same person, so an independent review by S05 is outstanding (see RC-001). + +--- + +[BC-001]: ../business-case.md +[SA-001]: ../stakeholder-analysis.md +[PP-001]: ../project-plan.md +[MIL-001]: ../milestones/mil-001-stabilise-metadata-sync.md +[MIL-002]: ../milestones/mil-002-onboarding-and-operations.md +[MIL-003]: ../milestones/mil-003-quality-checks.md +[MIL-004]: ../milestones/mil-004-versioned-release.md +[RC-001]: ./reviews/rc-001-business-case.md +[RC-002]: ./reviews/rc-002-project-plan.md +[RC-003]: ./reviews/rc-003-mil-001.md +[RC-004]: ./reviews/rc-004-stakeholder-analysis.md +[RC-005]: ./reviews/rc-005-mil-002.md +[RC-006]: ./reviews/rc-006-mil-003.md +[RC-007]: ./reviews/rc-007-mil-004.md