MIL-HDBK-61A: Configuration Verification and Audit
< Previous | Contents | Next >
8.1 Configuration Verification and Audit Activity.
The configuration verification and audit process includes:
-
Configuration verification of the initial configuration of a CI, and the incorporation of approved engineering changes, to assure that the CI meets its required performance and documented configuration requirements
-
Configuration audit of configuration verification records and physical product to validate that a development program has achieved its performance requirements and configuration documentation or the system/CI being audited is consistent with the product meeting the requirements.
The common objective is to establish a high level of confidence in the configuration documentation used as the basis for configuration control and support of the product throughout its life cycle. Configuration verification should be an imbedded function of the contractor's process for creating and modifying the CI or CSCI. Validation of this process by the Government may be employed in lieu of physical inspection where appropriate.
As shown in Figure 8-1, inputs to the configuration verification and audit activity are:
-
Configuration, status, and schedule information from status accounting,
-
Approved configuration documentation (which is a product of the configuration identification process),
-
The results of testing and verification,
-
The physical hardware CI or software CSCI and its representation
-
Manufacturing
-
Manufacturing/build instructions and engineering tools, including the software engineering environment, used to develop, produce, test and verify the product
Successful completion of verification and audit activities results in a verified System/CI(s) and a documentation set that may be confidently considered a Product Baseline. It also results in a validated process to maintain the continuing consistency of product to documentation.
For correct application of this information, see NOTE on Contents page