Only if architecture and design are in sync with your code 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.
The Axivion Suite gives you the full range of Axivion analysis tools in one box. The Axivion Suite includes static code analysis, architecture analysis and effective tools for the detection of code smells. For development in safety-oriented environments, the Tool Qualification Kit can also be added.
Code smells are indications that something is wrong in your software. Metaphorically speaking, it is giving off a somewhat unpleasant smell and this is an indication that you should invest in the internal code quality. Axivion helps you completely avoid these smells, similar to maintenance cleaning, as part of a CI strategy. But even if you take on an existing project, the Axivion Suite helps you locate unpleasant code smells and thus take action against them. The Axivion Suite helps you reliably detect and manage duplicated code across the entire project, detect cycles with inclusion of header files, as well as direct call cycles, regardless of the call depth and identify unreachable code.
The defect analysis checks the source code for potential runtime errors. The analyses include scalable data and control flow checks. These allow errors such as out-of-bounds access or division by zero to be detected early.
The Axivion Suite includes rule sets for lots of common software metrics. This includes metrics based on lines and tokens, nesting, cyclomatic complexity, control flow or golden oldies like Halstead metrics. Even whole rule sets like HIS are supported.
Axivion stellt innovative Software-Lösungen zur statischen Codeanalyse und Software-Architektur-Verifikation zum Schutz vor Software-Erosion her. Zu unseren Kunden zählen bekannte Unternehmen aus nahezu allen Industrien mit einem hohen Anspruch an Software-Qualität, Safety und Security.
With the defect analysis, you can identify weaknesses in your software project. With the metrics you can generate quantitative information about the internal quality of your software, and you can achieve compliance with the coding guidelines through the style checks. In addition to the predefined compliance checks for MISRA, AUTOSAR C++14, CERT, ISO/IEC TS 17961 or metrics like HIS and McCabe, and tracking memory leaks, you can also set and check your own rules with the Axivion Suite’s rule editor.
Is software development a boring, purely facts and figures based, rigid and sometimes painful undertaking? Where is the fun in it? Where does creativity fit in? How can the "software heroes" feed in great new ideas?