| 1 |
Actors are defined with correct UML stereotypes (e.g. <<System>>, <<Actor>>) |
Pass |
Unchanged; no new actor. |
| 2 |
System boundary is clearly drawn and labeled |
Pass |
The new use case is inside the Reusable Workflow Collection rectangle. |
| 3 |
Include/extend relationships are used correctly per UML 2.5.1, not as generic "uses" arrows |
Pass |
The new use case has no include or extend; the existing two are unchanged. |
| 4 |
Every actor participates in at least one use case (no orphan actors) |
Pass |
Software Engineer is linked to UC5, UC7 and UC8. |
| 5 |
Diagram is traceable to a documented stakeholder need |
Pass |
S02 and S05 interests are in UC-008; the actor table lists S02. |
| 6 |
Use case names are verb phrases describing actor goals, not internal system operations |
Pass |
Show Code Metrics and Coverage Badges. |
| 7 |
Diagram is free of implementation detail (e.g. UI widgets, database tables) |
Pass |
None added. |
| 8 |
Actor and use case naming is consistent with corresponding Use Case and User Story documents |
Pass |
Equals the title of UC-008 and the role of US-001.18 to US-001.20. |