RE: Where are the limits of Business Requirements Documents / Software Requirements Specifications?

["David Artman" <david -at- davidartman -dot- com>]

   I imagine it's company/culture-specific, but I usually see:

   * Marketing Requirements = What the function must do; e.g., "Allow for
   printing 2D bar codes on shipping labels".

   * Business Case = Whether the function is worth the cost; will it earn
   revenue or increase market share or loyalty.

   * Functional Specification = How the software will execute the
   requirement; UI elements to support it; messages, erros, and logging;
   tools develpment; user stories/use cases/mockups.

   * Project Plan = Usually a collection of several of the above tied to a
   release; time lines, resource and space allocations; factory floor
   reworks; steering group/project team/project sponsor/black-belt.



   Sometimes there's a tiny bit of overlap between MR and FS, but usually
   only if a customer has specific request a certain way of doing the
   function (e.g., "Make a button that shuts down all of your
   company's software, so I don't have to click fifteen close buttons").
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Doc-To-Help: The Quickest Way to Author and Publish Online Help, Policy & Procedure Guides, eBooks, and more using Microsoft Word | http://bit.ly/doctohelp2015

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

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


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

Looking for articles on Technical Communications?  Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions?  Search our public email archives @ http://techwr-l.com/archives