- 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.4 KiB
4.4 KiB
SQA Review Record: DM-003 Start the script as a global command, and the dictionary
Metadata
| Key | Value |
|---|---|
| ID | RC-025 |
| CrossReference | DM-003, QC-DM-001, QC-DICT-001, DICT-001, DM-002 |
Version History
| Date | Status | Author | Reviewer | Change | Commit |
|---|---|---|---|---|---|
| 2026-10-07 | Proposed | Jens Tirsvad Nielsen | S02 | Initial version | pending |
Artifact Under Review
- Instance reviewed: DM-003, and the changes it causes in DM-002 and DICT-001.
- Checklists used: QC-DM-001 for DM-003; QC-DICT-001 for DICT-001.
- Review date: 2026-10-07
Checklist Results (QC-DM-001)
| # | Criterion | Status | Evidence/Notes |
|---|---|---|---|
| 1 | Uses ubiquitous/business language throughout; no technical or implementation jargon (e.g. no "table", "class", "pointer") | Pass | Command Link, Checkout and Working Folder are Maintainer terms. "Checkout" is also a git word; it is kept because it names the folder the Maintainer cloned. |
| 2 | Multiplicities on associations are correct and complete (e.g. 1..*, 0..1) |
Pass | Every association has a multiplicity on both ends. |
| 3 | No operation/method signatures shown — attributes and associations only | Pass | Attributes and associations only. |
| 4 | Associations are named with an unambiguous reading direction | Pass | Every association has a reading direction in the table. |
| 5 | Generalization/specialization used correctly, reflecting true "is-a" relationships, not misused for code reuse | N-A | No generalization. |
| 6 | Every concept traces to a noun phrase found in the use cases or glossary | Pass | Each new concept cites its use case step. The concepts Maintainer, Configuration and Local Project come from DM-001 and are stated as not redefined. |
| 7 | Attributes are simple domain data (no foreign-key-like references or object pointers modeled as attributes) | Pass | folder and path are simple data; the links to other concepts are associations. |
Checklist Results (QC-DICT-001)
| # | Criterion | Status | Evidence/Notes |
|---|---|---|---|
| 1 | Every row has a PO term, its language, an IT term and a definition | Pass | Three new rows, each with PO term, language, IT term and definition. |
| 2 | Each PO term maps to exactly one IT term and the reverse (no synonyms) | Pass | One IT term per PO term and the reverse: Command Link / CommandLink, Checkout / Checkout, Working Folder / WorkingFolder. |
| 3 | Every Domain Model concept has a row, and the Domain Model uses its PO term | Pass | Every concept of DM-003 and of DM-002 has a row. |
| 4 | The Operation Contracts, Sequence Diagrams, Design Class Diagrams and ERD use the IT term, not the PO term | Pass | OC-002, SD-002 and DCD-003 use the IT terms. CommandLink appears in OC-002 only: it is a link the Maintainer makes, so it has no design class, which the DCD and the dictionary say. |
| 5 | Definitions are written in the PO language and are one sentence | Pass | One-sentence definitions in English, the PO language. |
| 6 | "Used as PO term in" and "Used as IT term in" name artifact types that exist in the project | Pass | Names DM, UC, OC, SD and DCD, which exist. |
| 7 | Translated artifacts (<artifact>.<language>.md) use the PO terms of the dictionary |
N-A | The PO language is English. |
Change checks on the other artifacts
| Artifact | Change | Status | Evidence/Notes |
|---|---|---|---|
| DM-002 | Three concepts and five associations added | Pass | Diagram, concept table and association table changed in the same way as DM-003; Purpose names UC-002. |
Overall Verdict
Go — DM-003 and the dictionary meet every mandatory criterion. 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 |
|---|---|---|
| None | - | - |