Tasktop Sync 2.0 Supports ALM Repository Introspection and REST Based Artifact Management
The latest version of application lifecycle unification framework Tasktop Sync supports ALM repository introspection and REST based application lifecycle artifact management. Tasktop team released last month version 2.0 of the tool. InfoQ spoke with Mik Kersten, CEO of Tasktop, about the new features in the latest release.
He said that the Tasktop Sync 1.0 release created a real-time connection between developers and QA team without requiring either to switch away from their tool of choice or to bridge the gap between dev teams using different ALM tools. While version 1.0 made it possible to write this mapping as XML, they wanted to help development managers discover and capture the ALM architecture in their organizations within the Sync tool.
The new release also includes an OSLC-based task linking feature that provides an OSLC linking service to repositories like HP Quality Center, Bugzilla, Jira, and Team Foundation Server. The OSLC service can be consumed by OSLC clients like IBM Rational Team Concert to allow the clients to preview tasks in the supported remote repositories.
Mik talked about the new features in Tasktop Sync 2.0 release.
InfoQ: How does the new OSLC-based application lifecycle artifacts linking works?
Mik: For Sync to work, ALM artifacts such as tasks and defects need to be linked across repositories via URLs. We have long had the feature of cross-repository linking within Tasktop Dev, with the ability to view the linked item without logging into another server. What OSLC does is provide this kind of on-demand preview of linked ALM artifacts within the browser UI, and is very nicely supported by IBM’s Collaborative Lifecycle Management (CLM) tools. To support this, Tasktop Sync provides an OSLC adapter for each of the dozens of ALM tools that we support via the Eclipse Mylyn common data model for ALM. While linking is only focused on a subset of the use cases supported by Sync, and is not intended to create a real-time and full-fidelity connection between stakeholders such as dev and QA, it provides a convenient way to create on-demand rich linking between ALM artifacts such as requirements and tests that reside in different tools.
InfoQ: The application lifecycle artifacts link feature has a REST interface. Can you tell us more about the architecture behind this feature?
Mik also discussed another new feature that can be used for ALM repository introspection. Sync connects to each supported ALM tool, retrieves its schema, displays it, and updates it as it changes. Prior to Sync 2.0, this had to be done by having an administrator log into each ALM tool, retrieving the repository schema, document it, then trying to figure out a mapping to the other ALM tools in the stack. Tasktop Sync 2.0 provides a console and authoring too for both introspecting and authoring each organization's ALM architecture. The goal is that each stakeholder in software delivery is able to use his or her tool of choice.