AMASS case studies

Share this post :

AMASS will validate and benchmark its results in 11 industrial case studies from six different application domains: Air Traffic Management, Automotive, Avionics, Industrial Automation, Railway, and Space. Their description and expected business impact have already been published in deliverable D1.1.

The case studies will deal with a variety of system types and with some of the most novel characteristics and most recent assurance needs of CPS, e.g. advanced automated and collaborative features of transport systems and the use of new software and hardware technologies in satellites. Examples of the aspects that will be evaluated in the case studies for each Scientific and Technical Objectives include:

  • Architecture-Driven Assurance – link of SysML and Simulink models with assurance models, and application of model- and pattern-based approaches for systematic analysis of functional safety of a cooperative system-of-systems.
  • Multi-Concern Assurance – co-analysis of safety and security on the same architectural models of an advanced driver assistance function, and automated support for the creation of assurance cases that address several dependability aspects (safety, security, reliability…).
  • Seamless Interoperability – integration of the AMASS platform with commercial engineering tools such as DOORS, IBM Rhapsody, and Matlab, and OSLC-based seamless tool chains.
  • Cross- and Intra-Domain Reuse – reuse of assurance information between automotive and avionics, and reuse of qualification dossiers of space components and applications.

For each case study, D1.1 presents:

  • Short description (overview) about the case study
  • Detailed technical description of the case study
  • Description of the state of the art regarding the case study
  • Description of the state of the practice in the partner companies regarding the case study
  • A rough description of the assurance workflow in the case study
  • Description about the assessment work by a third party or any independent company internal department
  • Which roles are involved in the case study and how many people work in this case study
  • Which methods and tools are used and how they interoperate
  • The expected improvement regarding the case study at the end of the AMASS project and which Scientific and Technical Objectives are covered
  • Description of the specific business needs to improve the case study and which AMASS goals are covered
  • Definition of the case study stakeholders and the practices developed by the stakeholders

The initial validation with the case studies will be conducted at the beginning of 2017, once the first prototype of the AMASS platform is available for its application on case study-specific needs.