After importing, the graph of the model can be immediately compared with the graph of the implementation obtained from an Axivion code analysis. As a result, convergence occurs when the model and implementation agree. Absences result from excess relationships in the model that are not implemented in the implementation. Finally, if there are excess relationships in the implementation, divergences arise, which then indicate problems in the code.
Implementation and architecture can now be brought into agreement in an iterative process. Once the architecture review has become an integral part of the CI process , you can avoid relapses. Any architectural violations that arise are discovered immediately and can be discussed and resolved at an early stage. Compliance with the specified architecture in the code is thereby ensured, further architectural erosion is stopped and architectural debts can be remedied by using targeted refactoring measures that can be directly monitored via the results of the architecture check.
