Changes for page IDP: Save a picture of the painting

Summary

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

Details

Page properties

Content

...	...	@@ -1,14 +1,13 @@
1		-**Design problem: **The PwD would like to paint but is not as active as it used to be because of the dementia condition. The Pepper robot in this case helps them to perform the activity and provides meaningful guidance and suggestions while they are doing the activity.
	1	+**Design problem: **The PwD likes to paint and was quite enthusiastic about painting in their past life but because of dementia they are not as active and can sometimes forget about what made them happy, who they are and their overall identity. We would like to help them to maintain their identity by engaging in the painting activity which brought them joy and to do that we first like to remind them to do the activity. The Pepper robot in this case tries to trigger the start of the activity.
2	2
3		-**Design solution:** In this design pattern, the robot first instantiates the interaction by first asking the PwD whether they want to perform the painting activity and then at certain milestones of the painting. The suggestions would not be annoying or too frequent so as to not cause annoyance but at proper intervals. The robot's tone remains friendly and uses open gestures to make the interaction less formal.
	3	+**Design solution:** In this design pattern, the robot first instantiates the interaction by first reminding the PwD about the painting activity preferably during their entertainment/break time. The PwD could be feeling bored or be less motivated to do something but because the robot tried to remind and engage them to perform the activity they would likely be inclined to do it.
4	4
5		-**Use when: **After the introduction but before the start of an activity, when PwD is unfamiliar with the flow of the interaction.
	5	+**Use when: **During the entertainment/break time when the patients are enjoying.
6	6
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.
	7	+**Design rationale: **This design pattern follows the design patterns mentioned in [1], where they show how reminder patterns provide a flexible and powerful way to manage time-based events and actions in a variety of different applications.
8	8
9		-**Example: **For our use case, Pepper triggers the activity using speech and hand gestures, which is to help the PwD paint. 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 the style of the painting and the topic. Appropriate suggestions and instructions are given at proper intervals. Pepper confirms that the explanation is understood and if not, repeats the explanation. For detail on the parameter setting, see the Table below.
	9	+**Example: **Pepper can during the break time approach the PwD and remind them by asking them whether they would like to paint. The PwD can choose to then engage in the activity or not. If they do decide to engage then [[UseCase 01>>doc:Design Patterns.Interaction Design Patterns.IDP\: Explain a Group Activity.WebHome]] will be executed. If they decide to not engage in the activity then Pepper would leave them alone but then ask them after some time again whether they have changed their mind. If they respond no again then Pepper would leave them alone for good.
10	10
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	14	|(% colspan="2" %)Proxemic Closeness|(((
...	...	@@ -21,4 +21,17 @@
21	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	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|The eyes should be white so as to not distract the PwD.
	23	+|(% colspan="2" %)Eye Color|White|(((
	24	+The eyes should be white so as to not distract the PwD.
	25	+
	26	+
	27	+)))
	28	+
	29	+
	30	+References:
	31	+
	32	+[1] Gamma, E., Helm, R., Johnson, R.~,~, Vlissides, J. M. (1994). //Design Patterns: Elements of Reusable Object-Oriented Software//. Addison-Wesley Professional. ISBN: 0201633612
	33	+
	34	+
	35	+
	36	+