Suspect Links

Working on a server project requires up-to-date knowledge of all relevant project changes. Thus, we introduce a new set of validation rules for suspect link analysis. These rules help you track changes in Requirements that are linked to design elements (such as SysML Blocks, Test Cases, Use Cases, etc.) by Satisfy, Derive, Refine or Verify relationships, and stay informed about unlinked and deprecated Requirements in the model.

Suspect links functionality

Enabling suspect links tracking applies the <<track>> stereotype to the relationships between the Requirements and the design elements. The stereotype contains a fingerprint tag dedicated to identifying changes at the relationship end (e.g., a Requirement by default). It also contains a version tag for storing the version when showing changes between relationship end elements.

The <<track>> stereotype is applied to the relationships automatically right after enabling the suspect links tracking, changing the tracking scope, or creating a new relationship (in the case when suspect links are already enabled) if the following criteria are satisfied:

• The relationship type is Satisfy, Verify, Refine, or deriveReq.
• If custom suspect links tracking is created, the relationship type, direction, source, and target element types should be as defined in the configuration.
• The relationship itself and the relationship's source and target elements are under the specified tracking scope.

The following topics contain more information on Requirements tracking:

• Tracking elements affected by Requirement changes
• Tracking deprecated Requirements
• Tracking unlinked Requirements

• Solving untracked links issue

You can also create your own suspect links customization to keep track of the changes in the elements of the specified type. To learn more, read the following topic:

• Customizing suspect links tracking