Description / Abstract:
GENERAL
There are two aspects of configuration identification that must
be considered, First , is the identification of the computer
program, a s described by technical data/documentation during its
life cycle. Second, is the associated identification of the
computer program by means of a tag, usually its name (mnemonic),
and/or a unique number and other selective identification
characteristic $ which correlate the specific code t o its
documentation and enable trace ability back to the development
requirements. The first aspect of this identification is an
evolutionary process, which occurs over the life cycle of the
computer program, while the second is usually accomplished by
selecting and applying a scheme which ensures that each element is
identified with its own unique identifier .
Contractors use such technical data/documentation to manage the
development of computer programs on a day-to-day basis. '
Configuration management planning is based upon the establishment
of reference points for specific milestones during a configuration
item's life cycle, At these milestones, a "snapshot" of the data
required for program management is made. The snapshot data are
designated a s configuration documentation (technical descriptions)
while the milestone is designated a baseline.