Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Business Requirements vs Functional Requirements
Previous Previous
 
Next Next
New Post 8/12/2008 2:06 PM
User is offline Jim
15 posts
9th Level Poster


Business Requirements vs Functional Requirements 

Hello,

I always struggle with the level of detail that should be expressed for the requirements at the business/user level vs the functional level.  I was wondering if anyone had a good example, like a case study or sample project, with documents describing the business requirements for the project and the corresponding functional requirements?  I am interested to see the level at which the business/user requirements are documented and compare them to the level of detail flushed out in the functional requirements.

This forum is great by the way!  I just came apon it and there is a wealth of great information.  I will be returning often for advice and to bounce ideas around.

Thanks - Jim

 
New Post 8/13/2008 6:05 AM
User is offline Craig Brown
560 posts
www.betterprojects.net
4th Level Poster




Re: Business Requirements vs Functional Requirements 

Hey

I have two tools I think are useful.

  1. The Zachmanenterprise architecture framework.  It targets enterprise analysis but it's principles apply really well to enterprise applications requirements as well.
  2. User stories, which are popular with agile project are also useful in a broad range of application dev projects.

You'll find good info on each of these below;

User Stories

Zachman,

Zachman, RUP and UML

 

But more imprtantly, a developer reminded me today that they are the ones who need to read and understadn specs, so why not go and speak with them about what works best for them?

 
New Post 8/13/2008 4:13 PM
User is offline Tony Markos
493 posts
5th Level Poster


Re: Business Requirements vs Functional Requirements 

Hi:

Are business requirements seperate from functional requirements.  The way I learned it, there are essential requirements and non-essential requirements.  Essential requirements exist irregardless of who or what mechanism accoplishes them.  Example:  Calculate Sales Tax.   Depending upon the company, this requirement could be met  by a person, a hand-held calculator, or a computer.  It will always need to be done - but the mechanism may change.  

Now a requirement like:  "Adjust the Servo Modulator" - which is, lets say, a prerequiste to a computer program being able to "Calculate Sales Tax" is non-essential.   If, for example, we throw away the computer and go back to having a person calculate sales tax, then, we no longer need to "Adjust the Servo Modulator".

Tony

 
New Post 8/14/2008 12:15 AM
User is offline Craig Brown
560 posts
www.betterprojects.net
4th Level Poster




Re: Business Requirements vs Functional Requirements 

Tony, the way I understand this is that the different types of requirements are contextual.  That's why I like the zachman model.

Business reqs are about the business goals,functional are about the system.

This also highlights the iterative nature of requiremnts definitions - as you peel off layers more constraints and solution decisions get embedded into the specs.

Of course your data flow diagrams also handle this layered approach to reqirements pretty well.

 

 
New Post 8/14/2008 2:53 PM
User is offline Tony Markos
493 posts
5th Level Poster


Re: Business Requirements vs Functional Requirements 

Craig:

I have heard of this concept many times:  a Buiness req (function) is different that a system function.    But my experience has always been that functions is functions .  If we don't incorporate them all into a single model, how are ever going to capture a complex as-is situation where the system currently consists of functions accomplished by men and computers - and maybe even machines and electronics?

Tony

 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Business Requirements vs Functional Requirements

Community Blog - Latest Posts

Arash
Arash
Decision model and notation (DMN) is a nice way to model policies and make sure your business rules are implemented properly. Opposite to traditional approach in business rules which was the focus on the rules them selves, in DMN we start from decisions. Let’s work on a tangible example. In an employees benefits and entitlement system, you...
0 Responses
Surbhi Mahnot
Surbhi Mahnot
Prepared by MindMeister tool   Have you ever planned a project or brainstormed an idea? It takes a lot of effort to manage the collected information in a way you can easily traverse through. On occasions you find yourself occupied with a lot of questions and confusion in scenarios such as You have a lot of details to get started with...
0 Responses
Trividh Patel, CBAP
Trividh Patel, CBAP
Use case modelling is the most powerful requirements modelling technique to model solution requirements if applied correctly. I have come across many BA teams (including my own) that made lot of common mistakes in use case modelling. By avoiding the top 10 mistakes identified in this paper, BA teams can not only save lot of efforts in use...
0 Responses




Latest Articles

Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC