Skip to Content

Changes for page Planning

Last modified by Sofia Kostakonti on 2022/03/01 11:07
From version Icon 11.1 Icon
edited by Veikko Saikkonen
on 2022/02/12 15:39
Change comment: There is no comment for this version
To version Icon 7.1 Icon
edited by Veikko Saikkonen
on 2022/02/12 15:34
Change comment: There is no comment for this version

Summary

Details

Icon Page properties
Content
... ... @@ -5,29 +5,13 @@
5 5  
6 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 7  
8 -//(The wellbeing discourse is suggested to avoid the issue with original concept of meal reminders being a fancy alarm clock.) - Veikko//
8 +//(The wellbeing discourse draft avoids the issue with original concept of meal reminders being a fancy alarm clock.) - Veikko//
9 9  
10 10  = Glossary: Use case, objective, function etc. =
11 11  
12 -Objective is the main purpose of the application, it fulfills the value proposition.
13 13  
14 -Use cases are more specific requirements that partially accomplish the objective.
15 15  
16 -Functions are technical features that enable the use cases.
17 17  
18 -Claims are "how" the function fulfills the specific use case.
19 19  
20 -== Example ==
21 -Objective: The PwD stays healthy.
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.
25 25  
26 26  
27 -
28 -
29 -
30 -
31 -
32 -
33 -