KR20060120296A - The method of building business relation ontology and creating semantic-based business rule by using business factor collector - Google Patents

Abstract

A method for building business relation ontology and generating semantic-based business rules by using a business factor collector is provided to enable a machine to process semantic analysis of the business rules, and permit an external application to access and reuse the business rules by using a RuleML(Markup Language)-based business rule repository and the ontology. A business factor processor(10) extracts business factors from an external repository(5), and filters and stores the extracted business factors. A business rule maker(20) generates and stores the business rules by using the collected business factors. A business rule access API(Application Program Interface)(30) permits the external application to access the business rules generated/stored by the business rule maker. The business factory processor comprises the business factor collector(11) collecting/filtering the business factors from the external repository and a business factor storing part(12) storing the collected business rules by using XML(eXtensible Markup Language).

Description

{The Method of Building Business Relation Ontology and Creating Semantic-based Business Rule by using Business Factor Collector}

1 is a block diagram of a business rule generation method according to an exemplary embodiment of the present invention.

2 is a flowchart illustrating a method of generating a business rule according to an exemplary embodiment of the present invention.

Compiled code and DBMS of Application System include business rules to efficiently handle business functions for specific purposes such as service activities and control activities. Business rules are created by a combination of business factors. Existing application system is a mixture of code and business rules, which requires a lot of system resources to be recompiled when changing business rules.

Business Rule Engine (BRE) technology, which allows code and rules to be separated to address these limitations, is in the limelight. The business rules engine provides an editor that makes processing languages and grammars very easy, shortens development time, and is easy to maintain.

However, currently available business rule engine technologies employ different methods for different architectures, data structures, and interface methods.

In addition, the business rule engine technology itself does not provide information on which application system the generated business rule is used for for what purpose, and requires a separate system for such meta information.

Also, the language and grammar adopted in the existing business rule engine technologies are a syntactic approach that cannot machine the process of defining semantic relationships in business rules. Therefore, in order to change or reuse the business rules, the human interpretation and intervention of the syntax must be supported.

Such a problem is a constraint on the intelligence of an intelligent rule base system in which an organization integrates and manages business rules.

The technical problem to be achieved by the present invention is to solve the problems of the existing technology by the machine to process the semantic interpretation of the business rules by using the business element repository (Repository) and ontology, the rule standard language RuleML-based business rules It is to provide work method ontology construction and semantic based work rule creation method using work element collection unit so that external application can access and reuse business rules by making repository.

In order to solve this problem, the present invention collects, filters, and stores refined work elements in a work element repository from various external repositories (RDB, Meta Data, etc.). Urea processing unit; A task rule preparation unit which creates a task rule using the task elements collected through the task element processor and ontology the relationships among the task elements based on the created task rules; It includes a business rule access API (Application Program Interface) that an external application can access and use the business rules created by the business rule preparation unit.

The business factor processing unit, which is a first feature of the present invention, provides a variety of connection methods with various external repositories and collects business elements from connected external repositories; It is preferable to include a work element storage unit for deriving the work elements to be used by purifying the collected work elements and storing them in the work element store.

The business element collection unit, it is preferable to configure an interface independent of the operating system to access a variety of external storage.

The work element storage unit may refine the work elements collected by the work element collection unit to suit a work environment, structure the purified work elements, and store the work elements in the work element store for reuse thereof.

The business rule creation unit which is a second feature of the present invention comprises: a business rule editor for creating a business rule using a business element of the business element store generated by the business element processing unit and storing the business rule in a business rule storage unit; A work relationship ontology which derives a relationship between work elements using a work rule created by the work rule editor to form an ontology (Business Rule Ontology); It is preferable to include a business rule storage unit for storing the business rules created in the business rule editor.

The business rule editor provides a method for creating a business rule that does not violate the previously generated business rule by using the business element in the business element store and the previously created business relationship ontology. It is a good idea to use a flowchart model that allows you to write business rules.

The work relationship ontology preferably stores and manages a relationship between work elements of a work rule generated by the work rule editor in an ontology so as not to violate a previously created work rule.

The business rule storage unit may store the business rules generated by the business rule editor using a system independent of RuleML (Rule Markup Lanaguage, a business rule definition language) proposed by the W3C.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention. As those skilled in the art would realize, the described embodiments may be modified in various different ways, all without departing from the spirit or scope of the present invention. In the drawings, parts irrelevant to the description are omitted in order to clearly describe the present invention.

