Tasktop Launches Software Lifecycle Integration, New Eclipse M4 Project

By Darryl K. Taft  |  Posted 2013-03-27 Print this article Print

Other components include the SLI Data Model, a common model and taxonomy that provides the key abstraction mechanisms needed for an organization to implement SLI, and SLI Integration Patterns, which are repeatable design patterns that will help architects streamline the automation and SLI process.  In addition, the new Eclipse Mylyn m4 open-source project will implement the SLI data model and provide the runtimes required to embed SLI into integrated ALM applications. The project will be server-side focused -- de-coupled from the Mylyn client -- and also serve as the bridge between the SLI data model and existing standards, such as Open Services for Lifecycle Collaboration (OSLC). Tasktop is familiar with OSLC from collaborations with IBM.

Faced with increasingly complex tool chains, outsourced development and the need to deliver more software with less, SLI will provide software organizations with the infrastructure to connect the software delivery and maintenance process. Its intent is to rally the industry around a common set of technical and process disciplines to enable software delivery professionals, project managers, operations and the PMO to work effectively together by maximizing the flow of information between software delivery tools and practices.

Kersten noted that 30 percent to 70 percent of software projects fail – a rate that is simply too high, he said.

“Agile creates the need to break down the barriers between disciplines. But software delivery tools add to the barriers,” said Ken Schwaber, founder of Scrum.org. “The time is right for organizations to start thinking about connecting tools more strategically to enable the practice of software delivery to flow.”

The foundation of SLI is based on the abstraction of the social task – or all of the related and interconnected activities that make up the software development, delivery and maintenance process, Tasktop said. This expands upon the data flow models associated with traditional ALM that center on core development artifacts. SLI provides the technical architecture – implemented as an ALM integration bus – to create a central flow for software delivery.

SLI will improve insight, choice and flow in the enterprise ALM lifecycle. It will unlock data trapped in ALM silos for end-to-end visibility and analytics, deploy a build-measure-learn loop from idea to deployment, and automate end-to-end traceability, governance and compliance, Kersten said. Regarding choice, SLI will integrate best-of-breed, open source, legacy and enterprise agile tools, connect stakeholders within and across the organization and connect the software supply chain. It also will help foster cross-stakeholder collaboration and capture the social conversation of software delivery.

“Similar to the benefits that we saw with enterprise services buses, we will be able to connect heterogeneous ALM stacks and create the connected lifecycle,” said Dave West, Tasktop’s chief product officer, in a statement. “Tool vendors will have the ability to integrate their solutions with entrenched and best-of-breed tools, and practitioners will have the ability to use their tool of choice. The lack of integration has become the main bottleneck in software delivery and this initiative takes a community approach to solving this problem once-and-for-all.”

Meanwhile, in an interview with TechTarget’s SearchSOA, West said: “You could say that SLI puts the L in ALM by integrating the tools and practices that comprise the lifecycle. While I have always preached the need for ALM, I have been very disappointed with the reality of ALM deployments.”


Submit a Comment

Loading Comments...
Manage your Newsletters: Login   Register My Newsletters

Rocket Fuel