Scmp

Configuration Management Plan FOR LASRS++ SIMULATION PROJECTSRelease 1Version 1Michael MaddenUnisys CorporationHampton, Virginia 23666December 2, 1996Table of contentsSectionPage1. Introduction1.1 Purpose1.2 Scope1.3 Abbreviations and Definitions1.3.1 Definitions1.3.1.1 Configuration Management Terminology1.3.1.2 Project-related Terminology1.3.2 Abbreviations1.4 References2. Management2.1 Organization2.1.1 Project Organization2.1.2 Software Configuration Management Organization2.2 SCM Roles and Responsibilities2.2.1 Activity Definitions2.2.2 Responsibility Definitions2.2.3 Role Definitions2.2.3.1 The Simulation Project CCB2.2.3.1.1 CCB Chairman2.2.3.1.2 CCB Secretary2.2.3.1.3 CCB Librarian2.2.3.2 Simulation Customers2.2.3.3 Architecture Consultant (AC)2.2.3.4 FSSS Management2.2.3.5 SSB Management2.2.3.6 SSB Facilitator2.3 Applicable Policies, Directives, and Procedures3. Activities3.1 Configuration Identification3.1.1 Identifying CIs3.1.1.1 Special Considerations for Base + Variants Simulation Projects.3.1.2 Naming CIs3.1.3 Acquiring CIs3.2 Configuration Control3.2.1 Submittal (Requesting Changes)3.2.2 Review (Evaluating Changes)3.2.3 Approval (Approving or Disapproving Changes)3.2.4 Deferring a CR3.2.5 Appealed (Overruling Rejection or Forwarding)3.2.6 Authorization3.2.7 Execution (Implementing changes)3.2.8 Closure (Closing the CR)3.3 Configuration Status Accounting3.3.1 Configuration Data3.3.2 Configuration Reports3.3.2.1 CR Summary3.3.2.2 Release Notes3.3.2.3 Monthly CR Status3.4 Configuration Audits and Reviews3.4.1 Code Review3.4.2 Functional Configuration Audit (FCA)3.4.3 In-Process Audit3.4.4 Physical Configuration Audit3.5 Interface Control3.5.1 Subcontractor/Vendor Control4. SCM Schedules5. SCM Resources5.1 Software Resources5.2 Hardware Resources5.3 Human Resources6. SCM Plan MaintenanceAppendix A Change Request Form RequirementsPART A: SubmissionPART B: ReviewPART C: Approval, Appeal, and AuthorizationPART D: ExecutionPART E: ClosureRequired Data...