|
Requirements are based on a user story, which is is an informal, natural language description of one or more features of a software system. User stories are often written from the perspective of an end user or user of a system. Depending on the community, user stories may be written by various stakeholders including clients, users, managers or development team members. They facilitate sensemaking and communication, that is, they help software teams organize their understanding of the system and its context. Please do not confuse user story with system requirements. A user story is an informal description of a feature; a requirement is a formal description of need (See section later). User stories may follow one of several formats or templates. The most common would be: "As a <role>, I want <capability> so that <receive benefit>" "In order to <receive benefit> as a <role>, I want <goal/desire>" "As <persona>, I want <what?> so that <why?>" where a persona is a fictional stakeholder (e.g. user). A persona may include a name, picture; characteristics, behaviours, attitudes, and a goal which the product should help them achieve. Example: “As provider of the Climate gateway I want to empower researchers from academia to interact with datasets stored in the Climate Catalogue, and bring their own applications to analyse this data on remote cloud servers offered via EGI.” |
EISCAT_3D will generate raw data at a few observation sites (antennas) and has to make those data browsable and analysable for researchers, as well as archiving the data for the long-term. This primary mission is achieved by procuring sufficiently big storage and network capacities at a few data/compute centres (for back-up or load distribution). The raw data is transferred to this/these locations, often after initial filtering and calibration at the data source(s). The data/compute centres are responsible for data archival, data curation, generation of derived data (level 1-2-3) and for sharing the data with scientists.
Data must be shared with scientists via a data portal and programming APIs. The 'EISCAT_3D Data Portal' should offer the following main features:
A secondary objective for many of these infrastructures is provisioning application frameworks or application platforms that enable researchers to interact with the data online, without the need to download or transfer relevant datasets to local/national compute facilities. Centrally provided application platforms can make ‘reference applications’ easily accessible for non-IT-savvy scientists, and may also support algorithm developers to inject/upload custom processing code for own, or for shared use. At the same time such frameworks may come with significant extra cost: If they become popular, then large compute resources must be also procured and the data portal must be turned into a computational portal that can scale out to the procured CPU/GPU resources.
Possible contributions from EGI/EOSC-hub:
Data transfer service: FTS is under negotiation with RAL and CERN
Application and data catalogue portal service with compute integration: DIRAC
No. | User stories |
|---|---|
US1 | |
US2 | |
... |
A use case is a list of actions or event steps typically defining the interactions between a role (known in the Unified Modeling Language as an actor) and a system to achieve a goal. Include in this section any diagrams that could facilitate the understanding of the use cases and their relationships. |
Step | Description of action | Dependency on 3rd party services (EOSC-hub or other) |
|---|---|---|
UC1 | ||
UC2 | ... | |
... |
Requirement ID | EOSC-hub service | GAP (Yes/No) + description | Requirement description | Source Use Case |
|---|---|---|---|---|
Example | EOSC-hub AAI | Yes: EOSC-hub AAI doesn’t support the Marine IdP | EOSC-hub AAI should accept Marine IDs | UC1 |
RQ1 | <Gap service> | Yes: …. | ||
RQ2 | Cloud Compute | No | Create VMs ia a gateway | UC2 |
EOSC-hub services | Amount of requested resources | Time period |
|---|---|---|