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 requirements, take II From:Geoff Hart <geoff-h -at- MTL -dot- FERIC -dot- CA> Date:Fri, 13 Feb 1998 07:56:52 +0000
A colleague just found another interesting document that should prove
interesting to anyone who must write (or live with) functional
requirement docs:
IEEE. 1994. IEEE recommended practice for software requirements
specifications. Institute of Electrical and Electronics Engineers,
New York, N.Y. IEEE Std 830-1993.
It's pricey for nonmembers, but it looks good based on my quick skim.
(That's _not_ a book review... I haven't had a chance to do more than
glance over it. Perhaps someone who's used it can elaborate?)
--Geoff Hart @8^{)}
geoff-h -at- mtl -dot- feric -dot- ca
