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.
Where are the limits of Business Requirements Documents / Software Requirements Specifications?
Subject:Where are the limits of Business Requirements Documents / Software Requirements Specifications? From:Uwe Ziegenhagen <ziegenhagen -at- gmail -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Sun, 25 Jan 2015 21:51:28 +0100
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
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?
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