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

Lessons Learned while Formalizing ISO 26262 for Compliance Checking


Publication Type:

Conference/Workshop Paper


2nd Workshop on TeReCom - Technologies for Regulatory Compliance


A confirmation review of the safety plan is required during a compliance assessment with ISO 26262. Its production could be facilitated by creating a specification of the standard's requirements in FCL (Formal Contract Logic), which is a language that can be used to automatically checking compliance. However, we have learned, via previous experiences, that interpreting ISO 26262 requirements and specifying them in FCL is complex. Thus, we perform a formalization-oriented pre-processing of ISO 26262 to find effective ways to proceed with this task. In this paper, we present the lessons learned from this pre-processing which includes the identification of the essential normative parts to be formalized, the identification of SCP (Safety Compliance Patterns) and its subsequent documentation as templates, and the definition of a methodological guideline to facilitate the formalization of normative clauses. Finally, we illustrate the defined methodology by formalizing ISO 26262 part3 and discuss our findings.


@inproceedings{Castellanos Ardila5309,
author = {Julieth Patricia Castellanos Ardila and Barbara Gallina and Guido Governatori},
title = {Lessons Learned while Formalizing ISO 26262 for Compliance Checking},
pages = {5--16},
month = {February},
year = {2019},
booktitle = {2nd Workshop on TeReCom - Technologies for Regulatory Compliance},
url = {}