DMCA
ILOG’s position on Rule Languages for Interoperability
| Citations: | 1 - 0 self |
BibTeX
@MISC{Mcclintock_ilog’sposition,
author = {Colleen Mcclintock and Christian De Sainte Marie},
title = {ILOG’s position on Rule Languages for Interoperability},
year = {}
}
Share
 |
 |
 |
 |
||
OpenURL
Abstract
languages is mostly focused on Business Rules and Production Rules. Business Rules are usually defined as atomic and highly specific and structured statements that constrain some aspect of a business, process or activity, and that control or influence its behaviour. Business rules are widely used to implement regulations, procedures, business policies and other potentially volatile decisions that impact a business, a process or an activity. In this paper, we refer more specifically to executable business rule statements for use in some rule-driven system. The most noticeable characteristic of executable business rules is that their execution results necessarily in executing some actions: specifically, the actions that are required to enforce the underlying business policy (or non-executable business rule). From an inference point of view, the true assertion that is inferred from a business rule is thus always that some specific actions must be executed. In other words, business rules specify which actions can or have to be executed when certain conditions are met. A car-renting business can for instance have a policy that “the driver must be 21 or older”: the corresponding executable business rule – that is, the rule that makes the policy enforceable – is that “rentals must be denied to drivers below 21”. As a consequence of that characteristic, business rules are often represented as production rules when they are meant to be directly executed by an automated system: a production rule is an independent statement of programming logic that specifies the execution of one or more actions in the case that its conditions are satisfied; it is usually defined in the context of being executable by an inference engine. In production rule form, our example above would read: “if the driver in a car-rental request is less than 21 year old, then reject the car-rental request”. Production rules are the most convenient way to represent most business rules, as well as the most widely supported by existing inference engines, including the main commercial ones. See some examples of business rules in production rule form in appendix 1.
Keyphrases
business rule production rule rule language inference engine car-rental request production rule form executable business rule business rule statement non-executable business rule inference point certain condition volatile decision convenient way specific action structured statement true assertion underlying business policy car-renting business policy enforceable business policy independent statement main commercial one noticeable characteristic rule-driven system execution result automated system
