How to configure bidirectional linking between Rational Design Manager and Rational Software Architect

Technote (FAQ)


Question

Can you configure bidirectional linking between IBM Rational Design Manager and IBM Rational Requirement Composer, regardless of their respective versions?

Cause

The release notes of Rational Design Manager 4 document a new feature that makes bidirectional linking possible. You can link between designs and requirements from Rational Requirement Composer. However, Rational Requirement Composer 4 introduced support for showing links from requirements to designs.

Answer

The following tables illustrate which types of links are available depending on the versions of the products.

Support for links from designs to requirements (these links are visible in Rational Design Manager):

Links from designs to requirements Rational Requirements Composer 3.0.x Rational Requirement Composer 4.0.x
Rational Design Manager 3.0.x Supported Supported
Rational Design Manager 4.0.x Supported Supported


Support for links from requirements to designs (these links are visible in Rational Requirements Composer):
Links from requirements to designs Rational Requirements Composer 3.0.x Rational Requirement Composer 4.0.x
Rational Design Manager 3.0.x Not Supported Not supported
Rational Design Manager 4.0.x Not supported Supported

In summary, you can establish bidirectional linking when using Rational Design Manager 4.0.x and Rational Requirement Composer 4.0.x.


Related information

DM 4.0 New and Noteworthy
Integrating DM with RRC

Cross reference information
Segment Product Component Platform Version Edition
Software Development Rational Requirements Composer Integrations: IBM Windows, Linux 3.0.1, 3.0.1.1, 3.0.1.2, 3.0.1.3, 3.0.1.4, 3.0.1.5, 4.0, 4.0.0.1

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Rational Software Architect Design Manager
Integrations: IBM

Software version:

3.0, 3.0.0.1, 3.0.1, 4.0

Operating system(s):

Linux, Windows

Reference #:

1614489

Modified date:

2012-10-18

Translate my page

Machine Translation

Content navigation