Use-case Descriptions
<In this section, each use-case is described in detail, optionally accompanied by a system sequence diagram (SSD) and operation contracts. Make sure that the use case descriptions are consistent with the domain model and the use case diagram from Section 1.5>
Use case 1
<Don’t really say “Use case 1.” State the use-case name instead.>
Fully-dressed use case description
<Provide a fully-dressed use-case description in the format you know from the OOAD course>
System Sequence Diagram (optional)
<In case the use-case entails complex scenarios, you may decide to create a system sequence diagram showing events generated by external actors, the order of events and inter-system events. All systems are treated as a black box>
Operation Contracts (optional)
<If the use case contains complex manipulations of domain objects, you may decide to specify operation contracts for all system operations included in the use case/ SSD.>
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. They'll press the 'View Race' button to view the race of a specific car. They'll then be redirected to a new web-page, where the crewmember or viewer can interact with the racecar's data. | |
| 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 Action | System Responsibility |
| 2. The system will redirect the viewer or crewmember to a new page. 3. The system will load up the new page, showing a few standard diagrams and graphs. |
| Extensions (alternative flow): | |
