A visual business rule orchestration method and configurator

Abstract

The present disclosure provides a visual business rule orchestration method, a visual business rule configurator, a business processing device, and a business processing method. The visual business rule orchestration method is used to display and set business rule parameters and generate business rules, thereby truly separating business rule settings from system programs. This allows business personnel to independently set business rules, improves the scalability and flexibility of the rule engine, enables system development to flexibly adapt to the continuous changes in business logic, and simplifies the system development and update process.

Description

Technical Field

[0001] The present disclosure relates to the field of data processing technology, and in particular to a visual business rule arrangement method, a configurator, a business processing device, and a business processing method. Background Art

[0002] During the development and implementation of enterprise application systems, business logic frequently changes. To adapt to these changes, rule engines are often incorporated into business requirements. Evolving from inference engines, rule engines are components embedded within applications. They separate business decisions from application code and author them using predefined semantic modules. They accept data input, interpret business rules, and make decisions based on these rules.

[0003] Existing rule engines require specific programming languages, such as DSL, Groovy, or JavaScript, to generate rule files. Implementers must learn a new rule expression language or programming language. This means that rule engines don't truly separate business processes from system programs. Changing business rules still requires business personnel to propose change logic, which then requires system developers to modify configuration files. This complicates system development and updates, and limits the scalability and flexibility of the rule engine. Summary of the Invention

[0004] In view of this, the purpose of the present disclosure is to solve the technical problems of complicated system development and update and poor scalability and flexibility of the rule engine due to the continuous changes in business logic.

[0005] Based on the above objectives, the present disclosure provides a visual business rule arrangement method, comprising the following steps:

[0006] S11, define the business proxy object;

[0007] S21, defining metadata of business rules for the business proxy object;

[0008] S31, a metadata set for visually displaying business rules;

[0009] S41, visually set business rule parameters;

[0010] S51: Generate business rules according to the business rule parameters and save them.

[0011] Optionally, in step S21 , metadata of the business rules are automatically generated according to the defined business proxy object.

[0012] Optionally, a page rendering method is used to visually display the metadata set of the business rule, or to visually set the business rule parameters.

[0013] Optionally, the method further includes step S52, updating the business proxy object.

[0014] Optionally, the method further includes step S53, displaying the saved business rules in an editable manner.

[0015] The present disclosure also provides a visual business rule configurator, comprising: a business proxy object definition module, a business rule metadata definition module, a visual editor, and a business rule generation module;

[0016] The business proxy object definition module is used to define the business proxy object;

[0017] The business rule metadata definition module is used to define metadata of business rules;

[0018] The visual editor is used to display metadata of business rules and visually set business rule parameters;

[0019] The rule generation module is used to generate business rules according to the set business rule parameters.

[0020] Optionally, the visual editor includes a rule rendering module.

[0021] Optionally, the business proxy object definition module updates the business proxy object according to the set business rule parameters.

[0022] The present disclosure also provides a business processing device, comprising: the above-mentioned visual business rule configurator, a matching module, and a rule engine processing module;

[0023] The visual business rule configurator generates a business rule file in a visual manner;

[0024] The business rule library stores the business rule file;

[0025] The matching module is used to match the corresponding rule file from the business rule library according to the received object entity instance;

[0026] The rule engine processing module is used to take the rule file and the above-mentioned object entity instance as parameters to perform business logic processing.

[0027] The present disclosure also provides a business processing method, comprising the following steps:

[0028] S01, construct an object instance of the business proxy object;

[0029] S02, using the above-mentioned visual business rule arrangement method to generate a business rule file;

[0030] S03, matching business rule files;

[0031] S04, calling the rule engine to perform business processing.

[0032] The present disclosure also provides a storage medium storing computer instructions for executing the above-mentioned visualized business rule arrangement method or business processing method.

[0033] The present disclosure also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned visualized business rule arrangement method or business processing method when executing the program.

