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.
Software Life Cycle/Functional Specifications-HELP!
Subject:Software Life Cycle/Functional Specifications-HELP! From:Kelly Leydon <kelly -dot- leydon -at- AMP -dot- COM> Date:Tue, 12 Mar 1996 11:03:01 -0500
Fellow Writers:
Having just returned from a Software Life Cyle meeting it has become very
clear that writing and using (or writing and NOT using) a functional
specifications document is critical to the success of any software development
project.
My questions to everyone is:
1. Can anyone recommend any current books or journals (other than STC) that
can provide leads as to what other companies are doing in the area of writing
and using functional specifications documents?
2. Is there an outline or template for writing functional specifications
documents that someone could send me?
3. What types of information goes into a functional specifications document,
is a skills matrix listing specific project items with specific skill
requirements appropriate?
4. How are changes handled, especially when you have last minute additions
or emergencies.
If these questions seem very unorganized it is because I don't actually write
the functional specs docs but I do write some of the manuals for the software
developed using (or not using) these documents and I'd like to know more about
them. I'm not actually a tech. writer either, but I play one in real life.
