Use-case Descriptions
Use case diagram
Use case diagram Tabs CRUD
During the development for the user tabs we got into an argument on how we were going to display the tabs a user can have. We came to the conclusion that it would be easier if we were to store the tabs in the database. This way the crewmembers don't have to recreate the tabs every time they would login. Also, this way every crewmember could design their dashboard the way they find easy to read.
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 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 | |
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 chooses a race to eatch 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 creates a new tab
|
4. System validates if supplied tab name is correct. 5. System adds the new tab. |
Extensions (alternative flow): | |
3a [Crewmember supplies starting round and ending round] | 4. System validates if supplied information is correct. 5. System adds the new tab. |
Update Tab
Primary Actor: Crewmember | |
Stakeholders & Interests: | |
Brief Description: A crewmember wants to update an 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 updates a tab
|
4. System validates if supplied tab name is correct. 5. 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 reads a tab. |
|
Extensions (alternative flow): | |
Delete Tab
Primary Actor: Crewmember | |
Stakeholders & Interests: | |
Brief Description: A crewmember wants to delete an 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 deletes a tab.
|
4. System deletes the 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 newly placed graphs. | |
Main success scenario (basic flow): | |
Actor Action | System Responsibility |
1. The crewmember adds 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 to the web application and selected a tab to remove a graph from. | |
Postconditions: The crewmember removed the 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): | |
System sequence diagram