Deployment diagram

Models the physical deployment of artifacts on nodes

A sample deployment diagram UML diagram types

Structural UML diagrams

* Class diagram
* Component diagram
* Composite structure diagram
* Deployment diagram
* Object diagram
* Package diagram
* Profile diagram

Behavioral UML diagrams

* Activity diagram
* Communication diagram
* Interaction overview diagram
* Sequence diagram
* State diagram
* Timing diagram
* Use case diagram

* v
* t
* e

A deployment diagram[1] "specifies constructs that can be used to define the execution architecture of systems and the assignment of  software artifacts to system elements."[1] 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).

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.

There are two types of Nodes:

1. Device Node
2. Execution Environment Node

Device nodes are physical computing resources with processing memory and services to execute software, such as typical computers or mobile phones. An execution environment node (EEN) 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.

## References

[edit]

1. ^ a b "Deployments". Unified Modeling Language 2.5.2. OMG Document Number formal/2017-12-05. Object Management Group Standards Development Organization (OMG SDO). December 2017. p. 653.

## External links

[edit]

Wikimedia Commons has media related to Deployment diagrams.

* Introduction to UML 2 Deployment Diagrams by Scott W. Ambler
* UML 2 Deployment Diagram
* UML Deployment Diagrams

* v
* t
* e

Unified Modeling Language

Actors|

* Organizations
* Object Management Group
* UML Partners
* Persons
* Grady Booch
* Ivar Jacobson
* James Rumbaugh

Concepts|

| Object oriented|

* Object-oriented programming
* Object-oriented analysis and design
* Object-oriented modeling

|

Structure|

* Actor
* Attribute
* Artifact
* Class
* Component
* Interface
* Object
* Package
* Profile diagram

Behavior|

* Activity
* Event
* Message
* Method
* State
* Use case

Relationships|

* Association
* Composition
* Dependency
* Generalization (or Inheritance)

Extensibility|

* Profile
* Stereotype

Other|

* Multiplicity

Diagrams|

| Structure|

* Class
* Component
* Composite structure
* Deployment
* Object
* Package

|

Behaviour|

* Activity
* State Machine
* Use case

Interaction|

* Communications
* Sequence
* Interaction overview
* Timing

Derived languages|

* Systems Modeling Language (SysML)
* UML eXchange Format (UXF)
* XML Metadata Interchange (XMI)
* Executable UML (xUML)

Other topics|

* Glossary of UML terms
* Rational Unified Process
* List of Unified Modeling Language tools
* Object Modeling in Color

This Unified Modeling Language article is a stub. You can help Wikipedia by expanding it.

|

* v
* t
* e

*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template