Modeling client and modeling method based on flow relationship

Abstract

The invention provides a modeling client and a modeling method based on a flow relationship, and the modeling client is used for describing a business system of each field based on a modeling language, and comprises a plurality of types and flows; each type is used for describing objects of the same attribute, and the flow is used for being configured between different types of classes and used for decoupling connection relations between the different types of classes so that parallel control can be carried out on processes between the different types of classes. According to the invention, tasks or processes which are originally tightly connected are isolated through streams, for example, producers and consumers are not directly connected any more, but information is transmitted through one stream, so that each part can work independently, the complexity of the whole system is reduced, and the cost is reduced. And the modeling efficiency and the expression capability of the multi-input multi-output relation logic are remarkably improved. And meanwhile, the modeling logic is simplified, so that errors caused by unclear expression are reduced, and the consistency and accuracy of the model logic are ensured.

Description

Technical Field

[0001] The present invention relates to the technical field of modeling, and in particular, to a modeling client and a modeling method based on flow relationships. Background Art

[0002] A modeling method is a method for describing business systems in various fields through a modeling tool, so that people can quickly and intuitively understand the composition of the relevant business system, the relationships between the components, and the business processes, etc.

[0003] In traditional modeling, the modeling tool is serially controlled in terms of relational logic expression. For example, if target A needs to transmit information to targets B and C respectively, then it can only be transmitted to C after being transmitted to B. When modeling, it is necessary to first construct attributes such as the transmission route from A to B and the start and end times of transmission, and then construct the process from A to C. This method has the following problems: on the one hand, the modeling requirements of parallel logic cannot be realized; on the other hand, for the modeling of complex business systems (such as multi-input multi-output systems), if serial logic is used for construction, the construction process will be very complex, not only the constructed view is not concise enough, prone to errors, but also the modeling efficiency is very low. Summary of the Invention

[0004] In view of this, the purpose of the present invention is to provide a modeling client and a modeling method based on flow relationships to simplify the modeling logic and improve the modeling efficiency and accuracy.

[0005] In a first aspect, a modeling client is provided for describing business systems in various fields based on a modeling language, including multiple types of classes and flows; each class is used to describe objects with the same attribute, and the flow is used to be configured between different types of classes to decouple the connection relationships between different types of classes, so as to perform parallel control on the processes between different types of classes; among them, the types of classes at least include producer classes, consumer classes, and collaborative classes.

[0006] Optionally, the flow is configured with flow attributes and a flow process; the flow attributes at least include the following members: flow type, flow speed, buffer size, buffer processing strategy, and consumption strategy; the flow process represents the function or behavior of the flow.

[0007] Optionally, the flow relationships at least include one of the following: consumption flow relationship, generation flow relationship, input influence flow relationship, output influence flow relationship, and two-way influence flow relationship.

[0008] In a second aspect, a modeling method based on flow relationships is provided, which is applied to the modeling client according to any one of the first aspect. The method includes:

[0009] Step S101: Create a flow instance in the design view based on the modeling task of the target business system; the flow instance is the specific implementation of the flow, including flow attributes and a flow process; the flow attributes and the flow process are in a hidden state in the design view; the target business system is a multi-input multi-output system;

[0010] Step S102: Adjust the hidden state of some or all of the flow attributes and the flow process to a visible state according to the modeling requirements;

[0011] Step S103: Add classes of the target business system associated with the flow attributes and the flow process in the visible state to the design view; the types of the classes include at least a producer class, a consumer class, and a collaboration class;

[0012] Step S104: Construct flow relationships between different types of classes and the flow instance respectively, and generate a process of the target business system based on the flow relationships;

[0013] Step S105: Configure a trigger event for triggering the process of the target business system;

[0014] Repeat the above steps S102 - S105 until the modeling is completed.

[0015] Optionally, creating a flow instance in the design view includes:

[0016] Respond to a drag operation on a flow primitive in the primitive display area to obtain a drag route; the flow primitive is a visual representation of the flow;

[0017] Display the flow primitive in the target area of the design view based on the drag route;

[0018] Respond to a configuration operation on the flow type, flow attributes, and flow process of the flow primitive to obtain configuration data;

