Course Registration System

Configuration Management Plan

Version 2.0

Revision History

Table of Contents

1.Introduction         

1.1Purpose     

1.2Scope     

1.3Definitions, Acronyms, and Abbreviations     

1.4References     

1.5Overview     

2.Software Configuration Management

2.1Organization, Responsibilities, and Interfaces     

2.2Tools, Environment, and Infrastructure     

3.The Configuration Management Program         

3.1Configuration Identification     

3.1.1Identification Methods           

3.1.2Project Baselines           

3.2Configuration and Change Control     

3.2.1Change Request Processing and Approval           

3.2.2Change Control Board (CCB)           

3.3Configuration Status Accounting     

3.3.1Project Media Storage and Release Process           

3.3.2Reports and Audits           

4.Milestones

5.Training and Resources     

6.Subcontractor and Vendor Software Control

Configuration Management Plan

1.                  Introduction

1.1               Purpose

The purpose of this document is to define the Configuration Management procedures to be followed by the Course Registration System project..

1.2               Scope

The Course Registration System follows the Wylie College Configuration Management Plan, which applies to all Wylie College projects.  In addition, this document defines additional procedures, project milestones, etc. that apply specifically to the Course Registration System project, and not necessarily to other projects at Wylie College.

1.3               Definitions, Acronyms, and Abbreviations

Refer to the Glossary [1].

1.4               References

Applicable references are:

1. Course Registration System Glossary , WyIT406, V1.0, 1998, Wylie College IT.
2. Course Registration System Software Development Plan, WyIT418, V1.0, 1998, Wylie College IT.
3. Wylie College Configuration Management Plan, WyIT420, V1.0, 1999, Wylie College IT.

1.5               Overview

The Course Registration System project follows the Wylie College Configuration Management Plan.  This plan contains project specific CM plan information, primarily by reference to other project plans.

2.                  Software Configuration Management

2.1               Organization, Responsibilities, and Interfaces

See the Software Development Plan.

2.2               Tools, Environment, and Infrastructure

Tools and environment are as specified in the Wylie College Configuration Management Plan.  

The project uses the Creg UCM Project, which is part of the Wylie College PVOB.

We currently use a single VOB, named CRegMain for storing Configuration Items.

We follow the Wylie College standard product directory structure.

We expect that there will be at most 2000 project files, requiring roughly 100M of disk space.

Simon Goodman is the Configuration Manager, and is responsible for setting up the CM environments.

3.                  The Configuration Management Program

3.1               Configuration Identification

3.1.1          Identification Methods

See Wiley College CM Plan.

3.1.2          Project Baselines

Baselines are created at the end of each iteration, as described in the Software Development Plan.

3.2               Configuration and Change Control

3.2.1          Change Request Processing and Approval

See Wiley College CM Plan.

The Configuration Control Manager and Project Manager roles of assigning work and reviewing/approving changes are performed by the lead of each team (see the organization chart in the Software Development Plan), who may delegate this responsibility as he/she deems appropriate.

3.2.2          Change Control Board (CCB)

There is no CCB, per Wiley College CM Plan.

3.3               Configuration Status Accounting

3.3.1          Project Media Storage and Release Process

See Wiley College CM Plan.

3.3.2          Reports and Audits

See Wylie College Measurement Plan.

4.                  Milestones

See the C-Reg Software Development Plan.

5.                  Training and Resources

All team members are fully trained.

6.                  Subcontractor and Vendor Software Control