Use-case Descriptions

Use case diagram

Fully dressed description

Primary Actor: Crewmember
Stakeholders & Interests: Viewers
Brief Description: A crewmember or a viewer wants to look at racedata or wants to view detailed information of a race.
Preconditions: A crewmember or viewer has logged in into the web application
Postconditions: A crewmember or viewer can now view and interact with the race and/or the racecar's data.
Main success scenario (basic flow):
Actor Action	System Responsibility
A crewmember or viewer wants the watch the race.	2. The system will redirect the viewer or crewmember to a new page. 3. The system will load up the new page, where the crewmember or viewer can see a new, empty tab.
Extensions (alternative flow):

Fully dressed description

Primary Actor: Crewmember
Stakeholders & Interests:
Brief Description: A crewmember wants to view the data of a specific round during the current race, to analyse that specific round and see if there's anything wrong with the car or the driver.
Preconditions: The crewmember has logged in on the website and is watching a race.
Postconditions: The crewemember can now view the data of one or more specific rounds.
Main success scenario (basic flow):
Actor Action	System Responsibility
1. A crewmember wants to view one or more specific rounds in a race. 3. The crewmember inserts the desired rounds to view.	2. The system will ask the crewmember to insert which range of rounds the user wants to view. 4. The system creates a new tab with only the desired rounds as data that can be viewed.
Extensions (alternative flow):

Primary Actor: Crewmember
Stakeholders & Interests:
Brief Description: A crewmember wants to view the data of a specific round during the current race, to analyse that specific round and see if there's anything wrong with the car or the driver.
Preconditions: The crewmember has logged in on the website and is watching a race.
Postconditions: The crewmember can now view the data of one or more specific rounds.
Main success scenario (basic flow):
Actor Action	System Responsibility
1. A crewmember wants to view one or more specific rounds in a race. 3. The crewmember inserts the desired rounds to view.	2. The system will ask the crewmember to insert which range of rounds the user wants to view. 4. The system creates a new tab with only the desired rounds as data that can be viewed.
Extensions (alternative flow):

Primary Actor: Crewmember
Stakeholders & Interests:
Brief Description: A crewmember wants to see a list of old races so he can choose one to watch back
Preconditions: The crewmember has logged in on the website and there should be more then one race
Postconditions: There is a list of all the races that happend
Main success scenario (basic flow):
Actor Action	System Responsibility
1. A crewmember is going to watch a raceback	2. The system will get all the races from the database and show them on the page
Extensions (alternative flow):