[0034] As described above, compared with the existing technology, the technical solution provided by the present invention achieves the following beneficial effects: by adopting a visual business rule orchestration method, the business rule setting is truly separated from the system program, so that business personnel can independently set business rules without the assistance of programmers, thereby improving the scalability and flexibility of the rule engine, enabling system development to flexibly adapt to the continuous changes in business logic, and simplifying the system development and update process. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the technical solutions in the present disclosure or related technologies, the following briefly introduces the drawings required for use in the embodiments or related technical descriptions. Obviously, the drawings described below are only embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0036] Figure 1 A schematic diagram of an embodiment of a visual business rule arrangement method disclosed herein;

[0037] Figure 2 A schematic diagram of an embodiment of a business proxy object disclosed herein;

[0038] Figure 3 A schematic diagram of a visual display and editing interface for business rule parameters disclosed herein;

[0039] Figure 4 A schematic diagram of an embodiment of a visual business rule configurator disclosed herein;

[0040] Figure 5 A schematic diagram of another embodiment of a visual business rule configurator disclosed herein;

[0041] Figure 6 A schematic diagram of an embodiment of a service processing device disclosed herein;

[0042] Figure 7 A schematic diagram of an embodiment of the business processing method disclosed herein;

[0043] Figure 8 This is a schematic diagram of another embodiment of the business processing method disclosed herein. DETAILED DESCRIPTION

[0044] In order to make the objectives, technical solutions and advantages of the present disclosure more clearly understood, the present disclosure is further described in detail below in conjunction with specific embodiments and with reference to the accompanying drawings.

[0045] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in the embodiments of the present disclosure should have the usual meanings understood by people with ordinary skills in the field to which the present disclosure belongs. The "first", "second" and similar words used in the embodiments of the present disclosure do not indicate any order, quantity or importance, but are only used to distinguish different components. "Include" or "comprise" and similar words mean that the elements or objects appearing before the word include the elements or objects listed after the word and their equivalents, without excluding other elements or objects. "Connect" or "connected" and similar words are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "Up", "down", "left", "right" and the like are only used to indicate relative position relationships. When the absolute position of the described object changes, the relative position relationship may also change accordingly.

[0046] The inventors discovered that because existing rule engines fail to truly separate business operations from system programs, business personnel are unable to independently build rule models and implement data processing. Furthermore, rule files are closely related to business logic, requiring a new rule file to be created for each new business requirement. The scalability and flexibility of existing rule engines are unable to adapt to the constant changes in business logic. Once the business logic is abstracted into rule files and loaded by back-end programs, business personnel cannot intuitively determine the correctness of rule files or manage them, requiring them to rely on the assistance of programmers, resulting in a complex system development and update process.

[0047] In order to solve the above problems, this paper proposes a visual business rule arrangement method, such as Figure 1 As shown, the following steps are included:

[0048] S11, define the business proxy object; the business proxy object represents one or more real business objects, which internally encapsulates the business condition parameters and execution action functions, but does not include the mapping relationship between conditions and actions, and provides attribute values ​​and method access entries to the outside world; the execution actions in the business proxy object are triggered by the rule engine, and ultimately execute the real business objects contained therein; the business proxy object is driven by the business rule domain, and it contains all the business condition parameters and execution action branches that this business rule domain relies on, and is reused for the rule definition.

[0049] Preferably, the business proxy object is implemented by defining a class, such as Figure 2 As shown, it encapsulates properties and methods, which correspond to business condition properties and execution actions respectively. The business proxy object is preferably pre-defined and stored in the database. When used, business personnel can directly search and select according to their needs.

[0050] S21, define the metadata of the business rules for the business proxy object; the metadata of the business rules is divided into two types. The condition type metadata mainly includes the display name, description, the identifier of the associated proxy object, the field attribute name of the associated proxy object, and the field attribute value type of the associated proxy object; the action type metadata mainly includes the display name, description, the identifier of the associated proxy object, and the method name of the associated proxy object. Preferably, the attributes and methods in the business proxy object are defined in the form of a configuration table. As shown in Tables 1 and 2, this is the metadata definition of the business rules of a certain equipment maintenance work order, Table 1 shows the condition type, and Table 2 shows the action type.

