Requirements for the CRIOS v12 [January, 2020] After a preliminary analysis, it was found useful to add the following requisites to achieve the previous ones: Support for the online data collection of specific items. It will be usually as forms to be fulfilled by users, though more complex interfaces can be considered, either with users or other systems, according to identified needs during the project. Provide some means of dissemination of limited information for the general public. Support the analysis of past activities using the platform. Allow the incorporation and modification of functionality in the future according to the identified needs.
Requirements for the CRIOS v12 [January, 2020] An ARUP actor becomes an XXXX when she/he is granted by a platform administrator rights to manage an ARU after her/his request. These rights allow performing the following actions: Manage users. To accept/refuse users’ request to join/leave the managed ARU or its projects. The ARUP can also manually assign or unassign an ARUP to her/his ARU. Manage projects. To create a project, to close a project the user manages, so no further modifications can be done on it, or to reopen a closed project. My ARUs. This functionality extends the one with the same name for the ARUP by adding the possibility to view the ARUs the user manages.
Requirements for the CRIOS v12 [January, 2020] 6 Conclusions This document has presented the analysis of requirements for the CRIOS platform. It has reviewed the needs already identified for it and the tools that can be regarded as related to them, either as a source of features or as a basis for their implementation. With this, it has outlined initial functional requirements and constraints of CRIOS. Given that the is going to be developed simultaneously with the methodology to create TAISs that it must support, the main concern has been offering a suitable starting base functionality. This functionality should consider several aspects. First, support for collaborative work. Here, shared resources (mainly documents) have been identified as the most flexible option, and one with which most users are comfortable. Second, offering capabilities to support that work with analysis tools. The potential variety of tools take to consider initially as a baseline being able to launch or indicate how to do so from CRIOS. The actual value of these tools is the kind of analyses they can do. Thus, the focus of the development related to them is in creating the analysis techniques more than in providing a tight integration with other tools. This way also aligns with the actual work of experts. Third, providing guidance in the process according to the TAIS methodology. This will be done through integrated guidelines in resources and workflow maps that help users to understand the whole process and give them hints on procedures for specific tasks. The previous functionality is the starting point to support the TAIS methodology and develop the analysis techniques for it. As such, this specification of requirements will be reviewed after each round of pilots (M19, M25 and M30) to incorporate new findings as features for the tool.
