Using Deployment Diagrams in UML 1.4


In This Chapter

  • Defining the Deployment diagram
  • Defining and modeling nodes and node properties
  • Defining and modeling node associations
  • Modeling component containment
  • Defining and modeling node and component instances
  • Defining the «become» and «deploy» stereotypes


A Deployment diagram describes an execution architecture, that is, the configuration of hardware and software that defines how the system will be set up and how it will operate. The purpose of a Deployment diagram is to present a static view, or snapshot, of the implementation environment. A complete description of the system will likely contain a number of different Deployment diagrams, each focused on a different aspect of system management. For many of these views the Deployment diagram is combined with the Component diagram to show the relationship between the hardware and the software. For example,

  • For a multi-tiered application, the Deployment diagram would model the distribution of the application layers, their physical connections, and their logical paths of communication.
  • Another diagram might focus on how software components are distributed across the network resources, such as where the source code resides and where it is shipped for implementation.
  • Another ...

Get UML™ Bible now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.