Validating documentation

Subject: Validating documentation
From: "Jackson, Malkia" <MJackson -at- dpconline -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Fri, 22 Mar 2002 10:51:14 -0800


My company is considering a more formal approach to validating the software
sections of our operator manuals by developing a more intimate alliance with
our internal software QA department. Specifically, we are considering
asking software QA to validate the operator manual at the same time as
software builds are tested.
I have some questions - Any ideas on how such a relationship can best work
for all parties involved? Is this a natural alliance (i.e. should
techwriters of software be closely linked with SQA)?
Thanks for the input.

-Malkia




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



Follow-Ups:

Previous by Author: Re: Occupational hazard - carpal tunnel (longish)
Next by Author: RE: What about "semi-official" internal docs?
Previous by Thread: Humor: How to end a sentence
Next by Thread: Re: Validating documentation


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

Sponsored Ads


Sponsored Ads