Associating existing requirements and domain elements
You can associate existing requirements and domain elements using
direct or indirect associations. Use menu items or simply drag one artifact
to another.
Creating direct associations between requirements and domain elements
You can create a direct association between an existing requirement and an existing domain element. This directly links the requirement and the domain element and synchronizes both artifacts so you can manage them as a single, conceptual item.
Reorganizing requirement proxies
You can reorganize proxies in the Requirement Explorer view
so they match the domain element structure in specific views such as the Navigator.
You need to reorganize proxies if you move domain elements around and want
to keep your proxies in locations meaningful 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 RequisitePro project.
A proxy package is a special RequisitePro 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 model 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 an domain element. This action does not remove the domain element, the requirement, or any traceability relationships with the requirement.