Skip to Content

Changes for page Team Design Patterns

Last modified by Mathieu Jung-Muller on 2022/04/04 13:54
From version Icon 16.1 Icon
edited by Pierre Bongrand
on 2022/03/30 16:22
Change comment: There is no comment for this version
To version Icon 17.1 Icon
edited by Pierre Bongrand
on 2022/03/30 18:10
Change comment: There is no comment for this version

Summary

Details

Icon Page properties
Content
... ... @@ -1,5 +1,9 @@
1 -===Definition of ===
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 2  
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].
3 3  
4 4  
5 5  
... ... @@ -18,11 +18,12 @@
18 18  * If the answer to the previous step was no, then Pepper proceeds by reminding the user to do the task in question.
19 19  * 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.
20 20  * Finally after receiving the confirmation, Pepper congratulates the the PwD and the DP comes to an end.
25 +|
21 21  {{html}}
22 22  <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"/>
23 23  {{/html}}
24 -|
25 25  
30 +
26 26  ===Activity Breakdown Design Pattern===
27 27  **Overview**
28 28  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.