Creating impact analysis diagrams by using SQL

The impact analysis flow supports the relational store, and you can create impact analysis diagrams by using SQL to find artifacts that are related to a selected focus artifact. You can then analyze each of the linked artifacts.

About this task

An impact analysis flow provides an overall view of how artifacts in a product are related. By using impact analysis diagrams, you can discover all the artifacts that link from the focus artifact, or you can explore the impact of changes on the related artifacts.

Procedure

  1. From the main menu, click Analysis > Create > Impact analysis diagram and create the diagram.
    1. In the Query language area, select SQL.
    2. Select the DataSource as Lifecycle Query Engine from the list. To select the project scope, click the Edit icon on the Focus and Profile tab.
      Note: If Lifecycle Query Engine scoped by a configuration is selected for the data source, you need to select the configuration by using the current configuration picker. For more information, see Working with data in configurations.
    3. In the Select project area dialog, select the project areas that you want to include for the impact analysis.
    4. To select the artifact type and the condition, click the Edit icon for the artifact type.
      Note: The Added artifacts page appears only when the query language is set to SPARQL.
    5. To add a condition, in the Select focus artifact type dialog, click Add condition. The related options are displayed with the list of conditions.
  2. On the Select artifact type page, click Start analysis to run impact analysis on your focus artifact.

    The analysis starts and draws the focus artifact with the artifacts that have a relationship to it.

  3. After the impact analysis diagram is created, browse the analysis diagram. From the main menu, click Analysis > Browse > Impact analysis diagram
    Note: To improve performance of the generated SQL by reducing the number of joins, Lifecycle Query Engine relational store only one direction of cross-application links.
    • Links between Engineering Workflow Management and DOORS® Next artifacts are always stored as outgoing from Engineering Workflow Management artifacts to DOORS Next artifacts.
    • Links between Engineering Workflow Management and Engineering Test Management artifacts are always stored as outgoing from Engineering Workflow Management artifacts to Engineering Test Management artifacts.
    • Links between Engineering Test Management and DOORS Next artifacts are always stored as outgoing from Engineering Test Management artifacts to DOORS Next artifacts.

    Creating an impact analysis diagram in Engineering Insights where the focus artifact is a requirement does not render any outgoing links, from requirements to test cases or work items because it reverses when stored in the Lifecycle Query Engine relational store.

What to do next

After analysis diagrams are created, different conditions can be created. The impact analysis condition allows the selection of exact type of artifacts to be included or excluded from the impact analysis diagram. Enter the condition name and description and select SQL for the query language. To add conditions to the analysis diagram, click the Add icon. Click Save to view the created conditions.

After the conditions are added, you can browse the conditions. From the main menu, click Analysis > Browse > Impact analysis conditions