ISO 26262 cuts electronics complexity risks: Pt. 1- Requirements and assessment flow

March 08, 2012 // By Christoph Hammerschmidt
Safety is one of the key issues and requirements of today's and tomorrow's automobile development. New functionalities, not only in the area of driver assistance, but also in vehicle dynamics control and active and passive safety systems, are increasingly being covered in the domain of safety engineering. Future development and integration of these functionalities will further strengthen the need to have safe system development processes and to provide evidence that all reasonable safety objectives are satisfied.

With the trend of increasing complexity, software content, and mechatronic implementation, risks of systematic failures and random hardware failures are also increasing. ISO 26262 provides guidance to reduce these risks to a tolerable level by providing feasible requirements and processes.

In a series of two papers, we will try to detail the functional safety standard (ISO 26262) for the automotive sector and the implications it has for the design community. The first paper in the series will touch upon the safety standard requirements, various steps involved in the overall safety assessment flow and what they mean for design community and the second paper will discuss in detail various steps that need to be taken in design for failure prevention.

To read the article click here. Courtesy of EETimes Automotive Designline


Design category: