|
|
|
|
Software configuration management
|
| |
|
| |
- Not to be confused with revision control.
In software engineering, software configuration management (SCM) is the task of tracking and controlling changes in the software. Configuration management practices include revision control and the establishment of baselines.
SCM concerns itself with answering the question "Somebody did something, how can one reproduce it?" Often the problem involves not reproducing "it" identically, but with controlled, incremental changes.
Discussion
Ask a question about 'Software configuration management' Start a new discussion about 'Software configuration management' Answer questions from other users |
Encyclopedia
- Not to be confused with revision control.
In software engineering, software configuration management (SCM) is the task of tracking and controlling changes in the software. Configuration management practices include revision control and the establishment of baselines.
SCM concerns itself with answering the question "Somebody did something, how can one reproduce it?" Often the problem involves not reproducing "it" identically, but with controlled, incremental changes. Answering the question thus becomes a matter of comparing different results and of analysing their differences. Traditional configuration management typically focused on controlled creation of relatively simple products. Now, implementers of SCM face the challenge of dealing with relatively minor increments under their own control, in the context of the complex system being developed.
Terminology
The history and terminology of SCM (which often varies) has given rise to controversy. Roger Pressman, in his book Software Engineering: A Practitioner's Approach, states that SCM is a "set of activities designed to control change by identifying the work products that are likely to change, establishing relationships among them, defining mechanisms for managing different versions of these work products, controlling the changes imposed, and auditing and reporting on the changes made."
Source configuration management is a related practice often used to indicate that a variety of artifacts may be managed and versioned, including software code, documents, design models, and even the directory structure itself.
Atria (later Rational Software, now a part of IBM), used "SCM" to mean "software configuration management". Gartner uses the term software change and configuration management.
Purposes
The goals of SCM are generally:
- Configuration identification - What code are we working with?
- Configuration control - Controlling the release of a product and its changes.
- Status accounting - Recording and reporting the status of components.
- Review - Ensuring completeness and consistency among components.
- Build management - Managing the process and tools used for builds.
- Process management - Ensuring adherence to the organization's development process.
- Environment management - Managing the software and hardware that host our system.
- Teamwork - Facilitate team interactions related to the process.
- Defect tracking - Making sure every defect has traceability back to the source
SCM tools
- See Application lifecycle management tools
See also
External links
- , Configuration Management Wiki - A wiki web dedicated to Configuration Management
- , online community and resource center for configuration management
- , a professional base bank
|
| |
|
|
