RequisitePro project properties reference

The project properties determine the behavior of the Rational® RequisitePro® integration with supported Rational Software Development Platform products. These settings include policies for drag-and-drop behavior, domain element creation, linking, requirement creation, and synchronization of domain elements and requirements. The default settings are suitable for typical use of the integration; however, you can refine the integration through these optional controls.
To access RequisitePro project properties, right-click a project icon in the Requirement Explorer view, and then click Properties. The Properties window contains the following pages:
Property Page Description
Drag and Drop Policy Specify the results of dragging a requirement to a container, such as a package, in the Project Explorer view. The alternatives include creating a new domain element within the container, which is then linked to the requirement, or creating a link between the requirement and the container itself. The link to the new element or the package can be either a direct association or an indirect association that uses a proxy requirement and traceability; this linking behavior is determined by the settings on the Link Policy page of this window.
Element Creation Policy Specify a domain element kind to correspond to each requirement type. This determines the kind of element that results when you create an element from a requirement. Also, set or clear the option to automatically link the requirement to the domain element after it is created.
Link Policy Specify whether or not a proxy requirement is used when associating requirements and domain elements and if so, which requirement type is used for the proxy requirement. By default in the UML domain, use-case requirements and use-case elements have direct associations and therefore do not use a proxy requirement. Conceptually, you can consider a direct (no proxy) association as a link between two artifacts that represent a single item. Proxy requirements are used to link two dissimilar (but related) items, such as a feature requirement and a class domain element.

To create a new proxy relationship, click the Add button to open the Add Link Policy window. On the Link Policy page, move the wildcard (*) selection to the bottom of the list, because it is the most general policy for any requirement/element pair that is not specifically addressed in your list of policies.

Requirement Creation Policy Specify a requirement type to correspond to each domain element kind. This determines the type of requirement that results when you create a requirement from an element. Also, set or clear the option to automatically link the element to the requirement after it is created.
Synchronization Policy Specify the behavior that results when a mismatch exists between the name and text of a requirement and the name and documentation text of a domain element in a direct association. The Requirement Wins and Element Wins synchronization policies cause the name and text of one artifact to overwrite the name and text of the associated artifact. The None policy exempts the association from synchronization. The Prompt policy displays options that enable the user to select which name and text to use in the synchronization.
Related concepts
Requirement projects
Requirement concepts and artifacts
Requirement synchronization
Related tasks
Opening requirement projects
Customizing the integration project properties

Feedback