Wiki source code of d. Use Cases
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
2.1 | 1 | Use Cases are a complete description of what a system will do (functionality) |
| 2 | |||
| 3 | (% style="width:761px" %) | ||
| 4 | |(% style="width:159px" %)Objective|(% style="width:598px" %)The “operational demand” that is (partially) met by the achievement of carrying out the use case, e.g., the mental fitness of the elderly. | ||
| 5 | |(% style="width:159px" %)TDP|(% style="width:598px" %)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. | ||
| 6 | |(% style="width:159px" %)Actors|(% style="width:598px" %)Main human and technology actors with their roles (permissions, prohibitions & obligations), e.g., the Robot (quiz master) and the Person with Dementia (bingo player). | ||
| 7 | |(% style="width:159px" %)Pre-Condition|(% style="width:598px" %)The state of the environment, technology or human just before the functions are | ||
| 8 | activated, e.g., a PwD group is waiting for the bingo in the activity room... | ||
| 9 | |(% style="width:159px" %)Post-Condition|(% style="width:598px" %)The state of the environment, technology or human just after the functions were active, | ||
| 10 | e.g. every PwD that joined the bingo has a price... | ||
| 11 | |(% style="width:159px" %)Action Sequence|(% style="width:598px" %)A top-to-bottom description of an easy-to-understand and fairly typical action sequence | ||
| 12 | 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. | ||
| 13 | ~1. <actions, incl. human-technology interactions> | ||
| 14 | 2. <actions, incl. human-technology interactions> | ||
| 15 | 3. ... | ||
| 16 | |(% style="width:159px" %)Interaction Flow|(% style="width:598px" %)Where applicable, a diagram that specifies the interaction flow. | ||
| 17 | |||
| 18 |