Files
014-higher_lower/docs/user-stories.md
T
Tirsvad 923dde7dc9 Accept MIL-003 and add the Play a Game use case
Create the use case chain for the game loop task: Use Case Diagram
UCD-001, User Stories US-001 (two stories), Use Case UC-001 and System
Sequence Diagram SSD-001, all Proposed. Link them from MIL-003.

Review MIL-003 (RC-006, Go) and accept it. Add the new artifacts to the
Traceability Matrix and register UCD, US, UC and SSD in the artifact
registry.

Refs #13
2026-10-04 23:41:35 +08:00

1.9 KiB

User Stories

Metadata

Key Value
ID US-001
CrossReference UCD-001, UC-001, BC-001, MIL-003

Version History

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

Purpose and Scope

The stories for epic MIL-003 (Console game): playing rounds and seeing the result. They support BC-001 objective O1.

Story List

US-001.01 Guess which account has more followers

  • As a Player, I want to guess which of two accounts has more followers and keep playing while I am right, so that I can build a streak.
  • Acceptance Criteria:
    • Given a new game, when it starts, then two different accounts A and B are shown.
    • Given two accounts, when I guess the one with more followers, then my score goes up by one and the next round starts with that account as A and a new account as B.
    • Given an invalid answer, when I submit it, then I am asked again and the round does not change.
  • Traces to: UC-001, MIL-003
  • Size: one iteration.

US-001.02 See my final score

  • As a Player, I want to see my final score when the game ends, so that I know how well I did.
  • Acceptance Criteria:
    • Given a round, when I guess the account with fewer followers, then the game ends and shows my final score.
    • Given every account has been used, when no new account can be shown, then the game ends and shows my final score.
  • Traces to: UC-001, MIL-003
  • Size: one iteration.

INVEST Check

Both stories are Independent of each other in wording, Negotiable in detail, Valuable to the Player, Estimable, Small (one iteration) and Testable through the acceptance criteria. No exceptions.