8.4.2 Configuration Identification Document



		8.4.2 Configuration Identification Document (CID)

Konfigurations-Identifikationsdokument (KID)

Contents
Introduction
Document Index
Document Structure
Links to the V-Model Mailinglist

Contents		Introduction Document Index Document Structure Links to the V-Model Mailinglist

Introduction

The Configuration Identification Document reflects the configurations of the hierarchical levels System (System CID) and SW Unit (SW CID) or HW Unit (HW CID).

The System CID lists Segments, HW Units and SW Units (including a reference to their CIDs), and documents on the System level. The SW CID contains SW Components, SW Modules and Databases of the SW Unit as well as the corresponding documents. The HW CID lists HW Components and HW Modules of the HW Unit as well as the corresponding documents. General Products are added to each corresponding object of the contract.

It is possible, to combine several Configuration Identification Documents into one document.

Document Index

1. General Information
2. Identification
3. Items
4. Documentation

Document Structure

1. General Information

See schema 1. General Information.

2. Identification

The identification of the configuration object will be given together with possible configuration attributes (e. g. laboratory version, test version, series), the characteristics of the configuration must be listed, and it is necessary to refer to a higher-level System CID or to lower-level SW CIDs and HW CIDs. Apart from this the following information will be listed:

version/number of the configuration
project identification
CM representative
status of the configuration
date of the last configuration modification.

Just as for the architecture documents (System Architecture, HW Architecture and SW Architecture), separate CIDs are required on the two levels "System" and "Software" or "Hardware". Since at least one CID has to be allocated to a delivery unit, project-specific peculiarities, such as delivery of individual or configured software or hardware components as one delivery unit, may require further CID levels. Definition and number of CIDs in the project, and therefore the interpretation of a "configuration unit" as well, depend on these project decisions, i. e. it is the responsibility of the configuration management to define further CIDs and thus further configuration units, or not.

3. Items

The elements required for the configuration are identified on the basis of their unique ID and their version. For a System CID, these are: Segments, SW Units, and HW Units; for a SW CID: SW Components, SW Modules, and Databases; for a HW CID: HW Components and HW Modules. Exact instructions for the configuration or an automated procedure have also to be documented.

The relationships between the individual items (internal relationships within the configuration) have to be documented. In order to automate generations, redundant and copied product parts, interfaces and hierarchical relationships between items have to be documented as well.

4. Documentation

All documents belonging to the configuration and its component parts (requirements, architecture, design, assessment documents, etc.) will be listed.

Links to the V-Model Mailinglist

Mail 0610 - Konfigurations-Identifikationsdokumente (610)

This page online • GDPA Online • Last Updated 05.Nov.2002 by C. Freericks