Author Topic: A Navel Approach for Evaluating Completeness of Business Rules using First Order  (Read 1754 times)

0 Members and 1 Guest are viewing this topic.

IJSER Content Writer

  • Sr. Member
  • ****
  • Posts: 327
  • Karma: +0/-1
    • View Profile
Quote
Author : M.Thirumaran, E. IIavarasan, R. Manoharan, Thanigaivel.K
International Journal of Scientific & Engineering Research, Volume 2, Issue 5, May-2011
ISSN 2229-5518
Download Full Paper : PDF

Abstract - Organizations are under increasing scrutiny to develop the rules to regulate their business requirements and it is important to standardize the business rules to automate the complex process into simple logic. So several process modeling languages and rule modeling languages are evolved to modulate the organizational policies and procedures. Business rules are the constraints which influence the behaviors and also specify the derivation of conditions that affect the execution flow. These rules are form of conditional operations attached to the process to give data result. These systems implement business rules that are restructured when organizations change the data to the varying business needs. When these rules are changed, it must be efficient to provide a decision based on the given constraints or based on business requirements. The correct decision logic are verified by evaluating or validating the completeness of the business rule. More often the rules can associate with another rule to derive business logic, but these rules are not complete enough to determine the computability of business logic. So it is necessary to check whether the rule is complete, this can be proved when the rules are interpreted with first order logic. This paper provides standard approach to evaluate the completeness of business rules by formulating the rules using first order logic. Applying these strategies introduces a structured approach and management aspects within rules by focusing on rule sources which are important for the process goal and providing a meaningful rule structure. It points out the necessity and also the real possibilities to establish new facilities for manipulation of business rules into the software development process. This can give rise increase in the performance of the legacy system.
Index Terms - Completeness, Rule Execution, Business process, Business rules, Business Rules Approaches, First Order Logic, Business rules, First Order logic, Completeness algorithm.

1. INTRODUCTION
Many efforts are already made to promote and integrate business rules modeling and management tools into business processes automation. Being ready for execution as a part of business process management applications business rules and the business rules approach still seem to lack a common methodological ground and support. Especially the fact that, before business rules can be modeled and managed they first need to be captured and extracted from different sources is often left to analystís  intuition. Well- known possible sources to look at to identify business rules are, among others: process documentation, source code or implicit sources like internal problem-solving knowledge of the employees involved in this process. But since not many enterprises capture their business rules in a structured, explicit form like documents or implicit software codes, they need to be identified first, before being captured and managed. Here the question about how to identify the potential sources of business rules emerges. Though some of them may seem obvious, like legal restrictions, standards or mandatory best practices, some are implicitly included within the elements involved in the process. On the other hand, many enterprises capture their business processes in business process models, providing a structured view for further analysis and management. Business is performed according to rules. They make an important and integral part of each information system (IS) by expressing business logic, constraints on concepts, their interpretation and relationships. Therefore is relevant to pay special attention to business rules in development of information systems. Defined rules of structure and behavior are captured in the models of structures, states, processes and other IS models. In general, models can be expressed using graphic symbols, text and formulas. Modeling constructs are grouped into a variety of diagram types by various aspects, for example, process, static structure, states. These rules are need to check for consistency and completeness. In order to facilitate the completeness of the rules we are using First Order Logic.

