| 0.1 | Original Submission | 3 March 1997 |
| 0.2 | Developer Edit | 8 March 1997 |
1.0 Overview 4
2.0 Objectives 4
3.0 Scope 4
3.1 Controlled Items 4
3.2 CM Activities 5
4.0 Roles and Responsibilities
5
4.1 Configuration Manager 5
4.2 Development 5
4.3 Project Document Authors 5
5.0 Processes and Procedures 6
5.1 Baselining Project Documents 6
5.2 Baseline Repository 6
5.3 Access to Baselined Documents 6
5.4 Snap Shots of WWW Site 6
5.5 Verification of WWW Site 6
6.0 Schedule 6
This plan documents the Configuration Management (CM) activities that will be used by the MJY Team during the implementation of the SOFTWARE RISK MANAGEMENT WWW SITE. This plan defines what will be put under configuration management control, who will be involved in the configuration management process, what procedures are to be used, and what timeline has been planned for these activities.
Identify items to be placed under CM control and the scope of CM activity on this project. (3.0)
Identify the roles and responsibilities of those involved in the configuration management process. (4.0)
Describe the processes and procedures to be used in configuration management of this project. (5.0)
Identify the planned schedule for configuration management activities on this project. (6.0)
Configuration management will be used on this project to maintain a repository of version controlled project documents. The following documents are subject to CM control:
CM will work with Development to:
CM will work with the Program Manager to provide the correct version of all final deliverables to the client.
The Configuration Manager is responsible for maintaining the project documents repository, working with Development to baseline the WWW Site as scheduled, verifying versions on the WWW Site for QA testing, providing QA tested versions for final delivery.
Development will ensure proper version control while implementing the WWW Site by using SCCS version control tool during development. Development will work with CM to ensure that the proper baselined version of the WWW Site and all documents are available prior to QA testing and final delivery of WWW Site.
Authors of project documents listed in section 3.1 are responsible for providing CM with either a soft copy, or both hard and soft copies of their project document to be baselined.
A project document is baselined once it is delivered to CM. A soft format, or both hard and soft format of the document must be delivered. To rebaseline a project document the above process is to be followed with the addition of a modification description to explain or justify the need for rebaselining.
CM will place all baselined material in off line storage.
Working drafts of all documents are kept on the MJY WWW Site. In addition any member of the MJY Team, or customer can request copies of baselined documents by emailing a request to CM. Copies will be sent by return email in MS Word format.
Development will provide CM a disk with latest software from SCCS as scheduled, an initial version and then prior to PDR, CDR, and final delivery.
CM will work with Development to audit the WWW Site as scheduled to verify the versions of each project document and software file matches the baseline.
2/10/97 Baseline Risk Mitigation Plan
2/17/97 Baseline Software Requirements Specification
2/17/97 Baseline Requirement Management Process Document
2/24/97 Baseline Draft Project Management Plan
2/24/97 Initial baseline of software
3/03/97 Deliver Draft Configuration Plan
3/17/97 Baseline software prior to PDR
3/24/97 Ensure baselines for PDR
3/24/97 Baseline Configuration Plan
3/24/97 QA/Test Plan
3/31/97 Baseline software prior to CDR
4/07/97 Ensure baselines for CDR
4/13/97 Baseline software for final delivery
4/28/97 Baseline QA Test Report
4/28/97 Ensure baselines for final delivery