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.
> > QA needed the manual to know how to run and test the application
> QA would have been just fine with a good set of use case docs, traceable
> business and system requirements, and a well-written detailed design doc.
OK, here are some questions for you:
What is QA testing and why?
What is the purpose of QA?
Where does QA fit into the overall engineering cycle?
> Alright, how many people on this list couldn't figure out how to write it
> that way?
Write what in which way, exactly? I'm quite lost in the generalities
being thrown around in this thread.
It's funny... I think I'm getting more answers to my poll in this
thread than in the actual poll thread. ;-)
WEBWORKS FINALDRAFT - EDIT AND REVIEW, REDEFINED
Accelerate the document lifecycle with full online discussions and unique feedback-management capabilities. Unlimited, efficient reviews for Word
and FrameMaker authors. Live, online demo: http://www.webworks.com/techwr-l
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit http://www.techwr-l.com/techwhirl/ for more resources and info.