Configuration Management is the processes through which a solution's baseline are identified and changes to those baselines are controlled.
Configuration Management must provide a mechanism for identifying, controlling and tracking the version of each software item.
The process of configuration management provides a mechanism for identifying, controlling and tracking the version of each software item. It also allows us to identify, define and plan for the identification of product baselines, version control of the product baseline, change control procedures, status of the change control process and baseline product and the ability to identify the release at each customer site and to determine what version of software best suits new customers.
A software change may only take place when Software Development receives an SDD, a PCR or Trouble Log.
Professional Services are responsible for providing the FSD for all internal and external customers (which Software Development will turn into an SDD) and the PCR (which may be turned into a SDD if required).
Quality Assurance Group is responsible for providing PRA forms to Software Development.
Software Development is responsible for managing the software source code release.
Professional Service is responsible for managing the software documentation and test cases release.
Software Development is responsible for providing the changes made to software items and product base to Professional Service for documentation and Sales & Marketing information.
Configuration management (CM) starts when a new software module is being developed or a current software module is being modified. The configuration
management for a software module ends when the module has been updated into the new Product Base Release Area and the corresponding documentation has been
updated to reflect the new Base release.
Procedures for Change Control
A change to a software source code item may only take place if accompanied by a Trouble Log, a PCR or a SDD. No changes are allowed to any software source code item without one of these 3 initiators. Any change to a software source code item will require a PCN to be filled out by the person making the change. The PCN will be turned over to the Release Coordinator after the software has been loaded into the Customer Site Directory Area. The Release Coordinator will be responsible merging the PCN changes into the Base release, updating the appropriate forms and providing a copy of the PCN to Professional Service so that Professional Service can manage the documentation. The detailed procedures for change control and configuration management are included in detail for changed initiated by a TL, a PCR and SDD.
Release Coordinator Duties
The release coordinator is responsible for creating a new software release, updating the associated configuration management documentation, and providing the documentation to Professional Services. The main duties of the Release Coordinator (RC) are to merge the software from the customer site area into the Product Base Release Area. Only the RC is allowed to merge the software and update the Product Base Release Area.