CN113159618A - Rule engine design method and device with separated technical view angles - Google Patents

Abstract

The invention provides a method and a device for designing a rule engine with separated technical visual angles, which relates to automatic program design and comprises the following steps: determining a full-scale library management rule according to the variable library and the function library; determining a transaction end management rule according to a mapping relation between the interface field and the variable library; determining a data end management rule according to a mapping relation between a data table and a variable base; determining a module management rule according to the module definition and the module trend; establishing a policy management rule according to the module management rule; determining a processing flow management rule according to the strategy management rule; and determining a business parameter management interface with separated business technology visual angles according to a full-scale management rule, a transaction end management rule, a data end management rule, a module management rule, a strategy management rule and a processing flow management rule. The technical scheme of separating business and technical views is provided, the business view and the technical view are distinguished, and the authority and responsibility range of business personnel and technical personnel is defined.

Description

Rule engine design method and device with separated technical view angles

Technical Field

The invention relates to the technical field of computer data processing, in particular to a rule engine design method and device with separated technical view angles.

Background

This section is intended to provide a background or context to the embodiments of the invention that are recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.

The rule engine is mainly aimed at independently, persistently and effectively managing the business rules, but lacks an efficient and convenient method for managing the business rule resources.

In the design of using the angle for business personnel, the existing rule engine mainly meets the requirements of the graphical and natural language-like form display of business logic and several universal business rule type designs, does not have reasonable and complete overall business logic display and adjustment, and is difficult to generate more comprehensive and deep auxiliary driving benefits for understanding and using the rule engine by the business personnel. This ultimately results in business personnel having difficulty participating in the activities of developing and maintaining business rules using the rules engine.

In the design of using this angle for the technician, the rule engine has no hard limit and must use the business rules, and the technician can often implement some more complex technical functions by directly writing codes. Furthermore, in principle, the rules engine also does not subdivide the well-defined boundaries between business and technical personnel. Because the business-oriented related design has the defect that business personnel can not really participate in actual development and maintenance, technicians have to bear the responsibility of the business personnel to develop and maintain business functions in the form of business rules as much as possible. From the technical point of view, it is not favorable to exert the ability of the technician to the maximum extent, is the action of reducing the development efficiency, and the retrieval and maintenance of the relevant business rules are cumbersome and heavy. In short, the tool is not suitable for the user, and the development resources are wasted, which is a frustrating problem.

Therefore, how to provide a new solution, which can solve the above technical problems, is a technical problem to be solved in the art.

Disclosure of Invention

The embodiment of the invention provides a rule engine design method with separated technical views, provides a technical scheme with separated service technical views, distinguishes service views from technical views, and defines authority and responsibility ranges of service personnel and technical personnel, and the method comprises the following steps:

determining a full-scale library management rule according to the variable library and the function library;

determining a transaction end management rule according to a mapping relation between the interface field and the variable library;

determining a data end management rule according to a mapping relation between a data table and a variable base;

determining a module management rule according to the module definition and the module trend;

establishing a policy management rule according to the module management rule;

determining a processing flow management rule according to the strategy management rule;

and determining a business parameter management interface with separated business technology visual angles according to a full-scale management rule, a transaction end management rule, a data end management rule, a module management rule, a strategy management rule and a processing flow management rule.

When the method for designing a rule engine with separated technical views provided by the embodiment of the present invention is implemented specifically, in an embodiment, determining a full-scale library management rule according to a variable library and a function library includes:

establishing a variable library according to the variable definition table and the variable enumeration value definition table;

establishing a function library according to the basic function and the compound function;

establishing an internal execution logic library of the module according to the basic logic and the customized logic;

and determining a full-scale library management rule according to the variable library, the function library and the module internal execution logic library.

When the method for designing a rule engine with separated technology views provided by the embodiment of the present invention is implemented specifically, in an embodiment, a variable library is established according to a variable definition table and a variable enumeration value definition table, and the method includes:

defining variables according to the variable names, the Chinese descriptions and the data types, and determining a variable definition table;

configuring corresponding Chinese description for the fixed value definition of the variable, and determining a quantity enumeration value definition table;

and establishing a variable library according to the variable definition table and the variable enumeration value definition table.

When the method for designing the rule engine with separated technical view angles is specifically implemented, in one embodiment, a variable library supports quick display of variable-processing logic and maps the variable-processing logic to a corresponding processing item, and a mode of using the technical variable first and then processing the technical variable is adopted; when a technical variable is added, a variable name, Chinese description and a data type are defined, and a processing variable requirement is generated in a project to-be-handled list.

When the method for designing a rule engine with separated technology views provided by the embodiment of the present invention is implemented specifically, in an embodiment, the establishing a function library according to a basic function and a complex function includes:

pre-developing functions including simple operation and character processing, expanding by combining service requirements, and determining a basic function;

combining the basic functions according to a set analysis format to determine a composite function;

and establishing a function library according to the basic function and the compound function.

When the method for designing a rule engine with separated technology view points provided by the embodiment of the present invention is implemented specifically, in an embodiment, the method for establishing a module internal execution logic library according to a basic logic and a customized logic includes:

taking general execution logic in the module as basic logic;

taking the customized execution logic in the module as the customized logic; the logic customization supports the requirement of business personnel for customizing the internal execution logic of the module, and can freely select and match the internal execution logic of the module with different business scenes;

and establishing an internal execution logic library of the module according to the basic logic and the customized logic.

When the method for designing a rule engine with separated technology view points provided by the embodiment of the present invention is specifically implemented, in an embodiment, determining a transaction-side management rule according to a mapping relationship between an interface field and a variable library includes:

establishing a mutual conversion relation between the interface field and the variable library; the message type of the interface field comprises: request message, response message;

and automatically analyzing each field in the request message to a corresponding variable in the variable library through an interface field-variable library variable mapping relation defined by the service, or assigning the variable in the variable library to the corresponding field in the response message.

When the method for designing a rule engine with separated technology view provided by the embodiment of the present invention is implemented specifically, in an embodiment, determining a data side management rule according to a mapping relationship between a data table and a variable library includes:

establishing a mutual conversion relation between the data table and the variable of the variable base;

and automatically analyzing each field in the request data table to a corresponding variable in the variable database or storing the variable in the variable database to the corresponding field in the data table through the mapping relation between the fields of the data table and the variable database defined by the service.

When the method for designing a rule engine with separated technology views provided by the embodiment of the present invention is implemented specifically, in an embodiment, determining a module management rule according to a module definition and a module trend includes:

describing relevant information of a module entity according to the module name and the module execution condition, and determining module definition;

dividing a business flow into a starting point module, a destination point module and a plurality of business customizing modules, and taking the connection among the modules as the module trend; the other modules except the terminal module are at least provided with a default trend, and the process can flow to the corresponding module without meeting any condition; the service customization module can also configure a custom trend by utilizing the trend condition;

and determining a module management rule according to the module definition and the module trend.

When the method for designing a rule engine with separated technology views provided by the embodiment of the present invention is implemented specifically, in an embodiment, the establishing of the policy management rule according to the module management rule includes:

defining a strategy body name and a strategy belonged module according to a module management rule; the module to which the policy belongs indicates in which module the policy is executed, and each policy ontology may belong to a plurality of modules at the same time;

creating a policy service number; the strategy service number is a character string consisting of a string of letters and numbers and is used for uniquely identifying the strategy;

configuring a strategy type, an example hit condition, an example hit result and a custom description; the strategy types are expanded by business personnel, and one strategy type is only corresponding to each execution logic of one module; the instance hit conditions are divided into basic strategy hit conditions, general configuration conditions and strategy instance hit conditions, the strategy ontology corresponds to the basic strategy hit conditions, the strategy instances correspond to the strategy instance hit conditions, and the strategy instance hit conditions are logic and operation of the basic strategy hit conditions and the general configuration conditions;

and establishing a policy management rule according to the policy ontology name, the policy belonging module, the policy service number, the policy type, the instance hit condition, the instance hit result and the custom description.

When the method for designing a rule engine with separated technical views provided by the embodiment of the present invention is implemented specifically, in an embodiment, determining a process flow management rule according to a policy management rule includes:

judging whether the execution precondition of the processing flow is met or not according to the strategy management rule;

if so, initializing the machining flow, configuring an execution mode of the current machining flow, and sequentially acquiring subordinate machining items of the current machining flow;

judging whether the current processing flow meets the precondition of the processing item;

if yes, configuring the execution mode of the current processing item;

sequentially selecting the conditions of the processing items to assign; wherein, the column condition of the processing item corresponds to the condition column of the decision table;

judging whether the processing items meet the row conditions or not;

if yes, selecting result variable processing functions to which the processing items belong in sequence, and carrying out assignment and operation; wherein, the result variable processing function to which the processing item belongs corresponds to the operation column of the decision table;

the execution mode of the current processing item is judged, if the execution mode of the processing item is finished, the execution mode of the current processing flow is judged, and if the execution mode of the processing flow is finished, the current processing flow is finished.

In an embodiment of the invention, when the method for designing a rule engine with separated technology views is implemented specifically, an execution mode of a processing flow or a processing item includes: a full execution mode, a hit ending mode and a cyclic execution mode;

under the full execution mode, the processing flow or the processing item finishes processing the processing item or the row to which the processing item or the processing item belongs;

under the hit ending mode, the processing flow or the processing item enters an ending stage after the processing conditions of the processing item or the line are met;

in the circulation execution mode, the processing flow or the processing item has a circulation condition, the processing flow or the processing item can be circularly executed, and the circulation condition is judged after each circulation.

An embodiment of the present invention further provides a rule engine design apparatus with separated technical views, including:

the system comprises a full-scale library management rule determining module, a full-scale library management rule determining module and a full-scale library management rule determining module, wherein the full-scale library management rule determining module is used for determining a full-scale library management rule according to a variable library and a function library;

the transaction end management rule determining module is used for determining the transaction end management rule according to the mapping relation between the interface field and the variable library;

the data end management rule determining module is used for determining a data end management rule according to the mapping relation between the data table and the variable base;

the module management rule determining module is used for determining a module management rule according to the module definition and the module trend;

the strategy management rule determining module is used for establishing a strategy management rule according to the module management rule;

the processing flow management rule determining module is used for determining the processing flow management rule according to the strategy management rule;

and the service parameter management interface determining module is used for determining a service parameter management interface with separated service technology visual angles according to a full-scale management rule, a transaction end management rule, a data end management rule, a module management rule, a strategy management rule and a processing flow management rule.

In an embodiment of the present invention, when the apparatus for designing a rule engine with separated technology views is implemented specifically, the module for determining a total library management rule is specifically configured to:

establishing a variable library according to the variable definition table and the variable enumeration value definition table;

establishing a function library according to the basic function and the compound function;

establishing an internal execution logic library of the module according to the basic logic and the customized logic;

and determining a full-scale library management rule according to the variable library, the function library and the module internal execution logic library.

In a specific implementation of the apparatus for designing a rule engine with separated technical views provided in an embodiment of the present invention, in an embodiment, the full-scale library management rule determining module is further configured to:

defining variables according to the variable names, the Chinese descriptions and the data types, and determining a variable definition table;

configuring corresponding Chinese description for the fixed value definition of the variable, and determining a quantity enumeration value definition table;

and establishing a variable library according to the variable definition table and the variable enumeration value definition table.

