Search

Business rules, whether defined explicitly or implicitly, are one of the primary artifacts of systems analysis. All systems analysts use business rules every day, whether or not they capture them as independent entities. They represent the decisions made at all levels within the system, whether it be a simple computation of sales commission or a complex determination of how best to route a fleet or delivery trucks. In systems analysis, facts are collected from stakeholders and in some manner codified. When business rules are not explicitly identified, their presence is reflected in program logic and database constraints. Many people consider business rules collection to be part of the data modeling process. This viewpoint is only partially correct. To ensure maximum viability, business rules should be identified and recorded first. A business rule is defined as a directive intended to influence or guide business behavior. Other definitions include statement of a constraint, a discrete operational business policy or practice or a term, fact or rule, representing a predicate. Three primary avenues exist for those desiring to implement business rules in their systems. These are programmatic, commercial rule engines and homegrown rules systems.