1. Brief Description

The goal of this use case is to allow the player to customize aspects of the settings to their liking. This consists of presenting the various settings to the player and allowing them to alter it to their needs.

2. Included Use Cases

N/A

3. Preconditions

4. Flow of Events

4.1 Basic Flow – The settings will be altered to the player’s preferences.

1. This use case begins when the player selects Settings.
2. The system presents the Settings Menu.
3. The player selects a setting and alter it.
4. The system validates that it is a valid input for that specific setting
5. The system saves the change.
6. The player may repeat Steps 3-5 until exiting the Settings Menu
7. The use case ends.

4.2 Alternative Flows

None

4.3 Exception Flows

E1: The system determines that invalid input for a setting has been entered.

1. This flow begins when the system determines that the input entered for a specific setting is invalid.
2. The system presents a message informing the player that the input is invalid, and displays a range of valid, acceptable input for that setting.
3. The flow returns to basic flow: step 3.

5. Requirements

N/A

6. Post-conditions

a) The player’s settings are now altered and saved to their preferences.

7. Notes & Open Issues

8. Out of Scope (Future Functionality)

---

Appendix A – Data Definition for Change Settings