Diagrams for different project members

[sim_sim]

Hi All,

I have a confusion, use case, activity, sequence diagrams ... but they can be interpreted only by the team members who understand UML. what about the rest of the team like graphics, instructional desingers, content / copy writer and even the not so techno savy client?

which UML diagrams wld be helpful for the rest of the team to understand the requirements.

rgds,
Seema

[jeshaw2]

I offer two approaches:

• Teach them how to read the UML
• Produce a text document that verbalizes the model.  This also has utility in model validation.
  

Given your list of individuals, I wonder why some of them  need to read the UML, for UML does not provide them with the information they need to perform their function.  For example, how would UML help a graphic artist produce a piece of art?  UML is color blind and unemotional which might lead to artwork that is grey and unstimulating.

[sargasso]

I offer two approaches:

    * Teach them how to read the UML
    * Produce a text document that verbalizes the model.  This also has utility in model validation.

I concur, in fact I disagree!

1. It takes about 10 minutes to expain stick people and footballs to the average non-technical client.  If they cant understand use case diagrams after that they are probably too incompetent to be a client.

2. Plumbers dont need to know how to build roof trusses.  Also dba's dont need to understand sequence diagrams.  IOW teach the tech's only what they need to know to do their bit.  If they keep asking about bits they dont need then just kill them - it'll save you a lot of time and stress.

3.  

the rest of the team like graphics, instructional desingers, content / copy writer

There is nothing in UML of interest to these geese.

Fable:  Mr and Mrs X are building/renovating a house.  You are thier architect.  They have different needs regarding the plans for this house.  Mr X wants to know that he has enough power circuits and ethernet cabling to run this years,  next years and the next 25 years of technology.  Mrs X is worrying about the colour of the walls so she can settle on the curtain colour material.  Would you attempt solve both these communcations problems with the one "tool-in-hand"?  Would you attempt to get Mrs X to understand the wiring diagram?  Would you attempt to engage Mr X in discussions re the colour samples?

In short  - horses for courses!  No-one said you can't use (godforbid) Powerpoint presentations on a project - just dont use them to record the real design decisions.  Just like the blueprints are the design for the house, not the sketches on the back of beer slabs.

hth
bruce

[sim_sim]

Hi Friends,

Thanks for your views. But dont you think that I would land up making lot of diagrams for tech and non-tech team members / clients.

I wanted to show the flow to all so that they would also be equal IDEA contibuters.

Thanks for your prespective.
Rgds,
Seema

[thomaskilian]

You should restart reading, what Bruce said. Why should Mr X be bothered with colors and Mrs X with wires? That only makes a lot of unnecessary fuss. Are you really planing to ask the graphic designers about IT infrastructure?