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

More documents

Recommendations

Info

They will be placed on a CI list in the Configuration Management Library andtracked as they are developed and changed. The original COTS software, prior tomodification, will be internally tracked as Version 0. As modifications occur, andare approved by the CMB, the version number will roll to Version 1.0 whenbaselined by the Configuration Control Board. Changes are controlled afterbaselining, and are only implemented by CMB direction. Un-modified COTSsoftware will be tracked within CM under its commercial version number.The following is a list of software SWCIs that will be maintained during theproduction phase.• COTS Products will follow the naming convention of it commercial versionnumber.• SQL Database Tables used with the DOCS database design are outlined anddescribed in the appendixes of the DOCS Programmer System MaintenanceDirectory,• Documents will include all scanned items and word perfect documents.• Userids and Passwords will be created and maintained on the LAN by theDOCS System Administrator and Senior Technical Manager.3.1.2. Documentation Configuration Items (DCIs)DOCS II system documentation is also considered as CIs. As a document isdeveloped and accepted by the client, it is placed under configuration control byCM and stored in a secure electronic and physical library. If the system evolveschanges that effect documentation, the documentation changes must be approvedby the CMB, and implemented by CM as directed.The following is a list of DOCS II system DCIs that will be maintained duringthe production phase.• DOCS Design Document contains the detailed proposed system design,based on the required system functionality. It includes the database tablestructures, and defines the attributes of all data items that are contained withinthe tables.• DOCS User System Reference Manual serves as a step-by-step DOCS userguide.• DOCS Programmer System Maintenance Directory is a technicalreference guide for the DOCS development team (programmers).Docsscb5c.doc Page 18 of 93 2/23/2007
• Documented Source Code contains source code for any program developedoutside of the COTS applications associated with DOCS.3.1.3. Hardware Configuration ItemsDOCS Hardware Configuration Items are equipment that requires itsconfiguration status to be tracked. Each unique item of equipment, such ascomputers, workstations, printers, scanners, etc., is tracked to capture the correctconfiguration. Changes are controlled, and approved by the ConfigurationManagement Board.3.1.4. System/Sub-system Configuration ItemsSeveral System/ Subsystem level configuration items have been selected forDOCS. These are high-level CI’s which break down to lower level hardware,software, and possibly documentation CIs. The Configuration ManagementBoard controls these changes as well.3.2. Configuration Item IdentifiersConfiguration Item Identifiers are a means for applying a unique number toDocumentation, Hardware, or Software CIs. The following tables show how a uniquenumber is developed for each project CI.3.2.1. SWCI Identification NumbersTable 3-1 shows an example of creating SoftWare CI identifiersField Name Field Location ExampleCI Type Identifier Positions 1-2 SW; HW;SYS;DOCI Number Positions 3-5 123Type of CI Position s 6-8 V01Table 3-1Therefore, the identifier for a SWCI would be SW123V01; the identifier for aHWCI would be HW456V01.Docsscb5c.doc Page 19 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: 3. Configuration IdentificationConf
Page 21 and 22: 3.4. DOCS Configuration Management
Page 23 and 24: When a release is needed, CM will p
Page 25 and 26: 4.1.2. System Change Request (SCR)
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?