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.
I recently attended an interesting class "A Methodology for Writing High
Quality Requirement Specifications and for Evaluating Existing Ones" and
found some information that I thought I'd share with those of you who write
System Requirement Specification (SRS) documents. The following web page
summarizes what was in the class: http://satc.gsfc.nasa.gov/tools/index.html. (Follow the link marked
"Automated Quality Analysis Of Natural Language Requirements.")
The document basically explains the metrics used to measure the usefulness
of an SRS. However, if you are new to writing an SRS, or if you'd like more
information on creating one, you might be particularly interested in
sections 3 and 4. A high-level overview of the specification standards for
IEEE and NASA appears in section 6.
A free requirements metrics/analysis tool, Automated Requirement Measurement
(ARM), also appears. I can't vouch for the tool because I've never used it,
nor do I have need for it at this time, but I found the information in the
document very helpful.
