A modeling client and a modeling method based on flow relationship

Abstract

The present application provides a modeling client and a modeling method based on flow relationships. 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 is used to describe objects with the same attributes, and flows are 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 of the processes between different types of classes. The present invention isolates tasks or processes that were originally closely connected through flows. For example, producers and consumers are no longer directly connected, but information is transmitted through a flow, so that each part can work independently, reducing the complexity of the entire system and significantly improving the modeling efficiency and expression ability of multi-input and multi-output relationship logic. At the same time, due to the simplification of the modeling logic, errors caused by unclear expression are reduced, ensuring the consistency and accuracy of the model logic.

Description

Technical Field

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

[0002] The modeling method is a method of describing business systems in various fields through modeling tools, so that people can quickly and intuitively understand the composition of related business systems, the relationship between each component, and business processes.

[0003] In traditional modeling, modeling tools use serial control to express relational logic. For example, if target A needs to transmit information to targets B and C separately, it can only transmit information from A to B first, and then to C. During modeling, it is necessary to first construct the transmission route from A to B, including transmission start and end times, and then construct the process from A to C. This approach has the following problems: First, it cannot meet the needs of modeling parallel logic; second, for modeling complex business systems (such as those with multiple inputs and multiple outputs), if serial logic is used, the construction process will be extremely complex, resulting in a concise and error-prone view and extremely low modeling efficiency. Summary of the Invention

[0004] In view of this, the object of the present invention is to provide a modeling client and a modeling method based on flow relationships to simplify modeling logic and improve 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. The client includes multiple types of classes and flows. Each type describes objects with the same attributes. Flows are configured between different types of classes to decouple connections between different types of classes, enabling parallel control of processes between these different types of classes. Class types include at least producer classes, consumer classes, and collaborative classes.

[0006] Optionally, the flow configuration includes flow attributes and flow processes; the flow attributes include at least the following members: flow type, flow speed, cache size, cache processing strategy and consumption strategy; the flow process characterizes the function or behavior of the flow.

[0007] Optionally, the flow relationship includes at least one of the following: a consumption flow relationship, a generation flow relationship, an input-influence flow relationship, an output-influence flow relationship, and a bidirectional-influence flow relationship.

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

[0009] Step S101: Based on the modeling task of the target business system, a flow instance is created in the design view. The flow instance is the specific implementation of the flow, including flow attributes and flow processes. The flow attributes and flow processes are hidden in the design view. The target business system is a multi-input and multi-output system.

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

[0011] Step S103: Add the target business system class associated with the visible state flow attributes and flow process in the design view; the class type includes at least producer class, consumer class and collaboration class;

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

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

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

[0015] Optionally, create a flow instance in Design view by:

[0016] In response to a drag operation on a flow element in the element display area, a drag route is obtained; the flow element is a visual representation of the flow;

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

[0018] Responding to configuration operations on the flow type, flow attributes, and flow process of the flow primitive, obtaining configuration data;

[0019] Generates a stream instance based on configuration data.

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

[0021] In response to a click operation on a supplement button of a flow instance, options for flow properties and flow process are displayed;

[0022] In response to the selection operation of the flow attribute and flow process options, graphic elements of the selected flow attribute and flow process are added and displayed, so that the state of the selected flow attribute and 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; and the flow relationships between different types of classes and flow instances are constructed as follows:

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

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

[0026] Optionally, the method further comprises:

[0027] Add a sub-process to the consumer process or producer process;

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

[0029] Optionally, create a flow instance in Design view by:

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

[0031] According to a third aspect, a computer-readable storage medium is provided, wherein a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, any method step described in the second aspect is implemented.

[0032] An embodiment of the present invention provides a modeling client and a modeling method based on flow relationships. 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 is used to describe objects with the same attribute. Flows are 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 of the processes between different types of classes. The present invention isolates tasks or processes that were originally closely connected through flows. For example, producers and consumers are no longer directly connected, but instead transmit information 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 capabilities of multi-input and multi-output relationship logic. At the same time, due to the simplification of the modeling logic, errors caused by unclear expressions are reduced, ensuring the consistency and accuracy of the model logic.

[0033] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the embodiments. It should be understood that the following drawings only illustrate certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can be obtained based on these drawings without paying any creative work.

