You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 29 Next »

Use-case Descriptions 

Use case diagram

Use case diagram Tabs CRUD

During the development for the user tabs we got into an argument on how we were going to display the tabs a user can have. We came to the conclusion that it would be easier if we were to store the tabs in the database. This way the crewmembers don't have to recreate the tabs every time they would login. Also, this way every crewmember could design their dashboard the way they find easy to read.

View Graphs

Fully dressed description

Primary Actor: Crewmember
Stakeholders & Interests: Viewers

Brief Description: A crewmember or a viewer wants to look at racedata or wants to view detailed information of a race.

Preconditions: A crewmember or viewer has logged in into the web application
Postconditions: A crewmember or viewer can now view and interact with the race and/or the racecar's data.
Main success scenario (basic flow):
Actor ActionSystem Responsibility
  1. A crewmember or viewer wants the watch the race.

2. The system will redirect the viewer or crewmember to a new page.

3. The system will load up the new page, where the crewmember or viewer can see a new, empty tab.

Extensions (alternative flow):




 View data per round

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 crewemember can now view the data of one or more specific rounds.
Main success scenario (basic flow):
Actor ActionSystem Responsibility

1. A crewmember is going to analyse 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 race

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 ActionSystem 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 ActionSystem 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 ActionSystem 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 ActionSystem 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 ActionSystem 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):




Place Graph

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 ActionSystem 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



Remove Graph

Fully dressed description

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.
Postconditions: The crewmember removed the graph from his tab.
Main success scenario (basic flow): 
Actor ActionSystem Responsibility

1. The crewmember selects a tab to remove a graph from.


3. The crewmember removes the graph he doesn't want.


2. System shows graphs on selected tab.


4. System removes the graph from the selected tab.

Extensions (alternative flow):

2a. There are no graphs on the selected tab.
      end of usecase.


System sequence diagram

  • No labels