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:Re: Flow Charting and Technical Writers From:Lynn & Elizabeth <lap8068 -at- W-LINK -dot- NET> Date:Sun, 8 Feb 1998 12:00:28 -0700
Tony,
I write User Guides and Desktop Procedures for the Electrical
Engineering Group of a major aircraft manufactuing company. I use
flowcharts all the time to structure my Desktop Procedures documents.
I develop a high level sequential series of tasks (a flowchart) which
define the "business" process and then get approval from the subject
matter experts. These high level tasks become the main chapter
headings. From these high level charts I, in conjunction with the
experts, develop the subtask flows. These detailed flowcharts define
the next level of detail and are usually included as an embeded graphic
at the beginning of each chapter.
So, to answer your question: Yes, I do develop flowcharts as an integral
part of my documentation process.