When the technical view-separated rule engine design device provided by the embodiment of the invention is specifically implemented, in one embodiment, the variable library supports quick display of variable-processing logic and maps the variable-processing logic to a corresponding processing item, and a mode of using the technical variable first and then processing the technical variable is adopted; when a technical variable is added, a variable name, Chinese description and a data type are defined, and a processing variable requirement is generated in a project to-be-handled list.

In a specific implementation of the apparatus for designing a rule engine with separated technical views provided in an embodiment of the present invention, in an embodiment, the full-scale library management rule determining module is further configured to:

pre-developing functions including simple operation and character processing, expanding by combining service requirements, and determining a basic function;

combining the basic functions according to a set analysis format to determine a composite function;

and establishing a function library according to the basic function and the compound function.

In a specific implementation of the apparatus for designing a rule engine with separated technical views provided in an embodiment of the present invention, in an embodiment, the full-scale library management rule determining module is further configured to:

taking general execution logic in the module as basic logic;

taking the customized execution logic in the module as the customized logic; the logic customization supports the requirement of business personnel for customizing the internal execution logic of the module, and can freely select and match the internal execution logic of the module with different business scenes;

and establishing an internal execution logic library of the module according to the basic logic and the customized logic.

When the apparatus for designing a rule engine with separated technology views provided in an embodiment of the present invention is implemented specifically, in an embodiment, the transaction side management rule determining module is specifically configured to:

establishing a mutual conversion relation between the interface field and the variable library; the message type of the interface field comprises: request message, response message;

and automatically analyzing each field in the request message to a corresponding variable in the variable library through an interface field-variable library variable mapping relation defined by the service, or assigning the variable in the variable library to the corresponding field in the response message.

In an embodiment of the present invention, when the apparatus for designing a rule engine with separated technology views is implemented specifically, the data side management rule determining module is specifically configured to:

establishing a mutual conversion relation between the data table and the variable of the variable base;

and automatically analyzing each field in the request data table to a corresponding variable in the variable database or storing the variable in the variable database to the corresponding field in the data table through the mapping relation between the fields of the data table and the variable database defined by the service.

In an embodiment of the present invention, when implementing the rule engine design apparatus with separated technology views, the module management rule determining module is specifically configured to:

describing relevant information of a module entity according to the module name and the module execution condition, and determining module definition;

dividing a business flow into a starting point module, a destination point module and a plurality of business customizing modules, and taking the connection among the modules as the module trend; the other modules except the terminal module are at least provided with a default trend, and the process can flow to the corresponding module without meeting any condition; the service customization module can also configure a custom trend by utilizing the trend condition;

and determining a module management rule according to the module definition and the module trend.

When the apparatus for designing a rule engine with separated technology views provided in an embodiment of the present invention is implemented specifically, in an embodiment, the policy management rule determining module is specifically configured to:

defining a strategy body name and a strategy belonged module according to a module management rule; the module to which the policy belongs indicates in which module the policy is executed, and each policy ontology may belong to a plurality of modules at the same time;

creating a policy service number; the strategy service number is a character string consisting of a string of letters and numbers and is used for uniquely identifying the strategy;

configuring a strategy type, an example hit condition, an example hit result and a custom description; the strategy types are expanded by business personnel, and one strategy type is only corresponding to each execution logic of one module; the instance hit conditions are divided into basic strategy hit conditions, general configuration conditions and strategy instance hit conditions, the strategy ontology corresponds to the basic strategy hit conditions, the strategy instances correspond to the strategy instance hit conditions, and the strategy instance hit conditions are logic and operation of the basic strategy hit conditions and the general configuration conditions;

and establishing a policy management rule according to the policy ontology name, the policy belonging module, the policy service number, the policy type, the instance hit condition, the instance hit result and the custom description.

In an embodiment of the present invention, when the apparatus for designing a rule engine with separated technical views is implemented specifically, the process flow management rule determining module is specifically configured to:

judging whether the execution precondition of the processing flow is met or not according to the strategy management rule;

if so, initializing the machining flow, configuring an execution mode of the current machining flow, and sequentially acquiring subordinate machining items of the current machining flow;

judging whether the current processing flow meets the precondition of the processing item;

if yes, configuring the execution mode of the current processing item;

sequentially selecting the conditions of the processing items to assign; wherein, the column condition of the processing item corresponds to the condition column of the decision table;

judging whether the processing items meet the row conditions or not;

if yes, selecting result variable processing functions to which the processing items belong in sequence, and carrying out assignment and operation; wherein, the result variable processing function to which the processing item belongs corresponds to the operation column of the decision table;

the execution mode of the current processing item is judged, if the execution mode of the processing item is finished, the execution mode of the current processing flow is judged, and if the execution mode of the processing flow is finished, the current processing flow is finished.

In an embodiment of the invention, when implementing the rule engine design apparatus with separated technology views, an execution mode of a process flow or a process item includes: a full execution mode, a hit ending mode and a cyclic execution mode;

under the full execution mode, the processing flow or the processing item finishes processing the processing item or the row to which the processing item or the processing item belongs;

under the hit ending mode, the processing flow or the processing item enters an ending stage after the processing conditions of the processing item or the line are met;

in the circulation execution mode, the processing flow or the processing item has a circulation condition, the processing flow or the processing item can be circularly executed, and the circulation condition is judged after each circulation.

The embodiment of the invention also provides computer equipment which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein the processor executes the computer program to realize the technical view separation rule engine design method.

An embodiment of the present invention further provides a computer-readable storage medium, where a computer program for executing the above rule engine design method for technology view separation is stored in the computer-readable storage medium.

The embodiment of the invention provides a method and a device for designing a rule engine with separated technical views, wherein the method comprises the following steps: firstly, determining a full-scale library management rule according to a variable library and a function library; then, determining a transaction end management rule according to a mapping relation between the interface field and the variable library; determining a data end management rule according to a mapping relation between the data table and the variable base; determining module management rules according to the module definition and the module trend; next, establishing a strategy management rule according to the module management rule; determining a processing flow management rule according to the strategy management rule; and finally, determining a business parameter management interface with separated business technology visual angles according to a full-scale management rule, a transaction end management rule, a data end management rule, a module management rule, a strategy management rule and a processing flow management rule. The embodiment of the invention provides a technical scheme for separating service technical views, which distinguishes a service view from a technical view and defines the authority scope of service personnel and technical personnel. The business personnel only need to configure the flow module, the business rule and the relevant variable parameter which can be efficiently managed by the business personnel to realize the business logic of the business personnel without concerning the realization of the specific logic. Technical personnel only need to process variables required by the business, support related technical functions and realize related technologies without being limited by a realization method, thereby avoiding unnecessary difficulties. Through the design and maintenance scheme which is relatively independent and convenient for the service view, when the service requirement details are changed frequently or maintained and changed, the service can be changed flexibly without depending on technology cooperation, and the current situations that the version is repeatedly deployed and on-line, and the flow is long and time-consuming are avoided. Through the efficient and easy-to-understand design of the business view, business personnel can actively and actively use and participate in development, and business function configuration can be conveniently and efficiently carried out; by maintaining the dependency relationship between the variables and the related processing logic, the function points and technical details which need to be checked are dynamically prompted after the business logic is changed. The workload of manually searching and judging related function points is reduced, the difficulty of function or technology development and maintenance is reduced, and detail loopholes caused by forgetting or unfamiliarity of related maintenance personnel to business logic details are avoided.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts. In the drawings:

fig. 1 is a schematic diagram of a rule engine design method with separated technology views according to an embodiment of the present invention.

Fig. 2 is a schematic overall flow chart of a rule engine design method based on technical view separation according to an embodiment of the present invention.

Fig. 3 is a variable library diagram of a rule engine design method based on technology view separation according to an embodiment of the present invention.

Fig. 4 is a functional library diagram of a rule engine design method with separated technology views according to an embodiment of the present invention.

Fig. 5 is a schematic diagram of an intra-module execution logic library of a rule engine design method with separated technology view points according to an embodiment of the present invention.

Fig. 6 is a diagram illustrating a transaction-side field mapping table of a rule engine design method with separated technology views according to an embodiment of the present invention.

Fig. 7 is a diagram illustrating a data-side field mapping table of a rule engine design method with separated technology views according to an embodiment of the present invention.

Fig. 8 is a transaction management diagram of a rule engine design method with separated technology views according to an embodiment of the present invention.

Fig. 9 is a schematic block management flow diagram of a rule engine design method with separated technology views according to an embodiment of the present invention.

FIG. 10 is a block logic diagram of a rule engine design method with view separation according to an embodiment of the present invention.

Fig. 11 is a schematic diagram illustrating a policy composition of a rule engine design method for technology view separation according to an embodiment of the present invention.

Fig. 12 is a process flow diagram of a rule engine design method with separated view angles according to an embodiment of the present invention.

FIG. 13 is a schematic diagram of a computer device running a technique view-separated rules engine design method implemented in accordance with the present invention.

Fig. 14 is a schematic diagram of a rule engine design apparatus for technical view separation according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the embodiments of the present invention are further described in detail below with reference to the accompanying drawings. The exemplary embodiments and descriptions of the present invention are provided to explain the present invention, but not to limit the present invention.

The invention relates to automatic programming. Fig. 1 is a schematic diagram of a method for designing a rule engine with separated technical views according to an embodiment of the present invention, as shown in fig. 1,

the embodiment of the invention provides a rule engine design method with separated technical views, provides a technical scheme with separated service technical views, distinguishes service views from technical views, and defines authority and responsibility ranges of service personnel and technical personnel, and the method comprises the following steps:

step 101: determining a full-scale library management rule according to the variable library and the function library;

step 102: determining a transaction end management rule according to a mapping relation between the interface field and the variable library;

step 103: determining a data end management rule according to a mapping relation between a data table and a variable base;

step 104: determining a module management rule according to the module definition and the module trend;

step 105: establishing a policy management rule according to the module management rule;

step 106: determining a processing flow management rule according to the strategy management rule;

step 107: and determining a business parameter management interface with separated business technology visual angles according to a full-scale management rule, a transaction end management rule, a data end management rule, a module management rule, a strategy management rule and a processing flow management rule.

The embodiment of the invention provides a rule engine design method with separated technical views, which comprises the following steps: firstly, determining a full-scale library management rule according to a variable library and a function library; then, determining a transaction end management rule according to a mapping relation between the interface field and the variable library; determining a data end management rule according to a mapping relation between the data table and the variable base; determining module management rules according to the module definition and the module trend; next, establishing a strategy management rule according to the module management rule; determining a processing flow management rule according to the strategy management rule; and finally, determining a business parameter management interface with separated business technology visual angles according to a full-scale management rule, a transaction end management rule, a data end management rule, a module management rule, a strategy management rule and a processing flow management rule. The technical scheme of the embodiment of the invention with separated service technical views distinguishes the service view from the technical view and defines the authority scope of service personnel and technical personnel. The business personnel only need to configure the flow module, the business rule and the relevant variable parameter which can be efficiently managed by the business personnel to realize the business logic of the business personnel without concerning the realization of the specific logic. Technical personnel only need to process variables required by the business, support related technical functions and realize related technologies without being limited by a realization method, thereby avoiding unnecessary difficulties. Through the design and maintenance scheme which is relatively independent and convenient for the service view, when the service requirement details are changed frequently or maintained and changed, the service can be changed flexibly without depending on technology cooperation, and the current situations that the version is repeatedly deployed and on-line, and the flow is long and time-consuming are avoided. Through the efficient and easy-to-understand design of the business view, business personnel can actively and actively use and participate in development, and business function configuration can be conveniently and efficiently carried out; by maintaining the dependency relationship between the variables and the related processing logic, the function points and technical details which need to be checked are dynamically prompted after the business logic is changed. The workload of manually searching and judging related function points is reduced, the difficulty of function or technology development and maintenance is reduced, and detail loopholes caused by forgetting or unfamiliarity of related maintenance personnel to business logic details are avoided.

