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.
You've raised a classic point of contention.
As I see it, hierarchical task analysis has the advantage of portraying the
user's view of the system. The approach does rely on the quality of the
analyst's interviews and data gathering to fully understand the ways that
the program can be realistically used. It wll produce a description that
is user focussed and is easy for readers to understand.
Data flow diagrams are more comprehensive, providing you can elicit the
information from the designers. I'm not sure that the output is as easy to
comprehend, and does not usually show the system in the user's terms. But
it may be required to meet the second part of Anna's task - exhaustive
Horses for cousres. We could have a wider discussion about task centered
vs data centric design - but maybe not in this forum?
WEBWORKS FINALDRAFT: New! Document review system for Word and FrameMaker
authors. Automatic browser-based drafts with unlimited reviewers. Full
online discussions -- no Web server needed! http://www.webworks.com/techwr-l
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 ejray -at- raycomm -dot- com -dot- Visit http://www.techwr-l.com/techwhirl/ for more resources and info.