| 1 |
Actors are defined with correct UML stereotypes (e.g. <<System>>, <<Actor>>) |
Pass |
Software Engineer is <<Actor>>, like the others. |
| 2 |
System boundary is clearly drawn and labeled |
Pass |
Unchanged. |
| 3 |
Include/extend relationships are used correctly per UML 2.5.1, not as generic "uses" arrows |
Pass |
Unchanged; the new use case has none. |
| 4 |
Every actor participates in at least one use case (no orphan actors) |
Pass |
Software Engineer reaches Run Project Quality Checks. |
| 5 |
Diagram is traceable to a documented stakeholder need |
Pass |
S02 in the Actor Table. |
| 6 |
Use case names are verb phrases describing actor goals, not internal system operations |
Pass |
"Run Project Quality Checks". |
| 7 |
Diagram is free of implementation detail (e.g. UI widgets, database tables) |
Pass |
No tool or file named. |
| 8 |
Actor and use case naming is consistent with corresponding Use Case and User Story documents |
Pass |
Checked mechanically: UC-005's title and the story role match. |