4.9.3. AUTOSAR Compliance Checking Guide

Similar to the MISRA rules, Axivion Suite can be used to check your code’s compliance with the AUTOSAR C++14 coding guidelines. These checks are implemented as style checks.

Configuration and support for deviations are the same as for the MISRA checks.

A few AUTOSAR checks require special configuration:

  • Rule AutosarC++-A1.4.1: Code metrics and their valid boundaries shall be defined, and the code shall comply with defined boundaries of code metrics.
    To check metrics, use the Metric rules and configure them as needed.

  • Rule AutosarC++-A9.6.1: The types used to interface with hardware or to conform to communication protocols must be provided to the rule. By default, all POD types are considered by the rule. To check only user-provided types, disable the check_pod_types option. This option is available for AutosarC++18_10-A9.6.1 and AutosarC++19_03-A9.6.1 only.

  • Rule AutosarC++-A16.2.2: Due to differences in system headers, the rule produces different messages depending on the platform and libraries used. As a result, the examples provided in the AUTOSAR documents may not be reproducible in your particular environment. To adapt the rule to your needs, you may wish to change the default configuration or disable certain messages completely.

  • Rule AutosarC++-A17.0.2: All project code, including used libraries (both standard and user-defined) and any third-party code, shall conform to the AUTOSAR C++14 Coding Guidelines.
    To check libraries used in your project, simply apply all the rules to the source code of these libraries. (Binary analysis is not supported).