You are required to read and agree to the below before accessing a full-text version of an article in the IDE article repository.

The full-text document you are about to access is subject to national and international copyright laws. In most cases (but not necessarily all) the consequence is that personal use is allowed given that the copyright owner is duly acknowledged and respected. All other use (typically) require an explicit permission (often in writing) by the copyright owner.

For the reports in this repository we specifically note that

  • the use of articles under IEEE copyright is governed by the IEEE copyright policy (available at
  • the use of articles under ACM copyright is governed by the ACM copyright policy (available at
  • technical reports and other articles issued by M‰lardalen University is free for personal use. For other use, the explicit consent of the authors is required
  • in other cases, please contact the copyright owner for detailed information

By accepting I agree to acknowledge and respect the rights of the copyright owner of the document I am about to access.

If you are in doubt, feel free to contact

Reuse in (re) certification of systems


Barbara Gallina, Jabier Martinez

Publication Type:



17th International Conference on Software Reuse


The reduction of time and cost for the creation of a safety case is an urgent challenge that industries must face in the context of safety-critical product lines. A safety case is a contextualized structured argument constituted of process and product-based sub-arguments to show that a system is acceptably safe and thus assure society at large that deployment of a given system does not pose an unacceptable risk of harm". Safety assurance and assessment processes required by standards and jurisdictions use to span several years and consume a large number of resources. To reduce time and cost, reuse capabilities are being investigated. At the core of this eff ort, there is the objective to provide a generic metamodel capturing concepts of safety compliance processes. This is opening many doors towards a common model-based certi cation framework that can simultaneously target diverse domains such as the automotive, railway, avionics, air traffic management, industrial automation, or space domains. Then, di fferent recurrent scenarios of (re)certi fication are being studied with their own characteristics and challenges. For example, in the system upgrade scenario we aim to identify the parts of the safety assurance project that can be reused for the upgraded system. In the cross-standard reuse scenario, the same system certi fied against a standard needs to be certfii ed with another standard or, in the case of jurisdictions, checking compliance with a country jurisdiction that di ffers from the current one. In the cross-concern reuse scenario, a system certifi ed against a given standard (e.g., security related) requires to be certifi ed with a standard targeting a different concerns (e.g., safety). The AMASS project (Architecture-driven, Multi-concern and Seamless Assurance and Certi fication of Cyber-Physical Systems) continues previous eff orts to defi ne the Common Assurance and Certi fication Metamodel (CACM) and a tool-based platform is being developed. Among its functionalities, advanced techniques are provided enabling reuse by combining process lines, product lines and safety case lines.


author = {Barbara Gallina and Jabier Martinez},
title = {Reuse in (re) certification of systems},
month = {May},
year = {2018},
url = {}