Skip to Content
Last modified by Mathieu Jung-Muller on 2022/04/04 13:55
From version Icon 5.1 Icon
edited by Sneha Lodha
on 2022/03/23 22:15
Change comment: There is no comment for this version
To version Icon 10.1 Icon
edited by Mathieu Jung-Muller
on 2022/03/30 00:18
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,8 +1,8 @@
1 1  (% style="background-color:#ffffff; font-size:14px" %)
2 2  
3 -== IDP001==
3 +== IDP01==
4 4  {{html}}
5 -<img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp1.jpg?rev=1.1" alt="IDP001" width="350"/>
5 +<img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp1.jpg?rev=1.1" alt="IDP01" width="350"/>
6 6  {{/html}}
7 7  
8 8  |(((
... ... @@ -10,7 +10,7 @@
10 10  
11 11  )))|(((
12 12  //Notion of the validity (e.g., empirically tested)//
13 -When Pepper is playing music this can clearly be heard by the PwD, and other evaluators around hence this IDP is empirically testable.
13 +When Pepper is playing music this can clearly be heard by the PwD, and other evaluators around so this IDP is empirically testable.
14 14  
15 15  )))
16 16  |(((
... ... @@ -64,9 +64,9 @@
64 64  )))
65 65  
66 66  
67 -== IDP002==
67 +== IDP02==
68 68  {{html}}
69 -<img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp2.jpg?rev=1.1" alt="IDP002" width="350"/>
69 +<img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp2.jpg?rev=1.1" alt="IDP02" width="350"/>
70 70  {{/html}}
71 71  
72 72  |(((
... ... @@ -130,9 +130,9 @@
130 130  )))
131 131  
132 132  
133 -== IDP003==
133 +== IDP03==
134 134  {{html}}
135 -<img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp3.jpg?rev=1.1" alt="IDP003" width="350"/>
135 +<img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp3.jpg?rev=1.1" alt="IDP03" width="350"/>
136 136  {{/html}}
137 137  
138 138  |(((
... ... @@ -193,9 +193,9 @@
193 193  )))
194 194  
195 195  
196 -== IDP004==
196 +== IDP04==
197 197  {{html}}
198 -<img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp3.jpg?rev=1.1" alt="IDP004" width="350"/>
198 +<img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp4.jpg?rev=1.1" alt="IDP04" width="350"/>
199 199  {{/html}}
200 200  
201 201  |(((
... ... @@ -258,3 +258,187 @@
258 258  )))
259 259  
260 260  
261 +== IDP05==
262 +{{html}}
263 +<img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp5.jpg?rev=1.1" alt="IDP05" width="350"/>
264 +{{/html}}
265 +
266 +|(((
267 +**RANKING/ validation**
268 +
269 +
270 +)))|(((
271 +//Notion of the validity (e.g., empirically tested)//
272 +This can be empirically tested as the PwD, and other evaluators around can hear Pepper congratulating the PwD.
273 +)))
274 +|(((
275 +**DESIGN PROBLEM (what)**
276 +
277 +
278 +)))|(((
279 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
280 +
281 +This design pattern is used to verbally congratulate the PwD, and make the feel about about a task that they just accomplished. This is to lift the spirits of the PwD and make the enjoy and want to do certain tasks.
282 +)))
283 +|(((
284 +
285 +**CONTEXT (use when…)**
286 +
287 +)))|(((
288 +//Contextual characteristics that are significant for the applicability of the pattern.//
289 +
290 +This IDP can be used in the following contexts:
291 +* Congratulate the PwD for having taken medication
292 +* Congratulate the PwD for having eaten medication
293 +* Congratulate the PwD for doing a particular activity completely
294 +The list can be further expanded as more task usecases are added.
295 +)))
296 +|(((
297 +**DESIGN SOLUTION (how)**
298 +
299 +
300 +)))|(((
301 +//Essential characteristics of the design solution that express the interaction intention.//
302 +
303 +This IDP is quite basic and simply pre-programmed into Pepper. Simply congratulating the PwD for finishing a certain task or activity is sufficient.
304 +)))
305 +|(((
306 +**DESIGN RATIONALE (why)**
307 +
308 +
309 +)))|(((
310 +//Argumentation that resulted in the chosen design solution.//
311 + 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 +
313 +)))
314 +|(((
315 +**EXAMPLES (as seen on…)**
316 +
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.//
319 +
320 +TBD (should we include or not?)
321 +)))
322 +
323 +
324 +== IDP06==
325 +{{html}}
326 +<img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp6.jpg?rev=1.1" alt="IDP06s" width="350"/>
327 +{{/html}}
328 +
329 +|(((
330 +**RANKING/ validation**
331 +
332 +
333 +)))|(((
334 +//Notion of the validity (e.g., empirically tested)//
335 +This can be tested by performing some other IDPs, which refer to utilizing the breakdown of a particular activity. Since this some programmed into Pepper, it is not empirically testable.
336 +)))
337 +|(((
338 +**DESIGN PROBLEM (what)**
339 +
340 +
341 +)))|(((
342 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
343 +
344 +This design pattern is used by the HPC inorder to enter some activities into Pepper, that that the PwD might personally enjoy. This is so that Pepper's system contains the breakdown to certain desired activities.
345 +)))
346 +|(((
347 +
348 +**CONTEXT (use when…)**
349 +
350 +)))|(((
351 +//Contextual characteristics that are significant for the applicability of the pattern.//
352 +
353 +This IDP can be used in the following contexts:
354 +* PwD wants to perform a new activity
355 +* Pepper is not yet personalized to the particular PwD
356 +)))
357 +|(((
358 +**DESIGN SOLUTION (how)**
359 +
360 +
361 +)))|(((
362 +//Essential characteristics of the design solution that express the interaction intention.//
363 +
364 +Here in order to easy configuration of Pepper, we will utilize the tablet feature where the HPC can enter activity steps. This is so that the caregiver also has some autonomy over Pepper rather than just the developers. The interface designed is easy to use as, HCPs are not required to have very high technical knowledge.
365 +)))
366 +|(((
367 +**DESIGN RATIONALE (why)**
368 +
369 +
370 +)))|(((
371 +//Argumentation that resulted in the chosen design solution.//
372 +We allow the HPC to provide steps has they are they 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 having some arbitrary step up of steps from the internet.
373 +
374 +)))
375 +|(((
376 +**EXAMPLES (as seen on…)**
377 +
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.//
380 +
381 +TBD (should we include or not?)
382 +)))
383 +
384 +
385 +== IDP07==
386 +{{html}}
387 +<img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp7.jpg?rev=1.1" alt="IDP07" width="350"/>
388 +{{/html}}
389 +
390 +|(((
391 +**RANKING/ validation**
392 +
393 +
394 +)))|(((
395 +//Notion of the validity (e.g., empirically tested)//
396 +This can be empirically tested as the PwD, and other evaluators around can hear Pepper saying a step to the PwD.
397 +
398 +)))
399 +|(((
400 +**DESIGN PROBLEM (what)**
401 +
402 +
403 +)))|(((
404 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
405 +
406 +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.
407 +)))
408 +|(((
409 +
410 +**CONTEXT (use when…)**
411 +
412 +)))|(((
413 +//Contextual characteristics that are significant for the applicability of the pattern.//
414 +
415 +This IDP can be used in the following contexts:
416 +* PwD needs the next step for a gardening activity
417 +* PwD needs the next step for making a paper plane
418 +)))
419 +|(((
420 +**DESIGN SOLUTION (how)**
421 +
422 +
423 +)))|(((
424 +//Essential characteristics of the design solution that express the interaction intention.//
425 +Here already having the activity broken down into certain steps is very crucial. Also Pepper needs to stay these steps verbally so the user can hear and act appropriately.
426 +)))
427 +|(((
428 +**DESIGN RATIONALE (why)**
429 +
430 +
431 +)))|(((
432 +//Argumentation that resulted in the chosen design solution.//
433 +A verbal step here works better than a simply following steps from a website, as would happen commonly these days. Also we believe that having Pepper's 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 in they want to take part in an activity they enjoy.
434 +)))
435 +|(((
436 +**EXAMPLES (as seen on…)**
437 +
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.//
440 +
441 +TBD (should we include or not?)
442 +)))
443 +
444 +