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.
> Giving users just what they want rather than what they really need is a common
> trap that software development falls into when writing requirements. The
> argument for this is that "we are customer oriented." Requirements then become
> the verbatim requests of the customer.
Quite. In the project where I work right now, they have things like the same
Print command in two different menus of the menu bar. When I asked
one of the developers, whether that wasn't a bit absurd, he shrugged and
said "user requirement". Most of the users are of the "VMS is the only
really cool operating system, and real men don't use mice anyway" kind
of persuasion, so designing a GUI application to their spec may
not be such a wonderful idea.
Peace,
Mike
------------------------------------------------------------------------
Mike Dannenberg
100767 -dot- 707 -at- compuserve -dot- com
"... but I am a great eater of beef, and I believe that does harm to my wit."
William Shakespeare
Twelfth Night, Act 1 Scene 3
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Post Message: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Get Commands: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "help" in body.
Unsubscribe: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "signoff TECHWR-L"
Listowner: ejray -at- ionet -dot- net
