CM 3: Change Management (Configuration Control)



		CM 3: Change Management (Configuration Control)

KM3 - Änderungsmanagement (Konfigurationssteuerung)

Contents
Product Flow
Handling
Recommendation
Explanation

Roles
Sub-activities
Tools Requirements
External Norms

Contents		Product Flow Handling Recommendation Explanation		Roles Sub-activities Tools Requirements External Norms

Product Flow

From		Product		to		Methods	Tool Req.	Ext. Norms
Activity	State	Chapter	Title	Activity	State	Methods	Tool Req.	Ext. Norms
CM1	accepted	All	CM Plan	-	-			/ISO IEC 12207/ Acquis. Proc.: Contract Prep. and Upd., Operation. Proc.: Proc. Implem., Maintenance. Proc.: Proc. Implemen. Doc. Proc.: Maintenance, CM Proc.: Config. Control
External ⁽¹⁾	-	All	Change Request/Problem Report	-	-
External ⁽²⁾	-	All	Final Project Report	-	-
-	-	All	Change Status List	CM4	-
-	-	All	Change Order	for submodel in question	-
-	-	All	Change Memo	CM4, External ⁽¹⁾	-
-	-	All	Protocol	CM4 External ⁽¹⁾	-

+ "Chapter" are extra columns from the original printed version of GD 250

Handling

Figure 6.5: CM3 - Change Management (Configuration Control)

Following activities are combined in the change management:

Registration and administration of incoming error reports, trouble reports, and improvement proposals as Change Request/Problem Reports.

Decision about the processing of Change Requests/Problem Reports (rejection/approval; selection of a solution proposal) by taking into account technical and deadline impacts on the course of the project, and initialization of processing.

Completion of the change and informing all people concerned.

Depending on the progress of development and on decisions made, a change has a certain status:

Figure 6.6: Status of a Change

These are typical change statuses. Based on project-specific conditions and the change procedures used it is also possible to make deviating definitions.

SD, QA, CM and PM roles participate in the change management. The actual involvement of these roles depends on the product(s) to be changed.

Only those products are subject to the CM 3 "Change Management (Configuration Control)" activity that already have reached the state "accepted". These products may also be part of a baseline.

Recommendation

When determining the change procedure it should be distinguished whether a product is already delivered to the customer, or not. Before product delivery, a shorter change procedure may be chosen.

Explanation

A change may concern results of different submodels like

Requirements documents, designs, implementation documents, etc. (submodel SD)
Project Manual, Project Plan, etc. (submodel PM)
Assessment Specification, Assessment Plan, etc. (submodel QA)
Configuration Identification Document (CID) (submodel CM)

Roles

Role	Participation
CM Administrator	cooperating (CM3.1, CM3.2, CM3.3)
CM Representative	cooperating (CM3.1, CM3.2, CM3.3)
Project Leader	responsible (CM3.1, CM3.2)

Sub-activities

CM3.1 - Change Evaluation,
CM3.2 - Decision about Change Procedures and Initiation of Change,
CM3.3 - Completion of Change.

Tools Requirements

Being defined

External Norms

Norm	Process	Chapter	Obs.
/ISO IEC 12207/	Acquisition Process	Contract Preparation and Update	(s. Part 3 - ISO 3.2.1)
	Operation Process	Process Implementation	(s. Part 3 - ISO 3.2.1)
	Maintenance Process	Process Implementation	(s. Part 3 - ISO 3.2.1)
	Documentation Process	Maintenance	(s. Part 3 - ISO 3.2.2)
	Configuration Management Process	Configuration Control	(s. Part 3 - ISO 3.2.2)

Notes:

(1) project member, customer, user

(2) All those Report Documents/Final Project Reports must be considered that were generated during the modification tasks according to the V-Model.

GDPA Online Last Updated 01.Jan.2002 Updated by Webmaster Last Revised 01.Jan.2002 Revised by Webmaster