Changes for page IDP: Motivate the PwD

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-IDP: Motivate the PwD
	1	+IDP: Explain a Group Activity

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.varunsingh3000
	1	+xwiki:XWiki.RuuddeJong

Content

...	...	@@ -1,33 +1,25 @@
1		-**Design problem: **The PwD would like to paint but is not as active and confident about their painting capabilities as they used to be because of the dementia condition. The Pepper robot in this case provides meaningful motivation and encouragement while they are doing the activity.
	1	+**Design problem: **The specific role of the [[Humanoid Robot>>doc:Main.c\. Technology.Humanoid Robot.WebHome]] (e.g., Pepper)  in the group activity (e.g., a game) and the game or activity to play, are not yet known to the [[Person with Dementia>>doc:Main.sdf.Stakeholders.Person with Dementia.WebHome]] (i.e., the participants). The participants do not know how the activity has to be played and how they should participate.
2	2
3		-**Design solution:** Pepper does this by saying words of encouragement and motivating the PwD to preserver and not give up on the task. Of course, if the PwD wants to take a break, is done for the day or is satisfied with the painting they have done then Pepper won't keep on egging them to continue but would understand this stage and congratulate the PwD for an awesome painting which they can be proud of and show their family members.
	3	+**Design solution:** In this design pattern, the robot follows a monologue to explain the activity and what the participants are expected to do in the session. After this monologue, the robot asks for confirmation about whether or not the explanation has been understood. If this is not the case, the explanation is repeated. The tone of the robot remains friendly and uses open gestures to make the interaction less formal.
4	4
5		-**Use when: **During the painting activity
	5	+**Use when: **After the introduction but before the start of an activity, when participants are unfamiliar with the goal of the interaction.
6	6
7		-**Design rationale: **This design pattern follows the strategies mentioned in [1] to provide motivation and encouragement to the PwD.
	7	+**Design rationale: **This design pattern follows the Didactic Communication pattern introduced by Khan et al., where there is a transmission of information from the robot to the human agent. By explaining the activity, participants will know what to expect and how they can participate in the activity.
8	8
9		-**Example: **For our use case, Pepper provides such encouragement and motivation at appropriate intervals making sure that the frequency isn't too much or less. Since Pepper does this verbally the speech rate is slightly lower than average considering the age and cognitive abilities of the participants. For detail on the parameter setting, see the relevant. For detail on the parameter setting, see Table below.
	9	+**Example: **In our use case (i.e. "group exercise"  as specified by group 4 of the SCE-course in 2020), Pepper explains using speech and hand gestures, the goal of the activity, which is to perform exercise moves together with the PwD. The speech rate is slightly lower than average considering the age and cognitive abilities of the participants. Pepper then explains the steps involved such as playing the song and demonstrating the dance moves that the participants are expected to repeat. Pepper confirms that the explanation is understood and if not, repeats the explanation. For detail on the parameter setting, see the Table below.
10	10
11	11
12	12	|=(% colspan="2" %)Parameter|=Choice|=Rationale
13	13	|(% colspan="2" %)Gesture Openness|Open|Makes the interaction less formal so that the PwD can familiarize themself better with Pepper.
	14	+|(% colspan="2" %)Gaze Diversion|Diverted|Pepper will be able to look at all the PwD instead of fixating on one of them.
14	14	|(% colspan="2" %)Proxemic Closeness|(((
15	15	Average
16	16
17		-(close)
18		-)))|Kept close to the PwD.
	18	+(between close and far)
	19	+)))|Kept in the middle since there will be PwD both close and far away from Pepper at the same time.
19	19	|(% rowspan="3" %)Voice
20	20	|(% colspan="1" %)Pitch|Middle|A high pitch makes Pepper sound friendly but it should not be too high otherwise the PwD might not be able to hear Pepper well.
21		-|(% colspan="1" %)Speed|Slower than average|Since the PwD are old, a low speech rate will help them understand Pepper better but it should not be too slow otherwise, they will be bored.
	22	+|(% colspan="1" %)Speed|Slower than average|Since the PwD are old, a low speech rate will help them understand Pepper better but it should not be too sow otherwise, they will be bored.
22	22	|(% colspan="1" %)Prosody|Strong|The prosody of the voice should be strong so that Pepper can articulate better.
23	23	|(% colspan="2" %)Speech Acts|Informal|An informal tone makes the interaction more comfortable for the participants.
24		-|(% colspan="2" %)Eye Color|White|(((
25		-The eyes should be white so as to not distract the PwD.
26		-)))
27		-
28		-References:
29		-
30		-1. Hollyforde, Sarah, and Steve Whiddett. //The motivation handbook//. CIPD Publishing, 2002.
31		-
32		-
33		-
	25	+|(% colspan="2" %)Eye Color|White|The eyes should be white so as to not distract the PwD.