DOE/RL-93-52Rev. 1AutomatedTransportationManagement System(ATMS) ConfigurationManagement PlanRECEIVEDMAR 2 2 1935OSTIUnited StatesDepartment of EnergyRichland, WashingtonMASTERApproved for Public Release

DISCLAIMERPortions of this document may be illegiblein electronic image products. Images areproduced from the best available originaldocument.

Automated TransportationManagement System (ATMS)Configuration ManagementPlanR. S. WeidertDate PublishedJanuary 1994United StatesDepartment of EnergyP.O. Box 550Richland, Washington 99352Approved for Public Release

LEGAL DISCLAIMERThis report was prepared as an account of work sponsored byan agency of the United States Government. Neither theUnited States Government nor any agency thereof, nor any oftheir employees, nor any of their contractors, subcontractorsor their employees, makes any warranty, express or implied,or assumes any legal liability or responsibility for theaccuracy, completeness, or any third party's use or the resultsof such use of any information, apparatus, product, or processdisclosed, or represents that its use would not infringeprivately owned rights. Reference herein to any specificcommercial product, process, or service by trade name,trademark, manufacturer, or otherwise, does not necessarilyconstitute or imply its endorsement, recommendation, orfavoring by the United States Government or any agencythereof or its contractors or subcontractors. The views andopinions of authors expressed herein do not necessarily stateor reflect those of the United States Government or anyagency thereof.This report has been reproduced from the best available copy.Available in paper copy and microfiche.Available to the U.S. Department of Energyand its contractors fromOffice of Scientific and Technical InformationP.O. Box 62Oak Ridge, TN 37831(615)576-8401Available to the public from the U.S. Department of CommerceNational Technical Information Service5285 Port Royal RoadSpringfield, VA 22161(703) 487-4650Printed in the United States ol America0ISCLM-t.CHP(1-9l)


DOE/RL-93-52, Rev. 1AUTOMATED TRANSPORTATION MANAGEMENT SYSTEMSOFTWARE CONFIGURATION MANAGEMENT PLAN1.01.1INTRODUCTIONPURPOSEThis document describes the Software Configuration Management (SCM)approach and procedures to be utilized in ensuring and controlling thedevelopment process and maintenance of the Automated Transportation ManagementSystem (ATMS VI.0 and ATMS V2.0). The sponsor has identified ATMS and itscomponents as unclassified and non-sensitive. The configuration managementprocedures are necessary to ensure that any changes made to software and relateddocumentation are consistent with ATMS goals and objectives and containedsecurely in a central library. The objectives of the Plan are to:1.2 Establish product baselines that support the change process Ensure that all system changes support ATMS goals and objectives Ensure that the potential impacts of system changes are adequatelyevaluated prior to implementation Ensure that the latest approved versions of all software are beingused in all environments (current production, development and futureproduction) Establish a configuration status reporting standard that informspertinent individuals of ATMS system status Ensure that the baselines always remain current with the productionsoftware and documentation Ensure that configuration management is integrated with othermanagement plans designed to meet the overall objectives and goalsof ATMS Ensure that the configuration library function of maintaining allmaster copies of documentation and software for each product issupported.SCOPEThis plan applies to all software and associated documentation used in theproduction of the ATMS VI.0 and ATMS V2.0 system. Software configuration itemsto be controlled by this plan include both procured software and applicationssoftware to be developed during the project. No distinction is made betweenphases of implementation of the project.2

DOE/RL-93-52, Rev. 1The software products to be produced are applications software for the ATMSVI.0 and ATMS V2.0. Host software products, (e.g., a relational databasemanagement system) and peripheral host products, (e.g., forms generator softwareto aid the programmer in building data entry screens and a report generator toaid in building reports) will be provided for systems developers.This SCM Plan specifically covers the configuration management for:1.2.3.Development of system software, ATMS V2.0Development of system documentation, ATMS V2.0Continued system support following implementation, for ATMS VI.0 andATMS V2.0.In addition, this plan discusses the following subjects:1.Configuration Identification - Description of the hardware, software,required documentation, project responsibilities, and limitations ofapprovals with respect to specific control, and the review and deliveryschedule.2.Configuration Control - Description of software configuration changeprocedures, hardware configuration change procedures, software interfacecontrol, and organization interfaces.3.Configuration Accounting - Description of procedures and forms used torecord configuration changes.4.Reviews and Audits - Description of audit and review plans, method forhandling deviations, change procedures, and relationships between reviewsand the development cycle.1.3OVERVIEWThis SCM Plan covers the development and maintenance of all ATMS softwareand associated documentation for both the PC version (VI.0) and ATMS (V2.0). Thesoftware and documentation are being developed by the ATMS Development Team, withguidance from the Technical Project Manager, the Integrated Program Coordinator,the ATMS Users Group, the ATMS Change Control Board (CCB), and the TransportationAutomation Program Manager.1.4DEFINITIONS AND ACRONYMSDefinitions and acronyms used in this document will follow AmericanNational Standards Institute (ANSI)/ Institute of Electrical and ElectronicsEngineers (IEEE) 610.12-1990, Glossary of Software Engineering Technology(ANSI/IEEE 1990).1.4.1DefinitionsThe following terms are used throughout this document.3

