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: Writing a functional spec? From:Ron Miller <RSMH -at- AOL -dot- COM> Date:Wed, 26 Apr 1995 21:40:38 -0400
I wouldn't go near the IEEE or DoD documents (no offense intended) unless you
require them for government work.
Contact someone in your company who has written a functional spec and simply
use that as a model. Short of that, find someone you know in the software
industry and ask for a copy of the table of contents.
A good functional spec may contain:
*The purpose of the software
*The intended audience
*Every proposed screen in the program
*Briefly list every function, menu, field etc.
*Discuss network requirements (as appropriate)
*List License requirements
This is by no means meant to list every subject you should include, but it
should get you started.