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:Scott Miller <smiller -at- PORTAL -dot- COM> Date:Tue, 4 May 1999 13:42:54 -0700
<<<<<
> Is it possible to have a user's manual near completion at the end of the
> requirements phase of development?
>>>>>
In many cases, the requirements phase just describes what the software needs
to do. The engineers use that to create the program, including the GUI, so
in that case, it's impossible to finish the doc at the requirements stage.
However, let's say that the requirements phase includes the complete GUI and
functional spec. (And then he woke up.) There is always something that will
change, which is only fair. Imagine if you were held to your original
outline for a document. OK, maybe your outlines never change, but mine
always do. I recognize that developers work the same way, you plan as well
as you can, and then reality hits.
