Skip to main content
← UML

UML Deployment Diagram Lab

UML / DEPLOYMENT / 01

Where does the order system run?

Select a device, runtime, artifact or solid line. Inspect nesting, deployment targets and communication paths.

«device»Client device«device»Gateway host«device»Application host«device»Database host«executionEnvironment»Browser«executionEnvironment»Gateway runtime«executionEnvironment»Application JVM«executionEnvironment»Database engineHTTPSHTTPSQLgateway.conforders.jarpayment-adapter.jarorders-schema.sql
Scroll the diagram on narrow screens or use the text list below.
List of devices, runtimes, artifacts and paths

The file icon marks an artifact. Drawing it inside a node places it on that target, as with the program artifacts inside the application JVM.

A solid line declares a communication path between devices. Labels describe the modeled traffic in this fictional example.

Notation and semantics

The lab checks the required target for each artifact and the declared direct paths between devices. Capacity, live connectivity, protocol behavior and availability require separate verification.

OMG · UML 2.5.1 §§19.2–19.5 ↗
Blank area: ← → chapters · Native keys inside controls01 / 06
Preparing the model