Package diagrams are most commonly found used in: Essentially, the content of two packages are combined to produce a new package.Īs we’ve shown earlier in this guide, packages are UML constructs that can be used to organize the elements within any UML classifier in a variety of UML diagrams. Package merge: A directed relationship in which the contents of one package are extended by the contents of another.This type of directed relationship adds the names of the members of the imported package to its own namespace Package import: A directed relationship between and importing namespace and an imported package.
This is used to import select individual elements without resorting to a package import and without making it public within the namespace. Element import: A directed relationship between an importing namespace and an imported packageable element.Dependencies are divided into two groups: access and import dependencies. Dependencies: A visual representation of how one element (or set of elements) depends on or influences another.Packageable elements can also be rendered as a rectangle within a package, labeled with the appropriate name. These can include events, components, use cases, and packages themselves. Packageable element: A named element, possibly owned directly by a package.Each element contained within the package should be a packageable element and have a unique name. Package: A namespace used to group together logically related elements within a system.Here are the basic components you’ll find within a package diagram: These symbols can be used in a variety of ways to represent different iterations of packages, dependencies, and other elements within a system. Depicts the relationship between one element (package, named element, etc) and another