One area where many business analysts get tripped up is in confusing business rules and business requirements.  In this article we will look at what business rules and business requirements have in common and where they differ.

Difference Between Business Rules and Business Requirements

What is the difference between a business rule and a business requirement?

• Business Rules — These are statements (or conditions) that tell a person whether they can perform a specific action that relates to how the business operates.  Business rules also supply the criteria and conditions for making these decisions.
  
  
• Business Requirements — These may include what needs to be done to enable the business rule to be implemented.  In other words, a business requirement may not be valid if it contradicts or breaks an existing business rule.

Example of Business Rules

Let's step back a minute.  My Dad has three pet ducks at his home — one water duck and two land ducks.  Yes, it gets very loud sometimes.

So, here are some rules regarding the ducks' health and safety:

• Ducks cannot be given bread.  (It may choke them.)
• Ducks cannot be left unattended when swimming.  (They are poor swimmers and may drown.)
• Ducks must be given water with all meals.  (It helps them digest.)
• Ducks must have buddies.  (They're very sociable and pine when alone.)
• Ducks must be kept out of the kitchen.  (Yes, I see the irony.)

Ok, these are some of the rules we have for the ducks.

From Business Rules to Business Requirements

Now, imagine we are building a new apartment block for millionaire ducks.  No doubt there will be many requirements about their lifestyle, feeding, entertainment, and transport.  While gathering and defining these requirements, we need to consider:

• That the new apartment owners must not allow folks to give bread to the ducks.
  
  
• Whether or not a swimming pool will be built.  They can have a pool if it's a requirement but then they also need a lifeguard.

You get the idea, right?

Connection Between Business Rules and Business Requirements

Now that we've looked at how business rules work, let's look at how and where they are connected to business requirements.

1. Do business rules exist even when you can't implement a requirement?  Yes.  The business rules are independent of the requirements-gathering process.  Business rules can and must exist independently of other processes.
   
   
2. Does implementing a business requirement mean complying with the business rules?  Depends.  In general, yes, but there can be exceptions.
   
   
3. Does implementing the business requirement make it easier to comply with the business rules?  Yes.  The connection will be stronger across all business processes and will allow greater understanding of how the business rules to business requirements function.

Sample Business Rule

This is an example of business rules for a bank that's taking credit card applications over the web.

Example:  Taking Credit Card Applications Over The Web

Business Rule:  Customer must have an Email Address.

Business Requirement:  Ability for bank staff to send and receive emails to the customer.

Now if we change the business rule:

Revised Rule:  Customer must have a valid Email Address.

Note:  A second rule is required to define 'valid email address'.  For example:  An Email Address is considered Valid if it does not return an 'undeliverable' response within 60 minutes of being sent out.

Here's an additional business requirement to support the business rule:

• System will immediately send email to customer once email address is received.  The email is not batch processed but sent in response to each email received.

Note:  The smallest change in the wording of the business rule can have significant impacts on other business processes.  When testing business requirements, make sure that you consider all possible scenarios where the revised business rule will impact other parts of the business.

Recap

• Business rules describe what you may or may not do in a specific business scenario.  Business rules also give the criteria, conditions, and exceptions for making these decisions.
  
  
• Business requirements capture what a user must do to implement and/or comply with a business rule.
  
  
• You may need different sets of business requirements to implement different sets of business rules — for example, when dealing with complex business processes that have complicated conditions and exceptions.
  
  
• Business rules are independent of business requirements and shouldn't be changed to accommodate a requirement.

Be careful when changing a business rule in case it impacts how a business process functions.

In Conclusion

There is one final point I want to share.  Make sure that ownership of the business rules is properly assigned to someone — and make that person accountable.  One approach is to assign this activity to a business analyst with strong skills in document control and with the ability to push through new versions of revised business rules.

Try to find the most practical solution for managing your business rules.  At a large European bank we used a networked Excel spreadsheet and it worked very well.  All documents were version controlled and we followed a strict naming convention that made it easier to retrieve and update the rules when needed.  Tip:  In the spreadsheet, cross-reference the business rule to the business requirements so you can quickly identify where one change impacts another.

Don't get tripped up on the technology.  Once the team members understand how the documents are structured, written, and shared then you should be fine.  Also, remember to purge outdated business rules.  This means you'll have fewer documents to manage and should speed up annual audits if/when the auditors want to check your document repository.

Notes

A version of this article first appeared on Klariti.com.

# # #