...
Requirements
Technical Requirements
Requirement number | Requirement title | Link to Requirement JIRA ticket | Source Use Case | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Example | EOSC-hub to provide an FTS data transfer service |
| UC1 | ||||||||
RQ1 |
Requirement ID | EOSC-hub service | GAP (Yes/No) + description | Requirement description | Source Use Case |
|---|---|---|---|---|
Example | EOSC-hub AAI | Yes: EOSC-hub AAI doesn’t support the Marine IdP | EOSC-hub AAI should accept Marine IDs | UC1 |
| RQ1 | ? | Yes: | Browsable catalogue of EO data that allows to discover the providers hosting the relevant data for the user | UC1 |
RQ2 | Cloud Compute | No | Create VMs on providers hosting the data | UC2 |
| RQ3 | Cloud Compute/DataHub | No: DataHub can provide that functionality | Provide data with a POSIX interface on VMs | UC3 |
| RQ4 | ? | Yes: there is no catalogue of OGC WS endpoints in the EOSC-hub | Discovery of OGC WS compliant services | UC4 |
| RQ5 | EOSC-hub AAI | No: OpenID Connect allows non-browser access to services | Use OGC WS services with EOSC-hub identities | UC5 |
RQ6 | EOSC-hub AAI | Yes: ESOC-hub AAI doesn't support ESA SSO | EOSC-hub AAI should accept ESA SSO ids | UC6 |
...