2. Project Configuration¶
A “project” corresponds to exactly one system under analysis. For a complete analysis of a project’s source code, the Axivion Suite analysis software must be integrated with the project’s build system, the version control system and the infrastructure presenting the results from the analysis. This is done by setting up suitable project configuration files. In addition, there are many user options that allow the erosion analysis to be customized.
The Axivion Suite is highly configurable allowing you to
integrate it into your existing build infrastructure
select, customize and fine-tune suitable analysis steps
add custom analysis steps.
The configuration can be split into multiple files. This allows reusing parts of the configuration in multiple projects, or separating configuration aspects done by different people (e.g., separating architecture configuration as done by the architect from code annotation configuration).
Starting from version 7.3 of the Axivion Suite, all these aspects are covered by a
single configuration system based on JSON files that can be created and edited using a
graphical user interface named axivion_config. These
JSON files can be complemented by manually written Python files, in which the
configuration state can be changed programmatically.
When setting up a new project, it is recommended to configure as much as possible using the GUI, and fall back to Python only where you need the power of a programming language, or where the GUI does not support the type of an option that you want to access.