Skip to Content

Wiki source code of Functions

Version 20.1 by Rembrandt Oltmans on 2022/03/30 11:03
Show last authors
1 == Requirements ==
2
3 The requirements together aim to enable the robot to successfully complete all tasks set out in the use cases from the original design.
4 We identified two main use cases the robot should be able to perform, which we will work out in more detail. These 2 use cases are the //Daily todo list//: UC001 and the //Quiz//: UC005 which have some dependencies which are also added.
5 The requirements are as follows:
6
7 === Main Use cases ===
8
9 **RQ001: Robot has the ability to play sounds**
10 Function description: It is critical for the functionality of the system that the robot is able to play specific songs at certain times. In order to achieve this the robot should be able to play sounds at an audible volume in the room and the Choregraphe Studio program should allow for picking and streaming songs to the NAO. This can be seen as one of the most important requirements as without it the system can not execute it's core functions.
11
12 **RQ002: The robot can recognize affirmative words/ detect hand gestures**
13 Function description: In order to know when the patient has completed a task, or the patient wants to stop the music as he knows the task to perform, the robot should be able to recognize an indication of being done. This indication can be given in various ways, one of those is through speech which depends on RQ009. However, other indications can be used to denote being finished such as detecting a hand signal from the patient or visually recognizing the completion of the current activity.
14
15 **RQ004: Have some way of modifying the TODO list and the music associated with the tasks**
16 Function description: Not directedly related to the main use cases, the requirement for being able to modify the music and schedule is still vital for the functionality of the system. If the data is not able to be created or modified then no personalized music can be played at certain times during the day. Thus making the system useless and making it a vital requirement for enabling the core functions of the system. The creation of the patients schedule and the association of certain personalized music can by done by the caregiver or loved ones and easily edited through a web portal.
17
18 **RQ009: Robot should recognize spoken words**
19 Function description: In order for the patient to communicate, about what activity is linked to current piece of music during the quiz, the robot should be able to processes spoken language. Furthermore the programming of the robot should be able to processes this information and activate the correct response regarding to the input. This requirement is vital for the patient to be able to effectively play the quiz with the robot. The voice recognition can also be used by the patient to ask to play the quiz or to deny the robot when it proposes to play the quiz.
20
21 === Other requirements ===
22
23 **RQ003: Have the means of contacting loved ones and caregiver**
24 Function description: The robot also facilitates the communication between the patient to the loved ones and care givers. This can be done in emergency situations where the patient is unresponsive such as in UC006 or can be done when the patients needs non-emergency assistance with certain robot features such as in use case 2. The communication can be as easy as a text message sent by the robot or an emergency call.
25
26 **RQ005: Robot has the ability to perform simple movements**
27 Function description: The ability to perform movements is necessary for the exercise use case UC003. However, simple hand movements while talking and head tracking movements can help communicate more naturally with the patient. Luckily these features are natively supported by the NAO and Choreography system.
28
29 **RQ006: Robot has the ability to save the data and upload it to cloud**
30 Function description: Having a robot that is able to monitor the patient when caregivers are not around enables the collection of interesting and important health data that can help with the further treatment of the patient. Therefore having the ability to upload this data to the cloud where it can be used in combination with an analysis platform could proof useful. However, this should be optional is not a core functionality of the system.
31
32 **RQ007: Robot has games and rules stored in memory and is able to recognize the players**
33 Function description: In order to utilise the sensors and presence of the robot fully, in combination with building a better bond with the patient, games should be able to be played with the patient and other players. This also keeps the patient more socially active. This however is again an extra feature of the system.
34
35 **RQ008: Robot can monitor an ongoing game**
36 Function description: This functionality links to the previous requirement RQ007 and is necessary to perform a successful interactive game.
37
38 **RQ010: Robot should recognize when the patient suddenly stops interacting**
39 Function description: Giving the robot the ability to detect a sudden stop in interaction with the patient can keep the patient safe from serious harm by contacting the care giver or loved ones.
40
41 **RQ011: Have the means of transmitting live audio and video**
42 Function description: In response to the detection of sudden loss of interaction in RQ010 the robot will need to be able to inform help, therefore the function of transmitting live video and audio is necessary as it enables the helper to see if there is a acute need for help.
43
44 **RQ012: Robot can remember the context of the emergency call**
45 Function description: To prevent false detections in RQ010 the robot will adapt its detection when the care giver or loved one detects it is false alarm in RQ011. This prevents the robots' warnings to be ignored when there is a real emergency.