Autosar_1.jpg

Making your C and C++ code safer with AUTOSAR

What is the AUTOSAR coding standard and why should my team care?

The AUTOSAR coding standard was created by an alliance of hundreds of automotive manufacturers, developers, and suppliers. Formerly called “Guidelines for the use of the C++14 language in critical and safety-related systems”, the standards consists of nearly 400 requirements that industry experts agree will mitigate bugs, remove inconsistencies and clarify C++ code. If you are part of the automotive industry, compliance is likely mandatory. However, due to the complexity of modern software systems, most teams will benefit by having a concrete coding standard in place, such as AUTOSAR.

It seems overwhelming, what tools are available to help?

Parasoft, Perforce, and Synopsis each have proved static-analysis tools that help teams adopt coding standards such as MISRA and AUTOSAR. Many of our customers happily use these tools in conjunction with Understand, our code comprehension offering. However, these tools can be quite expensive, and many of our customers have asked for an alternative at a fraction of the cost. We are proud to announce Understand will now help your team become AUTOSAR compliant with a much lower barrier of entry than our competitors, both in time and cost.

What AUTOSAR standards does Understand check?

Understand has checkers for 94% of the AUTOSAR checks that can be automated which is one of the best rates in the industry. Check out the full list of AUTOSAR checkers.

How can I check my code for compliance?

You can get started right away, no need to talk to a sales team first, or get your IT team to set up a server.

Just download a free trial of Understand, point it at your code to create an Understand project (remember the more accurate your project the more accurate the analysis) and launch the CodeCheck tool and select AUTOSAR.

The full text for each check is included in Understand so the user can know exactly what is required by each rule or guideline.

You can analyze the whole project at once (which may take a while), or limit the analysis to a specific file or directory.

Violations can be viewed individually in the code, collectively in reports, or graphically in a Treemap view. You can also implement the analysis into your DevOps/CI system using our command line tools or Jenkins.

Quickly see violations along with the corresponding code

The size shows the distinct kinds of violation in each file, the darkness shows the number of violations.