LOGIN | REGISTER NOW | SUBSCRIBE
 
Print

A team-first approach to ALM


By Carl Zetie
Email
October 11, 2011 —  (Page 1 of 3)
Carl Zetie Whether your favorite application life-cycle management tools come from commercial vendors, open-source projects, in-house development, or some mixture of all of these, it’s no secret that promoting collaboration across life-cycle tools, from requirements to development to test to build, has remained stubbornly difficult. Integrations can be complex to build, expensive to maintain, and frequently broken by tool upgrades. It’s easy to complain about tool integration, much harder to propose improvements; but there is a new approach to tool integration called Open Services for Lifecycle Collaboration (OSLC) that may provide the answer.

Integrating life-cycle tools has a long history. The most common approach has been to build pairwise integrations between tools, and while this is workable for a small number of integrations, the number of combinations can quickly grow unmanageably large. Version incompatibilities can also create an upgrade nightmare, often solvable only by relying on tools from a single vendor and its closest partners.

In reaction to this tangle, some vendors have attempted to build single repository solutions, with all the tools integrated around a common store. However, this limits development teams to tools integrated with the repository, which severely limits choice. This “Big Bang” upgrade simultaneously replaces every tool, migrates existing data, and recreates business processes and governance rules required to adopt the single repository. As you can tell, this is impractical for any team already invested in existing tools.

Other approaches depend on collaboration among committees of vendors, users and academics. For example, there have been attempts over the years to define a uniform meta-model for ALM assets, in the hope that this would at least facilitate the importation and exportation of assets between tools. Of course, getting so many interested parties, each with its own favored tools, to agree is, to put it politely, challenging, and the market often moves too fast for the standards setters to keep pace. Similarly, attempts to get competing vendors to integrate by standardizing around a common implementation framework stumble over the need for each vendor to protect its own investment.


Related Search Term(s): ALM, OSLC

Pages 1 2 3 


Share this link: http://sdt.bz/36001
 
Most Read  Latest News  Resources
SAP unveils SAP HANA platform innovations for Big Data and spatial processing
Features include smart data access and expanded cloud deployment options
Alteryx raises $12 million to put Big Data analytics in the hands of all business analysts
Quest founder's firm, Toba Capital, selects Alteryx as its first analytics investment
Google I/O kicks off
Developers get new APIs and tools, and the Go language hits version 1.1
Jelastic launches new version of its Java and PHP hosting platform
Jelastic today announced the launch of a new version of its ultra-scalable cloud hosting platform
Digg!  Digg
Reddit  Reddit
Slashdot  Slashdot
Share on facebook  Facebook
Share on Twitter  Twitter


close
NEXT ARTICLE
Organization works to blend application, product life-cycle management
The Open Services Lifecycle Collaboration group has made it its mission to bring these two concepts together Read More...
 
 
 




News on Monday  more>>
Android Developer News  more>>
SharePoint Tech Report  more>>
Big Data TechReport  more>>

   
 
 

 


Download Current Issue
MAY 2013 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?