Step	Description of action	Dependency on 3rd party services (EOSC-hub or other)
UC1	A researcher request to access the services of the EPOS-ORFEUS CC. He is redirected to the CC Authentication Service (based on B2ACCESS) where he registers. He receives a token. Depending on his profile he might be authorised to use the services of the CC. Profiles include for instance: data manager, special user (who has access to restricted data) and normal user	B2ACCESS
UC2	A researcher (authenticated and authorised) searches for datasets of her interest by using an API. She selects one ore more staging nodes from the available ones received by interrogating the API. Finally she initiates the data movement by calling a dedicated method of the same API.	B2STAGE, B2SAFE, EIDA WFCatalog (with Dublin Core extension)
UC3	A seismologist (authenticated and authorised) wants to perform an analysis on a datasets previously selected and staged. He logs in the Jupyter environment close to the staged datasets. He selects and launches a kernel containing his preferred seismological libraries. When the correspondent Jupiter notebook is up and running the datasets are available in a local directory and he can perform his analysis. He might choose to pause his work and save it for later. Finally he can download results on his PC, move them to his personal cloud storage folder or made them available on a local folder.	EGI NotebooksNotebook, B2DROP

Architecture & EOSC-hub technologies considered/assessed

...

Requirement number

Requirement title

Link to Requirement JIRA ticket

Source Use Case

Example

EOSC-hub to provide an FTS data transfer service

Jira

UC1

RQ1

iRODS instance accessible from the Jupyter environment and federated with local B2SAFE/iRODS instances

UC2, UC3

RQ2

Customisable and permanent kernels in Jupyter (EGI Notebook)

UC3

RQ3

Personal data folder with staged data to be mounted in Jupiter

UC3

Capacity Requirements

EOSC-hub services	Amount of requested resources	Time period

...