The developer shall perform software quality assurance in accordance with
the following requirements.
Note: If a system or CSCI is developed in multiple
builds, the activities and software products of each build should be evaluated
in the context of the objectives established for that build. An activity or
software product that meets those objectives can be considered satisfactory
even though it is missing aspects designated for later builds. Planning for
software quality assurance is included in software development planning (see 5.1.1 ).
5.16.1 Software quality assurance evaluations. The developer shall conduct
on-going evaluations of software development activities and the resulting
software products to:
a. Assure that each activity required by the contract or described in the
software development plan is being performed in accordance with the contract
and with the software development plan.
b Assure that each software product required by this standard or by other
contract provisions exists and has undergone software product evaluations,
testing, and corrective action as required by this standard and by other
contract provisions.
5.16.2 Software quality assurance records. The
developer shall prepare and maintain records of each software quality
assurance activity. These records shall be maintained for the life of the
contract. Problems in software products under project-level or higher
configuration control and problems in activities required by the contract or
described in the software development plan shall be handled as described in 5.17
(Corrective action).
5.16.3 Independence in software quality assurance. The persons responsible
for conducting software quality assurance evaluations shall not be the persons
who developed the software product, performed the activity, or are responsible
for the software product or activity. This does not preclude such persons from
taking part in these evaluations. The persons responsible for assuring
compliance with the contract shall have the resources, responsibility,
authority, and organizational freedom to permit objective software quality
assurance evaluations and to initiate and verify corrective
actions.
