(Apologies for the formatting problems in this posting. The editor is scrambling the input formats and won't change.)
Three of the eight behavior diagrams are discussed with examples in this section.
Activity diagrams can also include forks to describe conditions and parallel activities. A fork is used when multiple activities are occurring at the same time. As shown on the diagram , all branches at some point are followed by a merge to indicate the end of the conditional behavior started by that branch.
Sequence Diagram - A sequence diagram is an interaction diagram that emphasizes the time ordering of messages. A sequence diagram shows the objects and the messages that go between those objects at a particular instance of time. They are used to illustrate the dynamic view of a system. An example of a possible sequence diagram for the digital camera system is hown in Figure 11-5.
State Machine Diagram - A state machine is a behavior that specifies the sequence of states an object goes through during its lifetime in response to events, together with its response to those events. A state machine diagram shows the state machine, consisting of states, transitions, events, and activities. These diagrams are used to illustrate the dynamic view of a system. These are important when modeling the behavior of an interface, class, or collaboration and are useful when modeling reactive systems. Figure 11-6 shows a state machine diagram for the Shutter Object. When the button on the camera is pushed to take a picture, the Shutter object moves from the Opened state to the Closed state. Once the button is released, the Shutter Object moves back into the opened state.
Figure 11-8 Example Use Case Template
11-4 Unified Modeling Language Tutorial, http://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/activity.htm