configuration management plansunguidesoftware.com/sunguidesoftware/document... · software...

SunGuideSM: Configuration Management Plan SunGuide-CMP-1.0.1

Prepared for: Florida Department of Transportation Traffic Engineering and Operations Office 605 Suwannee Street, M.S. 90 Tallahassee, Florida 32399-0450 (850) 410-5600 June 29, 2004

Configuration Management Plan

SunGuide-CMP-1.0.1 i

Document Control Panel File Name: SunGuide-CMP-1.0.1.doc File Location: SunGuide CM Repository CDRL: 2-9.2

Name Initial Date

Tom Eisenhut, SwRI TJE 11/24/03 Created By: Steve Dellenback, SwRI SWD 11/25/03 Robert W. Heller, SwRI RWH 11/25/03 Susan B. Crumrine, SwRI SBC 11/25/03 Steve Dellenback, SwRI SWD 6/29/04 Steve Novosad, SwRI SEN 6/29/04

Reviewed By:

Robert W. Heller, SwRI RWH 6/29/04

Modified By:

Completed By:


SunGuide-CMP-1.0.1 ii

Table of Contents 1. Scope ................................................................................................. 1

1.1 Project Identification ............................................................................... 1 1.2 Project Overview...................................................................................... 1 1.3 Related Documents ................................................................................. 2 1.4 Contacts ................................................................................................... 3

2. Baseline Identification...................................................................... 4 2.1 Definitions ................................................................................................ 4 2.2 Baseline Deliveries .................................................................................. 4

3. Resources ......................................................................................... 6 3.1 Project SCM Staff Assignments ............................................................. 6 3.2 Tools and Project Repository ................................................................. 6

3.2.1 Rational® Tool-Based Method ....................................................6 3.2.2 Visual Source Safe (VSS) Workspaces ....................................11

4. Development Procedures for Version Control............................. 12 4.1 Procedures for Rational Tools.............................................................. 12

4.1.1 Rational ClearCase....................................................................12 4.1.2 Using ClearCase........................................................................12

4.2 Version Control of Documents ............................................................. 12 4.3 Commenting........................................................................................... 12 4.4 Backups.................................................................................................. 13

4.4.1 ClearCase Backup .....................................................................13 4.4.2 ClearQuest Backup ...................................................................14 4.4.3 VSS Backup ..............................................................................15 4.4.4 Local PC Files Backup..............................................................15

5. Configuration Status Accounting and Audit ................................ 16 5.1 Configuration Status Accounting......................................................... 16 5.2 Configuration Management Audit ........................................................ 16

6. Engineering Change Request and Software Problem Report Tracking .................................................................................................... 18

6.1 Engineering Change Requests............................................................. 18 6.2 Software Problem Reports.................................................................... 19


SunGuide-CMP-1.0.1 iii

List of Appendices

Appendix A – Configuration Status Accounting

Appendix B – Release 1 Directory Structure


SunGuide-CMP-1.0.1 iv

List of Acronyms

ATP............................Acceptance Test Plan

C2C ............................Center to Center

CCB............................Configuration Control Board

CDRL.........................Contract Data Requirments List

CD-ROM....................Compact Disk Read Only Media

CM .............................Configuration Management

CR ..............................Change Request

CSCI...........................Computer Software Configuration Item

DMS...........................Dynamic Message Sign

DOT ...........................Department of Transportation

DPM...........................Deputy Project Manager

ECR............................Engineering Change Request

FDOT .........................Florida Department of Transportation

HAR ...........................Highway Advisory Radio

ITN.............................Invitation to Negotiate

ITS..............................Intelligent Transportation Systems

IV&V .........................Independent Validation & Verification

MCMR .......................Master Configuration Management Repository

N/A.............................Not Applicable

NSG............................Network Support Group

PCA............................Physical Configuration Audit

PCM ...........................Project Configuration Manager

PIWS..........................Process Improvement Website

PM..............................Project Manager

RWIS..........................Roadway Weather Information Sensor

SCCB .........................Software Configuration Control Board

SCM ...........................Software Configuration Management

SCMP.........................Software Configuration Management Plan

SDP ............................Software Development Plan

SE...............................Software Engineering


SunGuide-CMP-1.0.1 v

SPM............................Software Project Manager

SPR ............................Software Problem Report

SRR............................Software Requirements Review

SRS ............................Software Requirments Specification

STMCSLS..................Statewide Transportation Management Center Software Library System

SUM...........................Software User Manual

SwRI ..........................Southwest Research Institute

TRR............................Test Readiness Review

TxDOT.......................Texas Department of Transportation

VOB ...........................Versioned Object Base

VSS ............................Visual Source Safe

W3..............................World Wide Web


SunGuide-CMP-1.0.1 vi

REVISION HISTORY

Revision Date Changes 1.0.0-Draft November 3, 2003 Initial Release 1.0.0-Final November 25, 2003 Incorporates SwRI responses to comments on Draft CMP

1.0.1 June 29, 2004 Incorporate changes based on recommendations from IV&V Audit Report dated 14-April-2004. Incorporate changes based on comments from FDOT dated 15-Feb-04. These changes include:

• replacement of STMCSLS with SunGuide; • removal of Chester Chandler from list of

contacts; • reorganize Section 3.2 into sections on ClearCase

and one for VSS; • add comment to section 3.2.1 noting that the

FDOT will not have access to the ClearCase repository from outside SwRI,

• rename figure in section 3.2.1.3 to note it describes Initial Release VOB structure;

• add appendix B to show directory structure of Release 1 repository

• update ClearCase backup procedures • minor editorial changes to improve organization

and readability.


SunGuide-CMP-1.0.1 1

1. Scope

1.1 Project Identification This document is the Software Configuration Management Plan (SCMP) for the SunGuide software. It describes the processes and procedures Southwest Research Institute® (SwRI®) will use to manage configuration baselines for the SunGuide project.

1.2 Project Overview

The Florida Department of Transportation (FDOT) is conducting a program that is developing SunGuide software. The SunGuide software is a set of Intelligent Transportation System (ITS) software that allows the control of roadway devices as well as information exchange across a variety of transportation agencies. The goal of the SunGuide software is to have a common software base that can be deployed throughout the state of Florida. The SunGuide software development effort is based on ITS software available from both the states of Texas and Maryland; significant customization of the software is being performed as well as the development of new software modules. The following figure provides a graphical view of the software to be developed:



Figure 1.1 – High-Level Architectural Concept The SunGuide development effort spans approximately two years. After the development, the software will be deployed to a number of Districts and Expressway Authorities throughout Florida and support activities will be performed.

1.3 Related Documents

The following documents were used to develop this document:

SwRI Qualification Response: Response to the Invitation to Negotiate (ITN): Statewide Transportation Management Center Software Library System, Negotiation Number: ITN-DOT-02/03-9025-RR, SwRI Proposal No. 10-35924, dated: November 18, 2002.

SwRI Technical Proposal: Technical Proposal for Invitation to Negotiate (ITN): Statewide Transportation Management Center Software Library System, Negotiation Number: ITN-DOT-02/03-9025-RR, SwRI Proposal No. 10-35924, dated: January 31, 2003.



