RE: Checking for technical accuracy

Subject: RE: Checking for technical accuracy
From: "Ward, Curtis (DBS-CLT)" <curtis_ward -at- dbs-systems -dot- com>
To: "'techwr-l'" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Thu, 29 Jun 2000 10:13:58 -0400

I work for a software development firm. We have found that except for user
manuals, which can go through QA, SME reviews and sign off is about the only
feasible way to ensure technical accuracy.
Curtis Ward
curtis_ward -at- dbs-systems -dot- com

On Thursday, June 29, 2000 9:51 AM, wrote:

> I was wondering what do most of you do to ensure that the documents
> you produce are technically accurate.
> 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?
> Is a sign off the most common way of saying that the document has now
> been completed?

Previous by Author: RE: Interviewing a technical writer -- questions?
Next by Author: RE: HTML help: HTML editors
Previous by Thread: Checking for technical accuracy
Next by Thread: Re: Checking for technical accuracy

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

Sponsored Ads