Related Artemis RTP projects perspective

If you have been involved in a previous Artemis RTP project, you want your results to be picked up by follow up work like CRYSTAL and brought to a higher level of advancement and adoption.  Also, the Artemis Industry Association wants to build a coherent set of solutions across projects that support system development of embedded and cyber-physical systems.

Drivers

·        Reuse project results of previous projects (CESAR, MBAT and others)

  • IOS results are reused and expanded in CRYSTAL (our work is not lost)
  • Show sustainability of related projects through CRYSTAL

·        Build tool coverage

  • Expand interoperable tool catalog
  • Build support for tool library

·        Build IOS

  • Make IOS more comprehensive
  • Build support for IOS
  • Make IOS a standard beyond CRYSTAL and establish governance for this standard

As with any EU collaborative project, the consortium collaboration is temporary. In practice, the projects give rise to much industrial collaboration afterward.

After the project end, the results run the risk of quickly becoming outdated. For the results of the project to be used in full, the Artemis program stimulates clusters of projects that build on top of related projects. In that sense, CRYSTAL was built on the shoulders of CESAR, MBAT , MODELWARE, iFEST, DANSE, D3COS and SafeCer.

These projects have an interest for their results to be taken up and be expanded. This shows the value and sustainability of the project results and avoids reinventing the wheel. For that reason, CRYSTAL has adopted parts of the MBAT and CESAR IOS and the corresponding approach. As some of the precursor projects had a specialized focus, CRYSTAL expanded this to the full scope of system engineering and the system life cycle. This means that not only the previous results are reused, but also that they are expanded.

The catalog of interoperable tools called the RTP was already started in MBAT and CESAR and is further developed in CRYSTAL and published with the Platform Builder. More and more tools have been adapted in CRYSTAL to expand the interoperable tool library. CESAR already selected OSLC as the key interoperability principle for the Interoperability Specification (IOS) which is elaborated in full in CRYSTAL. The critical mass that CRYSTAL provides helps to turn the IOS into a standard. With OSLC being adopted as a standard by OASIS and the IOS taken up by the CP-SETIS project, it has become clear who takes responsibility for the governance and sustainability of the standards.