Siteadmin, Check users, Administrators
6,631
edits
Changes
Jump to navigation
Jump to search
Line 3:
Line 3: − +
Configuration management (view source)
Revision as of 02:30, January 13, 2009
, 02:30, January 13, 2009no edit summary
There are three broad disciplines of configuration [[management]]:
There are three broad disciplines of configuration [[management]]:
* [[Software]] Configuration Management involves [[control]] of the source code [[file]]s used to generate software. This allows developers to retract changes that proved to be non-useful. Also, it allows the development of different versions of software. For instance, a company might develop a new game for both the PlayStation 3 and the [[XBox 360]]. Many files might be in common between the two, but others might be different. Software configuration management allows the developers to easily contribute to both.
* [[Software]] Configuration Management involves [[control]] of the source code [[file]]s used to generate software. This allows developers to retract changes that proved to be non-useful. Also, it allows the development of different versions of software. For instance, a company might develop a new game for both the PlayStation 3 and the [[Xbox 360]]. Many files might be in common between the two, but others might be different. Software configuration management allows the developers to easily contribute to both.
* Hardware Configuration Management involves tracking of physical computing resources and detailed descriptions of them.
* Hardware Configuration Management involves tracking of physical computing resources and detailed descriptions of them.
* Document Management involves tracking of versions of [[documents]].
* Document Management involves tracking of versions of [[documents]].