Guideline: Overview of the DOORS/RTC Integration
This guideline describes the tool prerequisites and the overall installation procedure.
Main Description

Overview

This installation guideline is largely based on the article found at: Configuring Rational DOORS and Rational Team Concert to integrate with one another article on jazz.net. Some of the steps have been modified for this specific Medical Device Solution demonstration.

You can configure Rational® DOORS® and Rational Team Concert™ (RTC) to integrate with one another by using Open Services for Lifecycle Collaboration (OSLC), an open standard that IBM is developing in co-operation with business partners and customers.

You use Rational DOORS to manage your requirements, and RTC to put your requirements under change control, preventing uncontrolled changes to your requirement set. Strict control of requirements is mandatory under many quality systems, and is needed if you are to keep track of the state of your requirements at any point in your product lifecycle.

The change control can be as strict or as loose as you like. After you have set up the two applications to communicate with one another, you can set up workflows in RTC and configuration templates in Rational DOORS with as much flexibility as you want. In this example, you will define a simple Requirements Change Request workflow that is based on the RTC Work Item Template which is part of the IBM Rational Systems Engineering solution.

As with many process automation tasks, it is essential that you plan your integration. You cannot set up a change control system "as you go". You must know in advance what types of work items you will want to use, whether you want to have more than one workflow, how you want to control your change requests, and so on.

This procedure contains example values for you to enter as you follow the instructions. If you already have values of your own, you can use them. Though the generic change management integration included in Rational DOORS works with Rational Change, Rational ClearQuest®, and RTC, this guideline focuses on RTC.

Finally, this guideline assumes you have an intermediate knowledge of Apache Tomcat, RTC and Rational DOORS, and it is organized sequentially to allow a single user to follow the procedure.

Supported software

The information in this guideline is based on the following software running on Microsoft Windows:

  • Rational DOORS 9.4
  • Rational DOORS Web Access 1.5
  • Rational License Key Server 8.1.2
  • Rational Team Concert RTC 4.0

The MS Windows server should have these minimum specifications for this evaluation:

  • One(1) multi-core CPU
  • 4Gb RAM
  • 60Gb HDD
  • IPv4 address
  • TCP Ports available: 27000, 36677, 8080, 8443, 9443
  • Windows Server 2003 or Windows Server 2008 (32-bit or 64-bit, 64-bit preferred)
  • Internet Explorer or (optional) Firefox w/IETab2 add-on
  • An internet connection is required from the machine used to evaluate the solution as there are many links in the method content to external sources
The MS Windows server must have a C: drive and you must have Windows administrator privileges on the local computer.

RTC can be used with a number of browsers. The DOORS/RTC integration is supported only with Internet Explorer and Firefox, and to make it run on Firefox you need to use the IETab2 plug-in to emulate Internet Explorer. This is because the Rational DOORS Web Access Change Details view needs ActiveX and the Change Details window cannot be rendered fully in Firefox without the plug-in.

We also recommend that you add the name of your Evaluation Windows Host to your Web Browser’s list of Intranet sites and/or Trusted Sites.

Procedure

The outline of the install procedure is as follows:

  • Install and configure the Rational License Key Server
  • Install and configure Rational DOORS Web Access and Rational DOORS
  • Configure Rational Team Concert (RTC)
  • Configure RTC and Rational DOORS to communicate with one another

To begin the tool installation and configuration, go to the Project Initiation scenario (also known as a Capability Pattern*) and execute the tasks in the order shown.

*Tip: In Rational Method Composer a scenario is described through a Capability Pattern. A Capability Pattern is simply a reusable set of tasks to accomplish a goal, a mini-work breakdown structure. One can create RTC work items from Capability pattern using Rational Method Composer in order to plan, assign and track work based on proven patterns of success. Each work item created in this manner has links back to the method guidance to help practitioners complete the task. We are using Capability Patterns to describe the evaluation tasks. On a real project, you would use Capability Patterns to capture a set of related work items that are performed frequently during development and maintenance.