Package diagrams reflect the organization of packages and their elements, and provide a visualization of their corresponding namespaces. 

The following example demonstrates a basic 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.

Note: Private elements within a package cannot be imported or merged. 

Toolbox Elements and Connectors

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

Tip: Click on the elements and connectors below for more information.

OMG UML Specification

The OMG UML specification (UML Superstructure Specification, v2.0, p. 12) states:

"A diagram that depicts how model elements are organized into packages and the dependencies among them, including package imports and package extensions."