Packages (RQM)

You can split the model into smaller subdivisions to avoid manipulating the entire set of model objects. Packages can be useful to assign portions of a model, representing different tasks and subject areas, to different development teams.

In the following example, a package contains functional requirements and another package contains non-functional requirements.

You can create several packages at the same level within an RQM and add sub-packages to packages 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 Traceability Links tab of the requirements property sheet (see Linking Requirements with Design Objects and External Files).

For more information on packages, see "Packages" in Chapter 3, Models of the Core Features Guide .

Requirements Package Properties
You can modify a package's properties from its property sheet. To open a package property sheet, double-click its Browser entry. The following sections detail the property sheet tabs that contain the properties most commonly entered for RQM packages.

Parent topic: Getting Started with Requirements Modeling