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

More documents

Recommendations

Info

4. Configuration ControlConfiguration Control is the formal process of managing changes to the system. It is focusedon identifying changes to a baselined configuration of hardware, software, or documentation;and managing the manner in which proposed changes are processed from inception toultimate disposition. Configuration Control is manifested through a Change Managementsystem, which will be described in this section.4.1. Change ControlChange Control is the main function of the Change Management Process. The ChangeManagement Process is the systematic evaluation, coordination, development, approvalor disapproval; and implementation of changes after the establishment of a baseline.Changes are managed from their inception to final resolution to ensure that a standardrepeatable process is maintained for handling proposed changes and to ensure thatunauthorized changes are not introduced into a controlled baseline. The vehicle forsubmitting proposed changes to the approved DOCS baseline is the System ChangeRequest (SCR). Configuration management uses a Change Tracking System to recordthe progress of a change as it proceeds through the change cycle.It should be noted that the DOCS System Administrator is responsible for ensuring theDOCS lookup tables are current at all times, and will be required to update these tablesupon occurrence. Although this is considered a change to the current baseline, this typeof change will not be processed through the formal change control procedures describedin this section. The DOCS System Administrator will complete an SCR for each changefor record maintenance.4.1.1. System Change Requests (SCRs)SCRs will be classified as being one of the following types:• New Requirement – A new requirement is defined as an item requested to beadded to the current configuration.• Requirement Change – A requirement change is defined as a change to theconfiguration that is necessary to fulfill a requirement.• Design Change – A design change is defined as an item that alters theoriginal design of the system (i.e. adding an additional server).• Other – An other change is defined as revisions to other related changes ofthe current baseline system as a result.Appendix C contains an example of the System Change Request Form.Docsscb5c.doc Page 24 of 93 2/23/2007
4.1.2. System Change Request (SCR) PrioritiesSCR priorities are classified as being one of three types. Any SCR maybeupgraded or downgraded, but only upon CMB approval.TypeDescription4.1.3. SCR Processing1 Work stoppage2 Application revision within 3-6 months3 Application upgrade within but no-later-than 12 monthsDOCS users, the Office of the Executive Secretariat, and project personnel maysubmit a proposed request for changes. All proposed request for changes will besubmitted to the DOCS System Administrator on the DOCS User Request forSoftware Change Form. The DOCS System Administrator will:• Review the DOCS User Request for Software Change form.• Forward to the appropriate Configuration Management Board members forinitial approval.• Complete a System Change Request if the change has been initially approved.• Enter the SCR on to the SCR Log.• Forward the SCR to the Project Manager.The Project Manager will:• Review the SCR.• Provide a detailed estimate of resources and costs associated with the change.• Submit the SCR with estimates to the Configuration Management Board forfinal approval.Appendix C contains an example of the DOCS User Request for Software Changeform.The diagram on the following page depicts the SCR Process.Docsscb5c.doc Page 25 of 93 2/23/2007
Page 1 and 2: U. S. Department of EnergyOffice of
Page 3 and 4: 4.4.2.1. System Modification.......
Page 5 and 6: Council documents received in or in
Page 7 and 8: • Section 8 - Backup and Restore:
Page 9 and 10: 2. Configuration Management Organiz
Page 11 and 12: 2.4. Configuration Management Envir
Page 13 and 14: 2.4.1.1. Standing Configuration Man
Page 15 and 16: • Analyzes proposed problem solut
Page 17 and 18: 3. Configuration IdentificationConf
Page 19 and 20: • Documented Source Code contains
Page 21 and 22: 3.4. DOCS Configuration Management
Page 23: When a release is needed, CM will p
Page 27 and 28: 4.1.3.1. Roles and Responsibilities
Page 29 and 30: • System-related. The problem is
Page 31 and 32: • Providing one or more additiona
Page 33 and 34: 5. Configuration Status AccountingC
Page 35 and 36: 6. Configuration Audits and Reviews
Page 37 and 38: • Track all FCA/PCA action items
Page 39 and 40: 7. Archive and RetrievalThe object
Page 41 and 42: 9. Records Collection and Retention
Page 43 and 44: Appendix ADocument On-line Correspo
Page 45: 3. AuthorityThe DOCS CMB derives it
Page 48 and 49: Configuration Management BoardMembe
Page 50 and 51: 5. ProtocolsCMB meetings will be he
Page 52 and 53: Appendix BDOCS System Configuration
Page 55 and 56: DOCS II System ConfigurationBaselin
Page 61 and 62: Appendix CSoftware Change Request F
Page 63 and 64: Docsscb5c.doc Page 63 of 93 2/23/20
Page 65 and 66: SCR # Short Title DateSubmittedPrio
Page 67 and 68: Docsscb5c.docPage 67 of 93 2/23/200
Page 69 and 70: Document Online Coordination System
Page 71 and 72: Appendix FAcronyms and Abbreviation
Page 73 and 74: Appendix GConfiguration LibraryDocs
Page 75 and 76:
CD - Program License Diskette 3.2 S
Page 77 and 78:
CD - Cheyenne Software from Compaq
Page 79 and 80:
Smart-2 Array Controller - User Gui
Page 81 and 82:
Legend:Letters and number placed be
Page 83 and 84:
Library 2 -Setup Disk 2 4 SW-0001A/
Page 85 and 86:
What's New in SQL Server 6.5 6.5Pro
Page 87 and 88:
Administrator's Guide - Enterprise
Page 89 and 90:
Release Notes 1.7 CTX-00F4-9301-F91
Page 91 and 92:
Compaq Systems Reference Library 2.
Page 93:
Docsscb5c.doc 02/23/07 Page 93 of 9
show all

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

Create successful ePaper yourself

Delete template?

Save as template?