Re: Use Cases - NEED INPUT - PLEASE HELP

[Suzette Leeming <suzette -dot- leeming -at- gmail -dot- com>]

 have had similar experiences - usually when the use case was written
by an engineer. I guess you can say the use case was "overengineered".

Suzette Leeming
Stouffville, Ontario


On 7/8/05, David Neeley <dbneeley -at- gmail -dot- com> wrote:
> 
> Anthony, Dick, Lisa, et al.:
> 
> Use cases can also be rather foolish when applied by rote. I had a
> memorable experience with the use cases done for a new feature being
> implemented for a Nortel switch by one of the engineers. He had six
> pages of text to describe what he had in mind. It took me two solid
> days to begin to understand what he was trying to say, even though he
> included separate diagrams for each of six scenarios; the resulting
> documentation was a page and a half with one very simple diagram and a
> brief table. The doc manager's comment was "Ah, now I see what he was
> trying to say!"
>

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l

Doc-To-Help 2005 now has RoboHelp Converter and HTML Source: Author
content and configure Help in MS Word or any HTML editor. No
proprietary editor! *August release. http://www.componentone.com/TECHWRL/DocToHelp2005

---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.