...
| 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 crewmember can now view the data of one or more specific rounds. | |
| Main success scenario (basic flow): | |
| Actor Action | System Responsibility |
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. |
| Extensions (alternative flow): | |
...
| Primary Actor: Crewmember | |
| Stakeholders & Interests: | |
Brief Description: A crewmember wants to read an exisiting existing tab | |
| Preconditions: A crewmember has logged in into to the web application and the crewmember needs to have a tab | |
| Postconditions: The crewmember can see its tab | |
| Main success scenario (basic flow): | |
| Actor Action | System Responsibility |
1. The crewmember reads a tab. |
|
| Extensions (alternative flow): | |
...
| Primary Actor: Crewmember | |
| Stakeholders & Interests: | |
Brief Description: A crewmember wants to delete a graph from a tab. | |
| Preconditions: A crewmember has logged in to the web application and selected a tab to remove a graph from. | |
| Postconditions: The crewmember has succesfully successfully removed a graph from his tab. | |
| Main success scenario (basic flow): | |
| Actor Action | System Responsibility |
1. The crewmember removes a graph. | 2. System removes the graph from the selected tab. |
| Extensions (alternative flow): | |
...