Defensive Driving Simulator

  Home

  Demo

  About

  Documentation

  Development

  Contact us

 

Detailed Use Cases:

Identification: UC 1 : Start Game

Primary Actor: Player
Stakeholders and Interests:
  • Player:
    • Wants to start a driving game either for fun or training
Preconditions:
  • System is loaded in a web browser.
Postconditions:
  • A new game has been started.
Main Success Scenario:
  1. Player loads the system and chooses to start a new game.
  2. Player selects difficulty level and a default map is loaded.
  3. The driving simulation starts.
Extensions and Alternative Flows:
  • None
Special Requirements:

Technology and Data Variation List:
  • The user must have internet access.
  • The user must have an advanced web browser installed which can support highly-interactive possibly-embedded portable software. The goal for such a platform is to relax installation efforts.
  • User's computing system should have 3D support, and capability of achieving framerates of at least 25 fps.
Frequency of Occurrence:
  • Every time the user navigates to the web page containing the software.
Open Issues:
  • None at this time.





Identification: UC1.1 : Choose Difficulty

Primary Actor: Player
Stakeholders and Interests:
  • Player:
    • Wants to choose level of difficulty of simulation.
Preconditions:
  • UC 1 has successfully completed.
Postconditions:
  • A default map is loaded using the selected difficulty.
  • Game screen comes up awaiting user input.
Main Success Scenario:
  1. User chooses a diffulty level.
  2. A new map is successfully loaded with traps set up throughout.
  3. The simulation is rendered and begins accepting user input.
Extensions and Alternative Flows:
  • None
Frequency of Occurrence:
  • As desired by the player throughout the simulation. Usuaully, this is set once per game.
Open Issues:
  • None at this time.




Identification: UC2 : Plays Game

Primary Actor : Player
Stakeholders and Interests :
  • Player:
    • Wants to drive through the simulation (player is encouraged to improve driving skills).
    • Needs to avoid hazards in order to progress through the level.
    • Ultimately, the player wants to complete each level in the simulation to win the game.
Preconditions :
  • UC1.1 have completed successfully.
Postconditions :
  • The player is playing the driving simulation.
Main Success Scenario :
  • The player completes driving objectives for each level and the game ends. User actions necessary to fulfill objectives are in Extensions UC 2.0.x
Extensions and Alternative Flows :
  • The player quits while in the game.
  • The player wrecks.
  • The player runs out of time.
Frequency of Occurrence:
  • As often as once per game.
Open Issues:
  • None at this time.



Identification: UC2.0.1 : Accelerate

Primary Actor : Player
Stakeholders and Interests :
  • Player:
    • The player wants to accelerate their vehicle.
Preconditions :
  • UC 2 has successfully completed.
Postconditions :
  • The player's vehicle has accelerated.
Main Success Scenario :
  • The player elects to accelerate vehicle
  • Player presses the acceleration control
  • System increases the player's vehicle acceleration.
Extensions and Alternative Flows :
  • None.
Frequency of Occurrence:
  • As desired by the player throughout the simulation.
Open Issues:
  • None at this time.


Identification: UC2.0.2 : Brake

Primary Actor : Player
Stakeholders and Interests :
  • Player:
    • Player wants to reduce speed or completely halt vehicle's movement.
Preconditions :
  • UC 2 has successfully completed.
Postconditions :
  • The player vehicle's speed has been reduced.
Main Success Scenario :
  • The player elects to reduce the vehicle's speed.
  • The player presses the brake control.
  • The system reduces the player vehicle's speed.
Extensions and Alternative Flows :
  • Player is stopped
    • Pressing the brake control has no effect on the vehicle.
Frequency of Occurrence:
  • As desired by the player throughout the simulation.
Open Issues:
  • None at this time.



Identification: UC2.0.3 : Turn vehicle

Primary Actor : Player
Stakeholders and Interests :
  • Player:
    • The player wants to turn the vehicle.
Preconditions :
  • UC 2 has successfully completed.
  • The player is in a state of motion.
Postconditions :
  • The player's vehicle will be turned in the desired direction.
Main Success Scenario :
  • The player elects to turn vehicle
  • The player presses the left or right turn control.
  • The system changes the direction of the player's vehicle in the direction of the desired turn.
Extensions and Alternative Flows :
  • Player is already turning.
    • The player's vehicle turning radius is decreased.
  • Player is stopped
    • The player vehicle's direction remains the same.
Frequency of Occurrence:
  • As desired by the player throughout the simulation.
Open Issues:
  • None at this time.




Identification: UC2.1 : Replay Game

Primary Actor : Player
Stakeholders and Interests :
  • Player:
    • Wants to review events leading up to the end of simulation play.
Preconditions :
  • UC2.0 have completed successfully.
