DOCS System Configuration Management Plan - U.S. Department of ...

6. Configuration Audits and ReviewsConfiguration Audits determine to what extent the as-designed/as-tested/as-built productreflects the required physical and functional characteristics specified in the requirements.Functional and Physical Configuration Audits (FCA/PCA) are done once, to establish theProduct Baseline. In-process CM status reviews are done whenever needed to verify theconfiguration. The difference is that FCA/PCAs are formal audits, accomplished by a team,which may or may not consist of Quality Assurance, whereas informal In-process CM statusreviews are accomplished by one person, and do not require the formality and resources ofthe formal audits. FCAs/PCAs can be done incrementally and concurrently.FCA/PCA audit will be conducted upon the release of a new version release or major systemenhancement.6.1. Configuration Audits6.1.1. Functional Configuration Audit (FCA)The objective of a FCA is to verify that all tests for a CI have been completed andthat the performance, based upon the test results, meets the specified performancerequirements. A FCA team is formed by direction of project management, led byan appointed Chairperson. CM coordinates the FCA (supporting the Chairperson)by ensuring that:• all materials are supplied.• an agenda is published.• minutes are recorded.• action items are recorded and reviewed for resolution.A report is prepared at the conclusion of the FCA, a copy of which is retained onthe CM Library.6.1.2. Physical Configuration Audit (PCA)The objective of a PCA is to verify the adequacy, completeness, and accuracy ofthe documentation that establishes the Production Baseline. A PCA team isformed by direction of project management, led by an appointed Chairperson, andconsisting of members from selected functional and partner organizations. CMcoordinates the PCA and supports the Chairperson by ensuring that:Docsscb5c.doc Page 35 of 93 2/23/2007