|CM 2.4: Configuration Update|
|From||Product||to||Methods||Tool Req.||Ext. Norms|
|CM2.2||being proc.||Existing||Configuration Identification Document (CID)||CM4.3,
|being proc. (2) /
+ "Chapter" are extra columns from the original printed version of GD 250CID initialized in activity CM2.2 - Configuration Initialization is updated/completed with the new product. Within the corresponding CID (System CID, HW CID, or SW CID), it is differentiated between the products "documents" (all development documents) and "items" (all units, from the SW Module/HW Module to the System).
It must be guaranteed with the help of the CID that a configuration unit can be configured or reconfigured out of its items at any time. To do so procedures must be maintained-apart from the complete listing of all items belonging to a configuration unit-that automate the required configuration measures. It must be possible to recognize all relationships and dependences among the individual products from the CID. The possibility or necessity of different configuration variants must also be taken into consideration accordingly.
The CID remains in the state "b. proc." until the corresponding configuration unit (System, SW Unit, HW Unit)(3) reaches the state "submitted". Only then does the corresponding CID also reach the state "submitted".
If a Configuration Identification Document (CID) is in the state "submitted"/"accepted" then the modification of a product in this configuration implies a modification of the version identification of the configuration.
|Product||Functional Tools Requirements|
|Configuration Identification Document (CID)||SCM01 - Supporting Configuration Planning and Control|
(2) "submitted", if the corresponding product has reached state "submitted"
(3) or according to project definition.
|GDPA Online Last Updated 01.Jan.2002 Updated by Webmaster Last Revised 01.Jan.2002 Revised by Webmaster|