-
Notifications
You must be signed in to change notification settings - Fork 3
R504
Real State entry executes exactly one State Activity
State Activity is executed on transition into exactly one Real State
Each Real State defines a single State Activity that is executed when an instance follows a Transition into the state. That activity may or may not define any Actions. So the net result of executing a State Activity will be to simply wait if no Actions are specified.
A State Activity is defined on a single Real State, but there may be class methods invoked within that State Activity that can also be invoked in many different Real States. This gives us the ability to define multiple Real States that can invoke common processing in different contexts.
Author's note (LS): Not sure if the idea was ever published, but in the early days I remember Sally Shlaer often referring to 'common processes' (as distinct from accessors as described in [OOA96]) whereby the same arbitrarily complex data flow diagram could be triggered in distinct states.
Copyright © 2021-2023 Leon Starr