...
| 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 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): | |
View race
| Primary Actor: Crewmember, viewer | |
| Stakeholders & Interests: | |
Brief Description: An actor wants to see a list of old races so he can choose one to watch back. | |
| Preconditions: The actor has logged in to the website. | |
| Postconditions: There is a list of all the races that happened. | |
| Main success scenario (basic flow): | |
| Actor Action | System Responsibility |
1. The primary actor goes to the race-overview page. | 2. The system will get all the races from the database and show them on the page. |
| Extensions (alternative flow): | |
...