Use-case Descriptions
Use case diagram
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. | |
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, where the crewmember or viewer can see a new, empty tab. |
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 is going to analyse 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 | |
Stakeholders & Interests: | |
Brief Description: A crewmember wants to see a list of old races so he can choose one to watch back. | |
Preconditions: The crewmember has logged in on the website. | |
Postconditions: There is a list of all the races that happened. | |
Main success scenario (basic flow): | |
Actor Action | System Responsibility |
1. A crewmember is going to watch a race back. | 2. The system will get all the races from the database and show them on the page. |
Extensions (alternative flow): | |
Tab CRUD
Fully dressed description
Create Tab
Primary Actor: Crewmember | |
Stakeholders & Interests: | |
Brief Description: A crewmember wants to create a new tab. | |
Preconditions: A crewmember has logged in into the web application. | |
Postconditions: The crewmember can see its new created tab. | |
Main success scenario (basic flow): | |
Actor Action | System Responsibility |
1. The crewmember wants to create a new tab
4. The crewmember confirms the given input. |
6. System adds the new tab. |
Extensions (alternative flow): | |
4a [Crewmember supplies starting round and ending round] | 5. System validates if supplied information is correct. 6. System adds the new tab. |
Update Tab
Primary Actor: Crewmember | |
Stakeholders & Interests: | |
Brief Description: A crewmember wants to update a existing tab. | |
Preconditions: A crewmember has logged in into the web application and the crewmember needs to have a tab | |
Postconditions: The crewmember can see its updated tab | |
Main success scenario (basic flow): | |
Actor Action | System Responsibility |
1. The crewmember wants to update a tab
4. The crewmember confirms the given input. |
6. System updates the tab name. |
Extensions (alternative flow): | |
Read Tab
Primary Actor: Crewmember | |
Stakeholders & Interests: | |
Brief Description: A crewmember wants to read an exisiting tab | |
Preconditions: A crewmember has logged in into 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 wants read its tab |
|
Extensions (alternative flow): | |
Delete Tab
Primary Actor: Crewmember | |
Stakeholders & Interests: | |
Brief Description: A crewmember wants to update a existing tab. | |
Preconditions: A crewmember has logged in into the web application and the crewmember needs to have a tab | |
Postconditions: The crewmember has deleted its tab. | |
Main success scenario (basic flow): | |
Actor Action | System Responsibility |
1. The crewmember wants to delete a tab
|
4. System deletes tab. |
Extensions (alternative flow): | |
Place Graph
Fully dressed description
Primary Actor: Crewmember | |
Stakeholders & Interests: | |
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. | |
Preconditions: A crewmember has logged in into the web application | |
Postconditions: The crewmember can see the chosen graphs. | |
Main success scenario (basic flow): | |
Actor Action | System Responsibility |
1. The crewmember is going to add a new graph to his tab.
|
|
Extensions (alternative flow): | |
2a. There are no sensors available in the database. 4a. There are no graphs available that are linked with the shown sensors. |
System sequence diagram
Remove Graph
Fully dressed description
Primary Actor: Crewmember | |
Stakeholders & Interests: | |
Brief Description: A crewmember wants to delete a graph from a tab. | |
Preconditions: A crewmember has logged in into the web application. | |
Postconditions: The crewmember removed the graph from his tab. | |
Main success scenario (basic flow): | |
Actor Action | System Responsibility |
1. The crewmember selects a tab to remove a graph from.
|
4. System removes the graph from the selected tab. |
Extensions (alternative flow): | |
2a. There are no graphs on the selected tab. |
System sequence diagram