Scribd
Upload
18 views

Deployment Diagram 1

The document provides an overview of deployment diagrams including: 1) Deployment diagrams show the physical relationship between hardware and software components in a system using nodes to represent devices and execution environments. 2) They are used to visualize hardware topology, model embedded systems, client-server systems, and distributed applications as well as enable forward and reverse engineering. 3) Nodes communicate through connections that can be bidirectional or unidirectional and may include labels to provide details. Components represent software artifacts deployed on nodes and artifacts are specific implementation files or elements. 4) Deployment relationships illustrate how components and artifacts are deployed on nodes to show the system architecture and runtime environment.

Uploaded by

Dominique Pelaez
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
18 views

Deployment Diagram 1

The document provides an overview of deployment diagrams including: 1) Deployment diagrams show the physical relationship between hardware and software components in a system using nodes to represent devices and execution environments. 2) They are used to visualize hardware topology, model embedded systems, client-server systems, and distributed applications as well as enable forward and reverse engineering. 3) Nodes communicate through connections that can be bidirectional or unidirectional and may include labels to provide details. Components represent software artifacts deployed on nodes and artifacts are specific implementation files or elements. 4) Deployment relationships illustrate how components and artifacts are deployed on nodes to show the system architecture and runtime environment.

Uploaded by

Dominique Pelaez
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 17

GROUP 7

Deployment
diagram
overview
• Show the physical relationship between hardware and software in a
system

• There are two types of nodes:


• Device node (Hardware) – with processing memory and service to
execute software.
• Example : PC, laptop or mobile phone
• Execution Environment Node (Software) – they provide a service to
host and execute and execute other executable software elements.
• Example : Web Server, Application Server, Database Server, Cloud
Platform, Virtual Machine
Purpose & usage
Purpose of Deployment Diagram can be described as:
• Visualize hardware topology of a system.
• Describe the hardware components used to deploy software components
• Describe runtime processing nodes

Usage of Deployment Diagram can be described as:


• To model the hardware topology of a system.
• To model the embedded system.
• To model hardware details for a client/server system.
• To model hardware details of a distributed application.
• Forward and reverse engineering.
Th e N o d e N o t a t i o n

A node is a computational resource, typically containing


memory and processing, on which artifacts are deployed for
execution. Nodes may contain other nodes to represent
complex execution capability; this is shown by nesting or
using a composition relationship. There are two types of
nodes: devices and execution environments
The Node Notation

A device is a piece of hardware that provides


computational capabilities, such as a computer, a
modem, or a sensor. An execution environment is
software that provides for the deployment of
specific types of executing artifacts
The Node Notation
Nodes communicate with one another, via messages
and signals, through a communication path indicated
by a solid line. Communication paths are usually
considered to be bidirectional, although if a particular
connection is unidirectional, an arrow may be added
to show the direction. Each communication path may
include an optional keyword label, such as «http» or
«TCP/IP», that provides information about the
connection. We may also specify multiplicity for each
of the nodes connected via a communication path.
mponents are the software artifacts that run on the nodes of a system. They represent the software modules, services, libraries, or applications that are deployed on a specific hardware or virtual machine. Components are represented as rectangular boxes in the diagram and contain the name of the compo

comp o n e n t s

The components are the software artifacts that run on the


nodes of a system. They represent the software modules,
services, libraries, or applications that are deployed on a
specific hardware or virtual machine. Components are
represented as rectangular boxes in the diagram and contain
the name of the component.
artifact
• Is the specification of a physical piece of information
• Ex: source files, binary executable files, table in a database
system,….
• An artifact defined by the user represents a concrete element
in the physical world
Deployment r e l a t i o n s h i p s

Deployment relationships are used to show how


software components and artifacts are deployed on
nodes in the system architecture. Deployment
relationships illustrate the associations and
dependencies between the different elements of a
system and provide a visual representation of how the
system operates in a runtime environment.
stereotype
Stereotypes are used to add additional information about the
properties or behavior of nodes, components, artifacts, and
deployment relationships. Stereotypes are typically represented
as text labels in guillemets (« ») and are placed above or below
the name of the element they modify.
deployment d
iagram repres
ents the work
of HTML5 vi i ng
deo player in
the browser
deployment d
iagram repres
ents the libra
ry
management
system
Deployme
nt Diagram
of Online
Shopping
System.
Thank You!

You might also like