Chapter 16. Configuration Management in Development Activities

In many companies, coding is closely connected with module test. Also, integration, integration test, and system test are performed in a way that can make it difficult to keep them clearly apart. This makes good sense, as in the end it is all a matter of the delivery of complete and tested systems.

Configuration management, however, distinguishes between coding, integration, and test. Coding produces code, which is integrated into systems to be delivered. Integration produces assembled (sub)systems for delivery. Testing produces test- related items, which do not necessarily have to be delivered. Therefore, this chapter distinguishes between these activities, with each one treated in a section below. (Although test levels and types may be categorized in many ways, from the point of view of configuration management these differences are not significant; therefore, all test levels and types are treated as one in the section on testing). Each activity requires the capability for unique identification, authorization, tracing, storage, change control, and status reporting, although these are not repeated in each case except where they merit special mention.