Research projects in the security domain often aim to develop innovative technology-based solutions for end users (e.g., situational awareness tools, crisis management tools). The pandemic crisis hit hard and without warning, not only influencing our everyday life but also the scientific community. To continue applied research projects during a pandemic, work structures needed to be adapted (e.g., user requirements collection, use case development), as face-to-face events were impossible but crucial to collect high quality requirements with a variety of different stakeholders. To ensure continued multi-stakeholder engagement we developed an overarching framework for collecting user requirements and use cases in an online setting and applied the framework within two research projects. The framework consists of four steps with the aim to assure high quality user requirements and use case collection (first analysis, stakeholder consultation, evaluation and prioritization, technical evaluation). The two projects presented in this paper provide insight on the potential of the framework. The framework offers a structured approach that fits for many different security research projects in terms of the easy application and its transferability. The main advantages (e.g., easily adaptable, reduced workshop time, no need to travel, suitability for different contexts and project types, etc.) and drawbacks (e.g., organization of online events, feedback collection time, etc.) of the framework are presented and discussed in this paper to offer increased stakeholder engagement. Empirical testing of the framework is proposed.

Since 2012, several national and international projects on ambient assisted living (AAL) active and healthy ageing gave insight into the different steps of development processes where the requirements of the target group were not met or just failed to be realized. This article shall provide a summary of terms and requirements from the experience of practice and project work on the topic. This article is a reflection and guide for self-criticism for technical developers. Starting with some terms and how they are linked to each other gives an overview of the field of action for the projects, which our experience is based on. A mixture between literature and results of projects illustrates the requirement analysis as it was anticipated in recent years. The conclusion consists of recommendations for further research on requirements.