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.

Tracked Resource Sets (TRS)

LQE creates an index of linked lifecycle data from one or more TRS records. Changes that occur in indexed resources are tracked in the TRS change log. Those changes are propagated to the index to keep it up to date. These changes include the creation, deletion, and modification of requirements, modules, and views. Data from Rational DOORS and multiple lifecycle tools can be queried as cross-application links between resources by using the SPARQL query language.

Data that is returned by these queries can be used to build impact analysis views, traceability views, and other presentations of linked resource data. Access to the TRS records in the index is controlled by licenses and user authentication.

To implement change tracking by using TRS, a system administrator must do these tasks:

Performance and security

If LQE is configured to make concurrent requests to Rational DOORS for TRS data, Rational DOORS Web Access might run slowly, especially if users add many resources to TRS during high-demand periods. To reduce delays, the Rational DOORS Web Access administrator can add interoperation servers.

The security mechanism in LQE does not support all levels of security in Rational DOORS. LQE users can see the attributes that the configured functional user can see, even if the LQE users do not have access permissions for those attributes in Rational DOORS. However, LQE users cannot see modules or objects (requirements) in Rational DOORS if they do not have read-access permissions for those artifacts.

Supported database servers

To use TRS and LQE, you must use version 9.4.0.1 or later of the Rational DOORS database server. The server must be configured to exclude Rational DOORS clients that are earlier than version 9.4.0.1. To exclude those clients, go to the General tab of the Database Properties window and set the minimum client version to 9.4.0.1.

Related concepts:
Configuring the Rational DOORS database
Related tasks:
Configuring Rational DOORS data for external applications

Feedback