CrossVista gives sneak peak of future “task driven development” functionality at webMethods UK User Group meeting

CrossVista was pleased to be invited to present at the webMethods UK User group meeting hosted at Sainsbury’s offices in London today. In addition to presenting a brief overview of CrossVista’s core lifecycle management solution, attendees also got a sneak peak at some new CrossVista features scheduled for release in late Q1 or early Q2 of this year.

For Project Managers

This new “task driven development” functionality expands CrossVista’s current ticket management support into the development side of the application lifecycle. In the near future, project managers will be able to leverage their third party ticket management tools (such as Jira, ClearQuest, HPQualityCenter, Remedy, etc) to assign tickets to one or more developers. Each ticket could represent a new feature under development, a bug that needs to be resolved, and/or some other action that needs to be performed on CrossVista TEAM Server as part of your application lifecycle processes. WebMethods developers will then have access to their personal list of assigned tickets from within CrossVista’s TEAM VCS plugin for webMethods Designer (or CrossVista’s TEAM VCS plugin for webMethods environments that do not leverage webMethods Designer.)

For WebMethods Developers

At the time of checkin, WebMethods Developers will be able to assign their code and/or configuration changes to a particular ticket. CrossVista will manage all of the baselining in the background so developers no longer have to worry about overwriting another developer’s code/configuration changes. Multiple developers will be able to contribute their code to a particular feature in parallel so true concurrent development will become even easier.

For Build Managers

When development on a new feature is complete, the build manager’s job also becomes much easier. Because all of the changes for a particular feature are logically associated with a given ticket within CrossVista, CrossVista can easily compose a patch release representing all of the changes associated with that ticket. Build managers will no longer have to “figure out” which revisions should be included for a particular feature… CrossVista keeps track of it for them. A patch release containing all changes related to a feature can then be promoted/deployed/rolled back independently or incorporated with other patches as part of a larger Release.

Note also that a given patch release can include code and/or configuration changes from IS, TN, Broker, BPM, Optimize, MyWebMethods, etc.

“This new functionality will make it considerably easier for users to organize their code and/or configuration changes as part of the end-to-end lifecycle.” says Dan Schirf, Vice President of Sales at CrossVista. “It also provides the foundation for a wide range of new change management features which we are planning to release later this year.”

By bundling together the functions of Version Control, Change Management, Configuration Management, and Release Management, CrossVista TEAM Server provides one solution for managing all aspects of the webMethods application lifecycle.

January 27, 2011 | News / Events