DOE/RL-93-52, Rev. 1Configuration Identification — (1) The process of designating theconfiguration items in a system and recording their characteristics; (2)The approved documentation that defines a configuration item; and (3) Thecurrent approved or conditionally approved technical documentation for aconfiguration item as set forth in specifications, drawings and associatedlists, and documents referenced therein.Configuration Item — (1) A collection of hardware or software elementstreated as a unit for the purpose of configuration management; and (2) Anaggregation of hardware/software, or any of its discrete portions, thatsatisfies an end use function and is designated for configurationmanagement. Configuration items may vary widely in complexity, size, andtype from an aircraft, electronic, or ship system to a test meter or roundof ammunition. During development and initial production, configurationitems are only those specification items that are referenced directly ina contract (or an equivalent in-house agreement). During the operationand maintenance period, any repairable item designated for separateprocurement is a configuration item.Configuration Management — The process of identifying, controlling,accounting for, and auditing an information system. The configuration ofa system is measured at discrete points in time to identify and controlchanges and to maintain the integrity and traceability of theconfiguration. Configuration management is also a management controlmechanism to ensure system changes are within the scope of the systemdesign and to keep track of system change status.Configuration Accounting — The recording and reporting of the informationthat is needed to manage a configuration effectively, including a listingof the approved configuration identification, the status of proposedchanges to the configuration, and the implementation status of approvedchanges.Production Library — A software library containing formally releasedversions of software and documentation.Product — The hardware and software that are required for an applicationto operate.Product Baseline — T h e state of hardware and software for an applicationand its associated documentation as it exists in the current productionenvironment.Release Package — A package containing all the components required todeliver a complete product release to the field, including releasenotification, release notes, installation notes, documentation, andsoftware.System/Software Change Request (SCR) — T h e form that is used to report asoftware or hardware problem or to request ADP support from computeroperations.4

DOE/RL-93-52, Rev. 1Software Library — A controlled collection of software and relateddocumentation designed to aid in software development, use, ormaintenance. Types include software development library, master library,production library, program library, and software repository.1.4.2Acronyms and GlossaryThe followingdocument.andacronymsare usedthroughoutANSIATMSIEEECCBCMPAmerican National Standards InstituteAutomated Transportation Management SystemInstitute of Electrical and Electronics EngineersChange Control BoardConfiguration Management PlanIRMInformationResourceManagementWestinghouse Hanford Company)Review Comment RecordSoftware Configuration ManagementSystem/Software Change RequestSoftware Design DescriptionSoftware Requirements SpecificationVerification and ionthisofREFERENCESWHC, 1988, Standard Engineering Practices WHC-CM-6-1, Engineering Change Notice,Section EP-2.2: Engineering Document Change Control.WHC, 1989, IRM Project Management, WHC-CM-3-2, Project Change Management,procedure 2.0100.07, and Change Control Guidelines for Production On-LineApplications, procedure 2.2015.WHC, 1993, Software Practices, WHC-CM-3-10, Configuration Control, Section 6.0,Westinghouse Hanford Company, Richland, Washington.5

DOE/RL-93-52, Rev. 12.02.1MANAGEMENTRESPONSIBILITIESThe Technical Project Manager is responsible for administering ATMSconfiguration management. ATMS configuration management is divided into twophases:1)Development phase: Software is controlled through release to theATMS development library for acceptance testing. The TechnicalProject Manager acts as the software librarian controlling therelease of the software during this phase. Hardware configurationis controlled through release memo to the development sites. TheTechnical Project Manager acts as the focal point to coordinatesimilar configuration on all development platforms.2)Production phase:ATMS software configuration management iscontrolled by the ATMS change control board (CCB) and IRM operationsproduction procedures.The ATMS CCB controls the approval ofmodifications to the ATMS software when the software will betransferred to production.An assigned Project Librarian willcontrol the physical release and coordination of the release. ATMShardware configuration management will be addressed in a laterrelease of this document.The general responsibilities of the Technical Project Manager during thedevelopment phase of configuration management are to ensure the SoftwareRequirement Specification (SRS) are developed in the software system as it iswritten, and to capture the as-built documentation, test data, reports, and codefor the system.Specific organizational responsibilities of the SCM coordinators are asfollows:Maintain a stable development environment.Establish naming conventionsApprove change requests and plansPrepare necessary status reports and monitor project statusConduct regular reviews.2.2INTERFACE CONTROLThis SCM plan interfaces with the following plans: 2.3Test Plan WHC-SD-TP-TP-004Implementation Plan WHC-SD-TP-SWD-003Documentation Plan WHC-SD-TP-PLN-007IMPLEMENTATIONThis SCM plan has the following implementation schedule for when itemsfirst become configuration items:6

