Files
014-higher_lower/docs/use-case-diagram.md

1.7 KiB

Use Case Diagram

Metadata

Key Value
ID UCD-001
CrossReference SA-001, BC-001, US-001, UC-001, RC-007

Version History

Date Status Author Reviewer Change Commit
2026-10-04 Deprecated Jens Tirsvad Nielsen S01 Initial version 923dde7
2026-10-04 Accepted Jens Tirsvad Nielsen S01 Accepted after review RC-007 c7164fe

Purpose and Scope

The system boundary is the Higher Lower console game. One actor, the Player, uses it to play a game. Traces to BC-001 objective O1 and to stakeholders S01 and S02 (SA-001), who play the game; S03 only reads the repository.

Diagram

@startuml
left to right direction
actor Player <<Actor>>
rectangle "Higher Lower <<System>>" {
  usecase "Play a Game" as PlayAGame
}
Player --> PlayAGame
@enduml

Actor Table

Actor Stereotype Stakeholder ID (SA) Goals (use cases)
Player Actor S01, S02 Play a Game

Use Case Table

Use Case Actor(s) Goal
Play a Game (UC-001) Player Guess, round after round, which of two accounts has more followers, and see the final score

Relationships

None: there is a single use case, so no <<include>> or <<extend>> is used.