Rule engine debugging method and rule engine debugging system

Abstract

The invention discloses a rule engine debugging method, which comprises the following steps of compiling a simulation rule in advance according to a business rule provided by a business expert; converting the simulation rule into a rule supported by a rule engine; transferring the rule into the rule engine to be executed; and obtaining the execution result. The invention also discloses a rule engine debugging system, and provides a technology for compiling, debugging and verifying a JBoss Drools rule. Through the embodiment of the invention, technicians can conveniently perform rule compiling and debugging and can perform standardized management on codes, so that the development efficiency is improved, and the rule running correctness is also ensured.

Description

technical field [0001] The invention relates to the field of aviation technology, in particular to a rule engine debugging method and system. Background technique [0002] Traditional IT technology aims to provide enterprises with the ability to process information. With the improvement of enterprise informatization, the traditional IT architecture model can no longer meet the needs of enterprises. Many business rules are generated in the operation of enterprises, and these rules are executed through rule engines. Rules to meet the flexible and fast business requirements of enterprises. For IT systems, the writing and management of rules has become a key concern of enterprises. [0003] The expression form and expression ability of rules depend on a specific rule engine system. Developed from the inference engine, the rule engine is a component embedded in the application, which separates business decisions from application code and writes rules using predefined semantic m...

AI Technical Summary

Problems solved by technology

However, in terms of project program management, technical rules have some defects compared with Java programs, and cannot well support enterprise-level application management. The defects are as follows: 1) The technical rule namespace cannot be strictly in accordance with the package name + rule name Name and save according to the directory / file; 2) The technical rules are written freely, and the grammar check before compilation cannot be performed when writing, and errors can only be found by running; 3) The traditional Java development environment (such as Eclipse) does not support the syntax of the technical rules Checking and grammatical assistance, low development efficiency; 4) technical rule codes cannot be found through code optimization tools (such as Sonar) to find code quality problems written by rules; 5) some rule files cannot be debugged

Images