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.
> As I have posted several times: The major thing that a
> TW is to do is come up with a detailed, comprehensive
> understanding of the essential end-user tasks, and how
> all those tasks interrelate - with special emphasis
> placed on understanding the interrelationships.
No, it's not. Tony, not every tech writer documents end-user stuff.
Not every tech writer documents process. You gotta consider other
aspects of our profession before going ape on one area. ;-)
> From the Gospel according to Ed Yourdon: "ONLY by
> following the flow of data [in task analysis] can we
> come up with an understanding [and therefore be able
> to explain to others] the underlying logic of a
> system".
This is a very unhealthy comment. It suggests blind devotion to an ideal.
> If we don't put enough energy on process, you will not
> produce good documents. Come on Andrew, you know it:
> Almost always, the main problem is that not enough
> effort has been placed on process. Thats the major
> reason why so much documentation is so disjointed and
> disorganized.
Process is but a small area, Tony. I can tell you do not see this, but
you're hurting only yourself if you don't consider the possibility
that there is more to technical writing than documenting process.
> I never said that the other things you mention do not
> need to be documented. Just that task anlaysis should
> always be done first, and that the other stuff is of
> secondary importance.
Secondary importance? How so?
> Data Flow Diagrams are a techical communications tool.
ROBOHELP X5 - SEE THE ALL NEW ROBOHELP X5 IN ACTION!
RoboHelp X5 is a giant leap forward in Help authoring technology, featuring all new Word 2003 support, Content Management, Multi-Author support, PDF and XML support and much more! View an online demo: http://www.macromedia.com/go/techwrldemo
---
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.
