Unformatted text preview: The techniques of configuration management
include configuration (or baseline) identification,
configura- NASA Systems Engineering Handbook
Management Issues in Systems Engineering tion control, configuration verification, and configuration
accounting (see Figure 18). •
identification of a baseline is accomplished by creating
and formally releasing documentation that describes the
baseline to be used, and how changes to that baseline
will be accounted for, controlled, and released. Such
documentation includes requirements (product, process,
and material), specifications, drawings, and code
listings. Configuration documentation is not formally
considered part of the technical baseline until approved
by control gate action of the buyer.
An important part of configuration identification
is the physical identification of individual configuration
items using part numbers, serial numbers, lot numbers,
version numbers, document control numbers, etc. •
• What is the design impact?
What is the effectiveness or performance
What is the schedule impact?
What is the program/project life -cycle cost
What is the impact of not making the change?
What is the risk of making the change?
What is the impact on operations?
What is the impact to support equipment and
What is the impact on spares requirements?
What is the effectivity of the change?
What documentation is affected by the change?
Is the buyer supportive of the change?
Configuration Control Board Conduct Configuration Control. Configuration control is the
process of controlling changes to any approved baseline
by formal action of a configuration control board (CCB).
This area of configuration management is usually the
most visible to the system engineer. In large
programs/projects, configuration control is accomplished
by a hierarchy of configuration control boards, reflecting
multiple levels of control. Each configuration control
board has its own areas of control and responsibilities,
View Full Document