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.
Jennifer Delmerico [mailto:Jennifer -dot- Delmerico -at- TSTNET -dot- COM]:
> I think I could improve the manner in which the docs are
> written, but I'll
> need some proof that things should be changed. Can anyone
> recommend any
> books or articles that I can read about how to write specs
> and requirements?
Yes. Practical Software Requirements: A Manual of Content and Style, by
famous techwr-l celebrity Benjamin L. Kovitz. I know I've plugged this book
here before, but I'm bringing it up again on the basis of new evidence. Yes,
Ladies and Gentlemen, this time, I've actually READ IT.
Ben has a lot of insight into the topic, and he takes things as close to
first principles as is reasonable and prudent. And, you know what? It's not
nearly as boring as you probably think!
