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.
Beth, perhaps the system your programmers use has some fields for technical
That is the case with NuMega's TrackRecord. Programmers, QA, and
Documentation share this database. You can set up separate databases for
each product. If you get alpha and beta releases of your products during
your documentation development, TrackRecord even allows for you to report
bugs or poorly designed features.
Is there such a thing as an electronic revision database system for
technical writing? The programmers here have a bug database in which they
register all the bugs and then fix them whenever they get the time. We want
our own database so that when someone says, "this thing should go in the
manual," we can enter it as a change to make for the next revision.