Skip to Content
Last modified by Mathieu Jung-Muller on 2022/04/04 13:55
From version Icon 11.1 Icon
edited by Mathieu Jung-Muller
on 2022/03/30 00:28
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
Content
... ... @@ -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 so 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  |(((
... ... @@ -75,7 +75,7 @@
75 75  
76 76  )))|(((
77 77  //Notion of the validity (e.g., empirically tested)//
78 -This can be empirically tested as the PwD, and other evaluators around can hear Pepper asking this question.
78 +This can be empirically tested as the PwD, and other evaluators around, can hear Pepper asking this question.
79 79  
80 80  )))
81 81  |(((
... ... @@ -141,7 +141,7 @@
141 141  
142 142  )))|(((
143 143  //Notion of the validity (e.g., empirically tested)//
144 -This can be empirically tested as the PwD, and other evaluators around can hear Pepper reminding the PwD to do the task.
144 +This can be empirically tested as the PwD, and other evaluators around, can hear Pepper reminding the PwD to do the task.
145 145  
146 146  )))
147 147  |(((
... ... @@ -204,7 +204,7 @@
204 204  
205 205  )))|(((
206 206  //Notion of the validity (e.g., empirically tested)//
207 -This can be empirically tested as the PwD, and other evaluators around can hear Pepper asking the PwD for confirmation.
207 +This can be empirically tested as the PwD, and other evaluators around, can hear Pepper asking the PwD for confirmation.
208 208  
209 209  )))
210 210  |(((
... ... @@ -245,7 +245,7 @@
245 245  )))|(((
246 246  //Argumentation that resulted in the chosen design solution.//
247 247  
248 -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.
248 +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 249  
250 250  )))
251 251  |(((
... ... @@ -269,7 +269,7 @@
269 269  
270 270  )))|(((
271 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.
272 +This can be empirically tested as the PwD, and other evaluators around, can hear Pepper congratulating the PwD.
273 273  )))
274 274  |(((
275 275  **DESIGN PROBLEM (what)**
... ... @@ -278,7 +278,7 @@
278 278  )))|(((
279 279  //Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
280 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.
281 +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.
282 282  )))
283 283  |(((
284 284  
... ... @@ -308,7 +308,7 @@
308 308  
309 309  )))|(((
310 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.
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 312  
313 313  )))
314 314  |(((
... ... @@ -315,7 +315,7 @@
315 315  **EXAMPLES (as seen on…)**
316 316  
317 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.//
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 319  
320 320  TBD (should we include or not?)
321 321  )))
... ... @@ -332,7 +332,7 @@
332 332  
333 333  )))|(((
334 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.
335 +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.
336 336  )))
337 337  |(((
338 338  **DESIGN PROBLEM (what)**
... ... @@ -341,7 +341,7 @@
341 341  )))|(((
342 342  //Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
343 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.
344 +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.
345 345  )))
346 346  |(((
347 347  
... ... @@ -361,7 +361,7 @@
361 361  )))|(((
362 362  //Essential characteristics of the design solution that express the interaction intention.//
363 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.
364 +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.
365 365  )))
366 366  |(((
367 367  **DESIGN RATIONALE (why)**
... ... @@ -369,7 +369,7 @@
369 369  
370 370  )))|(((
371 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.
372 +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 373  
374 374  )))
375 375  |(((
... ... @@ -393,7 +393,7 @@
393 393  
394 394  )))|(((
395 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.
396 +This can be empirically tested as the PwD, and other evaluators around, can hear Pepper saying a step to the PwD.
397 397  
398 398  )))
399 399  |(((
... ... @@ -422,7 +422,7 @@
422 422  
423 423  )))|(((
424 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.
425 +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.
426 426  )))
427 427  |(((
428 428  **DESIGN RATIONALE (why)**
... ... @@ -430,7 +430,7 @@
430 430  
431 431  )))|(((
432 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.
433 +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.
434 434  )))
435 435  |(((
436 436  **EXAMPLES (as seen on…)**