Fleckner und Simon Informationstechnik GmbH              http://www.FlecSim.de

4.3.7 ENG.7 Software integration test

Process ID

ENG.7

Process Name

Software integration test

Process Purpose

The purpose of the Software integration test process is to integrate the software units into larger assemblies, producing integrated software consistent with the software design and to test the interaction between the software items.

Process Outcomes

As a result of successful implementation of this process:

  1. a software integration and integration test strategy is developed for software items consistent with the software design according to the priorities and categorization of the software requirements;

  2. a test specification software integration is developed that ensures compliance with the software architectural design, software detailed design, allocated to the items;

  3. software units and software items are integrated as defined by the integration strategy;

  4. integrated software items are verified using the test cases;

  5. results of software integration testing are recorded;

  6. consistency and bilateral traceability are established between software architectural design and software detailed design to software integration test specification including test cases; and

  7. a regression strategy is developed and applied for re-integrating and re-verifying software items when a change in software items (including associated requirements, design and code) occurs.

NOTE 1: The test specification for software integration includes the test design specification, test procedure specification and test case specifications.

NOTE 2: The test results for software integration include the test logs, test incident reports and test summary reports.

Base Practices

ENG.7.BP1: Develop software integration strategy. Develop the strategy for integrating software items consistent with the release strategy and an order for integrating them. [Outcome 1]

ENG.7.BP2: Develop software integration test strategy. Develop the strategy for testing the integrated software items. Identify test steps according to the order of integration defined in the integration strategy. [Outcome 1]

NOTE 1: The Software integration test will focus mainly on interfaces, data flow, functionality of the items etc..

NOTE 2: The Software integration test should verify that only allowed application parameter combinations can influence functionality and that wrong parameter or parameter combinations are failsafe.

NOTE 3: The Software integration test process should start with the beginning of the software development process There is a close link from Software Requirements Analysis ENG.4, Software Design ENG.5 or Requirements Elicitation ENG.1 in developing test cases and testable requirements.

NOTE 4: The software integration strategy contains different approaches of integrating software items depending of the changes (e.g. new units, changed units). The integration strategy also includes the most suitable test methods to be used for each integration approach.

NOTE 5: The identified items and the order of integration will have an influence on integration test strategy.

ENG.7.BP3: Develop test specification for software integration test. Develop the test specification for software integration test including test cases, to be executed on each integrated software item. The test cases should demonstrate compliance to the software architectural design and software detailed design allocated to each software item. [Outcome 2]

ENG.7.BP4: Integrate software units and software items. Integrate the software units to software items and software items to integrated software according to the software integration strategy. [Outcome 3]

NOTE 6: Software units are integrated to software components and software components to integrated software.

NOTE 7: The integration of the software units and software components also integrates their data. Data can be calibration data and variant coding data.

ENG.7.BP5: Verify the integrated software. Verify each integrated software item against the test cases for software integration test according to the software integration test strategy. [Outcome 4]

NOTE 8: Verification of the integrated software produces the test logs.

ENG.7.BP6: Record the results of software integration testing. Document the results of software integration testing and communicate to all relevant parties. [Outcome 5]

NOTE 9: The test incident reports and the test summary report are based on the test logs.

ENG.7.BP7: Ensure consistency and bilateral traceability of software architectural design and software detailed design to software integration test specification. Ensure consistency of software architectural design and software detailed design to software integration test specification including test cases. Consistency is supported by establishing and maintaining bilateral traceability between software architectural design and software detailed design to software integration test specification including test cases. [Outcome 6]

ENG.7.BP8: Develop regression testing strategy and perform regression testing. Develop the strategy for re-testing the software items if changed software items are integrated. Perform regression testing as defined in the regression test strategy and document the results. [Outcome 7]

Output Work Products

08-52 Test plan [Outcome 1, 2, 7]

08-50 Test specification [Outcome 2]

13-50 Test result [Outcome 4, 5]

13-22 Traceability record [Outcome 6]

17-02 Build list [Outcome 3, 6, 7]

01-03 Software item [Outcome 3]

01-50 Integrated software [Outcome 3]

NOTE: For software and system test documentation, the IEEE-Standard 829- 2008 might be used.

 

5.Process Capability Indicators

Level 2: Managed process

Level 3: Established process

Level 4: Predictable process

Level 5: Optimizing process