014-higher_lower/docs/sqa/reviews/rc-007-ucd-001.md

SQA Review Record: UCD-001 Use Case Diagram

Metadata

Key	Value
ID	RC-007
CrossReference	UCD-001, QC-UCD-001

Version History

Date	Status	Author	Reviewer	Change	Commit
2026-10-04	Accepted	Jens Tirsvad Nielsen	S01	Initial version	c7164fe

---

Artifact Under Review

• Instance reviewed: UCD-001
• Checklist used: QC-UCD-001

Checklist Results

#	Criterion	Status	Evidence/Notes
1	Actors are defined with correct UML stereotypes (e.g. <<System>>, <<Actor>>)	Pass	Actor <> and boundary <> stereotyped.
2	System boundary is clearly drawn and labeled	Pass	Boundary rectangle labelled Higher Lower.
3	Include/extend relationships are used correctly per UML 2.5.1, not as generic "uses" arrows	Pass	No include/extend used; the Relationships section says so.
4	Every actor participates in at least one use case (no orphan actors)	Pass	Player is in Play a Game.
5	Diagram is traceable to a documented stakeholder need	Pass	Player traces to S01 and S02 in SA-001.
6	Use case names are verb phrases describing actor goals, not internal system operations	Pass	Play a Game is an actor goal.
7	Diagram is free of implementation detail (e.g. UI widgets, database tables) (Optional)	Pass	No UI or storage detail.
8	Actor and use case naming is consistent with corresponding Use Case and User Story documents (Optional)	Pass	Names match US-001 and UC-001.

Overall Verdict

Go — all applicable criteria pass. Reviewer and author are both S01: the project has a single participant, so the framework's author/reviewer separation cannot be met. S01 accepted this deviation when requesting acceptance (2026-10-04).

Action Items

Action	Owner	Due
None	—	—

---