GCube Development

gCube (http://www.gcube-system.org) is a Software System whose development activity is ongoing and performed according to the Agile software development methodology. This implies that software components are developed in relatively short subsequent iterations, each containing the tasks needed to release new functionality - planning, requirement analysis, detailed design, implementation, integration, testing and documentation. This leads to a very flexible and dynamic development activity that needs to be proper documented.

Such a technology is intrinsically complex because of the amount of standards, specifications, technologies, patterns and approaches put in place to guarantee a high quality (reliable, secure, autonomic, fault resilient, etc.) software system. This risks to overwhelm developers and distract them from the specific application logic of the services they are willing to develop.

This software system has been implemented with the support of the European Commission in the context of a series of projects including D4Science-II, iMarine, EUBrazilOpenBio.

D4Science-II Development

In the context of the D4Science-II project, the gCube technology has been developed with the synergistic activities of two work packages:

• JRA1 Knowledge Ecosystem Implementation whose objectives are (i) to provide the technology realising the common practices, standards and solutions identified by the NA4 work package (Interoperability Solutions) and (ii) to enhance and consolidate the gCube system to match the needs of the ecosystem approach;
  • This activity is documented via a dedicated report;
• JRA2 Scenario Specific Implementation whose objective 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.
  • This activity is documented via a dedicated report;