Previous Next V-Model Official Homepage by IABG  
Part 3: Collection of Manuals Homepage  
Tailoring Homepage  
T.4.3.3 Submodel CM  

  T.4.3.3 Submodell KM

BT TT Activity Reason for Deletion Effects
- CM1 - CM Planning
  • This is a small project and the project leader is in charge of the generation of CM regulations and filing.
    		• CM regulations have to be included in products Project Manual or Project Plan.
  • The organizational frame (CM Plan and CM infrastructure) is specified (e. g. in a SWMM project).
  • The CM regulations are specified by the organization.

    • Product CM Plan comes from "outside".
    CM1.1 - Generation the CM Plan
  • The CM Plan may be adopted from similar project (i. e. same characteristics).
    		• Product CM Plan comes from "outside".
    CM1.2 - Setting up CM
  • CM infrastructure and CM organization are available as required in the Project Plan and the CM Plan and may be used.
    		• -
    - - CM2 - Product and Configuration Management   
    CM2.1 - Product Initialization
  • Reduced CM management; initialization not required.
    		•  -
    - CM2.2 - Configuration Initialization
  • The assessed unit already exists in a first version. The Configuration Identification Document (CID) of the unit must only be updated (see activity CM2.4 - Configuration Update).
    		• -
    - - CM2.3 - Product Management   
    - - CM2.4 - Configuration Update   
    CM2.5 - Administration of Access Rights
  • This is a project where each project member has the right to access and change all products administrated by CM.
    		• This regulation must be included in the CM Plan.
    CM3 - Change Management (Configuration Control)
  • Planning, control and supervision of the tasks are not formally handled and realized by the Project Leader.
    		• Products Change Proposal, Change Order, Change Memo are deleted. The change status list has to be maintained in the Project Plan.
    CM3.1 - Change Evaluation
  • The change only refers to a product under development. Planning, control and supervision of all tasks are realized by the Project Leader.
    		• Product Change Proposal is omitted.
    CM3.2 - Decision about Change Procedures and Initiation of Change
  • The change refers to a project under development. Planning, control and supervision of the tasks are realized by the Project Manager.
    		• Products Change Proposal, Change Order, Change Memo are omitted.
    CM3.3 - Completion of Change
  • The change is realized during development (contractor, internally). The handling has already been defined in the detailed planning or has been documented in the Project History.
    		• -
    - CM4 - CM Services
  • The CM services are realized for all projects.
    		•  -
    - CM4.1 - Data Administration
  • There is no generally applicable data dictionary.
    		• -
    CM4.2 - Cataloging of SW/HW Products
  • Only documents (i. e. no SW Module, Database, SW Component, SW Unit, Segment or System) are generated in the product.
    		• -
    CM4.3 - Interface Coordination
  • The System to be developed has no complex interfaces.
    		• -
    CM4.4 - Data Backup
  • There is a central organization in charge of saving the data (at regular intervals and after being instructed).
  • The data backup takes place in regular intervals, either automatically with the CM tool or the project library.
    		•  -
    CM4.5 - Update of CM Documentation
  • CM documentation is not required.
    		• CM documentation is omitted.
    CM4.6 - Release Management
  • There is no set of units that is updated in configurations.
    		•  -
    CM4.7 - Recording Project History
  • It is a small project without identifiable development risks.
    		•  Product Project History is omitted. The essential decisions in the project must be documented in reporting documents.

    Table T.26: Deletion of Activities for Submodel CM

    Previous Next This page online  •  GDPA Online  •  Last Updated 03.Mar.2004 by C. Freericks