# SQA Review Record: UC-002 Start the script as a global command ## Metadata | Key | Value | | --- | --- | | ID | RC-023 | | CrossReference | [UC-002], [QC-UC-001], [UC-001], [UCD-001], [US-001] | ## Version History | Date | Status | Author | Reviewer | Change | Commit | | --- | --- | --- | --- | --- | --- | | 2026-10-07 | Proposed | Jens Tirsvad Nielsen | S02 | Initial version | [1cd27f7] | --- ## Artifact Under Review - Instance reviewed: [UC-002], and the changes it causes in [UC-001] and [UCD-001]. - Checklist used: [QC-UC-001] (Fully Dressed). - Review date: 2026-10-07 ## Checklist Results (QC-UC-001) | # | Criterion | Status | Evidence/Notes | | --- | --- | --- | --- | | 1 | Consists of a single, concise paragraph summarizing only the primary success scenario | N-A | Format is Fully Dressed. | | 2 | Written as an informal multi-paragraph narrative; may mention some alternate flows without formal structure | N-A | Format is Fully Dressed. | | 3 | All standard sections are present: actors, preconditions, postconditions, main success scenario, alternative/exception flows | Pass | Actor, stakeholders, preconditions, postconditions, main scenario, extensions, rules and open issues are present. | | 4 | Preconditions and postconditions are explicitly defined | Pass | Preconditions name the checkout, the config files and a writable `PATH` folder; postconditions name the link, the working folder and that nothing else was written. | | 5 | Primary actor is explicitly stated | Pass | Primary actor: Maintainer, as in [UCD-001]. | | 6 | Stakeholders and their interests are stated | Pass | S01, S02 and S03 with their interests. | | 7 | Main success scenario is written as clear, numbered steps | Pass | Six numbered steps; steps 1 and 2 are the Maintainer's, 3 to 6 the system's. | | 8 | Alternative/exception flows correctly reference `<>`/`<>` use cases where relevant, per UML 2.5.1 | Pass | Step 5 `<>` [UC-001], and [UCD-001] shows the same relationship. | | 9 | Explicit business rules are captured per step where applicable, rather than embedded loosely in narrative text | Pass | Five rules, each tied to a step. | | 10 | Naming of actors and use case title is consistent with the corresponding Use Case Diagram and User Stories | Pass | Title "Start the script as a global command" and actor equal those of [UCD-001] and US-002. | | 11 | Scope/level (e.g. summary, user-goal, subfunction) is explicitly stated | Pass | Level user-goal and scope are stated. | | 12 | Use case is written from the actor's goal perspective, free of UI or implementation detail | Pass | Written as the Maintainer's goal. It names `PATH`, `--config` and `--env`, which are the Maintainer's own vocabulary for this system, as in [UC-001]; the rule that named a missing tool was reworded to "on every supported platform" during this review. | ## Change checks on the other artifacts | Artifact | Change | Status | Evidence/Notes | | --- | --- | --- | --- | | [UC-001] | Step 6 and rule 6 (public-only AGPL-3.0 default); step 9 and extension 9e (the framework's own submodules) | Pass | Extension 9e stops the step and names the command to run by hand, without a credential; consistent with US-001.07 and MIL-007. | | [UCD-001] | UC-002 added with `<>` [UC-001] | Pass | Diagram, actor table, use case table and relationship table agree. | ## Overall Verdict Go — [UC-002] meets 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 | - | - | --- [UC-002]: ../../uc-002/uc.md [UC-001]: ../../uc-001/uc.md [UCD-001]: ../../use-case-diagram.md [US-001]: ../../user-stories.md [QC-UC-001]: ../../../framework/qc/qc-use-case.md [1cd27f7]: https://git.tirsystem.com/TirSystem-BashScript/repo_foundry/commit/1cd27f77ed844773a969210a11de0d8bb98ac98f