Skip to Content

Changes for page Team Design Patterns

Last modified by Mathieu Jung-Muller on 2022/04/04 13:54
From version Icon 10.1 Icon
edited by Sneha Lodha
on 2022/03/23 15:48
Change comment: There is no comment for this version
To version Icon 12.1 Icon
edited by Sneha Lodha
on 2022/03/23 15:48
Change comment: There is no comment for this version

Summary

Details

Icon Page properties
Content
... ... @@ -5,10 +5,10 @@
5 5  ===General Reminder Design Pattern===
6 6  **Overview**
7 7  The general reminder design pattern depicts the flow of interactions between Pepper and and 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.
8 -(((|
8 +|
9 9  **Purpose**
10 10  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.
11 -(((|
11 +|
12 12  **Steps Breakdown**
13 13  Although each of the IDPs contained in this TDP is described in great detail in Interactive Design Patterns section, below is a short overview:
14 14  * 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.
... ... @@ -16,6 +16,7 @@
16 16  * If the answer to the previous step was no, then Pepper proceeds by reminding the user to do the task in question.
17 17  * 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.
18 18  * Finally after receiving the confirmation, Pepper congratulates the the PwD and the DP comes to an end
19 +|
19 19  
20 20  
21 21