Framework-related Requirements
5.1 Framework-related Requirements
The framework related requirements define different requirements on the adaptive data acquisition framework. In the following, we briefly discuss whether they are covered and if so, were the associated discussion can be found.
ID AA_001
Description
The data acquisition framework shall allow multimodal data acquisition.
Type
Functional and data requirements
Priority
High
AA_001: This requirement has been covered in Section 2.1. As the data acquisition framework is required to capture different sorts of context data, it will use different sensors available on the mobile phone e.g. microphone, accelerometer, gyroscope, GPS, Wi-Fi etc to do it.
ID AA_002
Description
The data acquisition framework shall be extensible.
Type
Functional and data requirements
Priority
High
AA_002: This requirement has been covered in Section 2.1. The design description for the data acquisition framework given in previous sections ensures that the framework is extensible with regard to addition of new components, configurations, applications etc.
ID AA_003
Description
The data acquisition framework shall allow automated acquisition of context data.
Type
Functional and data requirements
Priority
High
AA_003: This requirement has been covered in Section 2.2. The adaptive data acquisition framework ensures this requirement through the use of activation system. The activation system enables automatic execution of context recognition configuration without any input from the user.
ID AA_012
Description
The data acquisition framework shall allow optimization of context recognition components by allowing configurable parameters.
Type
Functional and data requirements
Priority
High
AA_012: This requirement has been covered in Section 2.1.1.1.1. The component model described above allows developer to add/update parameters in the components to optimize their use.
ID AA_004
Description
The data acquisition framework shall be lightweight.
Type
Performance requirements
Priority
Medium
AA_004: This requirement has been covered in Section 2. The entire data acquisition framework is meant to be executed on constrained computer systems such as mobile phones. Therefore, the design for the framework (component system and activation system) presented in the above sections has been created with a very high consideration to this requirement.
ID AA_007
Description
The data acquisition framework shall enable energy efficient context recognition for several applications.
Type
Performance requirements
Priority
Medium
AA_007: This requirement has been covered in Section 2.1.2. The component system and the activation system applies configuration folding on simultaneously executed configurations such that there is a single folded configuration for all with minimized occurrences of redundant computations.
ID AA_009
Description
The data acquisition framework shall provide a control interface to the privacy framework.
Type
Functional and data requirements
Priority
High
AA_009: This requirement has been covered in Section 4.2. A control interface is need for the two frameworks to ensure that the user’s context data exported to the service providers is according to
the privacy policy of the user. A more elaborate description will be provided with version 2 of this document.
ID AA_026
Description
The data acquisition framework should provide an API to discover the types of data that are used to derive other data.
Type
Functional and data requirements
Priority
High
AA_026: This requirement has been covered in Section 4.1. A control interface is need for the two frameworks to ensure that the user’s context data is categorized appropriately with associated
metadata when exported to the SDS. A more elaborate description will be provided with version 2 of this document.
ID AA_025
Description
The data acquisition framework must be able to support the acquisition of public transport co-use.
Type
Functional and data requirements
Priority
High
AA_025: This requirement has been covered in Section 3.2. Using the trip recognition, duration prediction and destination prediction components the data acquisition system will be able to provide co-use of public transport by friends or colleagues.
ID AA_005
Description
The data acquisition framework shall be able to classify audio data.
Type
Functional and data requirements
Priority
High
AA_005: This requirement has been covered in Section 3.3 and 3.4. The component system provides speech and sound recognition components for detecting ambient sounds, announcements, discussions, etc. Moreover, with these components the user can speak his preferences to the system instead of typing.