Chapter 10. Communicating Objects
In Executable UML, we build statechart diagrams and state transition tables for classes and associations to capture their lifecycle behavior. The behavior is defined in actions, grouped together as procedures on the state machines. The behavior is sequenced by signals between state machine instances.
By formalizing behavior as actions in procedures, we make the procedures, the state machines, and so the entire domain model, executable.
Each procedure on a state machine is written using an action language such as that introduced in Chapter 7: Class Actions. This chapter extends these actions to include signaling to existing objects and signaling to cause creation of other objects. Certain rules govern the construction ...
Get Executable UML: A Foundation for Model-Driven Architecture now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
