RE: Developing a troubleshooting guide

Subject: RE: Developing a troubleshooting guide
From: "Morton, Christopher" <CMorton -at- caiso -dot- com>
To: <glen -dot- blair -at- gmail -dot- com>, <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Wed, 8 Mar 2006 07:59:41 -0800

>I built the charts in Visio and pasted them into my Word doc.

This is also the approach I used on one project at HP, having lifted the
concept from someplace else. I used the basic "software decision flow"
template in Visio, with appropriate Yes/No branching flowing from the
decision diamonds. If this is unfamiliar to you, it's used all the time
to mock up pseudo-code, so you can perhaps start your education there.

Best of luck!

> Chris


WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!.

Doc-To-Help includes a one-click RoboHelp project converter. It's that easy. Watch the demo at

You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit for more resources and info.


Previous by Author: Friday OT: It's everywhere
Next by Author: RE: Developing a troubleshooting guide
Previous by Thread: RE: Developing a troubleshooting guide
Next by Thread: Re: Developing a troubleshooting guide

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

Sponsored Ads