Linking to requirements and test artifacts

You can use the IBM® Engineering Lifecycle Management (ELM) product integration to create traceability links to new and existing artifacts in other Jazz-based products. Link from development artifacts to requirements and test artifacts. After creating links, you can display a summary of the linked artifact or navigate to the artifact. You can also add a widget to your dashboard to monitor the status of linked artifacts.

Before you begin

The product integration must be configured before you can perform this task.

About this task

As you link development artifacts to requirements and test artifacts, the link types define the traceability relationships between the artifact types. In the ELM, development artifacts are located in the Change and Configuration Management (CCM) application, requirement artifacts are located in the Requirements Management (RM) application, and test artifacts are located in the Quality Management (QM) application. The traceability relationships between the Change and Configuration Management application and the other applications are described in the following graphic and table.
The graphic shows how requirements and test artifacts are linked to development artifacts.

You can add links to requirements and test artifacts from the plan editor or work item editor.

Links page of Work Item editor.

Table 1. Cross-application linking for change and configuration management artifacts
CCM Link type RM Link type QM
Typically, groups of requirements are organized in collections for review, approval, and management purposes; for example, the high-level requirements that comprise the project vision are often grouped in a single collection. The requirements analyst, project manager, or development manager links the high-level requirements collection to a development plan in the CCM application. The test manager links the same collection to the test plan for the project. The test manager can generate high-level test cases from the each of the requirements in this collection.
Development plan

–> implements
<– implemented by

Requirements collection or module (high-level requirements, project vision)

–> validated by
<– validates

Test plan
High-level requirements are then elaborated by detailed requirements and associated artifacts such as business process diagrams, use cases, user interface sketches. Detailed requirements can be grouped in collections and linked to the development plan and test plan. Plan items and test cases can be generated for each requirement in the linked collection. Individual requirements can also be linked directly to work items or test cases.
Development plan

–> implements
<– implemented by

Requirements collection or module (detailed requirements)

–> validated by
<– validates

Test plan
Plan items, work items, stakeholder needs, enhancement requests, defects

–> implements
<– implemented by

Requirements

–> validated by
<– validates

Test cases
Note: Some applications support versioning of their artifacts by tracking the versions in configurations. A global configuration tracks multiple configurations. For example, a global configuration might include configurations from RM and QM project areas. If your organization uses the Global Configuration Management application to manage versioned artifacts in other applications, you can link work items to specific versions of those artifacts. To enable this linking, you must configure your project area accordingly. See Linking work items to artifacts in Configuration Management-enabled project areas.

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki