Wiki source code of Team Design Patterns

Version 20.1 by Pierre Bongrand on 2022/03/30 18:13

version	line-number	content
17.1	1	===Definition of Design Pattern symbols===
	2	{{html}}
	3	<img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/TDP_generalreminder.jpg?rev=1.1" alt="Design Pattern Calendar" width="1000"/>
	4	{{/html}}
2.1	5
17.1	6	In order to define our design pattern we needed to work from a baseline of symbols. Our definition of symbols are coming from J van Diggelen and M Johnson work [1].
16.1	7
20.1	8	[[image:directdp.png]]
16.1	9
	10
4.1	11	===General Reminder Design Pattern===
6.1	12	Overview
14.1	13	The general reminder design pattern depicts the flow of interactions between Pepper and the PwD in reminder related usecases. This TDP contains the overarching generalizations of the medication, nutrition and calendar event reminders as mentioned in the use cases (UC01, UC02, UC03). Below we describe this TDP in further detail.
11.1	14	\|
8.1	15	Purpose
	16	The purpose of this TDP is to demonstrate the flow of how a reminder interaction would take place. Reminders are an essential purpose of Pepper in our design, due to their necessity in PwD's daily life. Taking the correct medicine at precise times is crucial for the PwD's well-being, and once this information is available to Pepper, daily (or multiple times a day) reminders can be configured to ensure this is not forgotten. The same applies to meal reminder, although this in some cases is less crucial than taking medicine. Finally, another instance of this can also be calendar event reminders, which aids the PwD by reminding them of special events upcoming in their calendars i.e. grandchild's birthday party.
12.1	17	\|
9.1	18	Steps Breakdown
	19	Although each of the IDPs contained in this TDP is described in great detail in Interactive Design Patterns section, below is a short overview:
	20	* Pepper initially plays some music to gain the attention of the PwD. This is mainly done in order to not suddenly startle the PwD by the robots presence.
	21	* Now having gained the attention of the PwD, Pepper asks whether the PwD has already performed the task that the reminder is set for. If the answer is yes, then this is where the DP ends, because the reminder would serve no purpose.
	22	* If the answer to the previous step was no, then Pepper proceeds by reminding the user to do the task in question.
	23	* Now Pepper will wait for a confirmation of the user having done the task in question. The waiting times are different for different use cases, as taking medicine for example takes less time that eating a meal.
15.1	24	* Finally after receiving the confirmation, Pepper congratulates the the PwD and the DP comes to an end.
16.2	25	\|
13.1	26	{{html}}
16.1	27	<img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/TDP_generalreminder.jpg?rev=1.1" alt="Design Pattern Calendar" width="1000"/>
13.1	28	{{/html}}
16.1	29
16.2	30
14.1	31	===Activity Breakdown Design Pattern===
	32	Overview
	33	The general activity breakdown design pattern depicts the flow of interactions between Pepper and the PwD with respect to the breakdown of any activity that has been entered in Pepper's system. With respect to the usecases present, this TDP applies to the wake-up routine. Below we describe the TDP in further detail.
	34	\|
	35	Purpose
	36	The purpose of this TDP is to demonstrate the flow of how a activity interaction would take place. Often times it becomes challenging for patients to perform basic and complex activities. These might be essential life activities such as having a pleasurable wake-up routine, or more complex activities such as gardening or cooking. We see assisting the PwD with such activities as a meaningful addition to their daily life. The aim is to have Pepper guide the PwD through the steps of an activity and stop at each step to analyze whether everything went smoothly.
	37	\|
	38	Steps Breakdown
	39	Although each of the IDPs contained in this TDP is described in great detail in Interactive Design Patterns section, below is a short overview:
	40	* As a prerequisite, the health care professional (HCP) needs to initially enter the activity breakdown into Pepper's system.
	41	* Pepper initially plays some music to gain the attention of the PwD. This is mainly done in order to not suddenly startle the PwD by the robots presence.
	42	* Pepper then asks the PwD whether they would like to do an activity and if the PwD responds positively, the Pepper starts the activity breakdown.
	43	* For each step, the robot presents the step to the PwD, and waits for the PwD to complete the step in question and tell so to the robot.
	44	* Once all the steps have been successfully completed, Pepper congratulates the PwD.
	45	\|
6.1	46
16.1	47	{{html}}
	48	<img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/TDP_generalactivity.jpg?rev=1.1" alt="Design Pattern Calendar" width="1000"/>
	49	{{/html}}
6.1	50
7.1	51
8.1	52