[0019] Generate a flow instance based on the configuration data.

[0020] Optionally, adjusting the hidden state of some or all of the flow attributes and the flow process to a visible state according to the modeling requirements includes:

[0021] Respond to a click operation on the supplement button of the flow instance to display options for the flow attributes and the flow process;

[0022] Respond to a selection operation on the options for the flow attributes and the flow process to add and display primitives of the selected flow attributes and the flow process, so that the state of the selected flow attributes and the flow process is converted from a hidden state to a visible state.

[0023] Optionally, the producer class consists of a producer instance and a producer process; the consumer class consists of a consumer instance and a consumer process; constructing flow relationships between different types of classes and the flow instance respectively includes:

[0024] Construct the flow relationships between the producer instance, the producer process, and the flow instance respectively;

[0025] And, construct the flow relationships between the consumer instance, the consumer process, and the flow instance respectively.

[0026] Optionally, the method further includes:

[0027] Add a subprocess of the consumer process or the producer process;

[0028] Construct the flow relationship between the subprocess of the consumer process or the producer process and the flow instance.

[0029] Optionally, creating a flow instance in the design view includes:

[0030] Create the flow instances corresponding to different types of classes in the design views of different windows.

[0031] In a third aspect, a computer-readable storage medium is provided, in which a computer program is stored, and when the computer program is executed by a processor, the method steps described in any one of the second aspects are implemented.

[0032] A modeling client and a modeling method based on flow relationships provided by an embodiment of the present invention. The modeling client is used to describe business systems in various fields based on a modeling language, including multiple types of classes and flows. Each type of class is used to describe objects with the same attribute, and the flow is used to configure between different types of classes to decouple the connection relationships between different types of classes, so as to perform parallel control on the processes between different types of classes. The present invention isolates the originally closely connected tasks or processes through the flow. For example, the producer and the consumer are no longer directly connected, but information is transmitted through a flow. In this way, each part can work independently, reducing the complexity of the entire system and significantly improving the modeling efficiency and expression ability of the multi-input multi-output relationship logic. At the same time, due to the simplification of the modeling logic, the errors caused by unclear expression are reduced, ensuring the consistency and accuracy of the model logic.

[0033] To make the above objects, features, and advantages of the present invention more obvious and understandable, the following specific preferred embodiments are given, and in conjunction with the accompanying drawings, the detailed description is as follows. Description of the Drawings

[0034] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required to be used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention, and therefore should not be regarded as limiting the scope. For those of ordinary skill in the art, other related drawings can be obtained based on these drawings without creative efforts.

[0035] Figure 1 The flowchart of the modeling method based on the flow relationship provided by the embodiments of the present invention is shown;

[0036] Figure 2 The schematic diagram of a post office business system provided by the embodiments of the present invention is shown. Detailed implementation manners

[0037] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some of the embodiments of the present invention, rather than all the embodiments. Usually, the components of the embodiments of the present invention described and illustrated herein can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely represents the selected embodiments of the present invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0038] Considering the current modeling methods, on the one hand, the modeling requirements for parallel logic cannot be achieved; on the other hand, for the modeling of complex business systems (such as multi-input multi-output systems), if serial logic is used for construction, the construction process will be very complex. Not only is the constructed view not concise enough, error-prone, but also the modeling efficiency is very low.

[0039] Based on this, the embodiments of the present invention provide a modeling client and a modeling method based on the flow relationship, which will be described below through embodiments.

[0040] The embodiments of the present invention provide a modeling client for describing business systems in various fields based on a modeling language, including multiple types of classes and flows; each class is used to describe objects with the same attribute, and the flow is used to be configured between different types of classes to decouple the connection relationships between different types of classes, so as to perform parallel control on the processes between different types of classes; among them, the types of classes at least include producer classes, consumer classes, and collaboration classes.

[0041] In the embodiments of the present invention, producer classes are responsible for generating or providing certain resources or information. They can be any form of data source such as services, database query results, calculation results, etc.

[0042] Consumer classes are responsible for receiving and processing the resources or information provided by producer classes. Consumer classes may further analyze, transform, or directly apply this information to a specific business logic.

[0043] It should be noted that the same object can be both a producer class and a consumer class.

[0044] In one example, for the distribution and subscription of newspapers and periodicals, the distributor belongs to the producer class, and the subscriber belongs to the consumer class. Another example is the postal system. The sender belongs to the producer class, and the recipient belongs to the consumer class. For example, when Zhang San sends a letter, he belongs to the producer class, and when Zhang San receives a letter, he can be regarded as the consumer class.

[0045] A class is used to describe objects with the same attributes. For example, objects such as tigers, lions, and elephants all belong to the animal class.

[0046] The stream is a new element designed in the present invention. Through the stream, the process control can be decoupled to achieve parallel process control. For example, the relationship between the producer class and the consumer class. Before the stream, the producer class and the consumer class were directly connected, and the process between the producer class and the consumer class was a serial logic.

[0047] Taking the modeling of the postal system as an example, for instance, Zhang San needs to send letters to Li Si and Zhao Wu. According to the logic of the serial process, he can only send a letter to Zhao Wu after sending the letter to Li Si because Zhang San cannot send letters to two people simultaneously. When modeling, it is necessary to first establish the relationship between the object Zhang San and Li Si, and configure the first letter-sending process between the two, set the start time and end time of the letter-sending process, then establish the relationship between Zhang San and Zhao Wu, and configure the second letter-sending process between Zhang San and Zhao Wu, set the start time and end time of the second process. According to the serial logic, the start time of the second letter-sending process needs to be after the end time of the first letter-sending process.

[0048] According to the above example, the existing serial logic requires setting conditions such as the constraint time of the two processes respectively when modeling to meet the modeling logic. This not only has low modeling efficiency but also has a complex design process. However, in this application, by designing a stream, as Figure 2 shown, a schematic model diagram of a post office business system is given. The stream is the post office. Then Zhang San only needs to establish a stream relationship with the post office, and Li Si and Zhao Wu establish a stream relationship with the post office, and he can send letters to Li Si and Zhao Wu simultaneously. Moreover, when modeling, there is no need to consider the logic of time sequence, etc., which simplifies the modeling process, greatly reduces the complexity of the production + consumption model, and improves the modeling efficiency, achieving parallel process control.

[0049] Based on the above embodiments, the stream is configured with stream attributes and a stream process; the stream attributes at least include the following members: stream type, stream speed, buffer size, buffer processing strategy, and consumption strategy; the stream process represents the function or behavior of the stream.

[0050] The flow attributes define the basic characteristics of a flow, which affect how data or resources flow between producer classes and consumer classes. Among them, the flow type indicates the type of data or resources transmitted in the flow. It can be a basic type (boolean, string, enumeration, integer, number, datetime, date, time), a predefined type (array, set, map), or a type defined in the model or component.

[0051] The flow rate represents the speed at which data or resources pass through the flow, usually measured by the amount of data transmitted per unit time (such as bits per second).

[0052] The cache size specifies the maximum amount of data that the flow can temporarily store. The default cache is 1024 instances, that is, a flow can establish flow relationships with 1024 instances simultaneously.

[0053] The cache handling policy describes the actions to be taken when the cache reaches its capacity limit. Common policies include discarding the earliest entries (FIFO), discarding the latest entries (LIFO), priority discarding, etc.

[0054] The consumption policy determines how the consumer class retrieves data from the flow. For example, it can be a pull mode (the consumer actively requests data) or a push mode (the flow actively sends data to the consumer); another example is whether prefetching is allowed, reading one instance at a time or multiple instances at a time, etc.

[0055] The flow process characterizes the function or behavior of the flow. For example, if the flow is a post office, the flow process includes the two processes of receiving letters and sending letters. By configuring the flow process, the function of the flow is clarified, and different business systems have different configured flow processes.

[0056] In the embodiments of the present invention, the flow relationship includes at least one of the following: consumption flow relationship, generation flow relationship, input influence flow relationship, output influence flow relationship, and two-way influence flow relationship.

[0057] Specifically, divided by the direction of data transmission, it is divided into two parts: in and out. The out includes the consumption flow relationship and the output influence flow relationship, and the in includes the generation flow relationship and the input influence flow relationship. The two-way influence flow relationship is two-way, both out and in. The generation flow relationship and the input influence flow relationship are established between the producer class and the flow; the consumption flow relationship and the output influence flow relationship are established between the consumer class and the flow.

[0058] The consumption flow relationship refers to the process by which a consumer class or process reads or consumes data from a certain flow. For example, in a data processing system, the analysis module may extract specific data sets from the data flow for analysis.

[0059] The output influence flow relationship means that the output result of a certain process or module will affect other processes or flows. For example, the output of a calculation module may be the input of another visualization module, thus determining the content finally displayed to the user.

[0060] The generation flow relationship involves adding new data to the flow, which is usually done by the producer class. The producer class is responsible for creating or collecting data and putting it into the flow for subsequent processing or consumption. For example, a sensor can act as a producer class, continuously sending environmental monitoring data to the flow.

[0061] The input influence flow relationship describes how a process changes its own operation behavior by receiving external input data. For example, a rule-based decision engine may adjust its decision path according to the newly received input data.

[0062] The two-way influence flow relationship affects the process through data and is also affected by the process. For example, during the training process of a machine learning model, the prediction result (output) of the model can be used to adjust the model parameters (input) to improve the accuracy of future predictions.

[0063] The graphic elements of each flow relationship are designed as shown in Table 1 below:

[0064]

[0065] The present invention designs a flow and decouples the connection relationships between different types of classes based on this flow, realizing parallel control between different types of classes. It significantly improves the modeling efficiency and expression ability of the multi-input multi-output relationship logic. It supports multi-level logical nesting and multi-purpose result output, meeting the diverse modeling needs of complex scenarios.

[0066] Based on the same inventive concept, a modeling method based on flow relationship is provided, which is applied to the modeling client described in any one of the first aspects, as Figure 1 shown, the method includes the following steps:

[0067] Step S101: Create a flow instance in the design view based on the modeling task of the target business system.

[0068] In the embodiment of the present invention, the flow instance is a specific implementation of the flow, including flow attributes and flow processes.

[0069] By configuring the specific attributes and processes of the flow, it is changed into a flow instance. For example, by configuring the flow type, flow name, attributes, and processes, etc., the flow instance obtained is a post office.

[0070] Among them, in one example, the configuration of the specific attributes of the flow includes the following setting items:

[0071] 1) Single-channel or multi-channel.

[0072] The single-channel description indicates that the created stream instance has only one channel available for interaction between the producer class and the consumer class. The multi-channel description indicates that common stream instances have multiple channels available for interaction between the producer class and the consumer class.

[0073] 2) Whether to strictly control the time order of the data in the stream.

[0074] The data in the stream is the data through which the producer class interacts with the consumer class via the stream instance. Controlling the time order means processing the data in the stream in chronological order.

[0075] 3) The type of data in the stream, which can be a basic type (boolean, string, enumeration, integer, number, datetime, date, time), a predefined type (array, set, map), or a type defined in the model or component.

[0076] It should be noted that if the type of data in the stream is not set, the backend system of the client can also automatically infer the type of data in the stream based on the relationship between the producer class and the consumer class.

[0077] 4) Cache size, with a default of 1024 instances.

[0078] 5) Cache processing policy; when the cache size is reached, discard the previously cached data.

[0079] 6) Consumption policy, whether prefetching is allowed, reading one instance at a time or multiple instances at a time, etc.

[0080] Among them, when the stream is initially added to the design view, the stream attributes and the stream process are in a hidden state in the design view. This can make the interface more concise, and subsequently, the attributes and processes that need to be presented can be displayed according to requirements.

[0081] Among them, the target business system is a multi-input multi-output system, and the model structure of this target business system is mainly a producer-consumer model structure.

[0082] Step S102: Adjust the hidden state of some or all of the stream attributes and the stream process to a visible state according to the modeling requirements.

[0083] The processes and attributes owned by the stream instance are hidden when added to the view. The operation of adjusting the hidden state to a visible state is also referred to as a supplementation operation in this field. Supplementation makes the selected attribute items and process items visible.

[0084] This step can be repeated. As long as there is a need and the required processes and attributes have not been supplemented, then supplementation can be carried out. Unnecessary processes and attributes will not be supplemented, thus avoiding too many primitives in the view and causing confusion.

