User stories
Instruction
Requirements are based on a user story, which 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 portal administrator, I want to allow my users to transparently use DIRAC4EGI to run their workloads. |
US2 | As a user, I want to be able to access my data stored in B2DROP and Onedata (and possibly some other repository like Dropbox) directly from the web portal (avoiding local transfer steps), both for job submission and for uploading results. |
US3 | 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
Instruction
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 | Portal's administrator integrates into the portal job submission by users. | DIRAC4EGI |
UC2 | A portal user uses Virtual Folder service to access his data stored on remote services | West-Life Virtual Folder VM |
UC3 | West-Life Virtual Folder exposes through webdav multiple backend data storage services | B2DROP Onedata |
UC4 | A user is able to authenticate to the portals using it's own IdP supported by WeNMR | EGI CheckIn |
Requirements
Technical Requirements
Requirement ID | EOSC-hub service | GAP (Yes/No) + description | Requirement description | Source Use Case | Related tickets |
---|---|---|---|---|---|
Example | EOSC-hub AAI | Yes: EOSC-hub AAI doesn’t support the Marine IdP | EOSC-hub AAI should accept Marine IDs | UC1 | |
RQ1 | DIRAC4EGI | No | DIRAC4EGI usage should be integrated into the portals | UC1 | EOSCWP10-29 - Getting issue details... STATUS |
RQ2 | West-Life Virtual Folder VM | Yes: The West-Life Virtual Folder VM and service is not provided/offered by EOSC-Hub. And West-Life project will come to an end at the end of 2018. | West-Life Virtual Folder service should be operated by EOSC-hub | UC2 | EOSCWP10-30 - Getting issue details... STATUS |
RQ3 | B2DROP | No | B2DROP should be integrated within West-Life Virtual Folder | UC3 | EOSCWP10-31 - Getting issue details... STATUS |
RQ4 | Onedata | Yes: Onedata isn't integrated yet within West-Life Virtual Folder | Onedata should be integrated within West-Life Virtual Folder | UC3 | EOSCWP10-32 - Getting issue details... STATUS |
RQ5 | EGI CheckIn | Yes: EOSC-hub and EGI-CheckIn AAI doesn't support the IdP(s) used by WeNMR | AAI should accept the IdP(s) used by WeNMR | UC4 | EOSCWP10-33 - Getting issue details... STATUS |
Capacity Requirements
EOSC-hub services | Amount of requested resources | Time period |
---|---|---|
1 Comment
Baptiste Grenier
Slides on WeNMR AAI report at All Hands meeting in Malaga - April 2018: https://indico.egi.eu/indico/event/3903/session/32/material/0/4.pdf