SwRI Cost Proposal: Cost Proposal for Invitation to Negotiate (ITN): Statewide Transportation Management Center Software Library System, Negotiation Number: ITN-DOT-02/03-9025-RR, SwRI Proposal No. 10-35924, dated: January 31, 2003.

SwRI BAFO letter: Southwest Research Institute® Proposal No. 10-35924, “Invitation to Negotiate (ITN): Statewide Transportation Management Center Software Library System”, Reference: Negotiation Number: ITN-DOT-02/03-9025-RR, dated: May 5, 2003.

FDOT procurement document: Invitation To Negotiate (ITN), Negotiation Number: ITN-DOT-02/03-9025-RR, Statewide Transportation Management Center Software Library System, dated: October 21, 2002.

FDOT Scope of Services: Statewide Transportation Management Center Software Library System: Scope of Services, September 22, 2003.

FDOT Requirements Document: Statewide Transportation Management Center Software Library System: Requirements Specification, June 3, 2003.

Southwest Research Institute, TMC Software Study, November 15, 2001.

Southwest Research Institute, Introduction to an Operational Concept For the Florida Statewide Library, FDOT – OCD – 1.0, March 31, 2002.

World Wide Web Consortium (W3) website: http://www.w3.org.

SunGuide Project website: http://sunguide.datasys.swri.edu.

1.4 Contacts The following are contact persons for the SunGuide project:

Liang Hsia, FDOT Project Manager, [email protected], 850-410-5615 John Bonds, Senior ITS Specialist, [email protected], 408-873-2514 David Chang, ITS Specialist, [email protected], 850-410-5622 Steve Dellenback, SwRI Project Manager, [email protected], 210-522-3914 Robert Heller, SwRI Software Project Manager, [email protected], 210-522-3824 Charlie Wallace, PBF Deputy Project Manager, [email protected], 352-374-6635 John Schumitz, PBF Software Project Manager, [email protected], 301-816-1852

The following are contacts that will be used by the SunGuide software project team to assure consistency with other FDOT projects and FDOT procedures:

Dan Baxter, PB Farradyne, FDOT C2C Project, [email protected], 407-587-7809 David Lambert, University of North Florida, RWIS, [email protected], 904-620-3881 Bob Colins, PBS&J, Emergency Evacuation, [email protected], 850-575-1800 John Fain, FDOT, Comptroller, [email protected], 850-921-7332 Leslie Jacobson, PB Farradyne, Ramp Metering, [email protected], 206-382-5290



2. Baseline Identification

2.1 Definitions The following definitions are provided to facilitate common terms of reference.

• Baseline: A particular version of a baseline item whose status and content are known, which is reproducible, and which has some particular and specified designation or reason for existence. All deliverables are considered to be a baseline item. For example, a software baseline might be a snapshot of the software used for an FDOT demonstration, or a formal release incorporating some set of new features which the previous release did not have. A baseline of a Software Requirements Specification (SRS) might be the version approved following a Software Requirements Review (SRR).

• Baseline Item: A product of a software development effort which is to be maintained under configuration management. Typical baseline items include plans, specifications, and software source code. Software baseline items are sometimes referred to as Computer Software Configuration Items (CSCI).

• Configuration Audit: Configuration audits validate that the design and the final product conform to approved functional requirements defined in specifications and that the approved changes to the initially approved specifications have been incorporated into the design and final product.

• Configuration Status Accounting: Configuration Status Accounting provides a set of reports that contain information concerning the entities under Configuration Management.

• Configuration Management: The process of selecting items whose configuration and change status will be controlled (baseline items), defining the process by which those items will be controlled, and then implementing that process.

• Engineering Change Requests (ECRs): A formal request for a change to requirements. The use of ECRs implies that an approval process (typically an SCCB activity) is required to review/approve proposed changes.

• Module: A component of a software baseline item, sometimes referred to as a Computer Software Component (CSC). A CSCI is composed of one or more CSCs.

• Software Problem Reports: A tool used to track baselined work product issues, other than requirements changes.

• Software Configuration Control Board (SCCB): A group of people responsible for evaluating and approving or disapproving proposed changes to baseline items, and for ensuring implementation of approved changes.

2.2 Baseline Deliveries SwRI will establish baselines to assure reproducibility of artifacts that have been delivered to FDOT. SwRI will deliver baselines in accordance with the CDRLs listed in Section 4 of the Scope of Services. SwRI projected baseline deliveries are shown in Table 2.1.



Table 2.1 – Projected SunGuide Baseline Deliveries Item Description/Milestone Initial Baseline Baseline of code prior to SunGuide development

work Release 1P1 Prior to Test Readiness Review (TRR) Release 1 Following Acceptance Test Procedure (ATP)

execution Release 2a Prior to TRR Release 2a Following ATP execution Release 2b Prior to TRR Release 2b Following ATP execution Milestone Demonstration Software As required

1 The suffix P denotes preliminary or pre-test.



3. Resources

3.1 Project SCM Staff Assignments This section defines key project SCM staff assignments.

• Software Configuration Control Board (SCCB) will be composed of the following:

o SCCB Chairman (FDOT PM), o FDOT Additional members, o SwRI Project Manager (PM), o SwRI Software Project Manger (SPM), and o SwRI Project Configuration Manager (PCM).

The SCCB will approve all baselines and modifications to the baseline for the project.

• Project Configuration Manager (PCM) has the following responsibilities:

o Managing access and updates to the Project Repository. o Creating software products from the Project Repository. o Verifying that appropriate baselines are in the Project Repository. o Performing Configuration Management (CM) status accounting and audits.

• Software Engineering (SE) Secretarial Staff. The Intelligent Transportation Systems (ITS) Section secretary is primarily responsible for maintaining the SE Archive for the project. The ITS Section secretary has the following responsibilities:

o Placing an electronic copy of project deliverables in the SE Archive. o Placing a "compressed" copy of the final Project Repository into the SE Archive

(and/or the physical/paper archive) at the conclusion of a project.

3.2 Tools and Project Repository

3.2.1 Rational® Tool-Based Method The SunGuide project will use the Rational ClearCase LT2 tool in the configuration management process and ClearQuest for Engineering Change Request (ECR) and Software Problem Report (SPR) tracking. ClearCase will be installed behind the SwRI firewalls; such installation will prohibit outside organizations from accessing the SwRI on-line repository. SwRI will make available the baselines to the FDOT on a schedule as described in 2.2.

ClearCase is designed for storage and version control of artifacts for the project. All baselined code and document deliverables will be stored in ClearCase, i.e. ClearCase will be used to capture project baselines. ClearCase LT and ClearQuest were selected based on SwRI’s past experience with Rational tools and discussions with Rational representatives on the appropriate tools for this project. Additional information on these tools can be found on the following web site: http://www-3.ibm.com/software/rational/offerings/ ppa.html.

2 ClearCase and ClearCase LT are separate products, for the purposes of this document, the terms will be used interchangeably.



