CHAPTER 13
Modeling Behavior Using an Activity Diagram
In This Chapter
- Modeling the Activity diagram in UML 1.4
- Modeling activities and transitions
- Modeling split and merge of control
- Modeling fork and join for concurrency
- Modeling the Activity diagram in UML 2.0
- Modeling activities, activity groups, actions, and pre- and post conditions
- Modeling activity edges, object flow, object nodes, exceptions, and streaming
- Modeling interruptible regions
- Modeling central buffers and data stores
The Activity diagram is often seen as part of the functional view of a system because it describes logical processes, or functions. Each process describes a sequence of tasks and the decisions that govern when and how they are performed. You must understand a process in order to write or generate correct code for a behavior.
Some authors lump functional and dynamic aspects of modeling together because they both express behavior. However, in teaching these concepts, I find it useful to distinguish logic from interaction. Interactions address net results of processes, that is, net input and output. Functional or logical models address the mechanics of transforming input to output.
Also, functional ...
Get UML™ Bible 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.
