24.2 Configuration Management ProcessesOverview

This section contains lists of the processes needed for each configuration management activity. The lists here are "flat," whereas in a live project, the processes may be multidimensional: variations may exist, depending on the nature of the project and the configuration management. All the contents of the processesprocedures, conventions, and templatesare listed separately here, but they may well be combined.

Identification requires

  • Procedure(s) for registration of metadata, including procedure(s) for tracing

  • Procedure(s) for inheritance of metadata

  • Convention(s) for unique identification

  • Convention(s) for authorization, including restrictions on distribution, if any

  • Convention(s) for identification of components in a delivery

Storage requires

  • Procedure(s) for placement in storage and the related updating of metadata

  • Procedure(s) for release for usage

  • Procedure(s) for release to production

  • Template(s) for item approval

  • Template(s) for release request

Change control requires

  • Description of the change control process structure

  • Procedures in life cycles for events and changes

  • Convention(s) for forming different types of configuration control boards

  • Definition of the responsibility for each type of configuration control board

  • Template(s) for event registration

  • Template(s) for change request

Status reporting requires

  • Procedure(s) for producing status reports

  • Procedure(s) for ad hoc extracting of information

  • Templates for status reports the configuration management system should be able to produce

Special Requirements for Configuration Management Processes

The fact that configuration management is performed during the entire lifetime of a product, for a number of different types of items, and under various circumstances imposes certain requirements on process descriptions. On one hand, they must be integrated with process descriptions for all other processes for which configuration management is performed. These may be coding, test, project management, and quality assurance, to mention a few. Special product requirements may also have to be taken into consideration, as well as special conditions that apply to a project. This could be integrated product development, multivariants , or product-line development of items for reuse.

On the other hand, variants of some process descriptions may be necessary, depending on the types of configuration items and/or degree of formalism required. Types of configuration items may be source code or plans, to mention just two. More comprehensive lists of both types can be found elsewhere in this book.



Configuration Management Principles and Practice
Configuration Management Principles and Practice
ISBN: 0321117662
EAN: 2147483647
Year: 2002
Pages: 181

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net