deployment diagrams

1. UNIT I UML DIAGRAMS
Introduction to OOAD – Unified Process –
UML diagrams – Use Case – Class Diagrams–
Interaction Diagrams – State Diagrams –
Activity Diagrams –
Package, component and Deployment Diagrams.

2. Artifact
• An artifact is a product of the software development process.
• Information that is used or produced by a s/w development process or
when operating the system is called as artifact
• That may include
– Process models (e.g. use case models, design models etc),
– Source files, executables, design documents, test reports, prototypes, user
manuals, etc.

3. Deployment Diagram
Visualize the topology of
the physical components of a system
where the software artifacts are deployed.

4. Overview
• Deployment diagram
– Represents the deployment of s/w artifacts to deployment targets (nodes)
• There are two types of Nodes:
1. Device Node
2. Execution Environment Node
• Device nodes are physical computing resources (h/w)
– With processing memory and services to execute software.
– Few Example : PC, laptop, or mobile phone
• An EEN is a software computing resource that runs within an outer node
– They provides a service to host and execute other executable s/w elements.
– Few Example : OS, a JVM, or servlet container.

5. Purpose & usage
• Purpose of deployment diagrams 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 diagrams can be described as follows:
– To model the hardware topology of a system.
– To model embedded system.
– To model hardware details for a client/server system.
– To model hardware details of a distributed application.
– Forward and reverse engineering.

8. Notations
• Node is shown as a 3-dimensional box shape
• EEN can be nested
• An artifact is denoted by a rectangle
– With Artifact name, and document icon
Application Server
Device
Several execution environments
nested into server device

9. Communication path
• A communication path is association b/w two deployment targets,
– Through which they are able to exchange signals and messages.
Communication path b/w several application
servers and database servers.
Gigabit Ethernet as communication path
b/w application and database servers.
when deployment targets are some
physical devices,
communication path will typically
represent a physical connection b/w
the nodes

10. Communication path
• A communication path is association b/w two deployment targets,
– Through which they are able to exchange signals and messages.
TCP/IP protocol as communication path
b/w J2EE server and database system.
When deployment targets
are execution environments,
communication path will typically
represent some protocol.

11. Deployment
• A deployment is a dependency relationship which describes allocation
(deployment) of an artifact to a deployment target.
– Drawn from the artifact (supplier) to deployment target (client)
– It is labeled with «deploy».
• Deployment can be shown with deployed artifacts contained by
a deployment target.
J2EE web application archive portfolio.war
deployed on Apache Tomcat JSP server.

12. Deployment
• Deployment could be shown within a rectangular frame
– With deployment name in a compartment in the upper left corner.
– Diagram heading is deployment and abbreviated form is dep.

13. Example
This example just gives you an idea of
how a deployment looks when using the UML notation.
Devices : A web server, a DB server, and
user's machine where they view the website.
<<execution environment>>
:Browser

14. Example - J2EE Web Servers Load Balancing
A network load balancer is an appliance device that is used to split network load
across multiple servers.
An example shows jetNEXUS ALB-X hardware load balancer.
2 active hardware load balancers
connected to 2 to 4 Sun Fire Servers
Each server has 3
instances of IBM
WebSphere 7 J2EE
application servers
installed