Activity diagrams<\/b>\u00a0are graphical representations of\u00a0workflows<\/a>\u00a0of stepwise activities and actions with support for choice, iteration and concurrency. In the\u00a0Unified Modeling Language<\/a>, the first structured method for documenting process flow, the \u201cflow process chart\u201d. Activity diagrams combine techniques from flow charts, event diagrams, and Petri nets. Activity diagrams describe the workflow of a system. The diagrams describe activities by showing the sequence of activities performed. Activity diagrams are useful for analysing a use case by describing what actions need to take place and when they should occur. Usually activity diagrams are used to describe a complicated algorithm or to model the flow in applications with parallel processes. The distinction between state and activity diagrams is only in what they model. Where state diagrams are used to model state-dependent behaviour and conditions for transitions between states, activity diagrams are used to model the flow of actions and the order in which the actions take place.<\/p>\n The notational elements used in state diagrams and activity diagrams are the same except for a few subtle differences. The main difference between UML state diagrams and UML activity diagrams is in their intent. The basic elements of UML activity diagrams can be classified as activity nodes and edges. Activity nodes can either be action, object or control nodes. An activity is shown as a round-cornered rectangle which encloses all the action and control nodes which make up the activity. Action nodes represent a single step within an activity and are also denoted by a round-cornered rectangle. Control nodes model different flows that are controlled by conditions called guards.<\/p>\n The starting point of the flow that is shown in an activity diagram is indicated with a filled circle. An activity diagram must have exactly one initial node. An exit point in an activity diagram is called an final node. There are two kinds of final nodes, referred to as as activity final node and flow final node. The flow final node denotes the end of all flow controls within the activity. The activity final node denotes the end of a single flow control. An activity final node is shown with a filled circle with an outline.<\/p>\n Activity diagrams are constructed from a limited number of shapes, connected with arrows.[4]<\/a><\/sup>\u00a0The most important shape types:<\/p>\n Arrows run from the start towards the end and represent the order in which activities happen.<\/p>\n Activity diagrams can be regarded as a form of a structured\u00a0flowchart<\/a>\u00a0combined with a traditional data flow diagram. Typical flowchart techniques lack constructs for expressing concurrency. However, the join and split symbols in activity diagrams only resolve this for simple cases; the meaning of the model is not clear when they are arbitrarily combined with decisions or loops.<\/p>\n While in UML 1.x, activity diagrams were a specialized form of state diagrams, in UML 2.x, the activity diagrams were reformalized to be based on\u00a0Petri net<\/a>-like semantics, increasing the scope of situations that can be modeled using activity diagrams. <\/sup>These changes cause many UML 1.x activity diagrams to be interpreted differently in UML 2.x.<\/p>\n UML activity diagrams in version 2.x can be used in various domains, e.g. in design of embedded systems. It is possible to verify such a specification using model checking technique.<\/p>\n","protected":false},"excerpt":{"rendered":"Notational Elements<\/h4>\n
Initial and final nodes<\/h4>\n
Construction<\/span><\/h4>\n
\n