...
In this chapter, all of the use-cases in the use-case diagram will be expanded and explained, adding a primary actor, potential stakeholders, a brief description, pre- and postconditions as well as a main success path and any potential alternative paths to successfully complete the use-case. Next to this overview of the use-case, an SSD or System Sequence Diagram has been added, which shows the user actions as well as the system's responses to these user actions.
View race
Fully dressed description
| 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 crewmember or viewer 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): | |
System sequence diagram
View specific round(s)
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 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): | |
System sequence diagram
View Graphs
Fully dressed description
| Primary Actor: Crewmember | |
| Stakeholders & Interests | |
Brief Description: A crewmember wants to look at racedata or wants to view detailed information of a race. | |
| Preconditions: A crewmember has logged in to the web application | |
| Postconditions: A crewmember can now view and interact with the race and/or the racecar's data. | |
| Main success scenario (basic flow): | |
| Actor Action | System Responsibility |
3. Crewmember specifies race. | 2. The system will ask crewmember what race it wants to watch. 3. The system gets the Graphs and data from specified race. |
| Extensions (alternative flow): | |
System sequence diagram
Tab CRUD
Create Tab
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 to the web application and is on the dashboard page of a race | |
| Postconditions: The crewmember can see their 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 a starting round and ending round] | 4. System validates if supplied information is correct. 5. System adds the new tab which starts and ends with the supplied rounds |
Update Tab
Fully dressed description
| Primary Actor: Crewmember | |
| Stakeholders & Interests: | |
Brief Description: A crewmember wants to update an existing tab. | |
| Preconditions: A crewmember has logged in to the web application and the crewmember needs to have a tab | |
| Postconditions: The crewmember can see their updated tab | |
| Main success scenario (basic flow): | |
| Actor Action | System Responsibility |
1. The crewmember updates a tab
|
4. System validates if the supplied tab name is correct. 5. System updates the tab name. |
| Extensions (alternative flow): | |
Read Tab
Fully dressed description
| Primary Actor: Crewmember | |
| Stakeholders & Interests: | |
Brief Description: A crewmember wants to read an existing tab | |
| Preconditions: A crewmember has logged in to the web application and the crewmember needs to have a tab | |
| Postconditions: The crewmember can see their tab | |
| Main success scenario (basic flow): | |
| Actor Action | System Responsibility |
1. The crewmember reads a tab. |
|
| Extensions (alternative flow): | |
Delete Tab
Fully dressed description
| Primary Actor: Crewmember | |
| Stakeholders & Interests: | |
Brief Description: A crewmember wants to delete an existing tab. | |
| Preconditions: A crewmember has logged in to the web application and the crewmember needs to have a tab | |
| Postconditions: The crewmember has deleted their tab. | |
| Main success scenario (basic flow): | |
| Actor Action | System Responsibility |
1. The crewmember deletes a tab.
|
4. System deletes the tab. |
| Extensions (alternative flow): | |
...