You can create a requirement from
a domain element. By default, this creates an association between
the domain element and the new requirement.
This capability is configured
in the Requirement Creation Policy in the
Rational® RequisitePro® project
properties. All domain element kinds are configured by default to
create a requirement of a type that is based on the element kind;
for example, a folder in the Resource linkable domain creates a requirement
of the type FOLDER. The only exception is the UML use case, which
is configured by default to create a requirement of the use-case requirement
type with a UC tag prefix. The Requirement Creation Policy also has
a default setting that links the associated artifacts after the requirement
is created. You can modify this policy to create different relationships
in your integration.
To create requirements from domain elements:
- Right-click a domain element in the Project Explorer view
or a diagram and click . The domain element is displayed in the Link
Clipboard view.
- Right-click a package in the Requirements Explorer view
and click Create Requirement from element name. This creates an associated requirement in the package.
The type of requirement that is created is determined by the
properties on the Requirement Creation Policy page
in the Project Properties window. The association
is direct or indirect, depending on the properties on the Link Policy
page in the Project Properties window.
As an alternative to using
the menu items as previously described, you can create the requirement
by dragging a domain element from the Project Explorer view
to a package in the Requirement Explorer view.
For some domains, you cannot create requirements by dragging elements
to the Requirement Explorer view; for those domains,
use the menu commands described in this procedure.