UML deployment diagram
depicts a static view of the run-time configuration of hardware nodes and the
software components that run on those nodes. Deployment diagrams show the hardware for your system, the software that
is installed on that hardware, and the middleware used to connect the disparate
machines to one another. You create
a deployment model to:
- Explore the issues involved with installing your system into production.
- Explore the dependencies that your system has with other systems that are currently
in, or planned for, your production environment.
- Depict a major deployment configuration of a business application.
- Design the hardware and software configuration of an embedded system.
- Depict the hardware/network infrastructure of an organization.
There are guidelines for:
Nodes and Components
and Communication Associations
Figure 1. A project-specific UML
Figure 2. A network diagram
for an organization.
- Indicate Software Components on Project-Specific Diagrams.
1 depicts a UML Deployment diagram for a university administration system.
- Focus on Nodes and Communication Associations on Enterprise-Level
2 is an example a style of UML Deployment diagram often referred to as a
network diagram or technical architecture diagram, depicting the technical
infrastructure of a simple organization.
2is a very simple example, many
organizations would have tens if not hundreds of nodes on such a diagram.
A node, depicted as a three-dimensional box, represents a
computational unit, typically a single piece of hardware, such as a computer,
network router, mainframe, sensor, or personal digital assistant (PDA).
In UML 2 nodes can also be software.
represent software artifacts such as file, framework, or domain component.
- Name Nodes With Descriptive Terms
- Model Only Vital Software Components
- Apply Consistent Stereotypes to Components
- Apply Visual Stereotypes to Nodes
Communication associations, often called connections, are
depicted as lines connecting nodes. Dependencies between components are modeled
as dashed arrows, the same notation used on other UML diagrams.
- Indicate Communication Protocols Via Stereotypes
- Model Only Critical Dependencies Between Components