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:Functional specifications document From:geoff-h -at- MTL -dot- FERIC -dot- CA Date:Mon, 26 Jan 1998 13:11:07 -0600
A friend who's just beginning a software project asked for
advice on creating a "functional specifications document".
I gave him an overview of what I knew about "blueprints"
for a software design, but was honest enough to tell him
that I didn't know the details. Can anyone provide
relatively focused information on preparing one of these
specifications? He's indicated that he's willing to read a
journal article (or my summary), but not a book.
Please send your responses to me directly (I'm too far
behind on digests to be able to spot all the references
there); I'll summarize to the list in about a week (earlier
if the replies taper off before then).
--Geoff Hart @8^{)} geoff-h -at- mtl -dot- feric -dot- ca
Disclaimer: Speaking for myself, not FERIC.
