4.3 KiB
4.3 KiB
SQA Review Record: MIL-004 and the planning change it causes
Metadata
| Key | Value |
|---|---|
| ID | RC-018 |
| CrossReference | MIL-004, QC-MIL-001, US-001, UC-001 |
Version History
| Date | Status | Author | Reviewer | Change | Commit |
|---|---|---|---|---|---|
| 2026-10-05 | Proposed | Jens Tirsvad Nielsen | S02 | Initial version | 2a6bb8e |
Artifact Under Review
- Instance reviewed: MIL-004, and the changes it causes in BC-001, US-001, UC-001, SSD-001, OC-001, SD-001, DM-001, DM-002 and PP-001.
- Checklist used: QC-MIL-001 for MIL-004. The other artifacts were changed, not created; their change is checked below for consistency with the checklists of their types (user story, use case, SSD, operation contract, sequence diagram, domain model) and with the PP reference.
- Review date: 2026-10-05
Checklist Results (MIL-004, QC-MIL-001)
| # | Criterion | Status | Evidence/Notes |
|---|---|---|---|
| 1 | A concrete deliverable is defined for every gate | Pass | The script reads eight optional keys, skips their prompts and marks the source; the example config and the README document the keys; tests cover each key. |
| 2 | Explicit Go/No-Go criteria are stated for each gate | Pass | Eight criteria, each with an objective Go and No-Go, including all acceptance criteria of US-001.04. |
| 3 | Dependencies on other milestones are explicitly mapped | Pass | Depends on [MIL-003], with the reason. |
| 4 | Each milestone is traceable to a Business Case objective or KPI | Pass | Maps to objective 8 and success criterion 8 of BC-001, and to US-001.04. |
| 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-11-20 matches PP-001; the Business Case sets no duration, so nothing conflicts. The date is a proposal and is accepted here. |
Change checks on the other artifacts
| Artifact | Change | Status | Evidence/Notes |
|---|---|---|---|
| BC-001 | Objective 8, scope item, success criterion 8 | Pass | The criterion is measurable (tests with each key set, absent, empty and invalid). |
| US-001 | US-001.04 with four acceptance criteria | Pass | Given/when/then; traces to UC-001 step 3 and MIL-004; size and INVEST exception recorded. |
| UC-001 | Precondition, step 3 note, extensions 3a and 3b, business rule | Pass | Extensions name the failure (invalid key) and the outcome (stop before any request, no fallback to asking). |
| SSD-001 | Parameters of provideProjectDetails may come from config.env |
Pass | The message itself is unchanged, so the diagram is unchanged. |
| OC-001 | Preset details are part of the Configuration | Pass | Postcondition and rule added; no new operation. |
| SD-001 | Note that ConfigLoader reads and validates the preset details |
Pass | The second sequence is unchanged because the arguments are the same whether asked or preset. |
| DM-001, DM-002 | Configuration may hold preset project details |
Pass | Both models changed in the same way and the project model stays consistent with the use-case model, as the project rule requires. Dictionary unchanged: no new term. |
| PP-001 | Phase MIL-004, dependency chain and timeline | Pass | Dates agree with MIL-004; scope table and Gantt updated. |
Overall Verdict
Go — MIL-004 passes every mandatory criterion and the changes to the other artifacts are consistent with each other and with the Business Case. Author and reviewer are the same person for now (S01 and S02 are both held by the Maintainer), so the framework independence rule is not met; re-review when a second person takes S02.
Action Items
| Action | Owner | Due |
|---|---|---|
| None | - | - |