In the following sections, the use of ClearCase to manage project source code and documentation and other considerations related to SCM for the SunGuide Project are discussed. Because of the iterative nature of this project, some CM-related material will change from iteration to iteration and will be documented in changes to this document or in supplemental documentation to be developed as required.

3.2.1.1 Version Control of Software Assets Initial baseline project artifacts are being obtained under license agreement from the Texas Department of Transportation. These artifacts will be maintained in the SwRI Master Configuration Management Repository (MCMR). The initial baseline repository for the SunGuide project will be populated with artifacts from the MCMR, artifacts from the Maryland Department of Transportation CHART II and artifacts from PB Farradyne MIST product. The SwRI SunGuide repository will also contain future baselines identified as Release 1, Release 2a, and Release 2b. The SunGuide repository will be controlled using ClearCase.

3.2.1.2 ClearCase Repository Table 3.1 describes the ClearCase project file server.

Table 3.1 – ClearCase Repository Description

Project File Server Archimedes.datasys.swri.edu

Project File Server Type Windows 2003

Project Root Directory Location

\\Archimedes\FDOT\Clearcase_Repository\

Project Root Directory Environment Variable

N/A for Windows

Project File Server Access Method

\\Archimedes\FDOT\Clearcase_Repository\

3.2.1.3 VOB Structure In ClearCase, each project is typically composed of VOBs. A VOB is a collection of versioned items (known as elements). While a project in ClearCase can have multiple VOBs, it is less confusing to organize components so that they are part of a single VOB.

3.2.1.3.1 Initial Release Directory Structure The baseline release of the SunGuide software the directory structure is shown in Figure 3.1.



PM Admin_rvws ATP Cust_comm Status_reports Risk_Mit Schedules SCMP SDP S_Int SQAP SSP Train

Doc COO SRS SDD SUM VDD ATP ICD

DBUS DMS CCTV TD IM C2C RM RWIS AD HAR WS EE

DBDD

SubSys DBUS

Src Del

UI Src Del

Map Src Del

DMS Src Del

CCTV Src Del

TD Src Del

IM Src Del

C2C Src Del

RM Src Del

RWIS Src Del

AD Src Del

HAR Src Del

WS Src Del

EE Src

Del

Figure 3.1 – SunGuide Initial Baseline Structure

3.2.1.3.1.1 Repository Contents Baseline ready deliverable documents, source code, and installation files will be source controlled in the ClearCase repository.

The contents of each ClearCase_Repository directory are summarized below.



Directory Name Description/Contents

Del Contains directories and the baselined code that is ready for delivery to FDOT.

Doc Contains folders or baselined files of the documents required for the system and the ICDs for the subsystems.

PM Contains the deliverable and non-deliverable artifacts that are required for overall project management and communication with FDOT.

Src Contains directories and the baselined source code for each of the subsystems.

SubSys Contains the directories and files for the initial baseline licensed from TxDOT and the modified files and directories for the applicable release (e.g. Release 1, Release 2a, Release 2b).

3.2.1.3.1.2 Abbreviation List Due to ClearCase’s path length limitations, it is beneficial to keep file and folder names as short as possible. Whenever possible, the abbreviations shown below should be used when naming folders and files.

Abbreviation Meaning AD Archive Data ATMS Advanced Traffic Management System ATP Acceptance Test Plan C2C Center-to-Center CCTV Closed Circuit Television COC FDOT Central Office Configuration COO Concept of Operations DB Database DBDD Database Design Document DBUS Data Bus Del Deliverable (Installable code) DMS Dynamic Message Sign EE Emergency Evacuation ESS Environmental Sensor System HAR Highway Advisory Radio ICD Interface Control Document IM Incident Management IMDBMS Integrated Maintenance Database Management System Map Map display and control



Abbreviation Meaning PM Project Management PV Process Viewer RM Ramp Metering RWIS Road Weather Information System SCMP Software Configuration Management Plan SD Statewide Driver SDD Software Design Document SDP Software Development Plan SL Status Logger SQAP Software Quality Assurance Plan Src Source SRS Software Requirements Specification SSP Software Security Plan SUM Software Users Manual Sys System TD Traffic Detection, driver for Bitrans238I-95 TM Traceability Matrix TMC Transportation Management Center TSS Traffic Sensor System UI User Interface VDD Version Description Document WS Web Server

3.2.1.3.1.3 ClearCase Directory Structure The lower-level directory structures may change throughout the life of the project. Questions about where to place a document in ClearCase should be referred to the task lead or the designated PCM.

3.2.1.3.2 Release 1 Directory Structure. The FDOT IV&V agent noted that this directory does not easily support building the software “executables.” The SwRI SCCB accepted this recommendation and reorganized the directory structure for subsequent relesase to more closely match the directory structure used in daily development. This structure helps eliminate or reduce the problems associate with moving managed items between VSS and ClearCase. Additionally the ClearCase tools for accomplishing this task (moving items from VSS to ClearCase) can be utilized to automate this task.

The Release 1 directory structure is shown in Appendix B. The structure for Release 2a, and 2b will be similar. Only those portions of the directory structure relevant to a particular baseline of the project will be populated.



3.2.2 Visual Source Safe (VSS) Workspaces VSS is a Microsoft product that is integrated in SwRI’s development environment. It will be used for day-to-day development activities. The files required from the appropriate baseline maintained in ClearCase will be exported to the VSS environment. The developers will add to, modify or delete material as required to meet the SunGuide specifications. Once activities to prepare the artifacts for baselining have been completed, the files will be imported into the appropriate ClearCase directories for delivery to FDOT, as specified in the Scope of Services.

Project File Server Archimedes.datasys.swri.edu

Project File Server Type Windows 2000

Project Root Directory Location

C:\FDOT\VSS Repository\(on Archimedes file server)

Project Root Directory Environment Variable

N/A for Windows

Project File Server Access Method

\\Archimedes\FDOT\VSS Repository\



4. Development Procedures for Version Control The following sections describe CM procedures applicable to the software developers.

4.1 Procedures for Rational Tools

4.1.1 Rational ClearCase The base item in ClearCase is a “Versioned Object.” This is a single piece of code or other work that can be stored in multiple versions. The next step “up” is then an “Element”. This refers to all the versions of a single “Versioned Object.” This leads to the top level, which is a “Project” that consists of all the items that are related to a single development effort.

When you are working with ClearCase you will often be working with a VOB. This is a collection of elements that is created to help logically group the items for work as part of a development effort. Multiple VOBs can be created for a single ClearCase installation; however, for this project a single VOB will be used.

4.1.2 Using ClearCase The ClearCase PCM will be the focal point for supplying files or directories to the developers from the FDOT ClearCase baseline repository to the VSS day-to-day working repository. Normally the files and directories required by the SunGuide project will be pushed by the PCM from the TxDOT software repository to the FDOT ClearCase baseline repository. From there the PCM will push them to the VSS working repository. Once the developers have completed development activities and are ready to enter the files and/or directories into the FDOT ClearCase baseline, they will work with the PCM to import those files into the appropriate directory within the FDOT VOB. The updated FDOT ClearCase repository will then be the baseline for subsequent pushes to the development environment.

