...
| 정보 | ||
|---|---|---|
| ||
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 DODAS user I want a service that simplifies the process of provisioning, creating, managing and accessing a pool of heterogeneous computing resources, including private and public clouds. | |
US2 | As a user DODAS administrator, I want to transparent access the resources reserved on different providers be able to monitor DODAS services (DODAS Core services) | |
US3 | US5 | As service owner I want to be able to collect accounting information/data to be integrated in the EOSC-HUB accounting systemAs a userDODAS administrator I want to be able to access also public clouds |
| US4 | A service owner I want to provide data caching mechanisms that the users can benefit transparently | |
monitor processes and services running on the dodas clusters (check status resources consumption etc.) | ||
| US4 | As a DODAS end user (e.g. physicist) I want to transparently access my remote data | |
| US5 | As a DODAS end user (e.g. physicist) I want to temporary cache input and output data from dodas cluster | |
| US6 | As community adopting dodas, I want to be able to globally share libraries and software (e.g. runtime environment) more in general. | |
| US7 | As user of dodas i want to be able to move my sandboxes (input/output) through dropbox like solution | |
| US8 | As a user, I want to be able to access all my portals using the same credentials, including authentication through the EGI CheckIn when desired. |
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. |
...