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

[Uwe Ziegenhagen <ziegenhagen -at- gmail -dot- com>]

âHello,

a few days ago I was part of a discussion of what BRDs are to provide. A
few colleagues argued that BRDs not only define the business' requirements
but also what the solution (which the BRD describes) will provide.

For me a BRD describes the requirements (even the name says so), not the
actual deliverables.

To define what the actual deliverables for ths BRD are, other documents
such as design specifications (from the software vendor) must be prepared
and discussed with the business.

The following statement from IEEE 830 describes it well in my opinion:
"Establish the basis for agreement between the customers and the suppliers
on what the software product is to do." (not: will do)



What is your opinion on this?

Thanks,


Uwe
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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