Package Diagram

Package diagrams depict the organization of model elements into packages and the dependencies amongst them, including package imports and package extensions. They also provide a visualization of the corresponding namespaces.

The following example demonstrates a basic Package diagram.

Example of a Package Diagram

The nesting connector between ConnSeq and Controller reflects what the package contents reveal. Package contents can be listed by clicking on the diagram background to display the diagram's Properties dialog, selecting the Elements tab and selecting the Package Contents checkbox.

The «import» connector indicates that the elements within the target Integer package, which in this example is the single Class Integer, are imported into the package Controller. The Controller's namespace gains access to the Integer Class; the Integer namespace is not affected.

The «merge» connector indicates that the package Controller's elements are imported into GenApply, including Controller's nested and imported contents. If an element already exists within GenApply, such as Loader and Time, these elements' definitions are expanded by those included in the package Controller. All elements added or updated by the merge are noted by a generalization relationship back to that package.

Notes:

  • Private elements within a package cannot be imported or merged.
  • If you click on an element listed in a package, and then double-click, you can display and edit the element properties.

Toolbox Elements and Connectors

Select Package diagram elements and connectors from the Class pages of the Toolbox.

Tip:

Click on the following elements and connectors for more information.

Package Diagram Elements

Package Diagram Connectors

e_Package

c_Associate

e_Class

c_Generalize

e_Interface

c_Compose

e_datatype

c_Aggregate

e_enumeration

c_AssociationClass

e_primitive

c_Assembly

e_Table

c_Realize

e_signal

c_Nesting

c_Association

c_PkgMerge

 

c_PkgImport