Skip to Content
Last modified by Palina Yarmolenka on 2025/04/24 18:38
From version 11.1
edited by Ioana Raducanu
on 2025/04/04 13:52
Change comment: There is no comment for this version
To version 12.1
edited by Ioana Raducanu
on 2025/04/04 14:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -6,39 +6,38 @@
6 6  Please give feedback on this as we are unsure what TDPs to describe, or if it applies to our idea
7 7  
8 8  
9 -|(% colspan="1" %)Problem|The [[Activity Coordinator>>doc:Main.sdf.Stakeholders.Activity Coordinator.WebHome]] and [[Humanoid Robot>>doc:Main.c\. Technology.Humanoid Robot.WebHome]] have to manage the interactive game play and emerging social behaviors of a group of vulnerable game participants such as [[Person with Dementia>>doc:Main.sdf.Stakeholders.Person with Dementia.WebHome]]. The allocation of tasks should be harmonized to the momentary capacities of the coordinator and robot, the varying needs of the players, and to the context. Pausing the game is part of the game management, as a mitigation strategy for prevention and handling of troubles that appear during the game play.
10 -|Solution Structure|[[image:129826985.png||height="231" width="539"]]
9 +|(% colspan="1" %)Problem|(((
10 +The  [[Humanoid Robot>>doc:Main.c\. Technology.Humanoid Robot.WebHome]] has to process basic decision-making within the interaction of a [[Person with Dementia>>doc:Main.sdf.Stakeholders.Person with Dementia.WebHome]] and possibly display the appropriate schedule. The schedule is upkept by the patient themselves as well as the [[Nurses/ Caregiver Personnel>>doc:Main.sdf.Stakeholders.Activity Coordinator.WebHome]] (for scheduled health services) before any display interaction. Stopping the interaction preemptively is part of the display functionality as a strategy to give more independence to the patients.
11 +)))
12 +|Solution Structure|
11 11  |Solution Description|(((
12 -All actors (activity coordinator, humanoid robot, players) are **co-located**.
14 +All actors (humanoid robot, patient) are **co-located**. The schedule-making is not part of this Team Design Pattern.
13 13  
14 -1. Robot leads the game (i.e., is the game master, GM).
15 -1. Vulnerable game participants play the game (i.e., are the players, PL).
16 -1. Robot reflects on game play.
17 -1. Activity coordinator (CO) supervises players' state and engagement;
18 -11. if (s)he identifies risks for troubles to appear, the coordinator initiates a takeover from scene A (Active) to B (Pause).
19 -11. if (s)he recognizes that the risk for troubles disappeared, the coordinator initiates a takeover (from scene B to A)
20 -1. Activity coordinator starts and leads a social activity,
21 -1. Players socialize under the guidance of the activity coordinator.
22 -1. Robot engages in small talk.
16 +1. PwD initiates interaction
17 +1. Robot gives an option for further interaction, and schedule display.
18 +1. PwD makes a decision on will to engage;
19 +11. if they do not want to engage, the Robot reacts without judgement and moves from the current position in the scene, back to the original state (restart Scene A: Displaying the Schedule)
20 +1. Robot displays the appropriate schedule and walks PwD through it.
21 +1. Robot initiates scene B if pre-requisites for the scene are met (see [[Scene B: Adding extra activities with PwD>>doc:2\. Specification.Requirements.TDP02\.0\: Suggest Group Activities.WebHome]]);
22 +11. if the pre-requisites are not met the scene is restarted from the beginning (restart Scene A: Displaying the Schedule).
23 23  )))
24 24  |Human RQ|(((
25 -* Player:  Show perceptual and cognitive capabilities to play the game.
26 -* Coordinator: Know the vulnerabilities of the players (memory). Show perceptual and cognitive skills to identify and mitigate risks for troubles in the game play.
25 +* Patient: Communicate willingness to proceed with the interaction.
27 27  )))
28 28  |Machine RQ|(((
29 -* [[RQ01.0: Lead the bingo game>>doc:2\. Specification.Requirements.RQ01\.0\: Lead the bingo game.WebHome]]
30 -* [[RQ02.0: Personalize game assignments>>doc:2\. Specification.Requirements.RQ02.WebHome]]
31 -* [[RQ03.0: Reflect on game performance>>doc:2\. Specification.Requirements.RQ03\.0\: Reflect on game performance.WebHome]]
32 -* [[RQ04.0: Respond to players conversations.>>doc:2\. Specification.Requirements.RQ04\.0\: Respond to players conversations\..WebHome]]
28 +* [[RQ01.0: Personalise engagement based on willingness (stop/start)>>doc:2\. Specification.Requirements.RQ01\.0\: Lead the bingo game.WebHome]]
29 +* [[RQ02.0: Show the PwD's scedule>>doc:2\. Specification.Requirements.RQ02.WebHome]]
30 +* [[RQ03.0: Clearly communicate the scedule verbally>>doc:2\. Specification.Requirements.RQ03\.0\: Reflect on game performance.WebHome]]
31 +* [[RQ04.0: Switch between functions (scenes)>>doc:2\. Specification.Requirements.RQ04\.0\: Respond to players conversations\..WebHome]]
33 33  )))
34 34  |Consequences|(((
35 -**+** Offload of coordinator so that (s)he can concentrate on advancing players individual and social experiences.
34 +**+** Offload of Nurse/ Caregiver Personnel repetitive interaction of reminding patients of their schedule so that (s)he can concentrate on other aspects of their jobs.
36 36  
37 -**~ -** The game play may be constrained by robot's limitations to sense and understand players' game experience
36 +**~ -** The schedule display is limited in seeing mistakes and making corrections, possibly leading to the miscommunication of actual tasks happening.
38 38  )))
39 39  |Grounding|(((
40 40  Status: Proto Pattern.
41 41  
42 -Instantiations: [[UC01.0: Music Bingo>>doc:2\. Specification.b\. Use Cases.UC01\.0\: Music Bingo.WebHome]].
41 +Instantiations: [[UC01: Displaying the Schedule>>doc:2\. Specification.b\. Use Cases.UC01\.1\: Schedule Update.WebHome]].
43 43  )))
44 -|Related Patterns|[[IDP: Title>>doc:Design Patterns.Interaction Design Patterns.IDP\: Title.WebHome]]
43 +|Related Patterns|[[IDP>>doc:2\. Specification.Claims.WebHome]]