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.
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?
>
>
>
>
