IEC Certification Kit

for ISO 26262 and IEC 61508

IEC Certification Kit Workflow

IEC Certification Kit follows an in-context approach to IEC 61508 and ISO 26262 certification based on a specific workflow or set of workflows used when the applicant applies specific tools to develop or verify software for functional safety standard-compliant or -certified applications. The applicant must ensure that the tools are used within the referenced workflows and within the constraints and use cases specified in certification plans of the applicant’s projects.

IEC Certification Kit is designed to help you provide a complete certification package to certification authorities using MathWorks tools. You use the IEC Certification Kit product to do this as follows.

1. Document compliance with the relevant functional safety standard’s requirements and your intended use cases.
2. Propose an initial certification plan to certification authorities.
3. Collect tool-provided artifacts such as TÜV SÜD certificates and perform application-independent tool qualification activities, including execution of product test suites provided by IEC Certification Kit.
4. Perform application-specific tool qualification activities such as generation of model-to-code traceability using the traceability matrix-generation capability provided by IEC Certification Kit.
5. Provide the completed certification package to certification authorities.

IEC Certification Kit clearly shows how the artifacts, templates, test cases, and documentation provided for a MathWorks tool help satisfy a certification standard’s specific objectives.

Sample Kit Contents for the IEC 61508 Standard

The mapping of Embedded Coder and Polyspace code verifier artifacts to IEC 61508 objectives are shown below. Other supported tools and standards have different references and artifacts.

Embedded Coder

Polyspace Client for C/C++ (Including Its MISRA-C^®:2004 Code Analyzer)

Note: Embedded Coder and Polyspace code verifiers were not developed using an IEC 61508–compliant process. Using certified tools does not ensure the safety of the software or the system under consideration.