Publications and deliverables

Deliverable 2.1


Requirements analysis report

Due date:


Executive summary:

The aim of this document is to define the requirements on a system that collects and integrates user feedback data into existing integration solutions for building automation systems. This includes the definition of scenarios and use cases as well as a comprehensive state-of-the-art analysis and technology survey.

First, state-of-the-art and technologies in the areas of user feedback capturing, user feedback modelling, building automation integration, comfort perception modelling, knowledge engineering, and psychological aspects are investigated and summarized. In addition, related national and European research projects are studied.

An integral characteristic of the systems developed in HumBAS is the collection of sensitive data which is directly related to occupants of the building. Hence, considering privacy and security aspects is of utmost importance. Regarding privacy, state-of-the-art as well as available guidelines are explored. Based on the results of this study, privacy engineering goals for the HumBAS system are defined. In terms of security, requirements and solutions to enable secure collection, transmission, and storage of user-feedback data as well as user-sensitive sensor data are identified and outlined.

In order to define use cases, scenarios are elaborated. In an initial step, a contextual analysis is performed based on literature review and informal interviews. The results are a selection of important comfort parameters and the definition of representative personas. The gained insights are used to identify typical situations involving human perceptions in office buildings and to formulate them as so-called As-Is scenarios. The focus of the selected scenarios is on situations where potentially conflicting human perceptions of multiple persons have to be taken into account. This is especially the case in offices occupied by two or more persons. Afterwards, the Should-Be scenarios are defined. For this purpose, the As-Is scenarios are analyzed and shortcomings leading to discomfort among occupants of the building are identified. Based on this analysis, the Should-Be scenarios are defined in a way such that the occurrence of the detected issues as well as dissatisfaction of users is minimized.

In the next step, the Should-Be scenarios are subdivided into various use cases which are specified in detail. Involved (sub-)systems and actors as well as dependencies between use cases are identified and also visualized by means of use case diagrams. While the scenarios and therefore also the derived use cases are described from the view of building users, a second set of use cases specifying the interaction between facility management and the involved systems is defined.

Finally, the use cases are used to derive functional as well as non-functional requirements on the HumBAS system.