Business Rule: Jump To Navigation Jump To Search
Business Rule: Jump To Navigation Jump To Search
Contents
1Introduction
2Categories
3Real world applications and obstacles
4Formal specification
5See also
6References
7External links
Introduction[edit]
Business rules tell an organization what it can do in detail, while strategy tells it how to
focus the business at a macro level to optimize results.[citation needed] Put differently, a strategy
provides high-level direction about what an organization should do. Business rules provide
detailed guidance about how a strategy can be translated to action.
Business rules exist for an organization whether or not they are ever written down, talked
about or even part of the organization's consciousness. However it is a fairly common
practice for organizations to gather business rules. This may happen in one of two ways. [citation
needed]
Categories[edit]
According to the white paper by the Business Rules Group, [1] a statement of a business rule
falls into one of four categories:
The most basic element of a business rule is the language used to express it. The very
definition of a term is itself a business rule that describes how people think and talk about
things. Thus, defining a term is establishing a category of business rule. Terms have
traditionally been documented in a Glossary or as entities in a conceptual model.
The nature or operating structure of an organization can be described in terms of the facts
that relate terms to each other. To say that a customer can place an order is NOT a business
rule, but a fact. Facts can be documented as natural language sentences or as relationships,
attributes, and generalization structures in a graphical model.
Every enterprise constrains behavior in some way, and this is closely related to constraints
on what data may or may not be updated. To prevent a record from being made is, in many
cases, to prevent an action from taking place.
Derivations
Business rules (including laws of nature) define how knowledge in one form may be
transformed into other knowledge, possibly in a different form.
This lack of consistent approach is mostly due to the cost and effort required to maintain the
list of rules.[citation needed]
While newer software tools are able to combine business rule management and execution, it
is important to realize that these two ideas are distinct, and each provides value that is
different from the other. Software packages automate business rules using business logic.
The term business rule is sometimes used interchangeably with business logic; however the
latter connotes an engineering practice and the former an intrinsic business practice [citation needed].
There is value in outlining an organization's business rules regardless of whether this
information is used to automate its operations.
One of the pitfalls in trying to fill the gap between rules management and execution is trying
to give business rules the syntax of logic, and merely describing logical constructs in a
natural language. Translation for engines is easier, but business users will no longer be able
to write down the rules.
Formal specification[edit]
Business rules can be expressed using modeling approaches such as Unified Modeling
Language, Z notation, Business Process Execution Language, Business Process Modeling
Notation, Decision Model and Notation or the Semantics of Business Vocabulary and
Business Rules (SBVR).[citation needed]
Business rules encoded in computer code in an operational program are known as business
logic.
Similar to how Business Risks can be structured as:
If <condition(s)> Then <consequence(s)>
a Business Rule can be structured as:
When <condition(s)> Then <imposition(s)> Otherwise <consequence(s)>