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.
Re: Technical Communicators on Software Development Teams
Subject:Re: Technical Communicators on Software Development Teams From:Chuck Blessing <chuck -dot- blessing -at- CBIS -dot- COM> Date:Mon, 4 Mar 1996 15:42:55 -0600
Cathy (strawbie @ sfsu.edu) wrote:
>I'm doing research on technical writers and their value to software
>products and product documentation by being included with the overall
>development of software products. Can anyone offer any insight on this
>issue?
I am trying to convince my management that a technical writer needs to be on the
requirements development team. By participating in requirements development,
the writers will not only better understand the system, but also may point out
requirements that could be satisfied by documentation rather than software. This
point is appealing to development managers who may have not enough people to
code all the changes.
This point is part of a several page proposal that I wrote, which argues that a
tech
writer needs to be involved in requirements. I can send this to your e-mail
address
if you are interested. It is specific to the project that I am on, but you may
find it useful.
I 'm also be interested in seeing what other people have to say on this point.
*********************************
Chuck Blessing
Cincinnati Bell Information Systems, Inc. (CBIS)
Cincinnati, Ohio
chuck -dot- blessing -at- cbis -dot- com
- OR -
cjb -at- iglou -dot- com
