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.
Subject:QA plan help From:"Susan Hogarth" <hogarth -at- gmail -dot- com> To:TECHWR-L <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Mon, 12 Feb 2007 10:31:38 -0500
I need help here.
What is the difference between a QA plan and a protocol? To me it
seems there should be a fdifference, but I've been handed a 'qa plan'
to edit that looks more like a (not very detailed) protocol.
I look on the web, and many so-called QA plans seem to be of the same
nature. Any input as to what a QA plan should do, and how? Should ti
detail the process itself, or *just* elements to assure quality of the
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList
Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com