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 12.1 Icon
edited by Mathieu Jung-Muller
on 2022/03/30 00:36
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  )))
... ... @@ -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 in order 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 345  )))
346 346  |(((
347 347