Re: [AM] an anecdote about diagrams

At 10:56 AM 2/27/2004, you wrote:
><snip>
>During the discussion, the flowchart quickly became a mess and people were 
>getting confused about the notation. I then asked for a description of 
>one, straight-line task with no variations, end-to-end in a perfect world. 
>Using only arrows and boxes, we came up with 5 parallel chains with a lot 
>of redundancy. We then identified all the common elements and I showed 
>them how to draw a simple UML activity diagram by starting with a few 
>elements and explaining the notation for synchronization, decision points 
>and swim lanes. With minimal guidance, they finished up their desired 
>workflow in about 10 minutes PLUS they easily identified how they could 
>eliminate a further 3 manual steps. They also noted how one iteration was 
>self-correcting and we were able to eliminate one step in the auditing process.
>


Seems to be a pretty clear case of knowing your models, applying the right 
artifacts, modeling with others, and using the simplest tools (I'm assuming 
you started the sketches on a whiteboard) in action.  In this case the 
primary skill was to know that some sort of process model (e.g. a data flow 
diagram, a flow chart, or in this case a UML activity diagram) was needed 
and then working together to do it.


>I did construct a use-case diagram, initially, for my own benefit. 
>However, during the session it became apparent that the activity diagram 
>with swim lanes was much more descriptive and functional. It's pretty 
>clear to all involved that the use-case diagram was a nice springboard, 
>but the activity diagram will persist as permanent documentation and is 
>going to be included in the training manual.

Yes, some diagrams prove themselves to be valuable whereas other don't.  In 
other situations you could just as easily found that the activity diagram 
wasn't sufficiently valuable and thus you would decide to discard it after use.


>
>After the meeting, one of the program managers asked if I would be willing 
>to train some of her peers how to "draw that new flowchart you used."

My advice would be to keep it simple.  They might find 
http://www.agilemodeling.com/artifacts/activityDiagram.htm and perhaps 
http://www.modelingstyle.info/activityDiagram.html to be of interest.

- Scott

====================================================
Scott W. Ambler
Senior Consultant, Ronin International, Inc.
www.ronin-intl.com/company/scottAmbler.html

www.agiledata.org
www.agilemodeling.com
www.ambysoft.com
www.enterpriseunifiedprocess.info
www.modelingstyle.info
www.ronin-intl.com

For more information about AM, visit the Agile Modeling Home Page at www.agilemodeling.com
--^----------------------------------------------------------------
This email was sent to: [email protected]

EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrKDA.bWnbtk.Z2NtYS1h
Or send an email to: [email protected]

TOPICA - Start your own email discussion group. FREE!
http://www.topica.com/partner/tag02/create/index2.html
--^----------------------------------------------------------------