Configuration Management

SingTone Technologies uses the following Software Configuration Management (SCM) processes to ensure the success of each project. We use these processes to maintain, control, document, track, and report software application changes, operational environment changes to guard against third party threats, and document baselines.

  • Configuration Identification – Software is usually made up of several programs. Each program, its related documentation and data can be called as a “configurable item” (CI). The number of CI’s in any software project and the grouping of artifacts that make up a CI is a decision made for each project. The status of the CI’s at a given point in time is called a baseline. The baseline serves as a reference point in the SDLC.
  • Configuration Control – The process of deciding, co-coordinating the approved changes for the proposed CIs and implementing the changes on the appropriate baseline is called configuration control. It should be kept in mind that configuration control only addresses the process after changes are approved. The act of evaluating and approving changes to software comes under the purview of an entirely different process called change control.
  • Configuration Status Accounting – Configuration status accounting is the bookkeeping process of each release. This procedure involves tracking what is in each version of software and the changes that lead to this version. Configuration status accounting keeps a record of changes made to the previous baseline to reach the new baseline.
  • Configuration Authentication – Configuration authentication is the process of assuring the new baseline has the planned and approved changes incorporated. The process involves verifying functional aspects of the software are complete and also the completeness of the delivery of the right programs, documentation and data are being delivered.