[0051] Table 1

[0052]

[0053] Table 2

[0054]

[0055] Optionally, metadata for the business rules is automatically generated based on the business proxy object in step S11. The encapsulated and defined business proxy object includes the business condition attributes, execution actions, and corresponding attribute value types and annotations of the business proxy object. By setting a configuration table template, data from the defined business proxy object is extracted and automatically populated into the template, thereby automatically generating metadata for the business rules.

[0056] S31, displaying the metadata set of business rules; showing the metadata set of business rules to the user, showing the condition attribute name and execution action name of a business proxy object under a certain rule field in the configuration table to the user, such as Figure 3 shown.

[0057] S41, visually set business rule parameters; Figure 3 As shown, the business rule parameters include: rule attributes, business condition variable set, business condition calculation logic and business execution action name. The rule attributes include the identifier of the associated proxy object, rule priority, rule activation status, and rule effective time. The business condition variable set includes left value selection, comparison operator selection, and right value selection. The left value and right value are the comparison objects on the left and right sides of the comparison operator respectively. The data source of the left value selection is the business rule condition attribute name available for combination selection of the current business proxy object defined in the configuration table; the comparison operator includes: greater than operator, less than operator, less than or equal to operator, greater than or equal to operator, equal operator, unequal operator, etc. Right value selection: constant value, or functional function component with execution function. The business condition calculation logic is the combination relationship between business rules, including: logical AND operation, OR operation, negation operation, etc. The business execution action is a method call of the business proxy object.

[0058] Steps S31 and S41 can be implemented through page rendering, that is, visualizing the document-format file and visualizing different types of rule parameters as various editable objects to facilitate human-computer interaction. For example, parameters that require text input, such as rule description and effective time, are visualized as text boxes to receive user input, comparison operators are visualized as drop-down lists, and activation status is visualized as check boxes, etc., to receive user selections.

[0059] Optionally, business personnel can add, delete, and modify business rule parameters, such as adding or deleting certain business conditions and business condition calculation logic, adding or deleting execution actions, and modifying business condition attributes.

[0060] S51 generates and saves business rules based on the set business rule parameters; generates a conditional expression based on the business condition variable set and the business condition calculation logic, and stores the generated business rules and corresponding business rule identifiers in the rule engine; the conditional expression is composed of logical operations using the attributes of the business proxy object as variables, and the action is a method call of the business proxy object. The generated business rules include rule attributes, rule conditions, and triggering actions; the rule attributes mainly include: the identifier of the associated proxy object, the rule priority, the rule activation status, and the rule effective time; the rule conditions include: the business rule component source data composed of the method identifier of the associated proxy object and the converted conditional expression; the triggering action includes: the method identifier of the associated proxy object.

[0061] Taking the generation of a maintenance work order for the aforementioned equipment as an example, the generated conditional expression can be: Create a maintenance work order when one of the following conditions is met: the activation time reaches 30 days, the number of repairs reaches 1 or more, or the number of maintenances reaches 3 or more.

[0062] Optionally, the business condition variable set entered by the user and the calculation logic between the business conditions are stored in JSON format, which can facilitate page rendering when editing rules.

[0063] Optionally, the business condition variable set, the calculation logic between business conditions, and the execution action name are compiled into a rule file in YAML format that can be recognized by the rule engine.

[0064] Optionally, step S51 may be followed by step S52, in which the business proxy object is updated. Based on the user's operations of adding, deleting, or modifying the business rule metadata, the initially encapsulated and defined business proxy object is automatically updated to facilitate the next business rule arrangement and better adapt to the continuous changes of the business object.

