Introduction

This document describes the APEx design.

Relation of APEx to other projects

SEF Responsibilities

Providing training to stakeholders (end-users) on how to use specific APEx hosted services. This includes pricing concepts, the use of user interfaces or simple API’s.

Earth code

Earth code targets science projects, not application projects. Guidelines can be shared to a certain extent, but there may be a difference.

EOEPCA

APEx is to provide requirements to building block developers. EOEPCA is to provide the building blocks.

The final decision on the use of EOEPCA building blocks depends on an assessment of overall quality and compliance to the provided requirements. It is important that APEx has the freedom to select other software, if the EOEPCA building block has issues. It is up to EOEPCA developers & project to build high quality software that aligns with stakeholder needs. A traditional requirements based process does not necessarily lead to such a result, and more generally, any time-constrained software development process comes with a risk of not delivering on user needs.

MVP WP’s

Tasks

  • T3.1 Portal Setup (VITO)
  • T3.2 User Management (Inuits)
  • T3.3 Infrastructure Dashboards (Inuits)
  • T3.4 Documentation (VITO)

Software Deliverables

  • S01-PRT – APEx Portal (v1)

Tasks:

  • T4.1 Project Portal Service (VITO)
  • T4.2 Dashboard Service (Sparkgeo Consulting Inc)
  • T4.3 Interactive Development Environments (Terradue)
  • T4.4 Web Based Visualization (Sparkgeo Consulting Inc)
  • T4.5 User Workspace (Terradue)
  • T4.6 Catalogue (VITO)

Deliverables

  • D11-ISS: APEx Instantiation Services & Specifications

Tasks

  • T5.1 Algorithm Hosting Service (Terradue)
  • T5.2 Algorithm Upscaling Service (Terradue)
  • T5.3 Algorithm Enhancement Service (Brockmann Consult)
  • T5.4 Toolbox Cloudification Service (Brockmann Consult)
  • T5.5 Algorithm Intercomparison Service (Brockmann Consult)