Configuration
Management is about defining configuration items. Configuration items is a wellknown
term for DOD clients but is not so well known outside of that arena. We
use the following example. When a software system is being designed, it can be broken
up into several pieces. Those pieces may be the files, the data elements within
those files, programs, reports, and integrated or called modules. Those pieces can be
termed configuration items. An organization can have both high-level configuration
items and then lower-level configuration items that result from decomposing the
high-level items into lower-level, more detailed, smaller pieces. Each piece (or con-
figuration item) is assigned a label and a number to aid in tracking that all pieces
of the desired system are included as part of the delivered product. It also helps in
tracking changes, planning the effort, and auditing functionality satisfied.
Configuration Management is also about establishing baselines. Baselines are
basically where you draw a line in the sand and say, ???OK, anything developed past
this point, or any changes made past this point, must go through some sort of
offi cial review before being incorporated into the rest of the system.
Pages:
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208