Activity Diagram Resources
Activity Diagram Resources
com
Mary Chant, Certified Usability Analyst
Transition When an Activity State is completed, processing moves to another Activity State.
Transitions are used to mark this movement. Transitions are modeled using arrows.
Initial State The Initial State marks the entry point and the initial Activity State. The notation
for the Initial State is the same as in Statechart diagrams, a solid circle. There can only be
one Initial State on a diagram.
Final State Final States mark the end of the modeled workflow. There can be multiple Final
States on a diagram, and these states are modeled using a solid circle surrounded by
another circle.
Synchronization Bar Activities often can be done in parallel. To split processing ("fork"), or
to resume processing when multiple activites have been completed ("join"), Synchronization
Bars are used. These are modeled as solid rectangles, with multiple transitions going in
and/or out.
Like all UML diagrams, the number one purpose of the activity diagram is
to communicate information effectively.
http://download.boulder.ibm.com/ibmdl/pub/software/dw/rationaledge/sep03/f_umlbasic
s_db.pdf
Typically, you will not use every notation element described in this article
when you create your own activity diagrams. But you will make frequent
use of the initial state, transition line, action state, and final state notation
elements.
I started diagramming by creating a simple Activity diagram which illustrated the primary
success scenario.
Activity diagrams
The three involved classes (people, etc.) of the activity are Customer, ATM, and Bank. The
process begins at the black start circle at the top and ends at the concentric white/black
stop circles at the bottom. The activities are rounded
rectangles.
Activity diagrams can be divided into object swimlanes that determine which object is
responsible for which activity. A single transition comes out of each activity, connecting it
to the next activity.
A transition may branch into two or more mutually exclusive transitions. Guard
expressions (inside [ ]) label the transitions coming out of a branch. A branch and its
subsequent merge marking the end of the branch appear in the diagram as hollow
diamonds.
A transition may fork into two or more parallel activities. The fork and the subsequent join
of the threads coming out of the fork appear in the diagram as solid bars.
Altova UModel® 2008 lets you easily chart the flow of actions and illustrate the decision
points in your project design.
The UML 2 specification greatly expanded the features and scope of activity diagrams
beyond their earlier classification as a special case of state diagrams. Today, activity
diagrams can be thought of as flow charts for the 21st century, and UML modelers use
activity diagrams to describe:
• Business rules
• Single use cases
• Complex series of multiple use cases
• Processes with decision points and alternate flows
• Operations that take place in parallel
• Software flows and logic control structures
JoAnn Hackos and Janice (Ginny) Redish, internationally known experts in usable design,
take you through a step-by-step process to conduct a user and task analysis. You learn:
* How interface designers use user and task analysis to build successful interfaces
* Why knowledge of users, their tasks, and their environments is critical to successful
design
* How to prepare and set up your site visits
* How to select and train your user and task analysis team
* What observations to make, questions to ask, and questions to avoid
* How to record and report what you have learned to your development team members
* How to turn the information you've gathered into design ideas
* How to create paper prototypes of your interface design
* How to conduct usability tests with your prototypes to find out if you're on the right track.