A direct association links a model element and a requirement. This link associates the model element and requirement and synchronizes both artifacts so you can manage them as a single, conceptual item.
By default, the Rational® RequisitePro® integration directly associates use-case model elements and use-case requirements. This creates a one-to-one, exclusive relationship between the use-case artifacts.
A direct association extends the associated artifacts. For example, a direct link from a use-case requirement to a use-case model element further defines the use case by displaying its interaction with actors and other model elements. It also helps you ensure that your model satisfies all the use cases that are defined in the project requirements. With associated use cases, you can also navigate to documents that elaborate the use cases with descriptions, flows of events, special requirements, and conditions.
The following figure provides an example of a link in a direct association.
Notice that this direct link is represented by a link arrow , which is visible in both the Model
Explorer and the Requirement Explorer views.
When you link model elements and requirements in a direct association, the name and text of the requirement should be synchronized with the name and documentation text of the model element. Therefore, with the default project properties, when you create the link, you are prompted to resolve any differences between the name and text of the requirement and the model element if they do not match. This prompt is also displayed if you change the name or text of either of the linked artifacts. Synchronization is not required for blank requirement names, because requirements created within RequisitePro documents use the text rather than the name field.
Parent topic: Requirement concepts and artifacts
Related concepts
Requirement traceability
Indirect associations
Associations between requirements and model elements
Related tasks
Viewing requirements traceability
Creating direct associations between requirements and model elements
Creating model elements from requirements
Creating requirements from model elements