[0085] Step S103: Add different types of classes of the target business system associated with the flow attributes and flow process in the visible state in the design view.

[0086] Among them, the types of classes include at least producer classes, consumer classes, and collaborative classes.

[0087] In this step, the process of adjusting the state of the flow attributes and flow process from the hidden state to the visible state is called supplementation. For example, if the supplementation process is receiving a letter, then classes related to the sender of the letter can be added; similarly, if the supplementation process is sending a letter, then classes related to the recipient of the letter can be added.

[0088] Among them, the number of added classes is not limited.

[0089] Step S104: Construct the flow relationships between different types of classes and flow instances respectively, and generate the process of the target business system based on the flow relationships.

[0090] In an example, for instance, a production flow relationship is established between the sender and the post office, and a consumption flow relationship is established between the recipient and the post office.

[0091] The processes of the entire business system can be connected in series through the established flow relationships.

[0092] Step S105: Configure the trigger events for the process of the target business system.

[0093] In this step, after constructing the above flow relationships, only the static relationships between producer classes, consumer classes, and flow instances are described, and the entire flow operation can be started through trigger events.

[0094] In an example, the trigger events include instance creation events, instance value change events, and instance destruction events.

[0095] The instances in the above trigger events include producer class instances, consumer class instances, and flow instances. When any instance is created, the creation of the flow will be triggered; when the instance value of any instance changes, for example, Zhang San, the sender, is getting married, then this event will trigger Zhang San to send a letter to his classmate Li Si to notify the other party. When any instance is closed, the flow will be closed.

[0096] Repeat the above steps S102 - S105 until the modeling is completed.

[0097] Because the business system includes a large number of objects and processes, a large number of instances and processes also need to be created during modeling, so the above process needs to be continuously repeated until the modeling is completed.

[0098] After the modeling is completed, scenarios can be set. Scenario setting is a preparatory work for simulation deduction, specifically referring to the setting of the operating conditions or scenarios of the model, that is, setting the initial conditions and end conditions of the simulation deduction based on certain assumptions and preconditions. The created model is deduced and verified through the data configured in the scenario to determine whether it meets the modeling intention.

[0099] From the above embodiments, it can be understood that the present invention decouples the producer class and the consumer class through a flow instance, isolating the originally closely connected tasks or processes through the flow. For example, the producer and the consumer are no longer directly connected, but communicate through a flow to transfer information. In this way, each part can work independently, reducing the complexity of the entire system and significantly improving the modeling efficiency and expression ability of the multi-input multi-output relationship logic. At the same time, due to the simplification of the modeling logic, the errors caused by unclear expression are reduced, ensuring the consistency and accuracy of the model logic.

[0100] Based on the above embodiments, creating a flow instance in the design view includes:

[0101] Step S101A: In response to the dragging operation of the flow primitive in the primitive display area, obtain the dragging route.

[0102] The modeling client consists of a front-end interface and a back-end system. The front-end interface includes a design view area. Flow primitives can be configured on the left side of the design view area. Flow primitives are the visual representation of the flow, and an attribute setting area can be configured on the right side of the design view area.

[0103] In a feasible way, during modeling, select a flow primitive on the left and drag it into the design view area.

[0104] In another feasible implementation, it is also possible to automatically model based on the database information of the target business through the back-end system using an automatic modeling program, and automatically generate a flow instance in the design view area.

[0105] Step S101B: Display the flow primitive in the target area of the design view based on the dragging route.

[0106] Step S101C: In response to the configuration operations on the flow type, flow attributes, and flow process of the flow primitive, obtain the configuration data.

[0107] Configuration is performed in the right area of the design view. The configuration information of the flow attributes refers to the above embodiments and will not be elaborated here.

[0108] Step S101D: Generate a flow instance based on the configuration data.

[0109] The back-end system will obtain the information configured on the right and generate a flow instance with actual business meaning based on this information from the flow primitive.

[0110] Based on the above embodiments, adjusting some or all of the flow attributes and the hidden state of the flow process to a visible state according to the modeling requirements includes:

