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.
<<I am trying to develop a way to track or organize two different
things:
> * Errors found in documentation after it has been printed
> * Product evolutions before a new version is released>>
>
The best way, I think, is to use the same process the developers use
to track product bugs. Usually, it is some kind of database in which bugs
are logged and tracked. If you monitor the bugs database, you will know the
identified bugs and will know when/if bugs are fixed. You can use the same
database to log "bugs" in your docs. And track the versions of the manual in
which the "bugs" were fixed. This is helpful for technical support, as well.
Developers also need to monitor and coordinate their work on new features,
so that is another process you can tap into.
If software is released more often than manuals, you may feel the
need to publish errata or release notes to document changes/bug fixes
between versions of the manual. Since we started publishing manuals in
electronic format only, I am able to keep up with software release, so that
I have a new version of the manual ready for the CD when the new software is
released. I also update the manual on the web site with changes in-between
official released versions. The online manual is always the most current and
accurate version of the manual.
Janet
Janet Valade
Technical Writer
Systech Corporation, San Diego, CA mailto:janetv -at- systech -dot- com
