UML Deviations
This article details the structural and operational deviations where Logiop Studio purposefully differs from standard UML and PSSM semantics.
Deviations
Deviation ID
Description
Affected Elements
UMD1001
UML Deviation
Unlike standard UML 2.5.1 where a State Machine strictly owns one or more explicit Region containers at its root level, Logiop Studio State Machines host Vertices and Transitions directly on the top-level canvas without an explicit Region wrapper.
State Machine
UMD1002
UML Deviation
In UML, a Submachine defines top-level Vertices directly on its canvas. Logiop Studio requires a Submachine to enclose all internal modeling elements within a single top-level Composite State container.
Submachine
UMD1003
UML Deviation
In UML, a Submachine State Machine maintains its own encapsulated namespace and behavior definitions. In Logiop Studio, Submachines inherit the Behavior repository of their root State Machine, ensuring a unified catalog for Events, Actions, DoActivities, and Guards across the entire hierarchy.
Submachine
State Machine
UMD1004
UML Deviation
Standard UML allows a Submachine State to defer Events directly. In Logiop Studio, a Submachine State cannot defer Events directly; Event deferrals are instead defined on the top-level composite State of the Submachine definition.
Submachine
State Machine