Create a UML deployment diagram

In a deployment diagram (deployment diagram: An implementation diagram that shows the structure of a run-time system. From it, you can learn about the physical relationships among software and hardware components and the distribution of components to processing nodes.), drag a Node or Node Instance shape from the UML Deployment stencil onto the drawing page.Double-click the node to add a name, attributes, operations and other property values.Drag a corner selection handle to resize the node so it can accommodate the elements you want it to contain. Drag Component, Component Instance, and Object shapes on top of the Node shape, and then connect the shapes with dependency relationships where appropriate.Do one of the following:

Double-click each node. In the UML Node Properties dialog box, click Components. Under Choose the components which are deployed by this node, select the appropriate components, and then click OK. Double-click each component. In the UML Component Properties dialog box, click Nodes. Under Choose the nodes which deploy this component, select the appropriate nodes, and then click OK.

In a static structure (static structure diagram: A diagram that shows the static structure of a model; that is, the elements that exist (such as classes and types), the internal structure of the elements, and their relationships to one another.)component (component: In component and deployment diagrams, a distributable unit of implementation in a system. For example, a component can represent a physical module of code (source, binary, or executable) or a business document in a human system.), or deployment (deployment diagram: An implementation diagram that shows the structure of a run-time system. From it, you can learn about the physical relationships among software and hardware components and the distribution of components to processing nodes.) diagram, drag the lollipop Interface shape onto the drawing page. Glue the endpoint without the circle to a connection point on the class (class: In a static structure diagram, a set of objects with similar structure, behavior, and relationships. Classes are declared in class (static structure) diagrams and represent concepts in the systems being modeled.) component, or other element. Double-click the Interface shape to add a name, operations, and other property values.

You can also represent an interface with a rectangular Interface shape that resembles a class. Use this shape when you want to display a list of the interface operations.

To change the type of shape that displays for an interface, right-click the Interface shape and click Show as Class-like Interface or Show as Lollipop Interface.

In a deployment diagram (deployment diagram: An implementation diagram that shows the structure of a run-time system. From it, you can learn about the physical relationships among software and hardware components and the distribution of components to processing nodes.), drag a Communicates shape from the UML Deployment stencil onto the drawing page. Glue one endpoint of the Communicates shape to a connection point on the first node. Glue the other endpoint of the Communicates shape to a connection point on the second node. Double-click the Communicates shape to add a name and other property values to the element and to its ends.

Drag a Dependency shape from the UML Static Structure, UML Deployment, or UML Component stencil onto the drawing page and place it near the elements you want to relate. Glue the endpoint with an arrowhead to a connection point on the element the other element depends on. Glue the endpoint without an arrowhead to a connection point on the element that depends on the other element. Double-click the dependency to add a name, stereotype (stereotypes: A representation of a usage distinction. A stereotype is a subclass of an existing element with the same attributes and relationships as that element but with a different intent and possibly additional constraints.), and other properties.

 Tip   If you want to indicate a trace (trace: A kind of dependency that indicates a historical relationship between two elements that represent the same concept at different semantic levels or from different points of view.), refinement (refinement: A kind of dependency that indicates a historical or derivation relationship between two elements with a mapping between them. A description of the mapping may be attached to the dependency in a note.), usage (usage: A kind of dependency that indicates that one element requires the presence of another element for its correct implementation or functioning.), or binding (binding: A kind of dependency that indicates a binding of parameterized class, or template, parameters to actual values to create a bound, or nonparameterized, element.) dependency, you can use the Trace, Refinement, Usage, or Binding shapes from the UML Static Structure stencil.