Course Registration System
Configuration Management Plan
Version 2.0
Revision History
Date |
Version |
Description |
Author |
---|---|---|---|
08/Jan/1999 |
1.0 |
Initial Release |
Simon Jones |
10/Feb/1999 |
2.0 |
Extending plan |
Simon Jones |
|
|
|
|
|
|
|
|
Table of Contents
1.3 Definitions, Acronyms, and Abbreviations
2. Software Configuration Management
2.1 Organization, Responsibilities, and Interfaces
2.2 Tools, Environment, and Infrastructure
3. The Configuration Management Program
3.1 Configuration Identification
3.2 Configuration and Change Control
3.2.1 Change Request Processing and Approval
3.2.2 Change Control Board (CCB)
3.3 Configuration Status Accounting
3.3.1 Project Media Storage and Release Process
6. Subcontractor and Vendor Software Control
Configuration Management
Plan
The purpose of this document is to define the Configuration Management procedures to be followed by the Course Registration System project..
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.
Refer to the Glossary [1].
Applicable references are:
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.
See the Software Development Plan.
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.
See Wiley College CM Plan.
Baselines are created at the end of each iteration, as described in the Software Development Plan.
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.
There is no CCB, per Wiley College CM Plan.
See Wiley College CM Plan.
See Wylie College Measurement Plan.
See the C-Reg Software Development Plan.
All team members are fully trained.
C-Reg System has no subcontractors. See Wiley College CM Plan for guidelines for managing COTS products used in the product.