This guide is to provide guidance for OGCIO staff to plan and implement Software Configuration Management
(SCM) in development and maintenance stages of application software. Without SCM, considerable time and effort would
be required to control the products of SDLC projects or systems in production.
A Configuration is the complete technical description required to build, test, accept, install, operate, maintain and support a system. It includes all documentation pertaining to the system as well as the system itself.
SCM is a key process in managing software development, operation, maintenance, and enhancement. The objectives of the Software Configuration Management (SCM) process are :
to identify the configuration of software at discrete points in time; and
to systematically control changes to the identified configuration for the purpose of maintaining software integrity and traceability throughout the software life cycle.
SCM consists of four functions :
Identification of the components that make up the software system and that define its functional characteristics;
Control of changes to those components;
Status Accounting of the processing of change requests and, for approved requests, their implementation status;
Audit on the existence, completeness and integrity of the controlled components, and the implementation of SCM activities.
This guide describes the principles of SCM, its interfaces and its constituent functions throughout the
development and maintenance stages of application software. It also describes the generic organization structure and responsibilities
for performing SCM.