s You are here: Home > Support > Configuration management > Develop CM plan
UMP slogan Home | About UMP | FAQ | Discuss | Contacts | Site map
  Life cycle model   Development process   Support process   Organizational process   Product    
Documentation | Configuration management | Quality assurance | Verification | Validation | Problem resolution




Configuration management activities:

6.2.1&6.2.2: Develop CM plan
6.2.3&6.2.3&6.2.4: Control configuration

 

 

 

 

References:

UMP glossary
Bibliography
Conventions & Notation

Activity 6.2.1&6.2.2: Develop configuration management plan (CMP)

UMP
  Support Process

         Configuration management process
next task >>

 

Task goals

To develop configuration management plan, which should assure that the configuration process is optimized and adapted for both given target software product and the given development team.

The Configuration Management Plan (CMP) should describe project specifics, which are not covered by the chosen life cycle model and the Product Business Specification (PBS). In this sense the CMP should be developed as a supplement to the model and PBS.

The CMP should be based on the team knowledge, experience and culture to grant ease of following the CMP to each team member.

The CMP shall be developed and treated as an agreement by the team members.

Procedure
  1. Configuration Manager: Develops the CMP.
  2. Configuration Manager: Makes the CMP available to the project participants.
  3. Project Manager and Developers: Conduct Technical Review of the CMP. The goal is to have the CMP cleared with, and confirmed by, the developers.
  4. Project Manager: If necessary, agrees with the project participants, others than developers, on CMP.
  5. Configuration Manager: Publishes the corrected and approved CMP.
  6. Developers: Follow the CMP spirit, philosophy and directions.
  7. Participants: Propose changes.
Inputs Programming artifacts None
Model Project life cycle model
Documents Software Development Plan (SDP)
Checklists None
Guides Configuration management guide
Outputs Programming artifacts None
Model None
Documents Software configuration management plan
Checklists None
Completion criteria  
Quality metrics  
Milestones  
Task improvement opportunity events  

 

 

Last modified: 07-Jan-2005
Copyright © 2003—2005 Alexander Kozlinski. All rights reserved.
Use of this website signifies your agreement to the Terms of Use