4.2 Version Control of Documents ClearCase will be used to control both documents and software artifacts, the procedure for version control of documents is described in the previous section.

4.3 Commenting Not only does ClearCase have the capability to store multiple versions of a document or artifact as a single object, but it can also record information about the changes made to that object. ClearCase will store the dates and times that objects were accessed and changed, but it is up to the developers and the PCM to store information about those changes through the use of the Comment field when checking files into ClearCase. A descriptive, meaningful comment should be made whenever changes are made to an object.



4.4 Backups

4.4.1 ClearCase Backup The following table describes key parameters of the ClearCase server backup strategy. The ClearCase server is hosted on the machine Archimedes and is used to store all baselined project artifacts, including documents and source code.

Backup Responsibility Primary: Division 10 Network Support Group

Secondary: PCM

Backup Frequency Daily

CM Baseline Frequency As directed by the PM/SPM

Backup Type See the detailed discussion below

Backup Process See the detailed discussion below

Since a ClearCase server outage could significantly impact the project during critical phases, the backup strategy should be robust. The restore strategy should quickly and faithfully reconstruct the project repository. While the Redundant Array of Inexpensive Disks (RAID) 5 structure of the project server provides a first line of defense against data loss, additional backup procedures will be implemented to provide more robust protection of the data.

A standard functionality of the ClearCase software is to save past and deleted versions of stored files. The most recent day's backup should, in theory, hold all or nearly all previous file versions. However, since ClearCase software database corruption may occur and since this corruption could go undetected for several days, several days worth of backups will be kept.

To provide a complete backup of the ClearCase Repository by the Veritas Backup Exec software as it is configured by the Div 10 Network Support Group, the Clear Case administrator will need to do the following after each significant change to the Clear Case Repository (e.g. when updates from VSS are incorporated, elements from outside sources such as TxDOT are added, or structure changes to the repository are made.):

1. Log on to the ClearCase Server (Archimedes) as an administrator or with a user name that is contained in the Group “Domain Users”.

2. Lock the VOBs to be backed up using the ClearCase Admin Console (ccadminconsole). As a minimum this should include VOBs \FDOT and \projects.

3. Stop the Clear Case server using the Clear Case Console on the Archimedes Control Panel.

4. Backup the Clear Case Repository using xcopy.

a. Start the command line interface (Start\Run\cmd).

b. Use the following syntax to preserve the complete directory structure, the security descriptors, and suppress requests for permission to overwrite existing files.

Xcopy D:\FDOT\ClearCase_Repository clearcase_backup /E /O /Y

5. Restart the Clear Case server using the Clear Case Console on the Archimedes Control Panel.



6. Unlock the VOBs locked earlier in the backup process using the ClearCase Admin Console (ccadminconsole). As a minimum, this should include VOBs \FDOT and \projects.

The ClearCase server is backed up once each evening, after work hours: using a differential backup technique provided by the Veritas Backup Exec software. These tapes are stored on the tape backup server’s robotic tape library for two weeks to facilitate rapid restoration of files should the need arise. This robotic tape library is located in a server room in a different part of the building from the location of the project repository to add a level of protection from localized incidents in the project area.

• A daily differential backup is also run to provide tapes for offsite storage in the event a restoration from a catastrophic event within the project building is required. These are also kept for two weeks.

• A full backup is performed weekly on Friday nights after normal work hours and stored on the robotic tape library for up to six weeks. In the event additional room is required, the oldest weekly backups may be moved to storage near the robotic tape library to maintain the ability to restore files expeditiously.

• A second full backup is performed weekly on Saturday night for offsite storage to support recovery in the event of a major catastrophe in the project building. These backups are also kept for six weeks.

• Finally a full backup is performed monthly and kept offsite for two years as another restoral capability.

The offsite backup tapes are maintained in a fireproof safe in a SwRI building (Blg 128) removed from the project building to limit the likely-hood that a major catastrophe could affect both the project location and the backup site but still be close enough for timely restoral, if required, for less than catastrophic events.

The Division 10 Network Support Group (NSG) practices restoral actions approximately twice every three weeks. These restoral actions verify that the backup system is working correctly and that files can be restored successfully. The SwRI NSG maintains backup logs. They will be verified during Physical Configuration Audits.

4.4.2 ClearQuest Backup The following table describes key parameters of the ClearQuestData Server backup strategy. The ClearQuestData Server is also hosted on the machine Archimedes and is used to store and track project issues and defects.


Secondary: System Administration Team



Backup Type See ClearCase backup description above

Backup Process See ClearCase backup description above

Since the ClearQuest server is co-located with the ClearCase server on the machine Archimedes, backup procedures have been developed that are the same for both.



4.4.3 VSS Backup The following table describes key parameters of the VSS backup strategy. The VSS Server is also hosted on the machine Archimedes and is used to store and track project issues and defects.


Secondary: System Administration Team



Backup Type See VSS description above

Backup Process See VSS backup description above

Since the VSS server is co-located with the VSS server on the machine Archimedes, backup procedures have been developed that are the same for both.

4.4.4 Local PC Files Backup Working files resident on local developers' machines should be checked into the VSS working repository soon after creation so that they can be backed up to protect against their loss due to accidental or deletion or corruption. Since that repository also resides on the machine Archimedes, it will be backed up by the same procedures noted for the ClearCase repository and the ClearQuest repository. Backing up working files that are resident on local developers' machines is the responsibility of the developer. These files should be backed up at appropriate intervals to floppy drive, CD-ROM, or other media.



5. Configuration Status Accounting and Audit

5.1 Configuration Status Accounting The status of the project configuration management repository will be assessed whenever a new baseline is created or at the direction of the PM, SPM, or SCCB.

A checklist and procedure for performing Configuration Status Accounting is provided in Appendix A.

To conduct project configuration status accounting, perform the activities and inspections described in the table in Appendix A. Rate each area as Green (fully compliant), Yellow (partially compliant), or Red (non-compliant). If an area is Red, record corrective action in the Comments column. If an item is not applicable, write “N/A” in the Comments column along with a brief explanation. Audit each area in the context of the project’s Software Configuration Management Plan, as outlined in the latest Software Development Plan (SDP) and the latest Management Review Meeting minutes.

5.2 Configuration Management Audit Configuration audits will be conducted to validate that the design and the final product conform to approved functional requirements defined in specifications and that the delivered product is complete. The PCM will ensure that the released version of the software products is available for the audit so that it can be verified that the software performs as required by its allocated configuration. Two activities are involved in a CM audit:

Functional Configuration Audit: Verifies that the product being completed meets the requirements.

Physical Configuration Audit: Verifies that the files contained on the physical media are the proper version and constitute a complete system.

5.2.1.1 Functional Configuration Audit Functional Configuration Audits will be performed as part of Release 1, 2a, and 2b.

The following steps are performed during a Functional Configuration Audit:

