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.
Gene Kim-Eng wrote:
> I started writing a post along these lines, i.e., product requirements
> should
> come to development from customers (usually through Marketing/Product
> Management), and every time I've seen a "requirements spec" whose
> contents came from developers it was really a "functional description,"
> and in most cases the resulting product was a spectacular failure.
> However, upon re-reading the original post, I *think* the
> "requirements" spec being asked about actually *is* the functional
> description, that is, the product requirement proposal, the heart
> attacks and the negotiations have all taken place, now what modules
> does Engineering have to create and how will they all have to work
> together in order to do what the product requirments we just agreed
> to (or had imposed on us from above) say our product has to do?
Great point, Gene.
>From the article:
"An SRS is basically an organization's understanding (in writing) of a
customer or potential client's system requirements and dependencies
at a particular point in time (usually) prior to any actual design or
development work."
I was in a special place where I found functional descriptions being
written as if they were SRS. The article provided a creative spark for
me.
Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l
Doc-To-Help 2005 now has RoboHelp Converter and HTML Source: Author
content and configure Help in MS Word or any HTML editor. No
proprietary editor! *August release. http://www.componentone.com/TECHWRL/DocToHelp2005
---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-
