 |
 |
 |
|
 |
|||
| CM 4.6: Release Management |
KM4.6 - Release-Management durchführen
 Contents
|
|
|
|---|
Product Flow
| From | Product | to | Methods | Tool Req. | Ext. Norms | |||
|---|---|---|---|---|---|---|---|---|
| Activity | State | Chapter | Title | Activity | State | |||
| CM2 | being proc./ accepted |
All | Configuration Identification Document (CID) | - | - | |||
+ "Chapter" are extra columns from the original printed version of GD 250
Further Results:
* "Configuration unit"/"product to be delivered"
Handling
Activity CM 4.6 "Release Management" has the task of configuring or reconfiguring configuration units according to certain criteria/options and/or to prepare products for delivery. If necessary, the creation of a data medium has to be described (release procedure for the generation of a data medium). An installation procedure is required accordingly. Here activity CM 4.6 "Release Management" acts as the central and only delivery instance that prevents that, e. g., uncoordinated changes are integrated into a product to be delivered or that configuration parameters are set incorrectly.
Explanation
This activity maintains the control of all deliveries. Typical questions are: which configuration variants have been delivered, when and to whom, via which memory or transmission medium, and why was the delivery made.
Roles
| Role | Participation | ||||||
|---|---|---|---|---|---|---|---|
| Project Leader | cooperating
| CM Representative |
responsible
| CM Administrator |
cooperating
| System Administrator |
cooperating
| |
Tools Requirements
Being defined
External Norms
Being defined
|
|
|
GDPA Online
Last Updated 01.Jan.2002
Updated by Webmaster
Last Revised 01.Jan.2002
Revised by Webmaster
|