TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
The biggest part of analysis - as it is typically
difined - is requirements elicitation. Use Cases are
very poor for requirements elicitation because they
are based upon the the old "connect-the-boxes"
approach: FIRST we draw the boxes (stickmen
-whatever)- THEN we try to figure out how to connect
them all together.
The books on analysis that I read state, and my
personal work experince clearly confirms, that
analysis based upon the old "connect-the-boxes"
approach is going to result in a forced, artifical
partitioning (chunking) of the system. And if it is
forced and artifical, it is a lie.
Now in terms of requirements elicitation: Whether we
are analyzing the existing system or documenting
requirements of a new system, it really does not make
much a difference - as long as the basic business at
hand does not change, the essential requirements are
not going to change.
AJ Markos
Focused On The Essential Like A Laser
--- David Neeley <dbneeley -at- gmail -dot- com> wrote:
> Tony,
>
> Your view of use cases is substantially incorrect.
> Use cases are not
> properly used to analyze existing systems, but the
> uses to which a
> system is to be put with real-world individuals.
>
> Originally, use cases were introduced as a tool in
> requirements
> analysis--so that programmers would understand how a
> system was to be
> used when complete.
>
> It is always true that the technique needs to be
> suited to the
> situation. Use cases are
> definitely not a
> single means of solving all problems.
>
> David
>
____________________________________________________
Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
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.