[0035] Figure 1 A flow chart of a modeling method based on flow relations provided by an embodiment of the present invention is shown;

[0036] Figure 2 A schematic diagram of a model of a post office business system provided by an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0037] In order to make the purpose, 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 in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. The components of the embodiments of the present invention generally described and shown in the drawings 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 drawings is not intended to limit the scope of the claimed invention, but merely represents selected embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without making creative work are within the scope of protection of the present invention.

[0038] Considering that the current modeling methods cannot meet the modeling requirements of parallel logic on the one hand; on the other hand, for the modeling of complex business systems (such as systems with multiple inputs and multiple outputs), if serial logic is used, the construction process will be very complicated. Not only will the constructed views be not concise enough and prone to errors, but the modeling efficiency will also be very low.

[0039] Based on this, an embodiment of the present invention provides a modeling client and a modeling method based on flow relationships, which are described below through embodiments.

[0040] An embodiment of the present invention provides a modeling client for describing business systems in various fields based on a modeling language, including multiple types of classes and flows; each type is used to describe objects with the same attributes, and flows are 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 of processes between different types of classes; wherein the class types include at least producer classes, consumer classes, and collaborative classes.

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

[0042] The consumer class is responsible for receiving and processing the resources or information provided by the producer class. The consumer class may further analyze and transform this information or directly apply it 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 newspaper distribution and subscription, the publisher belongs to the producer class, and the subscriber belongs to the consumer class. Another example is the postal system, where the sender belongs to the producer class, and the receiver belongs to the consumer class. For example, when Zhang San sends a letter, he belongs to the producer class, and when he receives the letter, he can be regarded as the consumer class.

[0045] Classes are used to describe objects with the same attributes. For example, tigers, lions, and elephants all belong to the animal class.

[0046] Streams are a new element designed by this invention. They decouple process control and enable parallel process control. For example, before streams were introduced, the producer and consumer classes were directly connected, and the process between them was serial.

[0047] Take the modeling of the postal system as an example. For example, if Zhang San needs to send letters to Li Si and Zhao Wu, according to the logic of the serial process, he can only send the letter to Zhao Wu after sending the letter to Li Si, because Zhang San cannot send letters to two people at the same time. When modeling, you need to first build the relationship between the objects Zhang San and Li Si, and configure the first letter-mailing process between the two, set the start time and end time of the letter-mailing process, then build the relationship between Zhang San and Zhao Wu, and configure the second letter-mailing process between Zhang San and Zhao Wu, and set the start time and end time of the second process. According to the serial logic, the start time of the second letter-mailing process must be after the end time of the first letter-mailing process.

[0048] According to the above example, the existing serial logic needs to set the constraints of the two processes separately when modeling to meet the modeling logic. This is not only inefficient, but also complicated in design process. However, this application designs a flow, such as Figure 2 As shown in the figure, a model diagram of a post office business system is given. The flow is the post office. Then Zhang San only needs to establish a flow relationship with the post office, and Li Si and Zhao Wu only need to establish flow relationships with the post office. Then, letters can be sent to Li Si and Zhao Wu at the same time, and there is no need to consider the logic of time sequence when modeling. This simplifies the modeling process, greatly reduces the complexity of the production + consumption model, improves the modeling efficiency, and realizes parallel process control.

[0049] Based on the above embodiment, the flow configuration includes flow attributes and flow processes; the flow attributes include at least the following members: flow type, flow speed, cache size, cache processing strategy and consumption strategy; the flow process characterizes the function or behavior of the flow.

[0050] Stream properties define the basic characteristics of a stream, which affect how data or resources flow between producer and consumer classes. The stream type specifies the type of data or resource transferred in the stream. This can be a primitive type (Boolean, string, enumeration, integer, number, datetime, date, time), a predefined type (array, collection, map), or a type defined in a model or component.

[0051] Flow rate indicates the speed at which data or resources pass through a flow, and is usually measured in terms of the amount of data transferred per unit time (e.g., bits per second).

[0052] The cache size specifies the maximum amount of data that a flow can temporarily store. The default cache size is 1024 instances, meaning that a flow can establish a flow relationship with 1024 instances at the same time.

[0053] Cache handling policy, which describes the action to take when the cache reaches its capacity limit. Common policies include discarding the oldest entry (FIFO), discarding the latest entry (LIFO), and priority discarding.

[0054] The consumption strategy determines how the consumer class obtains data from the stream. For example, it can be a pull mode (the consumer actively requests data) or a push mode (the stream actively sends data to the consumer). Another example is whether pre-reading is enabled, and whether to read one instance at a time or multiple instances at a time.

[0055] The flow process represents 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 and sending letters. The function of the flow is clarified by configuring the flow process. Different business systems have different configured flow processes.

[0056] In the embodiment of the present invention, the flow relationship includes at least one of the following: a consumption flow relationship, a generation flow relationship, an input-influence flow relationship, an output-influence flow relationship, and a bidirectional-influence flow relationship.

[0057] Specifically, data is divided into two parts based on the direction of data transmission: input and output. Output includes consumption flow relationships and output-influence flow relationships, while input includes generation flow relationships and input-influence flow relationships. Bidirectional influence flow relationships are bidirectional, meaning both outbound and inbound. Producers establish generation flow relationships and input-influence flow relationships with streams, while consumers establish consumption flow relationships and output-influence flow relationships with streams.

[0058] A stream-consuming relationship refers to the process by which a consumer class or process reads or consumes data from a stream. For example, in a data processing system, an analysis module may extract a specific data set from a data stream for analysis.

[0059] An output-influence flow relationship means that the output of a process or module affects other processes or flows. For example, the output of a computational module may be the input of another visualization module, thus determining the content ultimately displayed to the user.

[0060] Producing a stream relationship involves adding new data to the stream, which is typically done by a producer class. A producer class is responsible for creating or collecting data and placing it into a stream for subsequent processing or consumption. For example, a sensor could act as a producer, continuously sending environmental monitoring data to a stream.

[0061] Input influence flow relationships describe how a process can change its operational behavior by receiving external input data. For example, a rule-based decision engine may adjust its decision path based on the new input data it receives.

[0062] A bidirectional influence flow relationship affects the process both through the data and by the process. For example, during the training of a machine learning model, the model's prediction results (output) can be used to adjust the model parameters (input) to improve the accuracy of future predictions.

[0063] The graphic element designs of each flow relationship are shown in Table 1 below:

[0064]

[0065] This invention achieves parallel control of different classes by designing a flow and decoupling the connections between different classes based on this flow. This significantly improves the modeling efficiency and expressiveness of multi-input and multi-output relational logic. It supports multi-level logic 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 any modeling client described in the first aspect, such as Figure 1 As shown, the method includes the following steps:

[0067] Step S101: Based on the modeling task of the target business system, a flow instance is created in the design view.

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

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

[0070] In one example, the specific properties of the configuration flow include the following settings:

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

[0072] Single-channel means that the created stream instance has only one channel that can be used for interaction between the producer class and the consumer class. Multi-channel means that a common stream instance has multiple channels that can be used for interaction between the producer class and the consumer class.

[0073] 2) Whether the time sequence of data in the stream is strictly controlled.

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

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

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

[0077] 4) Cache size, the default is 1024 instances.

[0078] 5) Cache handling strategy: when the cache size is reached, the previously cached data is discarded.

[0079] 6) Consumption strategy, whether pre-reading is possible, reading one instance at a time or reading multiple instances at a time, etc.

[0080] When you first add a flow to the design view, its properties and processes are hidden. This makes the interface more concise, and you can later display the properties and processes you need.

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

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

[0083] The processes and attributes of a flow instance are hidden when they are added to a view. The operation of adjusting the hidden state to the visible state is also called a supplement 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 added yet. Unnecessary processes and attributes will not be added, thus avoiding too many elements in the view and causing confusion.

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

[0086] The class types include at least producer class, consumer class and collaborative class.

[0087] In this step, the process of adjusting the flow attributes and process status from hidden to visible is called supplementation. For example, if the supplemented process is receiving a message, you can add a sender class related to receiving the message; similarly, if the supplemented process is sending a message, you can add a recipient class related to sending the message.

[0088] There is no limit on the number of added classes.

[0089] Step S104: construct 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 one example, 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] By establishing flow relationships, the processes of the entire business system can be connected in series.

[0092] Step S105: configuring a triggering event for triggering the process of the target business system.

