The developer shall perform unit integration and testing in accordance with the following requirements.
Note 1: Unit integration and testing means integrating the software corresponding to two or more software units, testing the resulting software to ensure that it works together as intended, and continuing this process until all software in each CSCI is integrated and tested. The last stage of this testing is developer-internal CSCI testing. Since units may consist of other units, some unit integration and testing may take place during unit testing. The requirements in this section are not meant to duplicate those activities.
Note 2: If a CSCI is developed in multiple builds, unit integration and testing of that CSCI will not be completed until the final build. Unit integration and testing in each build should be interpreted to mean integrating software developed in the current build with other software developed in that and previous builds, and testing the results.
The developer shall establish test cases (in terms of inputs, expected results, and evaluation criteria), test procedures, and test data for conducting unit integration and testing. The test cases shall cover all aspects of the CSCI-wide and CSCI architectural design. The developer shall record this information in the appropriate software development files (SDFs).
The developer shall perform unit integration and testing. The testing shall be in accordance with the unit integration test cases and procedures.
The developer shall make all necessary revisions to the software, perform all necessary retesting, and update the software development files (SDFs) and other software products as needed, based on the results of unit integration and testing.
The developer shall analyze the results of unit integration and testing and shall record the test and analysis results in appropriate software development files (SDFs).
Translator: Simon Wright simon@pogner.demon.co.uk
Last updated: 22.iii.99