4. ISO 26262 ASIL D Compliance
While many legacy electronic driving systems have been developed by small, experienced teams with a proven pedigree delivering safe and reliable software, the transformation to sophisticated ADAS requires a formalized process that can guarantee safety is not left as an afterthought: a safety culture must be permeated across the organization, including design, manufacturing, and operations, and recursively to suppliers. This promulgation of effective process standardization requires not only high quality standards but also enforcement of standards conformance.
The ISO 26262 safety standard, first published in 2011, aims to provide the guidance and has been generally well received throughout the automotive community. Enforcement, however, is lacking, as governments have yet to issue an ISO 26262 mandate. Thought leaders in the automotive industry, including some OEMs, Tier-1s, and Tier-2s, view ISO 26262 compliance as an internal mandate and goal in order to meet the challenging safety demands of ADAS and other systems. At a minimum, obtaining expertise in ISO 26262 and demonstrating both an ability to meet the highest level (ASIL D) as well as choosing suppliers that can do the same (e.g. via independent assessment by TUV) put themselves at a competitive advantage.
A developer can write perfect software only to still have it fail if the software’s compiler fails to correctly translate source code into machine code. ISO 26262 addresses the use of software development tools for the creation of safety-critical software, requiring tools qualification by a combination of pedigree (confidence from use), evaluation of the tool supplier’s development process, and validation of the tool’s functionality). Tools classified at the highest tool qualification level, T3, generate outputs that contribute to the executable code of a safety-related system. While a number of compiler vendors claim a certifiable compiler or qualification package that