In Information Technology and telecommunication, the term configuration management has the following meanings:
[The] management of security features and assurances through control of changes made to hardware, software, firmware, documentation, test, test fixtures and test documentation of an automated information system, throughout the development and operational life of a system. Source Code Management or revision control is part of this.
The control of changes--including the recording thereof--that are made to the hardware, software, firmware, and documentation throughout the system lifecycle.
Vesta (http://www.vestasys.org/), an advanced configuration management system. Free software. Used at Intel (http://www.intel.com/) for microprocessor design.
Sites for configuration management
CM Crossroads (http://www.cmcrossroads.com/), an online community for Configuration Management
Steve Easterbrook's CM Resource Guide [1] (http://www.cmiiug.com/faq-home.htm)
Parallel Development Strategies for Software Configuration Management [2] (http://www.methodsandtools.com/archive/archive.php?id=12)
Sourcecode systems such as CVS or Subversion are useful for managing collections of source files for building an application.
They also tend to have the hierarchical nature of their contents hard-coded; with sourcecode you rarely need to suddenly re-organize all of the files to browse by author or title, however this is a very common need for collections of documents.
They differ from a sourcecodemanagement system in that they often include a 'state' for a piece of content - it may be published, retired, or scheduled for release on a particular date, for instance.
Feeds |
Contact