Integrating

Learn how to configure the product to integrate with your reporting, design, quality, change, and configuration management solutions.

Integrating Rational DOORS and Rational Team Concert
You can configure Rational® DOORS® and IBM® Rational Team Concert to integrate with one another by using Open Services for Lifecycle Collaboration (OSLC), which is a set of specifications for linking and viewing artifacts across the software development lifecycle. You can use Rational DOORS to manage your requirements, and you can use the Rational Team Concert work items capability to place those requirements under change control.
Integrating Rational DOORS and Rational Quality Manager
You can configure Rational DOORS and Rational Quality Manager to integrate with one another by using Open Services for Lifecycle Collaboration (OSLC), an open standard that IBM is developing in cooperation with business partners and customers. You can use Rational DOORS to manage your requirements, and you can use Rational Quality Manager to manage test plans and test cases that validate the requirements.
Integrating Rational DOORS with Rational DOORS Next Generation
You can configure IBM Rational DOORS to integrate with IBM Rational DOORS Next Generation in the Rational solution for Collaborative Lifecycle Management (CLM).
Rational DOORS for HP Quality Center Interface
Rational DOORS for HP Quality Center Interface is delivered as a separate installer.
Integrating Rational DOORS and Design Management
You can configure IBM Rational DOORS to integrate with IBM Rational Rhapsody® Design Manager and the design management capabilities in IBM Rational Software Architect by using Open Services for Lifecycle Collaboration (OSLC) linking.
Integrating Rational DOORS and Rational Publishing Engine
You can configure the integration with IBM Rational Publishing Engine to generate report documents from within IBM Rational DOORS.
Integrating Rational DOORS and Rational Change
You can use the IBM Rational DOORS integration with IBM Rational Change to track the implementation of requirements by linking them with change requests and tasks in Rational Change. You can configure this integration by using Open Services for Lifecycle Collaboration (OSLC).
Introduction to Change Management for Rational DOORS
Change Management for Rational DOORS is a tool used to enforce a formal process for the modification of your requirements, track the implementation of requirements by linking them with change requests or work items, and gather requirements by importing data from change management tools to serve as the basis for a new Rational DOORS document.
Rational DOORS Requirements Management Framework Add-on
Rational DOORS Requirements Management Framework Add-on is a separate installer.
Integrating Rational DOORS and Jazz Reporting Service
You can integrate IBM Rational DOORS with Jazz® Reporting Service and use the capabilities of Data Collection Component and Report Builder to create reports on data in Rational DOORS projects. This integration applies to Rational DOORS 9.6.1.7 or later.
Configuring Rational DOORS data for external applications
You can use the working set, attribute and link type mapping, and the reportable shape to configure IBM Rational DOORS data for integration with external applications. These applications include Rational Engineering Lifecycle Management, Jazz Reporting Service, and applications that are integrated with Rational DOORS by using OSLC.
Tracking changes by using TRS and LQE
You can use tracked resource sets (TRS) and the Lifecycle Query Engine (LQE) to track changes to resources in IBM Rational DOORS from lifecycle applications, such as IBM Rational Engineering Lifecycle Manager.
Configuring integrations by using OSLC
You can integrate data in lifecycle applications, such as change management, quality management, design management, and other requirements management applications with requirements data in Rational DOORS and Rational DOORS Web Access. Integration is implemented by using Open Services for Lifecycle Collaboration (OSLC) data sharing. After the configuration is complete, you can create traceability relationships between your requirements and other lifecycle application artifacts.