Use-case Descriptions
<In this section, each use-case is described in detail, optionally accompanied by a system sequence diagram (SSD) and operation contracts. Make sure that the use case descriptions are consistent with the domain model and the use case diagram from Section 1.5>
View Graphs
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. They'll press the 'View Race' button to view the race of a specific car. They'll then be redirected to a new web-page, where the crewmember or viewer can interact with the racecar's data. | |
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 |
| 2. The system will redirect the viewer or crewmember to a new page. 3. The system will load up the new page, showing a few standard diagrams and graphs. |
Extensions (alternative flow): | |
View data per round
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): | |