| 1 |
Consists of a single, concise paragraph summarizing only the primary success scenario |
N-A |
Applies to the Brief format only; this use case is Fully Dressed. |
| 2 |
Written as an informal multi-paragraph narrative; may mention some alternate flows without formal structure |
N-A |
Applies to the Casual format only; this use case is Fully Dressed. |
| 3 |
All standard sections are present: actors, preconditions, postconditions, main success scenario, alternative/exception flows |
Pass |
Scope, level, actor, stakeholders, pre/postconditions, scenario, extensions, rules and open issues present. |
| 4 |
Preconditions and postconditions are explicitly defined |
Pass |
Both defined. |
| 5 |
Primary actor is explicitly stated |
Pass |
Player. |
| 6 |
Stakeholders and their interests are stated |
Pass |
S01 and S02 with interests. |
| 7 |
Main success scenario is written as clear, numbered steps |
Pass |
Seven numbered steps. |
| 8 |
Alternative/exception flows correctly reference <<include>>/<<extend>> use cases where relevant, per UML 2.5.1 |
Pass |
No include/extend applies; stated. |
| 9 |
Explicit business rules are captured per step where applicable, rather than embedded loosely in narrative text (Optional) |
Pass |
Rules listed for steps 2, 3b and 5. |
| 10 |
Naming of actors and use case title is consistent with the corresponding Use Case Diagram and User Stories |
Pass |
Title and actor match UCD-001 and US-001. |
| 11 |
Scope/level (e.g. summary, user-goal, subfunction) is explicitly stated (Optional) |
Pass |
Level: user goal. |
| 12 |
Use case is written from the actor's goal perspective, free of UI or implementation detail |
Pass |
Goal wording, no UI or implementation detail. |