[0065] Optionally, step S51 further includes S53, displaying the saved business rules in an editable manner, and loading the saved business rules into the front-end page to facilitate the user to reselect or edit.

[0066] See also Figure 4 ,The present disclosure also provides a visual business rule configurator, comprising: a business proxy object definition module, a business rule metadata definition module, a visual editor, and a rule generation module;

[0067] The business proxy object definition module is used to define the business proxy object, determine the business proxy object name, at least one business condition attribute, execution action, and annotation description, etc. The business condition attribute includes the business condition attribute name, value type, etc.;

[0068] The business rule metadata definition module is used to define metadata for business rules. Business rule metadata is divided into two types: conditional metadata primarily includes the display name, description, associated proxy object identifier, associated proxy object field attribute names, and associated proxy object field attribute value types; action metadata primarily includes the display name, description, associated proxy object identifier, and associated proxy object method names. Preferably, metadata is defined using a configuration table based on the attributes and methods in the business proxy object, and the configuration table is stored in the business rule library.

[0069] Optionally, the business rule metadata definition module automatically generates metadata for the business rules based on the defined business proxy objects. The business rule metadata definition module is pre-configured with a configuration table template. It extracts elements such as business condition attributes, execution actions, and annotations from the business proxy objects and automatically fills them into the configuration table template to perform metadata definition.

[0070] The visual editor is used to display the metadata of business rules and visually set business rule parameters; the business rule parameters include: rule attributes, business condition variable set, business condition calculation logic, and business execution action name. The rule attributes include the identifier of the associated proxy object, rule priority, rule activation status, and rule effective time. The business condition variable set includes left value selection, comparison operator selection, and right value selection, where the left value and right value are the comparison objects on the left and right sides of the comparison operator, respectively. The data source for the left value selection is the business rule condition attribute name available for combination selection for the current business proxy object defined in the configuration table; comparison operators include: greater than operator, less than operator, less than or equal to operator, greater than or equal to operator, equality operator, inequality operator, etc. The right value selection: a constant value or a functional function component with execution function. The business condition calculation logic is the combination relationship between business rules, including: logical AND operation, OR operation, negation operation, etc. The business execution action is a method call of the business proxy object.

[0071] Optionally, the visual setting of business rule parameters includes adding, deleting, modifying and other operations on business rule parameters, such as adding or deleting several business conditions and business condition calculation logic, adding or deleting execution actions, modifying business condition attributes, etc.

[0072] See also Figure 5 Optionally, the visual editor uses a page rendering module to display and edit the metadata of business rules; the rule rendering module is used to present and edit business rule parameters and actions in a visual manner, so as to facilitate business personnel to set rules interactively. For example, parameters that require text input, such as rule description and effective time, are visualized as text boxes to receive user input, comparison operators are visualized as drop-down lists, and activation status is visualized as check boxes, etc., to receive user selections; the metadata used to define the rules in the configuration table is presented to the user, and the displayed content mainly includes the name and description; the business rule data saved by the user is loaded into the front-end page to facilitate the user to reselect or edit.

[0073] The rule generation module is used to generate business rules based on the set business rule parameters. It first saves the user's selected input as a business rule data object, then converts the source data of the data object into a conditional expression. The conditional expression and execution action are compiled into a rule file recognizable by the rule engine. The generated business rules and corresponding business rule identifiers are stored in the business rule library. The conditional expression is composed of logical operations using the attributes of the business proxy object as variables, and the action is a method call of the business proxy object.

[0074] like Figure 5 As shown, optionally, after the business rule library saves the generated business rules, the business proxy object definition module automatically updates the business proxy object.

[0075] See also Figure 6 , the present disclosure also provides a business processing device, including: a visual business rule configurator, a business rule library, a matching module, and a rule engine processing module;

[0076] The visual business rule configurator generates a business rule file in a visual manner;

[0077] The business rule library stores the generated business rule files;

