Goals

The main OPENCOSS objective is to both reduce time and cost for safety (re)certification via compositional and evolutionary certification and by realizing the first European-wide open safety certification platform spanning different vertical embedded system markets like the railway, avionics and automotive domains.

The overall goals of OPENCOSS, to improve the current situation in safety-critical system development, are:

  • To demonstrate a potential reduction of recurring costs for component/product safety certification across systems by 40% and across vertical markets by 30%
  • To demonstrate a potential reduction of product safety risks by 20%
  • To demonstrate a potential gain for product innovation and upgrading by 20%

The overall goal achievements will be assessed by comparing estimated end of project levels with beginning of project levels for the OPENCOSS partners, as described in Section 1.1.4 (Industrial Use Cases) and 1.1.6 (Measures of Success).

The OPENCOSS main objective and overall goals will be achieved by means of the following project objectives:

  • Define a common conceptual safety certification language to improve mutual recognition agreement of safety approvals and to be employed to discuss abstract notions from different industrial markets.
  • Define a compositional and evolutionary approach that reuses safety arguments, in a way that it is easily certifiable and that such certification is re-usable when integrating the product in higher level systems and interconnected systems.
  • Develop a fully-fledged open-source tool infrastructure that will allow developers and other safety assurance stakeholders to:
    • Reduce uncertainty and (re)certification costs by following a measurable and auditable process
    • Assess their compliance with safety standards and practices
  • Benchmark the tool infrastructure against real industrial cases from railway, avionics and automotive.
  • Support the OPENCOSS community building and standardization of:
    • The common conceptual safety certification framework as a “de-jure” standard.
    • The open-source tool infrastructure as a “de-facto” standard.