AUTOSAR C++14 Compliance

for AUTOSAR C++14 (17.03, 17.10, 18.03, 18.10, and 19.03)

The AUTOSAR C++14 coding rules aim at making safety critical systems safer by flagging issues in the code. This enables developers to grind away inherently unsafe and insecure ways of coding C and C++.

Our AUTOSAR C++14 checker covers all decidable rules that do not need human interpretation of the rules for AUTOSAR C++14 (17.03, 17.10, 18.03, 18.10 and 19.03).

Our AUTOSAR C++14 checks seamlessly integrate into IDEs and CI environments allowing for easy integration into your processes ranging from local checks up to full-fledged automated CI checks with the very same configuration and the very same results.

Using the AUTOSAR C++14 coding rules

Use the severity of rules and rule groups to prioritize your work. Add justifications if deviations in the code are needed. Generate AUTOSAR C++14 conformance reports of your code.

Our unparalleled delta check keeps developers more focused on their daily job of creating safe code. During reviews, deviations introduced by sprints, releases, feature branches etc. can be easily witnessed. 

If you are in an ISO 26262 environment or similar safety standards such as IEC 61508 and so on, our Qualification Kit ensures confidence in using the tool in your environment and with your use cases up top the required ASIL level. 

Unleash the power of the Axivion Suite

Combine the AUTOSAR C++14 rules with other coding rule sets, e.g. MISRA C, MISRA C++, CERT, custom coding rules specific for your environment, and even results of other static code analyses.

Combine the code focus of the AUTOSAR C++14 rules with the architecture focus of our architecture verification.

As we believe that our customers pay maintenance fees for the development of new features, we are constantly adding new editions of MISRA and AUTOSAR coding standards as they emerge into our products.


Download AUTOSAR Fact Sheet

Success Stories

A selection of Success Stories about AUTOSAR C++14

Leuze electronic

Read Success Story