Activity diagram

From Wikipedia, the free encyclopedia

In the Unified Modeling Language, an activity diagram represents the business and operational step-by-step workflows of components in a system. An activity diagram shows the overall flow of control.

Contents 1 Overview 2 Construction 3 See also 4 External links

[edit] Overview

In SysML the activity diagram has been extended to indicate flows among steps that convey physical element (e.g., gasoline) or energy (e.g., torque, pressure). Additional changes allow the diagram to better support continuous behaviors and continuous data flows.

In UML 1.x, an activity diagram is a variation of the UML State diagram in which the "states" represent activities, and the transitions represent the completion of those activities.

The UML 2.0 activity diagram, while similar looking to the UML 1.x activity diagram, has semantics based on Petri nets. In UML 2.0, the interaction overview diagram is based on the activity diagram.

[edit] Construction

Activity diagrams are typically used for business process modeling. They consist of:

• Initial node.
• Activity final node.
• Activities

The starting point of the diagram is the initial node, and the activity final node is the ending. An activity diagram can have zero or more activity final nodes. In between activities are represented by rounded rectangles.

The other 2 major things are there in the activity diagram they are called as fork and join. Fork is used, when one activity splits in to two or more, When two activities done at same time simultaneously that time fork is useful.And join is used to join two or more activities.

[edit] See also

• Flowchart
• Control flow graph
• Data flow diagram

• State diagram
• Pseudocode

[edit] External links

• UML 2.0 Specification Documents
• Introduction to UML 2 Activity Diagrams
• UML 2 Activity Diagram Guidelines
• UML 2 Activity and Action Models

Unified Modeling Language (UML) (category) ( view • talk • edit )
Background
Organizations: Object Management Group (OMG) • UML Partners Persons: Grady Booch • Ivar Jacobson • James Rumbaugh
Concepts
Object oriented: programming (OOP) • analysis and design (OOAD) Structure: Actor • Attribute • Class • Component • Interface • Object • Package  Behavior: Activity • Event • Message • Method • Operation • State • Use case  Relationships: Aggregation • Association • Composition • Dependency • Generalization (or Inheritance)  Extensibility: Profile • Constraint • Stereotype • Tagged values  Other concepts: Multiplicity • Role
Diagrams
Structure diagrams Class diagram • Component diagram • Composite structure diagram • Deployment diagram • Object diagram • Package diagram		Behavior diagrams Activity diagram • State Machine diagram • Use case diagram • Communication diagram • Interaction overview diagram • Sequence diagram • Timing diagram
Topics
Compared to relational database model (ERD) • Glossary of UML terms • Systems Modeling Language (SysML) • UML colors:
Role	Moment, Interval	Description	Party, place, thing
Tools(category) and Processes
List of UML tools • Rational Unified Process (RUP)