ClickCease

Perspective 4 – Business Rules (Part 2)

In my last post we discussed that a business rule defines or constrains how business operations work.  The outcome of the rules should either be true or false. Identify them in a variety of ways.

Now that you have context about business rules, let’s discuss how to store these rules once you have identified them.

Technique 7: How to store business rules

There are many different tools you can leverage to store business rules. You can use a database container, excel spreadsheet, and even a Word document. No matter what mechanism you use here are some items you should consider to store regarding the business rules:

  • Unique Identifier – each business rule should have a unique ID assigned to it. This is an easy way to track the business and trace the business rules to processes, requirements, architectural or test documentation.
  • Business Rule – once you have the unique ID then document the business rule description. We discussed how to write business rules in Part 1.
  • Conditions – certain conditions must be met in order for the business rule to be invoked, or fired. In that event, include that information as well, as that information is very telling.
  • Ownership – this attribute describes what area of the organization, or business, owns the rule.
  • Date Added – it’s important to capture when you add the business rule to the database/application.
  • Modified Date – it’s important to capture the last time the business rule was modified, as rules can change over time.
  • Status – this attribute describes what is the status of the business rule? For example, is the business rule “active” or “suspended”? In some cases, you may not want to remove the business rule from the application/database. This is because of the chance it could be used later, or may be needed for audit purposes.
  • Traceability – the business rule should trace back to an activity in a process, or the process overall, as stated above when we discussed the “unique identified”. If there is a requirement documents the business rules should trace back to the requirements documents. In addition, the business rule may trace back to test scripts or technical documentation. Business rules may also link to other business rules.
  • Revision History – as you make updates to business rules, or as you add them to the application, you will want some type of version history. Again, depending on the tool you leverage this may happen organically, but in the case you need to store these manual this is an item to consider for audit trail purposes. It will help to track who has touched the data and why.

Here is an example of what this may look like in an Excel table.

Other Attributes Required

Depending on the application available to you in your organization, you may need to capture other attributes.  If you are using an excel spreadsheet the above considerations are a great place to start.  This list is not an all-inclusive list and your needs may require the storing of more attributes.

Store Your Rules & Requirements in iGrafx

If you are using a tool like iGrafx, the platform stores these rules or requirements. You can identify and easily report all corresponding relationships in a dynamic manner.

As you can see, business rules are very powerful.  They advise how the organization conducts business.  The rules also help mitigate risk to the organization to ensure compliance with policies, rules, or regulations.  It’s critical to ensure they are written well and stored correctly. This can provide a lot of insight, and knowledge, to all who consume them.

Related Content

Blog

Process Simulation Technology: Know Before You Go 

By Max Smith, Senior Director Product Marketing  “Change is the only constant in life.” Although Greek philosopher Hera...
Blog

Navigating the Seas of Business Process Excellence: MSC UK’s Journey 

Introduction to MSC  In the realm of shipping, MSC stands tall as the world's largest shipping container company, managing a...
Blog

Transforming Chaos into Order: A Practical Approach to Process Framework Adoption 

By Kim Scott, iGrafx Senior Consultant  Act 1: In the beginning, there was Chaos… and it was good?  You can find all sort...