UML Behavioral & Structural Projections

EdgeNode projects its unified data core into the Unified Modeling Language (UML) diagram suite. UML is the only standard within the EdgeNode ecosystem that spans both data projections: deriving dynamic artifact lifecycles (UML State) and role interactions (UML Sequence) from computable plans, while compiling domain hierarchies and type inheritance (UML Class) from semantic digital twins.

UML Projection Matrix

Part I: UML State Diagram (Artifact Lifecycles)

The UML State projection focuses on state space rather than node topology. In this projection, the graph is inverted: database cycle records become transition arrows, while state sentinels and intermediate states become state vertices.

1. The State-Node Inversion Principle

• State Vertices (artifact::state): Extracted from Origin state and Target state.
• Transitions (Cycle Arrows): Each operational cycle generates a solid transition arrow connecting its Origin state to its Target state.
• Transition Effects: The arrow is annotated with / <cycle name> [<duration>], designating the activity as an execution effect rather than a static state box.

2. Orthogonal Regions & Signal Triggers

• Concurrent Regions: Each distinct artifact stream is rendered as an isolated, dashed Orthogonal Region (region: <artifact>).
• Asynchronous Signals (<<signal>>): When a cycle triggers dependent streams via Plan pipelines, the compiler emits a dashed <<signal>> arrow originating from the triggering cycle's target state to the (entry) pseudostate of the concerned artifact stream.

Part II: UML Sequence Diagram (Role Interactions)

The UML Sequence projection transforms the computable plan into an execution chronology. Lifelines represent operational roles, and message vectors trace state-continuous handoffs.

1. Effective Role Resolution

Each lifeline represents an active execution role («Participant» <role>). If a cycle lacks an explicit responsible, the compiler resolves ownership hierarchically:

1. Direct Ownership

Uses Responsible mapped to roles.

2. Hierarchical Inheritance

Inherits the Responsible of the enclosing parent node via parent.

3. Fallback Classification

Defaults to the artifact name for root cycles without roles, or generic "Operator".

2. Chronological Timeline Traversal

The timeline engine traverses state-continuous execution paths from (entry) to (exit):

1. Handoff Messages: A transition from cycle $A$ to cycle $B$ renders as a solid horizontal arrow from $\text{Role}(A)$ to $\text{Role}(B)$, labeled with the operation name and cycle duration: step: execute [duration].
2. Trigger Spawns: Pipeline triggers produce dashed asynchronous messages directed to the owner of the spawned stream's entry state: step: «trigger» spawn <artifact> [<initial state>].
3. Subprocess Scoping: Hierarchical child cycles are abstracted into [subprocess] activation markers on the lifeline, expandable via scoped sub-views.

Part III: UML Class Diagram (Domain Model & Ontology)

The UML Class projection translates the digital twin's structural ontology into an object-oriented domain model with package containment, synthesized members, and typed relationships.

1. Package Containment & Stereotypes

• Package Nesting: Every parent node parent is rendered as a uml package container. Child nodes are encapsulated directly inside their parent package box.
• Stereotype Taxonomy: Leaf nodes are assigned standard stereotypes based on their resolved definition type:

2. Synthesized Class Compartments

Each UML class box exposes standard 3-compartment structure. Attributes and operations are synthesized from underlying twin metrics:

+---------------------------------------------------+
| «Service»                                         |
| OrderExecutionEngine                              |
+---------------------------------------------------+
| - laborCost: $1,420.00                            |
| - assetCost: $850.00                              |
| - assetVolume: 12                                 |
| - entropy: 0.1420                                 |
+---------------------------------------------------+
| + execute(duration: 02:30:00)                     |
| + oversee(role: OperationsLead)                   |
+---------------------------------------------------+

3. Relationship Typology

Semantic relationships map onto standard UML associations, dependencies, generalizations, and compositions:

Comparison of UML Projections