A package is a piece of a model.
When working with a large model, 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.
Package Hierarchy
You can create several packages at the same hierarchical level within a model, or decompose a package into other packages, and continue this process without limitation in decomposition depth. Each package is displayed with a default requirements view (document, traceability or user allocation view). At each level of decomposition, you can create several requirements views.
To display a package view, you must double-click its name or icon in the Browser tree view.
For more information on packages, see "Packages" in the Models chapter of the Core Features Guide.
Package Requirements
In a requirements model, packages only appear in the Browser tree view. To add requirements to a package, you can:
-
Create requirements directly from the package document view(s)
-
In the Browser, select requirements from the model Requirements folder, and drag and drop them either in the package document view(s) or beneath the package Requirements folder (for root requirements), or beneath other requirements (for child requirements)
You can link requirements from different packages of the same model. Use the Add Links to Other Requirements tool, in the Traceability Links tab of the requirements property sheet.