Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Primary Actor: Crewmember
Stakeholders & Interests: 

Brief Description: A crewmember wants to create a new tab.

Preconditions: A crewmember has logged in into to the web application.
Postconditions: The crewmember can see its new created tab.
Main success scenario (basic flow): 
Actor ActionSystem Responsibility

1. The crewmember creates a new tab


3. The crewmember supplies the system with a tab name.



2. System asks for a tab name.


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.

...

Primary Actor: Crewmember
Stakeholders & Interests: 

Brief Description: A crewmember wants to update an existing tab.

Preconditions: A crewmember has logged in into to 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 ActionSystem Responsibility

1. The crewmember updates a tab


3. The crewmember supplies system with a tab name.



2. System asks for a new tab name


4. System validates if supplied tab name is correct.

5. System updates the tab name.

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 to the web application and the crewmember needs to have a tab
Postconditions: The crewmember has deleted its tab.
Main success scenario (basic flow): 
Actor ActionSystem Responsibility

1. The crewmember deletes a tab.


3. The crewmember confirms deletion.



2. System asks for a confirmation

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 to the web application
Postconditions: The crewmember can see the newly placed graphs.
Main success scenario (basic flow): 
Actor ActionSystem Responsibility

1. The crewmember adds 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 graphs 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.

...