[0078] The matching module is used to match the corresponding rule file from the business rule library based on the received object entity instance; filter according to the entity instance type of the proxy object, the rule activation status and the rule effective time, and then sort them according to priority to form a matching business rule chain. The rule chain represents the logical combination of messages processed within the rule engine.

[0079] The rule engine processing module is used to directly trigger the rule engine to execute by taking the business rule file and the above-mentioned object entity instance as parameters to perform corresponding business logic processing.

[0080] See also Figure 7 , the present disclosure also provides a business processing method, comprising the following steps:

[0081] P10, construct an object instance of the business proxy object and assign it real business parameter values;

[0082] P20, matching rule files: Matching the corresponding rule files from the rule engine's rule file set. Specifically, filtering is performed based on the entity instance type of the proxy object, the rule activation status, and the rule effective time. Then, the rules are sorted by priority to form a matching business rule chain.

[0083] P30, call the rule engine for business processing; call the rule engine interface, pass in the rule file content and the object instance of the proxy object to trigger the corresponding business logic processing.

[0084] like Figure 8 As shown, optionally, step P11 is further included before step P20 to generate a business rule file in a visual manner; the business rule file is generated by using the visual business rule arrangement method described in the above embodiment, or a visual business rule configurator.

[0085] Optionally, the order of step P10 and step P11 can be interchanged.

[0086] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments and methods, the present disclosure also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and runnable on the processor, wherein when the processor executes the program, it implements the visualized business rule orchestration method or business processing method described in any of the above embodiments.

[0087] The processor can be implemented as a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0088] The memory can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage devices, dynamic storage devices, etc. The memory can store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory and called and executed by the processor.

[0089] It should be noted that although the above device only shows a processor and a memory, in a specific implementation, the device may also include other components necessary for normal operation. In addition, it will be understood by those skilled in the art that the above device may only include the components necessary to implement the embodiments of this specification, and does not necessarily include all the components shown in the figures.

[0090] The electronic device of the above embodiment is used to implement the corresponding visualized business rule arrangement method or business processing method in any of the above embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be described in detail here.

[0091] Based on the same inventive concept, corresponding to any of the above-mentioned embodiment methods, the present disclosure also provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the visual business rule orchestration method or business processing method described in any of the above embodiments.

[0092] The computer-readable media of this embodiment include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.

[0093] The computer instructions stored in the storage medium of the above embodiment are used to enable the computer to execute the visualized business rule arrangement method or business processing method described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0094] Those skilled in the art should understand that the discussion of any of the above embodiments is merely illustrative and is not intended to imply that the scope of the present disclosure (including the claims) is limited to these examples. Within the scope of the present disclosure, the technical features in the above embodiments or different embodiments may be combined, the steps may be implemented in any order, and there are many other variations of the different aspects of the embodiments of the present disclosure as described above, which are not provided in detail for the sake of simplicity.

[0095] In addition, to simplify the description and discussion, and so as not to obscure the embodiments of the present disclosure, known power / ground connections to integrated circuit (IC) chips and other components may or may not be shown in the provided figures. In addition, devices may be shown in the form of block diagrams to avoid obscuring the embodiments of the present disclosure, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform on which the embodiments of the present disclosure are to be implemented (i.e., these details should be fully within the purview of those skilled in the art). Where specific details (e.g., circuits) are set forth to describe exemplary embodiments of the present disclosure, it will be apparent to those skilled in the art that the embodiments of the present disclosure may be implemented without these specific details or with variations in these specific details. Therefore, these descriptions should be considered illustrative rather than restrictive.

[0096] While the disclosure has been described in conjunction with specific embodiments thereof, many alternatives, modifications and variations of these embodiments will be apparent to those skilled in the art in light of the foregoing description.

[0097] The embodiments of the present disclosure are intended to cover all such substitutions, modifications, and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present disclosure should be included in the scope of protection of the present disclosure.

Claims

