Re: TW--Description

["Bergen, Jane" <janeb -at- ANSWERSOFT -dot- COM>]

Hi again, Gina,

One thought about your TW description: it's usually a big "no-no" to
have the Technical Writer test her/his own work. Preliminary testing is
fine, but not the final. That should be done by someone with no
involvement in the actual documentation process. In the same way, the
developers don't do QA testing on their own software.

Do you plan to produce printed user documentation? If so, you might
mention that, also.

Jane

On Monday, January 12, 1998 10:40 AM, Gina Hertel
[SMTP:Ghertel -at- ALPHA88 -dot- COM] wrote:
> My company is just moving into the Software Development arena.  For
> proposal purposes, I am trying to create a "blurb," which describes
each
> team member's respective roles and responsibilities in terms of
> application development initiatives.  Obviously, these roles will
> change/evolve over time AND depending on the project.  However, I am
> presently trying to think of all of the POSSIBLE ways in which a
> technical writer could/would contribute to a software development
> project.  Below is the "blurb" that I've come up with so far.  I'm
> looking for ways to improve/expand it.  Technical Writers with this
kind
> of experience... what do you think?
> Thanks in advance!
>
> The Technical Writer will be responsible for interviewing SMEs
(subject
> matter experts) and conducting QA testing for the product.  Using the
> software itself, client specifications, and any user and engineer
> requirements as a guide, the Technical Writer will also be responsible
> for creating and/or contributing to the creation of on-line help files
> and user manuals.  If training is involved, the Technical Writer will
> work with our Certified Instructors to develop customized courseware
for
> the new applications.
>
>
> Gina Hertel
> Technical Writer
> Alpha Technologies, Inc.
> ghertel -at- alpha88 -dot- com
> (732) 980-1800 Ext.749