Business Rules Analysis is one of the techniques specified in the BABOK guide that Business Analysts should know. Business Rules Analysis generally consists of two parts.
- The first is documenting and validating business rules (especially if the business does not have formal and agreed upon repository).
- The second is assessing how the business rules impact the effort you are undertaking. While business rules are not requirements, they can imply requirements and constrain the proposed solution.
IIBA Business Rule Definition
A business policy is a non-actionable directive that supports a business goal. A business rule is a specific, actionable, testable directive that is under the control of an organization and that supports a business policy. Particularly complex rules, or rules with a number of interrelated dependencies, may be expressed as a decision table or decision tree.
The key thing for most business analysts to understand about business rules is that they generally should not be constrained by business unit, process, or application. Business rules should be independent of any application and should apply universally (or nearly so). Some business rules may be geographically driven, especially if they represent laws that the business must comply with.
- The Wikipedia entry on Business Rule
- Article – Business Analysis with Business Rules, by Ronald Ross. ModernAnalyst (2011).
- Blog Post – Business Analysis Technique #4 – Business Rules Analysis, by David Kohrell. TAPUniversity (2011).
- Blog Post – Business Analysis Technique: Business Rules Analysis at the LearningTree Perspectives on Project Management blog (2010)
- Blog Post – Business Rules entry at the AgileModeling site, by Scott Ambler.