Modeling Flexible Business Processes with Business Rule Patterns

Author(s):  
Milan Milanovic ◽  
Dragan Gasevic ◽  
Luis Rocha
2021 ◽  
Vol 14 (1) ◽  
pp. 281-295
Author(s):  
Irene Tangkawarow ◽  
◽  
Riyanarto Sarno ◽  
Daniel Siahaan ◽  
◽  
...  

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.


2009 ◽  
Vol 55 (No. 1) ◽  
pp. 20-24 ◽  
Author(s):  
I. Rábová

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.


Author(s):  
Marwane El Kharbili

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.


Author(s):  
Khadhir Bekki ◽  
Hafida Belachir

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.


2012 ◽  
Vol 21 (04) ◽  
pp. 1250013 ◽  
Author(s):  
BOJAN TOMIĆ ◽  
BORIS HORVAT ◽  
NEMANJA JOVANOVIĆ

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.


Author(s):  
Ivana Rábová ◽  
Michal Hodinka

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.


Author(s):  
Khadhir Bekki ◽  
Hafida Belachir

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.


Author(s):  
Dickson K.W. Chiu ◽  
Shing-Chi Cheung ◽  
Sven Till ◽  
Lalita Narupiyakul ◽  
Patrick C.K. Hung

In a business-to-business (B2B) e-service environment, cross-organizational collaboration is important for attaining the interoperability of business processes and their proper enactment. The authors find that B2B collaboration can be divided into multiple layers and perspectives, which has not been adequately addressed in the literature. Besides regular e-service process enactment, robust collaboration requires enforcement, while quality collaboration involves relationship management. These problems are challenging, as they require the enactment of business processes and their monitoring in counter parties outside an organization’s boundary. This paper presents a framework for B2B process collaboration with three layers, namely, collaboration requirements layer, business rule layer, and system implementation layer. The collaboration requirements layer specifies the cross-organizational requirements of e-service processes. In the business rule layer, detailed knowledge of these three types of process collaboration requirements is defined as business rules in a unified Event-Condition-Action (ECA) form. In the system implementation layer, event collaboration interfaces are supported by contemporary Enterprise JavaBeans and Web Services. Based on this architecture, a methodology is presented for the engineering of e-service process collaboration from high-level business requirements down to system implementation details. As a result, B2B process collaboration can be seamlessly defined, enacted, and enforced. Conceptual models of various layers are given in the Unified Modeling Language (UML). We illustrate the applicability of our framework with a running example based on a supply-chain process and evaluate our approach from the perspective of three main stakeholders of e-collaboration, namely users, management, and systems developers.


2011 ◽  
Vol 50 (01) ◽  
pp. 36-50 ◽  
Author(s):  
C. Bousquet ◽  
B. Sabatier ◽  
T. Caruba ◽  
P. Durieux ◽  
P. Degoulet ◽  
...  

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.


2013 ◽  
Vol 756-759 ◽  
pp. 1595-1599
Author(s):  
Peng Tan ◽  
Feng He ◽  
Chen Min Yan

At the moment Semantic Business Process Model (SBPM) build on the semantic annotation, the specification of process activity, the control flow between activities and business functions of process. However, the correctness of SBPM is based on technical knowledge and experiences of the model designer, which is apparently not feasible for complex and dynamic business processes. Therefore, the goal of this paper is present a formalization description which was understood by business experts and model designers, establishing a new method to verify the consistency between SBPM and requirement of enterprise. Our techniques are based on the SWRL and Business rule.


Sign in / Sign up

Export Citation Format

Share Document