DOE/RL-93-52, Rev. 12.41.December, 1992- ATMS V2.0 Functional Requirements Document2.January, 1993- ATMS V2.0 Data Requirements Document3.March, 1993- ATMS V2.0 Implementation Plan4.May, 1993- ATMS V2.0 Configuration Management Plan5.May, 1993- ATMS V2.0 Security Plan6.June, 1993- ATMS V2.0 Quality Assurance Plan7.August, 1993- ATMS V2.0 Training Plan8.September, 1993- ATMS V2.0 Documentation Plan9.September, 1993- ATMS V2.0 Verification and Validation Plan10.December, 1993- ATMS VI.0 Released Software11.December, 1993- ATMS VI.0 Users Manual12.April, 1994- ATMS V2.0 Test Plan13.April, 1994- ATMS V2.0 Test Materials14.Fiscal Year 1994 - ATMS released software, and the initiationthe ATMS Change Control 13oardPOLICIES AND PROCEDURESThe following procedures will be followed for all documents, software,etc., named in this plan as configuration items. Engineering Document Change Control, SectionEngineering Practices, WHC-CM-6-1 (WHC 1988) Project Change Management, procedure 2.0100.07; and Change ControlGuidelines for Production On-Line Applications, procedure 2.2015,IRM Project Management, WHC-CM-3-2 (WHC 1989) Configuration Control, Software Practices, WHC-CM-3-10 (WHC 1993) ,SP-6.0; Document Control, SP-6.1; Software Control, SP-6.2; ChangeRequests and Problem Reports, SP-6.3; and Document Approvals, SP6.4.7EP-2.2, Standard

DOE/RL-93-52, Rev. 13.03.1SOFTWARE CONFIGURATION MANAGEMENT ACTIVITIESCONFIGURATION IDENTIFICATIONThis section describes how ATMS documents and software will be identified.3.1.1Document IdentificationAll ATMS documents will be named in accordance with the instructionsoutlined in Standard Engineering Practices, WHC-CM-6-1, Section EP-1.12 or inaccordance with DOE document numbering practices. The person preparing asupporting document requests an identification number from a ConfigurationDocumentation Work Station operator. The ATMS document numbering convention fordocuments without a DOE document number is as follows:WHC-SD-XXX-YYY-999WHCSDXXXYYY999Z3.1.2- identifies- identifies- identifiesor TP for- identifies- identifies- identifiesRev. Zthe DOE contractorthe document as a Supporting Documentthe program indicator (e.g., WM for Waste Management,Transportation and Packaging)the supporting document typethe unique document numberthe revision number of the documentSoftware IdentificationAll ATMS software will be named in accordance with WHC Software Practices,WHC-CM-3-10, Section SP-6.2. The ATMS naming convention is as follows:XXYZZZZ.999XXYZZZZ9993.2- identifies the name of the module- identifies the module asM - for a menu identifierD - for a display identifierU - for a update identifierR - for a report identifier- sequential number for unique identification- sequential version number (only used when archiving unused code ina file structure)CONFIGURATION CONTROLBaselines are established by the DOE headquarters program manager'sapproval of the document. ATMS will utilize a change control board after thesystem enters the production environment. The purpose of the CCB is to decideapproval/disapproval and priority appointment of technical changes to ATMS.Technical changes can be requested by use of an SCR from (figure 1), or byemploying the error reporting module within the ATMS software.8

DOE/RL-93-52, Rev. 1Software Change Request/Problem ReportSCR/PR Number:1.Software/Document Identification (Name):2.Prepared by:Rev:Date:TCPN, W/O:System Name:3.SCR/PR Type:[ ] Change RequestRequested Completion Date:[ ] Problem Report4-. Description:5.Justification if Change Request:6.Submitter's Priority[ ] High[ ] Medium[ ] Low7.Change Authority:C J Accept[ J Modify[ ] Reject8.Assigned to:9.Solution Comments[ I Defer Until:Planned Release Date:Cost/Schedule Estimate:/10. Software/Documents Affected:11. Approvals Indicate SCR is Complete or PR is Resolved:Software DeveloperDate:Cognizant Manager:Date:SCR or PR Preparer:Date:Other:Date:Mail to: ATMS Project Manager/ATMS CCB BCS Richland, Inc. (Figure 1)9P.O. Box 300 MS B5-25 Richland WA 99352-3562

