Tracking changes with TRS and LQE

You can use Tracked Resource Sets (TRS) and the Lifecycle Query Engine (LQE) to track changes to resources in Rational DOORS from lifecycle applications, such as IBM Rational Engineering Lifecycle Manager (RELM).

TRS overview

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 LQE lifecycle index to keep it up to date. These changes include creation, deletion, and modification to requirements, modules, and views. Data from Rational DOORS and multiple lifecycle tools can be queried as cross-application links between resources by using SPARQL query language. The data that is returned by these queries can then be used to build impact analysis views, traceability views, and other presentations of linked resource data. Access to the TRS records in the lifecycle index are controlled by user authentication and tool licensing.

To implement change tracking with TRS, a system administrator must complete the following tasks:

Constraints and considerations

If LQE is configured to make multiple concurrent requests to Rational DOORS for TRS data, performance might be impacted for Rational DOORS Web Access users, particular if users add large numbers of resources to TRS during high-demand periods. To reduce delays, the Rational DOORS Web Access administrator can add additional interoperation servers.

The security mechanism in LQE does not support all levels of security in Rational DOORS. Attributes that the configured functional user can see are visible to LQE users, even if those 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.


Feedback