Changes for page Functions

Last modified by Mathieu Jung-Muller on 2022/04/04 22:50

From 14.1 to 15.1 From 18.1 to 19.1

From version

15.1

edited by Sneha Lodha
on 2022/04/04 20:42

Change comment: There is no comment for this version

To version

18.1

edited by Sneha Lodha
on 2022/04/04 21:47

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,57 +1,115 @@
  = Requirements =
--Below we define the requirements for certain action steps in detail. Along with this for each requirement you can see
++Below we define the requirements for certain action steps in detail. Along with this for each requirement you can see the feature descriptions in detail. These requirements are utilized in use cases, hence each one can be seen in context under that section.
--RQ001: Pepper has specific information about the PwD.
--RQ002: Pepper knows the date and time.
--RQ003: Pepper understands the response from PwD.
--RQ004: Pepper has access to the calendar of PwD and knows the date and time.
--RQ005: Pepper understands if the PwD is awake.
--RQ006: Pepper knows the activity breakdown of the requested activity.
--RQ007: Pepper knows the appropriate medication for the time of the day.
--RQ008: Pepper has access to the PwD's calendar.
++{{html}}
++<table>
++    <tr>
++        <td>No.</td>
++        <td>REQUIREMENTS</td>
++    </tr>
++    <tr>
++        <td>RQ001</td>
++        <td><b>Pepper knows the stage of dementia of PwD in order to ask questions in appropriate format.</b></td>
++    </tr>
++    <tr>
++        <td></td>
++        <td>This requirement comes directly from HCP, or is either pre-programmed into Pepper before hand. It ensures that Pepper asks questions in such a way that depending on the stage of dementia of the PwD, they are able to understand it. In order to fulfill this requirement Pepper needs a functioning speaker that can output speech.</td>
++    </tr>
++    <tr>
++        <td>RQ002</td>
++        <td><b>Pepper knows the date and time.</b></td>
++    </tr>
++    <tr>
++        <td></td>
++        <td>This requirement deals with knowing the appropriate time of the day. It comes in handy when dealing with reminder tasks, and is utilized to know when certain reminders should be activated during the day.</td>
++    </tr>
++    <tr>
++        <td>RQ003</td>
++        <td><b>Pepper understands the response from PwD.</b></td>
++    </tr>
++    <tr>
++        <td></td>
++        <td>After having asked something, it is crucial that Pepper is able to understand what the PwD just said. Moving on to the next action step would require Pepper to do this, otherwise it would be stuck in a loop of "I did not understand." </td>
++    </tr>
++    <tr>
++        <td>RQ005</td>
++        <td><b>Pepper understands if the PwD is awake.</b></td>
++    </tr>
++    <tr>
++        <td></td>
++        <td>This is a specific requirement that occurs during the wake up routine use case. Here understanding whether the PwD is awake is important for the alarm/musical setting. If the PwD is not awake, the volume of the music is increased to ensure they are awake.</td>
++    </tr>
++    <tr>
++        <td>RQ006</td>
++        <td><b>Pepper knows the activity breakdown of the requested activity.</b></td>
++    </tr>
++    <tr>
++        <td></td>
++        <td>This is a crucial requirement before performing the activity breakdown use case. If the activity breakdown is not given, the functionality can not be used. Here an HPC, or a caregiver inputs the breakdown steps of the activity beforehand to ensure it can be executed at a late time. </td>
++    </tr>
++    <tr>
++        <td>RQ007</td>
++        <td><b>Pepper knows the appropriate medication for the time of the day.</b></td>
++    </tr>
++    <tr>
++        <td></td>
++        <td>When reminding the PwD about their medication, it is also important for Pepper to know (pre-programmed or entered by HCP) which medication is correct for that time of day.</td>
++    </tr>
++    <tr>
++        <td>RQ008</td>
++        <td><b>Pepper has access to the PwD's calendar.</b></td>
++    </tr>
++    <tr>
++        <td></td>
++        <td>This requirement deals with reminding the PwD about an upcoming calendar event. Pepper should have access to such a calendar, or the HCP can also enter this prior to the event reminders.</td>
++    </tr>
--= 1. Key features =
++</table>
++{{/html}}
--== 1.1. Feature: Medication reminder ==
--=== 1.1.1 Initial Situation ===
++=Key Use Case Functionality=
++
++==Medication reminder==
++
++===Initial Situation===
  At a preset time each day, Pepper plays preselected music and engages with the PwD, and asks him/her to take their medicine. Pepper will continue to ask the PwD to take their medication until he/she does.
--=== 1.1.2 Patients response ===
++===Patients response===
  Two cases are possible. First, the patient has either already taken their medicine and would tell Pepper so. Otherwise, the patient will be reminded to take their medicine until the PwD does so. Playing music before reminding the PwD about their medication will help the patients to build up a routine and makes the experience more enjoyable.
--== 1.2. Feature: Meal reminder ==
++==Meal reminder==
--=== 1.2.1 Initial Situation ===
++===Initial Situation===
  At a preset time each day, Pepper plays preselected music and engages with the PwD, and asks him/her to eat. Pepper will continue to ask the PwD to eat until he/she does.
--=== 1.2.2 Patients response ===
++===Patients response===
  Two cases are possible. First, the patient has either already eaten and would tell Pepper so. Otherwise, the patient will be reminded to eat until the PwD does so. Playing music before reminding the PwD about their meal will help the patients to build up a routine and makes the experience more enjoyable.
--== 1.3. Feature: Calendar Event reminder ==
++==Calendar Event reminder==
--=== 1.3.1 Initial Situation ===
++===Initial Situation===
  Sometime before an upcoming event in which the PwD is invited, Pepper will play some music and remind the PwD to prepare for it. Pepper will then ask the PwD how they feel about the event and wish them to enjoy it.
--=== 1.3.2 Patients response ===
++===Patients response===
  As the patient is reminded about their event it will prevent the PwD to forget about it and miss it. Moreover, talking to Pepper about the upcoming event could both calm them and make them apprehend the event more peacefully.
--== 1.4. Feature: Wake up Routine ==
++==Wake up Routine==
--=== 1.4.1 Initial Situation ===
++===Initial Situation===
  At a preset time each day, Pepper plays preselected music and increases the volume slowly to wake up the patient as smoothly as possible and engages with the PwD and asks him/her to eat. Pepper will continue to ask the PwD to eat until he/she does.
--=== 1.4.2 Patients response ===
++===Patients response===
  The patient will wake up peacefully and will be supported in his/her first daily activities. The two mains advantages to these features are:
  * Slowly waking up the PwD will calm the patient and will make him/her feel supported by its environment.
  * Helping the PwD in setting up a routine will increase his/her quality of life and reduce the workload of the caretakers
--== 1.5. Feature: Activity Breakdown ==
++==Activity Breakdown ==
--=== 1.5.1 Initial Situation ===
++===Initial Situation===
  When there's a preset activity comes, Pepper would play some music first to get attention, and then ask the patient whether they want to do the activity or not. If the patient says no, Pepper would stop the activity. If the patient says yes, Pepper would start the activity with small steps.
--=== 1.2.2 Patients response ===
++===Patients response===
  The patient would start to follow the steps. After every step, Pepper would ask the patient if he/she catches up. If yes, Pepper will move to the next step. If not, the patient can choose to redo the last step or stop the activity.