1. THE OBJECT-ORIENTED DESIGN WORKFLOW Activity Diagrams

2. The Activity Diagram l Activity diagrams are sometimes called “object- oriented flowcharts”. They allow you to model a process as a collection of activities and transitions between those activities. l Activity diagrams are used to document workflows in a system, from the business level down to the operational level. l The general purpose of activity diagrams is to focus on flows driven by internal processing versus external events.

3. Guidelines for Building Activity Diagrams l Since the activity diagram can be used to model any kind of process, you should first set the context or scope of the activity being modeled. Once you have determined the scope, you should give the diagram an appropriate title. l You must identify the activities, control flows, and object flows that occur between the activities. l You should identify any decisions that are part of the process being modeled. l You should attempt to identify any prospects for parallelism in the process.

4. Some other things to keep in mind… l Limit the diagram to a single node that starts the process to be modeled and one final-activity node. l When modeling high-level business processes or workflows, you should only include the most important decisions. Make sure that the guard conditions associated with the outflows of decisions are mutually exclusive (i.e., all potential values of a decision are associated with one of the flows). l When decision modeling, you should only include forks and joins to represent the more important parallel activities in the process. l You should lay out the activities on the diagram in a left to right and/or top to bottom order based on the order that the activities are executed. l Swimlanes should only be used to simplify the understanding of the diagram and you should not have more than five lanes. l Finally, you should challenge any activity that does not have any outflows or any inflows. Activities with no outflows are referred to as black-hole activities. An activity that does not have any inflow is known as a miracle activity.

5. The Activity Diagram

7. Completion Transitions

8. Branching

9. Forking and Joining

10. Swimlanes

11. Modeling a Workflow

12. Activity Diagram Resources l IBM: –http://www- 128.ibm.com/developerworks/rational/library/2802.htmlhttp://www- 128.ibm.com/developerworks/rational/library/2802.html l Agile Modeling: –http://www.agilemodeling.com/artifacts/activityDiagram.ht mhttp://www.agilemodeling.com/artifacts/activityDiagram.ht m –http://www.agilemodeling.com/style/activityDiagram.htmhttp://www.agilemodeling.com/style/activityDiagram.htm