Architecture, distribution and integration
UML deployment diagram
Nodes, devices and execution environments as 3D boxes, with artifacts deployed on them and communication paths between.
uml.deployment@1New DDN source
Why use it?
Deployment is where architecture meets hardware; the 3D-box idiom keeps it readable.
When it helps
Documenting what runs on which machine or environment.
How to read it
- Boxes inside boxes are nesting: an artifact has exactly one home node.
- Communication paths are structural links, not runtime traffic.
What you need
- The nodes and devices
- The artifacts and their homes
- The paths between nodes
Things to check
- Do not deploy an artifact to two homes without saying which is authoritative.
- Do not draw network traffic as deployment.
Scope of this diagram
UML deployment notation; middleware-specific models and topology discovery are out of scope.
Work with the converted example
- Open the viewer and select
main. Inspect the rendered view and its source. - Open the designer. Keep the selected profile and inspect its legal palette and property controls.
- Change one displayed title or an appropriate data value. Apply the edit and check the resulting diagram.
- Run the verifier and review its diagnostics before moving complete content into review.
- Download your edited DDN source to retain the change.
The example uses the indentation-based ddn-next-1 dialect. The language guide explains reusable definitions, dotted data rows and explicit property blocks.