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: Is it just me? S/W doc question From:Mark Jordan <mjordan -at- TSSC -dot- CO -dot- NZ> Date:Fri, 30 May 1997 08:34:37 +1200
We have exactly the same problem. Because of the need to begin the
documentation process before the software development finishes (assuming
that at some point software development does finish!) we find that changes
occur and we are not notified of them.
Part of problem, of course, is that the document is based largely around the
user interface, and this is only a portion of the software developers arena.
In addition the developer does not reliably think about changes and there
affect on the UI and the user.
We do try to convince our software designers of the need to let us know of
changes, and for their part, I'm sure they try. Unfortunately, it is still
essential for the technical writer to go looking.