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: Declareren reiskosten
<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>
Brief description
Werknemer vult in het formulier in welke ritten zijn gemaakt de betreffende dag of week. Na het invullen bevestigd de werknemer de ritten en het systeem slaat de gegevens op.
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.>
Use case 2: Berekenen reisafstand
Fully-dressed use case description
Brief description
System Sequence Diagram (optional)
Operation Contracts (optional)
Use case 3: Invullen flexwerkplek schema
Fully-dressed use case description
Brief description
System Sequence Diagram (optional)
Operation Contracts (optional)
Use case 4: Aanvragen verlof
Fully-dressed use case description
Brief description
System Sequence Diagram (optional)
Operation Contracts (optional)
Use case 5: Beoordelen verlof
Fully-dressed use case description
Brief description
System Sequence Diagram (optional)
Operation Contracts (optional)
Use case 6: Genereren werkplekoverzicht
Fully-dressed use case description
Brief description
System Sequence Diagram (optional)
Operation Contracts (optional)
Use case 7: Beheren werknemers
Fully-dressed use case description
Brief description