Real Time software configuration control continues to be a problem area despite many guidelines, procedures, and regulations. Software traceability is particularly frustrating throughout the development phase. This paper will describe a "common sense" approach to software configuration management and a process of software migration during product development. The concept is independent of languages, compilers, and machine implementation.

First, a general classification scheme is developed, and controlling mechanisms are discussed. Second, the author defines a software development and migration process. This discussion will include software engineering development, test and integration, and operational and baseline areas. Next, this "common sense" approach will be related to MIL-STD 2167A. And last, an implementation of the "common sense" approach with lessons learned is presented.

While details of implementation must be developed for a specific configuration, the concept provides for traceability and controlled development with few constraints on the individual software engineer, a logical migration of software to a deliverable product, and a high degree of confidence in having "what you think you have."