Deployment Diagram
Deployment Diagram
Deployment Diagram
The deployment diagram is mostly employed by network engineers, system administrators, etc. with the purpose of
representing the deployment of software on the hardware system. It envisions the interaction of the software with the hardware
to accomplish the execution. The selected hardware must be of good quality so that the software can work more efficiently at a
faster rate by producing accurate results in no time.
The software applications are quite complex these days, as they are standalone, distributed, web-based, etc. So, it is very
necessary to design efficient software.
Deployment diagrams can be used for the followings:
1. To model the network and hardware topology of a system.
2. To model the distributed networks and systems.
3. Implement forwarding and reverse engineering processes.
4. To model the hardware details for a client/server system.
5. For modelling the embedded system.
Deployment diagrams are typically used to visualize the physical hardware and software of a system. Using it you can
understand how the system will be physically deployed on the hardware.
Deployment diagrams help model the hardware topology of a system compared to other UML diagram types which mostly
outline the logical components of a system.
In order to draw a deployment diagram, you need to first become familiar with the following deployment diagram notations and
deployment diagram elements.
Nodes
A node, represented as a cube, is a physical entity that executes one or more components, subsystems or executables. A node
could be a hardware or software element.
Artifacts
Artifacts are concrete elements that are caused by a development process. Examples of artifacts are libraries, archives,
configuration files, executable files etc.
Communication Association
This is represented by a solid line between two nodes. It shows the path of communication between nodes.
Devices
A device is a node that is used to represent a physical computational resource in a system. An example of a device is an
application server.
Deployment Specifications
Deployment specifications is a configuration file, such as a text file or an XML document. It describes how an artifact is
deployed on a node.
How to Draw a Deployment Diagram
Step 1: Identify the purpose of your deployment diagram. And to do so, you need to identify the nodes and devices within the
system you’ll be visualizing with the diagram.
Step 2: Figure out the relationships between the nodes and devices. Once you know how they are connected, proceed to add
the communication associations to the diagram.
Step 3: Identify what other elements like components, active objects you need to add to complete the diagram.
Step 4: Add dependencies between components and objects as required.
Artifact: A product developed by the software, symbolized by a rectangle with the name and the word “artifact” enclosed by
double arrows.
Association: A line that indicates a message or other type of communication between nodes.
Component: A rectangle with two tabs that indicates a software element.
Dependency: A dashed line that ends in an arrow, which indicates that one node or component is dependent on another.
Interface: A circle that indicates a contractual relationship. Those objects that realize the interface must complete some sort
of obligation.
Node: A hardware or software object, shown by a three-dimensional box.
Node as container: A node that contains another node inside of it—such as in the example below, where the nodes contain
components.
Stereotype: A device contained within the node, presented at the top of the node, with the name bracketed by double
arrows.
Nodes
There are two types of nodes in a deployment diagram: device nodes and
execution environment nodes. Device nodes are computing resources with
processing capabilities and the ability to execute programs. Some examples of
device nodes include PCs, laptops, and mobile phones.
Other shapes