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: Proposal vs Requirements/Specifications doc From:Anthony Markatos <tonymar -at- HOTMAIL -dot- COM> Date:Sat, 9 May 1998 07:45:32 PDT
Van:
I feel that Rowana Hart posted a very good article on what a proposal
is; so I will not comment on that.
What is a (software) requirements specification? I have extensive
experience creating such. A clear and concise software requirements
specification = Data Flow Diagrams (supplemented to the degree necessary
with Entity Relationship Diagrams and a Data Dictionary). Period.
Anything else is downhill (in terms of clarity and conciseness).
The poorest (and from what I have seen, most common type of)
requirements specification is a big text based document and no one can
understand. The primary purpose of these is not to clarify but to
mystify (i.e. read job security).
Tony Markatos
(tonymar -at- hotmail -dot- com)
SHOW ME YOUR DFD'S
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
