03 Process versus Configuration Management
Description
This article is from the Configuration Management Tools FAQ, by Dave Eaton dwe@arde.com with numerous contributions by others.
03 Process versus Configuration Management
Vendors Don't Always Differentiate
Some products noted in this FAQ provide configuration management, not
development process management, others provide both but to varying
degrees. The vendors marketing configuration management tools do not
always distinguish the difference nor do they always explain which
services their tool is actually trying to provide for you. Briefly,
these two concepts are:
* Traditional Configuration Management - checkin/checkout control of
sources (and sometimes binaries) and the ability to perform builds
(or compiles) of the entities. Other functions may be included as
well.
* Process Management - control of the software development
activities. For example, it might check to ensure that a problem
report existed and had been approved for fixing and that the
associated design, documentation, and review activities have been
completed before allowing the code to be "checked in" again.
While process management and control are necessary for a repeatable,
optimized development process, a solid configuration management
foundation for that process is essential.
You Choose
Be certain to determine what form of management is most important to
your project, then be certain the tools you consider provide that
function.
Continue to:
My Books
