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

4.3.8 ENG.8 Software testing

Process ID

ENG.8

Process Name

Software testing

Process Purpose

The purpose of the Software testing process is to confirm that the integrated software meets the defined software requirements.

Process Outcomes

As a result of successful implementation of this process:

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

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

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

  4. results of software testing are recorded;

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

  6. a regression test strategy is developed and applied for re-testing the integrated software when a change in software items occur.

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

NOTE 2: The verification is performed according to the test cases

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

Base Practices

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

ENG.8.BP2: Develop test specification for software test. Develop the test specification for software test including test cases, to be executed on the integrated software. The test cases should demonstrate compliance to the software requirements. [Outcome 2]

NOTE 1: The Software testing process should start early in the software development life cycle. There is a close link from Software Requirements Analysis ENG.4, Software Design ENG.5 and Requirements Elicitation ENG.1 in developing test cases and testable requirements.

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

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

NOTE 3: Verification of the integrated software produces the test logs

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

ENG.8.BP4: Record the results of software testing. Document the results of software 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.8.BP5: Ensure consistency and bilateral traceability of software requirements to software test specification. Ensure consistency of software requirements to software test specification including test cases. Consistency is supported by establishing and maintaining bilateral traceability between the software requirements and software test specification including test cases. [Outcome 5].

NOTE 6: Consistency can be demonstrated by review records.

ENG.8.BP6: Develop regression test strategy and perform regression testing. Develop the strategy for retesting the integrated software should a software item be changed. If changes are made to software items carry out regression testing as defined in the software 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