Need help selecting proper diagram type

[Vizionoob]

I'm pretty new to Visio and diagramming in general, I was wondering if anyone
could give me some guidance as to the appropriate chart type for the task
I've been given. I've been asked to diagram the flow of an application we're
developing from a very high level; the user perspective basically. The
purpose is to use this diagram as a seed to develop documentation for help
desk support, which we are outsourcing. The trouble I'm having is that basic
flowchart logic seems too low level, for example depicting user input and
then a seperate branching symol for every button press gets very cumbersome
very fast. I spent some time browsing through all the other diagram types
(I'm using Pro 2003 btw) and nothing jumped out at me. So is their a general
methodology and diagram standard for what I'm trying to accomplish?

 

[AlEdlund]

I'd go back to the group that wrote it for you and ask if they used any
formal modeling, such as uml, to architect the solution. The basic flow may
already have been created. Visio professional does support uml modeling but
IMHO that stuff isn't for the faint of heart.
al

 

[Paul Herber]

I'm pretty new to Visio and diagramming in general, I was wondering if anyone
could give me some guidance as to the appropriate chart type for the task
I've been given. I've been asked to diagram the flow of an application we're
developing from a very high level; the user perspective basically. The
purpose is to use this diagram as a seed to develop documentation for help
desk support, which we are outsourcing. The trouble I'm having is that basic
flowchart logic seems too low level, for example depicting user input and
then a seperate branching symol for every button press gets very cumbersome
very fast. I spent some time browsing through all the other diagram types
(I'm using Pro 2003 btw) and nothing jumped out at me. So is their a general
methodology and diagram standard for what I'm trying to accomplish?

To add to Al's reply, if there aren't any diagrams from the team
writing the software then ... It's difficult to know exactly what to
suggest without knowing what the application is for, who the users and
the level of support.
You have users - hence, you have interactions that can be documented.
Initially look at UML Sequence Diagrams, but get some input from the
development team.

 

[WapperDude]

I tend to agree with both Al and Paul, but, the Flow Chart doesn't have to go
down to the "bottom" level. It really is just a matter of your definitions
for what's in each shape. So instead of showing each user button to press,
just let the box indicate user keyboard input. Then, as your company defines
that box, it eventually takes on more detail. However, if you want a few
more symbols, I believe there some defined as "Basic" and "Block". These
ought to be more "generic", or just make your own shapes -- sounds like all
you need is a rectangle with some connection points. Just make one. You can
then copy and stretch as you desire. Any selected shape will allow you to
type into it.

Hope this helps.
Wapperdude