TABLE OF CONTENTS Configuration Management can be defined as:
A supporting process whose purpose is to identify, define, and baseline items; control modifications and releases of these items; report and record status of the items and modification requests; ensure completeness, consistency and correctness of the items; and control storage, handling and delivery of the items
The International Organization for Standardization
CM prevents unapproved changes that could result in costly problems: it attempts to maintain complete compatibility between all parts of a system when one part is added, changed, or deleted. Critical parts are deemed to be Configuration Item(s) and require a Configuration Management effort to track them. A Configuration Control Board (CCB) monitors all proposed changes. The CCB consists of an interdisciplinary team to avoid unanticipated impacts in other areas of ILS. CM must permit changes in design and development, but control changes later in the life cycle.
Selects Configuration Items and documents their approved technical characteristics to provide a baseline for change control, status accounting, and auditing. These include:
Allocated Baseline (defines functional requirements and configuration interfaces)
Functional Baseline (defines top-level performance and system interfaces)
Product Baseline (defines exact and detailed design)
Identification numbers and Nomenclatures
This is the process of assessing impacts, approving or disapproving proposed changes, and implementing approved changes to configuration baselines. It corrects deficiencies, reduces Life Cycle Costs (LCC), satisfies requirement changes, and responds to program changes. Configuration Control provides coordination with affected users and...
