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.
>>alliance with our internal software QA department
I've worked at two software companies and both were set up this way. I
report to the head of QA and I send all manuals to QA for review. "Bugs" in
the manuals are tracked similarly to bugs in the software, after the initial
release. I think it's a very beneficial alliance as long as the timing of
releases does not create bottlenecks in QA. It's also helpful for the QA
department because they get very familiar with the contents of the
documentation and use it for training, test development, and answering
questions about the software which boomerang back to them. I like the setup
Catherine Ednie, Technical Publications
203-882-9988 ext. 2610
cednie -at- eventra -dot- com
PC Magazine gives RoboHelp Office 2002 five stars - a perfect score!
"The ultimate developer's tool for designing help systems. A product
no professional help designer should be without." Check out RoboHelp at http://www.ehelp.com/techwr
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 http://www.raycomm.com/techwhirl/ for more resources and info.