AN EXPLANATION FACILITY FRAMEWORK FOR RULE-BASED SYSTEMS

2012 ◽  
Vol 21 (04) ◽  
pp. 1250013 ◽  
Author(s):  
BOJAN TOMIĆ ◽  
BORIS HORVAT ◽  
NEMANJA JOVANOVIĆ
Keyword(s):  
Natural Language ◽  
Business Processes ◽  
Management Systems ◽  
Business Rules ◽  
Business Rule ◽  
End User ◽  
Inference Process ◽  
Rule Based ◽  
Rule Management ◽  
Rule Based Systems

Rule engines, business rule management systems and other rule-based systems used today widely utilize methods, techniques and technologies from the era of expert systems. Unfortunately, this doesn't seem to be the case when it comes to explanation facilities. Nowadays, the use of explanation facilities seems more important than ever. Business rule management systems control or constrain the behavior of business processes through business rules and an explanation of the inference process intended for the end user would be more than welcome. An explanation facility framework which was created in order to remedy this situation is presented in this paper. It is written in Java and is supposed to be a generic solution for modern rule-based systems. Besides being free and open-source, it is simple to use and can generate explanations in the form of natural language like sentences. Internationalization is also supported and explanations can be saved as textual, XML or PDF reports.

Business Rules Management for Business Processes

2010 ◽  
pp. 540-563
Author(s):  
Marwane El Kharbili
Keyword(s):  
Business Process ◽  
Business Process Management ◽  
Process Management ◽  
Business Processes ◽  
Research Field ◽  
Business Rules ◽  
Business Rule ◽  
New Paradigm ◽  
Business Context ◽  
Rule Management

The power of rule-based solutions has been demonstrated over a wide range of domains and a number of industrial-scale solutions and business rules have now proven their usability in complex real world scenarios. But the use of business rules in conjunction with business process management is still a young research field. Business process management (BPM) is a new paradigm for companies to carry out their value-creating activities. Bringing agility and flexibility to business process management is one of the most pressing challenges we are facing today. In this chapter, we make the case for rule-enabled BPM by motivating the need for introducing business rules in BPM and studying the possible advantages of combining business rule management (BRM) and BPM techniques. A discussion of possible uses of business rules (BRs) in business processes (BPs) is made. Furthermore, we also propose a lifecycle for BPM-oriented business rule management, and illustrate this using a business scenario. Hence, the aim of this chapter is to provide readers with insights into issues conceptual BRM applied to BPM in a business context, not from a formal, but from a methodological point of view.

Towards a Flexible and Adaptable Modeling of Business Processes

2014 ◽  
pp. 174-183
Author(s):  
Khadhir Bekki ◽  
Hafida Belachir
Keyword(s):  
Business Process ◽  
Process Modeling ◽  
Business Processes ◽  
Business Activity ◽  
Separation Of Concerns ◽  
Business Rules ◽  
Business Rule ◽  
Rule Based ◽  
Eca Rules ◽  
Post Condition

This article proposes a flexible way in business process modeling and managing. Today, business process needs to be more flexible and adaptable. The regulations and policies in organizations, as origins of change, are often expressed in terms of business rules. The ECA (Event-condition-action) rule is a popular way to incorporate flexibility into a process design. To raise the flexibility in the business processes, the authors consider governing any business activity through ECA rules based on business rules. For adaptability, the separation of concerns supports adaptation in several ways. To cope with flexibility and adaptability, the authors propose a new multi concern rule based model. For each concern, each business rule is formalized using their CECAPENETE formalism (Concern -Event-Condition-Action-Post condition- check Execution- Number of check -Else-Trigger-else Event). Then, the rules based process is translated into a graph of rules that is analyzed in terms of relations between concerns, reliably and flexibility.

Towards a Flexible and Adaptable Modeling of Business Processes

2011 ◽  
Vol 6 (2) ◽  
pp. 57-67
Author(s):  
Khadhir Bekki ◽  
Hafida Belachir
Keyword(s):  
Business Process ◽  
Process Modeling ◽  
Process Design ◽  
Business Processes ◽  
Separation Of Concerns ◽  
Business Rules ◽  
Business Rule ◽  
Rule Based ◽  
Eca Rules ◽  
Post Condition

This article proposes a flexible way in business process modeling and managing. Today, business process needs to be more flexible and adaptable. The regulations and policies in organizations, as origins of change, are often expressed in terms of business rules. The ECA (Event-condition-action) rule is a popular way to incorporate flexibility into a process design. To raise the flexibility in the business processes, the authors consider governing any business activity through ECA rules based on business rules. For adaptability, the separation of concerns supports adaptation in several ways. To cope with flexibility and adaptability, the authors propose a new multi concern rule based model. For each concern, each business rule is formalized using their CECAPENETE formalism (Concern -Event-Condition-Action-Post condition- check Execution- Number of check -Else-Trigger-else Event). Then, the rules based process is translated into a graph of rules that is analyzed in terms of relations between concerns, reliably and flexibility.

