Reaching ASPICE Compliance with Axivion

SWE.5 – Software Integration and Integration Test

In the SWE.5 Software Integration and Integration Test process, the software units are combined into larger units up to the complete integration of the entire software.

From the point of view of Axivion Suite, the focus here is on analytical proof of compliance with the software architecture (Architecture Compliance Check). In this phase, the complete (and thus linked) software is analysed and compliance with a specified architecture is monitored. If this architecture is available as a development artefact, compliance with the architecture by the implementation can be easily checked by using the architecture verification of Axivion Suite.

But projects without an existing architecture definition also benefit from the capabilities of architecture verification. In this case, instead of an existing architecture model, the process starts with an architecture hypothesis. Through iterations, the hypothesis is refined further and further and compared with the reality in the source code. Deviations in the source code that clearly come to light in this process can then be corrected in the code in the further course of development. This architecture recovery process creates an architecture model that can be used as a validated architecture specification that must be fulfilled.

As described above, the results can be output both at the developer’s or software architect’s workplace and in reports. The Architecture Check is therefore ideally suited for integration into a CI workflow.

With its analysis capabilities, i.e. the unit check for MISRA and AUTOSAR C++14 compliance and the test for architecture compliance as part of the integration test, Axivion Suite contributes to achieving ASPICE compliance when integrated into your processes.