Re: Software Requirements Specification

["Gene Kim-Eng" <techwr -at- genek -dot- com>]

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?

Gene Kim-Eng


----- Original Message ----- 
From: "Bill Swallow" <techcommdood -at- gmail -dot- com>


Ah, I view requirements as a proactive thing and not a reactive thing.
By the time you get requirements from development, it's too late.


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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- 

To unsubscribe send a blank email to 
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40infoinfocus.com

Send administrative questions to lisa -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.