Page History

...

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 3. The crewmember supplies system with a tab name. 4. The crewmember confirms the given input.	2.System asks for a tab name. 5. System validates if supplied tab name is correct. 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 3. The crewmember supplies system with a tab name. 4. The crewmember confirms the given input.	2. System asks for a new tab name 5. System validates if supplied tab name is correct. 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	2. System shows details of given 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 3. The crewmember confirms deletion	2. System asks for a confirmation 4. System deletes tab.
Extensions (alternative flow):

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. 3. The crewmember selects the desired sensor to add a graph from. 5. The crewmember selects the desired type of graph to add to the tab	2. System shows all sensors to choose a graph from. 4. System shows all graph that are included in the current selection. 6. System adds the graph to the tab.
Extensions (alternative flow):
	2a. There are no sensors available in the database. end of usecase. 4a. There are no graphs available that are linked with the shown sensors. end of usecase.

System sequence diagram