Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
0% found this document useful (0 votes)
11 views16 pages

Work Flow Modeling Week 5

Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1/ 16

Workflow modeling

 Activity Diagrams

OOAD
1
• Models functional logic logic of the system in question
• Provide valuable insight in modeling workflow,
describing use cases and specifying operations
• Very much similar to flow charts, but different in that
they support parallel behavior
• Focus on flow driven by internal processing (as opposed
to external events)

Activity diagrams 2
• A workflow shows how work is being carried out in a
business
• Workflow model may consists of the following
• A set of sequentially performed activities representing the tasks to
be accomplished
• A set of decisions that guide the flow of control based on
conditions that are encountered during the workflow
• A set of partitions that allocate the activities among the
responsible parties that participate in the workflow
• A set of terminal activities that indicate the start and end of the
workflow
• A set of regions that indicate repetition and concurrency

Modeling Workflow 3

& Use cases


• Customer placing order at POS
• Creation of a record on a system
• Activating user accounts
• Or just any process that may involve several steps or
activities that use a system

Examples of
workflow 4
• May be used to show the implementation of complex
operations/methods/subroutines/functions
• Need to show the sequence of data manipulation and
transformation, looping and decision logic
• Maybe very useful as it translates quite well to pseudo
code or native code
• May help one to see all the requirements clearly

Modeling
operations 5
Activity
•Process were some work is
being done
•Must have an entry action
and atleast one outgoing
transition

Start State End State


Shows the start of an Shows the end of an
activity. activity.

Transition/Flow/Edge
Specifies the flow of control
Activity diagram for grade
between states.

recording 6
• Decision nodes
• Fork & Join nodes
• Partitions

More components of 7

activity diagrams
• Used for making decisions within an activity flow
• Route the flow of one outgoing edge
• Has guards to specify more information on one of the
outgoing edges

Decision node Guard


Represented as diamond Specifies information
Must have 1 entry transition About the transition such
And atleast 2 outgoing As condition for following the
transition Transition.
Note that guards are effectively
Boolean conditions 8

Decision node
• Bring together multiple alternate flows
• All controls and data arriving at a merge node are
immediately passed to the outgoing edge
• There is no synchronization of flows or joining of tokens

merge

Merge Nodes 9
• Fork allow parallel processes to Fork
begin
• Each branch is effectively a
separate activity diagram
• Control flows do not have to
wait for each other to complete
• Join allows parallel processes
to catch up and resume a
single-process flow
Join

Fork & Join nodes 10


Partition label
• Splits behavior according to
classes or organizational units
• They are done using swim lane
notation
• Allows one to represent flow of
activities according to actors

Vertical Activity Partition


•Actions for an order can be
separated into different
departments.
•Partitions could have also been
made horizontal.
•Number of swim lanes is
dependent on the separations
one wants to have.
11

Activity Partition
12
13
14
• Example scenario and an activity diagram
• Pick a scenario from any of the previous examples and
draw activity diagrams in VP. See tutorial for more
examples

Example scenario 15
• Chapter 13 of UML Bible

References 16

You might also like