Hello For my MSc project I'm looking at diagrams which can be used for specifying workflow. As a workflow developer in the real world I know that a lot of the diagrams promoted in the literature would completely put off the people who have to sign off the specifications - ie the end users. My project has therefore wandered away from simply comparing specification methods and is now examining some of the human factors in specification.
I should be very grateful if anyone can point me in the direction of studies which look at the 'user-friendliness' of diagrams, especially when used in specification; or at what makes people pay attention to diagrams, and what makes them switch off. If the studies looked at UML activity diagrams or Petri nets that would be a bonus, as these are the two techniques I'm using to explore the issues involved. Does anyone have any thoughts about what makes a 'good' specification method, from the point of view of the end user rather than the developer? Many thanks. Karen Mogridge ---------------------------------------------------------------------- PPIG Discuss List ([EMAIL PROTECTED]) Discuss admin: http://limitlessmail.net/mailman/listinfo/discuss Announce admin: http://limitlessmail.net/mailman/listinfo/announce PPIG Discuss archive: http://www.mail-archive.com/discuss%40ppig.org/
