CN116204177A - System service module development coupling assembly method and device and computer equipment - Google Patents

System service module development coupling assembly method and device and computer equipment Download PDF

Info

Publication number
CN116204177A
CN116204177A CN202310266482.4A CN202310266482A CN116204177A CN 116204177 A CN116204177 A CN 116204177A CN 202310266482 A CN202310266482 A CN 202310266482A CN 116204177 A CN116204177 A CN 116204177A
Authority
CN
China
Prior art keywords
customized
business
rule
event
target type
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202310266482.4A
Other languages
Chinese (zh)
Other versions
CN116204177B (en
Inventor
邝启康
张誉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hubei Kunying Digital Technology Co ltd
Original Assignee
Hubei Kunying Digital Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hubei Kunying Digital Technology Co ltd filed Critical Hubei Kunying Digital Technology Co ltd
Priority to CN202310266482.4A priority Critical patent/CN116204177B/en
Publication of CN116204177A publication Critical patent/CN116204177A/en
Application granted granted Critical
Publication of CN116204177B publication Critical patent/CN116204177B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • G06F8/36Software reuse
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/20Software design
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • G06F8/38Creation or generation of source code for implementing user interfaces
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02PCLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30Computing systems specially adapted for manufacturing

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Stored Programmes (AREA)

Abstract

The invention discloses a system service module development coupling assembly method, a system service module development coupling assembly device and computer equipment, and relates to the technical field of service systems. After a business rule target type, an execution event target type and at least one trigger condition defined by a user for a business module to be developed are obtained, at least one customized business rule belonging to the business rule target type is searched from all developed business modules, at least one customized executable event belonging to the execution event target type is searched from the customized business rules, and finally the at least one trigger condition and the at least one customized executable event are assembled together through a rule designer to form a customized business rule of the business module to be developed, so that the whole process is simplified and simplified by multiplexing the customized business rule and the customized executable event therein in the process of developing the business module, and the customization efficiency and the module development speed are improved.

Description

System service module development coupling assembly method and device and computer equipment
Technical Field
The invention belongs to the technical field of service systems, and particularly relates to a system service module development coupling assembly method, a system service module development coupling assembly device and computer equipment.
Background
When business processing is performed by enterprises and public institutions, in order to improve the business processing efficiency of a business system, a business rule making personnel is generally required to write a large number of business processing strategies or business rules to guide the business system to perform business processing. In general, the written business rules are all business rules applicable to a specific Application scenario, for example, business rules applicable to a single country, business rules applicable to APP (Application) marketing ticket issuance, and the like.
Conventional business rule execution generally executes a custom event if a trigger condition is satisfied, i.e., the combination of the trigger condition and the executable event can be regarded as a specific form of the business rule. In this case, even though the business processing logic of the business rules is the same, the specific form of the business rules in each application scenario may be different. For example, the business processing logic for different countries is the same business transaction rule, and the business transaction rule is assumed to include the limit of transaction amount and transaction time (i.e. as a trigger condition).
At present, under the condition that service processing logics of service rules are the same for different application scenes, new service rules are required to be rewritten for each application scene, so that great time and effort are required for formulating personnel, and therefore, in the development process of service modules of the existing service system, the problems of complex process, redundancy, poor customization efficiency and low development speed caused by low multiplexing rate of customized service rules are commonly existed.
Disclosure of Invention
The invention aims to provide a system service module development coupling assembly method, a system service module development coupling assembly device, computer equipment and a computer readable storage medium, which are used for solving the problems of complex process redundancy, poor customization efficiency and slow development speed caused by low multiplexing rate of customized service rules in the service module development process of the existing service system.
In order to achieve the above purpose, the present invention adopts the following technical scheme:
in a first aspect, a system service module development coupling assembly method is provided, including:
acquiring a business rule target type, an execution event target type and at least one triggering condition which are defined by a user for a business module to be developed in a business system;
According to the business rule target type, at least one customized business rule belonging to the business rule target type is searched from all developed business modules, wherein the developed business modules are business modules with a set of customized business rules applicable to specific business scenes, and the customized business rules comprise a plurality of customized executable events;
according to the execution event target type, at least one customized executable event belonging to the execution event target type is searched from the at least one customized business rule;
and assembling the at least one triggering condition and the at least one customized executable event together by a rule designer to form a customized business rule of the business module to be developed.
Based on the above summary, a new solution is provided for developing a service module capable of multiplexing a customized service rule, that is, after a service rule target type, an execution event target type and at least one trigger condition defined by a user for a service module to be developed in a service system are obtained, at least one customized service rule belonging to the service rule target type is first searched from all developed service modules, then at least one customized executable event belonging to the execution event target type is searched from the at least one customized service rule, and finally the at least one trigger condition and the at least one customized executable event are assembled together by a rule designer to form a customized service rule of the service module to be developed, so that the whole process is simplified, the customization efficiency is improved, the module development speed is accelerated, the workload of service rule formulator is reduced, and practical application and popularization are facilitated by multiplexing the customized service rule and the customized executable event therein.
In one possible design, when the customized business rule further includes a plurality of customized triggering conditions, according to the execution event target type, at least one customized executable event belonging to the execution event target type is found from the at least one customized business rule, including:
for each customized business rule in the at least one customized business rule, if the corresponding rule contains customized executable events belonging to the execution event target type, determining the corresponding rule as a business rule to be screened;
aiming at each service rule to be screened, calculating to obtain the similarity between all customized triggering conditions and at least one triggering condition in the corresponding rule;
and taking the business rule to be screened with the maximum similarity as a business rule to be copied, and taking all the customized executable events which belong to the execution event target type in the business rule to be copied as at least one customized executable event which is searched from the at least one customized business rule and belongs to the execution event target type.
In one possible design, for a certain business rule to be screened, calculating to obtain the similarity between the at least one trigger condition and all the customized trigger conditions corresponding to the business rule to be screened, where the similarity includes:
According to all customized triggering conditions in the certain business rule to be screened, each customized triggering condition is spliced in sequence through different arrangement modes to obtain M-! A first string, wherein M represents the total number of customized trigger conditions in the certain business rule to be screened, +|! Representing a mathematical factorial symbol;
according to the at least one trigger condition, each trigger condition is spliced in sequence through different arrangement modes to obtain N-! A second string, wherein N represents a total number of trigger conditions in the at least one trigger condition;
calculating and obtaining the information of the M-! Each first character string of the first character strings is associated with the first character string in the N-! Edit distance of each second character string in the second character strings;
and taking the calculated reciprocal of the minimum editing distance as the similarity between all the customized triggering conditions in the certain business rule to be screened and the at least one triggering condition.
In one possible design, when the customized business rule further includes a plurality of customized triggering conditions, according to the execution event target type, at least one customized executable event belonging to the execution event target type is found from the at least one customized business rule, including:
Determining, for each customized business rule in the at least one customized business rule, a conditional intersection of all customized trigger conditions corresponding and in the corresponding rule with the at least one trigger condition;
taking the customized business rule with the most condition intersection elements as a business rule to be copied, and taking all customized executable events which belong to the execution event target type in the business rule to be copied as at least one customized executable event which is searched from the at least one customized business rule and belongs to the execution event target type.
In one possible design, according to the execution event target type, finding at least one customized executable event belonging to the execution event target type from the at least one customized business rule includes:
determining, for each customized business rule in the at least one customized business rule, a total number of events of the customized executable events corresponding to and belonging to the execution event target type in the corresponding rule;
taking the customized business rule with the highest total number of events as a business rule to be copied, and taking all customized executable events which belong to the execution event target type in the business rule to be copied as at least one customized executable event which is searched from the at least one customized business rule and belongs to the execution event target type.
In one possible design, assembling the at least one trigger condition and the at least one customized executable event together by a rule designer to form a customized business rule for the business module to be developed, comprising:
importing the at least one triggering condition and the at least one customized executable event into a rule designer, and displaying the at least one customized executable event on a man-machine interaction interface of the rule designer;
responding to man-machine interaction operation generated by the user on the man-machine interaction interface, and performing event rejection processing, event modification processing and/or event sorting processing on the at least one customized executable event to obtain at least one new customized executable event;
and assembling the at least one triggering condition and the at least one new customized executable event together by the rule designer to form a customized business rule of the business module to be developed.
In one possible design, the business rule target type is a business transaction rule type, a business wind control rule type or a business operation rule type, and the execution event target type is a circulation event type, a reminding event type, a payment event type or a push event type.
The second aspect provides a system service module development coupling assembly device, which comprises a definition content acquisition module, a service rule searching module, an executable event searching module and a service rule assembling module which are connected in sequence in a communication way;
the definition content acquisition module is used for acquiring a business rule target type, an execution event target type and at least one triggering condition which are defined by a user for a business module to be developed in a business system;
the business rule searching module is used for searching at least one customized business rule belonging to the business rule target type from all developed business modules according to the business rule target type, wherein the developed business modules are business modules with a set of customized business rules applicable to specific business scenes, and the customized business rules comprise a plurality of customized executable events;
the executable event searching module is used for searching at least one customized executable event belonging to the execution event target type from the at least one customized business rule according to the execution event target type;
the business rule assembling module is used for assembling the at least one triggering condition and the at least one customized executable event together through a rule designer to form the customized business rule of the business module to be developed.
In a third aspect, the present invention provides a computer device comprising a memory, a processor and a transceiver in communication connection in turn, wherein the memory is configured to store a computer program, the transceiver is configured to send and receive messages, and the processor is configured to read the computer program, and perform the system service module development coupling assembly method according to the first aspect or any of the possible designs of the first aspect.
In a fourth aspect, the present invention provides a computer readable storage medium having instructions stored thereon which, when executed on a computer, perform a system business module development coupling assembly method as described in the first aspect or any of the possible designs of the first aspect.
In a fifth aspect, the present invention provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the system business module development coupling assembly method of the first aspect or any of the possible designs of the first aspect.
The beneficial effect of above-mentioned scheme:
(1) The invention creatively provides a new scheme for developing a business module capable of multiplexing customized business rules, namely after a business rule target type, an execution event target type and at least one trigger condition defined by a user for a business module to be developed in a business system are obtained, at least one customized business rule belonging to the business rule target type is searched from all the developed business modules, then at least one customized executable event belonging to the execution event target type is searched from the at least one customized business rule, and finally the at least one trigger condition and the at least one customized executable event are assembled together through a rule designer to form a customized business rule of the business module to be developed, so that the whole process is simplified and simplified through multiplexing the customized business rule and the customized executable event therein, the customization efficiency is improved, the module development speed is accelerated, the workload of business rule formulators is reduced, and the practical application and popularization are facilitated;
(2) The triggering condition can be used as a service scene characteristic, the similarity between the service scene of the service rule to be screened and the target service scene of the service module to be developed is calculated, and the customized executable event which is most in line with the user requirement is accurately screened by utilizing the similarity, so that the purpose of greatly reducing the number of events in the screening result can be realized, and the subsequent manual adjustment difficulty is reduced;
(3) The similarity between the service scene of the customized service rule and the target service scene of the service module to be developed can be positively reflected by utilizing the degree of the same triggering condition, and the customized executable events which are most in line with the requirements of the user can be precisely screened by utilizing the similarity, so that the purpose of greatly reducing the number of the events in the screening result can be realized, and the subsequent manual adjustment difficulty is reduced.
Drawings
In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flow chart of a system service module development coupling assembly method according to an embodiment of the present application.
Fig. 2 is a schematic structural diagram of a system service module development coupling assembly device according to an embodiment of the present application.
Fig. 3 is a schematic structural diagram of a computer device according to an embodiment of the present application.
Detailed Description
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the present invention will be briefly described below with reference to the accompanying drawings and the description of the embodiments or the prior art, and it is obvious that the following description of the structure of the drawings is only some embodiments of the present invention, and other drawings can be obtained according to these drawings without inventive effort to a person skilled in the art. It should be noted that the description of these examples is for aiding in understanding the present invention, but is not intended to limit the present invention.
It should be understood that although the terms first and second, etc. may be used herein to describe various objects, these objects should not be limited by these terms. These terms are only used to distinguish one object from another. For example, a first object may be referred to as a second object, and similarly a second object may be referred to as a first object, without departing from the scope of example embodiments of the invention.
It should be understood that for the term "and/or" that may appear herein, it is merely one association relationship that describes an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: three cases of A alone, B alone or both A and B exist; as another example, A, B and/or C, can represent the presence of any one of A, B and C or any combination thereof; for the term "/and" that may appear herein, which is descriptive of another associative object relationship, it means that there may be two relationships, e.g., a/and B, it may be expressed that: the two cases of A and B exist independently or simultaneously; in addition, for the character "/" that may appear herein, it is generally indicated that the context associated object is an "or" relationship.
Examples:
as shown in fig. 1, the system service module development coupling assembly method provided in the first aspect of the present embodiment may be performed by, but not limited to, a computer device with a certain computing resource, for example, a platform server, a personal computer (Personal Computer, PC, refer to a multipurpose computer with a size, price and performance suitable for personal use, a desktop computer, a notebook computer, a small notebook computer, a tablet computer, an ultrabook, etc. all belong to a personal computer), a smart phone, a personal digital assistant (Personal Digital Assistant, PDA), or an electronic device such as a wearable device. As shown in fig. 1, the system service module development coupling assembly method may include, but is not limited to, the following steps S1 to S4.
S1, acquiring a business rule target type, an execution event target type and at least one triggering condition which are defined by a user for a business module to be developed in a business system.
In the step S1, the user may be, but is not limited to being, a business rule making person. The business rule target type, the execution event target type and the at least one triggering condition are specifically set by the user according to the functional requirement of the business module to be developed and are input by a conventional man-machine interaction mode. Specifically, the business rule target type may be, but not limited to, a business transaction rule type, a business wind control rule type, a business operation rule type, or the like, and the execution event target type may be, but not limited to, a circulation event type, a reminding event type, a payment event type, a push event type, or the like.
S2, according to the business rule target type, at least one customized business rule belonging to the business rule target type is searched from all developed business modules, wherein the developed business modules are business modules with a set of customized business rules applicable to specific business scenes, and the customized business rules comprise, but are not limited to, a plurality of customized executable events.
In the step S2, the developed service module may be an existing service module in the service system, or may be an existing service module in another service system. The type attribute of the customized business rule can be manually determined during customization; since the specific form of the business rule is a combination of trigger conditions and executable events, the customized business rule may also include, but is not limited to, a number of customized trigger conditions. Furthermore, the number of customized executable events may be in particular a single customized executable event, or may be in particular at least two customized executable events that may be executed in parallel and/or sequentially. For example, if the all developed business modules correspond to a customized business rule a of a business transaction rule type, a customized business rule B of a business wind control rule type, a customized business rule C of a business operation rule type, a customized business rule D of a business wind control rule type, a customized business rule E of a business operation rule type, and a customized business rule F of a business wind control rule type, and the business rule target type is a business wind control rule type, the at least one customized business rule may include a customized business rule B, a customized business rule D, and a customized business rule F.
S3, according to the execution event target type, at least one customized executable event belonging to the execution event target type is searched from the at least one customized business rule.
In the step S3, the type attribute of the customized executable event may also be manually determined at the time of customization. Furthermore, the at least one customized executable event may belong to the same customized business rule or may belong to different pluralities of customized business rules. For example, the customized business rule B includes a customized executable event B1 of a streaming event type, the customized business rule D includes a customized executable event D1 of a reminder event type and a customized executable event D2 of a payment event type, the customized business rule F includes a customized executable event F1 of a streaming event type, a customized executable event F2 of a push event type and a customized executable event F3, if the execution event target type is a streaming event type, the at least one customized executable event includes a customized executable event B1 and a customized executable event F1, and if the execution event target type is a push event type, the at least one customized executable event includes a customized executable event F2 and a customized executable event F3.
S4, assembling the at least one triggering condition and the at least one customized executable event together through a rule designer to form the customized business rule of the business module to be developed.
In the step S4, the rule designer is an existing software product dedicated to business rule design, which can be used for editing and automatically generating business rules by a user through a visual/graphical man-machine interaction interface. In order to eliminate such deviation, it is preferable that the at least one trigger condition and the at least one customized executable event are assembled together by a rule designer to form a customized business rule of the business module to be developed, considering that the at least one customized executable event screened through the foregoing steps has a deviation from an actual user demand, including but not limited to the following steps S41 to S43.
S41, importing the at least one triggering condition and the at least one customized executable event into a rule designer, and displaying the at least one customized executable event on a man-machine interaction interface of the rule designer.
In the step S41, the user may conveniently check whether the user has deviation from the actual user requirement by displaying the at least one customized executable event, and if so, the user may further perform adjustment through man-machine interaction operation.
S42, responding to man-machine interaction operation generated by the user on the man-machine interaction interface, and performing event rejection processing, event modification processing and/or event ordering processing on the at least one customized executable event to obtain at least one new customized executable event.
In the step S42, the event rejection process refers to rejecting unnecessary executable events from the at least one customized executable event; for example, when the at least one customized executable event includes a customized executable event F2 and a customized executable event F3, if the customized executable event F3 is not needed, the customized executable event F3 may be removed through a man-machine interaction operation. The event modification processing means modifying the executable event in the at least one customized executable event to meet the requirement of a user; for example, when the at least one customized executable event includes a customized executable event B1 and a customized executable event F1, a new customized executable event B11 and a new customized executable event F11 according to the user's requirement can be obtained through modification of man-machine interaction operation. The event ordering processing means determining the sequential execution order of at least two executable events; for example, by man-machine interaction: the new customized executable event B11 is executed first, and then the new customized executable event F11 is executed. All the three processing modes can be realized by adopting conventional man-machine interaction operation.
S43, assembling the at least one triggering condition and the at least one new customized executable event together through the rule designer to form the customized business rule of the business module to be developed.
The system service module development coupling assembling method described in the foregoing steps S1 to S4 provides a new scheme for developing a service module capable of multiplexing customized service rules, namely, after obtaining a service rule target type, an execution event target type and at least one trigger condition defined by a user for a service module to be developed in a service system, at least one customized service rule belonging to the service rule target type is searched from all the developed service modules, then at least one customized executable event belonging to the execution event target type is searched from the at least one customized service rule, and finally the at least one trigger condition and the at least one customized executable event are assembled together by a rule designer to form a customized service rule of the service module to be developed.
Based on the foregoing technical solution of the first aspect, this embodiment further provides a possible design of how to accurately screen the customized executable events, that is, considering that the screening of the customized executable events by only the execution event target type may cause the problem that the number of events of the at least one customized executable event is too large, preferably, when the customized business rule further includes a plurality of customized triggering conditions, at least one customized executable event belonging to the execution event target type is found from the at least one customized business rule according to the execution event target type, including but not limited to the following steps S311 to S313.
S311, aiming at each customized business rule in the at least one customized business rule, if the corresponding rule contains a customized executable event belonging to the execution event target type, determining the corresponding rule as a business rule to be screened.
In the step S311, for example, the customized business rule B includes a customized executable event B1 of a streaming event type, the customized business rule D includes a customized executable event D1 of a reminder event type and a customized executable event D2 of a payment event type, the customized business rule F includes a customized executable event F1 of a streaming event type, a customized executable event F2 of a push event type and a customized executable event F3, and if the execution event target type is a streaming event type, the customized business rule B and the customized business rule F may be determined as business rules to be screened, respectively.
S312, calculating the similarity between all the customized triggering conditions and the at least one triggering condition in the corresponding rules according to each business rule to be screened.
In the step S312, since the triggering condition in the service rule may reflect the applicable service scenario of the service rule to a certain extent, for example, the triggering condition related to rmb or beijing time may reflect that the affiliated service rule may be applicable to a chinese scenario, the triggering condition may be used as a service scenario feature, and the similarity may be utilized to indirectly reflect the similarity between the service scenario of each service rule to be screened and the target service scenario of the service module to be developed, and to accurately screen the customized executable event. Specifically, for a certain business rule to be screened, the similarity between all the customized triggering conditions and the at least one triggering condition in the corresponding rule is calculated, including but not limited to the following steps S3121-S3124.
S3121, according to all customized triggering conditions in the certain business rule to be screened, sequentially splicing the customized triggering conditions in different arrangement modes to obtain M-! A first string, wherein M represents the total number of customized trigger conditions in the certain business rule to be screened, +|! Representing a mathematical factorial symbol.
In the step S3121, for example, if the certain business rule to be screened has customized triggering conditions 1-5, the method can sequentially splice the customized triggering conditions in different arrangement modes to obtain 5-! A first string.
S3122, according to the at least one trigger condition, splicing each trigger condition in turn by different arrangement modes to obtain N-! And a second string, wherein N represents a total number of trigger conditions in the at least one trigger condition.
S3123 calculating the rule of the M-! Each first character string of the first character strings is associated with the first character string in the N-! Edit distance of each of the second character strings.
In the step S3123, the edit distance algorithm is an existing algorithm for calculating the minimum number of editing operations (which permit editing operations including replacing one character with another, inserting one character, and/or deleting one character, etc.) required to switch from one to another between two character strings, so that the smaller the edit distance, the greater the similarity of the two character strings, so that the edit distance can reflect the business scene similarity in a negative correlation.
S3124, taking the calculated reciprocal of the minimum editing distance as the similarity between all the customized triggering conditions in the certain business rule to be screened and the at least one triggering condition.
In the step S3124, the final calculation result of the edit distance is also affected in consideration of different trigger condition arrangement sequences, so the present embodiment preferably reflects the business scene similarity in a negative correlation with the calculated minimum edit distance.
S313, taking the business rule to be screened with the maximum similarity as a business rule to be copied, and taking all customized executable events which belong to the execution event target type in the business rule to be copied as at least one customized executable event which is searched from the at least one customized business rule and belongs to the execution event target type.
In step S313, since the business rule to be copied has the greatest similarity, the business scenario reflecting the business rule to be copied is the most similar to the target business scenario of the business module to be developed, so that all the customized executable events belonging to the target type of the execution event in the rule may be the most suitable for the user requirement, and they can be used as the result of precisely screening the customized executable events, and the purpose of greatly reducing the number of events in the screening result is achieved.
Based on the first possible design, the triggering condition can be used as a service scene characteristic, the similarity between the service scene of the service rule to be screened and the target service scene of the service module to be developed is calculated, and the customized executable events which are most in line with the user requirements are accurately screened by utilizing the similarity, so that the aim of greatly reducing the number of events in the screening result can be fulfilled, and the subsequent manual adjustment difficulty is reduced.
Based on the foregoing technical solution of the first aspect, the present embodiment further provides another possible design two of how to accurately screen the customized executable event, that is, when the customized business rule further includes a plurality of customized triggering conditions, at least one customized executable event belonging to the target type of the execution event is found from the at least one customized business rule according to the target type of the execution event, including but not limited to the following steps S321 to S322.
S321, for each customized business rule in the at least one customized business rule, determining a condition intersection of all customized trigger conditions corresponding to and in the corresponding rule and the at least one trigger condition.
S322, taking the customized business rule with the most condition intersection elements as a business rule to be copied, and taking all customized executable events which belong to the execution event target type in the business rule to be copied as at least one customized executable event which is searched from the at least one customized business rule and belongs to the execution event target type.
Based on the second possible design, the similarity between the service scene of the customized service rule and the target service scene of the service module to be developed can be positively reflected by utilizing the degree of the same triggering condition, and the customized executable events which are most in line with the requirements of the user can be accurately screened by utilizing the similarity, so that the purpose of greatly reducing the number of the events in the screening result can be realized, and the subsequent manual adjustment difficulty is reduced.
The present embodiment further provides another possible design three of how to accurately screen the customized executable event based on the technical solution of the first aspect, that is, according to the target type of the executable event, at least one customized executable event belonging to the target type of the executable event is found from the at least one customized business rule, including but not limited to the following steps S331 to S332.
S331. determining, for each customized business rule in the at least one customized business rule, a total number of events of the customized executable events corresponding and belonging to the execution event target type in the corresponding rule.
S332, taking the customized business rule with the highest total number of events as a business rule to be copied, and taking all customized executable events which belong to the execution event target type in the business rule to be copied as at least one customized executable event which is searched from the at least one customized business rule and belongs to the execution event target type.
Therefore, based on the possible design III, the purpose of greatly reducing the number of events in the screening result can be achieved, and the subsequent manual adjustment difficulty is reduced.
As shown in fig. 2, in a second aspect of the present embodiment, a virtual device for implementing the system service module development coupling assembly method according to the first aspect or any possible design in the first aspect is provided, where the virtual device includes a definition content acquisition module, a service rule search module, an executable event search module, and a service rule assembly module that are sequentially connected in communication;
the definition content acquisition module is used for acquiring a business rule target type, an execution event target type and at least one triggering condition which are defined by a user for a business module to be developed in a business system;
The business rule searching module is used for searching at least one customized business rule belonging to the business rule target type from all developed business modules according to the business rule target type, wherein the developed business modules are business modules with a set of customized business rules applicable to specific business scenes, and the customized business rules comprise a plurality of customized executable events;
the executable event searching module is used for searching at least one customized executable event belonging to the execution event target type from the at least one customized business rule according to the execution event target type;
the business rule assembling module is used for assembling the at least one triggering condition and the at least one customized executable event together through a rule designer to form the customized business rule of the business module to be developed.
The working process, working details and technical effects of the foregoing apparatus provided in the second aspect of the present embodiment may refer to the first aspect or any possible design of the system service module development coupling assembly method in the first aspect, which are not described herein.
As shown in fig. 3, a third aspect of the present embodiment provides a computer device for executing the system service module development coupling assembling method according to the first aspect or any of the possible designs of the first aspect, where the computer device includes a memory, a processor, and a transceiver, which are sequentially communicatively connected, where the memory is configured to store a computer program, the transceiver is configured to send and receive a message, and the processor is configured to read the computer program, and execute the system service module development coupling assembling method according to the first aspect or any of the possible designs of the first aspect. By way of specific example, the Memory may include, but is not limited to, random-Access Memory (RAM), read-Only Memory (ROM), flash Memory (Flash Memory), first-in first-out Memory (First Input First Output, FIFO), and/or first-in last-out Memory (First Input Last Output, FILO), etc.; the processor may be, but is not limited to, a microprocessor of the type STM32F105 family. In addition, the computer device may include, but is not limited to, a power module, a display screen, and other necessary components.
The working process, working details and technical effects of the foregoing computer device provided in the third aspect of the present embodiment may refer to the first aspect or any possible design of the system service module development coupling assembly method in the first aspect, which are not described herein.
A fourth aspect of the present embodiment provides a computer readable storage medium storing instructions containing the system service module development coupling assembly method according to the first aspect or any of the possible designs of the first aspect, i.e. the computer readable storage medium has instructions stored thereon that when executed on a computer perform the system service module development coupling assembly method according to the first aspect or any of the possible designs of the first aspect. The computer readable storage medium refers to a carrier for storing data, and may include, but is not limited to, a floppy disk, an optical disk, a hard disk, a flash Memory, and/or a Memory Stick (Memory Stick), where the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
The working process, working details and technical effects of the foregoing computer readable storage medium provided in the fourth aspect of the present embodiment may refer to the system service module development coupling assembly method as described in the first aspect or any possible design of the first aspect, which is not described herein.
A fifth aspect of the present embodiments provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the system business module development coupling assembly method of the first aspect or any of the possible designs of the first aspect. Wherein the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus.
Finally, it should be noted that: the foregoing description is only of the preferred embodiments of the invention and is not intended to limit the scope of the invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (10)

1. The system service module development coupling assembly method is characterized by comprising the following steps:
acquiring a business rule target type, an execution event target type and at least one triggering condition which are defined by a user for a business module to be developed in a business system;
according to the business rule target type, at least one customized business rule belonging to the business rule target type is searched from all developed business modules, wherein the developed business modules are business modules with a set of customized business rules applicable to specific business scenes, and the customized business rules comprise a plurality of customized executable events;
according to the execution event target type, at least one customized executable event belonging to the execution event target type is searched from the at least one customized business rule;
and assembling the at least one triggering condition and the at least one customized executable event together by a rule designer to form a customized business rule of the business module to be developed.
2. The system business module development coupling assembling method of claim 1, wherein when the customized business rule further comprises a plurality of customized triggering conditions, according to the execution event target type, finding at least one customized executable event belonging to the execution event target type from the at least one customized business rule, comprising:
for each customized business rule in the at least one customized business rule, if the corresponding rule contains customized executable events belonging to the execution event target type, determining the corresponding rule as a business rule to be screened;
aiming at each service rule to be screened, calculating to obtain the similarity between all customized triggering conditions and at least one triggering condition in the corresponding rule;
and taking the business rule to be screened with the maximum similarity as a business rule to be copied, and taking all the customized executable events which belong to the execution event target type in the business rule to be copied as at least one customized executable event which is searched from the at least one customized business rule and belongs to the execution event target type.
3. The system service module development coupling assembling method according to claim 2, wherein for a certain service rule to be screened, calculating the similarity between all the customized trigger conditions corresponding to the service rule and the at least one trigger condition includes:
according to all customized triggering conditions in the certain business rule to be screened, each customized triggering condition is spliced in sequence through different arrangement modes to obtain M-! A first string, wherein M represents the total number of customized trigger conditions in the certain business rule to be screened, +|! Representing a mathematical factorial symbol;
according to the at least one trigger condition, each trigger condition is spliced in sequence through different arrangement modes to obtain N-! A second string, wherein N represents a total number of trigger conditions in the at least one trigger condition;
calculating and obtaining the information of the M-! Each first character string of the first character strings is associated with the first character string in the N-! Edit distance of each second character string in the second character strings;
and taking the calculated reciprocal of the minimum editing distance as the similarity between all the customized triggering conditions in the certain business rule to be screened and the at least one triggering condition.
4. The system business module development coupling assembling method of claim 1, wherein when the customized business rule further comprises a plurality of customized triggering conditions, according to the execution event target type, finding at least one customized executable event belonging to the execution event target type from the at least one customized business rule, comprising:
determining, for each customized business rule in the at least one customized business rule, a conditional intersection of all customized trigger conditions corresponding and in the corresponding rule with the at least one trigger condition;
taking the customized business rule with the most condition intersection elements as a business rule to be copied, and taking all customized executable events which belong to the execution event target type in the business rule to be copied as at least one customized executable event which is searched from the at least one customized business rule and belongs to the execution event target type.
5. The system business module development coupling assembling method of claim 1, wherein finding at least one customized executable event belonging to the execution event target type from the at least one customized business rule according to the execution event target type comprises:
Determining, for each customized business rule in the at least one customized business rule, a total number of events of the customized executable events corresponding to and belonging to the execution event target type in the corresponding rule;
taking the customized business rule with the highest total number of events as a business rule to be copied, and taking all customized executable events which belong to the execution event target type in the business rule to be copied as at least one customized executable event which is searched from the at least one customized business rule and belongs to the execution event target type.
6. The system business module development coupling assembly method of claim 1, wherein assembling the at least one trigger condition and the at least one customized executable event together by a rule designer to form a customized business rule for the business module to be developed comprises:
importing the at least one triggering condition and the at least one customized executable event into a rule designer, and displaying the at least one customized executable event on a man-machine interaction interface of the rule designer;
responding to man-machine interaction operation generated by the user on the man-machine interaction interface, and performing event rejection processing, event modification processing and/or event sorting processing on the at least one customized executable event to obtain at least one new customized executable event;
And assembling the at least one triggering condition and the at least one new customized executable event together by the rule designer to form a customized business rule of the business module to be developed.
7. The system business module development coupling assembling method of claim 1, wherein the business rule target type is a business transaction rule type, a business wind control rule type or a business operation rule type, and the execution event target type is a circulation event type, a reminding event type, a payment event type or a push event type.
8. The system service module development coupling assembly device is characterized by comprising a definition content acquisition module, a service rule searching module, an executable event searching module and a service rule assembling module which are connected in sequence in a communication mode;
the definition content acquisition module is used for acquiring a business rule target type, an execution event target type and at least one triggering condition which are defined by a user for a business module to be developed in a business system;
the business rule searching module is used for searching at least one customized business rule belonging to the business rule target type from all developed business modules according to the business rule target type, wherein the developed business modules are business modules with a set of customized business rules applicable to specific business scenes, and the customized business rules comprise a plurality of customized executable events;
The executable event searching module is used for searching at least one customized executable event belonging to the execution event target type from the at least one customized business rule according to the execution event target type;
the business rule assembling module is used for assembling the at least one triggering condition and the at least one customized executable event together through a rule designer to form the customized business rule of the business module to be developed.
9. A computer device comprising a memory, a processor and a transceiver in communication connection in sequence, wherein the memory is configured to store a computer program, the transceiver is configured to send and receive messages, and the processor is configured to read the computer program and execute the system service module development coupling assembly method according to any one of claims 1 to 7.
10. A computer readable storage medium having instructions stored thereon which, when executed on a computer, perform the system business module development coupling assembly method of any one of claims 1-7.
CN202310266482.4A 2023-03-17 2023-03-17 System service module development coupling assembly method and device and computer equipment Active CN116204177B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310266482.4A CN116204177B (en) 2023-03-17 2023-03-17 System service module development coupling assembly method and device and computer equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310266482.4A CN116204177B (en) 2023-03-17 2023-03-17 System service module development coupling assembly method and device and computer equipment

Publications (2)

Publication Number Publication Date
CN116204177A true CN116204177A (en) 2023-06-02
CN116204177B CN116204177B (en) 2023-10-03

Family

ID=86514717

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310266482.4A Active CN116204177B (en) 2023-03-17 2023-03-17 System service module development coupling assembly method and device and computer equipment

Country Status (1)

Country Link
CN (1) CN116204177B (en)

Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106227881A (en) * 2016-08-04 2016-12-14 腾讯科技(深圳)有限公司 A kind of information processing method and server
US20160364650A1 (en) * 2015-06-10 2016-12-15 Voalte, Inc. Domain Specific Languages and Complex Event Handling for Mobile Health Machine Intelligence Systems
CN110532536A (en) * 2019-08-30 2019-12-03 深圳前海微众银行股份有限公司 A kind of rule configuration method and device
CN110737821A (en) * 2018-07-03 2020-01-31 百度在线网络技术(北京)有限公司 Similar event query method, device, storage medium and terminal equipment
CN111177214A (en) * 2019-12-19 2020-05-19 腾讯云计算(北京)有限责任公司 Event linkage processing method, device and system, electronic equipment and storage medium
CN111461186A (en) * 2020-03-20 2020-07-28 支付宝(杭州)信息技术有限公司 Data similarity processing method and device, storage medium and computer equipment
CN112100250A (en) * 2020-11-23 2020-12-18 支付宝(杭州)信息技术有限公司 Data processing method and device
CN112256261A (en) * 2020-10-30 2021-01-22 贵州电网有限责任公司信息中心 Monitoring script visual configuration method based on power grid collaborative service scene
CN112394922A (en) * 2020-12-02 2021-02-23 成都新希望金融信息有限公司 Decision configuration method, business decision method and decision engine system
US20220101236A1 (en) * 2015-04-07 2022-03-31 Jabil Inc. System and method for modular customization of intermediate business documentation generation
CN114328495A (en) * 2021-12-31 2022-04-12 陕西优百信息技术有限公司 Enterprise material cleaning service system and data cleaning method thereof
CN115291857A (en) * 2022-07-26 2022-11-04 苏州慧工云信息科技有限公司 Visual business rule arranging method and configurator
CN115563160A (en) * 2022-10-10 2023-01-03 神策网络科技(北京)有限公司 Data processing method, data processing device, computer equipment and computer readable storage medium

Patent Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220101236A1 (en) * 2015-04-07 2022-03-31 Jabil Inc. System and method for modular customization of intermediate business documentation generation
US20160364650A1 (en) * 2015-06-10 2016-12-15 Voalte, Inc. Domain Specific Languages and Complex Event Handling for Mobile Health Machine Intelligence Systems
CN106227881A (en) * 2016-08-04 2016-12-14 腾讯科技(深圳)有限公司 A kind of information processing method and server
CN110737821A (en) * 2018-07-03 2020-01-31 百度在线网络技术(北京)有限公司 Similar event query method, device, storage medium and terminal equipment
CN110532536A (en) * 2019-08-30 2019-12-03 深圳前海微众银行股份有限公司 A kind of rule configuration method and device
CN111177214A (en) * 2019-12-19 2020-05-19 腾讯云计算(北京)有限责任公司 Event linkage processing method, device and system, electronic equipment and storage medium
CN111461186A (en) * 2020-03-20 2020-07-28 支付宝(杭州)信息技术有限公司 Data similarity processing method and device, storage medium and computer equipment
CN112256261A (en) * 2020-10-30 2021-01-22 贵州电网有限责任公司信息中心 Monitoring script visual configuration method based on power grid collaborative service scene
CN112100250A (en) * 2020-11-23 2020-12-18 支付宝(杭州)信息技术有限公司 Data processing method and device
CN112394922A (en) * 2020-12-02 2021-02-23 成都新希望金融信息有限公司 Decision configuration method, business decision method and decision engine system
CN114328495A (en) * 2021-12-31 2022-04-12 陕西优百信息技术有限公司 Enterprise material cleaning service system and data cleaning method thereof
CN115291857A (en) * 2022-07-26 2022-11-04 苏州慧工云信息科技有限公司 Visual business rule arranging method and configurator
CN115563160A (en) * 2022-10-10 2023-01-03 神策网络科技(北京)有限公司 Data processing method, data processing device, computer equipment and computer readable storage medium

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
CUICONG7110: "业务规则引擎", Retrieved from the Internet <URL:https://blog.csdn.net/cuicong7110/article/details/100395666> *
听到微笑: "一文详解编辑距离(Levenshtein Distance)", Retrieved from the Internet <URL:https://blog.csdn.net/tianjindong0804/article/details/115803158> *
林逢润: "基于行为关系的业务流程系统变体簇相似性方法研究", 《中国优秀硕士学位论文全文数据库信息科技辑》, no. 02 *
胡欣然: "基于ODM的城市规划业务规则库设计与实现", 《中国优秀硕士学位论文全文数据库信息科技辑》, no. 06 *

Also Published As

Publication number Publication date
CN116204177B (en) 2023-10-03

Similar Documents

Publication Publication Date Title
JP7228662B2 (en) Event extraction method, device, electronic device and storage medium
US8937619B2 (en) Generating an object time series from data objects
CN111428049B (en) Event thematic generation method, device, equipment and storage medium
WO2021190379A1 (en) Method and device for realizing automatic machine learning
CN110750654A (en) Knowledge graph acquisition method, device, equipment and medium
US11853684B2 (en) Synchronization and tagging of image and text data
CN109189931A (en) A kind of screening technique and device of object statement
CN111930366A (en) Rule engine implementation method and system based on JIT real-time compilation
CN114626731A (en) Risk identification method and device, electronic equipment and computer readable storage medium
CN114925143A (en) Method, device, equipment, medium and product for describing logical model blood relationship
US20240037084A1 (en) Method and apparatus for storing data
CN116204177B (en) System service module development coupling assembly method and device and computer equipment
CN113032674A (en) Project publishing method, device, equipment and medium
US12118578B2 (en) Method and apparatus for processing commodity information, device and storage medium
CN115760273A (en) Commodity label generating and displaying method, equipment and computer readable medium
US20150170068A1 (en) Determining analysis recommendations based on data analysis context
CN115544254A (en) Intelligent data processing method, device and equipment based on enterprise-level administrative organization tree
GB2608112A (en) System and method for providing media content
CN117350526B (en) Intelligent sorting method, device, equipment and storage medium for self-service items
CN114780773B (en) Document picture classification method and device, storage medium and electronic equipment
CN118095270B (en) Construction method and device of logic analysis graph, electronic equipment and storage medium
CN110189219B (en) Account checking method and device based on parameter preprocessing
EP4089592A1 (en) Method for determining annotation capability information, related apparatus and computer program product
CN115964550A (en) Method, device, equipment and medium for generating information text
CN115629828A (en) State machine display method, device and medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant