Skip to Content

Changes for page Functions

Last modified by Mathieu Jung-Muller on 2022/04/04 22:50
From version Icon 15.1 Icon
edited by Sneha Lodha
on 2022/04/04 20:42
Change comment: There is no comment for this version
To version Icon 11.1 Icon
edited by Haoran Wang
on 2022/03/18 20:36
Change comment: There is no comment for this version

Summary

Details

Icon Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.snehalodha
1 +XWiki.haoranwang
Content
... ... @@ -1,5 +1,4 @@
1 1  = Requirements =
2 -Below we define the requirements for certain action steps in detail. Along with this for each requirement you can see
3 3  
4 4  RQ001: Pepper has specific information about the PwD.
5 5  RQ002: Pepper knows the date and time.
... ... @@ -7,13 +7,9 @@
7 7  RQ004: Pepper has access to the calendar of PwD and knows the date and time.
8 8  RQ005: Pepper understands if the PwD is awake.
9 9  RQ006: Pepper knows the activity breakdown of the requested activity.
10 -RQ007: Pepper knows the appropriate medication for the time of the day.
11 -RQ008: Pepper has access to the PwD's calendar.
12 12  
13 13  = 1. Key features =
14 -
15 15  == 1.1. Feature: Medication reminder ==
16 -
17 17  === 1.1.1 Initial Situation ===
18 18  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.
19 19  
Icon XWiki.XWikiComments[0]
Author
... ... @@ -1,1 +1,0 @@
1 -Anonymous
Comment
... ... @@ -1,1 +1,0 @@
1 -I would not add another concept like "feature" to the design specification (use cases, requirements and claims. Try to include the "feature descriptions" in the requirements description. Not that playing appropriate music in the first 4 use cases is a very relevant requirement...
Date
... ... @@ -1,1 +1,0 @@
1 -2022-03-20 16:48:38.855