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: Dev. Cycle and the Manual From:Bob Gembey <bob -at- SUPERNOVA -dot- NL> Date:Wed, 5 May 1999 08:55:46 +0200
I suppose, if it's possible for software developers to "complete" a
software product, it's possible to for complete a manual. But software is
never finished -- there are always bugs, or enhancements, or improvements
that can be made, and the same is true of the manuals. I'd be thrilled if
the manual and the product which it describes are both at the same state
and the one accurately reflects the other (functionality, locations/names
of icons, buttons, menu's, etc.). I'm satisfied if they're close.
<<Is it possible to have a user's manual near completion at the end of the
requirements phase of development?>>
