4.6.3. AUTOSAR Compliance Checking Guide

As with the MISRA rules, the Axivion Suite can be used to check compliance of your code with AUTOSAR C++14 coding guideline rules. These checks are implemented as stylechecks.

Configuration and support for deviations is 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 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 used to conform to communication protocols need to be provided to the rule. By default, all POD-types are considered by the rule. In order to only check the user-provided types, the option check_pod_types needs to be disabled.

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

• Rule AutosarC++-A17.0.2: All project’s code including used libraries (including standard and user-defined libraries) and any third-party user 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. (We do not support binary analysis).