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

• System-related. The problem is a result of an error within the system (e.g., theapplication software, the telecommunication software, hardware failure/malfunction).Generally system related problems are classified as Other with a Type 1 priority, andwill be addressed immediately. All system support documentation will be correctedpromptly.4.3. Change Tracking SystemCM will establish a Change Tracking System (CTS) for tracking status of SCRs that willbe available to all project personnel. Within the CTS all SCR status information will benoted for all SCRs.• SCR number.• Originator.• Date of origination.• Date of initial review.• Initial Configuration Management Board Date.• Assigned analyst.• Proposed solution date.• Date of second CMB review.• CMB decision (accept, reject, rework).• Proposed implementation date, and remarks.Configuration management will maintain the configuration tracking system by insertingrelevant information, as it becomes available.4.4. Version ControlA version is an identified body of software and documentation. It is the initial release orre-release of a software configuration item. When a body of software is generated tosatisfy a specific purpose, all component parts are identified at the level at which it existsat the time of release. The totality of that software release is called a version. Theversion is documented in the form of a Version Description Document (VDD), whichaccompanies the release. As a system matures, the baselined software is inevitablychanged to accommodate problem fixes or new capabilities.Docsscb5c.doc Page 29 of 93 2/23/2007