Tirsvad
1cd27f77ed
- MIL-006: the AGPL-3.0 default needs GitHub and a public project - MIL-007: fetch the framework's own submodules (qc); start through a command link; README usage - UC-002 with SSD, DM, OC, SD and DCD; US-001.07 and US-002 - Reconcile the project DM, DCD, dictionary, use case diagram and traceability matrix - Review records RC-022 to RC-028
4.3 KiB
4.3 KiB
SQA Review Record: MIL-007 and the planning changes it causes
Metadata
| Key | Value |
|---|---|
| ID | RC-022 |
| CrossReference | MIL-007, QC-MIL-001, MIL-006, BC-001, US-001, UC-002, PP-001 |
Version History
| Date | Status | Author | Reviewer | Change | Commit |
|---|---|---|---|---|---|
| 2026-10-07 | Proposed | Jens Tirsvad Nielsen | S02 | Initial version | pending |
Artifact Under Review
- Instance reviewed: MIL-007, and the changes it causes in MIL-006, BC-001, US-001, PP-001 and TM-001. The use case and its artifacts are reviewed in RC-023, RC-024, RC-025, RC-026, RC-027 and RC-028.
- Checklist used: QC-MIL-001 for MIL-007. The other artifacts were changed, not created; their change is checked below.
- Review date: 2026-10-07
Checklist Results (QC-MIL-001)
| # | Criterion | Status | Evidence/Notes |
|---|---|---|---|
| 1 | A concrete deliverable is defined for every gate | Pass | The script that fetches the framework's own submodules and starts through a command link, plus the README usage section. |
| 2 | Explicit Go/No-Go criteria are stated for each gate | Pass | Eight criteria, each with an objective Go and No-Go, including every acceptance criterion of US-001.07 and US-002. |
| 3 | Dependencies on other milestones are explicitly mapped | Pass | Depends on MIL-003 (the framework step and README exist), with the reason. |
| 4 | Each milestone is traceable to a Business Case objective or KPI | Pass | Objectives 5, 7 and 11 and success criterion 11 of BC-001; US-001.07 and US-002. |
| 5 | Milestone owner and approving reviewer are identified | Pass | Owner S01, approving reviewer S02. |
| 6 | Milestone has a defined target date consistent with project constraints | Pass | 2026-12-11 matches PP-001; the Business Case sets no deadline. A proposal for S01 to confirm. |
Change checks on the other artifacts
| Artifact | Change | Status | Evidence/Notes |
|---|---|---|---|
| MIL-006 | AGPL-3.0 default only when GitHub is chosen and the project is public (purpose, order, criterion 3, tasks 1 and 4) | Pass | Criterion 3 is objective in both directions: AGPL-3.0 on a private project is a No-Go, and so is none on a public project with GitHub. Tasks and tests follow. |
| BC-001 | Objectives 2, 5, 10, 11; scope items; success criteria 10 and 11 | Pass | Objective 2 and criterion 10 name the public-only default; objective 11 and criterion 11 are new and measurable. |
| US-001 | US-001.06 reworded; US-001.07 and US-002 added; story count updated | Pass | Given/when/then; each traces to its use case and milestone; INVEST exceptions stated. |
| PP-001 | Phase MIL-007, dependency chain, timeline, scope coverage, end date 2026-12-11 | Pass | Dates agree with MIL-007. One point carried over from earlier plans: the assumption "phase length: two weeks" is not true of MIL-005, MIL-006 and MIL-007, which are one week. |
| TM-001 | Rows for MIL-007 and the UC-002 artifacts | Pass | Upstream and downstream columns agree with the CrossReference of each document. |
Overall Verdict
Go — MIL-007 meets every mandatory criterion and the changes to the other artifacts are consistent. Drafted by Claude Code for S02 against the checklist; the author and reviewer are the same person for now (as in the earlier records). The verdict takes effect, and the Version History rows of the reviewed documents change to Accepted, only when S02 confirms it.
Action Items
| Action | Owner | Due |
|---|---|---|
| Say in the plan assumptions that the later phases are one week, not two (or correct the phase length) | S01 | Before MIL-006 starts |
| Confirm the proposed target date 2026-12-11 | S01 | Before MIL-007 starts |