RE: Checking for technical accuracy

Subject: RE: Checking for technical accuracy
From: "Fisher, Melissa" <Melissa -dot- Fisher -at- delta-air -dot- com>
To: 'Sona Mehta' <sona -dot- mehta -at- haysmt -dot- co -dot- uk>, 'TECHWR-L' <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Thu, 29 Jun 2000 10:39:13 -0400


Assuming your company is large enough to have evolved a QA department, Tech
Support, or Training groups, they are usually good sources of technical
information. I assume you are asking about documenting "legacy" products, or
products that are no longer currently in development, because of course
questions about a product in development are usually most accurately
answered by the developers themselves.

Also, because a developer is now in a different role, this does not
necessarily mean that they are no longer available to you. Depending on the
size and organizational structure of your company, and the corporate
culture, you can probably send a few emails to the developer in the new role
if you can't find the answers elsewhere. I wouldn't count on getting a fast
response, but this depends more on the value that the company as a whole
places on accurate documentation.

HTH, and Good luck,
Melissa Fisher
melissa -dot- fisher -at- delta-air -dot- com
(404) 773-8674

-----Original Message-----
From: Sona Mehta [mailto:sona -dot- mehta -at- haysmt -dot- co -dot- uk]
Sent: Thursday, June 29, 2000 9:51 AM
Subject: Checking for technical accuracy


Technical review by the developers is one way I know of but in the real
world, the developer you want is no longer with your company or has now
assumed some other role. What helps you to write a technically accurate
document ( Eg Programmer's Manual) in the first place?


Previous by Author: RE: Style Guide Help
Next by Author: RE: Ratio of tech writers to developers
Previous by Thread: Re: Checking for technical accuracy
Next by Thread: DTD - any info about them

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

Sponsored Ads