| 1 |
Actors are defined with correct UML stereotypes (e.g. <<System>>, <<Actor>>) |
Pass |
DevOps Professional and Platform Operator are <<Actor>>; Gitea Instance and GitHub are <<System>>. |
| 2 |
System boundary is clearly drawn and labeled |
Pass |
Boundary "Reusable Workflow Collection". |
| 3 |
Include/extend relationships are used correctly per UML 2.5.1, not as generic "uses" arrows |
Pass |
One include and one extend, each with a justification in the Relationships table; the extend applies only on failure. |
| 4 |
Every actor participates in at least one use case (no orphan actors) |
Pass |
All four actors appear in the Actor Table with goals. |
| 5 |
Diagram is traceable to a documented stakeholder need |
Pass |
S05, S03 and S04 in the Actor Table; SA-001 and BC-001 cited. |
| 6 |
Use case names are verb phrases describing actor goals, not internal system operations |
Pass |
Four goal names, none a system operation. |
| 7 |
Diagram is free of implementation detail (e.g. UI widgets, database tables) |
Pass |
No tool, file or UI detail. |
| 8 |
Actor and use case naming is consistent with corresponding Use Case and User Story documents |
Pass |
Checked mechanically: all four titles and both story roles match. |
