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.
Subject:Flow Charting and Technical Writers From:Anthony Markatos <tonymar -at- HOTMAIL -dot- COM> Date:Tue, 3 Feb 1998 14:54:35 PST
Question to all software Technical Writers:
Do software technical writers often have to flow chart the system they
are creating documentation on? I would ordinarily assume that any flow
chart (i.e., logical flow chart, data flow diagram, etc.) would be
created by developers and systems analysts and then given to the
technical writer. However, I have always had to create these myself.
Existing flow charts were either non-existent or unusable.
I have read numerous books on technical writing and none has even
mentioned flow charting as a TW task. Yet this is often one of the most
important things that I have to do.
I seek answers to the above for career planning reasons.
Tony Markatos
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
