Skip to Content
Last modified by Mathieu Jung-Muller on 2022/04/04 13:55
From version Icon 16.1 Icon
edited by Sneha Lodha
on 2022/03/31 18:39
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
... ... @@ -6,18 +6,28 @@
6 6  {{/html}}
7 7  
8 8  |(((
9 -**RANKING/ validation**
9 +**RANKING/ validation**
10 +
10 10  )))|(((
12 +//Notion of the validity (e.g., empirically tested)//
11 11  When Pepper is playing music this can clearly be heard by the PwD, and other evaluators around, so this IDP is empirically testable.
14 +
12 12  )))
13 13  |(((
14 -**DESIGN PROBLEM (what)**
17 +**DESIGN PROBLEM (what)**
18 +
19 +
15 15  )))|(((
21 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
22 +
16 16  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.
17 17  )))
18 18  |(((
19 19  **CONTEXT (use when…)**
27 +
28 +
20 20  )))|(((
30 +//Contextual characteristics that are significant for the applicability of the pattern.//
21 21  This IDP can be used in the following contexts:
22 22  * Alert the PwD before an interaction takes place
23 23  * Wake up reminder for PwD
... ... @@ -26,17 +26,34 @@
26 26  )))
27 27  |(((
28 28  **DESIGN SOLUTION (how)**
39 +
40 +
29 29  )))|(((
42 +//Essential characteristics of the design solution that express the interaction intention.//
43 +
30 30  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.
31 31  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.
32 32  )))
33 33  |(((
34 34  **DESIGN RATIONALE (why)**
49 +
50 +
35 35  )))|(((
52 +//Argumentation that resulted in the chosen design solution.//
53 +
36 36  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.
37 37  )))
56 +|(((
57 +**EXAMPLES (as seen on…)**
38 38  
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.//
39 39  
63 +TBD (should we include or not?)
64 +)))
65 +
66 +
40 40  == IDP02==
41 41  {{html}}
42 42  <img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp2.jpg?rev=1.1" alt="IDP02" width="350"/>
... ... @@ -44,17 +44,29 @@
44 44  
45 45  |(((
46 46  **RANKING/ validation**
74 +
75 +
47 47  )))|(((
77 +//Notion of the validity (e.g., empirically tested)//
48 48  This can be empirically tested as the PwD, and other evaluators around, can hear Pepper asking this question.
79 +
49 49  )))
50 50  |(((
51 51  **DESIGN PROBLEM (what)**
83 +
84 +
52 52  )))|(((
86 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
87 +
53 53  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.
54 54  )))
55 55  |(((
56 -**CONTEXT (use when…)**
91 +**CONTEXT (use when…)**
92 +
93 +
57 57  )))|(((
95 +//Contextual characteristics that are significant for the applicability of the pattern.//
96 +
58 58  This IDP can be used in the following contexts:
59 59  * Understanding whether the PwD has taken medication before reminding them
60 60  * Understanding whether the PwD has eaten a meal before reminding them
... ... @@ -61,17 +61,36 @@
61 61  The list can be further expanded as more crucial task usecases are added.
62 62  )))
63 63  |(((
64 -**DESIGN SOLUTION (how)**
103 +**DESIGN SOLUTION (how)**
104 +
105 +
65 65  )))|(((
66 -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 +
67 67  )))
68 68  |(((
69 69  **DESIGN RATIONALE (why)**
114 +
115 +
70 70  )))|(((
117 +//Argumentation that resulted in the chosen design solution.//
118 +
71 71  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 +
72 72  )))
122 +|(((
123 +**EXAMPLES (as seen on…)**
73 73  
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.//
74 74  
129 +TBD (should we include or not?)
130 +)))
131 +
132 +
75 75  == IDP03==
76 76  {{html}}
77 77  <img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp3.jpg?rev=1.1" alt="IDP03" width="350"/>
... ... @@ -79,17 +79,29 @@
79 79  
80 80  |(((
81 81  **RANKING/ validation**
140 +
141 +
82 82  )))|(((
143 +//Notion of the validity (e.g., empirically tested)//
83 83  This can be empirically tested as the PwD, and other evaluators around, can hear Pepper reminding the PwD to do the task.
145 +
84 84  )))
85 85  |(((
86 -**DESIGN PROBLEM (what)**
148 +**DESIGN PROBLEM (what)**
149 +
150 +
87 87  )))|(((
152 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
153 +
88 88  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.
89 89  )))
90 90  |(((
91 91  **CONTEXT (use when…)**
158 +
159 +
92 92  )))|(((
161 +//Contextual characteristics that are significant for the applicability of the pattern.//
162 +
93 93  This IDP can be used in the following contexts:
94 94  * Reminding the PwD to take medication if they have not done so already
95 95  * Reminding the PwD to eat food if they have not done so already
... ... @@ -97,16 +97,32 @@
97 97  )))
98 98  |(((
99 99  **DESIGN SOLUTION (how)**
170 +
171 +
100 100  )))|(((
173 +//Essential characteristics of the design solution that express the interaction intention.//
174 +
101 101  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.
102 102  )))
103 103  |(((
104 104  **DESIGN RATIONALE (why)**
179 +
180 +
105 105  )))|(((
182 +//Argumentation that resulted in the chosen design solution.//
106 106  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 +
107 107  )))
186 +|(((
187 +**EXAMPLES (as seen on…)**
108 108  
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.//
109 109  
192 +TBD (should we include or not?)
193 +)))
194 +
195 +
110 110  == IDP04==
111 111  {{html}}
112 112  <img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp4.jpg?rev=1.1" alt="IDP04" width="350"/>
... ... @@ -114,17 +114,29 @@
114 114  
115 115  |(((
116 116  **RANKING/ validation**
203 +
204 +
117 117  )))|(((
206 +//Notion of the validity (e.g., empirically tested)//
118 118  This can be empirically tested as the PwD, and other evaluators around, can hear Pepper asking the PwD for confirmation.
208 +
119 119  )))
120 120  |(((
121 121  **DESIGN PROBLEM (what)**
212 +
213 +
122 122  )))|(((
215 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
216 +
123 123  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.
124 124  )))
125 125  |(((
220 +
126 126  **CONTEXT (use when…)**
222 +
127 127  )))|(((
224 +//Contextual characteristics that are significant for the applicability of the pattern.//
225 +
128 128  This IDP can be used in the following contexts:
129 129  * Asking for confirmation of having taken medication
130 130  * Asking for confirmation of having eaten a meal
... ... @@ -133,16 +133,33 @@
133 133  )))
134 134  |(((
135 135  **DESIGN SOLUTION (how)**
234 +
235 +
136 136  )))|(((
237 +//Essential characteristics of the design solution that express the interaction intention.//
238 +
137 137  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.
138 138  )))
139 139  |(((
140 140  **DESIGN RATIONALE (why)**
243 +
244 +
141 141  )))|(((
246 +//Argumentation that resulted in the chosen design solution.//
247 +
142 142  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 +
143 143  )))
251 +|(((
252 +**EXAMPLES (as seen on…)**
144 144  
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.//
145 145  
257 +TBD (should we include or not?)
258 +)))
259 +
260 +
146 146  == IDP05==
147 147  {{html}}
148 148  <img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp5.jpg?rev=1.1" alt="IDP05" width="350"/>
... ... @@ -149,18 +149,29 @@
149 149  {{/html}}
150 150  
151 151  |(((
152 -**RANKING/ validation**
267 +**RANKING/ validation**
268 +
269 +
153 153  )))|(((
271 +//Notion of the validity (e.g., empirically tested)//
154 154  This can be empirically tested as the PwD, and other evaluators around, can hear Pepper congratulating the PwD.
155 155  )))
156 156  |(((
157 157  **DESIGN PROBLEM (what)**
276 +
277 +
158 158  )))|(((
279 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
280 +
159 159  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.
160 160  )))
161 161  |(((
284 +
162 162  **CONTEXT (use when…)**
286 +
163 163  )))|(((
288 +//Contextual characteristics that are significant for the applicability of the pattern.//
289 +
164 164  This IDP can be used in the following contexts:
165 165  * Congratulate the PwD for having taken medication
166 166  * Congratulate the PwD for having eaten medication
... ... @@ -169,17 +169,32 @@
169 169  )))
170 170  |(((
171 171  **DESIGN SOLUTION (how)**
298 +
299 +
172 172  )))|(((
301 +//Essential characteristics of the design solution that express the interaction intention.//
302 +
173 173  This IDP is quite basic and simply pre-programmed into Pepper. Simply congratulating the PwD for finishing a certain task or activity is sufficient.
174 174  )))
175 175  |(((
176 176  **DESIGN RATIONALE (why)**
307 +
308 +
177 177  )))|(((
178 178  //Argumentation that resulted in the chosen design solution.//
179 179  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 +
180 180  )))
314 +|(((
315 +**EXAMPLES (as seen on…)**
181 181  
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.//
182 182  
320 +TBD (should we include or not?)
321 +)))
322 +
323 +
183 183  == IDP06==
184 184  {{html}}
185 185  <img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp6.jpg?rev=1.1" alt="IDP06s" width="350"/>
... ... @@ -187,17 +187,28 @@
187 187  
188 188  |(((
189 189  **RANKING/ validation**
331 +
332 +
190 190  )))|(((
334 +//Notion of the validity (e.g., empirically tested)//
191 191  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.
192 192  )))
193 193  |(((
194 194  **DESIGN PROBLEM (what)**
339 +
340 +
195 195  )))|(((
342 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
343 +
196 196  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.
197 197  )))
198 198  |(((
347 +
199 199  **CONTEXT (use when…)**
349 +
200 200  )))|(((
351 +//Contextual characteristics that are significant for the applicability of the pattern.//
352 +
201 201  This IDP can be used in the following contexts:
202 202  * PwD wants to perform a new activity
203 203  * Pepper is not yet personalized to the particular PwD
... ... @@ -204,16 +204,32 @@
204 204  )))
205 205  |(((
206 206  **DESIGN SOLUTION (how)**
359 +
360 +
207 207  )))|(((
362 +//Essential characteristics of the design solution that express the interaction intention.//
363 +
208 208  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.
209 209  )))
210 210  |(((
211 211  **DESIGN RATIONALE (why)**
368 +
369 +
212 212  )))|(((
371 +//Argumentation that resulted in the chosen design solution.//
213 213  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 +
214 214  )))
375 +|(((
376 +**EXAMPLES (as seen on…)**
215 215  
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.//
216 216  
381 +TBD (should we include or not?)
382 +)))
383 +
384 +
217 217  == IDP07==
218 218  {{html}}
219 219  <img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp7.jpg?rev=1.1" alt="IDP07" width="350"/>
... ... @@ -221,17 +221,29 @@
221 221  
222 222  |(((
223 223  **RANKING/ validation**
392 +
393 +
224 224  )))|(((
395 +//Notion of the validity (e.g., empirically tested)//
225 225  This can be empirically tested as the PwD, and other evaluators around, can hear Pepper saying a step to the PwD.
397 +
226 226  )))
227 227  |(((
228 228  **DESIGN PROBLEM (what)**
401 +
402 +
229 229  )))|(((
404 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
405 +
230 230  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.
231 231  )))
232 232  |(((
409 +
233 233  **CONTEXT (use when…)**
411 +
234 234  )))|(((
413 +//Contextual characteristics that are significant for the applicability of the pattern.//
414 +
235 235  This IDP can be used in the following contexts:
236 236  * PwD needs the next step for a gardening activity
237 237  * PwD needs the next step for making a paper plane
... ... @@ -238,13 +238,27 @@
238 238  )))
239 239  |(((
240 240  **DESIGN SOLUTION (how)**
421 +
422 +
241 241  )))|(((
424 +//Essential characteristics of the design solution that express the interaction intention.//
242 242  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.
243 243  )))
244 244  |(((
245 245  **DESIGN RATIONALE (why)**
429 +
430 +
246 246  )))|(((
432 +//Argumentation that resulted in the chosen design solution.//
247 247  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.
248 248  )))
435 +|(((
436 +**EXAMPLES (as seen on…)**
249 249  
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.//
250 250  
441 +TBD (should we include or not?)
442 +)))
443 +
444 +