Re: Product Task Analysis

Subject: Re: Product Task Analysis
From: Jon at TaskArchitect <jon -at- taskarchitect -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Fri, 24 Sep 2004 14:02 -0400

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
feature documentation.

Horses for cousres. We could have a wider discussion about task centered
vs data centric design - but maybe not in this forum?



ROBOHELP X5: Featuring Word 2003 support, Content Management, Multi-Author
support, PDF and XML support and much more!

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!

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 for more resources and info.


Previous by Author: Re: Product Task Analysis
Next by Author: RE: MS Word Question
Previous by Thread: Re: Product Task Analysis
Next by Thread: Super-Charged Task Analysis

What this post helpful? Share it with friends and colleagues:

Sponsored Ads