SCM Configuration Item.

Dissatisfied with the extensive existing definition on Configuration Item, based on a list of examples (which I find both arbitrary and disputable), I try here to offer an alternative definition of both Software Configuration and Configuration Item.

The two concepts are abstract, susceptible to be mapped onto real entities, for the purpose of managing them in a generic way. The definition builds upon the following interrelation:

A software configuration is a set of configuration items.

Members of such a set are identified in such a way that:

• the criterion used for the identification is applicable across various software configurations;
• out of all the possible items identified in such a way in different software configurations, only one at most may be found in any of them (exclusion principle).

Everything else I could add is beyond the definition proper.
I believe it may be useful to mention the issue of structure, without losing abstraction, or significant generality.

A software configuration is in most cases structured, e.g. as a graph, in which case the configuration item is tied to a certain 'node' in the graph. One must then however be able to tell which node plays the same role in different graphs.

The criterion used for the identification is, in all practical cases, objective, and supported by a tool.
The choice of the tool (software, again in all practical cases) results from complex tradeoffs. It is important to understand that this choice affects the conceptual nature of the management offered, which makes it difficult to compare different SCM systems.

-- MarcGirod - 25 Feb 2007