scholarly journals A Report on the Ninth International Web Rule Symposium

AI Magazine ◽  
2016 ◽  
Vol 37 (1) ◽  
pp. 105-106
Author(s):  
Adrian Paschke
Keyword(s):  
Decision Rules ◽  
Management Systems ◽  
Inference Rules ◽  
Business Rule ◽  
Production Rules ◽  
Rule Based ◽  
Rule Management ◽  
Transformation Rules ◽  
Rule Languages ◽  
Eca Rules

The annual International Web Rule Symposium (RuleML) is an international conference on research, applications, languages and standards for rule technologies. RuleML is a leading conference to build bridges between academe and industry in the field of rules and its applications, especially as part of the semantic technology stack. It is devoted to rule-based programming and rule-based systems including production rules systems, logic programming rule engines, and business rule engines/business rule management systems; semantic web rule languages and rule standards; rule-based event processing languages (EPLs) and technologies; and research on inference rules, transformation rules, decision rules, production rules, and ECA rules. The 9th International Web Rule Symposium (RuleML 2015) was held in Berlin, Germany, August 2-5. This report summarizes the events of that conference.

scholarly journals Modeling Business Rule Parallelism by Introducing Inclusive and Complex Gateways in Semantics of Business Vocabulary and Rules

2021 ◽  
Vol 14 (1) ◽  
pp. 281-295
Author(s):  
Irene Tangkawarow ◽  
◽  
Riyanarto Sarno ◽  
Daniel Siahaan ◽  
◽  
...  
Keyword(s):  
Business Process ◽  
Free Choice ◽  
Business Processes ◽  
Formal Model ◽  
Formal Description ◽  
Object Management Group ◽  
Business Rules ◽  
Business Rule ◽  
Management Group ◽  
Object Management

The Semantics of Business Vocabulary and Rules (SBVR) standard was developed by the Object Management Group (OMG) for business purposes. SBVR is used for transformation of business vocabulary and business rules into business processes. Gateways are used for regulating the divergence and convergence of flow objects in the business process. The existing business rules in SVBR do not support all gateways in BPMN, whereas there are conditions where branching situations in business rules occur. This article introduces parallelism rules (OR rules) and complex rules to increase 50.6% usage of the existing AND rules and XOR rules in SBVR. The main contribution of this research is to introduce new formal model of inclusive gateway (OR) and complex gateway that allow parallelism and branching to be modeled using SBVR. Thus, this study increases coverage of the usage gateway in SBVR achieved 66.7%. The authors provide branching cases with various levels of complexity, i.e. nested conditions and non-free choice conditions, using the formal description of SBVR.

scholarly journals Business rules specification and business processes modeling

2009 ◽  
Vol 55 (No. 1) ◽  
pp. 20-24 ◽  
Author(s):  
I. Rábová
Keyword(s):  
Process Model ◽  
Large Scale ◽  
Business Processes ◽  
System Development ◽  
Entire Body ◽  
Business Rules ◽  
Business Rule ◽  
Policy Document ◽  
Business Policy ◽  
Body Of Knowledge

Up to date business is managed by large-scale different rules that regulate how the business acts and how it is structured. We find the rules in law, regulation, business policy document, procedures manual, system documentation, memoranda etc. These reference resources may provide the specific basis for a rule or offer a background, context or explanation of the business rule. In the recent years, it has been discovered that business rules constitute an entire body of knowledge that has not been adequately addressed in either the analysis or design phases of the information system development. Typically, business rules have been buried in the program code or in the database structures. The article deals with the business rules approach and rule technology and helps to identify the business and technical opportunities they afford to the company. It offers the business process model and its integration with business rules. This approach could provide business analysts with an essential approach to understanding, redesigning and communicating what really happens in the business processes (in agricultural area). It serves to understand the business impact of any change in small and medium-sized organizations. We use the UML notation and its business model extension.

scholarly journals Gramática de usuario final extendida para procesos de negocios

2020 ◽  
Author(s):  
◽  
Enrique Eduardo Aramayo
Keyword(s):  
Natural Language Processing ◽  
Natural Language ◽  
Language Processing ◽  
Business Processes ◽  
End User ◽  
El Sistema

