Business rules de ne and constrain various aspects of the business, such as vocabulary, behavior and organizational issues. Enforcing the various rules of the business in information systems is not straightforward, because di erent mechanisms exist for the transformation of business rules into model driven implementations, leading to partial solutions for process management, data constraints, audit constraints, etc. In this paper, we examine if and how business rules, not only data rules, but also process rules, timing rules, authorization rules, etc., can be expressed in SBVR and translated using patterns into a more uniform event mechanism, such that the event handling could provide an integrated enforcement of business rules of many kinds.
Control-Flow Rule: Precedence of activities
<Activity2> may … only after <Activity1> (Conditional allowance)
Activities: o Activity1: Trainee attends car classes o Activity2: Trainee takes practical session Business Rule: #4: A trainee may take a practical session only after that trainee has attended car classes On start (<Activity2>) : if not completed (<Activity1>) then notify (Rule #) On start (trainee takes practical session) : if not completed (trainee attends car classes) then notify (#4) various business rule types, leading to partial solutions for data constraints, process mangement and audit constraints. Event handling provides a more uniform enforcement of business rules of many kinds, not only data rules, but also control- ow rules and organizational rules.
To this end, we provide a pattern mechanisme to transform SBVR business rules into event-driven enforcement rules and noti cations. For each type of rule we de ne a general template. The rule template generates a set of EventCondition-Actions rules once a business rule is de ned. The Event-ConditionAction rules are equivalent to the SBVR Business rules but have the advantage that they make clear when they have to be checked. Example templates for Data aspects(integrity constraints, derivations rules), Control ow aspects(precedence of activities (see gure 1)) and organizational aspects(Authorization rules) are provided.
Conclusion By transforming the business rules into Event-Condition-Action rules we provide a more uniform event mechanism, such that event handling can provide an integrated enforcement of business rules of many kinds.