Skip to Content
Last modified by Mathieu Jung-Muller on 2022/04/04 13:55
From version Icon 35.1 Icon
edited by Sneha Lodha
on 2022/04/02 15:43
Change comment: There is no comment for this version
To version Icon 13.1 Icon
edited by Mathieu Jung-Muller
on 2022/03/30 00:43
Change comment: There is no comment for this version

Summary

Details

Icon Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.snehalodha
1 +XWiki.Mathieu
Content
... ... @@ -1,24 +1,33 @@
1 1  (% style="background-color:#ffffff; font-size:14px" %)
2 2  
3 -(% style="text-align:center" %)
4 4  == IDP01==
4 +{{html}}
5 +<img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp1.jpg?rev=1.1" alt="IDP01" width="350"/>
6 +{{/html}}
5 5  
6 -(% style="text-align:center" %)
7 -[[image:idp1.jpg||width="400" height="350"]]
8 -
9 9  |(((
10 -**RANKING/ validation**
9 +**RANKING/ validation**
10 +
11 11  )))|(((
12 +//Notion of the validity (e.g., empirically tested)//
12 12  When Pepper is playing music this can clearly be heard by the PwD, and other evaluators around, so this IDP is empirically testable.
14 +
13 13  )))
14 14  |(((
15 -**DESIGN PROBLEM (what)**
17 +**DESIGN PROBLEM (what)**
18 +
19 +
16 16  )))|(((
21 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
22 +
17 17  Here the interaction intention of the IDP is to gently remind/alert the PwD about the presence of Pepper around the room. This is in order not to startle the PwD by directly talking to them, but rather providing a gentle musical reminder of interaction about to take place. Sometimes the PwD might want to listen to some music for entertainment purposes and this IDP can also be applied in that scenario.
18 18  )))
19 19  |(((
20 20  **CONTEXT (use when…)**
27 +
28 +
21 21  )))|(((
30 +//Contextual characteristics that are significant for the applicability of the pattern.//
22 22  This IDP can be used in the following contexts:
23 23  * Alert the PwD before an interaction takes place
24 24  * Wake up reminder for PwD
... ... @@ -27,17 +27,34 @@
27 27  )))
28 28  |(((
29 29  **DESIGN SOLUTION (how)**
39 +
40 +
30 30  )))|(((
42 +//Essential characteristics of the design solution that express the interaction intention.//
43 +
31 31  This IDP contains minimal interaction, and only consists of Pepper playing music. The musical tone that will play in a specific scenario is pre-programmed for each activity. Hence the solution for gentle reminders for interaction about to happen for PwD, is to simply play some gentle reminder music.
32 32  In the case where this IDP is used for the entertainment of the PwD (external usecase), a list of songs that the PwD enjoys can be programmed into Pepper and played when the usecase is activated.
33 33  )))
34 34  |(((
35 35  **DESIGN RATIONALE (why)**
49 +
50 +
36 36  )))|(((
37 -According to many studies music has shown to have a dramatic effect on people with dementia in terms of improving recollection and making them feel more calm overall [1][2]. Due to these researches we decided to incorporate it not only for entertainment purposes, but also for some gentle reminder purposes.
52 +//Argumentation that resulted in the chosen design solution.//
53 +
54 +According to many studies music has shown to have a dramatic effect on people with dementia in terms of improving recollection and making them feel more calm overall. (Citations needed) Due to these researches we decided to incorporate it not only for entertainment purposes, but also for some gentle reminder purposes.
38 38  )))
56 +|(((
57 +**EXAMPLES (as seen on…)**
39 39  
59 +
60 +)))|(((
61 +//Illustration (eg. picture, screenshot, animated graphic, video etc.) of an implementation of the design solution in a ‘real-life’ application, and include a short explanation describing the context of use.//
40 40  
63 +TBD (should we include or not?)
64 +)))
65 +
66 +
41 41  == IDP02==
42 42  {{html}}
43 43  <img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp2.jpg?rev=1.1" alt="IDP02" width="350"/>
... ... @@ -45,17 +45,29 @@
45 45  
46 46  |(((
47 47  **RANKING/ validation**
74 +
75 +
48 48  )))|(((
77 +//Notion of the validity (e.g., empirically tested)//
49 49  This can be empirically tested as the PwD, and other evaluators around, can hear Pepper asking this question.
79 +
50 50  )))
51 51  |(((
52 52  **DESIGN PROBLEM (what)**
83 +
84 +
53 53  )))|(((
86 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
87 +
54 54  It is important to understand whether the PwD did a particular task or not. Tasks such as taking medicine or eating a meal are crucial, and understanding whether the PwD has successfully done this is an important first step to many reminder tasks.
55 55  )))
56 56  |(((
57 -**CONTEXT (use when…)**
91 +**CONTEXT (use when…)**
92 +
93 +
58 58  )))|(((
95 +//Contextual characteristics that are significant for the applicability of the pattern.//
96 +
59 59  This IDP can be used in the following contexts:
60 60  * Understanding whether the PwD has taken medication before reminding them
61 61  * Understanding whether the PwD has eaten a meal before reminding them
... ... @@ -62,17 +62,36 @@
62 62  The list can be further expanded as more crucial task usecases are added.
63 63  )))
64 64  |(((
65 -**DESIGN SOLUTION (how)**
103 +**DESIGN SOLUTION (how)**
104 +
105 +
66 66  )))|(((
67 -The solution consists of explicitly asking the PwD whether they have already performed a particular task. The response from PwD can either be yes or no, and depending on that Pepper proceeds with the next step. Simply asking the PwD whether they have performed a task is the best way to ensure a clear and concise reply which is understandable.
107 +//Essential characteristics of the design solution that express the interaction intention.//
108 +
109 +The solution consists of explicitly asking the PwD whether they have already performed a particular task. The response from PwD can either be yes or no, and depending on that Pepper proceeds with the next step. Simply asking the PwD whether they have performed a task is the best way to ensure a clear and concise reply which is understandable.
110 +
68 68  )))
69 69  |(((
70 70  **DESIGN RATIONALE (why)**
114 +
115 +
71 71  )))|(((
117 +//Argumentation that resulted in the chosen design solution.//
118 +
72 72  Here instead of assessing from visual cues whether the PwD has conducted a particular task, a verbal approach is taken. This is due to Pepper's limitations in constantly being around the PwD. Although simply verbally asking whether the PwD performed a certain task might seem too straightforward, it ensures that important information is conveyed in the most explicit manner.
120 +
73 73  )))
122 +|(((
123 +**EXAMPLES (as seen on…)**
74 74  
125 +
126 +)))|(((
127 +//Illustration (eg. picture, screenshot, animated graphic, video etc.) of an implementation of the design solution in a ‘real-life’ application, and include a short explanation describing the context of use.//
75 75  
129 +TBD (should we include or not?)
130 +)))
131 +
132 +
76 76  == IDP03==
77 77  {{html}}
78 78  <img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp3.jpg?rev=1.1" alt="IDP03" width="350"/>
... ... @@ -80,17 +80,29 @@
80 80  
81 81  |(((
82 82  **RANKING/ validation**
140 +
141 +
83 83  )))|(((
143 +//Notion of the validity (e.g., empirically tested)//
84 84  This can be empirically tested as the PwD, and other evaluators around, can hear Pepper reminding the PwD to do the task.
145 +
85 85  )))
86 86  |(((
87 -**DESIGN PROBLEM (what)**
148 +**DESIGN PROBLEM (what)**
149 +
150 +
88 88  )))|(((
152 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
153 +
89 89  The idea of this design pattern is to verbally remind the PwD of an upcoming task. Such tasks can include medicine reminders, meal reminders etc. The intended effect on the user would be that they are reminded to do this particular task if they have not done it already. It also takes some of the burden away from primary caregivers and partners to do such a reminding job constantly.
90 90  )))
91 91  |(((
92 92  **CONTEXT (use when…)**
158 +
159 +
93 93  )))|(((
161 +//Contextual characteristics that are significant for the applicability of the pattern.//
162 +
94 94  This IDP can be used in the following contexts:
95 95  * Reminding the PwD to take medication if they have not done so already
96 96  * Reminding the PwD to eat food if they have not done so already
... ... @@ -98,16 +98,32 @@
98 98  )))
99 99  |(((
100 100  **DESIGN SOLUTION (how)**
170 +
171 +
101 101  )))|(((
173 +//Essential characteristics of the design solution that express the interaction intention.//
174 +
102 102  The design solution consists of Pepper reminding the PwD to do a particular task if they have not done it already. We ensure this reminder is only activated when the PwD has not performed the task in order not to overwhelm them with something they have already done. The goal of the pattern is to successfully remind and encourage the PwD to perform an essential task they should do.
103 103  )))
104 104  |(((
105 105  **DESIGN RATIONALE (why)**
179 +
180 +
106 106  )))|(((
182 +//Argumentation that resulted in the chosen design solution.//
107 107  A verbal reminder here works better than a simple reminder on the phone, as would happen commonly these days. Also we believe that having Pepper as a physical being there might encourage the PwD to take such reminders with higher importance than a simple notification. On top of that, phone reminders would mean that the PwD is familiar with this kind of technology, which is not necessarily the case.
184 +
108 108  )))
186 +|(((
187 +**EXAMPLES (as seen on…)**
109 109  
189 +)))|(((
190 +//Illustration (eg. picture, screenshot, animated graphic, video etc.) of an implementation of the design solution in a ‘real-life’ application, and include a short explanation describing the context of use.//
110 110  
192 +TBD (should we include or not?)
193 +)))
194 +
195 +
111 111  == IDP04==
112 112  {{html}}
113 113  <img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp4.jpg?rev=1.1" alt="IDP04" width="350"/>
... ... @@ -115,17 +115,29 @@
115 115  
116 116  |(((
117 117  **RANKING/ validation**
203 +
204 +
118 118  )))|(((
206 +//Notion of the validity (e.g., empirically tested)//
119 119  This can be empirically tested as the PwD, and other evaluators around, can hear Pepper asking the PwD for confirmation.
208 +
120 120  )))
121 121  |(((
122 122  **DESIGN PROBLEM (what)**
212 +
213 +
123 123  )))|(((
215 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
216 +
124 124  This design pattern occurs hand in hand with Pepper just having told the PwD to do a certain task or activity step. The intention is to understand whether this task was successfully done by the PwD. This ensures the PwD had indeed successfully completed a certain task, which in some case may be crucial.
125 125  )))
126 126  |(((
220 +
127 127  **CONTEXT (use when…)**
222 +
128 128  )))|(((
224 +//Contextual characteristics that are significant for the applicability of the pattern.//
225 +
129 129  This IDP can be used in the following contexts:
130 130  * Asking for confirmation of having taken medication
131 131  * Asking for confirmation of having eaten a meal
... ... @@ -134,16 +134,33 @@
134 134  )))
135 135  |(((
136 136  **DESIGN SOLUTION (how)**
234 +
235 +
137 137  )))|(((
237 +//Essential characteristics of the design solution that express the interaction intention.//
238 +
138 138  The design solution consists of Pepper asking for a verbal confirmation of having done a task. The user is prompted with a closed question such as "have you done it?," and is expected to reply in a truthful manner. Pepper will not move on unless a positive confirmation is given, in order to ensure successful completion of crucial tasks.
139 139  )))
140 140  |(((
141 141  **DESIGN RATIONALE (why)**
243 +
244 +
142 142  )))|(((
246 +//Argumentation that resulted in the chosen design solution.//
247 +
143 143  The solution consists of explicitly asking the PwD whether they have already performed a particular task. The response from PwD can either be positive or negative, and depending on that Pepper proceeds with the next step. Simply asking the PwD whether they have performed a task is the best way to ensure a clear and concise reply which is understandable.
249 +
144 144  )))
251 +|(((
252 +**EXAMPLES (as seen on…)**
145 145  
254 +)))|(((
255 +//Illustration (eg. picture, screenshot, animated graphic, video etc.) of an implementation of the design solution in a ‘real-life’ application, and include a short explanation describing the context of use.//
146 146  
257 +TBD (should we include or not?)
258 +)))
259 +
260 +
147 147  == IDP05==
148 148  {{html}}
149 149  <img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp5.jpg?rev=1.1" alt="IDP05" width="350"/>
... ... @@ -150,18 +150,29 @@
150 150  {{/html}}
151 151  
152 152  |(((
153 -**RANKING/ validation**
267 +**RANKING/ validation**
268 +
269 +
154 154  )))|(((
271 +//Notion of the validity (e.g., empirically tested)//
155 155  This can be empirically tested as the PwD, and other evaluators around, can hear Pepper congratulating the PwD.
156 156  )))
157 157  |(((
158 158  **DESIGN PROBLEM (what)**
276 +
277 +
159 159  )))|(((
279 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
280 +
160 160  This design pattern is used to verbally congratulate the PwD, and make them feel about about a task that they just accomplished. This is to lift the spirits of the PwD and make them enjoy and want to do certain tasks.
161 161  )))
162 162  |(((
284 +
163 163  **CONTEXT (use when…)**
286 +
164 164  )))|(((
288 +//Contextual characteristics that are significant for the applicability of the pattern.//
289 +
165 165  This IDP can be used in the following contexts:
166 166  * Congratulate the PwD for having taken medication
167 167  * Congratulate the PwD for having eaten medication
... ... @@ -170,17 +170,32 @@
170 170  )))
171 171  |(((
172 172  **DESIGN SOLUTION (how)**
298 +
299 +
173 173  )))|(((
301 +//Essential characteristics of the design solution that express the interaction intention.//
302 +
174 174  This IDP is quite basic and simply pre-programmed into Pepper. Simply congratulating the PwD for finishing a certain task or activity is sufficient.
175 175  )))
176 176  |(((
177 177  **DESIGN RATIONALE (why)**
307 +
308 +
178 178  )))|(((
179 179  //Argumentation that resulted in the chosen design solution.//
180 180  This IDP was added in order to give the PwD a feeling of accomplishment after doing a task that might have been challenging for them. Giving some encouragement can aid in finding enjoyment in and remembering such tasks.
312 +
181 181  )))
314 +|(((
315 +**EXAMPLES (as seen on…)**
182 182  
317 +)))|(((
318 +//Illustration (eg. picture, screenshot, animated graphic, video, etc.) of an implementation of the design solution in a ‘real-life’ application, and include a short explanation describing the context of use.//
183 183  
320 +TBD (should we include or not?)
321 +)))
322 +
323 +
184 184  == IDP06==
185 185  {{html}}
186 186  <img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp6.jpg?rev=1.1" alt="IDP06s" width="350"/>
... ... @@ -188,17 +188,28 @@
188 188  
189 189  |(((
190 190  **RANKING/ validation**
331 +
332 +
191 191  )))|(((
334 +//Notion of the validity (e.g., empirically tested)//
192 192  This can be tested by performing some other IDPs, which refer to utilizing the breakdown of a particular activity. Since this is for now hard-coded into Pepper, it is not empirically testable.
193 193  )))
194 194  |(((
195 195  **DESIGN PROBLEM (what)**
339 +
340 +
196 196  )))|(((
342 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
343 +
197 197  This design pattern is used by the HCP (or a relative) to enter some activities into Pepper, that the PwD might personally enjoy. This is so that Pepper's system contains the breakdown to certain desired activities.
198 198  )))
199 199  |(((
347 +
200 200  **CONTEXT (use when…)**
349 +
201 201  )))|(((
351 +//Contextual characteristics that are significant for the applicability of the pattern.//
352 +
202 202  This IDP can be used in the following contexts:
203 203  * PwD wants to perform a new activity
204 204  * Pepper is not yet personalized to the particular PwD
... ... @@ -205,16 +205,32 @@
205 205  )))
206 206  |(((
207 207  **DESIGN SOLUTION (how)**
359 +
360 +
208 208  )))|(((
362 +//Essential characteristics of the design solution that express the interaction intention.//
363 +
209 209  The interface has not been implemented. Ideally, the interface designed is easy to use, HCP and relatives are not required to have very high technical knowledge.
210 210  )))
211 211  |(((
212 212  **DESIGN RATIONALE (why)**
368 +
369 +
213 213  )))|(((
371 +//Argumentation that resulted in the chosen design solution.//
214 214  We allow the HCP to provide steps as they are the ones that have spent a significant amount of time with the PwD and know about their likes and dislikes. In this case, they can also provide the steps in the complexity they think the PwD will understand, rather than simply having some arbitrary steps from the internet.
373 +
215 215  )))
375 +|(((
376 +**EXAMPLES (as seen on…)**
216 216  
378 +)))|(((
379 +//Illustration (eg. picture, screenshot, animated graphic, video etc.) of an implementation of the design solution in a ‘real-life’ application, and include a short explanation describing the context of use.//
217 217  
381 +TBD (should we include or not?)
382 +)))
383 +
384 +
218 218  == IDP07==
219 219  {{html}}
220 220  <img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp7.jpg?rev=1.1" alt="IDP07" width="350"/>
... ... @@ -222,17 +222,29 @@
222 222  
223 223  |(((
224 224  **RANKING/ validation**
392 +
393 +
225 225  )))|(((
395 +//Notion of the validity (e.g., empirically tested)//
226 226  This can be empirically tested as the PwD, and other evaluators around, can hear Pepper saying a step to the PwD.
397 +
227 227  )))
228 228  |(((
229 229  **DESIGN PROBLEM (what)**
401 +
402 +
230 230  )))|(((
404 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
405 +
231 231  This design pattern is used to tell the PwD the next step in a certain activity breakdown. This activity can be anything, and the steps are added by the HCP into Pepper's system as a prerequisite.
232 232  )))
233 233  |(((
409 +
234 234  **CONTEXT (use when…)**
411 +
235 235  )))|(((
413 +//Contextual characteristics that are significant for the applicability of the pattern.//
414 +
236 236  This IDP can be used in the following contexts:
237 237  * PwD needs the next step for a gardening activity
238 238  * PwD needs the next step for making a paper plane
... ... @@ -239,15 +239,27 @@
239 239  )))
240 240  |(((
241 241  **DESIGN SOLUTION (how)**
421 +
422 +
242 242  )))|(((
424 +//Essential characteristics of the design solution that express the interaction intention.//
243 243  Here, already having the activity broken down into certain steps is very crucial. Also Pepper needs to say these steps verbally so the user can hear and act appropriately.
244 244  )))
245 245  |(((
246 246  **DESIGN RATIONALE (why)**
429 +
430 +
247 247  )))|(((
432 +//Argumentation that resulted in the chosen design solution.//
248 248  A verbal step here works better than merely following steps from a website, as would happen commonly these days. Also we believe that having Pepper as a physical being there might encourage the PwD to perform activities they used to enjoy, with higher frequency as Pepper would come up to them and ask them if they want to take part in an activity they enjoy.
249 249  )))
435 +|(((
436 +**EXAMPLES (as seen on…)**
250 250  
438 +)))|(((
439 +//Illustration (eg. picture, screenshot, animated graphic, video etc.) of an implementation of the design solution in a ‘real-life’ application, and include a short explanation describing the context of use.//
251 251  
252 -[1] Baird, A., & Samson, S. (2015). Music and dementia. Progress in brain research, 217, 207-235. https://www.cochranelibrary.com/cdsr/doi/10.1002/14651858.CD003477.pub2/abstract.
253 -[2] McDermott, O., Orrell, M., & Ridder, H. M. (2014). The importance of music for people with dementia: the perspectives of people with dementia, family carers, staff and music therapists. Aging & mental health, 18(6), 706-716. https://www.tandfonline.com/doi/full/10.1080/13607863.2013.875124
441 +TBD (should we include or not?)
442 +)))
443 +
444 +
Icon idp1.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.snehalodha
Size
... ... @@ -1,1 +1,0 @@
1 -77.9 KB
Content Icon
Icon idp2.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.snehalodha
Size
... ... @@ -1,1 +1,0 @@
1 -86.2 KB
Content Icon
Icon idp3.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.snehalodha
Size
... ... @@ -1,1 +1,0 @@
1 -90.9 KB
Content Icon
Icon idp4.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.snehalodha
Size
... ... @@ -1,1 +1,0 @@
1 -84.4 KB
Content Icon
Icon idp5.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.snehalodha
Size
... ... @@ -1,1 +1,0 @@
1 -88.5 KB
Content Icon
Icon idp6.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.snehalodha
Size
... ... @@ -1,1 +1,0 @@
1 -91.1 KB
Content Icon
Icon idp7.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.snehalodha
Size
... ... @@ -1,1 +1,0 @@
1 -88.5 KB
Content Icon