CM versus SCM?

It seems we have separate lists of definitions for Software Configuration Management and for Configuration Management. Are these different? If so, what is the difference?

Historically, the term CM has been used first, in domains not related to software. It was process oriented (prescriptive). Then CM was applied to software, and soon one spoke of SCM without ever quite clearly expliciting what was meant. Relatively recently, one has started to speak again of CM, maybe hinting that it would be more general.

I don't think so. To me, SCM is exactly as general as CM. It is only (post-)modern CM, CM with software tools, applied to software representations of what is ultimately being managed, and enabling a descriptive (and less intrusive) approach: Manage what you do instead of Do what you manage. [Developed in CM Antithesis]

-- MarcGirod - 23 Jan 2003

---

We have a sub set of CM disciplines, which breaks out the more general CM function or "Classic CM" from the software build and release team, who compile operational code and load it onto media for use on the operational system (which in itself is dependant on configuration control), and the documentation control team, who administer the baseline doc set.

The "Classic CM" team (known as Systems CM) deal with and maintain the System Configuration of the system as a whole. As the build and release and document control functions are being managed by seperate teams under the CM banner, this leaves Systems CM to concentrate of the core roles of CM: Identification of CIs, Configuration Control, Configuration Status Accounting and Configuration Audits of Systems, whether the system conatins HW, SW or FW. Opinion: Folks - Its not just Software Configuration Management.

Agreed: The list of definitions probably got the wrong title just by accident.

Correct it's not just SCM. CMwiki is all about all types of CM thus there are seperate sections on SCM and CM. Feel free to update either one. -- PatrickEgan

The list of SCM definitions was named as such because a great many of the definitions are specific to software, and even many of the ones that aren't are software-centric from books or papers specific to software and/or from people who are primarily from the world of software development. There are still a few general CM definitions thrown in, but the list is predominantly focused on SCM. -- BradAppleton?

Patrick makes the most important point! Since this is a Wiki, most content is 100% collaborative. There are two separate wiki pages for CM and SCM. Those who feel strongly that a particular definition is not software-specific should feel "empowered" to go add that definition to the CM definitions page. or better yet, move it to the CM definitions page but put a reference to the new location from the old location (like this reference to Susan Dart's SCM definition) -- BradAppleton?

In the first historical phase, the use of plain CM ignored Software. In the most recent phase, the use of plain CM (or the belief it is equivalent to, or even included in Change Management) considers the S in SCM as accidental (instrumental). I take it as essential. -- MarcGirod - 02 Feb 2003

Could someone state whether Software Configuration Management means CM of software or CM by software? There seem to be two different implications above. -- NealFreeman? - 10 Feb 2003

I'm pretty sure SCM means CM of software. It will often be the case that software applications aid in the process of carrying out CM (of all things, hardware, software, documentation, etc.). But the "S" in SCM refers to what is being managed, and what those configurations are (software). -- BradAppleton? - 10 Feb 2003

You mean for you, it means... For me, it is ambiguous. This is the way it goes with natural languages. -- MarcGirod - 12 Feb 2003

SCM seems to have a more technical bent for me. It deals with the intangible, software and the "good" or running configurations. The number and variety of configuration items in software (and speed of change) becomes quite overwhelming for classic CM methodologies, where SCM tools and methods (especially Agile SCM) handles constant, parallel change accurately. Classic CM doesn't usually handle constant and parallel change terribly well. So SCM is a speciality arena of CM, adapted to the treacherous, inimical environment of software. -- ClintSchaeffer? - 20 Feb 2003

I could agree with this last view. It doesn't feel reasonable to consider the CM of Software, unless it is also CM in Software. CM is actually CM before Software. -- MarcGirod - 25 Feb 2003

Looking at this (old) page, makes me feel that there is a need to manage disagreements.