RESILIENCE as a European cross-disciplinary research infrastructure for research on religion in all academic fields prioritises its future users and their needs. WP3 aims to survey the user requirements as comprehensively as possible, so that the research infrastructure (RI) will be able to offer those services that are requested or envisioned by the community. WP3 is tasked with organising workshops in cooperation with WP4 (Communication, Dissemination and Exploitation) in which the RI and its possibilities are presented to the focus groups. WP2 has also collaborated on this task from the outset, as the collection of user requirements (WP3) and the strategic planning and the preparation of the services (WP2) must be closely coordinated. The aim of these workshops is to find out the requirements of the users in detail, to understand the needs of the future end users, to find out what their priorities are, to align the development of the services accordingly and to map existing services. From the basis of the first batch of workshops and user stories collected from these (see D3.1 and D3.5), it is the additional task of the WP to refine the eight archetype users’ profiles that have been already presented in the RESILIENCE User Strategy.1 Based on a list of prioritised services (see T3.1), the intention is that the users lay the foundation for the use cases by presenting their perspective and requirements for each service in the interviews. At a later stage, this input is to be prototyped and presented back to the end-users for User Interface/User experience validation sessions whenever a new service goes in development.This deliverable presents the foundations for these further developments in three chapters. First, the evolution of the archetypes is presented and the decisions that led to the redefinition are explained. In a second step, the use cases based on the user stories will be showcased. In this chapter, the use case template will be presented and applied to three use cases for three future services providing “Data access: discoverability of data sources” that answers the user need for “Accessibility” (3.3.1-3.3.3), one use case for an existing service (TNA) will be presented that addresses the need for “Networking” (3.3.4), one for “Research Data Management” (3.3.5) and another one for the future service ”Help Desk” that fulfils the need for “Scientific support/Empowerment” (3.3.6). Finally, S.M.A.R.T objectives are formulated in relation to the user/functional requirements, that will then represent the future work focus.
Nusser et al. (Mon,) studied this question.