CM Outsider point of view

From the three different definitions of SCM, the "management of Software Configurations" is the SCM choice.

CM's choice is quite clumsy and unclearly stated though: it tries to avoid even the choice of "Software CM" definition by building up a defensive wall of restrictions.

Firstly, CM admits that SCM is the "CM of software", but stipulates for such an amazing term as the pure software, i.e. ignoring the open door for management of arbitrary domains via their software representations. This is a strikingly incongruous limitation.

Secondly, positioning SCM as "CM in (with the help of) software" cannot be avoided, but CM claims it's a partial and insignificant help of some software tools, that may be possible, and it is of a little interest.

I.e. CM tries as hard as it can (in a non-convincing way, though) to remain uninvolved in the Software Configuration Management and keep the outsider point of view. - Why would this be so necessary?

Perhaps, the answer is that CM has an ambition of being/becoming a governing discipline and thus trying to employ the principle "Divide and Conquer". Whereas SCM thinks of itself as of collaborative concern.

-- TatyanaShpichko? - 04 Feb 2007