Main Content

Industry Standards

Applying Model-Based Design to a safety-critical system requires extra consideration and rigor so that the system adheres to defined safety standards, including:

If you have a Simulink® Check™ product license, you can check that your Simulink model or subsystem and the code that you generate from it complies with the industry standard. For more information, see Modeling Guidelines and Model Advisor Checks for Verifying Compliance with Industry Standards.

IEC 61508: 2010

Development of high-integrity systems within the automotive industry is characterized by demonstrating compliance with IEC 61508: 2010, Functional safety of electrical/electronic/programmable electronic safety related systems. This standard addresses E/E systems1 in commercial vehicles – especially off-highway vehicles. IEC 61508: 2010 was published when most software was coded by hand, therefore the standard needs to be mapped to Model-Based Design technologies. For further information about MathWorks® support for IEC 61508, see IEC 61508 Support in MATLAB and Simulink.

ISO 26262: 2018

Development of high-integrity systems within the automotive industry is characterized by demonstrating compliance with ISO 26262. ISO 26262: 2018 Road vehicles — Functional safety. This standard, which is an adaptation of IEC 61508, addresses E/E systems in passenger road vehicles.

For additional information about MathWorks support for ISO 26262, see ISO 26262 Support in MATLAB and Simulink.

If you have a Simulink Check product license, you can check that your Simulink model or subsystem and the code that you generate from it complies with selected aspects of the ISO 26262 standard. For more information, see Using Model Advisor Checks for IEC 61508, IEC 62304, ISO 26262, ISO 25119, and EN 50128/EN 50657 Industry Standards (Simulink Check).

IEC 62304: 2015

IEC 62304: 2015, Medical device software - Software life cycle processes is an international standard that defines the requirements of the software life-cycle processes for medical device software development. The standard specifies a set of processes, activities, and tasks that establish a common framework for designing safe and tested software for medical devices. For more information about MathWorks support for IEC 62304, see MATLAB and Simulink for Medical Devices.

If you have a Simulink Check product license, you can check that your Simulink model or subsystem and the code that you generate from it complies with selected aspects of the IEC 62304 standard. For more information, see Using Model Advisor Checks for IEC 61508, IEC 62304, ISO 26262, ISO 25119, and EN 50128/EN 50657 Industry Standards (Simulink Check).

EN 50128 / EN 50128: 2011

High-integrity systems developed within the railway industry need to demonstrate compliance with:

  • EN 50128: 2011, Railway applications — Software for railway control and protection systems

  • EN 50657:2017, Railways Applications - Rolling stock applications - Software on Board Rolling Stock

These European standards specify procedures and technical requirements for the development of programmable electronic systems for use in railway control and protection applications. For more information about MathWorks support for EN 50128, see EN 50128/EN 50657.

If you have a Simulink Check product license, you can check that your Simulink model or subsystem and the code that you generate from it complies with selected aspects of the EN 50128 standard. For more information, see Using Model Advisor Checks for IEC 61508, IEC 62304, ISO 26262, ISO 25119, and EN 50128/EN 50657 Industry Standards (Simulink Check).

ISO 25119 Standard

Applying Model-Based Design to a safety-critical system requires extra consideration and rigor so that the system adheres to defined functional safety standards. ISO 25119, Tractors and machinery for agriculture and forestry — Safety-related parts of control systems, is such a standard.

MathWorks provides an IEC Certification Kit product that you can use to qualify MathWorks code generation and verification tools for projects based on the ISO 25119 standard.

If you have a Simulink Check product license, you can check that your Simulink model or subsystem and the code that you generate from it complies with selected aspects of the ISO 25119 standard. For more information, see Using Model Advisor Checks for IEC 61508, IEC 62304, ISO 26262, ISO 25119, and EN 50128/EN 50657 Industry Standards (Simulink Check).

DO-178C Standard

Applying Model-Based Design to a high-integrity system requires extra consideration and rigor so that the system adheres to defined safety standards. DO-178C, Software Considerations in Airborne Systems and Equipment Certification, is such a standard. A supplement to DO-178C, DO-331, provides guidance on the use of Model-Based Design technologies. MathWorks provides a DO Qualification Kit product that you can use to qualify MathWorks verification tools for projects based on the DO-178C, DO-331, and related standards. For more information, see https://www.mathworks.com/products/do-178/.

For information about Model-Based Design and MathWorks support of aerospace and defense industry standards, see DO Qualification Kit.

If you have a Simulink Check product license, you can check that your Simulink model or subsystem and the code that you generate from it complies with selected aspects of the DO-178C standard. For more information, see Using Model Advisor Checks for DO-178C/DO-331 Industry Standards (Simulink Check).

AUTOSAR Standard

Simulink software supports AUTomotive Open System ARchitecture (AUTOSAR), an open and standardized automotive software architecture. Automobile manufacturers, suppliers, and tool developers jointly develop AUTOSAR components.

The AUTOSAR standard addresses:

  • Architecture – Application, run-time environment, and service layers, which serve to decouple AUTOSAR software components from the execution platform. Standard interfaces between software components and the run-time environment allow reuse or relocation of components within the Electronic Control Unit (ECU) topology of a vehicle.

    The standard defines two AUTOSAR platforms:

    • Classic Platform (CP), with Application, Runtime Environment (RTE), and Basic Software (BSW) layers

    • Adaptive Platform (AP), with Application, AUTOSAR Runtime for Adaptive Applications (ARA), Services, and Basis layers

  • Methodology – Specification of code formats and description file templates, for example.

  • Foundation – Requirements and specifications shared between AUTOSAR platforms, supporting platform interoperability.

  • Application Interfaces – Specification of interfaces for typical automotive applications.

For more information, see:

If you have an AUTOSAR Blockset product license, you can check that your Simulink model or subsystem and the code that you generate from it complies with selected aspects of the AUTOSAR standard. For more information, see AUTOSAR Blockset Checks (AUTOSAR Blockset).

See Also

External Websites

1 Systems that consists of electrical and electronic elements, including: programmable electronic elements, power supplies, input devices, communication paths, and output devices.