Step	Description of action	Dependency on 3rd party services (EOSC-hub or other)
UC1	Joining the cloud federation with a cloud site (cloud provider perspective): AAI integration Connect cloud to the RDSDS Connect cloud to the reference application distribution service Policy compliance with policies (ELIXIR, EGI cloud, and EOSC-hub policies)	EOSC-hub centrally provided data distribution service (a new requirement to EOSC-hub!) EOSC-hub centrally provided application distribution and orchestration service (a new requirement to EOSC-hub) ELIXIR cloud federation policies, protocols and interfaces. (under definition)
UC2	Making reference/core datasets available for replication to the federated cloud providers (data provider perspective): ...use EOSC-hub FTS service... ...	Same as above.
UC3	Requesting the replication of a reference/core dataset to my local cloud (researcher perspective): ...use EOSC-hub FTS service... ...	Same as above.
UC4	Making virtualised, reference/core applications available for replication and orchestration on the federated cloud providers (data provider perspective): ...use EOSC-hub 'Kubernetes as a Service'...	Same as above.
UC5	Requesting the replication of a reference/core application to my local cloud (researcher perspective): ...use EOSC-hub 'Kubernetes as a Service'... ...	Same as above.

EOSC-hub technologies considered/assessed

....

Requirements

...

...

Requirement number

Requirement title

Link to Requirement JIRA ticket

Source Use Case

RQ1

EOSC-hub to provide an FTS data transfer service

Jira

UC1, 2, 3

RQ2

EOSC-hub to provide Kubernetes as a service

Jira

UC1, 4, 5

...