AURORA D2.1 - Requirements Document

The present document is the Requirements Document (RD) of the AURORA project (deliverable [D2.1]). It contains the contributions from all partners arranged in sections and subsections according to the AURORA template. The responsible for this delivery is Ugo Cortesi (IFAC), in charge of the coordination of WP2. All partners are involved in the requirements definition, on the basis of their specific competences and expertise and of their role in the project. The RD is intended to specify the scientific and technical requirements for all the tools, procedures and products developed or provided within the project. The RD has the twofold purpose of setting the basis for most of the subsequent WPs of the work plan and of providing reference terms for quality assessment and validation activities. An important premise is, therefore, necessary, in order to point out that on one side the first release of the RD has to cover all specifications and requirements requested to proceed with development of tools, procedures and products of AURORA based on the information available at the present stage about the Sentinel 4 (S4), Sentinel 5 (S5) and Sentinel 5 Precursor (S5P) missions. On the other hand, the commitment taken by the project to develop the AURORA system on the basis of simulated data, which are as close as possible to the one expected from actual operational missions, any possible evolution and change in the above mentioned information must be updated and the contest of the RD adjusted accordingly. Periodic checks must be planned and further release(s) of the RD have to be issued if necessary. The requirements are provided for: ? ? ? ? ? ? all the scientific and technological tools developed in the project; all the scientific and technological products of the project (both intermediate and finals); the technological infrastructure of the project, including the geo-database, service, data-interface and visualization tools; the Data Processing Chain (DPC) implemented in the AURORA PDP; the pre-market applications; some management procedures. Although the requirements are specified in terms of functional description, not a design, some information concerning technical choices and design overview can be included with the requirements description in order to establish a practical baseline for all project activities.