| 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 <<include>>/<<extend>> use cases where relevant, per UML 2.5.1 |
Pass |
Step 5 <<include>> 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. |
