Brief Description: A crewmember wants to look at racedata or wants to view detailed information of a race.

1. A crewmember watches 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.

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.

1. A crewmember analyses the data of a specific round.

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.

Brief Description: An actor wants to see a list of old races so he can choose one to watch back.

1. The crewmember or viewer goes to the race-overview page.

2. The system will get all the races from the database and show them on the page.

Brief Description: A crewmember wants to delete an existing tab.

1. The crewmember deletes a tab.

3. The crewmember confirms deletion.

2. System asks for a confirmation

4. System deletes the tab.

Brief Description: A crewmember wants to view the data from the sensors in a graph, to do this they place their desired graph in their tab.

1. The crewmember adds a new graph to his tab.

3. The crewmember selects the desired sensor to add a graph from.

5. The crewmember selects the desired type of graph to add to the tab

2. System shows all sensors to choose a graph from.

4. System shows all graphs that are included in the current selection.

6. System adds the graph to the tab.

2a. There are no sensors available in the database.
      end of usecase.

4a. There are no graphs available that are linked with the shown sensors.
      end of usecase.