1. The product is tested using the Software Integration Case Procedures (SCIP) for Release 1 and 2a and the Acceptance Test Plan (ATP) for Release 2b to verify that the requirements in the Software Requirements Specification (SRS) are implemented.

2. A Functional Configuration Audit report is developed which includes the following information:

a) Name of software product b) Auditor c) Dates of audit d) Results of test (a reference to project documentation is acceptable if

the results are documented.)



5.2.1.2 Physical Configuration Audit Physical Configuration Audits will be performed to assure that the software distribution under review is complete. Typically the first step in a project's ATP is to verify that the configuration and installation information contained in the SUM and VDD are correct. A Physical Configuration Audit is typically performed before a software product is delivered to FDOT, immediately before a Functional Configuration Audit.

The following steps are performed during a Physical Configuration Audit:

1. The software product is placed on electronic media (typically in the same form as it will be delivered).

2. The Software's Software User's Manual (SUM) and Version Description Document (VDD) are utilized to determine what files are needed to build a software product.

3. The software delivery media is verified to insure that all necessary files are available.

4. The software product is built; any build discrepancies are noted. 5. A Physical Configuration Audit report is developed which includes the following

information: a) Name of software product b) Auditor c) Dates of audit d) List of files utilized (a reference to project documentation is acceptable) e) Results of build



6. Engineering Change Request and Software Problem Report Tracking

Engineering Change Requests (ECRs) and Software Problem Reports (SPRs) will be tracked using Rational® ClearQuest.

6.1 Engineering Change Requests Because ECRs can by submitted by FDOT and by SwRI, the ClearQuest tool will be used to track ECRs. The SCCB is responsible for the overall administration of the ECRs and will determine which ECRs will be contained in which baseline. The SCCB will determine the impact of ECRs, will determine if ECRs submitted are actually ECRs or SPRs, and provide recommendations. Once approved by the SCCB, the SPM is responsible for assignment and resolution of ECRs. The master ECR file is maintained in the project repository.

An ECR is divided into four major sections:

Requests

Evaluation Results

Recommendations

Disposition

At a minimum, the following information will be provided in the sections:

Requests:

Change Request (CR) Identifier (unique number for each CR entered by the Development Agency)

Date CR submitted

Requesting organization

Point of Contact - including name, phone number, e-mail address

Type of change (addition, modification, or deletion)

Requirement text

Rationale

Threshold

Objective

Priority (Urgent - mission critical change needs to be implemented during current build; Routine - should be implemented consistent with the current development schedule)



Evaluation Results:

Type of evaluation performed: Functional, Developmental, Operational

For each evaluation performed:

Organization assigned to perform evaluation

Point of Contact for evaluation - including name, phone number, e-mail address

Date evaluation task assigned

Suspense date

Evaluation results

Recommendations:

Date of meeting when CR reviewed

Recommendation

Rationale

Clarification request

Disposition:

Date Configuration Control Board (CCB) addressed CR

CR Status: Possible statuses include: Request Received, Awaiting clarification, Undergoing Evaluation, Evaluation Complete, Recommendation Complete, Closed

CR Disposition: Approved, Approved with modification, Disapproved

6.2 Software Problem Reports The SPM is responsible for prioritization, assignment, and resolution of SPRs. The master SPR log is maintained in the project repository.

SPRs will contain the following:

• Uniquely assigned identifier • Title • Problem status (open or closed) • Priority (high, medium, or low) • Date reported • Reporting individual • Problem description • Software component affected • Version or baseline affected • Person responsible to fix the problem • Description of actions taken or resolution • Date of resolution


SunGuide-CMP-1.0.1

Appendix A

Configuration Status Accounting


SunGuide-CMP-1.0.1

Audit Activity Green Yellow Red Comments

Project Repository Status

Are all baselined documents and Computer Software Configuration Item (CSCIs) in the project CM repository?

Are all historical project artifacts (paper and electronic) that have been delivered to FDOT in the departmental archive?

Source Code Control

Have the development directories been set up as described in the project CMP?

Have source files under development been checked into ClearCase?

Run a report listing the status of each source file. Are there any files currently checked out which should not be?

Are there any files that have any indication of corruption or other bad status?

Have critical project utilities (such as XML parsers or other libraries/binaries) been checked into source code control?

Have baselined modules been captured using an appropriately named ClearCase Baseline?

Checkout a copy of a baseline. Does each directory contain the source files, binaries, and output from the build process (if applicable)? Are there any files in those directories that should not be there? Are any files missing?


SunGuide-CMP-1.0.1

Audit Activity Green Yellow Red Comments

Versioning

Has each baseline item document been assigned a unique identifier, and is that identifier used consistently across the project?

Has each baseline item CSCI been assigned a unique identifier, and is that identifier used consistently across the project?

Are baseline items (documents and software) being assigned version numbers consistent with the SDP? Record the current version of all baseline items in the column to the right (or attach separate sheet).

Engineering Change Requests/Problem Reports

Has the project ECR/SPR system been implemented and is it being used?

Is the status of each ECR and SPR current?

Backups

Are backups being performed regularly and as described in the project CMP?

Are backup media stored in a separate facility as described in the CMP?

Retrieve a backup. Select one or more files that have changed since that backup was performed. Attempt to restore the file(s) from the backup media and verify that the file(s) were successfully restored


SunGuide-CMP-1.0.1

Audit Completed By: Date:


SunGuide-CMP-1.0.1

Appendix B

Release 1 Directory Struture


SunGuide-CMP-1.0.1

$/ $/Dlls $/Documents $/Documents/Database $/Documents/Database/Population scripts $/Documents/Designs $/Documents/Emergency Evacuation $/Documents/ICD $/Documents/ICD/CCTV $/Documents/ICD/DataBus $/Documents/ICD/DMS $/Documents/ICD/HAR $/Documents/ICD/Incident Management $/Documents/ICD/TSS $/Documents/Planning Documents $/Documents/Sdd $/Documents/Sdd/SddResources $/Documents/Sdd/SddResources/PbfResources $/Documents/Srs $/Documents/Srs/soda finished docs $/Documents/Srs/soda templates $/Documents/TestPlans $/Documents/TestPlans/Admin Editor $/Exes $/Installers $/Installers/BuildFiles $/Installers/BuildFiles/DMS $/Installers/DevStudioV9 $/Installers/DevStudioV9/SunGuide $/Installers/DevStudioV9/SunGuide/Disk1 $/Installers/DevStudioV9/SunGuide/InstallFiles $/Installers/DevStudioV9/SunGuide/ScriptFiles $/Installers/DmsSubsystem $/Installers/DmsSubsystem/DmsServices $/Installers/DmsSubsystem/DmsServices/DmsPollingSvc $/Installers/DmsSubsystem/DmsServices/DmsServicesLib $/Installers/DmsSubsystem/DmsServices/DmsXmlInterfaceSvc $/Installers/DmsSubsystem/DmsServices/StatewideDriverSvc $/Installers/DmsSubsystem/InstallFiles $/Installers/DmsSubsystem/Lib


SunGuide-CMP-1.0.1

