ABSTRACT

In an ideal world, the operational, functional, and module specifications are placed under configuration control in the same manner as the source code itself. These documents can be viewed as source code in exactly the same manner as the source code program. They would be stored in a file system or database managed by SCCS or RCS in the same manner as for source code to maintain the various versions of each of the specification elements. These specifications constitute a document in exactly the same manner as the source code itself. As the various specifications evolve, they must be tracked and managed in precisely the same manner as the source code. Some specification elements will come and go. The code representing these eliminated versions will also come and go. As the source code base changes, it is extremely important to know how the version of each requirement element is represented by the code base.