If you don’t define and manage what you’re going to
change, how do you know if the change has been successful?
The primary objective of Configuration Management (CM) is to maintain
the integrity of products throughout the project life cycle. CTA’s
developers are experts at large enterprise development; they have
the maturity and experience to address not only the project itself,
but how the change affects the entire enterprise.
CM is defined as a process of identifying a standard set of criteria
or a baseline, facilitating organized controlled change to that
baseline, and monitoring that baseline for both authorized and
unauthorized change. CM processes play a key role in the management
of individual products and the entire enterprise. Effective use
of a documented and repeatable configuration management process
helps to ensure successful achievement of program goals.
CTA has adopted a CM methodology that addresses the requirements
of a large enterprise. In a large enterprise CM must be implemented
in a hierarchical manner. Each level has a span of authority
which yields a balance of control over all levels of CM in the
entire enterprise. Those change requests that affect elements
over which a Configuration Control Board (CCB) at a certain level
is not authorized, are relegated to the next level to adjudicate. The
results of this pass up are returned to the original CCB for final
implementation. CTA’s proven methodology has been successful
with multiple clients and multiple large scale contracts.
Each CM element is addressed by CTA in a tailored manner, dependent
upon the requirements of the particular client or contract. CM
consists of the following elements:
-
Identification
-
Change Control
-
Configuration Audits
-
Status Accounting
|
