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.
> John Posada wrote:
> I don't consider Busness Requirements (BR) as important as Functional
> Requirements (FS), except to write the FS, and if whoever is writing
> the FS thinks they don't need the BR, maybe they do and maybe they
> don't. It could be that the person writing the FS knows that business
> and its requirements very well.
I think that's a pretty big assumption -- that whoever is writing the FR knows the business requirements. In my experience, the FRs have been written by coders who have no exposure to clients, domain space, or users. Or, the exposure is based on knowledge that is out dated. (In my experience.) I don't remember where I read it, but the author made the point that even if a company hires a domain expert as, say, a product manager, once that person is out of the domain space and in the software industry their knowledge ages and after a time just is not as useful as it used to be.
Even if someone does know the busienss requirements, though, they might be the only person within the organization that does. BRs, then, ensure that everyone in the company understands the context within which the FRs are written. The BRs constrain design and provide a way to measure whether fucntionality in an FR makes sense. BRs also provide information to people outside of development, such as QA, documentation, sales, and devilvery, that can be used to test, document, sell, and deploy the solution.
Now, of course, all of this depends on the nature of the software. If we're talking about an ERP, then the BRs are critical for establishing a baseline. If we're talking about Media Player, then perhaps they're not as important.
Create your own web site for FREE at http://www.freehomepage.com
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-