Profile contract
uml.deployment@1
UML 2.5.1 deployment diagrams: nodes/devices/execution environments (3D-box), artifacts (document icon), deploy/manifest dependencies, communication paths with multiplicity, node nesting via frames, deployed components.
graph projectionUML deployment diagram
Open this profile in the gallery
Primary palette
Relationship roles
Legal endpoints
| Relation | Source roles | Target roles | Self relation |
|---|---|---|---|
uml.commpath | uml.device, uml.executionenv, uml.node | uml.device, uml.executionenv, uml.node | Not allowed |
uml.dependency | uml.component | uml.component | Not allowed |
uml.deploy | uml.artifact, uml.component, uml.device, uml.executionenv, uml.node | uml.device, uml.executionenv, uml.node | Not allowed |
uml.manifest | uml.artifact | uml.artifact, uml.component | Not allowed |
Profile verification
- Deployment and manifestation have different registered endpoint directions.
- Communication-path ends may carry multiplicity/roles but no qualifiers.
- Nesting frames scope to node/device/execution-environment elements; preserve 3D node and artifact document glyphs.
Profile defaults
Explicit file settings override eligible CSS, then these profile defaults and the common standard apply. Unspecified semantic facts remain unspecified.
{
"projection.kind": "graph",
"projection.profile": "uml.deployment@1"
}Projection properties
kind, profile, inputs, analysis_budget, traces, iso, depth
Design operations
- Create node/device/environment/artifact; place scoped frames; connect deploy, manifest and communication paths.
Bounded analysis
Structural verification and display only; no execution or implied process engine.
Outside this profile
- middleware-specific deployment models
- artifact content descriptors
- topology discovery
- communication-path protocol vocabulary
- formal UML conformance