Previous Next V-Model Official Homepage by IABG  
6 Regulations Submodel Configuration Management  

  6 Regelungen Submodell Konfigurationsmanagement

  • 6.1 Overview
  • 6.2 The Activities of Submodel CM
  • 6.1 Overview

    The goal of configuration management (CM) is to guarantee that a product can be uniquely identified with regard to its functional and representational characteristics, e. g. as is the case with documents, at any time. This identification serves to control modifications and to guarantee integrity, even during application.

    The configuration management supervises the configurations so the relationships and the differences between previous configurations and the current configurations can be recognized at any time. CM guarantees that it will be possible at any time to access previous versions. This way, modifications can be easily reconstructed and checked.

    Activity CM1 - CM Planning definitely specifies the regulations and procedures for the project and creates the basis for a reliable configuration management. Activity CM2 - Product and Configuration Management makes sure that products and configurations are uniquely identified, their accesses will be protected, and that they are stored in a reconstructable way. Activity CM3 - Change Management (Configuration Control) supervises the entire change process, starting with the change request and all decisions up to the change conclusion as well as the acknowledgment. CM Services (activity CM4 - CM Services) are realized in certain intervals or when required. This includes the backup of results and the CM documentation as well as the CM services for the central and for the general data administration, the reuse of the product, the interface coordination and the release management.

    The activities described below are valid for the development process as well as for the use of the system.

    With regard to the treatment of products in the V-Model, it must be considered that products go through different maturing degrees, i. e. states, during the development process. The various product states-required at the very least-are defined in section 2.3.2. Product States.

    The change from one state to another is triggered by an activity only. The state transitions are mentioned in the corresponding activities. The state transition usually goes along with changing access rights. The responsibility for changing the state has to be uniquely defined.

    Figure 6.1: Valid State Transitions of Products to be developed shows the minimally required state transitions and the activity triggering the state change for products to be developed. In the case of off-the-shelf products the state "b. proc." is merged with state "planned".

    Figure 6.1
    Figure 6.1: Valid State Transitions of Products to be developed

    6.2 The Activities of Submodel CM

    CM1 - CM Planning ,
    CM2 - Product and Configuration Management
    CM3 - Change Management (Configuration Control)
    CM4 - CM Services

    Figure 6.2
    (daVinci Graph Visualization Tool v2.0)

    Figure 6.2: Overview of Functions in Submodel CM

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