Wiki source code of Functions
Version 15.1 by Rembrandt Oltmans on 2022/03/29 15:54
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
8.1 | 1 | == Requirements == |
| |
9.1 | 2 | The requirements together aim to enable the robot to successfully complete all tasks set out in the use cases from the original design. |
| |
12.1 | 3 | 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. |
| |
10.1 | 4 | The requirements are as follows: |
| |
3.1 | 5 | |
| |
11.1 | 6 | === Main Use cases === |
| |
14.1 | 7 | **RQ001: Robot has the ability to play sounds** |
| |
15.1 | 8 | 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. |
| |
12.1 | 9 | |
| |
14.1 | 10 | **RQ002: Robot should recognize an indication of being done** |
| |
15.1 | 11 | 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. |
| |
12.1 | 12 | |
| |
14.1 | 13 | **RQ004: Have some way of modifying the todo list and the music associated with the tasks** |
| |
12.1 | 14 | Function description: |
| 15 | |||
| |
14.1 | 16 | **RQ009: Robot should recognize spoken words** |
| |
12.1 | 17 | Function description: |
| |
10.1 | 18 | |
| 19 | === Other requirements === | ||
| |
14.1 | 20 | **RQ003: Have the means of contacting loved ones and caregiver** |
| |
13.1 | 21 | Function description: |
| 22 | |||
| |
14.1 | 23 | **RQ005: Robot has the ability to perform simple movements** |
| |
13.1 | 24 | Function description: |
| 25 | |||
| |
14.1 | 26 | **RQ006: Robot has the ability to save the data and upload it to cloud** |
| |
13.1 | 27 | Function description: |
| 28 | |||
| |
14.1 | 29 | **RQ007: Robot has games and rules stored in memory and is able to recognize the players** |
| |
13.1 | 30 | Function description: |
| 31 | |||
| |
14.1 | 32 | **RQ008: Robot can monitor an ongoing game** |
| |
13.1 | 33 | Function description: |
| 34 | |||
| |
14.1 | 35 | **RQ010: Robot should recognize when the patient suddenly stops interacting** |
| |
13.1 | 36 | Function description: |
| 37 | |||
| |
14.1 | 38 | **RQ011: Have the means of transmitting live audio and video** |
| |
13.1 | 39 | Function description: |
| 40 | |||
| |
14.1 | 41 | **RQ012: Robot can remember the context of the emergency call** |
| |
13.1 | 42 | Function description: |
| 43 |