ISO 26262 Software Compliance in the Automotive Industry

AUTOSAR C++14 Compliance

AUTOSAR C++14 does not provide explicit guidance on the process of achieving compliance. However, given that AUTOSAR C++ 14 guidelines are based on MISRA C++ 2008, it’s reasonable to refer to the MISRA compliance guidelines for guidance on achieving compliance.

The desired situation is to have a static analysis tool that covers as many guidelines as possible. The rules that cannot be enforced with static analysis will require manual reviews, which are expensive.

As with MISRA C compliance, a deviation handling procedure needs to be established. The deviation procedure formalizes the steps that need to be taken when development needs to deviate from a specific guideline. As MISRA prescribes, it’s expected that “…the procedure will be based around obtaining a sign-off for every deviation or class of deviations.”

This is a particularly important piece of the puzzle. It prevents abusing the deviation concept by developers deviating at will. Effectively, you’ll need formal tickets stored in your system that document every deviation in the source code. The same pertains to the compliance matrix and any additional configurations and process descriptions created to enforce compliance. MISRA C++2008 is truly clear here and requires “formalization within quality system.”

Finally, if all the procedures described in MISRA C++ 2008 point 4.3 are in place for AUTOSAR C++14, we can claim compliance by demonstrating:

• A compliance matrix has been completed that shows how compliance has been enforced.
• All the C++ code in the product is compliant with the rules of AUTOSAR C++ 14 document. If not, they are documented deviations.
• A list of all instances of the rules not being followed is maintained and for each instance, there is an appropriately signed-off deviation.

Support for AUTOSAR C++14 in Parasoft C/C++test

The only practical way to enforce compliance with a coding standard like AUTOSAR C++14 is with a static analysis tool, like Parasoft C/C++test, a code quality tool supporting multiple testing technologies. Parasoft C/C++test support for AUTOSAR C++14, provides a set of built-in checkers (rules) for verifying compliance with standards including MISRA C 2023, MISRA C++ 2023, MISRA C 2012, MISRA C++ 2008, JSF AV C++, SEI CERT C/C++, HIC++, CWE Top 25, CWE On the Cusp, OWASP, and more.

Parasoft compliance packs provide users with standard specific configurations, automatic generation of compliance documentation, risk assessment framework, and dynamic compliance reporting dashboards (DTP) to help stakeholders easily aggregate, correlate, and apply analytics to centralize reporting for each step along the complex software supply chain.

With the 100% coverage for Required & Automated rules, Parasoft testing tool suite ensures AUTOSAR compliance throughout the software development life cycle, improves code quality, and reduces cost associated with resources and time to market.