User:Giorgos.papanikos

Introduction

The content of this report captures the development status of all software components that are direct or indirect consequence of the work performed by the Joint Research Activity 2 (JRA2) work package of the D4ScienceII project.

The objective of this work package is to cover the design and implementation case-specific needs for each particular interoperable infrastructure. Each case is analyzed and the system to implement it, on the side of the interoperating infrastructure, is designed in detail. Following the initial design, each case implements the specific components required so that it can exploit the facilities offered by the evolving ecosystem core and it can export the identified interoperable features to the rest of the ecosystem cases.

The cases involved in these scenarios are the ones defined by the high level needs and requirements exposed by the one of the following infrastructures and have been specialized through the NA4 and NA5 process. These interoperability cases through this process evolved to specific implementation requirements whose definitions and status of implementation is reported in this document. The implementation is performed in the context of the following tasks:

• INSPIRE specific implementation
• DRIVER specific implementation
• AquaMaps specific implementation
• FCPPS specific implementation
• ICIS specific implementation

This document reports on the implementation progress made in the context of these tasks. Progress is reported both in the context of each individual task as well as in the direction of ecosystem interoperability. The report groups related functionalities (from an implementation point of view), with respect to their impact in components that are involved for their provision. Thus, the status of development is presented by functional group, whereas this can be the result of the combined status of various elements involved in a particular functional scope. Furthermore, as a single component might expose more than a single functional facet, it might be implicitly or explicitly involved in several functional groups.

As a result of a requirement (or an entire requirement group), development can be aiming to:

• An entirely new software suite (Service including libraries and user interface elements if applicable) for extending gCube potential in a new domain.
• A minor new component (of any of the aforementioned types) that plugs into the infrastructure (or to a particular existing component) in well defined areas, adding to its behavior.
• Modification/extension of existing components, for provision of new functionality or modification/improvement of the existing one.

In this stage of D4ScienceII project, the status of a component can be any of the following:

• Canceled (components that their design and implementation has been canceled due to shift of interest)
• Design (components that are in the stage of design and the best implementation approach is yet to be decided)
• Prototypes (components that are already designed and implemented as prototypes but have not been delivered yet as stable versions).
• Delivered (components that have been completely delivered, i.e. are deployable on the infrastructure, but further refinements are performed)
• Completed (delivered components that their formal development cycle is finished and no updates are planned for next versions)

A further clarification is given with respect to development so as to make evident which is the degree to which a component can be included in a production infrastructure in its current state.

It is important to note that a component can be a product of joint community requirements, and as such it is co-referenced in the respective sections. In this report, a clear reference to the request originator is made wherever suited, with a potential clarification on whether this is a “diffusion” adoption or an original request. In the former case a reference is made in the respective section to detail the role of the component in the collaboration among ecosystems.

Functionality Status Sum-up

INSPIRE

Functionality	Related TRACked Requirements	Support	Diffusion	Status	Stage Completion (%)	Completion Date	Production Release Date
In-document reference to detailed description	Track URI	List of partners involved	List of in-document references to related functionalities where this component is diffused	The current status of the component	percentage completed	The envisaged or actual completion date	The envisaged or actual release date