Code Manual for CONTAIN 2.0 - Federation of American Scientists

When the review is complete, the update is delivered to the revision manager. The revision manager
inspects the package to check for completeness, accuracy, and adherence to project standards. The
manager creates the source code from the update and compiles this source code to check for compile
errors and warning messages. The manager or an internal beta tester runs the test problems used by
the developer and checks the results qualitatively for error messages, code bombs, etc. The manager
inspects the documentation to ensure that it contains all mandatory sections, such as descriptions of
testing and new input, and that upward compatibility has been maintained.
When the revision manager is satisfied with the update and documentation, the manager signifies
acceptance by signing the Change Document cover sheet. A sample copy of the Change Document
cover sheet is shown in Figure D-4. This signoff constitutes a process called “freezing.” Once the
update is frozen, it can no longer be modified. Any further modifications or emor corrections must
be addressed in a subsequent update.
D.2.5 Configuration Control
The CONTAIN quality assurance program includes a strictly enforced configuration control
component. The objective of this component is to ensure that whenever users or developers access
the CONTAIN code, they are presented with a complete, consistent, and tested code.
D.2.5. 1 Baseline Co ntrol. CONTAIN configuration control employs a baseline system to ensure
consistency and to control context. A baseline consists of a set of updates that are used without
modification and that can be changed only under strictly controlled procedures. CONTAIN
configuration control enforces two baselines: operational and developmental. The operational
baseline is the software released to the user community as a “version” or “revision.” A version
embodies major changes and entails the publication of a new edition of the Code Manual. A revision
consists of less significant, but often still substantial, changes and includes the distribution of change
documents to the most recent version of the Code Manual. The developmental baseline, derived
from the operational baseline, provides a controlled environment for development and testing. The
same mechanism is used to control both baselines, but control is exercised over each baseline
independently.
D.2.5.2 The Co ntrol Mechan ism. Prior to CONTAIN 1.2, the UPDATE utility was used to enforce
baseline control. UPDATE is a CW4Y utility designed to facilitate the maintenance of a large code
project by managing and tracking software changes. [UPD84] It is a line-oriented text editor that
creates and maintains program libraries (data sets) and other data on the basis of line and deck
identifiers. A library can be modified by adding or purging decks, or by adding, modifying, or
deleting cards in existing decks. UPDATE can be used to generate new program libraries, source
data sets (with UPDATE directives embedded), compile data sets (ready for compilation), or
selected listings. Duplicated code can be defined once and referenced for inclusion in other decks.
Options in UPDATE ensure correct line numbers by assigning new sequence numbers using the
UPDATE 4.0 scheme. UPDATE produces output that can be used as input to other programs,
particularly compilers and assemblers. Although there are many alternative ways of enforcing
baseline control, UPDATE was chosen for CONTAIN because it
Rev O D-9 6/30/97