Associating existing requirements and domain
elements
You
can associate requirements and domain elements using direct or indirect associations.
You can create associations by using menu items or dragging one artifact to
another.
What to do next
Creating direct associations between requirements and domain elements You
can create a direct association between a requirement and a domain element
if the Rational RequisitePro project
properties are configured to permit linking of the two artifact types. This
association links the requirement and the domain element in a one-to-one,
exclusive relationship and synchronizes the name and text (or documentation)
of both artifacts so that you can manage them as a single, conceptual item.
Reorganizing requirement proxies You
can reorganize requirement proxies in the Requirement Explorer view
so that they match the domain element structure in specific views, such as
the Navigator view. You must reorganize the proxies if
you move domain elements and want to keep the proxies in locations that correspond
to your project.
Renaming proxy packages You
can rename a proxy package; however, renaming a proxy package will affect
all team members associated with the Rational RequisitePro project.
A proxy package is a special requirement package that contains
proxy requirements created when linking requirements to domain elements.
Viewing and repairing requirement association problems Use
the Requirement Link Problems view to review and resolve
link problems between requirements and domain elements. Association (or link)
problems occur when associated artifacts are moved, deleted, or are otherwise
unavailable.
Removing requirement associations You
can remove a direct association between a requirement and a domain element.
This action does not remove the domain element, the requirement, or any traceability
relationships with the requirement.