IEC Certification Kit (for ISO 26262 and IEC 61508)

Qualify software tools for ISO 26262 and IEC 61508 certification

IEC Certification Kit provides tool classification and tool qualification work products, together with templates, certificates, and validation suites. The kit lets you qualify MathWorks specification, design, code generation, and verification tools in your environment.

You use the kit to streamline certification of your embedded systems to produce a complete and standard-compliant tool qualification package for ISO^® 26262, IEC 61508, ISO 25119, EN 50128, EN 50657, and IEC 62304. The kit supports ASIL A through ASIL D (for ISO 26262) and SIL 1 through SIL 4 (for IEC 61508). Certificates and assessment reports from certification authority TÜV SÜD are included in the kit for the supported products and standards.

IEC Certification Kit provides documents for you to map Model-Based Design use cases to requirements from functional safety standards and automotive standards like ISO 21434 (for cybersecurity), ISO 21448 (SOTIF), and Automotive SPICE. You can use automation tools and case study examples from the kit to get started with your certification projects and produce work products required throughout the lifecycle of your products.

Note: ISO26262:2018 states that Simulink and Stateflow are suitable for Software Architecture and Software Unit Design Notations and as a basis for automatic code generation.

Develop ISO 26262-Compliant ADAS Applications with Model-Based Design

A diagram illustrating classification steps (left) and qualification needs (right) for tool use cases per ISO 26262.

Tool Classification and Tool Qualification

Classify and qualify MathWorks specification, design, code generation, and verification tools according to functional safety standards with the help of qualification artifacts and template documents.

Software Tool Qualification According to ISO 26262

Documentation

A certification mark issued by TÜV SÜD for tools used with Model-Based Design.

TÜV SÜD Certification Artifacts

Strengthen your safety case and tool qualification package with available certificates and certificate reports from TÜV SÜD.

View certificate details from TÜV SÜD

Model-Based Design Case Study for ISO 26262

Explore a case study that shows step-by-step how Model-Based Design can help automate and accelerate your engineering processes while ensuring compliance with ISO 26262.

How to Use Simulink for ISO 26262 Projects

Documentation | Examples

Guidance for IEC 61508 and Related Standards

Establish standard-compliant processes in your project or organization with pre-qualified and proven in wide use reference workflows and tool mapping documents. Supported standards include IEC 61508 and derivate standards such as EN 50128, EN 50657, IEC 62304, ISO 25119, and ISO 26262.

Developing Embedded Software for Induction Motor Control Using Model-Based Design (19:49)

Documentation

An excerpt of A-SPICE tool mapping document available in the IEC Certification Kit showing example Base Practices from SWE1 (left column) and applicable use cases and artifacts (other columns).

Tool Mapping for Automotive SPICE (A-SPICE)

Build high-quality A-SPICE-compliant products using Model-Based Design with guidance focused on traceability, correctness, consistency, and completeness.

Accelerate A-SPICE compliance with Model-Based Design - Part 1/2 (Systems Engineering Processes) (56:37)

Accelerate A-SPICE compliance with Model Based Design - Part 2/2 (Software Engineering Processes) (55:47)

Verifications and Validation Methods for ISO 21448 (SOTIF)

Use Model-Based Design to develop Advanced Driver Assistance Systems (ADAS) and automated driving (AD) applications that meet ISO 21448:2021 (SOTIF) requirements.

Verify and validate the safety of the intended functionality with scenario-based testing.

A Conceptual Framework for ADAS/AD Safety (19:53)

Documentation

An example Simulink system model that includes controller and plant submodels connected via a CAN bus as well as a switch for initiating simulated cybersecurity attacks on the CAN bus.

Cybersecure Systems for ISO 21434

Apply IEC Certification Kit guidance to better detect vulnerabilities in your embedded software and build cybersecure and ISO 21434-compliant systems with Model-Based Design.

Dealing with Cyber Security Challenges in Embedded System Designs (45:20)

Product Resources:

Documentation Technical articles Functions IEC 61508 Support ISO 26262 Support Requirements Release notes

KOSTAL Asia R&D Center Receives ISO 26262 ASIL D Certification for Automotive Software Developed with Model-Based Design

“Using Model-Based Design to design, implement, and verify our software for the highest functional safety standard enabled our team to save costs, increase efficiency, and ensure software quality. Without Model-Based Design, more engineers would be needed to complete the project in the same time frame.”
Cheng Hui, KOSTAL

View more customer stories

Interested in IEC Certification Kit?

Request a trial Request a quote

What's Next?

Free white paper

11 Best Practices for Developing ISO 26262 Applications with Simulink

TRAINING

Applying Model-Based Design for ISO 26262

Technical Article

A Verification and Validation Workflow for IEC 61508 Applications

Notations		ASIL
Notations		A	B	C	D
1a	Natural language^a	++	++	++	++
1b	Informal notations	++	++	+	+
1c	Semi-formal notations^b	+	+	++	++
1d	Formal notations	+	+	+	+

Natural language can complement the use of notations for example where some topics are more readily expressed in natural language or provide an explanation and rationale for decisions captured in the notations.

EXAMPLE: To avoid possible ambiguity of natural language when designing complex elements, a combination of an activity diagram with natural language can be used.

Semi-formal notations can include pseudocode or modelling with UML^®, SysML^®, Simulink^® or Stateflow^®.

NOTE: UML^®, SysML^®, Simulink^® and Stateflow^® are examples of suitable products available commercially. This intormation is given for the convenience or users ot this document and does not constitute an endorsement by ISO ot these products.

NOTE: In the case of model-based development with automatic code generation, the methods for representing the software unit design are applied to the model which serves as the basis for the code generation.