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

4.3.10 ENG.10 System testing

Process ID

ENG.10

Process Name

System testing

Process Purpose

The purpose of the Systems testing process is to ensure that the implementation of each system requirement is tested for compliance and that the system is ready for delivery.

Process Outcomes

As a result of successful implementation of this process :

  1. a strategy is developed to test the system according to the priorities of and categorization the system requirements;

  2. a test specification for system test of the integrated system is developed that demonstrates compliance with the system requirements;

  3. the integrated system is verified using the test cases;

  4. results of system testing are recorded;

  5. consistency and bilateral traceability are established between system requirements and the system test specification including test cases; and

  6. a regression test strategy is developed and applied for re-testing the integrated system when a change in system elements is made.

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

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

Base Practices

ENG.10.BP1: Develop system test strategy. Develop the strategy for system testing consistent with the release strategy. [Outcome 1]

ENG.10.BP2: Develop test specification for system test. Develop the test specification for system test, including the test cases, to be executed on the integrated system. [Outcome 2]

NOTE 1: The System testing process should start early in the system development life cycle. There is a close link to System Requirements Analysis ENG.2, System architectural design ENG.3 and Requirements Elicitation ENG.1 in developing test cases and testable requirements.

NOTE 2: The test cases should demonstrate compliance to the system requirements over the complete range of allowed application parameter combinations.

ENG.10.BP3: Verify integrated system. Verify the integrated system against the test cases for system testing and according to the system test strategy. [Outcome 3]

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

NOTE 4: Tests should be automated as far as possible having regard to efficiency.

ENG.10.BP4: Record the results of system testing. Document the results of system testing and communicate to all relevant parties. [Outcome 4]

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

ENG.10.BP5: Ensure consistency and bilateral traceability of system requirements to the systems test specification. Ensure consistency of system requirements to the systems test specification including test cases. Consistency is supported by establishing and maintaining bilateral traceability between the system requirements and system test specification including test cases. [Outcome 5]

NOTE 6: Consistency can be demonstrated by review records.

ENG.10.BP6: Develop system regression test strategy and perform testing. Develop the strategy for re-testing the integrated system if a system element is changed. If changes are made to system elements, carry out regression testing as defined in the system regression test strategy, and record the results. [Outcome 6]

Output Work Products

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

08-50 Test specification [Outcome 2]

13-50 Test result [Outcome 3, 4]

13-22 Traceability record [Outcome 5]

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