Use Cases

From Secure Computing Wiki
Revision as of 22:49, 20 September 2010 by Benjamincrist (Talk | contribs)

Jump to: navigation, search
Use Case UC1: Play Game
Scope: Laser Chess application

Level: User goal
Primary Actor: Player
Stakeholders and Interests:
- Player: plays the game as a form of entertainment.
- Company: wants to ensure game flows as intended and players enjoy playing the game.
- Advertiser: wants players to view and interact with their advertisement(s) within the game.
Preconditions: Player has application installed.
Success Guarantee: Player plays through an entire game.
Main Success Scenario:
1. Player starts the application and initiates a game mode: Single Player, Two Player Mode, or Online Multiplayer.
2. Game is initiated, sides are chosen, and the player who moves first is selected.
3. Play begins and player makes move(s).
4. AI or human opponent takes turn making move(s).
5. Steps 3 and 4 are repeated until a winner is declared.
Extensions:
1. Player exits game before a winner is declared:
- a. The player who exits the game forfeits.
2. Player times-out (fails to make a move within 7 days):
- a. The player whose turn was pending forfeits the game.


Use Case UC2: Register Player
Scope: Laser Chess application

Level: User goal
Primary Actor: Player
Stakeholders and Interests:
- Player: wants to experience online multiplayer mode and/or be notified of the game's updates, improvements, or other news
- Company: wants to know more about the game's players for marketing and customized experiences
Preconditions: Player has application installed.
Success Guarantee: Player registers
Main Success Scenario: <A typical, unconditional happy path scenario of success>
Extensions: <Alternate scenarios of success or failure>


Use Case UC3: Obtain Support
Scope: <The system under design>

Level: <”user-goal” or “subfunction”>
Primary Actor: <Calls on the system to deliver its services>
Stakeholders and Interests: <Who cares about this use case, and what do they want?>
Preconditions: <What must be true on start, and worth telling the reader?>
Success Guarantee: <What must be true on successful completion, and worth telling the reader?>
Main Success Scenario: <A typical, unconditional happy path scenario of success>
Extensions: <Alternate scenarios of success or failure>
Special Requirements: <Related non-functional requirements>
Technology and Data Variations List: <Varying I/O methods and data formats>
Frequency of Occurrence: <Influences investigation, testing, and timing of implementation>
Miscellaneous: <Such as open issues>


Project Topics