| Prev | Next |
Deployment Diagram
A Deployment diagram shows how and where the system is to be deployed; that is, its execution architecture.
Hardware devices, processors and software execution environments (system Artifacts) are reflected as Nodes, and the internal construction can be depicted by embedding or nesting Nodes. Deployment relationships indicate the deployment of Artifacts, and Manifest relationships reveal the physical implementation of Components. As Artifacts are allocated to Nodes to model the system's deployment, the allocation is guided by the use of Deployment Specifications. A Deployment diagram can also indicate that a Node has a State, or show an instance of a Node with an actual run-time value for the state, representing a specific condition or scenario.
You generate Deployment diagram elements and connectors from the 'Deployment' pages of the Diagram Toolbox.
Example Diagram
This is a simple Deployment diagram, representing the arrangement of servers at a head office. The elements are instances of Nodes and show specific run-time states.
The servers are represented by Nodes linked by either simple or aggregate Association relationships.
Deployment diagrams are ideal for applying alternative images to depict the objects that the elements represent. Such images can be substituted for the elements in the diagram, as shown here:
Deployment Diagram Element Toolbox Icons
Icon |
Description |
See also |
|---|---|---|
|
A Node is a physical piece of equipment on which the system is deployed, such as a workgroup server or workstation. |
Node |
|
A Device is a physical electronic resource with processing capability upon which Artifacts can be deployed for execution, as represented in a Deployment diagram. |
Device |
|
An Execution Environment is a node that offers an execution environment for specific types of component that are deployed on it in the form of Executable Artifacts. |
Execution Environment |
|
A Component is a modular part of a system, whose behavior is defined by its provided and required interfaces. |
Component |
|
An Interface is a specification of behavior (or contract) that implementers agree to meet. |
Interface |
|
An Artifact is any physical piece of information used or produced by a system. |
Artifact |
|
A Deployment Specification (spec) specifies parameters guiding deployment of an artifact, as is necessary with most hardware and software technologies. |
Deployment Specification |
Deployment Diagram Connector Toolbox Icons
Icon |
Description |
See also |
|---|---|---|
|
An Association implies that two model elements have a relationship, usually implemented as an instance variable in one or both Classes. |
Association |
|
A Communication Path defines the path through which two DeploymentTargets are able to exchange signals and messages. |
Communication Path |
|
An Association Class is a UML construct that enables an Association to have attributes and operations (features). |
Association Class |
|
A Generalization is used to indicate inheritance. |
Generalization |
|
A source object implements or Realizes its destination object. |
Realization |
|
A Deployment is a type of Dependency relationship that indicates the deployment of an artifact onto a node or executable target, typically in a Deployment diagram. |
Deployment |
|
A Manifest relationship indicates that the Artifact source embodies the target model element, typically in Component and Deployment diagrams. |
Manifest |