Wiki source code of Planning
Version 8.1 by Veikko Saikkonen on 2022/02/12 15:38
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | |||
2 | = Concept [DRAFT] = | ||
3 | |||
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 | |||
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 | |||
8 | //(The wellbeing discourse draft avoids the issue with original concept of meal reminders being a fancy alarm clock.) - Veikko// | ||
9 | |||
10 | = Glossary: Use case, objective, function etc. = | ||
11 | |||
12 | Objective is the main purpose of the application, it fulfills the value proposition. | ||
13 | |||
14 | Use cases are more specific requirements that partially accomplish the objective. | ||
15 | |||
16 | Functions are technical features that enable the use cases. | ||
17 | |||
18 | Claims are "how" the function fulfills the specific use case. | ||
19 | |||
20 | E.g. | ||
21 | Objective: The PwD stays healthy. | ||
22 | Use case: As a HCP I want the robot to remind the PwD about eating so that they stay healthy. | ||
23 | Function: The robot reminds the PwD about eating every 4h or on a set timetable. | ||
24 | Claim: Reminding the PwD about eating causes them to eat and to stay healthy. | ||
25 | |||
26 | |||
27 | |||
28 | |||
29 | |||
30 | |||
31 | |||
32 |