5.15 Software product evaluation.

The developer shall perform software product evaluation in accordance with the following requirements.

Note: If a system or CSCI is developed in multiple builds, the software products of each build should be evaluated in the context of the objectives established for that build. A software product that meets those objectives can be considered satisfactory even though it is missing information designated for development in later builds.

5.15.1 In-process and final software product evaluations.

The developer shall perform in-process evaluations of the software products generated in carrying out the requirements of this standard. In addition, the developer shall perform a final evaluation of each deliverable software product before its delivery. The software products to be evaluated, criteria to be used, and definitions for those criteria are given in Appendix D.

5.15.2 Software product evaluation records.

The developer shall prepare and maintain records of each software product evaluation. These records shall be maintained for the life of the contract. Problems in software products under project-level or higher configuration control shall be handled as described in 5.17 (Corrective action).

5.15.3 Independence in software product evaluation.

The persons responsible for evaluating a software product shall not be the persons who developed the product. This does not preclude the persons who developed the software product from taking part in the evaluation (for example, as participants in a walk-through of the product).


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