$/Installers/DmsSubsystem/StatewideDriverSvc $/Jars $/Jars/DMS $/PBF Code Drops $/PBF Code Drops/April_18,2004 $/PBF Code Drops/April_23,2004 $/PBF Code Drops/April_28,2004 $/PBF Code Drops/April_29,2004 $/PBF Code Drops/April_8,2004 $/PBF Code Drops/April_9,2004 $/Presentations $/Presentations/demos $/Presentations/demos/CAMERA_PROTOTYPE $/Presentations/demos/CAMERA_PROTOTYPE/CCTVControlServer $/Presentations/demos/CAMERA_PROTOTYPE/CCTVControlServer/bin $/Presentations/demos/CAMERA_PROTOTYPE/CCTVControlServer/build $/Presentations/demos/CAMERA_PROTOTYPE/CCTVControlServer/build/classes $/Presentations/demos/CAMERA_PROTOTYPE/CCTVControlServer/build/classes/gov $/Presentations/demos/CAMERA_PROTOTYPE/CCTVControlServer/build/classes/gov/its $/Presentations/demos/CAMERA_PROTOTYPE/CCTVControlServer/build/classes/gov/its/cctv $/Presentations/demos/CAMERA_PROTOTYPE/CCTVControlServer/build/classes/gov/its/net $/Presentations/demos/CAMERA_PROTOTYPE/CCTVControlServer/build/classes/gov/its/utils $/Presentations/demos/CAMERA_PROTOTYPE/CCTVControlServer/icons $/Presentations/demos/CAMERA_PROTOTYPE/CCTVControlServer/intellij $/Presentations/demos/CAMERA_PROTOTYPE/CCTVControlServer/src $/Presentations/demos/CAMERA_PROTOTYPE/CCTVControlServer/src/gov $/Presentations/demos/CAMERA_PROTOTYPE/CCTVControlServer/src/gov/its $/Presentations/demos/CAMERA_PROTOTYPE/CCTVControlServer/src/gov/its/cctv $/Presentations/demos/CAMERA_PROTOTYPE/CCTVControlServer/src/gov/its/cctv/icons $/Presentations/demos/CAMERA_PROTOTYPE/CCTVControlServer/src/gov/its/net $/Presentations/demos/CAMERA_PROTOTYPE/CCTVControlServer/src/gov/its/utils $/SourceCode $/SourceCode/Admin $/SourceCode/Admin/Code $/SourceCode/Admin/Equip $/SourceCode/Admin/Equip/Cctv $/SourceCode/Admin/SunGuideAdmin $/SourceCode/Admin/TestDatabase $/SourceCode/Cctv $/SourceCode/Cctv/Cctv


SunGuide-CMP-1.0.1

$/SourceCode/Cctv/CctvDatabase $/SourceCode/Cctv/Driver $/SourceCode/Cctv/Driver/CctvPelcoDriver $/SourceCode/Common $/SourceCode/Common/CommonConstants $/SourceCode/Common/ConfigFileReader $/SourceCode/Common/Database $/SourceCode/Common/GenericSubsystem $/SourceCode/Common/MainProcess $/SourceCode/Common/Security $/SourceCode/Common/SecurityController $/SourceCode/Common/StatusLogger $/SourceCode/Common/XmlInterface $/SourceCode/Common/XmlUtility $/SourceCode/CommunicationMgr $/SourceCode/CommunicationMgr/CommunicationMgrApp $/SourceCode/CommunicationMgr/CommunicationMgrLib $/SourceCode/CommunicationMgr/CommunicationMgrSvc $/SourceCode/CppUtil $/SourceCode/CppUtil/UtilLib $/SourceCode/CppUtil/ZShared $/SourceCode/CppUtil/ZShared/Include $/SourceCode/CppUtil/ZShared/Library $/SourceCode/DataBus $/SourceCode/DataBus/DataBusSys $/SourceCode/DataBus/Deprecated $/SourceCode/Dms $/SourceCode/Dms/gov $/SourceCode/Dms/gov/its $/SourceCode/Dms/gov/its/dms $/SourceCode/Dms/gov/its/dms/conflicts $/SourceCode/Dms/gov/its/dms/converter $/SourceCode/Dms/gov/its/dms/dmsmain $/SourceCode/Dms/gov/its/dms/dmsmain/dmsmainerrors $/SourceCode/Dms/gov/its/dms/externalinterface $/SourceCode/Dms/gov/its/dms/libraries $/SourceCode/Dms/gov/its/dms/libraries/configsys $/SourceCode/Dms/gov/its/dms/libraries/dbaccess $/SourceCode/Dms/gov/its/dms/libraries/dmsclasses $/SourceCode/Dms/gov/its/dms/libraries/dmsgroup


SunGuide-CMP-1.0.1

$/SourceCode/Dms/gov/its/dms/libraries/message $/SourceCode/Dms/gov/its/dms/libraries/misc $/SourceCode/Dms/gov/its/dms/libraries/sequence $/SourceCode/Dms/gov/its/dms/polling $/SourceCode/Dms/gov/its/dms/transactions $/SourceCode/Dms/gov/its/dms/transactions/requests $/SourceCode/Dms/gov/its/dms/transactions/requests/configdms $/SourceCode/Dms/gov/its/dms/transactions/requests/configsys $/SourceCode/Dms/gov/its/dms/transactions/requests/conflict $/SourceCode/Dms/gov/its/dms/transactions/requests/dmsgroup $/SourceCode/Dms/gov/its/dms/transactions/requests/externalinterface $/SourceCode/Dms/gov/its/dms/transactions/requests/font $/SourceCode/Dms/gov/its/dms/transactions/requests/message $/SourceCode/Dms/gov/its/dms/transactions/requests/messagelib $/SourceCode/Dms/gov/its/dms/transactions/requests/retrieve $/SourceCode/Dms/gov/its/dms/transactions/requests/sequence $/SourceCode/Dms/gov/its/dms/transactions/requests/sequencelib $/SourceCode/Dms/gov/its/dms/transactions/requests/spelling $/SourceCode/Dms/gov/its/dms/transactions/requests/status $/SourceCode/Dms/gov/its/dms/transactions/requests/user $/SourceCode/Dms/gov/its/dms/transactions/responses $/SourceCode/Dms/gov/its/dms/transactions/responses/configdmsresponse $/SourceCode/Dms/gov/its/dms/transactions/responses/configsysresponse $/SourceCode/Dms/gov/its/dms/transactions/responses/conflictresponse $/SourceCode/Dms/gov/its/dms/transactions/responses/dmsgroup $/SourceCode/Dms/gov/its/dms/transactions/responses/externalinterfaceresponse $/SourceCode/Dms/gov/its/dms/transactions/responses/fontresponse $/SourceCode/Dms/gov/its/dms/transactions/responses/messagelib $/SourceCode/Dms/gov/its/dms/transactions/responses/messageresponse $/SourceCode/Dms/gov/its/dms/transactions/responses/retrieve $/SourceCode/Dms/gov/its/dms/transactions/responses/sequence $/SourceCode/Dms/gov/its/dms/transactions/responses/sequencelib $/SourceCode/Dms/gov/its/dms/transactions/responses/spellingresponse $/SourceCode/Dms/gov/its/dms/transactions/responses/statusresponse $/SourceCode/Dms/gov/its/dms/transactions/responses/user $/SourceCode/Dms/gov/its/dms/userinterface $/SourceCode/Dms/gov/its/dms/userinterface/beans $/SourceCode/Dms/gov/its/dms/userinterface/configdms $/SourceCode/Dms/gov/its/dms/userinterface/dmsgroup $/SourceCode/Dms/gov/its/dms/userinterface/dmssysstatus


