Configuration management
Configuration management is a necessary tool for managing complex software systems. Lack
of configuration management can cause serious problems with reliability, uptime, and the ability
to scale a system.
tracking software is software installed in an electronic device that is capable of reporting the
device's location remotely. Some device tracking software is sold as part of a subscription to a
staffed service that will assist the device's owner to update police officers with the device's
location.
Configuration Control
(Aliases: change control, change management)
It is not the strongest of the species that survive, nor the most intelligent, but the ones
most responsive to change. Charles Darwin
Configuration control is an important function of the configuration management discipline. Its
purpose is to ensure that all changes to a complex system are performed with the knowledge and
consent of management. The scope creep that results from ineffective or nonexistent
configuration control is a frequent cause of project failure.
Configuration control tasks include initiating, preparing, analysing, evaluating and authorising
proposals for change to a system (often referred to as "the configuration"). Configuration control
has four main processes:
1. Identification and documentation of the need for a change in a change request
2. Analysis and evaluation of a change request and production of a change proposal
3. Approval or disapproval of a change proposal
4. Verification, implementation and release of a change.
The Configuration Control Process
Why Configuration Control is Important
Configuration control is an essential component of a project's risk management strategy. For
example, uncontrolled changes to software requirements introduce the risk of cost and schedule
overruns.
Scenario - Curse of the Feature Creep
A project misses several key milestones and shows no sign of delivering anything.
WHY?
The customer regularly talks directly to software developers asking them to make 'little
changes' without consulting the project manager.
The developers are keen to show off the new technology they are using. They slip in the
odd 'neat feature' that they know the customer will love.
Solution: Implement configuration control. Document all requests for change and have them
considered by a Configuration Control Board.
Software configaration management
Software Configuration Management (SCM) is a process to systematically manage, organize,
and control the changes in the documents, codes, and other entities during the Software
Development Life Cycle. The primary goal is to increase productivity with minimal mistakes.
SCM is part of cross-disciplinary field of configuration management and it can accurately
determine who made which revision.
Configuration Identification:
Configuration identification is a method of determining the scope of the software system. With
the help of this step, you can manage or control something even if you don't know what it is. It is
a description that contains the CSCI type (Computer Software Configuration Item), a project
identifier and version information.
Activities during this process:
Identification of configuration Items like source code modules, test case, and
requirements specification.
Identification of each CSCI in the SCM repository, by using an object-oriented approach
The process starts with basic objects which are grouped into aggregate objects. Details of
what, why, when and by whom changes in the test are made
Every object has its own features that identify its name that is explicit to all other objects
List of resources required such as the document, the file, tools, etc.
Example:
Instead of naming a File [Link] its should be named login_v1.[Link] where v1.2 stands for the
version number of the file
Instead of naming folder "Code" it should be named "Code_D" where D represents code should
be backed up daily.
Baseline:
A baseline is a formally accepted version of a software configuration item. It is designated and
fixed at a specific time while conducting the SCM process. It can only be changed through
formal change control procedures.
Activities during this process:
Facilitate construction of various versions of an application
Defining and determining mechanisms for managing various versions of these work
products
The functional baseline corresponds to the reviewed system requirements
Widely used baselines include functional, developmental, and product baselines
In simple words, baseline means ready for release.
Change Control:
Change control is a procedural method which ensures quality and consistency when changes are
made in the configuration object. In this step, the change request is submitted to software
configuration manager.
Activities during this process:
Control ad-hoc change to build stable software development environment. Changes are
committed to the repository
The request will be checked based on the technical merit, possible side effects and overall
impact on other configuration objects.
It manages changes and making configuration items available during the software
lifecycle
Configuration Status Accounting:
Configuration status accounting tracks each release during the SCM process. This stage involves
tracking what each version has and the changes that lead to this version.
Activities during this process:
Keeps a record of all the changes made to the previous baseline to reach a new baseline
Identify all items to define the software configuration
Monitor status of change requests
Complete listing of all changes since the last baseline
Allows tracking of progress to next baseline
Allows to check previous releases/versions to be extracted for testing
Configuration Audits and Reviews:
Software Configuration audits verify that all the software product satisfies the baseline needs. It
ensures that what is built is what is delivered.
Activities during this process:
Configuration auditing is conducted by auditors by checking that defined processes are
being followed and ensuring that the SCM goals are satisfied.
To verify compliance with configuration control standards. auditing and reporting the
changes made
SCM audits also ensure that traceability is maintained during the process.
Ensures that changes made to a baseline comply with the configuration status reports
Validation of completeness and consistency