1. A visual business rule arrangement method, characterized in that: The following steps are involved: S11, define the business proxy object; S21, defining metadata of business rules for the business proxy object; S31, a metadata set for visually displaying business rules; S41, visually set business rule parameters; S51, generating business rules according to the business rule parameters and saving them; Defining the business proxy object includes: encapsulating the business condition parameters and execution action functions within the business proxy object, wherein the business proxy object includes all the business condition parameters and execution action branches that are dependent on the business rule domain; The business proxy object is pre-defined and stored in the database for direct search and selection; The S21 further includes: extracting data from the defined business proxy object by configuring the table template, automatically filling it into the template, and automatically generating metadata for the business rules; The metadata of the business rule includes an identifier of the associated proxy object, a field attribute name of the associated proxy object, a field attribute value type of the associated proxy object, or a method name of the associated proxy object; The business rule parameters include: rule attributes, business condition variable set, business condition calculation logic and business execution action name; The business condition variable set includes left value selection, comparison operator selection, and right value selection; The left value and right value are the comparison objects on the left and right sides of the comparison operator respectively. The data source for the left value selection is the business rule condition attribute name of the current business proxy object defined in the configuration table that can be combined and selected. The right value selects a constant value or a functional function component with execution function.

2. The arrangement method according to claim 1, characterized in that: In step S21, metadata of the business rules are automatically generated according to the defined business proxy object.

3. The arrangement method according to claim 1, characterized in that: The metadata set of the business rule is visually displayed by using page rendering, or the business rule parameters are visually set by using page rendering.

4. The arrangement method according to claim 1, wherein: The method further includes step S52 of updating the business proxy object.

5. The arrangement method according to claim 1, characterized in that: The method further includes step S53 of displaying the saved business rules in an editable manner.

6. A visual business rule configurator, characterized in that: include: Business proxy object definition module, business rule metadata definition module, visual editor, business rule generation module; The business proxy object definition module is used to define the business proxy object; The business rule metadata definition module is used to define the metadata of the business rules for the business proxy object; The visual editor is used to visually display the metadata of the business rules and visually set the business rule parameters; The rule generation module is used to generate business rules according to the set business rule parameters; The business proxy object definition module is further used to: perform proxy encapsulation of business condition parameters and execution action functions within the business proxy object, and the business proxy object includes all business condition parameters and execution action branches that are dependent on the business rule field; The business proxy object is pre-defined and stored in the database for direct search and selection; The business rule metadata definition module is further used to: extract data from the defined business proxy object through the configuration table template, automatically fill it into the template, and automatically generate metadata for the business rules; The metadata of the business rule includes an identifier of the associated proxy object, a field attribute name of the associated proxy object, a field attribute value type of the associated proxy object, or a method name of the associated proxy object; The business rule parameters include: rule attributes, business condition variable set, business condition calculation logic and business execution action name; The business condition variable set includes left value selection, comparison operator selection, and right value selection; The left value and right value are the comparison objects on the left and right sides of the comparison operator respectively. The data source for the left value selection is the business rule condition attribute name of the current business proxy object defined in the configuration table that can be combined and selected. The right value selects a constant value or a functional function component with execution function.

7. A business processing device, characterized in that: include: The visual business rule configurator, business rule library, matching module, and rule engine processing module as described in claim 6; The visual business rule configurator generates a business rule file in a visual manner; The business rule library stores the business rule file; The matching module matches a corresponding rule file from the business rule library according to the received object entity instance; The rule engine processing module takes the rule file and the object entity instance as parameters to perform business logic processing.

8. A business processing method, characterized in that: The following steps are involved: S01, construct an object instance of the business proxy object; S02, generating a business rule file using the visual business rule arrangement method according to any one of claims 1 to 5; S03, matching business rule files; S04, calling the rule engine to perform business processing.

9. A storage medium storing computer instructions for executing the visual business rule arrangement method or business processing method according to any one of claims 1 to 5 and 8.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the method for visualizing business rules or the method for business processing as described in any one of claims 1 to 5 or 8 is implemented.

Images