ISO 26262 is an international standard for functional safety that governs software safety requirements for all automotive product development processes. Although adapted from IEC 61508, modern regulations have become more stringent in terms of compliance. Therefore, depending on the function of the automotive product, a compliance level is required.
You can read more about ISO 26262 and Parasoft on compliance here, let’s first discuss how to achieve ASIL-D compliance. After all, this is the most difficult aspect of ISO 26262 compliance to achieve.
What is the ISO 26262 standard?
Many Parasoft articles, white papers and webinars cover ISO 26262, primarily because of the standard's importance in terms of automotive safety. It can be broken down into several key concepts.
-
A standard that provides OEMs with guidance on automotive software safety lifecycle activities.
-
Including security analysis, requirements analysis, quality management, verification, confirmation, etc.
-
Consists of 12 sections covering vocabulary, lifecycle, development protocols, and other important aspects of ISO 26262 compliance.
The reason why the ISO 26262 standard is so important is simple. It keeps us safe in our cars.
What is ASIL AD?
ASIL, the Automotive Safety Integrity Level, classifies the functional safety risks of road vehicles. Different parts of a car have different ASIL ratings. If a product is grade A, it ranks lower in safety standards. If they are Class D, the software and/or hardware must adhere to the strictest safety standards.
Products like rear lights and even dashboards are not above ASIL-B or above. Electric steering and ABS brakes are listed as ASIL-D in terms of safety compliance because of their significant impact on vehicle operation. Meeting these requirements requires the use of solutions like Parasoft C/C++test to ensure compliance.
What are the requirements for ASIL-D?
The risk classification in this section corresponds to the highest level. Any system or component that meets ASIL-D specifications requires a high degree of risk mitigation. Generally speaking, developers consider 3 key deciding factors when considering ASIL-D compliance.
The seriousness of the incident. How will passengers, drivers, and nearby people and vehicles be affected if a failure occurs? How severe will the damage be?
Possibility or frequency of exposure. How likely is it that something that could lead to failure is sent?
Fault controllability. If a system or product ultimately fails, developers must consider the reasons for the failure. Perhaps you can avoid undue damage through quick responses or fail-safe measures.
The diagram above details exactly the safety requirements for ASIL-D. The biggest challenge developers face when trying to achieve ASIL-D compliance is how many assumptions they have to make when developing a product or service.
What are the requirements for ASIL-D?
Meeting ASIL-D safety features requires several tests to help expose, prevent and fix any errors. Parasoft C/C++test helps eradicate these problems through the following features:
unit test. Help the team develop, execute, optimize and maintain unit tests.
Static analysis. Perform data flow analysis, control flow analysis, metrics analysis, and more.
Requirements traceability. Link tests and code to requirements for better visibility.
Code coverage. Shows what code was executed using a test run.
Runtime error. Find memory leaks, access errors, corruption, and more.
The way you implement these elements doesn't have to be difficult or inefficient. In fact, Parasoft C/C++ software development solutions make the development process smoother, faster, and more accurate.
Benefits of Parasoft C/C++test
Automated code analysis
Allows for compliance monitoring at any time. Take advantage of hundreds of embedded rules such as MISRA C:2008, AUTOSAR C++14, MISRA C:2012 and more. The graphical RuleWizard editor allows users to customize rules.
Identify errors without execution
Ability to find problems without executing code. In fact, for things like embedded code, thorough runtime analysis of errors becomes both possible and efficient.
Enhanced code review
In order to find code defects, all teams should conduct code reviews. It does take a lot of work, but Parasoft DTP Change Explorer helps make the process more convenient.
Integration and unit testing with coverage analysis
Automation is critical if you want to make your compliance agreements more agile and effective. Specific GUI widgets simplify test management and creation. The test case wizard even enables developers to quickly conduct black-box functional testing on different feature sets without worrying about embedded data dependencies. What's more, the data source wizard parameterizes the test cases and stubs, which you can view in the stubs view.