DEPLOYMENT

DIAGRAM
Muhammad Fikry
Deployment Diagram
 A deployment diagram models the physical
deployment of artifacts on nodes.
 To describe a web site, for example, a
deployment diagram would show what
hardware components ("nodes") exist (e.g., a
web server, an application server, and a
database server), what software components
("artifacts") run on each node (e.g., web
application, database), and how the
different pieces are connected (e.g. JDBC,
REST, RMI).
Purpose
 Visualize
hardware topology of a system.
 Describe the hardware components used
to deploy software components.
 Describe runtime processing nodes.
Node
 The nodes appear as boxes, and the
artifacts allocated to each node appear
as rectangles within the boxes.
 Nodes may have subnodes, which
appear as nested boxes.
 A single node in a deployment diagram
may conceptually represent multiple
physical nodes, such as a cluster of
database servers.
Type of Node
 Device Node
 Device nodes are physically computing resources with
processing memory and services to execute software,
such as typical computer or mobile phones.
 Execution Environment Node
 An execution environment node is a software
computing resource that runs within an outer node and
which itself provides a service to host and execute other
executable software elements.
 An execution environment represents software
containers (such as operating systems, JVM, servlet/EJB
containers, application servers, portal servers etc.)
Usage
 When modeling devices, it is possible to
model them in several different ways:
 Using the type and make, for instance "IBM
RS6000", "HP 9000".
 Using its intended function, for instance
"Database Server", "High Speed Switch"
 Using the operating system deployed on it, for
instance "Linux Server", "Solaris Server".
 Use tagged values to specify characteristics
of devices / execution environments, for
instance "Memory=2GB", "Disk Space=32GB",
"Version=2.5.1".
Artifact
 Stereotypes that apply to artifacts
 <<file>>
 <<source>>
 <<executable>>
 <<document>>
 <<library>>
 <<script>>