RE: Troubleshooting formats: any standards?

Subject: RE: Troubleshooting formats: any standards?
From: "Gilger.John" <JGilger -at- acresgaming -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Wed, 30 Apr 2003 11:06:53 -0700

Con & Yu wants to know more about making Trouble shooting diagrams.

The best troubleshooting charts I used in a previous life were flow charts. There was a flow chart for each "high level" problem, i.e., "Engine won't start"

You will need a good mechanic to help you understand the process, but basically you step through the things to check in order of their probability and the ease of correcting the problem and follow through in a simple decision tree.

For Example: "Is there gas in the tank?"
YES NO ------> Fill tank
"Is the ignition switch closed?" ....



Last chance to order RoboHelp X3 and receive a $100 mail-in rebate,
PLUS free RoboScreenCapture and WebHelp Merge Module. Offer expires
4/30/03! Order here:

Help celebrate TECHWR-L's 10th Anniversary starting this month!
Check out the contests at
Happy birthday to you, happy birthday to you, happy birthday 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 for more resources and info.

Previous by Author: RE: Exploitation is a two-way street (was a bunch of other thread s)
Next by Author: Job opportunity in Yorktown, Virginia
Previous by Thread: Troubleshooting formats: any standards?
Next by Thread: Results: what do you call your online manuals

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

Sponsored Ads

Sponsored Ads