This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Activity Diagram"

From HL7Wiki
Jump to navigation Jump to search
 
 
Line 1: Line 1:
An Activity Diagram is a type of diagram in the [http://en.wikipedia.org/wiki/Unified_Modeling_Language Unified Modeling Language].
+
An Activity Diagram is a type of diagram in the [http://en.wikipedia.org/wiki/Unified_Modeling_Language Unified Modeling Language]. The UML 2.0 Activity diagram has semantics based on [http://en.wikipedia.org/wiki/Petri_net Petri nets]. The Interaction Overview diagram is based on the Activity diagram.
  
Activity diagrams represent the business and operational workflows of a system. An Activity Diagram shows the overall flow of control.
+
An Activity Diagram identifies a sequence of steps and the information that is transferred from one participating role to another. Sometimes called a “Swim-lane Diagram”, the pictures represent the flow of control among the steps and help identify when information is required to be transmitted to achieve the objectives of the Storyboard.  
  
The UML 2.0 Activity diagram has semantics based on [http://en.wikipedia.org/wiki/Petri_net Petri nets]. The Interaction Overview diagram is based on the Activity diagram.
+
Following is an example of an Activity Diagram, an output of the process step – Capture Process Flow: Activity Diagram. Of particular interest in the data information exchange focus of HL7, are the Activity Diagram semantics that depict the passing of “objects” (e.g., data, information, messages, documents) between swim-lanes.

Latest revision as of 11:25, 22 December 2006

An Activity Diagram is a type of diagram in the Unified Modeling Language. The UML 2.0 Activity diagram has semantics based on Petri nets. The Interaction Overview diagram is based on the Activity diagram.

An Activity Diagram identifies a sequence of steps and the information that is transferred from one participating role to another. Sometimes called a “Swim-lane Diagram”, the pictures represent the flow of control among the steps and help identify when information is required to be transmitted to achieve the objectives of the Storyboard.

Following is an example of an Activity Diagram, an output of the process step – Capture Process Flow: Activity Diagram. Of particular interest in the data information exchange focus of HL7, are the Activity Diagram semantics that depict the passing of “objects” (e.g., data, information, messages, documents) between swim-lanes.