Data-related Requirements
5.3 Data-related Requirements
The data-related requirements define different requirements on the adaptive data acquisition framework from a data acquisition perspective. In the following, we briefly discuss whether they are covered and if so, were the associated discussion can be found.
ID AA_014
Description
The activity recognition components must be able to capture the past user locations in an energy-efficient manner.
Type
Functional and data requirements
Priority
High
AA_014: This requirement has been covered in Section 3.1.1. The locations which a user visits are captured using the Wi-Fi fingerprints and if needed using the GSM or GPS. The capturing of finger prints is done stage wise e.g. it is activated only when other sensors such as accelerometer indicates movement of any kind. Moreover, the processing for the captured location is only done when the device is being charged.
ID AA_016
Description
The localization performed by the activity recognition components should not expose the user's location to untrusted third parties.
Type
Usability and humanity requirements
Priority
High
AA_016: This requirement has been covered in S ection 4.2. User’s location data is only exposed to the third parties or service providers if and only if the privacy policy of the user allows that. A more elaborate description will be provided with version 2 of this document.
ID AA_017
Description
The activity recognition components must be able to capture the mode of locomotion.
Type
Functional and data requirements
Priority
High
AA_017: This requirement has been covered in Section 3.1.2. As mentioned that multistage classifiers will be developed using the accelerometer, Wi-Fi, GSM, GPS data to identify the mode of locomotion used by the user.
ID AA_023
Description
The intent recognition component must record context histories in a storage-efficient manner.
Type
Functional and data requirements
Priority
High
AA_023: This requirement has been covered in Section 3.2.1 and 3.2.2. The history about the locations visited by the user is stored locally on the device. The data is stored in a processed and compressed form to ensure the efficient storage.
ID AA_015
Description
The intent recognition components are able to predict the next location of a user.
Type
Functional and data requirements
Priority
High
AA_015: This requirement has been covered in Section 3.2.2. The location prediction component allows service providers to know the next location of the user so that they can provide timely and relevant services to him.
ID AA_018
Description
The intent recognition components are able to predict the stay duration of the user.
Type
Functional and data requirements
Priority
High
AA_018: This requirement has been covered in Section 3.2.1. The duration prediction component allows service providers to know how long the user will stay at the current location so that they can provide timely and relevant services to him.
ID AA_020
Description
The sound recognition components shall enable the classification of different environmental sounds.
Type
Functional and data requirements
Priority
High
AA_018: This requirement has been covered in Section 3.3. The classification of environmental sounds assist in identifying the location of the user and announcements made on loud speakers. Moreover, the classification of sound can also help to estimate the level of noise pollution in the environment.
ID AA_021
Description
The speech recognition components support server-less operation with a limited vocabulary.
Type
Functional and data requirements
Priority
High
AA_021: This requirement has been covered in Section 3.4. In order to support the privacy preserving operations, the sound and speech processing is also done on the device. Since mobile AA_021: This requirement has been covered in Section 3.4. In order to support the privacy preserving operations, the sound and speech processing is also done on the device. Since mobile