The following table describes the elements that you can add to Deployment diagrams. The elements are grouped by Modeling Palette section.
Element | Icon | Description |
---|---|---|
Basic Section | ||
Component | ![]() |
A physical and replaceable part of a system that conforms to and provides the realization of a set of interfaces. |
Interface | ![]() |
A stereotype of class offering only public operations, but no attributes or method bodies. |
Package | ![]() |
A grouping of class definitions. |
Artifact | ![]() |
A physical piece of information that is used or produced by a software development process, may include models, source files, scripts, and binary executables. |
Node | ![]() |
A classifier that represents a run-time computational resource, which generally has at least a memory and often processing capability. |
Deployment Specification | ![]() |
A set of properties which determine execution parameters of a element artifact that is deployed on a node. |
Generalization | ![]() |
The relationship between a subtype element and a supertype element. The elements in this relationship must possess the same attributes. For example, the subtype Manager and the supertype Employee share a generalization relationship. |
Implementation | ![]() |
An implementation relationship between two elements. |
Association | ![]() |
An association relationship between two elements. |
Dependencies Section | ||
Dependency | ![]() |
The relationship between two elements whose definitions depend on one another in such a way that changes to one can result in changes to the other. For example, when one class mentions another as an operation parameter, or as part of its data, the two classes exhibit dependency. |
Realize | ![]() |
A semantic relationship between classifiers. One classifier specifies a contract that another classifier guarantees to carry out. These relationships are used in two places: between interfaces and the classes that realize them, and between use cases and the collaboration that realize them. |
Usage | ![]() |
A dependency in which one element (the client) requires the presence of another element (the supplier) for its correct functioning or implementation. |
Permission | ![]() |
A dependency that signifies granting of access rights from the supplier model element to a client model element, in which the client requires access to some or all of the constituent elements of the supplier. |
Abstraction | ![]() |
A boundary relative to the perspective of the viewer. The essential characteristics of an entity that distinguish it from all other kinds of entities. |
Comments Section | ||
Comment | ![]() |
A Notepad notation. Use Comments to record information for a element or link in a diagram. This information is not included in generated code but is for information only. Each Comment can contain unlimited text, and be numbered. You can also define a stereotype, and enter a noted element. |
Link Comment | ![]() |
The connection between the comment element and the associated element. |