Skip to Content
Last modified by Palina Yarmolenka on 2025/04/24 18:38
From version 10.1
edited by Ioana Raducanu
on 2025/04/04 13:51
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
... ... @@ -4,3 +4,40 @@
4 4  )))
5 5  
6 6  Please give feedback on this as we are unsure what TDPs to describe, or if it applies to our idea
7 +
8 +
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|
13 +|Solution Description|(((
14 +All actors (humanoid robot, patient) are **co-located**. The schedule-making is not part of this Team Design Pattern.
15 +
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 +)))
24 +|Human RQ|(((
25 +* Patient: Communicate willingness to proceed with the interaction.
26 +)))
27 +|Machine RQ|(((
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]]
32 +)))
33 +|Consequences|(((
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.
35 +
36 +**~ -** The schedule display is limited in seeing mistakes and making corrections, possibly leading to the miscommunication of actual tasks happening.
37 +)))
38 +|Grounding|(((
39 +Status: Proto Pattern.
40 +
41 +Instantiations: [[UC01: Displaying the Schedule>>doc:2\. Specification.b\. Use Cases.UC01\.1\: Schedule Update.WebHome]].
42 +)))
43 +|Related Patterns|[[IDP>>doc:2\. Specification.Claims.WebHome]]