What is the difference between ALM and C/ALM?
3 answers
ALM is very often associated with s single supplier integrated tool solution. Whereas Collaborative ALM is an open, interface based, multiple supplier framework, leveraging collaboration capabilities, and performance benefits, beyond single tool environment.
Example: In a traditional ALM solution, you would need to stick to the specific Requirements Management, Testing, and CM tools which the ALM vendor provides. In CALM, you would pick the best of breed tool for each domain engineering task - and still use these in a single environment.
This is exactly what Jazz provides; an object model and integration framework for flora of tool suppliers.
Even if here at the Jazz forum, we mainly see and hear about IBM solutions, Jazz community actually includes range of external (non-IBM) collaboration partners and tools. And this distincts Jazz, and CALM from any other "ALM" solution.
Example: In a traditional ALM solution, you would need to stick to the specific Requirements Management, Testing, and CM tools which the ALM vendor provides. In CALM, you would pick the best of breed tool for each domain engineering task - and still use these in a single environment.
This is exactly what Jazz provides; an object model and integration framework for flora of tool suppliers.
Even if here at the Jazz forum, we mainly see and hear about IBM solutions, Jazz community actually includes range of external (non-IBM) collaboration partners and tools. And this distincts Jazz, and CALM from any other "ALM" solution.
Theju, as you mentioned, ALM is about integrating the different disciplines required to design, develop and deploy applications. CALM is about supporting the efforts of multiple people, including small and large teams and those which may be geographically distributed in ALM efforts. Collaboration is really one of the most important aspects of any substantial effort because a single person can only achieve so much within a given time period. You may also see us refer to CLM which is really just a recognition that not all efforts are focused on delivering IT applications but there are other kinds of deliverables and user audiences such as those in the systems space.