SunGuide-CMP-1.0.1

$/SourceCode/Dms/gov/its/dms/userinterface/images $/SourceCode/Dms/gov/its/dms/userinterface/message $/SourceCode/Dms/gov/its/dms/userinterface/sequences $/SourceCode/Dms/gov/its/dms/userinterface/systemconfig $/SourceCode/Dms/gov/its/dms/xmlinterface $/SourceCode/Dms/gov/its/dms/xmlinterface/xmlhandlers $/SourceCode/Dms/gov/its/driver $/SourceCode/Dms/gov/its/driver/address $/SourceCode/Dms/gov/its/driver/applicationlayer $/SourceCode/Dms/gov/its/driver/commands $/SourceCode/Dms/gov/its/driver/commands/fds $/SourceCode/Dms/gov/its/driver/commands/markIV $/SourceCode/Dms/gov/its/driver/commands/ntcip $/SourceCode/Dms/gov/its/driver/commands/telespot $/SourceCode/Dms/gov/its/driver/datalinklayer $/SourceCode/Dms/gov/its/driver/driverdata $/SourceCode/Dms/gov/its/driver/driverdata/fds $/SourceCode/Dms/gov/its/driver/driverdata/markIV $/SourceCode/Dms/gov/its/driver/driverdata/oid $/SourceCode/Dms/gov/its/driver/driverdata/telespot $/SourceCode/Dms/gov/its/driver/drivermanager $/SourceCode/Dms/gov/its/driver/equipmentmanager $/SourceCode/Dms/gov/its/driver/exceptions $/SourceCode/Dms/gov/its/driver/language $/SourceCode/Dms/gov/its/driver/physicallayer $/SourceCode/Dms/gov/its/driver/protocol $/SourceCode/Dms/gov/its/driver/simulator $/SourceCode/Dms/gov/its/driver/simulator/gui $/SourceCode/Dms/gov/its/net $/SourceCode/Dms/gov/its/net/connection $/SourceCode/Dms/gov/its/net/security $/SourceCode/Dms/gov/its/net/socketconnectionpkg $/SourceCode/Dms/gov/its/net/xml $/SourceCode/Dms/gov/its/net/xml/xmlhandler $/SourceCode/Dms/gov/its/tester $/SourceCode/Dms/gov/its/tester/client $/SourceCode/Dms/gov/its/tester/converter $/SourceCode/Dms/gov/its/tester/main $/SourceCode/Dms/gov/its/util $/SourceCode/Dms/gov/its/util/accessslogger


SunGuide-CMP-1.0.1

$/SourceCode/Dms/gov/its/util/configurationfile $/SourceCode/Dms/gov/its/util/properties $/SourceCode/Dms/gov/its/util/xml $/SourceCode/ExecutiveHandler $/SourceCode/ExecutiveHandler/ExecClientLib $/SourceCode/ExecutiveHandler/ExecutiveHandler $/SourceCode/ExecutiveHandler/ExecutiveHandler/ExecHandlerApp $/SourceCode/ExecutiveHandler/ExecutiveHandler/ExecHandlerApp/res $/SourceCode/ExecutiveHandler/ExecutiveHandler/ExecHandlerDll $/SourceCode/ExecutiveHandler/ExecutiveHandler/ExecHandlerDll/res $/SourceCode/ExecutiveHandler/ExecutiveHandler/ExecHandlerEditor $/SourceCode/ExecutiveHandler/ExecutiveHandler/ExecHandlerEditor/res $/SourceCode/ExecutiveHandler/ExecutiveHandler/ExecHandlerLib $/SourceCode/ExecutiveHandler/ExecutiveHandler/ExecHandlerSvc $/SourceCode/ExecutiveHandler/ExecutiveHandler/ExecHandlerSvc/res $/SourceCode/ExecutiveHandler/ExecutiveHandler/ExecHandlerTestClient $/SourceCode/ExecutiveHandler/ExecutiveHandler/ExecHandlerTestClient/res $/SourceCode/ExecutiveHandler/ExecutiveHandler/ExecHandlerViewer $/SourceCode/ExecutiveHandler/ExecutiveHandler/ExecHandlerViewer/res $/SourceCode/ExecutiveHandler/TestExecClient $/SourceCode/NotifyManager $/SourceCode/NotifyManager/NotifyManager $/SourceCode/NotifyManager/NotifyManager/NotifyClientLib $/SourceCode/NotifyManager/NotifyManager/NotifyManagerApp $/SourceCode/NotifyManager/NotifyManager/NotifyManagerSvc $/SourceCode/NotifyManager/NotifyManager/NotifyMgrLib $/SourceCode/StatusLogger $/SourceCode/StatusLogger/Slogger $/SourceCode/StatusLogger/StatusLogger $/SourceCode/StatusLogger/StatusLogger/StatusLogClient $/SourceCode/StatusLogger/StatusLogger/StatusLogClient/res $/SourceCode/StatusLogger/StatusLogger/StatusLoggerCplApplet $/SourceCode/StatusLogger/StatusLogger/StatusLoggerCplApplet/res $/SourceCode/StatusLogger/StatusLogger/StatusLoggerDll $/SourceCode/StatusLogger/StatusLogger/StatusLoggerDll/res $/SourceCode/StatusLogger/StatusLogger/StatusLogServer $/SourceCode/StatusLogger/StatusLogger/StatusLogServer/res $/SourceCode/StatusLogger/StatusLogger/StatusLogService $/SourceCode/StatusLogger/StatusLogger/StatusLogService/res $/SourceCode/StatusLogger/StatusLogger/StatusLogViewer


SunGuide-CMP-1.0.1

