Lets begin at the beginning. The terms Source Code Control and Configuration Management, are often bandied about, but what do they mean?
Traditional Source Code Control
When many software developers think of SCM/CM they think of of traditional SCC,
Tools like CVS and PVCS VM fall into this category. Whilst PVCS VM does have some higher end CM features, it is still primarily a SCM tool.
Configuration Management takes a much broader look at the process of developing software. The degree to which a particular tool implements CM features varies greatly, however they include:
These features make implementing source code control much more worthwhile for the software developer. Allowing each developer to create software in an insulated work area, updating with outside changes at their discretion leads to a much better working environment than one where one developers 'build' is constantly being broken by another developers 'fix'.
With CM developers work on checked-out versions of objects to prototype, edit, build and debug before making their changes available to other developers, without being isolated from the development process.
Read more about Uniface Version Control
Beginning to your CM Solution, Nadine M. Bounds, Susan Dart.
Configuration Management Frequently Asked Questions, Version: 6.7c
|$Revision$ $Date$||[go to top]|