|
User stories
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.” |
No. | User stories |
|---|---|
US1 | |
US2 | |
... |
Use cases
Technical plan: https://docs.google.com/document/d/1nc4aUrO8y39lt_wlvePI8GHxvRdGaIlC 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 | VESPA Providers want to order a VM with the VO framework installed | CloudCompute, Check-in, eduTEAMS |
UC2 | VESPA Providers want to configure the server for their science application. | CloudCompute, Check-in, eduTEAMS |
UC3 | VESPA Providers want to manage the server packages with the VESPA team. | CloudCompute, Check-in, eduTEAMS |
| UC4 | VESPA Providers want to update the content and the metadata. | CloudCompute, Check-in, eduTEAMS, B2ACCESS, B2SAFE |
Requirements
Technical Requirements
- Requirement number: Use numbers RQ1, RQ2, RQ3, ... |
Requirement number | Requirement title | Link to Requirement JIRA ticket | Source Use Case |
|---|---|---|---|
RQ1 | Integrate eduTEAMS as community AAI and EGI Check-in as e-infrastructure AAI | UC1 | |
RQ2 | Integrate eduTEAMS as community AAI and EUDAT B2ACCESS as e-infrastructure AAI | UC4 |
Capacity Requirements
EOSC-hub services | Amount of requested resources | Time period |
|---|---|---|
| EGI Cloud Compute | 20 VM instances linux based (split evenly across 2 sites): 2 CPU per VM, 4GB RAM per VM, 20 GB disk per VM, 1 fixed DNS name per VM Ports open: 22, 80, 8080 5 remote ssh-key access per VM | Until end of EAP (end of 2020 as of now) |
| EGI Object Storage | 2 x 2TB | Until end of EAP (end of 2020 as of now) |
| EUDAT B2SAFE | 2TB accessible via iRDODS | Until end of EAP (end of 2020 as of now) |
| GEANT eduTEAMS | Community AAI | Until end of EAP (end of 2020 as of now) |
| EGI Check-in | Gateway to EGI resources | Until end of EAP (end of 2020 as of now) |
| EUDAT B2ACCESS | Gateway to EUDAT resources | Until end of EAP (end of 2020 as of now) |
| EUDAT B2FIND | Harvesting of VESPA data | Until end of EAP (end of 2020 as of now) |