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

4.3.9 ENG.9 System integration test

Process ID

ENG.9

Process Name

System integration test

Process Purpose

The purpose of the System integration test process is to integrate the system elements to produce an integrated system that will satisfy the system architectural design and the customers’ expectations expressed in the system requirements.

Process Outcomes

As a result of successful implementation of this process:

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

  2. a test specification for system integration test is developed to verify compliance with the system architectural design, including the interfaces between system elements;

  3. an integrated system is integrated as defined by the integration strategy;

  4. the integrated system elements are verified using the test cases;

  5. results of system integration testing are recorded;

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

  7. a regression strategy is developed and applied for re-testing the system elements when changes are made.

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

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

Base Practices

ENG.9.BP1: Develop system integration strategy. Develop the strategy for integrating the hardware, mechanics and software consistent with the release strategy and an order for integrating them. [Outcome 1]

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

NOTE 1: The System integration test will focus mainly on interfaces, data flow, functionality of the system elements etc..

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

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

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

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

ENG.9.BP3: Develop a test specification for system integration. Develop the test specification system integration, including the test cases, to be executed on each integrated system element. The test cases should demonstrate compliance to the system architectural design. [Outcome 2]

ENG.9.BP4: Integrate system elements. Integrate the system elements to an integrated system according to the system integration strategy. [Outcome 3]

NOTE 6: The system integration can be performed step wise integrating the hardware elements as prototype hardware, peripherals (sensors and actuators), the mechanics and integrated software to produce a system consistent with the priorities and categorization of the system requirements.

ENG.9.BP5: Verify the integrated system. Verify each integrated system element against the test cases for system integration according to the system integration test strategy. [Outcome 4]

NOTE 7: Verification of the integrated system produces the test logs.

NOTE 8: Verification of the integrated system can be supported using environment simulation methods (e.g. Hardware-in-the-Loop- Simulation, vehicle network simulations).

ENG.9.BP6: Record the results of system integration testing. Document the results of system 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.9.BP7: Ensure consistency and bilateral traceability of system architectural design to the system integration test. Ensure consistency of system architectural design to the system integration test specification including test cases. Consistency is supported by establishing and maintaining bilateral traceability between the system architectural design and system integration test specification including test cases. [Outcome 6].

ENG.9.BP8: Develop regression testing strategy and perform regression testing. Develop the strategy for re-testing the system elements if changed hardware, mechanics or software or 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]

11-06 System [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