Getting ahead in DevOps with Collaborative Lifecycle Management 6.0
By: Vidhya V Kumar
Last week, IBM® announced the release of Coll
As you know, DevOps is about being quicker and more flexible - quicker in getting product features to customers; and flexible in catering to multiple customer requirements at the same time. The first requires automation and the second parallel development capabilities.
Central to parallel development is conf
More importantly – for parallel development - you can create parallel ‘streams’. A stream is a set of artifacts linked together by their common relationship to a product variant. The coexistence of multiple product variants necessitates the coexistence of multiple streams. In CLM you create streams by simply branching from a ‘baseline’ stream. You can then manage the streams independently without having to duplicate the artifacts common between streams.
When you do have multiple copies of an artifact, and wish to make similar changes to each of them, you can save time and effort by using the compare and merge functionality of CLM. With it you can examine the differences between artifacts in a stream, replace versions in one stream with those of another, and even merge versions across streams.
This ability to comp
A stream links together artifacts. For instance, it links together the test cases, test scripts, and other test artifacts either worked on by one team or related to a particular product variant. By following a link you can identify the test script version that is related to a particular test case version which in turn is related to a particular test suite version, and so on. A set of artifacts so related is called a ‘configuration’. CLM makes it easy to create and visualize configurations.
Configuration management across contexts – a simplified view
By introducing ‘global’ or cross-lifecycle configuration management, CLM 6.0 enhances this capability. CLM has supported geographically distributed agile development teams. Its highly integrated collaborative development environment accommodates feature-oriented development. Any activity or artifact - requirements, product designs and architectures, and test plans – can be cross-linked.
You can even create ‘hierarchies’ of global configurations to manage composite products. Hierarchies are strategic because they save time, effort, and capital by simplifying the reuse of requirements (IBM
CLM 6.0’s flexible and comprehensive configuration management is what you would use to smoothly move forward and back and sideways without tripping over multiple product strands. It is the feature that teams rely on most to lay the foundation for excellence in planning, project management, reporting and tracking, and collaboration, all hallmarks of a bustling DevOps culture.
To know more about the other exciting things in CLM 6.0, see Coll
This article was first posted on IBM developerWorks.