...
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 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): | |
...
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 creates a new tab
4. The crewmember confirms the given input. |
54. System validates if supplied tab name is correct. 65. System adds the new tab. |
Extensions (alternative flow): | |
4a 3a [Crewmember supplies starting round and ending round] | 54. System validates if supplied information is correct. 65. System adds the new 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 wants to update updates a tab
4. The crewmember confirms the given input. |
54. System validates if supplied tab name is correct. 65. System updates the tab name. |
Extensions (alternative flow): | |
...
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 reads a tab. |
|
Extensions (alternative flow): | |
...
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 wants to delete deletes a tab.
|
4. System deletes the tab. |
Extensions (alternative flow): | |
...
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 is going to add 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. |
...
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 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 the a graph he doesn't want. | 2. System removes the graph from the selected tab. |
Extensions (alternative flow): | |
...