| 페이지 속성 | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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
| 정보 | ||
|---|---|---|
| ||
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 | ... | ..
The PHIS information system and the Galaxy environment will be deployed on EGI virtual machines. The storage layer is based on the existing FranceGrilles iRODS infrastructure. An authentication layer based on the EGI check-in serviceand a computing layer provided with the EGI Notebooks servicewill be added. | |
UC2 |
Compared to the previous pilot the storage layer is based on the B2SAFE service supported by the EGI infrastructure. | |||
| UC3 |
Compared to the previous pilot the storage layer is based on the Data Hub service supported by the EGI infrastructure. |
Requirements
Technical Requirements
| 정보 | ||
|---|---|---|
| ||
- Requirement number: Use numbers RQ1, RQ2, RQ3, ... |
Requirement number | Requirement title | Link to Requirement JIRA ticket | Source Use Case | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Example | EOSC-hub to provide an FTS data transfer service |
| UC1 | ||||||||
RQ1 | EGI Cloud Compute & Cloud Container Compute - EGI/CESNET - , EGI/IN2P3 | ||||||||||
RQ2 | EGI Notebook - EGI/EGI.eu | ||||||||||
RQ3 | B2SAFE - EUDAT/CINES | ||||||||||
| RQ4 | EGI DataHub - EGI/CYFRONET | ||||||||||
| RQ5 | Check-in - EGI/GRNET | ||||||||||
| RQ6 | B2ACCESS - EUDAT/Juelich | ||||||||||
| RQ7 | B2HANDLE - EUDAT/GRNET |
Capacity Requirements
EOSC-hub services | Amount of requested resources | Time period |
|---|---|---|
| RQ1 | CESNET-MCC: 6x4CPUs with 6x32GB RAM (including support for a Oneprovider) IN2P3-IRES: 2VMs with 32GB RAM for pilot and Oneprovider VM with 8 vCPU, 32GB RAM with SSD | |
RQ2 | EGI: community-deployment for notebooks for 4 concurrent users (2 vCPUs cores, 4GB of RAM and 40GB of storage per notebook) | |
RQ3 | 10 TB safe storage | |
RQ4 | 10 TB on DataHub Oneprovider, user support |
| 목차 |
|---|