Axivion – Static Code Analysis with Architecture verification

High-end static code analysis to stop software erosion, detect places in code that has high risk to appear as a Bug, reduce code complexity, find code that is 100% dead code, and much more…

Axivion is now part of QT group.

With the *defect analysis* feature , you can identify weaknesses in your software project. With the *metrics* you can generate quantitative information about the internal quality and complexity of your code. with *style checks* you can achieve compliance with the *coding guidelines* you choose. In addition to the predefined compliance checks for MISRA C, AUTOSAR C++14, CERT, CWE or Metrics like HIS and McCabe, and tracking *memory leaks* and *dead code*, you can also set and check your own rules with the Axivion Suite’s rule editor.

This and more – the tool can find if your code follows the software architecture and help you build one if you don’t have any. *Architecture verification*

you can learn more about these features here: AxivionSuite_Overview

Press here to go to the Axivion (QT) website.

Support C, C++, C#

Coding Guidlines:

• MISRA C/C++
• AUTOSAR C++14
• SEI CERT® C/C++
• C Secure Coding
• CWE
• Qt-specific rule sets
• Best practice (e.g. CQM)
• Customized checks

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.

Defect analysis: By identifying potential defects and coding errors early in the development cycle, Axivion can help minimize the risk of software malfunctions that could lead to patient harm, which is a key tenet of IEC 62304.
Compliance with Coding Standards: Axivion can be configured to check code against industry coding standards relevant to medical device development, such as MISRA C/C++ or CERT Secure Coding. Following these standards can help improve code quality and reduce the likelihood of errors, which aligns with IEC 62304’s emphasis on safe and reliable software.
Improved Maintainability: By identifying code smells and complexities, Axivion can help developers write cleaner and more maintainable code. This can be crucial for medical device software, where long-term maintenance and support are essential. Easier to understand code reduces the risk of introducing errors during modifications, which is a concern for IEC 62304 compliance.

While Axivion might not directly manage document control or workflows, it plays a significant role in ensuring code quality and reducing errors, which indirectly contributes to achieving IEC 62304 compliance.

Architecture verification

• Integrated modeler
• Interfaces to UML tools
• AUTOSAR XML import (ARXML)
• Freedom from Interference
• Architecture reconstruction
• Architecture views for safety and security
Coding guidelines
• MISRA C/C++
• AUTOSAR C++14
• SEI CERT® C/C++
• C Secure Coding
• CWE
• Qt-specific rule sets
• Best practice (e.g. CQM)
• Customized checks

Metrics monitoring

• HIS
• OO Design metrics
• Complexity metrics
• Best practice and customized checks
Dead code analysis
• Reachability analysis
• Analysis of libraries

Clone Detection
• Type I (1:1)
• Type II (Parametrizations)
• Type III (Parametrizations + Add/Delete)

Cycle detection

• Calls
• Module dependencies
• Includes/Imports
• Customized checks

Defect detection

• NULL dereferences
• Escaping addresses of local variables
• Memory leaks from new/malloc without delete/free
• Mismatched resource allocations/releases
• Resources used for reading/writing at the same time
• Forbidden operations on resources
• Double free/use after free
• Comparison/subtraction of unrelated pointers
• Array access out of bounds
• Buffer overflow
• Side effects
• Taint analysis
• Race condition analysis

Exceptions

• Exceptions during stack unwinding
• Violations of exception specifications
• Uncaught exceptions
• Dead catch blocks
Numerical errors
• Divisions by zero
• Overflow in arithmetic computation
• Assignment of bad values to enum-typed variables
Logical errors and customized rules
• Forbidden argument values
• Uninitialized variables
• Unused definitions
• Constant conditions

Results appear on a special dashboard and/Ot on the IDE of the user:

Qt Creator, CLion, EclipseTM, Eclipse-based (e.g. Atollic TrueSTUDIO®, CodeWarrior®, DAVETM, STM32CubeIDE,
TI Code Composer StudioTM), Microsoft® Visual Studio®, Microsoft® Visual Studio Code®, Generic plugins

Axivion Suite is suited for use in the development
of safety systems. Axivion Static Code Analysis
(SCA) is certified by SGS-TÜV Saar GmbH for the
following safety-relevant standards:

• ISO 26262 (up to ASIL-D)
• IEC 61508 (up to SIL 4)
• EN 50128 (up to SIL 4)
• EN 50657 (up to SIL 4)
• IEC 62304 (up to Class C)

As well as DO-178C