Tags and keywords
This content has been marked as discussing an ADVANCED topic!
Before we inspect Activity
IdentifyAcquireAttachPhysical in detail, it helps to inspect some of the 'effect' Activities used by the StateMachine Transitions shown in: 22: Mini StateMachines for @Entity, PotentialPhysicalAsset, ActualPhysicalAsset.
The case of the 'effect' Activity
manifest()Transition to state
Existsis interesting w.r.t. this Webel Best Practice policy:
Webel Best Practice: UML/SysML: If you have a Boolean "state flag" attribute corresponding to a State you MUST set it on an 'entry' of the State, not on the 'effect' of a Transition into the State (otherwise with multiple incoming Transitions it could be WET and breaks SSoT).It represents in fact a «physical»
PhysicalEntitybecoming "real". At the time it reads itself the
PhysicalEntitymust still be in the state
Phantom; by the end of the Activity in the real world it "exists" (and indeed now has mass), but the Boolean state flag
isExistsdoes not get set to 'true' until we hit the 'entry' Activity of the state
Exists(which is a simple OpaqueExpression