Changes for page Robotic Partner

Last modified by Andrei Stefan on 2022/04/04 12:11

From 3.1 to 2.1 From 6.3 to 6.2

From version

6.2

edited by Andrei Stefan
on 2022/02/15 11:55

Change comment: There is no comment for this version

To version

3.1

edited by Andrei Stefan
on 2022/02/15 11:43

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -1,14 +5,9 @@
--====Choice of robotic partner====
--
--We want the robots to be able to interact with the users through more than just music, so robots such as Pepper, who has an in-built display or NAO, who can interact with a tablet, are considered more suitable than Miro. Furthermore, it might feel unnatural to hear an animal-shaped robot play music rather than animal sounds. A smaller robot, such as NAO, is more suitable when users live (more or less) independently, as it can be moved where it needs to be, does not take up a lot of space, and is also easier to take on walks. Furthermore, if the user regularly wisits care homes, they can take the robot with them without too much trouble.
--
  ===Goals===
--The goals of the robotic partner are strongly correlated with the Problem Scenarios and the Use Cases.
++====Routines====
--==== Daily routines====
++The main goal of the robotic partner is to help users maintain their daily routines. Towards this end, the robot should be able to display a list of tasks and should also help the users remember to do them. Therefore, robots such as Pepper, who has an in-built display or NAO, who can interact with a tablet, are considered more suitable than Miro.
--The main goal of the robotic partner is to help users maintain their daily routines. Towards this end, the robot should be able to display a list of tasks and should also help the users remember to do them. Therefore, the robot should have access to a tablet which can show the list when needed.
  ====Reducing memory deterioration====