Misra_transparent_BG (1)

MISRA Checker

Achieve compliance in critical systems according to MISRA C:2004, MISRA C:2012, MISRA C:2019, MISRA C:2023 and MISRA C++:2008 and MISRA C++:2023

Do you need to switch to MISRA C:2023/MISRA C++:2023? Or want to know how to get started?

Contact Us

Comply with MISRA Coding Guidelines When Developing Safety-Critical Software

The various versions of the MISRA Guidelines for the use of the C and C++ languages in critical systems were and are developed by the MISRA consortium. MISRA stands for Motor Industry Software Reliability Association.

The original focus of the MISRA standards is therefore on the development of safety-relevant and reliable software in the automotive environment and thus within the scope of ISO 26262. Compliance with the MISRA guidelines is regularly required for software development in all industries throughout the embedded sector, especially when it comes to functional safety. By applying the generally accepted MISRA rules, code quality is controlled along the supply chain.

The MISRA checker of the Axivion Suite covers 100% of the automatically testable rules for MISRA C:2004, MISRAC:2012, MISRA C:2019, MISRA C:2023 and MISRA C++:2008 as well as the majority of the rules for MISRA C++:2023.

Certified to Ensure Compliance

Axivion Suite’s MISRA checker has been certified by SGS TUEV Saar for use in software projects with safety requirements according to ISO 26262 up to ASIL D, IEC 61508 up to SIL 4, IEC 62304 up to Class C.


Achieve MISRA Compliance Through Simple Process Integration into Safety Quality Management

Axivion Suite provides you with central building blocks for your Safety Quality Management, especially if you want to - or have to - adhere to the procedures outlined by MISRA.

Misra_check_BG (1)
  • The customisable severity classification of rules and rule groups allows you to prioritise your work and categorise the rules in a MISRA-compliant way. MISRA categorises the rules it contains as mandatory, required or advisory. To be MISRA-compliant, rules marked as mandatory must not be violated. If justifications exist, a rule categorised as required may be deviated from. MISRA provides a documented process for this.
  • By means of justifications in the code or in external files, deviations from the MISRA rules can be handled in a structured and systematic way in the work process in order to develop in conformity with the standards. MISRA justifications and permissions can be specified directly.
  • By applying different delta intervals, progressions over the development can be observed and evaluated. In addition, the delta analysis can be used to make the achievement of targets such as “do not introduce new findings” transparent.
  • Automatically generated reports on the MISRA compliance of your code make documentation easier.

Request a Demo


Contact Us

Learn More About Axivion


Read More

Download the Brochure


Read More