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:How do you prefer to deal with long flowcharts? From:SIANNON -at- VISUS -dot- JNJ -dot- com To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 24 May 2002 13:41:33
Greetings!
While I've already dealt with my specific example of this phenomenon, I'd
really like to hear how other people addressed the issue, since I can't
help but feel there's got to be "A Better Way"(tm) to deal with it:
How do you prefer to incorporate long, complex, branching flowcharts in a
document, when they won't fit on a single page, legibly? In my example,
one such flow is describing program logic as part of the detailed design
document; it spans three portrait-oriented pages vertically, if cut into
chunks. Design doc output is to the US standard 8 1/2" x 11" (LTR) format,
with the body of the doc authored in Word. Flowcharts are created in
Visio.
The "why" behind your "how" can help,...if I haven't faced it yet, I may
face a circumstance in the future where that "why" becomes a necessary
consideration. I'll post a summary next Friday, if there are more than a
scattered few responses.
Some things I can think of include:
-- Do you just cut them into pieces, cropping the graphic wherever the page
would break it? Do you prefer to crop it in Word, or save pieces as
separate graphics and import them separately?
-- Do you shrink the flow and label sections with callouts that refer to
cropped sections that fit on a single page each?
-- Do you prefer to label your flows with captions? Where do you stick
those captions (e.g., before, after, or on each page)?
-- What if the flowchart is wider, as well as taller? (e.g., would have to
be broken into 2 pages across by 3 pages down, to still have the text
legible)
-- Do you try to impose a rule on the Developers to make their flows fit on
a standard page, using off-page connectors to continue them? Do you rework
the flows you receive yourself, to achieve this?
Thanks in advance for any input...
Shauna
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Free copy of ARTS PDF Tools when you register for the PDF
Conference by May 15. Leading-Edge Practices for Enterprise
& Government, June 3-5, Bethesda,MD. www.PDFConference.com
Check out RoboDemo for tutorials! It makes creating full-motion software
demonstrations and other onscreen support materials easy and intuitive.
Need RoboHelp? Save $100 on RoboHelp Office in May with our mail-in rebate.
Go to http://www.ehelp.com/techwr-l
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.