DOE/RL-93-52, Rev. 13.3CONFIGURATION ACCOUNTINGAccounting for change is accomplished by tracking the changes to moduleson the change control log located with the hard copy print out of the code.The software unit development folders will contain a copy of a change controllog. As software modules are generated, a copy of the source code will beplaced in the unit development folders and duly noted on the log. Moduleswhich are changed or modified will have updated source code listings placed inthe unit development folders and appropriately documented on the changecontrol log as to version and the nature of the change. During ATMSdevelopment, the Technical Project Manager will regularly check to ensure thefolders and change control logs for any modifications are being created andmaintained. Once released into production the change control log will be usedto formally prepare all required engineering change notices as required.After the initial alpha release of the ATMS change requests or problemswill be reported using a change request form. Change requests to thedevelopment programs will be reported to the Technical Project Manager on aweekly basis. When the software is beta released for formal release testing,the release and version number are recorded along with the current changelevel. In addition, the Technical Project Manager will oversee the projectthrough regular weekly status reports from development team members.3.4AUDITS AND REVIEWSTo ensure proper execution of procedures in support of the configurationmanagement function, and to identify any areas in the procedures that requiremodifications, the Technical Project Manager should conduct periodic informalreviews and audits.The Audits and Reviews procedure should be conducted to measure theproper execution of activities relative to the control and processing ofchange requests. Included in these informal reviews should be a periodicassessment of the interfaces occurring with development team activities toensure their adherence to sound Configuration Management procedures. Thisprocedure also involves comparing the physical contents of the ATMS productsrunning in the production environment (i.e., software, documentation) to therecords maintained in the CM Library. This will ensure the effectiveness oflibrary controls and the integrity of library contents.3.5ACCESS CONTROLAccess to ATMS software and data will be controlled through the use ofpasswords. Further details about the access control plan can be found in theATMS System Security Plan. Since ATMS hardware typically consists of personalcomputers at the local site that are used for other purposes, access to thehardware will not be controlled.3.6BACKUP AND RECOVERYComputer equipment, software, and data are susceptible to damage, loss,or destruction. To protect ATMS from such risks, a backup and recoveryprocedure has been established and is contained within the ATMS SystemSecurity Plan.10

DOE/RL-93-52, Rev. 14.0TOOLS, TECHNIQUES, AND METHODOLOGIESConfiguration management procedures will be used to monitor and controlthe release of ATMS software and documentation into production libraries.Deployment of software will be performed using similar control procedures.5.0SUPPLIER CONTROLContract-developed software will form the basis of ATMS. Thesubcontractor will be responsible for releasing software in accordance withthis SCM Plan.6.0RECORDS COLLECTION AND RETENTIONStatus reports will be maintained as a historical record for the ATMSproject in the project notebook. All test data, test procedures, and testresults will be maintained and saved for use in defining the productionsystem, including the software unit development folders and associated changecontrol logs. Baseline code, test data and reports will be maintained at thetermination of the project for two years. All associated documentation willbe maintained in the Records Holding Area for a two-year period.11

DOE/RL-93-52, Rev. 17.07.1HARDWARE CONFIGURATION MANAGEMENT ACTIVITIESHardware Configuration IdentificationThis section describes now ATMS VI.0 and V2.0 hardware will beconfiguration controlled.7.2ATMS VI.0 HardwareThe minimum hardware configuration to use ATMS VI.0 is as follows: 386-25MHZ IBM compatible,2MB RAM,3 1/2 inch floppy drive,9600 Baud modem (bits, stop/bit, X0N/X0FF, Parity check, even/odd).Software will be able to be loaded by personnel at the requesting sitefollowing simple installation procedures.7.3ATMS V2.0 HardwareDuring the development phase of the project the initial configuration ofthe development platforms will be done at one site. The deployment ofdevelopment hardware to remote development sites will require closecommunications between the operational system managers to document and testany configuration changes away from the initial configuration. Thisdocumentation will be used to and in the installation of similar hardware atother sites. Site specific configuration changes will be supported but mustbe approved by the ATMS Change Control board.12

type from an aircraft, electronic, or ship system to a test meter or round of ammunition. During development and initial production, configuration . development phase of configuration management are to ensure the Software Requirement Specification (SRS) are developed in the software system as it is written, and to capture the as-built .