[0111] Step S102A: In response to a click operation on the supplement button for the flow instance, display the options of the flow attributes and the flow process.

[0112] In a feasible implementation, a supplement button is provided above the design view. Clicking on this supplement button, the client responds to this click operation and will display a drop-down list of the options of the flow attributes and the flow process.

[0113] Step S102B: In response to a selection operation on the options of the flow attributes and the flow process, add and display the graphic elements of the selected flow attributes and the flow process, so that the state of the selected flow attributes and the flow process is converted from a hidden state to a visible state.

[0114] Continuing with the previous example, a check box can be configured in front of each option in the drop-down list, and the required flow attributes and the flow process are presented by clicking on the check box. The presentation method is in the form of graphic elements.

[0115] In the embodiments of the present invention, the producer class consists of a producer instance and a producer process; the consumer class consists of a consumer instance and a consumer process.

[0116] For the above step S104, constructing the flow relationships between different types of classes and flow instances respectively includes:

[0117] Step S104A: Construct the flow relationships between the producer instance, the producer process and the flow instance respectively.

[0118] In the design view, one or more production processes can be added, and the flow relationships between each production process and the flow instance are constructed respectively.

[0119] And, step S104B: Construct the flow relationships between the consumer instance, the consumer process and the flow instance respectively.

[0120] In the design view, one or more consumption processes can be added, and the flow relationships between each consumption process and the flow instance are constructed respectively.

[0121] Based on the above embodiments, the method further includes:

[0122] Step S106: Add a subprocess of the consumer process or the producer process.

[0123] For a complex business system, subprocesses can also be set under the producer process or the consumer process. For example, the letter-sending process can be subdivided into a regular letter-sending subprocess and an urgent letter-sending subprocess.

[0124] Step S107: Construct the flow relationship between the sub-process of the consumer process or the producer process and the flow instance.

[0125] After adding the sub-process, by constructing the relationship between the sub-process and the flow instance, the sub-process can be added to the flow process, and the business system process can be controlled based on the flow process.

[0126] By constructing the flow relationship between the sub-process and the flow instance, the present invention can support multi-level logical nesting and multi-purpose result output, meeting the diverse modeling requirements of complex scenarios.

[0127] The above-mentioned embodiments are all modeled in a single view, that is, all instances and processes are constructed in the same view. However, when the target business system is too complex, modeling in the same view, due to the complex logical relationship, the interface is not concise, and it looks very messy during modeling, reducing the modeling efficiency.

[0128] Therefore, based on the above-mentioned embodiments, creating a flow instance in the design view includes:

[0129] Step S108: Create the flow instances corresponding to different types of classes in the design views of different windows.

[0130] In an example, the producer class and the consumer class can be split into different views. The relationship between the producer class and the flow instance is constructed in one view, and the relationship between the consumer class and the flow instance is constructed in another view. The classes in different views are associated through the same flow instance, simplifying the logic and improving the modeling efficiency.

[0131] In a feasible implementation manner, if the producer class or the consumer class is also complex, it can be split even finer, into a group of production views and a group of consumption views.

[0132] The computer program product for the modeling method based on the flow relationship provided by the embodiments of the present invention includes a computer-readable storage medium storing program code, and the instructions included in the program code can be used to execute the methods described in the foregoing method embodiments. For the specific implementation, reference can be made to the method embodiments, and details will not be repeated here.

[0133] The device for modeling based on the flow relationship provided by the embodiments of the present invention can be specific hardware on the device or software or firmware installed on the device, etc. The implementation principle and the technical effects generated by the device provided by the embodiments of the present invention are the same as those of the foregoing method embodiments. For the sake of brief description, for the parts not mentioned in the device embodiments, reference can be made to the corresponding content in the foregoing method embodiments. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the foregoing-described systems, devices, and units can all refer to the corresponding processes in the above method embodiments, and details will not be repeated here.

[0134] In the embodiments provided by the present invention, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For another example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections between each other can be through some communication interfaces. The indirect couplings or communication connections of the devices or units can be in electrical, mechanical or other forms.

[0135] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0136] In addition, the functional units in the embodiments provided by the present invention can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit.

