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.

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

Example Diagram

This example illustrates a basic Package diagram.




See also

Nesting connector

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.

Set Diagram Properties

«import» connector

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.

«merge» connector

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.

Package Diagram Connector Toolbox Items



See also

An Association implies that two model elements have a relationship, usually implemented as an instance variable in one or both Classes.


A Generalization is used to indicate inheritance.


A Composition is used to depict an element that is made up of smaller components, typically in a Class or Package diagram.


An Aggregation connector is a type of association that shows that an element contains or is composed of other elements.


An Association Class is a UML construct that enables an Association to have attributes and operations (features).

Association Class

An Assembly connector bridges a component's required interface (Component1) with the provided interface of another component (Component2), typically in a Component diagram.


A source object implements or Realizes its destination object.


You create a Template Binding connector between a binding Class and a parameterized Class.

Template Binding

The Nesting Connector is an alternative graphical notation for expressing containment or nesting of elements within other elements.


In a Package diagram, a Package Merge indicates a relationship between two Packages whereby the contents of the target Package are merged with those of the source Package.

Package Merge

A Package Import relationship is drawn from a source Package to a Package whose contents are to be imported.

Package Import

An Abstraction is a relationship between two elements that represent the same concept, either at different levels of abstraction or from different viewpoints.


A Substitution is a relationship between two Classifiers, signifying that the substituting Classifier complies with the contract specified by the contract Classifier.


A Usage is a Class diagram relationship in which one element requires another element for its full implementation or operation.


Package Diagram Element Toolbox Items



See also

Packages are used to organize your project contents, but when added onto a diagram they can be use for structural or relational depictions.


A Class is a representation of a type of object that reflects the structure and behavior of such objects within the system.


An Interface is a specification of behavior (or contract) that implementers agree to meet.


A Data Type is a specific kind of classifier, similar to a Class except that a Data Type cannot own sub Data Types, and instances of a Data Type are identified only by their value.

Data Type

An Enumeration is a data type, whose instances can be any of a number of user-defined enumeration literals.


A Primitive element identifies a predefined data type, without any relevant substructure (that is, it has no parts in the context of UML).


A Table is a stereotyped Class typically used in Data Modeling.


A Signal is a specification of Send request instances communicated between objects, typically in a Class or Package diagram.


An n-Ary A ssociation element is used to model complex relationships between three or more elements, typically in a Class diagram.