Changes for page Interaction Design Patterns

Last modified by Mathieu Jung-Muller on 2022/04/04 13:55

From 8.1 to 7.1 From 12.1 to 11.1

From version

11.1

edited by Mathieu Jung-Muller
on 2022/03/30 00:28

Change comment: There is no comment for this version

To version

8.1

edited by Sneha Lodha
on 2022/03/23 23:43

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.Mathieu
++XWiki.snehalodha

Content

@@ -10,7 +10,7 @@
  )))|(((
  //Notion of the validity (e.g., empirically tested)//
--When Pepper is playing music this can clearly be heard by the PwD, and other evaluators around so this IDP is empirically testable.
++When Pepper is playing music this can clearly be heard by the PwD, and other evaluators around hence this IDP is empirically testable.
  )))
  |(((
@@ -172,7 +172,7 @@
  )))|(((
  //Essential characteristics of the design solution that express the interaction intention.//
--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.
++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 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.
  )))
  |(((
  **DESIGN RATIONALE (why)**
@@ -180,7 +180,7 @@
  )))|(((
  //Argumentation that resulted in the chosen design solution.//
--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.
++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's as a physical being there might encourage the PwD to take such reminders with higher importance than a simple notification.
  )))
  |(((
@@ -382,63 +382,3 @@
  )))
--== IDP07==
--{{html}}
--<img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp7.jpg?rev=1.1" alt="IDP07" width="350"/>
--{{/html}}
--
--|(((
--**RANKING/ validation**
--
--
--)))|(((
--//Notion of the validity (e.g., empirically tested)//
--This can be empirically tested as the PwD, and other evaluators around can hear Pepper saying a step to the PwD.
--
--)))
--|(((
--**DESIGN PROBLEM (what)**
--
--
--)))|(((
--//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
--
--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.
--)))
--|(((
--
--**CONTEXT (use when…)**
--
--)))|(((
--//Contextual characteristics that are significant for the applicability of the pattern.//
--
--This IDP can be used in the following contexts:
--* PwD needs the next step for a gardening activity
--* PwD needs the next step for making a paper plane
--)))
--|(((
--**DESIGN SOLUTION (how)**
--
--
--)))|(((
--//Essential characteristics of the design solution that express the interaction intention.//
--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.
--)))
--|(((
--**DESIGN RATIONALE (why)**
--
--
--)))|(((
--//Argumentation that resulted in the chosen design solution.//
--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.
--)))
--|(((
--**EXAMPLES (as seen on…)**
--
--)))|(((
--//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.//
--
--TBD (should we include or not?)
--)))
--
--