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: Moving Target , Part 2 From:"Carol Anne T. Wall" <usmml8wl -at- IBMMAIL -dot- COM> Date:Fri, 23 Feb 1996 14:16:52 GMT
I'm beginning to think I've been a bit spoiled. But maybe that's because
we're a smaller team (under 20 members) that works with the software
development.
In our area, we don't have tech writers per se. The Systems Analysts are
responsible for the system design documentation and the help
documentation. Most of the time, you wind up writing both, so you're in
control of when you update your help documentation. The programmers
don't make a change in the screen layout without the initial system
design document.
Also, the Analysts are part of the testing group as well, so we can
always get our hands on the latest version of the software, to double
check our documentation.
The help file documentation unfortunately still winds up being one of the
last things that happens, but speaking strictly from personal experience,
that's a result of my procrastination, not a lack of information.
Carol Anne
--
************************************************************
Carol Anne T. Wall ** Opinions expressed here are **
Asst. Marketing Systems Analyst ** not those of my employer. **
Minnesota Mutual Life Insurance Company, St. Paul, Minnesota, USA
************************************************************************
