Wiki source code of Planning
Version 10.1 by Veikko Saikkonen on 2022/02/12 15:38
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
5.1 | 1 | |
| 2 | = Concept [DRAFT] = | ||
| 3 | |||
| |
7.1 | 4 | The main objective of the application is to help the PwD to retain their wellbeing and autonomy. This is done through engaging in a wellbeing discourse and reminding them about mealtimes and drinking. |
| 5 | |||
| |
5.1 | 6 | The discourse is initiated by the robot and is aimed to help the PwD in connecting with themselves and self-reflecting their wellbeing, with special attention on eating and drinking. |
| 7 | |||
| |
6.1 | 8 | //(The wellbeing discourse draft avoids the issue with original concept of meal reminders being a fancy alarm clock.) - Veikko// |
| |
5.1 | 9 | |
| |
7.1 | 10 | = Glossary: Use case, objective, function etc. = |
| |
5.1 | 11 | |
| |
8.1 | 12 | Objective is the main purpose of the application, it fulfills the value proposition. |
| |
5.1 | 13 | |
| |
8.1 | 14 | Use cases are more specific requirements that partially accomplish the objective. |
| |
5.1 | 15 | |
| |
8.1 | 16 | Functions are technical features that enable the use cases. |
| |
5.1 | 17 | |
| |
8.1 | 18 | Claims are "how" the function fulfills the specific use case. |
| |
5.1 | 19 | |
| |
9.1 | 20 | == Example == |
| |
8.1 | 21 | Objective: The PwD stays healthy. |
| |
10.1 | 22 | Use case #1: As a HCP I want the robot to remind the PwD about eating so that they stay healthy. |
| 23 | Function #1: The robot reminds the PwD about eating every 4h or on a set timetable. | ||
| 24 | Claim #1: Reminding the PwD about eating causes them to eat and to stay healthy. | ||
| |
7.1 | 25 | |
| 26 | |||
| |
8.1 | 27 | |
| 28 | |||
| 29 | |||
| 30 | |||
| 31 | |||
| 32 | |||
| 33 |