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:Why docs aren't tested From:Mark Levinson <mark -at- SD -dot- CO -dot- IL> Date:Wed, 10 Aug 1994 10:23:53 IDT
[Documentation] can't be tested until the software is done. So,
it can't be frozen before the software is frozen'
The reason this is a hard sell is that most software managers don't
really see the documentation as part and parcel of the product
** Another reason in some places is that by the time the software
is frozen the development process has eaten up not only its own
slack time but the hoped-for documentation time as well,
and the product has got to get out the door PDQ or else.
Each day's delay attributable to fine-tuning the
documentation is a very visible immediate horror, while the
future problems from inaccurate documentation are still well
over the horizon. (In fact, in a properly underorganized
company, they may never trickle back to HQ at all...)
_________________________________________________________________________
Mark L. Levinson | E-mail: mark -at- sd -dot- co -dot- il
Summit EDA Technologies | Voice: +972-9-507102, ext. 230 (work),
Box 544 | +972-9-552411 (home)
46105 Herzlia, ISRAEL | Fax: +972-9-509118
_________________________________________________________________________
If God intended one space between sentences, why do we have two thumbs?
_________________________________________________________________________
