Forums for the Business Analyst

  Modern Analyst Forums  Business and Sy...  Requirements  Business Requirements vs Functional Requirements
Previous Previous
Next Next
New Post 8/6/2009 10:50 AM
User is offline KIERANC
22 posts
9th Level Poster

Re: Business Requirements vs Functional Requirements 

I would agree with that. The primary difference between the two levels is the "What" in Business Requirements and the "How" in Functional Requirements. "What" does the business need to do (Business Requirement) and ''How" is that that problem is going to be solved (Functional Requirement). Business Requirement never should propose or assume a solution. Functional Requirements are technically focussed and reflect the 'How' the Business Requirement can be met. In most cases Functional requirements will be best presented with a Use Case.

1. Business Requirements are the "Why" in business language. This includes the business objectives, vision and sets out the scope of a business problem that needs to be solved

2. Functional Requirements are the "What" in system language and normally include functional requirements specification, non-functional requirements specification, design constraints, data model and interface specifications - screens, reports etc.

The primary Business Analyst Role is to perform a liaison function between the business side and technology services. Business requirements are about the Business Goals, Functional requirements are about the System.

New Post 8/7/2009 8:37 AM
User is offline Tony Markos
493 posts
5th Level Poster

Re: Business Requirements vs Functional Requirements 

K states:

In summary, the business requirement document describes what the business requires, and the functional specification document describes detailed functions for which the system wil/may perform. 

Tony Markos asks:

So if the business needs to have sales tax on a purchase calculated and if this activity is performed within the computer system, then  "Calculate Sales Tax" is both a business requirement and a functional requirement? 

But if there is a business requirement to "Choose a Day to Have Raw Material X Delivered", and if this activity is to be done completely manual - without any computer system involved - then this activity is a business requirement, but not a functional requirement?

How does all of the above sound?


New Post 8/9/2009 12:11 PM
User is offline cooltoy
1 posts
No Ranking

Re: Business Requirements vs Functional Requirements 

 Hi there, was looking through the posts and I saw your above problem with Business Requirements. I have the exact same problem you have with all three of the examples bove being called Biz requirements. Any luck on which you feel was the most effective?

New Post 8/9/2009 5:43 PM
Online now... Adrian M.
741 posts
3rd Level Poster

Re: Business Requirements vs Functional Requirements 

Well - we are trying to describe words and provide some definitions and the problem is that most of these terms do not appear in the Webster Dictionary thus we all tend to have slightly different points of view as to what these things are.  Here are some thoughts...

First of all we have Requirements and BABOK® Guide, Version 2.0, states:

“A requirement is:

1. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
2. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract, standard, specification, or other formally imposed documents.
3. A documented representation of a condition or capability as in (1) or (2).”

As you can see, the definition is broad (on purpose) as there are many ways to categorize requirements depending on what you are trying to communicate.  So what we do is add various adjectives to the word "requirements" to refer to something more specific.

One thing we want to describe is the source of the requirements such as:

  • Business Requirements - these come from the line of business and are the needs of the business including what problems do we need to solve or what opportunities do we want to seize.  Ideally, the documented business requirements would be solution agnostic (but we all know that is not always the case).
  • Legal Requirements - these are requirements that come from laws which govern a specific business' operations and with which the business must comply unless they want to risk fines and even criminal charges.
  • Regulatory Requirements - these are requirements what come from bodies which regulate a specific industry and which issue rules and guidance on how companies in a specific domain must conduct itself.  While not as strong as legal requirements, non-compliance with these types of rule can lead to fines and all civil lawsuits.
  • etc.

At different times we try to categorize requirements by attributes or characteristics such as in Functional Requirements vs. Non-Functional Requirements.

  • Functional Requirements - requirements which call for action aka the people/process/system is called to "do" something (ex: respond to customer complaints, generate monthly statements, notify government of non-compliance, etc.)
  • Non-Functional Requirements - requirements which specify "properties" or characteristics that the end solution must have (ex: financial data must be secure, system must be redundant, font size must be 12 points of greater, etc.).  Note that there are also many categories of non-functional requirements such as:
    • Security Requirements
    • Performance Requirements
    • Scalability Requirements
    • etc.

The fact that a requirement is labeled one way it does not exclude it from also being referred by a different name.  For example: a "business requirement" can also be a "functional requirement", a "regulatory requirement" can also be a "non-functional" requirement.

And now a quick word on functional specifications.  Functional specifications tend to specify how the functional requirements are implemented by the solution.  The functional specification document would address functional requirements regardless of the source (business requirements vs. legal requirements, etc.).  Similarly, a supplemental specification document would address the non-functional requirements regardless of the source.

Hope this helps!

- Adrian

Adrian Marchis
Business Analyst Community Blog - Post your thoughts!
Previous Previous
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Business Requirements vs Functional Requirements

Community Blog - Latest Posts

Is Agile a reason to avoid documentation? I bet this question shows up again and again while working with product requirements. On one side, we have got long specifications, complicated diagrams, mystical technical design, too many prototypes and pretty obvious for engineers user guides (do we really need so much?). On the other side, can we actual...
The cloud-native application development has helped enterprises all around the globe reduce time-to-market, enhance performance, and develop agility and flexibility. Several enterprises are achieving these results by migrating their systems or traditional monolithic applications to the cloud. But to gain from the real benefits of cloud technology, ...
So you’ve found the perfect time and place to study and you’re ready to finally get some work done. You’ve pulled out your laptop, your textbook, and your notes, and four different highlighters. After five minutes of reading your textbook, you start zoning out and thinking about puppies. Then, you go on Tumblr and look at cut...


Upcoming Live Webinars


Copyright 2006-2021 by Modern Analyst Media LLC