Like parts are designated by like reference numerals throughout the specification.

First, a method of generating a business rule according to an exemplary embodiment of the present invention will be described in detail with reference to FIG. 1.

1 illustrates a business rule generation and method according to an embodiment of the present invention.

As shown in FIG. 1, the work rule generating method according to an embodiment of the present invention includes a work element processing unit 10 and a work rule editor 21 including a work element collecting unit 11 and a work element storage unit 12. ) And a business relationship ontology 22, a business rule preparation unit 20 including a business rule storage unit 23, and a business rule access API 30.

The work element collection unit 11 collects work elements from an external store by using an interface for accessing an external store.

The work element storage unit 12 collects only work elements corresponding to tasks to which the system is to be applied among the collected work elements, and stores the refined work elements in an XML form.

The business rule editor 21 accesses a business element in the form of stored XML to a Document Object Model (DOM), which is a memory model provided by an XML process, and creates a business rule by specifying a relationship between the business elements.

The work relationship ontology 22 parses the relationship between the work elements used in the work rule by using Mandarax, which is an open source, to derive the relationship between the work elements required for the system and to store it in the RDF (Resource Description Framework).

The business rule storage unit 23 defines the generated business rule in RuleML format.

The business rule access API 30 allows the external application to access and use the previously created business rule by accessing the written business rule (RuleML). This API allows you to use operating system independent Java.

Looking at the operation of the business rule generation method according to an embodiment configured as described above with reference to the accompanying drawings.

2 is a flowchart illustrating a business rule generation method according to an embodiment of the present invention.

The work element collection unit collects work elements using an interface provided by an external storage and the collected work elements are transferred to the work element storage unit (S1).

The work element storage unit stores various work elements collected by the work element collection unit in the work element store through the refining rule (S2) and the user's work (S3).

The business rule editor displays the business element relationship stored in the business element store and the business element relationship stored in the business relationship ontology repository in the editor so that the user can create a business rule (S4). Stores a business rule (RuleML format) to create a business rule (S5).

The work relationship ontology parses the work rules created in the work rule editor using Mandarax, an open source, ontotizes the relationships among the necessary elements and stores them in RDF (Resource Description Framework) format (S6).

The business rule access API creates an API that allows external applications to access business rules stored in the business rule repository (S7).

On the other hand, the business rule generation method according to an embodiment of the present invention as described above may be implemented as a program and stored in a recording medium (CD-ROM, hard disk, etc.) in a computer-readable form.

Although the preferred embodiment of the present invention has been described in detail above, the present invention is not limited thereto, and various other changes and modifications are possible.

According to the present invention, the work relationship ontology is stored in a semantic manner so that the machine can process the semantics, rather than the Syntax Approach process in which an existing person can intervene to understand the meaning. Because of this, knowledge and reasoning are possible. In addition, since the Semantic Base business rule repository is stored in the form of RuleML, which is a semantic web rule definition standard language, other application systems can access it through API and reuse it without writing a separate business rule code. You can eliminate duplication and reduce creation time.

Claims (8)

A task element processor for extracting, filtering, and storing a task element from an external storage to extract a task element; A business rule preparation unit for generating and storing a business rule by using the business elements collected by the business element processor; A business rule access API (Application Program Interface) that allows an external application to access a business rule created and stored by the business rule preparation unit. Business rule generation method comprising a. The method of claim 1, Business element processing unit, A work element collection unit for collecting and refining work elements from an external repository; A business element collection system consisting of a business element storage unit that stores the collected business elements as XML. The method of claim 2, The business element collection unit, Collect business elements from external storage using an interface that can access external storage. The method of claim 2, The business element store, Among the collected work elements, only the work elements corresponding to the work to be applied to the system are collected and the refined work elements are stored in XML format. The method of claim 1, Business rule making department, A task rule editor for creating a task rule from a task element; A business rule generation system comprising a business relationship ontology processing unit that stores relationships among business elements used in business rules. The method of claim 5, The business rule editor Create business rules by accessing business elements in the form of stored XML through the Document Object Model (DOM), which is a memory model provided by XML processes. The method of claim 5, Work relationship ontology, The relationship between work elements used in work rules is parsed using open source Mandarax to derive the relationship between work elements needed in the system and stored in RuleML. The method of claim 1, The business rule access API, How external applications can access the already created business rules by accessing the written business rules (RuleML).

Images