In software package engineering, Software Configuration Management (SCM) is that the task of tracking and dominant changes within the software. Configuration management practices embody revision management and therefore the institution of baselines.
SCM issues itself with respondent the question “Somebody did one thing, however will one reproduce it?” typically the matter involves not reproducing “it” identically, however with controlled, progressive changes. respondent the question so becomes a matter of comparison totally different results and of analysing their variations. ancient configuration management generally centered on controlled creation of comparatively easy merchandise. Now, implementers of SCM face the challenge of handling comparatively minor increments below their own management, within the context of the advanced system being developed.
The history and world of SCM (which typically varies) has given rise to difference. Roger Pressman, in his book Software Engineering: A Practitioner’s Approach, states that SCM could be a “set of activities designed to regulate amendment by distinctive the work merchandise that area unit seemingly to vary, establishing relationships among them, shaping mechanisms for managing totally different versions of those work merchandise, dominant the changes obligatory, and auditing and reportage on the changes created.”
Source configuration management could be a connected practise typically wont to indicate that a spread of artifacts could also be managed and versioned, as well as software package code, documents, style models, and even the directory structure itself.
Atria used “SCM” to mean “software configuration management”. Gartner uses the term software package amendment and configuration management.
The goals of SCM area unit generally:
Configuration identification – What code area unit we have a tendency to operating with?
Configuration management – dominant the discharge of a product and its changes.
Status accounting – Recording and reportage the standing of elements.
Review – making certain completeness and consistency among elements.
Build management – Managing the method and tools used for builds.
Process management – making certain adherence to the organization’s development method.
Environment management – Managing the software package and hardware that host our system.
Teamwork – Facilitate team interactions associated with the method.
Defect Tracking– ensuring each defect has traceability back to the supply
For more project management related articles – click on Project Management Articles