User-centered requirements engineering to manage the fuzzy front-end of open innovation in e-health: A study on support systems for seniors' physical activity.

BACKGROUND

Although e-health potentials for improving health systems in their safety, quality and efficiency has been acknowledged, a large gap between the postulated and empirically demonstrated benefits of e-health technologies has been ascertained. E-health development has classically been technology-driven, often resulting in the design of devices and applications that ignore the complexity of the real-world setting, thus leading to slow diffusion of innovations to care. Therefore, e-health innovation needs to consider the mentioned complexity already from the start. The early phases of innovation, fuzzy front-end (FFE) defined as "the period between when an opportunity is first considered and when an idea is judged ready for development" has been identified to have the highest impact on the innovation process and its outcome. The FFE has been recognized as the most difficult stage to manage in the innovation process as it involves a high degree of uncertainty. Such a phase becomes even more difficult when different sectors and organizations are involved. Therefore, effective methods for involving different organizations and user groups in the FFE of innovation are needed.

OBJECTIVE

The aim of this study was to manage the FFE of a collaborative, open innovation (OI) process, to define a software system supporting seniors' physical activity (PA) by applying a framework of methods from software requirements engineering (RE) to elicit and analyze needs and requirements of users and stakeholders, as well as the context in which the system should be used.

METHODS

Needs and requirements of three future user groups were explored through individual- and focus group interviews. Requirements were categorized and analyzed in a workshop with a multidisciplinary team: a system overview was produced by conceptual modelling using elicited functional requirements; high-level non-functional requirements were negotiated and prioritized. Scenario descriptions of system's supportive roles in different phases of a behavioral change process were developed.

RESULTS

User-centered RE methods were successfully used to define a system and a high-level requirements description was developed based on needs and requirements from three identified user groups. The system aimed to support seniors' motivation for PA and contained four complementary sub-systems. The outcome of the study was a Concept of Operations (ConOps) document that specified the high-level system requirements in a way that was understandable for stakeholders. This document was used both to identify and recruit suitable industrial partners for the following open innovation development and to facilitate communication and collaboration in the innovation process.

CONCLUSIONS

Applying software RE methods and involving user groups in the early phases of OI can contribute to the development of new concepts that meet complex real-world requirements. Different user groups can complement each other in conveying needs and requirements from which systems can be designed. Empirical studies applying and exploring different methods used to define new e-health solutions can contribute with valuable knowledge about handling innovation FFE.