The following table lists the OSLC relationships that are used when you link artifacts across various domains. The table also links to definitions of the OSLC relationships.
Domain | Link relationships in Rational DOORS | Link relationships in external applications |
---|---|---|
Change Management (CM) | Rational DOORS artifacts can be linked to CM artifacts by using one of the following link types: |
A CM artifact can be linked to a Rational DOORS artifact by using one of the following link types: |
Quality Management (QM) | Rational DOORS artifacts can be linked to QM artifacts by using the following link type: |
A QM artifact can be linked to a Rational DOORS artifact by using one of the following link types: |
Requirements Management (RM) | Rational DOORS artifacts can be linked to external RM artifacts by using one of the following link types: |
An external RM artifact can be linked to a Rational DOORS artifact by using one of the following link types: |
Architecture Management (AM) | None. Rational DOORS artifacts do not have outgoing links to AM artifacts. | An AM artifact can be linked to a Rational DOORS artifact by using one of the following link types: |
When you open a module in Rational DOORS, if the module has external OSLC links with other lifecycle products, those links are discovered. In addition, the results are stored in a database-wide cache so that modules open faster in the future. This link discovery process might impact performance when you open a module, depending on the performance of the integrated product. The cache has a default timeout value of 5 minutes. After that time, the links must be rediscovered so that the cache has the latest status of the links. You can change the timeout value by using the setCachedExternalLinkLifeTime DXL perm. For more information, see "OSLC Link Discovery" in the DXL Reference Manual, which is available both as a PDF file and as from the Help menu.
When OSLC links are created in Rational DOORS or in an integrated remote application, a level 0 link label is created and can be stored in the remote application. Level 0 links are intentionally brief because they can be seen by users who do not have permission to see the full information about the linked artifact. Level 0 links are in this format: MODULE_NAME (OBJECT NUMBER). For example: System Requirements (121)
If the remote application requests more information by using an OSLC GET operation, which requires authentication, Rational DOORS returns a level 1 link label. The level 1 label includes more detail about linked object, in this format: OBJECT NUMBER: [OBJECT HEADING|OBJECT TEXT|OBJECT SHORT TEXT]. For example: 121: The car shall be able to accelerate to 60 MPH in less than 5 seconds.
Make sure that the remote application does not cache level 1 link label values. Those values must be calculated at run time to ensure that access control is enforced.