Profile contract
uml.activity@2
uml.activity@1 plus UML 2.5.1 activity notation: decision/merge distinction, pins with parameter sets and streaming (x_pin on ports), send/accept signal pentagons, time-event hourglass, flow final (⊗), interruptible regions with lightning edges, exception handlers, structured/expansion regions.
graph projectionUML activity diagram
Open this profile in the gallery
Primary palette
Additional context roles
flow.annotationflow.callconversationflow.cardflow.choreotaskflow.collateflow.connectorflow.conversationflow.datainputflow.dataobjectflow.dataoutputflow.datastoreflow.delayflow.displayflow.documentflow.gatewayflow.groupflow.intermediateflow.ioflow.isoextractflow.isomergeflow.loopendflow.loopstartflow.manualinputflow.manualopflow.offpageflow.parallelmodeflow.preparationflow.sortflow.storageflow.subconversationRelationship roles
Legal endpoints
| Relation | Source roles | Target roles | Self relation |
|---|---|---|---|
uml.flow | flow.acceptsignal, flow.choreotask, flow.connector, flow.decision, flow.end, flow.flowfinal, flow.forkjoin, flow.gateway, flow.group, flow.intermediate, flow.io, flow.merge, flow.objectnode, flow.process, flow.sendsignal, flow.start, flow.subprocess, flow.timeevent | flow.acceptsignal, flow.choreotask, flow.connector, flow.decision, flow.end, flow.flowfinal, flow.forkjoin, flow.gateway, flow.group, flow.intermediate, flow.io, flow.merge, flow.objectnode, flow.process, flow.sendsignal, flow.start, flow.subprocess, flow.timeevent | Not allowed |
Profile verification
- Retain flow start/end, reachability and named-decision-branch checks.
- Partition references name declared lanes; fork/join counts balance under the current structural check.
- Activity edges use uml.flow rather than ordinary flow.next.
- Merge fans in at least two and out exactly one.
- Pins belong to permitted action kinds; interrupt/exception edges preserve explicit ownership and marker rules.
- Streaming/typed pin notation does not introduce object-flow type inference, activity execution or collection expansion.
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.activity@2"
}Projection properties
kind, profile, inputs, analysis_budget, traces, iso, depth
Design operations
- Create actions/control nodes; add named lane frames; assign partitions; connect flows and label decisions.
Bounded analysis
Structural verification and display only; no execution or implied process engine.
Outside this profile
- activity execution semantics
- object-flow type checking
- expansion-region collections
- parameter-set boxing (cosmetic grouping)
- formal UML conformance