WO2015137641A2 - Système de gestion de règles commerciales ayant une structure de règles hiérarchique et procédé de représentation associé - Google Patents

Système de gestion de règles commerciales ayant une structure de règles hiérarchique et procédé de représentation associé Download PDF

Info

Publication number
WO2015137641A2
WO2015137641A2 PCT/KR2015/001778 KR2015001778W WO2015137641A2 WO 2015137641 A2 WO2015137641 A2 WO 2015137641A2 KR 2015001778 W KR2015001778 W KR 2015001778W WO 2015137641 A2 WO2015137641 A2 WO 2015137641A2
Authority
WO
WIPO (PCT)
Prior art keywords
rule
business
rules
hierarchical
task
Prior art date
Application number
PCT/KR2015/001778
Other languages
English (en)
Korean (ko)
Other versions
WO2015137641A3 (fr
Inventor
조도연
현창환
김성민
Original Assignee
(주)이노룰스
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by (주)이노룰스 filed Critical (주)이노룰스
Publication of WO2015137641A2 publication Critical patent/WO2015137641A2/fr
Publication of WO2015137641A3 publication Critical patent/WO2015137641A3/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Definitions

  • the present invention relates to a business rule management system having a hierarchical rule structure and a method thereof, and more particularly, through a rule performing a method for determining a business requirement (business rule) that is hierarchically associated with each other.
  • the present invention relates to a system and method for performing optimal work results using the result of a rule as an input value of a function.
  • a system As a means of developing a conventional work system, a system has been constructed by hard coding work requirements (business rules) through a specific programming language that depends on system specifications. In this case, when a change in work requirements or a system specification occurs, a work process occurs in which the source code of the program is adjusted / modified or the program language is changed and rewritten.
  • BRMS BUSINESS RULE MANAGEMENT SYSTEM
  • BRMS manages business rules to be defined separately from the program, and provides results to the program through interpretation / execution service by the rule engine.
  • BRMS manages business rules separately and enables development, management, and execution of business logic independently from the application.
  • Korean Patent Publication No. 10-2013-0055683, "Editing and Compiling Business Rules,” refers to a technology for converting and editing business rules using graph-based operations.
  • the technical problem to be achieved by the present invention is a table format, decision table to accommodate the rules of various business requirements, so that IT non-experts can easily and conveniently express the business rules of the company in a non-programming manner through an Excel-like user interface. It is to provide a rule expression template such as format, branch format, and flow format.
  • the rule processing request for the task is input
  • a rule generation and management unit that develops, manages, and generates the rule generated as a specific rule template according to need; and a rule repository in which the generated rule is stored; and the contents of the rule.
  • a rule cache unit configured to store a result value processed using the rule;
  • a business rule management system having a hierarchical rule structure is provided, including; and a rule engine for executing a task by executing a rule capable of processing a task corresponding to the rule processing request.
  • each rule template is composed of an execution region and a condition region, and has a hierarchical association structure, so that a rule template corresponding to an Nth depth in the hierarchical structure has an N + 1th depth in the execution region and a condition region. It can be characterized by performing execution processing request to determine the condition and return through the result value through the rule call expression and the expression (rule expression) using various other arithmetic / logic / character / date functions and operators. .
  • the rule is a modularized function, and each rule is hierarchically related to each other according to the associated work flow, and the result value through the lower rule is input to determine the condition of the upper rule or to generate the result value.
  • the rule may be characterized as being able to call or be called other rules.
  • the rule generation and management unit expresses the task hierarchically, expresses a rule required for the task execution through a corresponding attribute and a version through a list, or generates a new rule including a function generated by a user or has already been generated. It provides an editing tool for editing the rule, and can be characterized in that the generated rule in the form of a specific template.
  • the rule engine searches for a corresponding rule in the rule store and, when there is a required result value among the result values of the cache unit, applies the rule to the searched rule. It may be characterized by generating a result value for the processing request.
  • the rule template is composed of a decision table template in Excel format so that the contents can be modified and edited by copying the contents between the rule templates as needed, and the contents created in the Excel program can be used when generating the rule template. It can be characterized by that.
  • the decision table template includes a condition area and a return area
  • the condition area includes a condition expression (rule expression) that is a comparison factor and a series of comparison values to be compared with the result of the condition expression.
  • the condition may be configured as a column, and the rows of the return region may express values satisfying each condition by comparing the result of the conditional expression with the comparison value.
  • a business rule management system to create and manage a rule (rule) for performing a task determination method, through which the task is resolved, a) a rule processing request for the task is input And b) selecting a business processing rule that performs the rule processing request among the rules; and c) analyzing an association relationship between the rules stored in the rule repository and associated with the business processing rule. Searching for rules; And d) generating a result for the rule processing request through the business processing rule by using a result value of the rule associated with the business processing rule stored in the rule cache unit.
  • a business rule management method having a hierarchical rule structure composed of a rule template having a format of.
  • the business processing rule and the rules associated with the business processing rule are each composed of functions, and have a hierarchical association structure with each other according to the business flow, and individual rules may call or be called other rules, respectively.
  • the result value of the rule of the hierarchy may be used as an option value of the function.
  • the rule template is composed of a hierarchical association structure consisting of an execution region and a condition region, so that a rule template corresponding to a depth of Nth in the hierarchical structure is a rule template corresponding to a depth of N + 1th.
  • the rule processing request may be performed using a result value as an input value of a function of the execution region or a condition value of the condition region.
  • a part of the rule template is composed of a decision table template in Excel format so that the contents can be modified and edited by copying the contents between the rule templates as needed, and when the rule template is generated from the contents created in an Excel program. It can be characterized by being available for.
  • the decision table template includes a condition area and a return area
  • the condition area includes a condition expression (rule expression) that is a comparison factor and a series of comparison values to be compared with the result of the condition expression.
  • the condition may be configured as a column, and the rows of the return region may express values satisfying each condition by comparing the result of the conditional expression with the comparison value.
  • the present invention separates various business rules from a program and manages them as business rules through systematic objectization, provides various management functions such as rule history management and rule verification and services through APIs to provide flexibility to applications by providing flexibility and speed. This can enable business operations, reduce system development and maintenance efforts, and reduce costs.
  • the present invention can increase the speed of business decision by caching the rule content stored in the rule repository and the result value of the intermediate step in the memory in order to provide fast processing performance in the memory without access to the DB when performing the execution. It has an effect.
  • the present invention can be reflected as a new rule by a simple operation when creating a similar rule, there is an effect that can conveniently manage a large amount of rules by providing a variety of search and batch modification functions.
  • BRMS InnoRules Business Rule Management System
  • FIG. 3 is a diagram illustrating an example of an InnoRules Server system configuration.
  • 5 is a diagram illustrating a flow rule.
  • 6 is a view showing a variable rule.
  • 10 is a diagram illustrating a CallBack rule.
  • 11 is a diagram for explaining the priority of conditions.
  • Fig. 12 is a diagram for explaining common component rules of processing steps.
  • FIG. 13 illustrates a rule implementation and a service process through a business rule management system having a hierarchical rule structure according to an embodiment of the present invention.
  • FIG. 14 is a diagram illustrating a rule-based business operation process through a business rule management system having a hierarchical rule structure according to an embodiment of the present invention.
  • 15 is a diagram showing the configuration of a business rule management system having a hierarchical rule structure according to an embodiment of the present invention.
  • 16 is a flowchart illustrating an operation of a business rule management system having a hierarchical rule structure according to an embodiment of the present invention.
  • 17 is a diagram illustrating a screen configuration of a rule development and editing environment according to an embodiment of the present invention.
  • FIG. 18 illustrates a rule processing request for a task using hierarchical rule associations according to an embodiment of the present invention.
  • FIG. 1 is a conceptual diagram illustrating a business rule management system having a hierarchical rule structure according to the present invention.
  • Business rule management system having a hierarchical rule structure of the present invention performs business rule management in the following configuration.
  • Rule Builder is a configuration for developing rules in the client and stores the rules and edited rules developed through the server's Rule Builder server in the Rule Repository.
  • Rule Builder Server is in charge of rule development and receives / requires rule builder request and changes / informs rule information and contents to rule DB.
  • Rule Engine is a module that executes rule service by receiving application request.
  • Rule Repository is a rule repository that manages all data related to rules such as rule information and contents, users and items. Rule Repository can be included in the server.
  • Rule Server sends Rule service request through TCP to Rule Engine.
  • Web-server Adapter is a module that delivers Rule Service to Web Service request.
  • Rule Engine Manager is a module that monitors the status of Rule Engine and Rule Builder Server and manages environment options.
  • a user consists of an administrator and a normal user.
  • -Administrator User management, top-level task management, and general user authorization can only be performed with administrator privileges.
  • Item management, rule creation and management can be performed according to the authorized authority.
  • -DataBase Configures the connection information for the period database to be used in the DB query rule.
  • SAP R / 3 Configures the connection information for the SAP server to be used in RFC (Remote Function Call) rules.
  • -Table Rule A rule that executes and operates the rule expression of each row of the condition region to execute the execution region for the condition region row whose result is True, and returns the result.
  • -Loop rule A rule that executes the iteration logic.
  • -DB query rule A rule that uses Dynamic SQL to query the Legacy DB.
  • -Variable rule A rule that branches to a rule with the corresponding name according to a parameter (see the result after execution).
  • Call Back rule Calls and executes a module in a normal program by passing arguments and returns the result.
  • This rule expresses the work flow in the flow chart format.
  • -Relational Map Displays the relationship between the upper rule calling the selected rule and the lower rules calling in the selected rule so that the calling relationship of rules can be easily identified.
  • Rule Reporter Automatically generates rule reports of various levels.
  • -Rule Tracer It shows the execution path of rule by showing the result of rule execution step by step including sub-rules.
  • Consistency Checker Verifies the contradiction between the rules transferred from the development system to the production system and the existing rules of the production system.
  • -Rule History Manages migration history when rules are transferred from development system to operation system.
  • FIG. 3 is a diagram illustrating an example of an InnoRules Server system configuration.
  • FIG. 4 is a diagram illustrating a table rule.
  • 5 is a diagram illustrating a flow rule.
  • 6 is a view showing a variable rule.
  • FIG. 7 is a diagram illustrating a loop rule.
  • FIG. 8 is a diagram illustrating a decision table rule.
  • Decision Table rule is a rule that consists of the same condition limited to rule type that is mainly used in data with strong data. It is used for rules including subrules. It is used for rules that are frequently used for work because the contents of defined rules exist in memory. do.
  • Decision Table rule consists of condition area and return area, and the value of return area (or the result of executing rule expression) is returned to upper rule as a result of execution of Rule of condition area (here rule is expressed by ⁇ ). .
  • a Decision Table rule consists of one conditional expression (rule expression), which is a comparison factor, and a series of comparison values to be compared with the result of this conditional expression, and each condition (column) of the conditional area is compared.
  • Rule expression conditional expression
  • This is a rule template that returns the return of the rows that satisfy each condition.
  • Each condition may specify whether or not to execute the condition expression of the condition through the execution decision expression. If the execution decision is not described or if the execution result is “True”, the condition is used to determine the execution of the rule expression in the return area. Otherwise, the condition is excluded.
  • the rule return will have the default value (or the result of executing the rule expression) specified in the default return area, and will be ignored if there is a result.
  • the rule expression in the same line of the return region corresponding to the first conditional line that satisfies is executed, and the rule return has a single-valued form. There must be one condition that always satisfies, and the rule return must always have one result (row).
  • rule expression is executed in which all satisfying condition rows are in the same row of the corresponding return area, and the rule return has a multivalued format. If you specify a multivalued format and do not check the execution of all satisfying conditions, the rule expression in the same row of the return region corresponding to the first satisfying conditional row is executed, and the rule return has a multivalued format. In the multivalued form, rule return may not have a value because there are no conditions satisfied, and a plurality of result values may have a plurality of result values (rows).
  • the data type of the return item can be a character type, numeric type, or logical type.
  • the rule expression result is a basic single value type and must have a value of one of the logical values "T" or "F".
  • the rule return will have the result of executing the default value specified in the default return area or the rule expression described in the default return area.
  • the default rule expression can use any rule expression that conforms to the rules of the rule expression in the return region.
  • FIG. 9 is a diagram illustrating a data rule.
  • 10 is a diagram illustrating a CallBack rule.
  • 11 is a table rule and illustrates the priority of conditions.
  • condition column When processing Decision and Table rules, the condition column performs evaluation from left to right and top to bottom, and the value of the execution region (rule call expressions and functions) for the row corresponding to the condition where the result of the AND operation between each column is “T”.
  • the result of the rule expression is that the use of the rule expression in the condition and execution region cell is possible up to N-Depth, and returns).
  • Each condition column of condition area or each column of execution area is unlimited in number and can be added or decreased through Rule Builder.
  • FIG. 13 illustrates a rule implementation and a service process through a business rule management system having a hierarchical rule structure according to an embodiment of the present invention.
  • the business rule management system 100 having a hierarchical rule structure according to the present invention expresses various business rules as rules through duplicate exclusion and systematic objectization, and various functions such as rule verification and history management of BRMS and services through API. This gives you the flexibility of your application.
  • a rule (business rule) is generated by referring to a work guide, a work experience, an existing program, an existing DB, and using a rule integrated management tool of the business rule management system 100 having a hierarchical rule structure of the present invention. Develop and test to create, manage, and operate rules.
  • the generated rule is stored in the rule store (ie, the rule store 120).
  • the rules are stored with hierarchical relationships (object, common, and centralized) according to the business relationship.
  • the rule engine executes it and returns the result.
  • FIG. 14 is a diagram illustrating a rule-based business operation process through a business rule management system having a hierarchical rule structure according to an embodiment of the present invention.
  • the rules may be registered in various rule template formats.
  • Rules registered in the rule repository can be searched for rules and managed rule history, and by analyzing rule associations, it is possible to grasp rule ranges related to changes in business requirements and respond quickly to business changes.
  • the rule in the present invention is compatible with the Excel program and can be edited by copying as needed.
  • the contents created in the Excel program can be used for rule generation.
  • the business rule management system 100 having a hierarchical rule structure according to the present invention may generate and display various rule reports on a screen of rule development, operation, and processing.
  • 15 is a diagram showing the configuration of a business rule management system having a hierarchical rule structure according to an embodiment of the present invention.
  • Business rule management system 100 having a hierarchical rule structure of the present invention is a rule generation and management unit 110, rule storage unit 120, rule processing request unit 130, rule engine 140, rule cache unit And 150.
  • the rule generation and management unit 110 develops, edits, manages, and generates a rule required for business processing into a specific rule template as needed.
  • the rule generation and management unit 110 may express a rule development and management editing process in a GUI format on the display device.
  • the rule generation and management unit 110 may express the property and the version of the rule required to perform a task through a list, and create a new rule including a function generated by a user or modify and edit an already generated rule. can do.
  • the rule storage unit 120 stores the rules generated through the rule generation and management unit 110.
  • the rule processing request unit 130 is an API (Application Programming Interface) corresponding to various programming languages that receive a rule processing request for a task and deliver it to a rule engine and return a result of executing the rule engine. For example, Java, C / C ++, COBOL, etc.
  • the rule engine 140 performs task resolution using a rule capable of processing a task corresponding to a rule processing request.
  • the rule cache unit 150 stores the result value processed using the rule.
  • the rule engine 140 may generate a result for the corresponding rule processing request by using a result value of the related rule stored in the rule cache 150.
  • 16 is a flowchart illustrating an operation of a business rule management system having a hierarchical rule structure according to an embodiment of the present invention.
  • step S100 a rule processing request is input.
  • the user of the present invention requests a rule processing request to the business rule management system 100 having a hierarchical rule structure when a task to be solved occurs.
  • the rule processing request includes a start step in which a user processes a corresponding task through a task program on a display screen.
  • Step S110 is a step of selecting a business processing rule that performs the rule processing request from the rule.
  • the business rule management system 100 having a hierarchical rule structure of the present invention selects a rule capable of performing the task, and executes a rule to be executed in association with S120. Navigate through.
  • the rule that can perform the task is displayed on the screen as a rule template in the format desired by the user.
  • Step S120 is a step of searching for a rule associated with the business process rule by analyzing an association between the rules stored in the rule repository.
  • the business rule management system 100 having a hierarchical rule structure analyzes the contents of a rule template capable of performing a desired task and searches for and finds out an associated rule included in a function of the corresponding rule template. Through the step S130 to use the cache, or additional execution to generate and return the result of the rule requested by the user.
  • a result of the rule processing request is generated through the business processing rule using the result value of the rule associated with the business processing rule stored in the rule cache unit.
  • the result of the processing of the task desired by the user is generated by replacing the result of the associated rule constituting the function of the rule template capable of performing the task desired by the user with the function of the rule template.
  • the business processing rule and the rules associated with the business processing rule are each composed of functions, and have a hierarchical association structure according to the business flow, and individual rules may call or be called other rules (that is, rules Can include other rules in the function, and can be included in functions of other rules), and the result value of the rules of the lower layer can be used as option values of the function.
  • the rule template has a hierarchical association structure composed of an execution region and a condition region.
  • Execution area means the function of the task performed by the rule template, and condition area means the result value of the associated rule constituting the function.
  • N is the rule template corresponding to the depth of Nth
  • the result value of the rule template corresponding to the depth of N + 1 is the input value of the function of the execution region or the condition value of the condition region.
  • 17 is a diagram illustrating a screen configuration of a rule development and editing environment according to an embodiment of the present invention.
  • Screen 1 is a screen composition expressing hierarchical business structure.
  • the business rule management system 100 having a hierarchical rule structure according to the present invention can easily identify and define hierarchical hierarchical structure between tasks by displaying tasks hierarchically and systematically. To be displayed.
  • Screen 2 is a screen for displaying a rule list.
  • the business rule management system 100 having a hierarchical rule structure according to the present invention may display the rule of the minimum unit constituting the rule component in a list by displaying attributes and versions.
  • Screen 3 is for creating and editing rules.
  • the business rule management system 100 having a hierarchical rule structure of the present invention provides an intuitive and familiar user environment such as an Excel form so that a user can create and edit rules more conveniently and simply.
  • Screen 4 is a screen for selecting a rule template.
  • the business rule management system 100 having a hierarchical rule structure of the present invention may convert the generated or edited rule into various types of rule templates so that the user can intuitively grasp the corresponding rule.
  • the rule template may be a table rule, a variable rule, a DB query rule, a call back rule, a loop rule, an RFC rule, a flow rule, or the like.
  • FIG. 18 illustrates a rule processing request for a task using hierarchical rule associations according to an embodiment of the present invention.
  • the business rule management system 100 having a hierarchical rule structure of the present invention creates a rule for processing a discount rate into a plurality of rule templates, and a condition area of each rule template. Or by writing rule expressions in execution region cells.
  • the curly brace notation used in the illustration is an expression that calls another rule.
  • rule template 10 is a rule template in which a rule for processing a discount rate calculation is displayed in the form of a Decision Table rule
  • rule template 20 is a rule template located at the first depth position of rule template 10.
  • the rule template 20 is a rule for ⁇ day additional discount rate ⁇ constituting the function of the rule template 10.
  • the rule for ⁇ VIP or not ⁇ needs a rule for ⁇ customer information check ⁇ , and the rule for ⁇ monthly performance check ⁇ needs a rule for ⁇ performance aggregate ⁇ .
  • rule for ⁇ customer information check ⁇ and the rule for ⁇ performance aggregation ⁇ become association rules having the second depth of rule template 10.
  • the rule template 30 is a rule template in which a rule on ⁇ service application ⁇ is expressed in the form of a table rule
  • the rule template 40 is a flow rule in which a rule on ⁇ transmission record level ⁇ is expressed in the form of a flow rule.
  • the invention can also be embodied as computer readable code on a computer readable recording medium.
  • the computer-readable recording medium includes all kinds of recording devices in which data that can be read by a computer device is stored. Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage, and also in the form of carrier wave (transfer over the Internet). It includes what is implemented.
  • the computer-readable recording medium can also be distributed over computer devices connected over a wired or wireless communication network so that the computer-readable code is stored and executed in a distributed fashion.
  • the present invention has the potential to provide a business rule management system that has a hierarchical rule structure in which IT professionals can easily and conveniently express corporate business rules in a non-programming manner through an Excel-like user interface. have.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Strategic Management (AREA)
  • Economics (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Tourism & Hospitality (AREA)
  • Quality & Reliability (AREA)
  • Operations Research (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Educational Administration (AREA)
  • Software Systems (AREA)
  • Development Economics (AREA)
  • Game Theory and Decision Science (AREA)
  • Data Mining & Analysis (AREA)
  • General Engineering & Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Devices For Executing Special Programs (AREA)

Abstract

L'objectif de la présente invention est de produire un modèle de représentation de règles pour non-professionnels IT afin de représenter facilement et commodément des règles de tâches d'entreprise d'une manière non-programmée par l'intermédiaire d'une interface utilisateur similaire à Excel. Pour cela, l'invention propose un système de gestion de règles commerciales (BRMS) ayant une structure de règles hiérarchique, le système de gestion de règles commerciales (BRMS) générant et gérant des règles pour exécuter un procédé de détermination concernant des tâches, et résolvant les tâches à l'aide des règles. Le système de gestion de règles commerciales (BRMS) ayant une structure de règles hiérarchique comprend : une unité de demande de traitement de règles destinée à recevoir une demande de traitement de règles pour une tâche ; une unité de gestion et de génération de règles pour développer et gérer des règles et pour générer des règles en tant que modèle de règles spécifique si besoin ; un espace de stockage de règles destiné à stocker les règles générées ; une unité de cache de règles destinée à stocker une valeur de résultat traitée à l'aide des règles ; et un moteur de règles destiné à résoudre une tâche à l'aide d'une règle pouvant traiter une tâche correspondant à la demande de traitement de règles.
PCT/KR2015/001778 2014-03-11 2015-02-24 Système de gestion de règles commerciales ayant une structure de règles hiérarchique et procédé de représentation associé WO2015137641A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2014-0028140 2014-03-11
KR20140028140 2014-03-11

Publications (2)

Publication Number Publication Date
WO2015137641A2 true WO2015137641A2 (fr) 2015-09-17
WO2015137641A3 WO2015137641A3 (fr) 2017-05-18

Family

ID=54072553

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2015/001778 WO2015137641A2 (fr) 2014-03-11 2015-02-24 Système de gestion de règles commerciales ayant une structure de règles hiérarchique et procédé de représentation associé

Country Status (2)

Country Link
KR (1) KR20150106365A (fr)
WO (1) WO2015137641A2 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106201537A (zh) * 2016-07-18 2016-12-07 浪潮通用软件有限公司 一种数据处理方法及装置
CN108229907A (zh) * 2017-12-06 2018-06-29 链家网（北京）科技有限公司 一种基于表达式引擎的规则变更方法和系统
CN110647546A (zh) * 2019-09-18 2020-01-03 北京明略软件系统有限公司 第三方规则引擎生成方法及装置

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021172953A1 (fr) * 2020-02-27 2021-09-02 주식회사 이노룰스 Système de gestion de règles commerciales
KR102150911B1 (ko) * 2020-02-27 2020-09-03 주식회사 이노룰스 비즈니스 룰 관리 시스템
KR102150910B1 (ko) * 2020-02-27 2020-09-03 주식회사 이노룰스 비즈니스 룰 관리 시스템
KR102187321B1 (ko) * 2020-02-27 2020-12-08 주식회사 이노룰스 비즈니스 룰 관리 시스템
KR102187322B1 (ko) * 2020-02-27 2020-12-08 주식회사 이노룰스 비즈니스 룰 관리 시스템
KR102150909B1 (ko) * 2020-02-27 2020-09-03 주식회사 이노룰스 비즈니스 룰 관리 시스템
KR102217937B1 (ko) * 2020-02-27 2021-02-23 주식회사 이노룰스 비즈니스 룰 관리 시스템
KR102164607B1 (ko) * 2020-02-27 2020-10-13 주식회사 이노룰스 비즈니스 룰 관리 시스템
KR102337271B1 (ko) * 2020-07-28 2021-12-09 주식회사 이노룰스 Brms 기반 글로벌 생산 관리 시스템

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001005654A (ja) * 1999-06-24 2001-01-12 Nec Corp ビジネスルール管理装置
KR20020085005A (ko) * 2001-05-04 2002-11-16 주식회사 이네트 룰기반의 워크플로우를 지원하기 위한 워크 플로우 체인생성방법
US8069129B2 (en) * 2007-04-10 2011-11-29 Ab Initio Technology Llc Editing and compiling business rules
JP5715905B2 (ja) * 2011-08-01 2015-05-13 株式会社エヌ・ティ・ティ・データ ビジネスプロセス／ビジネスルール実行システム、ビジネスプロセス／ビジネスルール実行方法及びプログラム

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106201537A (zh) * 2016-07-18 2016-12-07 浪潮通用软件有限公司 一种数据处理方法及装置
CN108229907A (zh) * 2017-12-06 2018-06-29 链家网（北京）科技有限公司 一种基于表达式引擎的规则变更方法和系统
CN110647546A (zh) * 2019-09-18 2020-01-03 北京明略软件系统有限公司 第三方规则引擎生成方法及装置

Also Published As

Publication number Publication date
KR20150106365A (ko) 2015-09-21
WO2015137641A3 (fr) 2017-05-18

Similar Documents

Publication Publication Date Title
WO2015137641A2 (fr) Système de gestion de règles commerciales ayant une structure de règles hiérarchique et procédé de représentation associé
WO2021008017A1 (fr) Procédé d'apprentissage de fédération, système, dispositif terminal, et support d'informations
WO2011122724A1 (fr) Système exécutant une inspection de code pour effectuer une inspection de code sur les codes sources abap
WO2010087566A1 (fr) Système d'analyse de documents
WO2018097407A1 (fr) Procédé et système de partage de fonctions erp définies par l'utilisateur
WO2017213281A1 (fr) Procédé de désidentification de données volumineuses
WO2014065444A1 (fr) Système de collaboration utilisant un réseau public ouvert
WO2021157897A1 (fr) Système et procédé pour la compréhension et l'extraction efficaces d'une entité multi-relationnelle
EP3241102A1 (fr) Système électronique doté d'un mécanisme de gestion d'accès, et son procédé de fonctionnement
WO2014027836A1 (fr) Procédé et dispositif électronique pour éditer du contenu
WO2017111197A1 (fr) Système et procédé de visualisation de mégadonnées pour l'analyse d'apprentissage
WO2022234876A1 (fr) Procédé permettant de fournir des informations sur un article et appareil correspondant
WO2022050551A1 (fr) Système de fourniture de services juridiques et procédé associé
WO2022030670A1 (fr) Système et procédé d'apprentissage profond par cadre utilisant une requête
WO2019245247A1 (fr) Procédé de gestion d'objet utilisant un identifiant de trace, un appareil pour celui-ci, un programme informatique pour celui-ci, et un support d'enregistrement stockant un programme informatique de celui-ci
WO2023163405A1 (fr) Procédé et appareil de mise à jour ou de remplacement de modèle d'évaluation de crédit
WO2022203387A1 (fr) Système et procédé de développement intégrés, pour plate-forme d'interface utilisateur, comportant un compilateur de sources
WO2018097361A1 (fr) Procédé de création de fonctions erp définies par l'utilisateur et système informatique d'exécution associé
WO2019098428A1 (fr) Procédé de fourniture de fonction erp faisant appel à une table de gestion extensible spécifique à un utilisateur, et système de fourniture de fonction erp permettant la mise en œuvre dudit procédé
WO2016195330A1 (fr) Programme, procédé, appareil et interface utilisateur permettant de prendre en charge différents formats de fichier de document exécutables
WO2010120063A2 (fr) Procédé de gestion de documents xml permettant d'annuler sélectivement une opération antérieure spécifique et système l'utilisant
WO2024048827A1 (fr) Appareil électronique et procédé de gestion de test d'application associé
WO2021172953A1 (fr) Système de gestion de règles commerciales
WO2024048866A1 (fr) Procédé et système de visualisation de données cibles
WO2015126043A1 (fr) Procédé d'affichage de publicité, procédé de fourniture de publicité, et appareil appliqué à ceux-ci

Legal Events

Date Code Title Description
NENP Non-entry into the national phase in:

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 19.01.2017)

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15761720

Country of ref document: EP

Kind code of ref document: A2

122 Ep: pct application non-entry in european phase

Ref document number: 15761720

Country of ref document: EP

Kind code of ref document: A2