[0093] In this step, after constructing the above-mentioned flow relationship, only the static relationship between the producer class, consumer class and flow instance is described, and the entire flow operation can be started by triggering an event.

[0094] In one example, the trigger event includes an instance creation event, an instance value change event, and an instance destruction event.

[0095] The trigger events mentioned above include producer instances, consumer instances, and stream instances. The creation of any of these instances triggers the creation of a stream. When the value of any of these instances changes, for example, if the sender, Zhang San, is getting married, this event triggers a letter to be sent from Zhang San to his classmate, Li Si, to notify them. When any of these instances closes, the stream closes.

[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 need to be created during modeling, so the above process needs to be repeated until the modeling is completed.

[0098] After modeling is complete, scenarios can be set. Scenarios are a preparatory step for simulations. Specifically, scenarios define the model's operating conditions or scenarios. This involves setting the initial and final conditions for the simulation based on certain assumptions and preconditions. Scenario data is used to verify that the model meets the modeling intent.

[0099] From the above examples, we can understand that the present invention decouples the producer class from the consumer class through stream instances, isolating previously closely connected tasks or processes through streams. For example, the producer and consumer are no longer directly connected, but instead transmit information through a stream. This allows each part to work independently, reducing the complexity of the entire system and significantly improving the modeling efficiency and expressiveness of multi-input and multi-output relationship logic. At the same time, by simplifying the modeling logic, errors caused by unclear expression are reduced, ensuring the consistency and accuracy of the model logic.

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

[0101] Step S101A: In response to a drag operation on a stream element in the element display area, a drag route is acquired.

[0102] The modeling client consists of a front-end interface and a back-end system. The front-end interface includes a design view area. On the left side of the design view area, you can configure flow elements. Flow elements are the visual representation of the flow. On the right side of the design view area, you can configure the property setting area.

[0103] In one possible way, when modeling, select a flow element on the left and drag it into the design view area.

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

[0105] Step S101B: Display the flow element in the target area of ​​the design view based on the drag route.

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

[0107] Perform configuration in the right area of ​​the design view. For the configuration information of the flow attributes, refer to the above embodiment and will not be repeated here.

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

[0109] The backend system obtains the information configured on the right and generates flow instances with actual business meaning based on the flow graph elements.

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

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

[0112] In a feasible implementation, a supplement button is provided above the design view. When the supplement button is clicked, the client displays a drop-down list of flow attributes and flow process options in response to the click operation.

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

[0114] Continuing with the previous example, a checkbox can be configured before each option in the drop-down list. Clicking the checkbox will display the required flow attributes and flow process. The presentation method is to present the flow in the form of graphic elements.

[0115] In the embodiment 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] The flow relationships between different types of classes and flow instances are constructed in step S104 as follows:

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

[0118] In the design view, you can add one or more production processes and build the flow relationship between each production process and the flow instance.

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

[0120] In the design view, you can add one or more consumer processes and build a flow relationship between each consumer process and the flow instance.

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

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

[0123] For complex business systems, sub-processes can be set under the producer process or consumer process. For example, the mailing process can be subdivided into a normal mailing sub-process and an expedited mailing sub-process.

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

[0125] After adding a sub-process, by building a relationship between the sub-process and the flow instance, the sub-process can also 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 sub-processes and flow instances, the present invention can support multi-level logical nesting and multi-purpose result output, meeting the diverse modeling needs of complex scenarios.

[0127] The above embodiments all use a single view for modeling, meaning all instances and processes are constructed within the same view. However, when the target business system is complex, modeling within the same view can lead to an unsophisticated interface and a cluttered appearance due to complex logical relationships, reducing modeling efficiency.

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

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

[0130] In one example, the producer and consumer classes can be split into different views. In one view, the relationship between the producer class and the stream instance is established, while in another view, the relationship between the consumer class and the stream instance is established. Classes in different views can be associated through the same stream instance, simplifying logic and improving modeling efficiency.

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

[0132] The computer program product for the flow relationship-based modeling method provided in the embodiment of the present invention includes a computer-readable storage medium storing program code. The instructions included in the program code can be used to execute the method described in the previous method embodiment. The specific implementation can be found in the method embodiment and will not be repeated here.

