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 'Package' pages of the Diagram Toolbox.

Example Diagram

This example illustrates a basic Package diagram.

Package Diagram Element Toolbox Icons

Icon	Description	See also
	Packages are used to organize your project contents, but when added onto a diagram they can be used to depict the structure and relationships of your model.	Package
	Generates a Profile Package that has the stereotype «profile» in the Package diagram in your technical development model. A Profile Package is used in defining new types of structure in a model.	Create a Profile Package
	Generates a Model Package with the stereotype «model», to represent the parent node in a model structure.

Package Diagram Relationship Toolbox Icons

Connector	Description	See also
	The Nesting Connector is an alternative graphical notation for expressing containment or nesting of elements within other elements. The Nesting connector between ConnSeq and Controller reflects what the Package contents reveal. The 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 in the 'Show Compartments' panel.	Nesting Diagram Properties
	In a Package diagram, a Package Merge indicates a relationship between two Packages whereby the contents of the target Package have been merged with those of the source Package. In the example diagram, the «merge» connector indicates that the Controller Package's elements have been 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 Merge
	A Package Import relationship is drawn from a source Package to a Package whose contents have been imported. The «import» connector indicates that the elements within the target Integer Package, which in this example is the single Class Integer, have been imported into the Package Controller. The Controller's namespace gains access to the Integer Class; the Integer namespace is not affected.	Package Import
	A Profile Application relationship indicates that the source Profile has been applied to the target Package.

UML Standard Profile Toolbox Icons

Icon	Description	See also
	Generates a Model Package with the stereotype «framework», to represent the parent node in framework structure.
	Generates a Model Package with the stereotype «metamodel», to represent the parent node in metamodel structure.
	Generates a Model Package with the stereotype «modelLibrary», to represent the parent node in model library structure.
	Generates a Model Package with the stereotype «systemModel», to represent the parent node in system model structure.