Requirements and their related history can be exported from Doors to Microsoft Visio or MindJet's MindManager, two common applications for diagramming systems, he said. Doors is also linked to Microsoft Visual Studio Team Foundation Server, which allows requirements to be dragged and dropped onto work items in Visual Studio's software development process.
Through a new Web access feature, requirements and the discussion around them can be viewed from any Web browser as well as the Doors user interface, making Doors' requirements accessible by a widely distributed development team, Carillo said.
Likewise, there are more team aspects to the next release of Telelogic Change version 5.0. Change basically is a change management system that captures changes to source code and establishes an audit trail of all changes to a system. In this function, it's been integrated with the open source Subversion change management system so that independent teams may submit their code from a Subversion-based project, Carillo said.
But Change 5.0 is also now geared "for a different kind of change, collaborative change" between designers, developers, and product managers. Change serves as the underlying, shared repository for information on both software and design changes.
Change 5.0 is meant to "do problem tracking, change request tracking, and workflow management," Carillo said. It's also been integrated with the IBM Rational ClearCase configuration management tool. Once an application is configured to its operating system and hardware and committed to production, any changes to that configuration need to be available in the tools that maintain the application, he said.
Telelogic System Architect release 11.1, a software and business process modeling tool, has been integrated to work with Change. The integration allows analysis of software services and business processes, relating captured changes to such questions as: "Why was this changed? Who made this change? What is the impact of this change?"
Being able to relate changes in existing software back to original models and requirements allows system architects to track dependencies, foresee other changes that must be added, and model how the system should work in the future, Carillo said.
Telelogic executives report to the Rational Software unit general manager, Danny Sabbah.