Modeling data flow between a client and a web service

Hello.

I have a need to model the data flow between a client application and a web
service. Does anyone have any good reference on best practices for modeling
in Visio with web services. Or maybe some examples just to help get me
started in the right direction.

Thanks.
Ryan.

A few options I can think of are:

1. Data Flow Model Diagram (Gane Sarson)
It's very simple but effective.  It revolves around data stores and
processes and how data flows in and out of data stores when a process
occurs.

2. UML diagram
Sequence or collaboration diagrams would both be useful.  If you create
classes to represent your web service and clients and other involved
objects, you can get a good diagram (though Visio is somewhat clumsy with
some of the UML diagrams, especially the sequence).  There are many UML
primers on the web if you are not familiar with it.

3.  Blank Drawing!
Requires the least amount of prerequisite knowledge :)  Just use your
imagination and flow what you need to communicate to your audience.  It
doesn't need to be fancy to be effective.

Pointer: Regardless of the method you choose keep it as simple as possible.
Only include information that is necessary to portray a main thought /
process.  If your diagram gets too complicated, consider breaking it out
into multiple diagrams.  You can use a train of thought similar to that
taught in writing/composition classes -- break out into logical "paragraphs"
and cut out unnecesary information!

Mike

Sorry for the late reply. I want to think you for your suggestions. I too
think that Visio is somewhat clumsy with UML.

"Mike Jansen" <mjansen_nntp@mail.com> wrote in message
news:u81EZiGQFHA.3716@TK2MSFTNGP14.phx.gbl...
> A few options I can think of are:
>
> 1. Data Flow Model Diagram (Gane Sarson)
> It's very simple but effective.  It revolves around data stores and
> processes and how data flows in and out of data stores when a process
> occurs.
>
> 2. UML diagram
> Sequence or collaboration diagrams would both be useful.  If you create
> classes to represent your web service and clients and other involved
> objects, you can get a good diagram (though Visio is somewhat clumsy with
> some of the UML diagrams, especially the sequence).  There are many UML
> primers on the web if you are not familiar with it.
>
> 3.  Blank Drawing!
> Requires the least amount of prerequisite knowledge :)  Just use your
> imagination and flow what you need to communicate to your audience.  It
> doesn't need to be fancy to be effective.
>
> Pointer: Regardless of the method you choose keep it as simple as
possible.
> Only include information that is necessary to portray a main thought /
> process.  If your diagram gets too complicated, consider breaking it out
> into multiple diagrams.  You can use a train of thought similar to that
> taught in writing/composition classes -- break out into logical
"paragraphs"
> and cut out unnecesary information!
>
> Mike
>
>