SWE.5 – Software Integration and Integration test

---

Hi everyone,
its time to continue the A-SPICE series with the upcoming SWE.5 process. Last time we had a look onto the SWE.4 – Software Unit Verification process.

ID: SWE.5
Process name: Software Integration and Integration Test
Process purpose: The goal of the process for software integration and integration testing is to combine individual software units into larger components until a fully integrated software system is achieved, consistent with overall software architecture. The process also verifies that the integrated software components conform to the software architecture, including the interfaces between software units and components, by conducting appropriate testing to provide evidence of compliance.
Process outcomes: We were successful if:

• a consistent software integration strategy with the release plan, project plan and the software architectural design is developed to integrate the software items;
• a software integration test strategy including regression test strategy is developed interaction between software items & units
• a software integration test specification has been created in accordance with the software integration test strategy. This specification is designed to provide proof of compliance of the integrated software components with the software architectural design, which includes the interfaces between the software units and the software items.
• according to the integration strategy the software units & items are integrated up to a complete integrated software.
• the within software integration test specification included Test Cases are chosen in accordance to the software integration test strategy and release plan.
• integrated software items undergo testing using the chosen Test Cases, and the outcomes of the software integration test are documented
• established consistency and bidirectional traceability between the elements of the software architectural design and Test Cases within the software integration test specification and between Test Cases and test results; and
• outcomes of the software integration test are summarized and communicated to all relevant parties

Base practices:

SWE.5-BP.1: Develop software integration strategy
As a first step we start to craft a comprehensive approach to seamlessly incorporate software elements in line with the project and release plans. Determine the software components by analyzing the software architectural design and establish a logical order for their integration. So if we try to simplify it. That´s the picture I get:

SWE.5-BP.2: Develop software integration test strategy including regression test strategy
Formulate a testing strategy for the integrated software components in accordance with the integration strategy. This encompasses the development of a regression test strategy to ensure thorough re-testing of integrated software items in the event of any changes to individual software components.

SWE.5-BP.3: Develop specification for software integration test
Create a test specification for the software integration test, which encompasses the development of test cases based on the software integration test strategy for each integrated software item. The test specification should serve as valid evidence, ensuring compliance of the integrated software items with the software architectural design.
Notes also stress that the compliance to the architectural design indicates that the defined integration tests are suitable to ensure the interfaces in-between software units and software items are fulfilled by the specification (software architectural design). It also hints that the focus of software integration test cases may be on:

• right dataflow between software items
• timeliness & timing dependencies of the dataflow between software items
• right interpretation of data by the use of an interface and its using software items
• dynamic interaction between software items
• compliance to resource consumption objectives of interfaces

SWE.5-BP.4: Integrate software units and software items
To ensure a smooth integration process, it is crucial to effectively integrate software units into software items and further combine these software items into integrated software. This integration should be carried out in alignment with the software integration strategy, which outlines the systematic approach for merging different software components. By following this strategy, the integration process can be streamlined, allowing for efficient collaboration and seamless functionality across the software system.

SWE.5-BP.5: Select test cases
Now based on the software integration test specification we choose our test cases. This set of test cases shall have sufficient coverage according to the software integration test strategy and release plan.

SWE.5-BP.6: Perform software integration test
Conduct the software integration test by employing the designated test cases. Document the outcomes and logs of the integration test.
In case of any non-conformances we should check for SUP.9 Problem Resolution Management. Also testing activities can be supported by hardware debug interfaces or environment simulations (SIL)

SWE.5-BP.7: Establish bidirectional traceability
Based on our activities we now need to ensure that everything is related/connected properly. This also supports the knowledge for impact, consistency and coverage.
That means we need the following connections:

• Software architectural design elements – Software integration test specification test cases
• Software integration test specification test cases – Software integration test results

SWE.5-BP.8: Ensure consistency
To fulfil that we need to provide a consistency between

• Software architectural design elements – Software integration test specification test cases

SWE.5-BP.9: Summarize and communicate results
Summarize the software integration test results and provide a communication to all affected parties. This will help the stakeholders to get an understanding on possible consequences.

I hope this was a bit of help for you.
Next Up will be:

• SWE.6 Software Qualification Test

Thank You