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:Re: test phase From:Marc Santacroce <santa -at- TFS -dot- COM> Date:Fri, 3 Mar 1995 15:31:00 PST
At 2:05 PM 3/2/95 -0600, Christopher Shade wrote:
>If a technical writer were on a test team, in the test phase of a software
>development life cycle, what responsibilities would he/she have?
===========
I'm one of those...and we are just now getting around to answering this
issue. (Actually I'm a writer/trainer.) I've proposed that I participate in
the system test as well as validate the user manuals by testing the doc
procedures.
I'd be interestd in seeing the responses you get.
=======================
Regards,
Marc
M_a_r_c_ A. _S_a_n_t_a_c_r_o_c_e_________________________
Technical Writer/Trainer
TRW Financial Systems, Inc.
300 Lakeside Dr.
Oakland, CA 94612-3540
santa -at- tfs -dot- com santacroce -at- aol -dot- com
"An idiot with a computer is a faster, better idiot"
- Rich Julius
