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:Books on how to write software specs? From:71024 -dot- 3571 -at- COMPUSERVE -dot- COM Date:Mon, 18 Sep 1995 11:10:05 GMT
Your questions highlight our problem - our programmers don't really know what
they want.
My impression is that they want a descriptive document that a new programmer
could use
to get up to speed right away. What would you call this?
>From: Price, Becca
>Subject: RE: Books on how to write software specs?
>ask your audience what they expect to see in a software spec.
>BTW, do you mean spec as in requirements doc? or spec as in systems design
>spec that gets archived and only used when the program needs tweaking?
