버전 비교
키
- 이 줄이 추가되었습니다.
- 이 줄이 삭제되었습니다.
- 서식이 변경되었습니다.
| 페이지 속성 | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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 | As a service owner, I want to be able to deploy the Data Miner (DM) cluster in an IaaS infrastructure |
US2 | As a service owner, I want to be able to monitor the performance of the DM |
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 | DM cluster service is deployed in the Cloud as a long-running service | EGI Cloud Compute service |
UC2 | Resource consumption (compute, data) is tracked and accessible | Accounting |
| UC3 | DM cluster service is monitored | DM cluster |
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 | DM cluster deployment in the EGI Cloud Compute service | dd
| UC1 | ||||||||||
RQ2 | Tracking compute consumption | UC2 | |||||||||||
| RQ3 | Get performance metrics: number of analytics tasks |
| UC3 | ||||||||||
| RQ4 | Get performance metrics: availability / uptime (percentage) |
| UC3 | ||||||||||
| RQ5 | Display of performance metrics in Nagios |
| UC3 |
Capacity Requirements
EOSC-hub services | Amount of requested resources | Time period |
|---|---|---|
| EGI Cloud Compute service | Initial cloud compute capacity for the pilot is 4 VMs with 16 vCPU cores and 32GB RAM running in a single data center with local disk space of 250GB. Additionaly, 1 VM + 1 public IP for proxying requests to the DM cluster. | Apr → Dec 2020 |
| 목차 |
|---|