Most CM professionals, I think, would agree that the CM database is not just another component of Application Life-Cycle (ALC) management, it's really at the heart of the matter. I'd like to say that the CM function shares the same stature - it's not just another component of your ALC management - it's the nerve. In fact, I'd like to go one step further and say that the integration of CM and Data Management (DM) capabilities, when done properly, can transform your ALC management environment into a next generation engine that will empower each component of your environment.
Perhaps you view CM as just another component of your ALC management suite. Let's explore a different approach by understanding CM as a capability that can be applied to the various components.
The ALC requires management tools spanning a wide spectrum. From request tracking and requirements management through to deployment management, problem tracking and customer tracking, there are a range of component tools required to manage the lifecycle. Internally, we use our own tool [CM+] for:
· Request management
· Requirements tracking and traceability
· Projects and activity work breakdown structures
· Document management
· Software version control
· Change management
· Baseline and build definition
· Problem tracking
· Test case and test run tracking
· Build and release management
· Customer tracking
That's quite a list of tool components. So, where does configuration management fit in? Is it all of these, some of these, none of these? Configuration management is a backbone technology.