Postconditions :
  • The player reviews the simulation and returns to the main menu.
Main Success Scenario :
  • The player fails driving objectives for a level and the game ends. User actions necessary to fail objectives are in Extensions UC 2. A menu prompts asking the player if they want to review a replay. The player selects the "replay" option. The replay loads and automatically starts when finished loading.
Extensions and Alternative Flows :
  • The player opts not to review replay and returns to the main menu.
Frequency of Occurrence:
  • By default, the replay menu is prompted once per ended game. However, the user may not watch or watch the replay as many times as desired.
Open Issues:
  • None at this time.



Identification: UC2.2 : Pause Game

Primary Actor : Player
Stakeholders and Interests :
  • Player:
    • Player wants to pause the current simulation.
Preconditions :
  • UC 2 has successfully completed.
Postconditions :
  • Game is paused.
  • The game screen is replaced with the pause menu.
Main Success Scenario :
  • The player selects the pause option in the game.
  • The system pauses the simulation.
  • The game screen is replaced with the pause menu.
Extensions and Alternative Flows :
  • None
Frequency of Occurrence:
  • As desired by the player throughout the simulation.
Open Issues:
  • None at this time.





Identification: UC2.3 : Quits Game

Primary Actor : Player
Stakeholders and Interests :
  • Player:
    • Player wants to quit the simulator.
Preconditions :
  • UC 2.1 has successfully completed.
Postconditions :
  • The simulation is ended.
Main Success Scenario :
  • The player selects the quit option from the pause menu.
  • The system ends the current simulation.
  • The system presents the user with the main menu.
Extensions and Alternative Flows :
  • None for top level use case.
Open Issues:
  • None at this time.




Identification: UC 3.1 : Administrator Logs In

Primary Actor : Administrator
Stakeholders and Interests :
  • Administrator:
    • Wants to login to the system
Preconditions :
  • The simulation is loaded.
Postconditions :
  • Access is granted to administration options.
Main Success Scenario :
  • Selects the administrator login option from the main menu.
  • Provide login credentials to the system.
  • The system validates the user's credentials.
  • The system presents the administration options to the user.
Extensions and Alternative Flows :
  • Invalid credentials.
    • The system informs the user that credentials are invalid.
    • The system presents the user with the administrator login option.
Open Issues:
  • None at this time.





Identification: UC 3.2 : Change Administrator Password

Primary Actor : Administrator
Stakeholders and Interests :
  • Administrator:
    • Wants to change the administrator password.
Preconditions :
  • The simulation is loaded.
  • UC 3.1 has successfully completed.
Postconditions :
  • Administrator password has been updated.
Main Success Scenario :
  • UC 3.1 has successfully completed.
  • Change password option is selected.
  • Administrator updates password.
  • System validates the new password.
  • Administrator password is updated in the system.
Extensions and Alternative Flows :
  • Invalid password is entered.
  • System reprompts the user to enter a valid password.
Open Issues:
  • None at this time.





Identification: UC 3.3 : Create Map/Hazard

Primary Actor : Administrator
Stakeholders and Interests :
  • Administrator:
    • Administrator wants to create a new map or hazard for the simulation.
Preconditions :
  • UC 3.1 has successfully completed.
  • User chooses create map or create hazard.
Postconditions :
  • Administrator has successfully created a new map or road hazard.
Main Success Scenario :
  • UC 3.1 has successfully completed.

  • User selects create map option.
  • User creates a new map and registers it with the simulation.
  • The system incorporates the new map into the simulation.

  • User selects create road hazard option.
  • User creates a new road hazard and registers it with the simulation.
  • The system incorporates the new road hazard into the simulation.
Extensions and Alternative Flows :
  • Invalid production of the road hazard.
    • User is notified that the hazard has not been created.
    • User is taken back to the Administrator options screen.
Open Issues:
  • None at this time.





Identification: UC 3.4 : Delete Map/Hazard

Primary Actor : Administrator
Stakeholders and Interests :
  • Administrator:
    • Administrator wants to delete an existing map or road hazard from the simulation.
Preconditions :
  • UC 3.1 has successfully completed.
  • User selects delete map or delete road hazard option.
Postconditions :
  • Administrator has successfully deleted an existing map or road hazard.
Main Success Scenario :
  • UC 3.1 has successfully completed.

  • User selects delete map option.
  • User deletes the selected map.
  • The system removes the map from the simulation.

  • User selects delete road hazard option.
  • User deletes the selected road hazard.
  • The system removes the road hazard from the simulation.
Extensions and Alternative Flows :
  • None at this time.
Open Issues:
  • None at this time.
Web site and all contents Copyright © 2006 CS4911 Team 26, All rights reserved.
Free website templates