In the embodiment of the invention, the variables are roughly divided into three types of variables, namely basic variables, technical variables and business variables.

The basic variables are subdivided into two types, namely the basic variables obtained from the message interfaces and the basic variables obtained from the data tables;

the technical variables are processed by technicians, and the method is characterized by no or weak correlation of services and flexible processing mode. The business personnel do not need to configure the business personnel, the project execution stage of the business personnel is 'business front flow', the business front flow is not reflected in a business view, but the technical variable and the logic thereof can be retrieved in a variable library. In theory, if the business variable processing logic is too complex, the business person can also hand over to the technician as a technical variable to implement.

The business variable is configured and processed by business personnel, and the method has the characteristics of strong correlation of business, limited implementation mode and capability of processing in a user-defined processing flow. The business personnel hope to effectively manage and rapidly configure the business personnel, and the project execution stage of the business personnel is 'business process', which is only reflected in the business view.

The specific development of the design of the existing rule engine for the business-oriented function can be roughly divided into graphical representation form, natural code language and standardized business rule form.

Firstly, the presentation form of the existing business logic is graphically displayed, and the presentation form mainly comprises the following steps:

1. displaying a flow chart of the rule flow, wherein each graphical node represents each relatively independent functional module in the service logic;

2. the specification of the common business rules illustrates the page format.

Then, the writing of the existing business logic is realized by technical codes, but the natural language display is mainly divided into two pieces of content:

the java structure and the natural language of the specific attribute thereof are converted into natural language, corresponding natural language descriptions are manually configured for each layer directly, and the layers are connected with each other by separators;

the natural language of the function method needs to additionally insert a plurality of placeholders in the natural language description according to the number of parameters of the function, so as to insert other variables when in use.

Finally, the existing rule engines only provide certain kinds of business rules, and they have the characteristics of uniform and standard formats, and the processed business problems also have the characteristics of a certain specific form, such as:

the operation rule is implemented in the form of if then else. The design of some special rule engines can also support the effect of predefining some variables, such as that a local variable A of 'predefine' belongs to a list ListA, and the operation rules are executed circularly by traversing the list variables;

