Search ::     [ Advanced ]
Username:   Password: Auto login next time?  

RuleXpress: The business tool for expressing and communication business rules.

AttainingEdge : World Class Training For Critical Business Innovations


 

 

 

 

     LAM ARCHIVES ...
untitled

Business Rules vs. Business Requirements
Are you confused?

I am asked this all the time.  What is the difference between a business rule and a business requirement?  It is simple, really.  Business rules are lists of statements that tell you whether you may or may not do something, or give you the criteria and conditions for making a decision.  One factor of a business requirement is what you need to do to enable the implementation of and compliance with a business rule.

Believe it or not, my daughter will be turning thirteen this summer.  She is definitely a twelve year old going on twenty-one.  One Saturday morning during breakfast, we got into a conversation about what some of her rules will be when she is old enough to go out on her own (I say around sixteen or seventeen... her dad would say twenty-five).

Here are my rules to my daughter:

  • Must not stay out past 10:30 pm.  (Of course there were grumbles.)

  • Must not let a new driver (this includes all her friends) drive you home without my permission.  (I got one of those looks and an "Oh!  Mooommmm!")

  • I must know where you are at all times.  (I got an "Oh, boy!" and a big sigh!)

  • Must not go in a car with someone I don't know.  (I got a big fat "WHAT!  You might not know all my friends when I am sixteen, you know.")

  • Must not go anywhere with a stranger.  (I got an "I am not stupid, you know!")

So I said those are the rules -- take it or be prepared to stay home through your teenage years.

She thought about it for a little while and said ok.  However, she said she has one requirement.  She needs a car!

There you go — she requires a car in order to comply with the rules.  

Here are some questions for the readers:

  1. Do the rules exist even when you can't implement the requirement?  Absolutely.

  2. Will implementing the requirement mean all the rules will be complied with?  Not for sure.

  3. Will implementing the requirement enable easier compliance with the rules?  Yes.

  4. Is this the ONLY feasible requirement to enable compliance with this set of rules?  No.

How does this relate to your projects?

Consider the following examples:

Example 1:  License Inspection Project

Business Rules:

Rule 1:

A Driver of a Vehicle must have a valid Driver's License.

Rule 2:

A Driver's License must be considered valid if all of the following are true:

      • The Driver's License belongs to the Driver.

      • The Expiry Date of the Driver's License is later than the Inspection Date.

      • The physical proof is produced within 24 hours of the Inspection Date.

Possible business requirements to enforce these rules:

  1. Police officer to inspect driver's license.

  2. Scanner to read driver's license for validity.

  3. Card reader for driver to insert driver's license when driving through a checkpoint.

Any one of these requirements can enforce the above 2 rules with different degrees of efficiency and effectiveness.  Which business requirements are appropriate largely depends on the corporation's business strategies, business risk tolerance, and budget.

The important point to remember is that the business rules are what we need to guide behavior.  However you choose to implement or enforce those rules is a different matter.  Do not confuse the two.

Example 2: Order Entry System

Business Rule:

A Customer must have an Email Address.

Business Requirement:

Capability to enter email address for a customer.

This can easily be implemented by providing a GUI to enter an email address.

Now consider a simple change to the business rule:

Business Rule:

Revised Rule:  A Customer must have a valid Email Address.

A second rule is required to define 'valid email address'.

Rule 2:  An Email Address must be considered Valid if an email sent to Email Address does not return 'undeliverable' within 60 minutes.

Additional Business Requirement to support revised rule:

Capability to immediately send email to customer after email address is received.

Notice how the change of one word in a business rule can mean different or additional requirements.  Keep in mind one affects the other.

The question I want to leave you with now is:  What do you need to manage?  The rules or the requirements?

Just Remember...

Plainly speaking, here are some of the main things you need to remember:

  • Business rules are lists of statements that tell you whether you may or may not do something or that give you the criteria and conditions for making a decision.

  • Business requirements are what you need to do to enable the implementation of and compliance with business rules.

  • There can be many different alternative business requirements to implement/enforce a set of business rules.

  • Business rules are what they are.  They shouldn't change to fit the business requirements.

  • A change in a rule can mean different or additional requirements.


standard citation for this article:
Gladys S. W. Lam, "Business Rules vs. Business Requirements," Business Rules Journal, Vol. 7, No. 5 (May 2006), URL:  http://www.BRCommunity.com/a2006/b290.html  

January 2012
Top 10 Mistakes Business Analysts Make When Capturing Rules — Mistake #9: Not Having a Business Rule Methodology

October 2011
Top 10 Mistakes Business Analysts Make When Capturing Rules — Mistake #8: Not Having the Right Skill Set

August 2011
Top 10 Mistakes Business Analysts Make When Capturing Rules — Mistake #7: Not Having a Well-Defined Scope

June 2011
Top 10 Mistakes Business Analysts Make When Capturing Rules — Mistake #6: Not Having Strong Sponsorship

April 2011
Top 10 Mistakes Business Analysts Make When Capturing Rules — Mistake #5: Not Having the Right Business Infrastructure

February 2011
Top 10 Mistakes Business Analysts Make When Capturing Rules — Mistake #4: Not Managing Business Rules from the Start

January 2011
Top 10 Mistakes Business Analysts Make When Capturing Rules — Mistake #3: Assume Everyone Knows What a Business Rule Is

December 2010
Top 10 Mistakes Business Analysts Make When Capturing Rules Mistake #2: Not Focusing on Terminology

November 2010
Top 10 Mistakes Business Analysts Make When Capturing Rules Mistake #1: Treating Business Rules Initiatives Simply As IT Projects

May 2006
Business Rules vs. Business Requirements

October 2004

Organizing A Pile of Rules

 

June 2004

Family Reunion... Facilitated Session… Having the Right People Doing the Right Things

 

November 2003

Family Reunion ... Facilitated Session -- Same Difference

 

September 2003

A Relationship between Process and Business Rules

 

July 2003

The Hidden Secrets about a Business Rule

 

May 2003

Plainly Speaking: What Is A Rule?

 

May 1998

Business Knowledge ~ Packaged in a Policy Charter Policy Charter as a Deliverable

 

 

 about . . .

 GLADYS S.W. LAM


Gladys S.W. Lam is an expert IT project manager, consultant, and seminar leader. She has extensive experience in various business contexts, including BPR, strategic IT planning, and managing and implementing information systems. She works closely with companies in developing Business Rule solutions.

Ms. Lam has gained a reputation for fostering positive professional relationships with principal and support staff in projects. Her wide business and technical knowledge is invaluable in achieving consensus among project participants. She has also developed an impressive track record of completing projects on time and within budget. She is committed to achieving quality results within available resources.

 

 

 





[ Home ] [ Staff ] [ About BRC Publications ] [ Editorial Feedback ] [ About BRCommunity ]
[ Contributor's Guidelines ] [ Privacy Policy ] [ Technical Support ]