physicalconfigurationauditreport.docVIP

Physical Configuration Audit Report for Project Name (Project Acronym) #.# [do not put the word version] Prepared for : United States Patent and Trademark Office Office of the Chief Information Officer Prepared on Month Day, Year Approved by : OCIO Project Manager System Development Lead Business Project Manager Date Date Date Change Log Version Number Date Nature of Change Pages POC for change  TABLE OF CONTENTS 1. Introduction 1 1.1 Configuration Audits 1 1.2 Purpose 1 1.3 Referenced Documents 1 2. AIS WITH VERSION PCA 2 2.1 System Interfaces 2 2.2 Audit Participants 2 2.3 Results/Conclusions 2 2.4 Audit Certification 3 AIS WITH VERSION Verification List Error! Bookmark not defined.  1. Introduction The Enterprise Systems Services Group/Pre-Production Services Division/Configuration Management Services Branch [ESS/PPSD/CMSB] identified a need to document the as-built configurations of each Automated Information System (AIS) in deployment and production. The audit task was added for this purpose. SUPCM is the project to implement a Configuration Management and Change Management capability based on IBM Rational ClearCase/ClearQuest enabling tools. The SUPCM supports deep integrated solution to support Model Driven Architecture (MDA) and Model Driven Development from high-level Enterprise Architecture through Use Case Realization to code deployment. 1.1 Configuration Audits Three types of configuration audits may be conducted on a project under development: the Functional Configuration Audit (FCA), the Physical Configuration Audit (PCA), and in-process audits. Audit findings will be retained by ESS/PPSD/CMSB. The SDL is responsible for taking action on audit findings. The FCA is a formal examination of the functional characteristics of a project, prior to acceptance, to verify that the project has achieved the requirements specified in the approved project documentation.