d. Use Cases
Last modified by Dongxu Lu on 2022/12/22 11:53
Use Cases are a complete description of what a system will do (functionality)
The use cases are often formatted as the table below.
| Objective | The “operational demand” that is (partially) met by the achievement of carrying out the use case, e.g., the mental fitness of the elderly. |
| TDP | Where applicable, a reference to a Team Design Pattern (i.e., when the UC has a generic design problem for which an appropriate solution is available. |
| Actors | Main human and technology actors with their roles (permissions, prohibitions & obligations), e.g., the Robot (quiz master) and the Person with Dementia (bingo player). |
| Pre-Condition | The state of the environment, technology or human just before the functions are activated, e.g., a PwD group is waiting for the bingo in the activity room... |
| Post-Condition | The state of the environment, technology or human just after the functions were active, e.g. every PwD that joined the bingo has a price... |
| Action Sequence | A top-to-bottom description of an easy-to-understand and fairly typical action sequence in which the actor’s goal is accomplished, and related to the function and claim. Several alternative(sub) action sequences can be included in the list. 1. <actions, incl. human-technology interactions> 2. <actions, incl. human-technology interactions> 3. ... |
| Interaction Flow | Where applicable, a diagram that specifies the interaction flow. |