• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

use case - diagram needed?

 
Ranch Hand
Posts: 3852
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am writing use cases for a project. We have a template where in I have to write all the steps of a use case and then a task flow diagram which eventually has same number of steps (each step has its own box and start and stop oval). I just wonder why do we need a diagram for it... it's a waste of time to draw diagram, its not needed at least for small (simple) use cases...

How do you write use case documents? Any diagram you provide? Any use of that diagram you feel?

Thanks.
 
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Have a look at the Use Cass section of the FAQ.
[ April 08, 2008: Message edited by: Peer Reynders ]
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I think you are dead-on when asking about the usefulness of the diagram. But you are asking the wrong people.

There are two groups of people who are much more qualified to answer your question than we are: those who will consume your use cases, and those who made up the template.

Knowing whether and why those diagrams are needed won't only help you to decide whether to produce them at all, but also make you more efficient in deciding how much effort to put into them, and more importantly, on which aspects to focus the effort.

See also http://www.agilemodeling.com/principles.htm#ModelWithAPurpose
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic