An indirect association links domain elements and requirements through proxy requirements and traceability. Indirect associations are particularly powerful for creating many-to-many relationships with traceability between multiple requirements and a single proxy or between multiple proxies and a single requirement.
With the default project configuration, when you associate a non-use-case
domain element (such as a class) with a requirement, the integration creates
a proxy. This proxy requirement represents the domain element within Rational RequisitePro and is
linked directly to the domain element. This direct link is represented by
a link arrow , which
is visible in both the Model Explorer view and the Requirement
Explorer view. Proxy requirements are created in the Eclipse Element
Proxies package in the Requirement Explorer view. The
integration also creates traceability from the proxy to the requirement that
you selected for the association. This requirement trace is represented by
a link-by-proxy arrow.
The following figure provides an example of a link to
a proxy and a requirement trace from the proxy to the requirement. Notice
that the requirement trace from the "Create report" proxy to the "Generate
reports" requirement is visible in the Requirement Trace view.
The following figure represents an indirect association between a domain element and multiple requirements using a proxy and multiple requirement traces.
Using the previous example of a class, the following figures demonstrate how the "Create report" class can be associated with two feature requirements and viewed within the Requirement Query Results view. The first figure shows a Traceability Tree view; the second figure shows a Traceability Matrix view.
Related information