Changes for page Team Design Patterns

Summary

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

Details

Page properties

Content

...	...	@@ -5,10 +5,8 @@
5	5	In our case, the agent interacting in our environment can be of two different nature:
6	6	* Human
7	7	* Robot
8		-
9		-(% style="text-align:center" %)
10	10	[[image:agentdp.png||width="400" height="350"]]
11		-Figure 1: Depiction of human and robot in our design patterns
	9	+Figure 1: ADD CAPTION HERE
12	12	===Type of work:===
13	13	The language model of van Diggelen et al. emphasises two important aspect of work, wether it is tangible or intangible work and how much it is related to the team goal. Below are the definition of both these concepts as they are explained in their paper [1].
14	14
...	...	@@ -21,16 +21,15 @@
21	21	* //Indirect work// is any type of work that aims at making the team more effective or efficient at achieving the team goal, but does not move the team closer to its goal. It is represented by the colour of either the object or the agent's head is pale red.
22	22	* //Off-task work// is any type of work that is unrelated to achieving the team goal and does not have the intention of improving team effectiveness. It is represented by the colour of either the object or the agent's head is dark grey.
23	23
24		-(% style="text-align:center" %)
25	25	[[image:directdp.png||width="400" height="350"]]
26		-Figure 2: Types of work and their depictions in design patterns
	23	+
27	27	===Scalability:===
28	28	The image below shows that both cognitive and physical work can be quantified.
29	29	Moreover, even though it is not shown on the image, a quantified amount of cognitive or physical work can still be contributing directly, indirectly to the team goal or even being off-task.
30	30
31		-(% style="text-align:center" %)
32	32	[[image:scalabledp.png||width="400" height="350"]]
33		-Figure 3: Tasks and their scalability in as seen in design patterns
	29	+
	30	+
34	34	===Type of communication:===
35	35	van Diggelen et al. propose three different level of communication:
36	36	* Supervision, it is represented by a dotted line between both agents and an arrow indicating who is supervising who. In the image below, the agent on the left supervises the agent on the right.
...	...	@@ -37,9 +37,8 @@
37	37	* Open communication channel, it it is represented by a dotted line between both agents.
38	38	* No communication, it is represented by the lack of dotted line between both agents.
39	39
40		-(% style="text-align:center" %)
41	41	[[image:comm2dp.png||width="400" height="350"]]
42		-Figure 4: Depiction of communication channels in design patterns
	38	+
43	43	==General Reminder Design Pattern==
44	44	**Overview**
45	45	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.
...	...	@@ -80,8 +80,6 @@
80	80	<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"/>
81	81	{{/html}}
82	82
83		-
84		-===References===
85	85	[1]: van Diggelen, J., & Johnson, M. (2019, September). Team design patterns. In Proceedings of the 7th International Conference on Human-Agent Interaction (pp. 118-126).
86	86
87	87