[0137] If the described functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned storage medium includes: USB flash drives, mobile hard disks, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), magnetic disks or optical disks and other various media that can store program codes.

[0138] It should be noted that: similar reference numerals and letters represent similar items in the following drawings. Therefore, once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. In addition, the terms "first", "second", "third", etc. are only used for distinguishing descriptions and cannot be understood as indicating or implying relative importance.

[0139] Finally, it should be noted that the above-described embodiments are only specific embodiments of the present invention, which are used to illustrate the technical solutions of the present invention rather than to limit them. The protection scope of the present invention is not limited thereto. Although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that any person skilled in the art within the technical scope disclosed by the present invention can still modify the technical solutions recorded in the foregoing embodiments, or can easily think of changes, or perform equivalent replacements on some of the technical features; and these modifications, changes or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention. All should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A modeling client for describing business systems in various fields based on a modeling language, characterized in that, It includes multiple types of classes and a stream; each of the classes is used to describe objects with the same attribute, and the stream is used to configure between different types of classes to decouple the connection relationships between different types of classes, so as to perform parallel control on the processes between different types of classes; among them, the types of the classes at least include producer classes, consumer classes, and collaborative classes.

2. The modeling client according to claim 1, wherein The stream is configured with stream attributes and a stream process; the stream attributes at least include the following members: stream type, stream velocity, cache size, cache processing strategy, and consumption strategy; The stream process characterizes the function or behavior of the stream.

3. The modeling client according to claim 1, characterized in that The stream relationships at least include any one of the following: consumption stream relationship, generation stream relationship, input influence stream relationship, output influence stream relationship, and two-way influence stream relationship.

4. A modeling method based on flow relationships, characterized in that, Applied to the modeling client according to any one of claims 1-3, the method includes: Step S101: Based on the modeling task of the target business system, create a stream instance in the design view; the stream instance is a specific implementation of the stream, including stream attributes and a stream process; the stream attributes and the stream process are in a hidden state in the design view; the target business system is a multi-input multi-output system; Step S102: Adjust the hidden state of some or all of the stream attributes and the stream process to a visible state according to the modeling requirements; Step S103: Add the classes of the target business system associated with the stream attributes and the stream process in the visible state in the design view; the types of the classes at least include producer classes, consumer classes, and collaborative classes; Step S104: Respectively construct the stream relationships between different types of classes and the stream instance, and generate the process of the target business system based on the stream relationships; Step S105: Configure the trigger event for triggering the process of the target business system; Repeat the above steps S102-S105 until the modeling is completed.

5. The method according to claim 4, wherein Creating a stream instance in the design view includes: In response to the drag operation of the stream graphic element in the graphic display area, obtain the drag route; the stream graphic element is a visual representation of the stream; Based on the drag route, display the stream graphic element in the target area of the design view; In response to the configuration operation of the stream type, stream attributes, and stream process of the stream graphic element, obtain the configuration data; Generate a stream instance based on the configuration data.

6. The method according to claim 4, wherein The adjusting the hidden state of some or all of the stream attributes and the stream process to a visible state according to the modeling requirements includes: In response to the click operation on the supplement button of the stream instance, display the options of the stream attributes and the stream process; In response to the selection operation on the options of the stream attributes and the stream process, add and display the graphic elements of the selected stream attributes and the stream process, so that the state of the selected stream attributes and the stream process is converted from the hidden state to the visible state.

7. The method according to claim 4, wherein The producer class consists of a producer instance and a producer process; the consumer class consists of a consumer instance and a consumer process; respectively constructing the stream relationships between different types of classes and the stream instance includes: Respectively construct the stream relationships between the producer instance, the producer process and the stream instance; And respectively construct the stream relationships between the consumer instance, the consumer process and the stream instance.

8. The method according to claim 7, wherein The method further includes: Adding a subprocess of the consumer process or the producer process; Construct the flow relationship between the subprocess of the consumer process or the producer process and the flow instance.

9. The method according to claim 4, wherein Creating a flow instance in the design view includes: Creating flow instances corresponding to different types of classes in the design views of different windows.

10. A computer-readable storage medium, characterized in that, A computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, it implements the method steps described in any one of claims 4-9.

Images