Tirsvad
c7164feab1
Review the use case chain for Play a Game (RC-007 to RC-010, all Go) and accept the four documents. Update the Traceability Matrix.
2.2 KiB
2.2 KiB
UC-001 Play a Game
Metadata
| Key | Value |
|---|---|
| ID | UC-001 |
| CrossReference | UCD-001, US-001, SA-001, SSD-001, RC-009 |
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-009 | pending |
Format: Fully Dressed
Scope
The Higher Lower console game.
Level
User goal.
Primary Actor
Player.
Stakeholders and Interests
| Stakeholder | Interest |
|---|---|
| S01 | A correct game that shows good practice (SA-001) |
| S02 | Readable behaviour that matches the assignment (SA-001) |
Preconditions
The Player has started the game.
Postconditions (Success Guarantee)
The Player has seen the final score of the game.
Main Success Scenario
- The Player starts a game.
- The System shows two different accounts, A and B.
- The Player guesses which account has more followers.
- The System tells the Player the guess was right, adds one to the score, and shows the new score.
- The System makes the account the Player compared against the new A and shows a new B.
- The Player repeats from step 3 until a guess is wrong.
- The System tells the Player the guess was wrong and shows the final score.
Extensions / Alternative Flows
- 3a. The Player gives an answer that is not a valid choice: the System asks again; the round does not change.
- 3b. Both accounts have the same number of followers: either choice counts as right.
- 5a. No account is left that differs from the current A: the System ends the game and shows the final score.
No <<include>> or <<extend>> use cases apply.
Special Requirements / Business Rules
- Step 2 and 5: A and B are never the same account.
- Step 3b: equal follower counts make both choices right.
Open Issues
None.