Object Oriented Systems Presentation

Deployment Diagram

By:
Anshal Anand
Chaitanya Reddy
Hardika Narula
Paranjay Naik
Shashank Siddarth
What is a Deployment Diagram?

Deployment diagrams are one of the four diagrams in the Unified

Modelling Language (UML) for modelling the static aspects of
systems. Deployment diagrams are one of the 2 kinds of diagrams
used in modeling the physical aspects of an object-oriented system. A
deployment diagram shows the configuration of run time processing
nodes and the components that live on them.

We use deployment diagram to model the static deployment view of a

system. For the most part, this involves modeling the topology of the
hardware on which your system executes. Deployment diagrams are
essentially class diagrams that focus on a system’s nodes.

The deployment diagram shows how a system will be physically

deployed in the hardware environment. Its purpose is to show where
the different components of the system will physically run and how
they will communicate with each other. Since the diagram models the
physical runtime, a system's production staff will make considerable
use of this diagram.
Deployment diagrams are not only important for visualizing,
specifying, and documenting embedded, client/server, and distributed
systems, but also for managing executable systems through forward
and reverse engineering.

A Deployment Diagram
ELEMENTS OF A DEPLOYMENT
DIAGRAM:

A Deployment diagram is just a special kind of diagram and shares

the common properties as all other diagrams-a name and graphical
contents that are a projection into a model. What distinguishes a
deployment diagram from all other kinds of diagrams is its particular
content. There are two primary elements of a deployment diagram:
 Nodes
 Dependency and association relationships

Nodes
Nodes, just like components, live in the material world and are an
important building block in modeling the physical aspects of a
system. A node is a physical element that exists at run time and
represents a computational resource, generally having at least some
memory and, often, processing capability.
You use nodes to model the topology of the hardware on which your
system executes. A node typically represents a processor or a device
on which components may be deployed. Graphically, a node is
represented as a cube. Every node must have a name that
distinguishes if from other nodes.
Simple Nodes

Relationships
The most common kind of relationship you’ll use among nodes is a
association represents a physical connection among nodes. You can
even use associations to model indirect connections.The figure below
shows an ethernett connection, a serial line, 0r a shared bus between
server and host.
Because nodes are class-like, you have full power of associations at
your disposal. This means you include roles,multiplicity and
constraints.

Difference between Nodes and Components

In many ways, nodes are a lot like components. However, there
are some significant differences between nodes and components.
 Components are thing that participate in the execution of a
system; nodes are things that execute components.
 Components represent the physical packaging of otherwise
logical elements; nodes represent the physical deployment
of components.

Nodes and Components