Tracking changes by using TRS and LQE
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 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.
- Configure LQE to consume the DOORS database as a TRS provider. For more details, see the LQE documentation in the TRS consumer application, such as Rational Engineering Lifecycle Manager. Also see the Lifecycle Query Engine (LQE) - Getting Started documentation on Jazz™.net or the documentation for your integrated lifecycle applications.
Performance and security
If LQE is configured to make concurrent requests to DOORS for TRS data, IBM Engineering Requirements Management DOORS - Web Access (DWA) might run slowly, especially if users add many resources to TRS during high-demand periods. To reduce delays, the DWA administrator can add interoperation servers.
The security mechanism in LQE does not support all levels of security in 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 DOORS. However, LQE users cannot see modules or objects (requirements) in 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 DOORS database server. The server must be configured to exclude 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.