Business Rules: From SBVR to Information Systems
The ability to rapidly adapt to change is an important feature of any information system. Business rules play an important role in this dynamic as they have a high probability of being changed as time goes by. To closely follow these constant changes, the information system must be very flexible. The Semantic of Business Vocabularies and Business Rules (SBVR) is a model designed to be used by business people to communicate their business rules in a standard and formal way. SBVR and most of the business rules models do not define how to implement business rules in an information system in such a way that all flexibility needs are met. In this work we suggest an approach in with business rule implementations are confined to rules engines (independent systems designed to execute business rules) and kept separated from system executions. We will start explaining our method to identify which events in the SBVR model could lead to a violation of the defined business rules. Then we define a standard model to establish communication between business rule engines and all other information system elements. Our model uses the identified events of the first part to define when each business rule must be verified by the rule engines.
KeywordsCommunication Model Semantic Formulation Universal Quantification Business People Business Rule
- 1.Team, S.: Semantics of business vocabulary and rules (sbvr), Technical Report dtc/06-03-02, Technical report (2006)Google Scholar
- 2.Chapin, D.: Sbvr: What is now possible and why. Bus. Rules J. 9(3) (2008)Google Scholar
- 3.Cheesman, J., Daniels, J.: UML Components. Addison-Wesley, Reading (2001)Google Scholar
- 4.Bajwa, I.S., Lee, M.G., Bordbar, B.: Sbvr business rules generation from natural language specification. In: AAAI Spring Symposium: AI for Business Agility (2011)Google Scholar
- 8.De Roover, W., Vanthienen, J.: Unified patterns to transform business rules into an event coordination mechanism. In: Proceedings of the 4th International Workshop on Event-Driven Business Process Management (edBPM’10), pp. 61–73 (2010)Google Scholar