decision tables are implemented in the form of [ conditional if "+" action column then "] rows. Partial contents of each condition column and each operation column can be fixed, and the relatively neat view is realized.

The decision tree is implemented in the form of if parent node "-" then pass through left child node "-" else pass through right child node ". The essence can be understood as a tree diagram representation of the multi-layer operation rule.

It is possible for the skilled person to use both the above-mentioned business rules and technical rules. The technical rules are that the technical codes are directly used to realize the corresponding business logic. Unlike the business rules, which need to be restricted to various standard forms, the technical rules can freely use various conditions, circulation and other statements, are flexible and convenient to use, and are convenient for solving complex business or technical problems. However, in general, and mainly from the aspect of usage specification, when developing by using a rule engine, even if a technician is responsible for designing all development contents, the technician needs to avoid using the technical rules as much as possible and use the business rules facing the business personnel as much as possible to develop the related business functions.

The embodiment of the invention provides a design scheme of a highly configurable rule engine based on service technology perspective separation.

Through the design and maintenance scheme which is relatively independent and convenient for the service view, when the service requirement details are changed frequently or maintained and changed, service personnel can flexibly and independently perform related changes in a technical cooperation manner, and the current situations that versions are repeatedly deployed and on-line, and the flow is long and time-consuming are avoided.

Through the efficient and easy-to-understand design of the business view, business personnel can actively and actively use and participate in development, and business function configuration can be conveniently and efficiently carried out. Technicians only need to pay attention to related technology development support and do not need to be in a business rule form.

By maintaining the dependency relationship between the variables and the related processing logic, after the business logic is changed, the functional points and technical details which need to be checked are dynamically prompted. The workload of manually searching and judging related function points is reduced, the difficulty of function or technology development and maintenance is reduced, and detail loopholes caused by forgetting or unfamiliarity of related maintenance personnel to business logic details are avoided.

The maintenance of the variable base of the rule engine is dynamically realized through the parameter management configuration of the interface and the data table, the increase, the decrease and the modification of the number of the variable base are realized through a set of resource management configuration mode, and the basic variables of the variable base are conveniently and dynamically maintained by business and technical personnel.

Fig. 2 is a schematic overall flow chart of a rule engine design method with separated technology views according to an embodiment of the present invention, and as shown in fig. 2, when the rule engine design method with separated technology views provided by the embodiment of the present invention is implemented specifically, in an embodiment, the method may include: determining a full-scale library management rule according to the variable library and the function library; determining a transaction end management rule according to a mapping relation between the interface field and the variable library; determining a data end management rule according to a mapping relation between a data table and a variable base; determining a module management rule according to the module definition and the module trend; establishing a policy management rule according to the module management rule; determining a processing flow management rule according to the strategy management rule; and determining a business parameter management interface with separated business technology visual angles according to a full-scale management rule, a transaction end management rule, a data end management rule, a module management rule, a strategy management rule and a processing flow management rule.

The design concept of the design on the business view is based on the fact that a business parameter management interface with separated business technology visual angles is provided, and a high-configurable and high-efficiency parameterization integrated interface enables special affairs on pages to be special, supports multi-dimensional retrieval, is displayed in a table form, and is convenient for comprehensive management and control and understanding.

When the method for designing a rule engine with separated technical views provided by the embodiment of the present invention is implemented specifically, in an embodiment, determining a full-scale library management rule according to a variable library and a function library includes:

establishing a variable library according to the variable definition table and the variable enumeration value definition table;

establishing a function library according to the basic function and the compound function;

establishing an internal execution logic library of the module according to the basic logic and the customized logic;

and determining a full-scale library management rule according to the variable library, the function library and the module internal execution logic library.

Fig. 3 is a schematic diagram of a variable library of a rule engine design method based on technology view separation according to an embodiment of the present invention, and as shown in fig. 3, when a rule engine design method based on technology view separation according to an embodiment of the present invention is specifically implemented, in an embodiment, a variable library is established according to a variable definition table and a variable enumeration value definition table, including:

defining variables according to the variable names, the Chinese descriptions and the data types, and determining a variable definition table;

configuring corresponding Chinese description for the fixed value definition of the variable, and determining a quantity enumeration value definition table;

and establishing a variable library according to the variable definition table and the variable enumeration value definition table.

When the method for designing the rule engine with separated technical view angles is specifically implemented, in one embodiment, a variable library supports quick display of variable-processing logic and maps the variable-processing logic to a corresponding processing item, and a mode of using the technical variable first and then processing the technical variable is adopted; when a technical variable is added, a variable name, Chinese description and a data type are defined, and a processing variable requirement is generated in a project to-be-handled list.

In the embodiment, the variable library is divided into two pieces of content, namely variable definition and variable enumeration value definition. The variable definition mainly defines variable names, Chinese descriptions and data types; the variable enumeration value is a Chinese description corresponding to certain fixed value definitions of a certain variable, and is convenient to use. And the full variable library supports quick display of the variable-processing logic and mapping to a corresponding processing item, and adopts a first-use and then-processing policy for the technical variable. If a new technical variable needs to be added, only the 'variable name', 'type', 'Chinese processing description' needs to be defined, a 'processing variable requirement' is automatically generated in a project to-be-handled list, and subsequent realization by technical personnel can use the variable in the processing logic of business writing without influencing the fluency of business writing the business logic by the business personnel, avoid the efficiency waiting dilemma of relying on before and after a development link, and also improve the understanding and mastering fluency of business logic processing by the business personnel.

Fig. 4 is a schematic diagram of a function library of a rule engine design method based on technology view separation according to an embodiment of the present invention, and as shown in fig. 4, when the rule engine design method based on technology view separation according to the embodiment of the present invention is specifically implemented, in an embodiment, a function library is established according to a basis function and a complex function, including:

pre-developing functions including simple operation and character processing, expanding by combining service requirements, and determining a basic function;

combining the basic functions according to a set analysis format to determine a composite function;

and establishing a function library according to the basic function and the compound function.

In the embodiment, the function library is divided into two contents, namely a basic function and a compound function. The basic function is various function functions developed in advance by technicians, including various simple operations and character processing, and can also be expanded according to business needs. The composite function is a basic function combined according to a specific analytic format, so that service personnel can use the basic function when the basic function cannot meet the requirement.

Fig. 5 is a schematic diagram of an intra-module execution logic library of a rule engine design method based on technology view separation according to an embodiment of the present invention, and as shown in fig. 5, when the rule engine design method based on technology view separation according to an embodiment of the present invention is implemented specifically, in an embodiment, an intra-module execution logic library is established according to a basic logic and a customized logic, and includes:

taking general execution logic in the module as basic logic;

taking the customized execution logic in the module as the customized logic; the logic customization supports the requirement of business personnel for customizing the internal execution logic of the module, and can freely select and match the internal execution logic of the module with different business scenes;

and establishing an internal execution logic library of the module according to the basic logic and the customized logic.

In an embodiment, the library of intra-module execution logic includes both base logic and custom logic. The base logic is generic execution logic within the module and the custom logic is custom execution logic within the module. The requirement of business personnel for customizing the internal execution logic of the module is supported, and the internal execution logic of the module in different business scenes can be freely selected and matched.

Fig. 6 is a schematic diagram of a transaction-side field mapping table of a rule engine design method based on technology view separation according to an embodiment of the present invention, and as shown in fig. 6, when a rule engine design method based on technology view separation according to an embodiment of the present invention is implemented specifically, in an embodiment, determining a transaction-side management rule according to a mapping relationship between an interface field and a variable library includes:

establishing a mutual conversion relation between the interface field and the variable library; the message type of the interface field comprises: request message, response message;

and automatically analyzing each field in the request message to a corresponding variable in the variable library through an interface field-variable library variable mapping relation defined by the service, or assigning the variable in the variable library to the corresponding field in the response message.

In the embodiment, the interface format processed by the transaction end (interface) comprises an XML format and a json format, and the type of the processed message comprises a request message and a response message. The data end (data table) processes two functions of data table number checking and data storage.

The transaction end management provides a technical scheme for converting interface fields such as xml and json and variable library variables into one another. Through the interface field-variable library variable mapping relation defined by the service, each field in the request message can be automatically analyzed to a corresponding variable in the variable library, and the variable in the variable library can be assigned to the corresponding field in the response message.

Fig. 6 is a schematic diagram of a transaction-side field mapping table of a rule engine design method based on technology view separation according to an embodiment of the present invention, fig. 7 is a schematic diagram of a data-side field mapping table of a rule engine design method based on technology view separation according to an embodiment of the present invention, and fig. 8 is a schematic diagram of transaction-side management of a rule engine design method based on technology view separation according to an embodiment of the present invention, as shown in fig. 6, fig. 7, and fig. 8, when a rule engine design method based on technology view separation according to an embodiment of the present invention is specifically implemented, in an embodiment, a data-side management rule is determined according to a mapping relationship between a data table and a variable library, including:

establishing a mutual conversion relation between the data table and the variable of the variable base;

and automatically analyzing each field in the request data table to a corresponding variable in the variable database or storing the variable in the variable database to the corresponding field in the data table through the mapping relation between the fields of the data table and the variable database defined by the service.

In the embodiment, the data end management provides a technical scheme for mutually converting the data table and the variable of the variable base. Through the mapping relation between the data table field and the variable of the variable base defined by the service, the fields in the request data table can be automatically analyzed to the corresponding variable in the variable base, and the variable in the variable base can be stored in the corresponding field in the data table.

Fig. 9 is a schematic diagram of a module management flow of a rule engine design method with separated technical views according to an embodiment of the present invention, and fig. 10 is a schematic diagram of a module logic execution of the rule engine design method with separated technical views according to an embodiment of the present invention, as shown in fig. 9 and fig. 10, when a rule engine design method with separated technical views according to an embodiment of the present invention is specifically implemented, in an embodiment, determining a module management rule according to a module definition and a module trend includes:

describing relevant information of a module entity according to the module name and the module execution condition, and determining module definition;

dividing a business flow into a starting point module, a destination point module and a plurality of business customizing modules, and taking the connection among the modules as the module trend; the other modules except the terminal module are at least provided with a default trend, and the process can flow to the corresponding module without meeting any condition; the service customization module can also configure a custom trend by utilizing the trend condition;

and determining a module management rule according to the module definition and the module trend.

In an embodiment, a module is the smallest element in a business view that represents a flow. The module is divided into a module definition and a module trend to two pieces of content. The module definition describes the relevant information of the module entity, mainly including the module name, the module execution condition, etc.

The business process is composed of a plurality of modules, wherein two modules representing a starting point and an end point are necessary, and a plurality of modules with customized business are also provided, and the number can be freely expanded and contracted.

The connections between modules are represented by module trends, which in turn express the flow direction of the process. Each module has at least one default trend, and the process can flow to the corresponding module without meeting any condition. In addition, the module can be configured with a custom trend, the custom trend must be set with conditions, and the process can flow to the corresponding module only when the corresponding trend conditions are met. The custom orientation of the modules may also be configured in a telescoping manner. The "end" module has no strike.

The modules may be considered to have the same internal execution logic, i.e., each module may be considered to use a single template. But different rules, such as various types of strategies, various process flows, are located on different modules. When the internal execution logic of the module is executed, the type of the rule to which the module belongs is searched and judged, and then the corresponding rule is processed according to the specific internal execution logic corresponding to the rule type. In the event that a rule of some type is missing on a module, the corresponding internal execution logic is not executed.

A module is essentially composed of an infinite number of internal execution logic. The internal execution logic that the module must go to is: initialization of module internal execution logic, module internal main execution logic and module trend execution logic. Other internal execution logic is selected based on the type of rule to which the module belongs. Generally, the internal execution logic of the process flow rule is executed first, and then the internal execution logic of the strategy rule is executed.

Fig. 11 is a schematic diagram of a policy composition of a rule engine design method with separated technology views according to an embodiment of the present invention, and as shown in fig. 11, when the rule engine design method with separated technology views provided by the embodiment of the present invention is implemented specifically, in an embodiment, a policy management rule is established according to a module management rule, including:

defining a strategy body name and a strategy belonged module according to a module management rule; the module to which the policy belongs indicates in which module the policy is executed, and each policy ontology may belong to a plurality of modules at the same time;

creating a policy service number; the strategy service number is a character string consisting of a string of letters and numbers and is used for uniquely identifying the strategy;

configuring a strategy type, an example hit condition, an example hit result and a custom description; the strategy types are expanded by business personnel, and one strategy type is only corresponding to each execution logic of one module; the instance hit conditions are divided into basic strategy hit conditions, general configuration conditions and strategy instance hit conditions, the strategy ontology corresponds to the basic strategy hit conditions, the strategy instances correspond to the strategy instance hit conditions, and the strategy instance hit conditions are logic and operation of the basic strategy hit conditions and the general configuration conditions;

and establishing a policy management rule according to the policy ontology name, the policy belonging module, the policy service number, the policy type, the instance hit condition, the instance hit result and the custom description.

In an embodiment, the policy management rules include:

1. policy service numbers, i.e., a string of letters and numbers, are used to uniquely identify a policy and are unique within a service view. In addition, each strategy can be provided with a Chinese rule name;

2. the policy type, and the policy type number is used to indicate the type of the policy. The strategy types can be freely expanded by business personnel, and one strategy type only corresponds to one module internal execution logic. When a policy type needs to be extended, in addition to defining a policy type number, a corresponding module internal execution logic needs to be defined. One strategy ontology corresponds to a plurality of strategy instances, and one strategy instance can correspond to a plurality of strategy types;

3. and the module to which the strategy belongs is used for indicating the module in which the strategy is executed. Each policy ontology may belong to multiple modules simultaneously.

4. And the execution priority is used for expressing the execution sequence among the strategy ontologies.

5. The hit conditions are divided into basic hit conditions of the strategy, general configuration conditions and hit conditions of strategy examples. The strategy ontology corresponds to the basic strategy hit condition, and the strategy instance corresponds to the strategy instance hit condition. The strategy instance hit condition is the logic and operation of the strategy basic hit condition and the general configuration condition.

6. The hit results correspond to the policy instance one to one. Because a policy instance can correspond to multiple policy types, each policy instance has a hit result set, and as long as the hit condition of the policy instance is met, the module sequentially calls corresponding module internal execution logic to process the corresponding policy type-result.

7. And self-defining the Chinese description, and corresponding to the strategy examples one by one. Different Chinese descriptions of the same strategy service number under different scenes of service personalized configuration are supported, so that polymorphic configuration of strategy description on a page is supported.

Fig. 12 is a schematic process flow diagram of a rule engine design method with separated technology views according to an embodiment of the present invention, and as shown in fig. 12, when the rule engine design method with separated technology views provided by the embodiment of the present invention is specifically implemented, in an embodiment, determining a process flow management rule according to a policy management rule includes:

judging whether the execution precondition of the processing flow is met or not according to the strategy management rule;

if so, initializing the machining flow, configuring an execution mode of the current machining flow, and sequentially acquiring subordinate machining items of the current machining flow;

judging whether the current processing flow meets the precondition of the processing item;

if yes, configuring the execution mode of the current processing item;

sequentially selecting the conditions of the processing items to assign; wherein, the column condition of the processing item corresponds to the condition column of the decision table;

judging whether the processing items meet the row conditions or not;

if yes, selecting result variable processing functions to which the processing items belong in sequence, and carrying out assignment and operation; wherein, the result variable processing function to which the processing item belongs corresponds to the operation column of the decision table;

the execution mode of the current processing item is judged, if the execution mode of the processing item is finished, the execution mode of the current processing flow is judged, and if the execution mode of the processing flow is finished, the current processing flow is finished.

In an embodiment, the process flow management rule includes:

the process flow is a carrier for managing, configuring and executing business variable process logic.

The execution sequence is as follows:

1. judging whether the execution precondition of the processing flow is met, if so, turning to 2, and if not, turning to 10;

2. initializing a machining flow, configuring an execution mode of the current machining flow, and sequentially acquiring subordinate machining items of the current machining flow;

3. judging whether the precondition of the processing item is met, if so, turning to 4, and if not, turning to 10;

4. configuring an execution mode of a current processing item;

5. sequentially selecting the conditions (corresponding to the condition columns of the decision table) to which the processing items belong, and assigning values;

6. judging whether the column conditions are met, if the column conditions are met, rotating 7 is not met, and rotating 8 is not met;

7. sequentially selecting result variable processing functions (corresponding to operation columns of the decision table) to which the processing items belong, and carrying out assignment and operation;

8. judging the execution mode of the processing item, and judging whether the processing item is finished, if so, turning to 9, and if not, turning to 4;

9. judging the execution mode of the processing flow, judging whether the processing flow is finished, if so, turning to 10, and if not, turning to 2;

10. the process flow ends.

In an embodiment of the invention, when the method for designing a rule engine with separated technology views is implemented specifically, an execution mode of a processing flow or a processing item includes: a full execution mode, a hit ending mode and a cyclic execution mode;

under the full execution mode, the processing flow or the processing item finishes processing the processing item or the row to which the processing item or the processing item belongs;

under the hit ending mode, the processing flow or the processing item enters an ending stage after the processing conditions of the processing item or the line are met;

in the circulation execution mode, the processing flow or the processing item has a circulation condition, the processing flow or the processing item can be circularly executed, and the circulation condition is judged after each circulation.

In an embodiment, the execution mode of the processing flow/processing item. There are three modes, namely, a full execution mode, a hit-end mode, and a loop execution mode. In the full execution mode, the processing flow/processing item will finish processing the processing item/row. In the post-hit finish mode, the process flow/process item enters the finish stage after the process conditions of the process item/row are satisfied. In the circulation execution mode, the processing flow/processing item has circulation conditions, the processing flow/processing item can be circularly executed, and the circulation conditions are judged once after each circulation.

The embodiment of the invention provides a technical scheme for separating service technical views, distinguishes the service view from the technical view and defines the authority scope of service personnel and technical personnel. The business personnel only need to configure the flow module, the business rule and the relevant variable parameter which can be efficiently managed by the business personnel to realize the business logic of the business personnel without concerning the realization of the specific logic. Technical personnel only need to process variables required by the business, support related technical functions and realize related technologies without being limited by a realization method, thereby avoiding unnecessary difficulties.

By maintaining the dependency relationship between the variables and the related processing logic, after the business logic is changed, the functional points and technical details which need to be checked are dynamically prompted. The workload of manually searching and judging related function points is reduced, the difficulty of function or technology development and maintenance is reduced, and detail loopholes caused by forgetting or unfamiliarity of related maintenance personnel to business logic details are avoided.

Through resource management configuration of the interface and the data table, maintenance of a variable library of the rule engine is dynamically realized, increase, decrease and modification of the number of variables are realized, and alias names, attributes, mapping and the like of the variables are convenient for business and technicians to quickly and dynamically maintain basic variables of the variable library.

The invention provides a design scheme of a highly configurable rule engine based on business technology perspective separation. Through the design and maintenance scheme which is relatively independent and convenient for the service view, when the service requirement details are changed frequently or maintained and changed, the service can be changed flexibly without depending on technology cooperation, and the current situations that the version is repeatedly deployed and on-line, and the flow is long and time-consuming are avoided. Through the efficient and easy-to-understand design of the business view, business personnel can actively and actively use and participate in development, and business function configuration can be conveniently and efficiently carried out. By maintaining the dependency relationship between the variables and the related processing logic, the function points and technical details which need to be checked are dynamically prompted after the business logic is changed. The workload of manually searching and judging related function points is reduced, the difficulty of function or technology development and maintenance is reduced, and detail loopholes caused by forgetting or unfamiliarity of related maintenance personnel to business logic details are avoided. The maintenance of the variable library of the rule engine is dynamically realized through the resource management configuration of the interface and the data table so as to realize the increase, decrease and modification of the alias, the attribute, the mapping and the like of the variables, and thus, the basic variables of the variable library can be quickly and dynamically maintained by business and technical personnel.

The scheme can be used for managing all resources through a database, only curing a part of general processing logic as a technical code, processing and analyzing all parameters, realizing a service view design scheme with high freedom degree, highest flexibility degree and largest management range, and can also be changed into a service view design scheme which only supports configuration of part of contents which change most frequently and is relatively limited in management range through curing parameters which can not be changed, so that the operation efficiency can be reasonably ensured. The management scope of the business view can be determined by configuration and compilation, and the purpose is achieved by a universal resource management configuration and business view compilation scheme.

In the embodiment of the invention, a project refers to a specific project, is represented by a service number, and represents a solution set of a business scenario. Under a project, a plurality of parallel business entities are subdivided, each business entity represents a solution to the business scene, each business entity has a business view which is unique and independent from the fact, and business variables, rules and the like between each business view are not intercommunicated. Specifically, the difference between the service scenes is only the specialization of the service view, and for the service personnel, only certain parameters can be changed, and the service rules and the service logic can be adjusted in a large range,

the project can be regarded as a composition of a technical view, a plurality of business views and various full-scale libraries

The project execution process is divided into three stages, namely a business front process, a business process and a business back process.

The 'flow before service' and 'flow after service' are technical development flows and use technical views;

the 'business process' is a process of business development, configuration and maintenance, and uses a business view.

In the development process, the 'flow before business' is used as the premise of the 'business flow', and all technical rules and other technical implementation are processed; the 'business process' configures main business logic and parameters; the "post-business flow" is the encapsulation of the returned result BOM and other final technical processing.

The scheme subdivides a service view and a technical view. The project consists of a business view and a technical view, wherein the business view is used by business personnel, and the technical view is used by technical personnel. The service view is the leading one, the technical view is the complement one, the service view provides 'variable/function processing requirement' for the technical view, and the technical view supports the function realization of the service view. The business view may be developed prior to the technical view.

1. The service view adds features more suitable for service usage, e.g.

(1) Basic configuration, hit conditions and results of the strategies are decoupled, all components on a page can be freely combined, flexibly configured and processed in batch, a foundation is laid for the strategies to be induced and classified, and the strategy processing logic which can be unified and reused can be customized, specified and unified for service problems of corresponding specific classes;

(2) the method comprises the steps of realizing the module materialization of the flow chart, regularizing the flow direction of the module and positioning and configuring the regular module, so that the logic of the flow chart can be configured by the rule, the retrievability of related contents is realized, and the characteristic of simple configuration is realized. The rule processing logic is solidified in the module, so that the rule processing logic is automatically and strongly associated with the type of the rule to be processed by the module, and the effect of simple configuration is achieved;

(3) the interface of business customization screens according to each condition dimension, and accurate location shields too detailed, the function option that too the bottom realized, accomplishes that the function is brief practical, and the purpose is clear and definite, and the visual angle is comprehensive unified. And service personnel are ensured to only concentrate on the most critical service parameter management and the most important service logic maintenance.

2. The technical view discards the contents of all business views in the conventional rule engine based on the angle of the maximum technical capability, and only uses java code to solve the technical problem. Meanwhile, a set of mechanism aiming at the change-association-prompt of technical variables in the variable library is designed, and after a technical variable is changed, the mechanism prompts and checks the associated variable.

The notion of rules, policies, modules, and process volumes exists only in the business view.

The design is mainly explained aiming at five aspects:

the first part, full-scale library management such as variable library and function library:

the variable library is divided into two contents of variable definition and variable enumeration value definition. The variable definition mainly defines variable names, Chinese descriptions and data types; the variable enumeration value is a Chinese description corresponding to certain fixed value definitions of a certain variable, and is convenient to use. And the full variable library supports quick display of the variable-processing logic and mapping to a corresponding processing item, and adopts a first-use and then-processing policy for the technical variable. If a new technical variable needs to be added, only the 'variable name', 'type', 'Chinese processing description' needs to be defined, a 'processing variable requirement' is automatically generated in a project to-be-handled list, and subsequent realization by technical personnel can use the variable in the processing logic of business writing without influencing the fluency of business writing the business logic by the business personnel, avoid the efficiency waiting dilemma of relying on before and after a development link, and also improve the understanding and mastering fluency of business logic processing by the business personnel.

The function library is divided into two contents, namely a basic function and a compound function. The basic function is various function functions developed in advance by technicians, including various simple operations and character processing, and can also be expanded according to business needs. The composite function is a basic function combined according to a specific analytic format, so that service personnel can use the basic function when the basic function cannot meet the requirement.

The module internal execution logic library comprises basic logic and custom logic. The base logic is generic execution logic within the module and the custom logic is custom execution logic within the module. The requirement of business personnel for customizing the internal execution logic of the module is supported, and the internal execution logic of the module in different business scenes can be freely selected and matched.

And the second part, transaction end (interface) and data end (data table) management:

the interface format processed by the transaction end (interface) comprises XML and json format, and the type of the processed message comprises a request message and a response message.

The data end (data table) processes two functions of data table number checking and data storage.

The transaction end management provides a technical scheme for converting interface fields such as xml and json and variable library variables into one another. Through the interface field-variable library variable mapping relation defined by the service, each field in the request message can be automatically analyzed to a corresponding variable in the variable library, and the variable in the variable library can be assigned to the corresponding field in the response message.

The data end management provides a technical scheme for converting data tables and variable library variables into one another. Through the mapping relation between the data table field and the variable of the variable base defined by the service, the fields in the request data table can be automatically analyzed to the corresponding variable in the variable base, and the variable in the variable base can be stored in the corresponding field in the data table.

And a third part, module management:

a module is the smallest element in a business view that represents a flow. The module is divided into a module definition and a module trend to two pieces of content. The module definition describes the relevant information of the module entity, mainly including the module name, the module execution condition, etc.

The business process is composed of a plurality of modules, wherein two modules representing a starting point and an end point are necessary, and a plurality of modules with customized business are also provided, and the number can be freely expanded and contracted.

The connections between modules are represented by module trends, which in turn express the flow direction of the process. Each module has at least one default trend, and the process can flow to the corresponding module without meeting any condition. In addition, the module can be configured with a custom trend, the custom trend must be set with conditions, and the process can flow to the corresponding module only when the corresponding trend conditions are met. The custom orientation of the modules may also be configured in a telescoping manner. The "end" module has no strike.

The modules may be considered to have the same internal execution logic, i.e., each module may be considered to use a single template. But different rules, such as various types of strategies, various process flows, are located on different modules. When the internal execution logic of the module is executed, the type of the rule to which the module belongs is searched and judged, and then the corresponding rule is processed according to the specific internal execution logic corresponding to the rule type. In the event that a rule of some type is missing on a module, the corresponding internal execution logic is not executed.

A module is essentially composed of an infinite number of internal execution logic. The internal execution logic that the module must go to is: initialization of module internal execution logic, module internal main execution logic and module trend execution logic. Other internal execution logic is selected based on the type of rule to which the module belongs. Generally, the internal execution logic of the process flow rule is executed first, and then the internal execution logic of the strategy rule is executed.

And the fourth part is policy management:

1. policy service numbers, i.e., a string of letters and numbers, are used to uniquely identify a policy and are unique within a service view. In addition, each strategy can be provided with a Chinese rule name;

2. the policy type, and the policy type number is used to indicate the type of the policy. The strategy types can be freely expanded by business personnel, and one strategy type only corresponds to one module internal execution logic. When a policy type needs to be extended, in addition to defining a policy type number, a corresponding module internal execution logic needs to be defined. One strategy ontology corresponds to a plurality of strategy instances, and one strategy instance can correspond to a plurality of strategy types;

3. and the module to which the strategy belongs is used for indicating the module in which the strategy is executed. Each policy ontology may belong to multiple modules simultaneously.

4. And the execution priority is used for expressing the execution sequence among the strategy ontologies.

5. The hit conditions are divided into basic hit conditions of the strategy, general configuration conditions and hit conditions of strategy examples. The strategy ontology corresponds to the basic strategy hit condition, and the strategy instance corresponds to the strategy instance hit condition. The strategy instance hit condition is the logic and operation of the strategy basic hit condition and the general configuration condition.

6. The hit results correspond to the policy instance one to one. Because a policy instance can correspond to multiple policy types, each policy instance has a hit result set, and as long as the hit condition of the policy instance is met, the module sequentially calls corresponding module internal execution logic to process the corresponding policy type-result.

7. And self-defining the Chinese description, and corresponding to the strategy examples one by one. Different Chinese descriptions of the same strategy service number under different scenes of service personalized configuration are supported, so that polymorphic configuration of strategy description on a page is supported.

Fifth part, process flow management:

the process flow is a carrier for managing, configuring and executing business variable process logic.

The execution sequence is as follows:

1. judging whether the execution precondition of the processing flow is met, if so, turning to 2, and if not, turning to 10;

2. initializing a machining flow, configuring an execution mode of the current machining flow, and sequentially acquiring subordinate machining items of the current machining flow;

3. judging whether the precondition of the processing item is met, if so, turning to 4, and if not, turning to 10;

4. configuring an execution mode of a current processing item;

5. sequentially selecting the conditions (corresponding to the condition columns of the decision table) to which the processing items belong, and assigning values;

6. judging whether the column conditions are met, if the column conditions are met, rotating 7 is not met, and rotating 8 is not met;

7. sequentially selecting result variable processing functions (corresponding to operation columns of the decision table) to which the processing items belong, and carrying out assignment and operation;

8. judging the execution mode of the processing item, and judging whether the processing item is finished, if so, turning to 9, and if not, turning to 4;

9. judging the execution mode of the processing flow, judging whether the processing flow is finished, if so, turning to 10, and if not, turning to 2;

10. the process flow ends.

Execution mode of process flow/process item. There are three modes, namely, a full execution mode, a hit-end mode, and a loop execution mode. In the full execution mode, the processing flow/processing item will finish processing the processing item/row. In the post-hit finish mode, the process flow/process item enters the finish stage after the process conditions of the process item/row are satisfied. In the circulation execution mode, the processing flow/processing item has circulation conditions, the processing flow/processing item can be circularly executed, and the circulation conditions are judged once after each circulation.

Fig. 13 is a schematic diagram of a computer device for executing a method for designing a rule engine with separated technology view implemented by the present invention, and as shown in fig. 13, an embodiment of the present invention further provides a computer device including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the method for designing a rule engine with separated technology view when executing the computer program.

In an embodiment of the computer device, when the processor executes the computer program, the method for designing a rule engine with separated technology view angles may include:

determining a full-scale library management rule according to the variable library and the function library;

determining a transaction end management rule according to a mapping relation between the interface field and the variable library;

determining a data end management rule according to a mapping relation between a data table and a variable base;

determining a module management rule according to the module definition and the module trend;

establishing a policy management rule according to the module management rule;

determining a processing flow management rule according to the strategy management rule;

and determining a business parameter management interface with separated business technology visual angles according to a full-scale management rule, a transaction end management rule, a data end management rule, a module management rule, a strategy management rule and a processing flow management rule.

In an embodiment, determining a full-scale library management rule according to a variable library and a function library includes:

establishing a variable library according to the variable definition table and the variable enumeration value definition table;

establishing a function library according to the basic function and the compound function;

establishing an internal execution logic library of the module according to the basic logic and the customized logic;

and determining a full-scale library management rule according to the variable library, the function library and the module internal execution logic library.

In an embodiment, the creating a variable library according to a variable definition table and a variable enumeration value definition table includes:

defining variables according to the variable names, the Chinese descriptions and the data types, and determining a variable definition table;

configuring corresponding Chinese description for the fixed value definition of the variable, and determining a quantity enumeration value definition table;

and establishing a variable library according to the variable definition table and the variable enumeration value definition table.

In an embodiment, a variable library supports quick display of a variable-processing logic and maps the variable-processing logic to a corresponding processing item, and a first-use and then-processing mode is adopted for a technical variable; when a technical variable is added, a variable name, Chinese description and a data type are defined, and a processing variable requirement is generated in a project to-be-handled list.

In an embodiment, the method for designing a rule engine with separated technical views is implemented by a processor executing a computer program, and the method for establishing a function library according to a basic function and a complex function includes:

pre-developing functions including simple operation and character processing, expanding by combining service requirements, and determining a basic function;

combining the basic functions according to a set analysis format to determine a composite function;

and establishing a function library according to the basic function and the compound function.

In an embodiment, the method for designing a rule engine with separated technical views is implemented by a processor executing the computer program, and establishing a module internal execution logic library according to a basic logic and a customized logic, including:

taking general execution logic in the module as basic logic;

taking the customized execution logic in the module as the customized logic; the logic customization supports the requirement of business personnel for customizing the internal execution logic of the module, and can freely select and match the internal execution logic of the module with different business scenes;

and establishing an internal execution logic library of the module according to the basic logic and the customized logic.

In an embodiment, the determining the transaction side management rule according to the mapping relationship between the interface field and the variable library includes:

establishing a mutual conversion relation between the interface field and the variable library; the message type of the interface field comprises: request message, response message;

and automatically analyzing each field in the request message to a corresponding variable in the variable library through an interface field-variable library variable mapping relation defined by the service, or assigning the variable in the variable library to the corresponding field in the response message.

In an embodiment, the determining a data-side management rule according to a mapping relationship between a data table and a variable base includes:

establishing a mutual conversion relation between the data table and the variable of the variable base;

and automatically analyzing each field in the request data table to a corresponding variable in the variable database or storing the variable in the variable database to the corresponding field in the data table through the mapping relation between the fields of the data table and the variable database defined by the service.

In an embodiment, the determining module management rules according to the module definition and the module trend includes:

describing relevant information of a module entity according to the module name and the module execution condition, and determining module definition;

dividing a business flow into a starting point module, a destination point module and a plurality of business customizing modules, and taking the connection among the modules as the module trend; the other modules except the terminal module are at least provided with a default trend, and the process can flow to the corresponding module without meeting any condition; the service customization module can also configure a custom trend by utilizing the trend condition;

and determining a module management rule according to the module definition and the module trend.

In an embodiment, the method for designing a rule engine with separated technical views is implemented when the processor executes the computer program, and the establishing a policy management rule according to a module management rule includes:

defining a strategy body name and a strategy belonged module according to a module management rule; the module to which the policy belongs indicates in which module the policy is executed, and each policy ontology may belong to a plurality of modules at the same time;

creating a policy service number; the strategy service number is a character string consisting of a string of letters and numbers and is used for uniquely identifying the strategy;

configuring a strategy type, an example hit condition, an example hit result and a custom description; the strategy types are expanded by business personnel, and one strategy type is only corresponding to each execution logic of one module; the instance hit conditions are divided into basic strategy hit conditions, general configuration conditions and strategy instance hit conditions, the strategy ontology corresponds to the basic strategy hit conditions, the strategy instances correspond to the strategy instance hit conditions, and the strategy instance hit conditions are logic and operation of the basic strategy hit conditions and the general configuration conditions;

and establishing a policy management rule according to the policy ontology name, the policy belonging module, the policy service number, the policy type, the instance hit condition, the instance hit result and the custom description.

In an embodiment, the determining a process flow management rule according to a policy management rule includes:

judging whether the execution precondition of the processing flow is met or not according to the strategy management rule;

if so, initializing the machining flow, configuring an execution mode of the current machining flow, and sequentially acquiring subordinate machining items of the current machining flow;

judging whether the current processing flow meets the precondition of the processing item;

if yes, configuring the execution mode of the current processing item;

sequentially selecting the conditions of the processing items to assign; wherein, the column condition of the processing item corresponds to the condition column of the decision table;

judging whether the processing items meet the row conditions or not;

if yes, selecting result variable processing functions to which the processing items belong in sequence, and carrying out assignment and operation; wherein, the result variable processing function to which the processing item belongs corresponds to the operation column of the decision table;

the execution mode of the current processing item is judged, if the execution mode of the processing item is finished, the execution mode of the current processing flow is judged, and if the execution mode of the processing flow is finished, the current processing flow is finished.

In an embodiment, an execution mode of a process flow or a process item includes: a full execution mode, a hit ending mode and a cyclic execution mode;

under the full execution mode, the processing flow or the processing item finishes processing the processing item or the row to which the processing item or the processing item belongs;

under the hit ending mode, the processing flow or the processing item enters an ending stage after the processing conditions of the processing item or the line are met;

in the circulation execution mode, the processing flow or the processing item has a circulation condition, the processing flow or the processing item can be circularly executed, and the circulation condition is judged after each circulation.

An embodiment of the present invention further provides a computer-readable storage medium, where a computer program for implementing the rule engine design method for technology view separation is stored in the computer-readable storage medium.

In an embodiment, when a computer program for implementing the rule engine design method for technology view separation is stored in a computer-readable storage medium provided by an embodiment of the present invention, the computer-readable storage medium may include:

determining a full-scale library management rule according to the variable library and the function library;

determining a transaction end management rule according to a mapping relation between the interface field and the variable library;

determining a data end management rule according to a mapping relation between a data table and a variable base;

determining a module management rule according to the module definition and the module trend;

establishing a policy management rule according to the module management rule;

determining a processing flow management rule according to the strategy management rule;

and determining a business parameter management interface with separated business technology visual angles according to a full-scale management rule, a transaction end management rule, a data end management rule, a module management rule, a strategy management rule and a processing flow management rule.

In an embodiment, when a computer program for implementing the rule engine design method for technology view separation is stored in a computer readable storage medium, determining a full-scale library management rule according to a variable library and a function library includes:

establishing a variable library according to the variable definition table and the variable enumeration value definition table;

establishing a function library according to the basic function and the compound function;

establishing an internal execution logic library of the module according to the basic logic and the customized logic;

and determining a full-scale library management rule according to the variable library, the function library and the module internal execution logic library.

In a specific implementation, when a computer program for implementing the rule engine design method for technology view separation is stored in a computer readable storage medium provided by an embodiment of the present invention, in an embodiment, establishing a variable library according to a variable definition table and a variable enumeration value definition table includes:

defining variables according to the variable names, the Chinese descriptions and the data types, and determining a variable definition table;

configuring corresponding Chinese description for the fixed value definition of the variable, and determining a quantity enumeration value definition table;

and establishing a variable library according to the variable definition table and the variable enumeration value definition table.

In a specific embodiment, when a computer program for implementing the rule engine design method for technology view separation is stored in the computer readable storage medium, the variable library supports quick display of a variable-processing logic and maps the variable-processing logic to a corresponding processing item, and a first-use and then-processing mode is adopted for a technology variable; when a technical variable is added, a variable name, Chinese description and a data type are defined, and a processing variable requirement is generated in a project to-be-handled list.

In an embodiment, when a computer program for implementing the rule engine design method for technology view separation is stored in the computer readable storage medium, the creating a function library according to a basic function and a complex function includes:

pre-developing functions including simple operation and character processing, expanding by combining service requirements, and determining a basic function;

combining the basic functions according to a set analysis format to determine a composite function;

and establishing a function library according to the basic function and the compound function.

In an embodiment, when a computer program for implementing the rule engine design method for technology view separation is stored in the computer readable storage medium, the establishing a module internal execution logic library according to a basic logic and a customized logic includes:

taking general execution logic in the module as basic logic;

taking the customized execution logic in the module as the customized logic; the logic customization supports the requirement of business personnel for customizing the internal execution logic of the module, and can freely select and match the internal execution logic of the module with different business scenes;

and establishing an internal execution logic library of the module according to the basic logic and the customized logic.

In an embodiment, when a computer program for implementing the rule engine design method for technology view separation is stored in the computer readable storage medium, determining the transaction-side management rule according to the mapping relationship between the interface field and the variable library includes:

establishing a mutual conversion relation between the interface field and the variable library; the message type of the interface field comprises: request message, response message;

and automatically analyzing each field in the request message to a corresponding variable in the variable library through an interface field-variable library variable mapping relation defined by the service, or assigning the variable in the variable library to the corresponding field in the response message.

In an embodiment, when a computer program for implementing the rule engine design method for technology view separation is stored in the computer readable storage medium, determining a data side management rule according to a mapping relationship between a data table and a variable base includes:

establishing a mutual conversion relation between the data table and the variable of the variable base;

and automatically analyzing each field in the request data table to a corresponding variable in the variable database or storing the variable in the variable database to the corresponding field in the data table through the mapping relation between the fields of the data table and the variable database defined by the service.

In an embodiment, when a computer program for implementing the rule engine design method for technology view separation is stored in the computer readable storage medium, determining the module management rule according to the module definition and the module trend includes:

describing relevant information of a module entity according to the module name and the module execution condition, and determining module definition;

dividing a business flow into a starting point module, a destination point module and a plurality of business customizing modules, and taking the connection among the modules as the module trend; the other modules except the terminal module are at least provided with a default trend, and the process can flow to the corresponding module without meeting any condition; the service customization module can also configure a custom trend by utilizing the trend condition;

and determining a module management rule according to the module definition and the module trend.

In an embodiment, when a computer program for implementing the rule engine design method for technology view separation is stored in the computer readable storage medium, the establishing a policy management rule according to a module management rule includes:

defining a strategy body name and a strategy belonged module according to a module management rule; the module to which the policy belongs indicates in which module the policy is executed, and each policy ontology may belong to a plurality of modules at the same time;

creating a policy service number; the strategy service number is a character string consisting of a string of letters and numbers and is used for uniquely identifying the strategy;

configuring a strategy type, an example hit condition, an example hit result and a custom description; the strategy types are expanded by business personnel, and one strategy type is only corresponding to each execution logic of one module; the instance hit conditions are divided into basic strategy hit conditions, general configuration conditions and strategy instance hit conditions, the strategy ontology corresponds to the basic strategy hit conditions, the strategy instances correspond to the strategy instance hit conditions, and the strategy instance hit conditions are logic and operation of the basic strategy hit conditions and the general configuration conditions;

and establishing a policy management rule according to the policy ontology name, the policy belonging module, the policy service number, the policy type, the instance hit condition, the instance hit result and the custom description.

In an embodiment, when a computer program for implementing the rule engine design method for technology view separation is stored in a computer readable storage medium, determining a process flow management rule according to a policy management rule includes:

judging whether the execution precondition of the processing flow is met or not according to the strategy management rule;

if so, initializing the machining flow, configuring an execution mode of the current machining flow, and sequentially acquiring subordinate machining items of the current machining flow;

judging whether the current processing flow meets the precondition of the processing item;

if yes, configuring the execution mode of the current processing item;

sequentially selecting the conditions of the processing items to assign; wherein, the column condition of the processing item corresponds to the condition column of the decision table;

judging whether the processing items meet the row conditions or not;

if yes, selecting result variable processing functions to which the processing items belong in sequence, and carrying out assignment and operation; wherein, the result variable processing function to which the processing item belongs corresponds to the operation column of the decision table;

the execution mode of the current processing item is judged, if the execution mode of the processing item is finished, the execution mode of the current processing flow is judged, and if the execution mode of the processing flow is finished, the current processing flow is finished.

In an embodiment, when a computer program for implementing the rule engine design method for technology view separation is stored in a computer-readable storage medium, an execution mode of a process flow or a process item includes: a full execution mode, a hit ending mode and a cyclic execution mode;

under the full execution mode, the processing flow or the processing item finishes processing the processing item or the row to which the processing item or the processing item belongs;

under the hit ending mode, the processing flow or the processing item enters an ending stage after the processing conditions of the processing item or the line are met;

in the circulation execution mode, the processing flow or the processing item has a circulation condition, the processing flow or the processing item can be circularly executed, and the circulation condition is judged after each circulation.

The embodiment of the present invention further provides a rule engine design apparatus with separated technology views, as described in the following embodiments. Because the principle of solving the problems of the device is similar to the rule engine design method with the separated technical view angle, the implementation of the device can refer to the implementation of the rule engine design method with the separated technical view angle, and repeated parts are not repeated.

Fig. 14 is a schematic diagram of a rule engine design device with separated technology views according to an embodiment of the present invention, and as shown in fig. 14, an embodiment of the present invention further provides a rule engine design device with separated technology views, which may include:

a full-scale library management rule determining module 1401, configured to determine a full-scale library management rule according to the variable library and the function library;

a transaction side management rule determining module 1402, configured to determine a transaction side management rule according to a mapping relationship between the interface field and the variable library;

a data side management rule determining module 1403, configured to determine a data side management rule according to a mapping relationship between the data table and the variable library;

a module management rule determining module 1404, configured to determine a module management rule according to the module definition and the module trend;

a policy management rule determining module 1405, configured to establish a policy management rule according to a module management rule;

a process flow management rule determining module 1406 for determining a process flow management rule according to the policy management rule;

the service parameter management interface determining module 1407 is configured to determine a service parameter management interface with a service technology view separation according to a full-scale management rule, a transaction-side management rule, a data-side management rule, a module management rule, a policy management rule, and a process flow management rule.

In an embodiment of the present invention, when the apparatus for designing a rule engine with separated technology views is implemented specifically, the module for determining a total library management rule is specifically configured to:

establishing a variable library according to the variable definition table and the variable enumeration value definition table;

establishing a function library according to the basic function and the compound function;

establishing an internal execution logic library of the module according to the basic logic and the customized logic;

and determining a full-scale library management rule according to the variable library, the function library and the module internal execution logic library.

In a specific implementation of the apparatus for designing a rule engine with separated technical views provided in an embodiment of the present invention, in an embodiment, the full-scale library management rule determining module is further configured to:

defining variables according to the variable names, the Chinese descriptions and the data types, and determining a variable definition table;

configuring corresponding Chinese description for the fixed value definition of the variable, and determining a quantity enumeration value definition table;

and establishing a variable library according to the variable definition table and the variable enumeration value definition table.

When the technical view-separated rule engine design device provided by the embodiment of the invention is specifically implemented, in one embodiment, the variable library supports quick display of variable-processing logic and maps the variable-processing logic to a corresponding processing item, and a mode of using the technical variable first and then processing the technical variable is adopted; when a technical variable is added, a variable name, Chinese description and a data type are defined, and a processing variable requirement is generated in a project to-be-handled list.

In a specific implementation of the apparatus for designing a rule engine with separated technical views provided in an embodiment of the present invention, in an embodiment, the full-scale library management rule determining module is further configured to:

pre-developing functions including simple operation and character processing, expanding by combining service requirements, and determining a basic function;

combining the basic functions according to a set analysis format to determine a composite function;

and establishing a function library according to the basic function and the compound function.

In a specific implementation of the apparatus for designing a rule engine with separated technical views provided in an embodiment of the present invention, in an embodiment, the full-scale library management rule determining module is further configured to:

taking general execution logic in the module as basic logic;

taking the customized execution logic in the module as the customized logic; the logic customization supports the requirement of business personnel for customizing the internal execution logic of the module, and can freely select and match the internal execution logic of the module with different business scenes;

and establishing an internal execution logic library of the module according to the basic logic and the customized logic.

When the apparatus for designing a rule engine with separated technology views provided in an embodiment of the present invention is implemented specifically, in an embodiment, the transaction side management rule determining module is specifically configured to:

establishing a mutual conversion relation between the interface field and the variable library; the message type of the interface field comprises: request message, response message;

and automatically analyzing each field in the request message to a corresponding variable in the variable library through an interface field-variable library variable mapping relation defined by the service, or assigning the variable in the variable library to the corresponding field in the response message.

In an embodiment of the present invention, when the apparatus for designing a rule engine with separated technology views is implemented specifically, the data side management rule determining module is specifically configured to:

establishing a mutual conversion relation between the data table and the variable of the variable base;

and automatically analyzing each field in the request data table to a corresponding variable in the variable database or storing the variable in the variable database to the corresponding field in the data table through the mapping relation between the fields of the data table and the variable database defined by the service.

In an embodiment of the present invention, when implementing the rule engine design apparatus with separated technology views, the module management rule determining module is specifically configured to:

describing relevant information of a module entity according to the module name and the module execution condition, and determining module definition;

dividing a business flow into a starting point module, a destination point module and a plurality of business customizing modules, and taking the connection among the modules as the module trend; the other modules except the terminal module are at least provided with a default trend, and the process can flow to the corresponding module without meeting any condition; the service customization module can also configure a custom trend by utilizing the trend condition;

and determining a module management rule according to the module definition and the module trend.

When the apparatus for designing a rule engine with separated technology views provided in an embodiment of the present invention is implemented specifically, in an embodiment, the policy management rule determining module is specifically configured to:

defining a strategy body name and a strategy belonged module according to a module management rule; the module to which the policy belongs indicates in which module the policy is executed, and each policy ontology may belong to a plurality of modules at the same time;

creating a policy service number; the strategy service number is a character string consisting of a string of letters and numbers and is used for uniquely identifying the strategy;

configuring a strategy type, an example hit condition, an example hit result and a custom description; the strategy types are expanded by business personnel, and one strategy type is only corresponding to each execution logic of one module; the instance hit conditions are divided into basic strategy hit conditions, general configuration conditions and strategy instance hit conditions, the strategy ontology corresponds to the basic strategy hit conditions, the strategy instances correspond to the strategy instance hit conditions, and the strategy instance hit conditions are logic and operation of the basic strategy hit conditions and the general configuration conditions;

and establishing a policy management rule according to the policy ontology name, the policy belonging module, the policy service number, the policy type, the instance hit condition, the instance hit result and the custom description.

In an embodiment of the present invention, when the apparatus for designing a rule engine with separated technical views is implemented specifically, the process flow management rule determining module is specifically configured to:

judging whether the execution precondition of the processing flow is met or not according to the strategy management rule;

if so, initializing the machining flow, configuring an execution mode of the current machining flow, and sequentially acquiring subordinate machining items of the current machining flow;

judging whether the current processing flow meets the precondition of the processing item;

if yes, configuring the execution mode of the current processing item;

sequentially selecting the conditions of the processing items to assign; wherein, the column condition of the processing item corresponds to the condition column of the decision table;

judging whether the processing items meet the row conditions or not;

if yes, selecting result variable processing functions to which the processing items belong in sequence, and carrying out assignment and operation; wherein, the result variable processing function to which the processing item belongs corresponds to the operation column of the decision table;

the execution mode of the current processing item is judged, if the execution mode of the processing item is finished, the execution mode of the current processing flow is judged, and if the execution mode of the processing flow is finished, the current processing flow is finished.

In an embodiment of the invention, when implementing the rule engine design apparatus with separated technology views, an execution mode of a process flow or a process item includes: a full execution mode, a hit ending mode and a cyclic execution mode;

under the full execution mode, the processing flow or the processing item finishes processing the processing item or the row to which the processing item or the processing item belongs;

under the hit ending mode, the processing flow or the processing item enters an ending stage after the processing conditions of the processing item or the line are met;

in the circulation execution mode, the processing flow or the processing item has a circulation condition, the processing flow or the processing item can be circularly executed, and the circulation condition is judged after each circulation.

To sum up, the method and apparatus for designing a rule engine with separated technology views provided by the embodiments of the present invention include: firstly, determining a full-scale library management rule according to a variable library and a function library; then, determining a transaction end management rule according to a mapping relation between the interface field and the variable library; determining a data end management rule according to a mapping relation between the data table and the variable base; determining module management rules according to the module definition and the module trend; next, establishing a strategy management rule according to the module management rule; determining a processing flow management rule according to the strategy management rule; and finally, determining a business parameter management interface with separated business technology visual angles according to a full-scale management rule, a transaction end management rule, a data end management rule, a module management rule, a strategy management rule and a processing flow management rule. The technical scheme of the embodiment of the invention with separated service technical views distinguishes the service view from the technical view and defines the authority scope of service personnel and technical personnel. The business personnel only need to configure the flow module, the business rule and the relevant variable parameter which can be efficiently managed by the business personnel to realize the business logic of the business personnel without concerning the realization of the specific logic. Technical personnel only need to process variables required by the business, support related technical functions and realize related technologies without being limited by a realization method, thereby avoiding unnecessary difficulties. Through the design and maintenance scheme which is relatively independent and convenient for the service view, when the service requirement details are changed frequently or maintained and changed, the service can be changed flexibly without depending on technology cooperation, and the current situations that the version is repeatedly deployed and on-line, and the flow is long and time-consuming are avoided. Through the efficient and easy-to-understand design of the business view, business personnel can actively and actively use and participate in development, and business function configuration can be conveniently and efficiently carried out; by maintaining the dependency relationship between the variables and the related processing logic, the function points and technical details which need to be checked are dynamically prompted after the business logic is changed. The workload of manually searching and judging related function points is reduced, the difficulty of function or technology development and maintenance is reduced, and detail loopholes caused by forgetting or unfamiliarity of related maintenance personnel to business logic details are avoided.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the present invention in further detail, and it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.

Claims (26)

1. A design method of a rule engine with separated technical view angles is characterized by comprising the following steps:

determining a full-scale library management rule according to the variable library and the function library;

determining a transaction end management rule according to a mapping relation between the interface field and the variable library;

determining a data end management rule according to a mapping relation between a data table and a variable base;

determining a module management rule according to the module definition and the module trend;

establishing a policy management rule according to the module management rule;

determining a processing flow management rule according to the strategy management rule;

and determining a business parameter management interface with separated business technology visual angles according to a full-scale management rule, a transaction end management rule, a data end management rule, a module management rule, a strategy management rule and a processing flow management rule.

2. The method of claim 1, wherein determining full-scale library management rules from a library of variables and a library of functions comprises:

establishing a variable library according to the variable definition table and the variable enumeration value definition table;

establishing a function library according to the basic function and the compound function;

establishing an internal execution logic library of the module according to the basic logic and the customized logic;

and determining a full-scale library management rule according to the variable library, the function library and the module internal execution logic library.

3. The method of claim 2, wherein building a variable library from a variable definition table and a variable enumeration value definition table comprises:

defining variables according to the variable names, the Chinese descriptions and the data types, and determining a variable definition table;

configuring corresponding Chinese description for the fixed value definition of the variable, and determining a quantity enumeration value definition table;

and establishing a variable library according to the variable definition table and the variable enumeration value definition table.

4. The method of claim 3, wherein the variable library supports quick display and mapping of variable-to-process logic to corresponding process items, taking a use-first-then-process approach to technical variables; when a technical variable is added, a variable name, Chinese description and a data type are defined, and a processing variable requirement is generated in a project to-be-handled list.

5. The method of claim 2, wherein building a library of functions from the basis functions and the complex functions comprises:

pre-developing functions including simple operation and character processing, expanding by combining service requirements, and determining a basic function;

combining the basic functions according to a set analysis format to determine a composite function;

and establishing a function library according to the basic function and the compound function.

6. The method of claim 2, wherein building a library of intra-module execution logic based on the base logic and the custom logic comprises:

taking general execution logic in the module as basic logic;

taking the customized execution logic in the module as the customized logic; the logic customization supports the requirement of business personnel for customizing the internal execution logic of the module, and can freely select and match the internal execution logic of the module with different business scenes;

and establishing an internal execution logic library of the module according to the basic logic and the customized logic.

7. The method of claim 1, wherein determining transaction side management rules based on the mapping between the interface fields and the variable library comprises:

establishing a mutual conversion relation between the interface field and the variable library; the message type of the interface field comprises: request message, response message;

and automatically analyzing each field in the request message to a corresponding variable in the variable library through an interface field-variable library variable mapping relation defined by the service, or assigning the variable in the variable library to the corresponding field in the response message.

8. The method of claim 1, wherein determining the data-side management rule based on the mapping between the data table and the variable repository comprises:

establishing a mutual conversion relation between the data table and the variable of the variable base;

and automatically analyzing each field in the request data table to a corresponding variable in the variable database or storing the variable in the variable database to the corresponding field in the data table through the mapping relation between the fields of the data table and the variable database defined by the service.

9. The method of claim 1, wherein determining module management rules based on module definitions and module trends comprises:

describing relevant information of a module entity according to the module name and the module execution condition, and determining module definition;

dividing a business flow into a starting point module, a destination point module and a plurality of business customizing modules, and taking the connection among the modules as the module trend; the other modules except the terminal module are at least provided with a default trend, and the process can flow to the corresponding module without meeting any condition; the service customization module can also configure a custom trend by utilizing the trend condition;

and determining a module management rule according to the module definition and the module trend.

10. The method of claim 1, wherein establishing policy management rules based on module management rules comprises:

defining a strategy body name and a strategy belonged module according to a module management rule; the module to which the policy belongs indicates in which module the policy is executed, and each policy ontology may belong to a plurality of modules at the same time;

creating a policy service number; the strategy service number is a character string consisting of a string of letters and numbers and is used for uniquely identifying the strategy;

configuring a strategy type, an example hit condition, an example hit result and a custom description; the strategy types are expanded by business personnel, and one strategy type is only corresponding to each execution logic of one module; the instance hit conditions are divided into basic strategy hit conditions, general configuration conditions and strategy instance hit conditions, the strategy ontology corresponds to the basic strategy hit conditions, the strategy instances correspond to the strategy instance hit conditions, and the strategy instance hit conditions are logic and operation of the basic strategy hit conditions and the general configuration conditions;

and establishing a policy management rule according to the policy ontology name, the policy belonging module, the policy service number, the policy type, the instance hit condition, the instance hit result and the custom description.

11. The method of claim 1, wherein determining process flow management rules based on policy management rules comprises:

judging whether the execution precondition of the processing flow is met or not according to the strategy management rule;

if so, initializing the machining flow, configuring an execution mode of the current machining flow, and sequentially acquiring subordinate machining items of the current machining flow;

judging whether the current processing flow meets the precondition of the processing item;

if yes, configuring the execution mode of the current processing item;

sequentially selecting the conditions of the processing items to assign; wherein, the column condition of the processing item corresponds to the condition column of the decision table;

judging whether the processing items meet the row conditions or not;

if yes, selecting result variable processing functions to which the processing items belong in sequence, and carrying out assignment and operation; wherein, the result variable processing function to which the processing item belongs corresponds to the operation column of the decision table;

the execution mode of the current processing item is judged, if the execution mode of the processing item is finished, the execution mode of the current processing flow is judged, and if the execution mode of the processing flow is finished, the current processing flow is finished.

12. The method of claim 11, wherein the execution pattern of the process flow or process item comprises: a full execution mode, a hit ending mode and a cyclic execution mode;

under the full execution mode, the processing flow or the processing item finishes processing the processing item or the row to which the processing item or the processing item belongs;

under the hit ending mode, the processing flow or the processing item enters an ending stage after the processing conditions of the processing item or the line are met;

in the circulation execution mode, the processing flow or the processing item has a circulation condition, the processing flow or the processing item can be circularly executed, and the circulation condition is judged after each circulation.

13. A split-technology-view rules engine design apparatus, comprising:

the system comprises a full-scale library management rule determining module, a full-scale library management rule determining module and a full-scale library management rule determining module, wherein the full-scale library management rule determining module is used for determining a full-scale library management rule according to a variable library and a function library;

the transaction end management rule determining module is used for determining the transaction end management rule according to the mapping relation between the interface field and the variable library;

the data end management rule determining module is used for determining a data end management rule according to the mapping relation between the data table and the variable base;

the module management rule determining module is used for determining a module management rule according to the module definition and the module trend;

the strategy management rule determining module is used for establishing a strategy management rule according to the module management rule;

the processing flow management rule determining module is used for determining the processing flow management rule according to the strategy management rule;

and the service parameter management interface determining module is used for determining a service parameter management interface with separated service technology visual angles according to a full-scale management rule, a transaction end management rule, a data end management rule, a module management rule, a strategy management rule and a processing flow management rule.

14. The apparatus of claim 13, wherein the full scale library management rule determining module is specifically configured to:

establishing a variable library according to the variable definition table and the variable enumeration value definition table;

establishing a function library according to the basic function and the compound function;

establishing an internal execution logic library of the module according to the basic logic and the customized logic;

and determining a full-scale library management rule according to the variable library, the function library and the module internal execution logic library.

15. The apparatus of claim 14, wherein the full scale library management rule determination module is further to:

defining variables according to the variable names, the Chinese descriptions and the data types, and determining a variable definition table;

configuring corresponding Chinese description for the fixed value definition of the variable, and determining a quantity enumeration value definition table;

and establishing a variable library according to the variable definition table and the variable enumeration value definition table.

16. The apparatus of claim 15, wherein the variable library supports quick display and mapping of variable-to-process logic to corresponding process items, taking a use-first-then-process approach to technical variables; when a technical variable is added, a variable name, Chinese description and a data type are defined, and a processing variable requirement is generated in a project to-be-handled list.

17. The apparatus of claim 14, wherein the full scale library management rule determination module is further to:

pre-developing functions including simple operation and character processing, expanding by combining service requirements, and determining a basic function;

combining the basic functions according to a set analysis format to determine a composite function;

and establishing a function library according to the basic function and the compound function.

18. The apparatus of claim 14, wherein the full scale library management rule determination module is further to:

taking general execution logic in the module as basic logic;

taking the customized execution logic in the module as the customized logic; the logic customization supports the requirement of business personnel for customizing the internal execution logic of the module, and can freely select and match the internal execution logic of the module with different business scenes;

and establishing an internal execution logic library of the module according to the basic logic and the customized logic.

19. The apparatus of claim 13, wherein the transaction side management rule determination module is specifically configured to:

establishing a mutual conversion relation between the interface field and the variable library; the message type of the interface field comprises: request message, response message;

and automatically analyzing each field in the request message to a corresponding variable in the variable library through an interface field-variable library variable mapping relation defined by the service, or assigning the variable in the variable library to the corresponding field in the response message.

20. The apparatus of claim 13, wherein the data side management rule determining module is specifically configured to:

establishing a mutual conversion relation between the data table and the variable of the variable base;

and automatically analyzing each field in the request data table to a corresponding variable in the variable database or storing the variable in the variable database to the corresponding field in the data table through the mapping relation between the fields of the data table and the variable database defined by the service.

21. The apparatus of claim 13, wherein the module management rule determination module is specifically configured to:

describing relevant information of a module entity according to the module name and the module execution condition, and determining module definition;

dividing a business flow into a starting point module, a destination point module and a plurality of business customizing modules, and taking the connection among the modules as the module trend; the other modules except the terminal module are at least provided with a default trend, and the process can flow to the corresponding module without meeting any condition; the service customization module can also configure a custom trend by utilizing the trend condition;

and determining a module management rule according to the module definition and the module trend.

22. The apparatus of claim 13, wherein the policy management rule determining module is specifically configured to:

defining a strategy body name and a strategy belonged module according to a module management rule; the module to which the policy belongs indicates in which module the policy is executed, and each policy ontology may belong to a plurality of modules at the same time;

creating a policy service number; the strategy service number is a character string consisting of a string of letters and numbers and is used for uniquely identifying the strategy;

configuring a strategy type, an example hit condition, an example hit result and a custom description; the strategy types are expanded by business personnel, and one strategy type is only corresponding to each execution logic of one module; the instance hit conditions are divided into basic strategy hit conditions, general configuration conditions and strategy instance hit conditions, the strategy ontology corresponds to the basic strategy hit conditions, the strategy instances correspond to the strategy instance hit conditions, and the strategy instance hit conditions are logic and operation of the basic strategy hit conditions and the general configuration conditions;

and establishing a policy management rule according to the policy ontology name, the policy belonging module, the policy service number, the policy type, the instance hit condition, the instance hit result and the custom description.

23. The apparatus of claim 13, wherein the process flow management rule determination module is specifically configured to:

judging whether the execution precondition of the processing flow is met or not according to the strategy management rule;

if so, initializing the machining flow, configuring an execution mode of the current machining flow, and sequentially acquiring subordinate machining items of the current machining flow;

judging whether the current processing flow meets the precondition of the processing item;

if yes, configuring the execution mode of the current processing item;

sequentially selecting the conditions of the processing items to assign; wherein, the column condition of the processing item corresponds to the condition column of the decision table;

judging whether the processing items meet the row conditions or not;

if yes, selecting result variable processing functions to which the processing items belong in sequence, and carrying out assignment and operation; wherein, the result variable processing function to which the processing item belongs corresponds to the operation column of the decision table;

the execution mode of the current processing item is judged, if the execution mode of the processing item is finished, the execution mode of the current processing flow is judged, and if the execution mode of the processing flow is finished, the current processing flow is finished.

24. The apparatus of claim 23, wherein the execution pattern of the process stream or process item comprises: a full execution mode, a hit ending mode and a cyclic execution mode;

under the full execution mode, the processing flow or the processing item finishes processing the processing item or the row to which the processing item or the processing item belongs;

under the hit ending mode, the processing flow or the processing item enters an ending stage after the processing conditions of the processing item or the line are met;

in the circulation execution mode, the processing flow or the processing item has a circulation condition, the processing flow or the processing item can be circularly executed, and the circulation condition is judged after each circulation.

25. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any of claims 1 to 12 when executing the computer program.

26. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program for executing a method according to any one of claims 1 to 12.

Images