$/SourceCode/StatusLogger/StatusLogger/StatusLogViewer/res $/SourceCode/StatusLogger/StatusLogMgdLib $/SourceCode/Tester $/SourceCode/Tester/TestServer $/SourceCode/Tester/TestServerGui $/SourceCode/Tester/TestServerGui/TSApp.root $/SourceCode/Tester/TestServerGui/TSApp.root/TSApp $/SourceCode/Tss $/SourceCode/Tss/TestDriver $/SourceCode/Tss/Tss $/SourceCode/Tss/tssDatabase $/SourceCode/UnitTests $/SourceCode/UnitTests/CctvUnitTest $/SourceCode/UnitTests/CommonUnitTest $/SourceCode/UnitTests/DataBusUnitTest $/SourceCode/UnitTests/TssUnitTest $/SourceCode/UnitTests/XmlInterfaceUnitTest $/SourceCode/UserInterface $/SourceCode/UserInterface/ConnectionManager $/SourceCode/UserInterface/ConnectionManager/BIN $/SourceCode/UserInterface/ConnectionManager/BUILD $/SourceCode/UserInterface/ConnectionManager/CONF $/SourceCode/UserInterface/ConnectionManager/DIST $/SourceCode/UserInterface/ConnectionManager/DIST/lib $/SourceCode/UserInterface/ConnectionManager/LIB $/SourceCode/UserInterface/ConnectionManager/LOGS $/SourceCode/UserInterface/ConnectionManager/SRC $/SourceCode/UserInterface/ConnectionManager/SRC/gov $/SourceCode/UserInterface/ConnectionManager/SRC/gov/its $/SourceCode/UserInterface/ConnectionManager/SRC/gov/its/net $/SourceCode/UserInterface/ConnectionManager/SRC/gov/its/net/connection $/SourceCode/UserInterface/ConnectionManager/SRC/gov/its/util $/SourceCode/UserInterface/ConnectionManager/SRC/gov/its/util/configurationfile $/SourceCode/UserInterface/ConnectionManager/SRC/gov/its/util/xml $/SourceCode/UserInterface/OperatorMap $/SourceCode/UserInterface/OperatorMap/Data $/SourceCode/UserInterface/OperatorMap/Data/CCTV $/SourceCode/UserInterface/OperatorMap/Data/CCTV/parsing $/SourceCode/UserInterface/OperatorMap/Data/Common $/SourceCode/UserInterface/OperatorMap/Data/Common/parsing


SunGuide-CMP-1.0.1

$/SourceCode/UserInterface/OperatorMap/Data/ControlPanel $/SourceCode/UserInterface/OperatorMap/Data/DataBus $/SourceCode/UserInterface/OperatorMap/Data/DMS $/SourceCode/UserInterface/OperatorMap/Data/DMS/parsing $/SourceCode/UserInterface/OperatorMap/Data/IM $/SourceCode/UserInterface/OperatorMap/Data/MapBackground $/SourceCode/UserInterface/OperatorMap/Data/MessagePanel $/SourceCode/UserInterface/OperatorMap/Data/Shields $/SourceCode/UserInterface/OperatorMap/Data/TSS $/SourceCode/UserInterface/OperatorMap/Data/TSS/parsing $/SourceCode/UserInterface/OperatorMap/Data/WaitScreen $/SourceCode/UserInterface/OperatorMap/Data/WinSkin $/SourceCode/UserInterface/OperatorMap/Data/WinSkin/firstscripts $/SourceCode/UserInterface/OperatorMap/Data/WinSkin/scripts $/SourceCode/UserInterface/OperatorMap/Data/WM $/SourceCode/UserInterface/OperatorMap/Data/WM/scripts $/SourceCode/UserInterface/OperatorMap/Structure $/SourceCode/UserInterface/OperatorMap/Structure/Footer $/SourceCode/UserInterface/OperatorMap/Structure/Header $/SourceCode/UserInterface/OperatorMap/Structure/InlineScripts $/SourceCode/UserInterface/OperatorMap/Structure/MapLayer $/SourceCode/UserInterface/OperatorMap/Structure/ScriptLinks $/SourceCode/UserInterface/OperatorMap/Structure/SVGDefs $/SourceCode/UserInterface/OperatorMap/Structure/WaitScreen $/SourceCode/UserInterface/OperatorMap/Structure/WMLayer $/SQL $/SQL/General $/SQL/SunGuide $/SQL/SUNGUIDE $/SupportFiles $/SupportFiles/DMS $/Xml $/Xml/Configuration $/Xml/Documents $/Xml/Documents/common $/Xml/Documents/databus $/Xml/Documents/databus/messages $/Xml/Documents/databus/objects $/Xml/Documents/databus/requests $/Xml/Documents/databus/responses


SunGuide-CMP-1.0.1

$/Xml/Documents/dms $/Xml/Documents/dms/objects $/Xml/Documents/dms/requests $/Xml/Documents/dms/responses $/Xml/Documents/tss $/Xml/Documents/tss/messages $/Xml/Documents/tss/objects $/Xml/Documents/tss/requests $/Xml/Documents/tss/responses $/Xml/ExecutiveHandlerSchemas $/Xml/SampleXml $/Xml/SampleXml/cctv $/Xml/SampleXml/cctv/requests $/Xml/SampleXml/cctv/responses $/Xml/SampleXml/common $/Xml/SampleXml/databus $/Xml/SampleXml/databus/messages $/Xml/SampleXml/databus/objects $/Xml/SampleXml/databus/requests $/Xml/SampleXml/databus/responses $/Xml/SampleXml/dms $/Xml/SampleXml/dms/messages $/Xml/SampleXml/dms/requests $/Xml/SampleXml/dms/responses $/Xml/SampleXml/tss $/Xml/SampleXml/tss/messages $/Xml/SampleXml/tss/objects $/Xml/SampleXml/tss/requests $/Xml/SampleXml/tss/responses $/Xml/Schemas1.0 $/Xml/Schemas1.0/admin $/Xml/Schemas1.0/admin/messages $/Xml/Schemas1.0/cctv $/Xml/Schemas1.0/cctv/deprecated $/Xml/Schemas1.0/cctv/messages $/Xml/Schemas1.0/cctv/objects $/Xml/Schemas1.0/cctv/requests $/Xml/Schemas1.0/cctv/responses $/Xml/Schemas1.0/common $/Xml/Schemas1.0/common/messages


SunGuide-CMP-1.0.1

$/Xml/Schemas1.0/common/objects $/Xml/Schemas1.0/common/requests $/Xml/Schemas1.0/common/responses $/Xml/Schemas1.0/dataBus $/Xml/Schemas1.0/dataBus/messages $/Xml/Schemas1.0/dataBus/objects $/Xml/Schemas1.0/dataBus/requests $/Xml/Schemas1.0/dataBus/responses $/Xml/Schemas1.0/dms $/Xml/Schemas1.0/dms/objects $/Xml/Schemas1.0/dms/requests $/Xml/Schemas1.0/dms/responses $/Xml/Schemas1.0/har $/Xml/Schemas1.0/har/objects $/Xml/Schemas1.0/har/requests $/Xml/Schemas1.0/har/responses $/Xml/Schemas1.0/incident $/Xml/Schemas1.0/incident/objects $/Xml/Schemas1.0/incident/requests $/Xml/Schemas1.0/incident/responses $/Xml/Schemas1.0/incident_swri $/Xml/Schemas1.0/incident_swri/objects $/Xml/Schemas1.0/incident_swri/objects/Data $/Xml/Schemas1.0/incident_swri/requests $/Xml/Schemas1.0/incident_swri/responses $/Xml/Schemas1.0/tss $/Xml/Schemas1.0/tss/messages $/Xml/Schemas1.0/tss/objects $/Xml/Schemas1.0/tss/requests $/Xml/Schemas1.0/tss/responses