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: User documentation as product specs? From:Marv Cochrane <cochrane -at- JOCASNEXT1 -dot- EGLIN -dot- AF -dot- MIL> Date:Fri, 19 Apr 1996 12:13:32 -0500
I think that user docs as product specs is exactly the was to go.
Old Model (ideal world): A coordinated Requirements Document
followed by a coordinated Design Document followed by coding a
product followed by user docs that reflect the product.
Better Model: A coordinated User's Guide outline/draft, which is the
user requirement and the interface design; perhaps an
Adiminstrator's Guide, Interface Specification,etc--code a product
that does what the documentation promises.
Post Message: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Get Commands: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "help" in body.
Unsubscribe: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "signoff TECHWR-L"
Listowner: ejray -at- ionet -dot- net