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.
>The "thing" about those standards is that they should be
>used just as guides. For your particular situations, you'll
>probably need to adapt whatever format you find works best
>at the start.
>
>I don't know any shops using the Kovitz standard although
>I'm sure it's wonderful. All the companies I've had dealings
>with use the IEEE standards for requirements, design
>descriptions and testing.
Yep. I don't believe in standards for this sort of documentation. My own
writing about this subject is certainly not an attempt at a standard, just
bunches of techniques and ideas to mix and match and modify as the
situation demands. Those "standards" usually consist of either a
prefabricated table of contents or a set of rules for force-fitting the
subject into known concepts. For some reason, programmers don't write
programs by filling in a standard table of contents for programs. I'm not
sure where this idea came about that specifying software could work that
way. (Well, I've got a few ideas...)
