Packages (RQM)

You can divide your requirements model into packages in order to avoid manipulating the entire set of requirements and to provide views on particular logical subsets of the requirements. You could create packages to represent different tasks, domains, or subject areas.

In the following example, one package contains functional requirements and the other contains non-functional requirements:

You can create packages as peers and divide packages into subpackages as necessary. Each package has its own default requirements view (document, traceability or user allocation view) and you can create others if required.

In a requirements model, packages only appear in the Browser tree view. To add requirements to a package, you can:

Create requirements directly in the package document view(s).
In the Browser, select requirements from the model Requirements folder, and drag and drop them onto the package or one of its sub-requirements.

You can link requirements in different packages of the same model together from the Requirement Traceability Links tab of the requirements property sheet (see Linking Requirements with Design Objects and External Files).

Creating a Package
You can create a package in a requirements document view, or from the Browser or Model menu.
Package Properties
To view or edit a package's properties, double-click its diagram symbol or Browser or list entry. The property sheet tabs and fields listed here are those available by default, before any customization of the interface by you or an administrator.

Parent topic: Requirements Views