Page History

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 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: A crewmember wants to look at racedata or wants to view detailed information of a race.

1. A crewmember wants to watch a race.

  3. Crewmember specifies race.

2. The system will ask crewmember what race it wants to watch.

3. The system gets the Graphs and data from specified race.

Brief Description: A crewmember wants to create a new tab.

Preconditions: A crewmember has logged in to the web application and is on the dashboard page of a race

1. The crewmember creates a new tab.

3. The crewmember supplies the system with a tab name.

2. System asks for a tab name.

4. System validates if supplied tab name is correct.

5. System adds the new tab.

3a [Crewmember supplies a starting round and ending round]

4. System validates if supplied information is correct.

5. System adds the new tab which starts and ends with the supplied rounds.

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

1. The crewmember updates a tab.

3. The crewmember supplies the system with a tab name.

2. System asks for a new tab name.

4. System validates if the supplied tab name is correct.

5. System updates the tab name.

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

1. The crewmember reads a tab.

2. System shows details of given tab.

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.

Brief Description: A crewmember wants to delete a graph from a tab because he doesn't need it anymore. 

1. The crewmember removes a graph.

2. System removes the graph from the selected tab.