5.9 CSCI qualification testing.

The developer shall perform CSCI qualification testing in accordance with the following requirements.

Note 1: CSCI qualification testing is performed to demonstrate to the acquirer that CSCI requirements have been met. It covers the CSCI requirements in software requirements specifications (SRSs) and in associated interface requirements specifications (IRSs). This testing contrasts with developer-internal CSCI testing, performed as the final stage of unit integration and testing.

Note 2: If a CSCI is developed in multiple builds, its CSCI qualification testing will not be completed until the final build for that CSCI, or possibly until later builds involving items with which the CSCI is required to interface. CSCI qualification testing in each build should be interpreted to mean planning and performing tests of the current build of each CSCI to ensure that the CSCI requirements to be implemented in that build have been met.

5.9.1 Independence in CSCI qualification testing.

The person(s) responsible for qualification testing of a given CSCI shall not be the persons who performed detailed design or implementation of that CSCI. This does not preclude persons who performed detailed design or implementation of the CSCI from contributing to the process, for example, by contributing test cases that rely on knowledge of the CSCI's internal implementation.

5.9.2 Testing on the target computer system.

CSCI qualification testing shall include testing on the target computer system or an alternative system approved by the acquirer.

5.9.3 Preparing for CSCI qualification testing.

The developer shall define and record the test preparations, test cases, and test procedures to be used for CSCI qualification testing and the traceability between the test cases and the CSCI requirements. The result shall include all applicable items in the Software Test Description (STD) DID (see 6.2). The developer shall prepare the test data needed to carry out the test cases and provide the acquirer advance notice of the time and location of CSCI qualification testing.

5.9.4 Dry run of CSCI qualification testing.

If CSCI qualification testing is to be witnessed by the acquirer, the developer shall dry run the CSCI test cases and procedures to ensure that they are complete and accurate and that the software is ready for witnessed testing. The developer shall record the results of this activity in appropriate software development files (SDFs) and shall update the CSCI test cases and procedures as appropriate.

5.9.5 Performing CSCI qualification testing.

The developer shall perform CSCI qualification testing of each CSCI. The testing shall be in accordance with the CSCI test cases and procedures.

5.9.6 Revision and retesting.

The developer shall make necessary revisions to the software, provide the acquirer advance notice of retesting, conduct all necessary retesting, and update the software development files (SDFs) and other software products as needed, based on the results of CSCI qualification testing.

5.9.7 Analyzing and recording CSCI qualification test results.

The developer shall analyze and record the results of CSCI qualification testing. The results shall include all applicable items in the Software Test Report (STR) DID (see 6.2).


Translator: Simon Wright simon@pogner.demon.co.uk
Last updated: 22.iii.99