...
The <<CRUD>> and <<CRD>> would look like the diagram below when expanded. The CRUD acronym stands for Create, Read, Update & Delete. This simple collectivisation shows that an actor can interact with a certain use-case, in this case a tab. They can add new tabs, they can read the data that is present within the tabs, they can update the tab by adding new graphs or removing graphs and they can delete tabs by removing them from the view.
Use Case Descriptions
View Graphs
...
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
| 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 |
- A crewmember wants to watch a race
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): | |
View specific round(s)
...
| 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
...
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): | |
Tab CRUD
Fully dressed description
...