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:Dev. Cycle and the Manual From:Lief Erickson <lerickso -at- MQSOFTWARE -dot- COM> Date:Tue, 4 May 1999 11:19:39 -0500
Is it possible to have a user's manual near completion at the end of the
requirements phase of development?
My boss has done some research and found that it is possible, but it goes
against his understanding of software development. He cannot believe that
it is possible to have a user's manual complete before the code is even
written. In our organization we have five software development phases:
analysis, requirements, design, coding, and testing.
Please respond regarding the feasibility of having a user's manual near
completion at the end of the requirements phase. If it is not feasible to
have the user's manual near completion at the end of the requirements
phase, comment on where in the development cycle it can be complete. I have
my opinion, but would like to hear what the list has to say.
lerickson -at- mqsoftware -dot- com