[0133] The flow relationship-based modeling device provided in the embodiment of the present invention can be specific hardware on the device or software or firmware installed on the device. The implementation principle and technical effects of the device provided in the embodiment of the present invention are the same as those in the aforementioned method embodiment. For the sake of brief description, for matters not mentioned in the device embodiment, reference can be made to the corresponding content in the aforementioned method embodiment. Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can all refer to the corresponding processes in the aforementioned method embodiment, and 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 schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed may be through some communication interface, the indirect coupling or communication connection of the device or unit may be electrical, mechanical or other forms.

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

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

[0137] If the functions are implemented in the form of software functional 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, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling 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 method described in each embodiment of the present invention. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0138] It should be noted that similar numbers and letters represent similar items in the following figures. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. In addition, the terms "first", "second", "third", etc. are only used to distinguish the description and are not to be understood as indicating or implying relative importance.

[0139] Finally, it should be noted that the above-described embodiments are only specific implementations of the present invention, which are used to illustrate the technical solutions of the present invention, rather than to limit them. The scope of protection of the present invention is not limited thereto. Although the present invention has been described in detail with reference to the above-described embodiments, those skilled in the art should understand that any person skilled in the art can modify or easily conceive of changes to the technical solutions described in the above-described embodiments within the technical scope disclosed by the present invention, or replace some of the technical features therein with equivalents. However, such modifications, changes, or replacements do not deviate from the spirit and scope of the technical solutions of the embodiments of the present invention. They should all be included in the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. A modeling client, used to describe business systems in various fields based on a modeling language, characterized by: It includes multiple types of classes and flows; each class is used to describe objects with the same attributes, and the flows are 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 of the processes between different types of classes; wherein the types of classes include at least producer classes, consumer classes and collaborative classes; the flows are configured with flow attributes and flow processes; the flow attributes include at least the following members: flow type, flow speed, cache size, cache processing strategy and consumption strategy; the flow process characterizes the function or behavior of the flow; the flow relationship includes at least one of the following: consumption flow relationship, generation flow relationship, input-affecting flow relationship, output-affecting flow relationship and bidirectional-affecting flow relationship.

2. A modeling method based on flow relations, characterized in that: Applied to the modeling client according to claim 1, the method comprises: Step S101: Based on the modeling task of the target business system, a flow instance is created in the design view; the flow instance is a specific implementation of the flow, including flow attributes and flow processes; the flow attributes and flow processes are hidden 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 flow attributes and flow processes to a visible state according to modeling requirements; Step S103: adding the classes of the target business system associated with the visible flow attributes and flow processes in the design view; the types of the classes include at least producer class, consumer class and collaboration class; Step S104: constructing flow relationships between different types of classes and the flow instances respectively, and generating a process of the target business system based on the flow relationships; Step S105: configuring a triggering event for triggering the process of the target business system; Repeat the above steps S102-S105 until the modeling is completed.

3. The method according to claim 2, characterized in that Creating a flow instance in Design view involves: In response to a drag operation on a flow element in an element display area, obtaining a drag route; the flow element is a visual representation of the flow; Displaying the flow graphic element in a target area of ​​a design view based on the dragging route; Responding to configuration operations on the flow type, flow attributes, and flow process of the flow primitive, obtaining configuration data; A flow instance is generated based on the configuration data.

4. The method according to claim 2, characterized in that Adjusting the hidden state of some or all flow attributes and flow processes to a visible state according to modeling requirements includes: In response to a click operation on a supplement button of the flow instance, options for flow attributes and flow process are displayed; In response to a selection operation on the options of the flow attribute and flow process, graphic elements of the selected flow attribute and flow process are added and displayed, so that the status of the selected flow attribute and flow process is converted from a hidden state to a visible state.

5. The method according to claim 2, characterized in that 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 instances includes: Construct the flow relationship between producer instance, producer process and flow instance respectively; And, construct the flow relationship between consumer instance, consumer process and flow instance respectively.

6. The method according to claim 5, characterized in that The method further comprises: Adding a sub-process of the consumer process or the producer process; A flow relationship between the consumer process or a sub-process of the producer process and a flow instance is constructed.

7. The method according to claim 2, characterized in that Creating a flow instance in Design view involves: Create flow instances corresponding to different types of classes in the design views of different windows.

8. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method steps described in any one of claims 2 to 7 are implemented.

Images