Architecture verification aims at getting your architecture and design in sync with your code.
Only then you are sure you can use the architecture as a guideline for discussing the impact and gravity of new features and thus the evolution of your products. That is what architecture is meant for.
Architecture conformance is key to success in the long run.
The AUTOSAR C++14 coding rules aim at making safety critical systems safer by flagging issues in the code. This enables developers to grind away inherently unsafe and insecure ways of coding C and C++.
Our AUTOSAR C++14 checker covers all automatically checkable rules for AUTOSAR C++14 (17.03, 17.10, 18.03, 18.10 and 19.03).
The MISRA coding rules aim at making safety critical systems safer by flagging issues in the code. This enables developers to grind away inherently unsafe and insecure ways of coding C and C++.
Our MISRA checker covers 100 per cent of the automatically checkable rules for MISRA C:2004, MISRA C:2012 (including Amendment 1 security rules and Amendment 2) and MISRA C++:2008.
Our MISRA checks seamlessly integrate into IDEs and CI environments allowing for easy integration into your processes ranging from local checks up to full-fledged automated CI checks with the very same configuration and the very same results.
Software erosion happens every day. Therefore, stopping software erosion effectively means a tight integration into your build environments and processes – in the environment of your DevOps toolchains and a developer's workplace.
The standard Axivion Suite setup supports central server infrastructures as well as a decentralized local analysis.
Axivion Suite delivers the results from nightly analysis directly to your IDEs. For fast responses, code changes and their impact can be analyzed locally to different degrees prior to the integration of the changes into upstream development.
The ISO 26262 series of standards is the adaptation of IEC 61508 series of standards to address the sector specific needs of electrical and/or electronic (E/E) systems within road vehicles.
The achievement of functional safety is influenced by the development process (including such activities as requirements specification, design, implementation, integration, verification, validation and configuration), the production and service processes and the management processes.
Axivion Suite supports especially compliance with ISO26262-6:2018 - Product development at the software level.
Axivion Suite supports the development of Software for Medical Devices for all severity levels.
In the development process Axivion Suite supports you during the Software architectural design and detailed design with Axivions Architecture Verification. During Software verification and testing on unit, integration and system level Axivion Suite supports you with checks for MISRA C, MISRA C++, AUTOSAR C++14, CERT or custom coding rules specific for your environment.
Axivion Suite integrates with almost any CI-System which allows for repeatable and comparable analysis of software.
The CERT C coding rules aim at making safety critical systems more secure by flagging security issues in the code. This enables developers to grind away inherently insecure ways of coding C and C++.
Our CERT C checker covers a lot of decidable rules that do not need human interpretation of the rules and seamlessly integrates into IDEs and CI environments.