El concepto proceso de negocio está estrechamente vinculado a la forma en la que una organización gestiona sus operaciones. Conocer y comprender las operaciones de una organización es un punto clave que se debe tener presente dentro del proceso de desarrollo de software. A su vez, el enfoque de desarrollo dirigido por modelos denominado MockupDD captura requerimientos usando prototipos de interfaz de usuario denominados Mockups. Los usuarios finales pueden comprender fácilmente dichos prototipos y realizar anotaciones sobre los mismos. Este enfoque se basa en ésta característica principal y a partir de la misma genera valiosos modelos conceptuales que luego pueden ser aprovechados por todos los integrantes de un equipo de desarrollo de software. Utilizar el lenguaje natural para realizar anotaciones sobre los Mockups es un aspecto clave que puede ser aprovechado. En éste último aspecto una rama de la inteligencia artificial denominada “Natural Language Processing – Procesamiento del Lenguaje Natural” (NLP) viene realizando importantes aportes vinculados al uso y al aprovechamiento del lenguaje natural de las personas. El presente trabajo de tesis propone una nueva técnica denominada “End User Grammar Extended for Business Processes – Gramática de Usuario Final Extendida para Procesos de Negocios” (EUGEBP). La misma está compuesta por un conjunto de reglas de redacción diseñada para ser aplicada sobre Mockups, y por una serie de pasos que permiten procesar dichas anotaciones con el propósito derivar procesos de negocios desde las mismas. Esto se logra a través de la identificación de los elementos que componen los procesos de negocios y de las relaciones que existen entre ellos. En esencia el presente trabajo propone utilizar las anotaciones de usuario final realizadas sobre los Mockups en lenguaje natural y a partir de las mismas derivar procesos de negocio. Las anotaciones del usuario final tienen como objetivo ayudar a describir las interfaces de usuario, pero también pueden ayudarnos a identificar los procesos de negocio que el sistema debe soportar. Mientras en analista recopila información para el desarrollo de una aplicación, implícitamente también está describiendo los procesos de negocio de la organización.

scholarly journals Business rules in knowledge management and in information systems – methodology of mining business rules and knowledge

2011 ◽  
Vol 59 (4) ◽  
pp. 267-272 ◽  
Author(s):  
Ivana Rábová ◽  
Michal Hodinka
Keyword(s):  
Information System ◽  
Information Systems ◽  
Business Processes ◽  
Business Rules ◽  
Business Logic ◽  
Business Rule ◽  
Systems Methodology ◽  
New Approach ◽  
Business Knowledge ◽  
Application Logic

Every organisation works according to principles which define business logic that controls all business processes. However, lot of basic rules of business logic are hidden in companies’ guidelines and directives, in informal techniques of experts, processes owners and specialists. The aim of all managers should be a replacement of this incoherent set of information by set of clear and unambiguous terms which describe the way the company is controlled from inside. This notion is a ground of control and administration of business knowledge.Contemporary practises in development of informational systems demand openness and availability to correspond to constant changes. With the complexity of information system grows the amount of work and its level of difficulty. The rules of business logic are transferred to application logic and implemented into a source code. Therefore, change of the business rule needs change of the code. This means compilation or replacement of the code. Adoption of this new approach would mean more effective possibilities in adjustment of the information systems to environment dynamics thanks to the change of the rules. The article deals with mining methods and subsequent structure of business rules for easier implementation into information system. Business rules base is at the same time business knowledge base which can serve for different purposes then development and use of information systems.

A Business Rules Design Framework for a Pharmaceutical Validation and Alert System

2011 ◽  
Vol 50 (01) ◽  
pp. 36-50 ◽  
Author(s):  
C. Bousquet ◽  
B. Sabatier ◽  
T. Caruba ◽  
P. Durieux ◽  
P. Degoulet ◽  
...  
Keyword(s):  
Business Processes ◽  
Clinical Information ◽  
Drug Dosage ◽  
University Hospital ◽  
Design Framework ◽  
Business Rules ◽  
Knowledge Modeling ◽  
Business Rule ◽  
Alert System ◽  
Support Design

Summary Objectives: Several alert systems have been developed to improve the patient safety aspects of clinical information systems (CIS). Most studies have focused on the evaluation of these systems, with little information provided about the methodology leading to system implementation. We propose here an ‘agile’ business rule design framework (BRDF) supporting both the design of alerts for the validation of drug prescriptions and the incorporation of the end user into the design process. Methods: We analyzed the unified process (UP) design life cycle and defined the activities, subactivities, actors and UML artifacts that could be used to enhance the agility of the proposed framework. We then applied the proposed framework to two different sets of data in the context of the Georges Pompidou University Hospital (HEGP) CIS. Results: We introduced two new subactivities into UP: business rule specification and business rule instantiation activity. The pharmacist made an effective contribution to five of the eight BRDF design activities. Validation of the two new subactivities was effected in the context of drug dosage adaption to the patients’ clinical and biological contexts. Pilot experiment shows that business rules modeled with BRDF and implemented as an alert system triggered an alert for 5824 of the 71,413 prescriptions considered (8.16%). Conclusion: A business rule design framework approach meets one of the strategic objectives for decision support design by taking into account three important criteria posing a particular challenge to system designers: 1) business processes, 2) knowledge modeling of the context of application, and 3) the agility of the various design steps.

Sign in / Sign up

Export Citation Format

Share Document