- Created by Thomas Exner, last modified on 2020 Sep 22
| Short description | OpenRiskNet/OpenRiskNet is providing an e-infrastructure to the communities involved in safety assessment, including toxicology and especially predictive toxicology, systems and structural biology, bioinformatics and its subtopics toxicogenomics, cheminformatics, biophysics and computer science specifically targeting the EU’s chemical manufacturing industries, e.g. pharmaceutical companies, chemical and agrochemical industries and cosmetic industries, and the corresponding regulatory agencies. |
|---|---|
| Type of community | Others (EAP) |
| Community contact | Thomas Exner, thomas.exner@edelweissconnect.com |
| Interviewer | |
| Date of interview | |
| Meetings | |
| Supporters |
User stories
Instruction
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 user, I want a public instance of the OpenRiskNet/NanoCommons virtual environment (VE) to test and get first experience with the data and modelling services provided by OpenRiskNet/NanoCommons, especially also in connection to other EOSC service, before deploying a VE internally or ask for additional EOSC resources. |
US2 | As a user, I want to use federated authentication mechanisms to access the public VE, including authentication through the EGI Check-In when desired. |
US3 | As a toxicology data and modelling service provider, I want to have my service listed in the EOSC marketplace based on information I provided to OpenRiskNet/NanoCommons. |
| US4 | As a toxicology data service provider, I want to find solutions to index, link and make the data available via general EOSC services like B2FIND and OpenAIRE improving their FAIRness. |
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 | ||
UC2 | ... | |
... |
Requirements
Technical Requirements
Instruction
- Requirement number: Use numbers RQ1, RQ2, RQ3, ...
- Requirement title: Use a short but descriptive title. Use the same title in the Jira ticket 'Summary' field
- Link to requirement JIRA ticket: Open a ticket in <this JIRA queue https://jira.eosc-hub.eu/projects/EOSCWP10/issues/EOSCWP10-4?filter=allopenissues> (click on 'CREATE' button in the middle-top of JIRA)
- Source use case: Refer back to the use cases above (UC1, 2, ...)
Requirement number | Requirement title | Link to Requirement JIRA ticket | Source Use Case |
|---|---|---|---|
Example | EOSC-hub to provide an FTS data transfer service | EOSCWP10-21 - Getting issue details... STATUS | UC1 |
RQ1 | |||
RQ2 |
Capacity Requirements
EOSC-hub services | Amount of requested resources | Time period |
|---|---|---|