2. LITERATURE SURVEY
Business Process Management (BPM) is an established discipline for building, maintaining, and evolving large enterprise systems on the basis of business process models. A business process model is a flow-oriented representation of a set of work practices aimed at achieving a goal, such as processing a customer request or complaint, satisfying a regulatory requirement, etc. The Business Process Modeling Notation (BPMN) is gaining adoption as a standard notation for capturing business processes. The main purpose of business process models generally, and BPMN models in particular, is to facilitate communication between domain analysts and to support decision-making based on techniques such as cost analysis, scenario analysis, and simulation Chun Ouyang [1] proposed an acyclic BPMN model, or an acyclic fragment of a BPMN model, falls under the class if it satisfies a number of semantic conditions such as absence of deadlock. He applied Petri net analysis techniques to statically check these semantic conditions on the source BPMN model. According to Michael zur Muehlen [2], Business Processes are sets of activities that create value for a customer. While research in Business Process Management initially focused on the documentation and organizational governance of processes, organizations are increasingly automating processes using workflow systems, and are building elaborate management systems around their processes. Such management infrastructures integrate modeling, automation, and business intelligence applications. The inclusion of compliance management activities is a logical next step in governing the business process life cycle. Josef Schiefer [3] says that Business Process Management (BPM) systems are software solutions that support the management of the life cycle of a business process. For the execution of business processes, many organizations are increasingly using process engines supporting standard-based process models (such as WSBPEL) to improve the efficiency of their processes and keep the testing independent from specific middleware. A major challenge of current BPM solutions is to continuously monitor ongoing activities in a business environment and to respond to business events with minimal latency. One of the most promising concepts that approaches the problems of closed-loop decision making and the lack of gaining real-time business knowledge is the concept of Complex Event Processing (CEP), The system automatically discovers and analyzes business situations or exceptions and can create reactive and proactive responses, such as generating early warnings, preventing damage, loss or excessive cost, exploiting time-critical business opportunities, or adapting business systems with minimal latency. Claire Costello [4] says A business process as a complete set of end-to-end activities that together create value for the customer. Business process management is the ability to orchestrate and control the execution of a business process across heterogeneous systems and allow users to view the components of an infrastructure from a process view rather than set of applications and databases. Anca Andreescu [5] says every organization operates according to a set o business rules. These may be external rules, coming from legal regulations that must be observed by all organizations acting in a certain field, or internal rules which define the organizationís business politics and aim to ensure competitive advantages in the market. Starting from the previous observations, it is obvious the important role that business rules play within the development process of a software system. Milan Milanović1 [6] proposed that BPM languages have limited support for representing logical expressions, business vocabularies, and business rules, which severely limits their flexibility and expressivity. To address these challenges, he integrated business rule modeling constructs of the REWERSE Rule Markup Language (R2ML) with the Business Process Modeling Notation (BPMN), resulting in a rBPMN proposal. Olegas Vasilecas [7] says Business rules make an important and integral part of each information system (IS) by expressing business logic, constraints of concepts, and their interpretation and relationships. Therefore it is relevant to pay special attention to business rules in development of information systems. Rules related to domain structure and behavior are presented in data, states, processes and other IS models. Taking into account that rules are expressed in several models, there is a risk that overall specification is inconsistent. Unambiguous models are crucial for the successful implementation of IS models transformation and finally code generation tasks. Therefore it is necessary to check consistency among related rules models. The problem of models inconsistency can be solved by using of formal or partially formal models with constraints. However formal models are often too complex to be used in practice. Semi-formal models are widely used, but constraints used in such a models often are suitable only for one model and relationships among models are not defined. He suggests extending of IS approach based on semi-formal models and constraints, by adding the consistency rules for IS models. Anis Charfi [8] applied the divide and conquer principle to web service composition by explicitly separating business rules from the process specification. The combination of the business rules approach with the process-oriented composition solves a twofold problem. First, he provided a solution to the problem of dynamic adaptation of the composition. In fact, current standards for process-based web service composition are not capable to deal with the flexibility requirements of composite web services. Second, business rules are important assets of a business organization that embody valuable domain knowledge. So, it is no longer acceptable to bury them in the rest of the composition. Bruno de Moura Araujo [9] proposed Business rules (BR) are declarations which constrain, derive and give conditions for existence, representing the knowledge of the business. BRs are not descriptions of a process or processing. Rather, they define the conditions under which a process is carried out or the new conditions that will exist after a process has been completed. BR can be represented using Semantics of Business Vocabulary and Rules (SBVR).  SBVR is appropriate to be used by business experts, since it allows the representation of business vocabulary and rules using controlled natural language.

Read More: Click here...