WEBINAR ON-DEMAND
Why ISO 26262 Compliant?

The bits and bolts of the automotive industry has met with the latest advances in computing technology that automotive electronics currently accounts for about 25% of the capital cost of new cars and the amount of software now exceeds one gigabyte per vehicle. Adapting to such dramatic increases in software has spawned process errors that have resulted in unfortunate loss of lives, countless recalls, and expensive litigation. To curb this level of risk and to enforce software quality, automotive OEMs have begun to demand ISO 26262 compliance from their supply chain.

This webinar will examine what’s needed to demonstrate compliance to the ISO 26262 Functional Safety Standard. With ISO 26262, product safety life cycles are based on a risk-oriented approach determined by system and software Safety Integrity Levels (SILs).

Not only is it required to capture the high-level system requirements, system architecture, detailed design and low-level implementation, but each high-level system requirement must also be formally verified. This includes the use of structural coverage analysis metrics to document testing completeness.

The methodology is based on a compliance management system that provides a compliance roadmap to help manage the software planning, development, verification, and regulatory activities of ISO 26262 Part 6, Product Development: Software Level (ISO 26262-6).

Login or register to view