Logical Behavior Modeling Method, Device, Equipment, and Medium Based on Entity Activity Diagram
Through the logical behavior modeling method based on entity activity diagram, the defects of the existing technology in code-free executable modeling, complex concurrent logical expression and entity-behavior relationship description are solved, and efficient and flexible logical behavior modeling is achieved.
Patent Information
- Application Number
- CN202210617020.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-06-01
- Publication Date
- 2025-06-20
- Estimated Expiration
- 2042-06-01
AI Technical Summary
Existing graphical logical behavior modeling methods cannot meet the diverse needs, especially in terms of code-free executable modeling, complex concurrent logical expressions, and graphical descriptions of entity-behavior relationships.
Using a logical behavior modeling method based on entity activity diagrams, we use the establishment of entity activity diagrams, activity template diagrams and activity implementation diagrams, and combining nodes, node labels, connections and layout elements to realize graphical and rapid and agile construction of multi-grained logical behavior models.
It realizes code-free executable modeling, improves the expressive ability of complex concurrent logic, and performs graphical descriptions of the relationship between entities and behaviors, significantly improving the flexibility and efficiency of modeling.
Smart Images

Figure CN115048780B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of system modeling and simulation technologies, and in particular to a logical behavior modeling method, device, equipment, and medium based on an entity activity diagram. Background Art
[0002] Modeling and simulation is a new discipline. Modeling is to abstract data, processes, constraints, etc. in reality into various models, and simulation is the execution of the models.
[0003] Simulation modeling can be broadly classified into entity modeling and behavior modeling. Behavior refers to the impact on internal or external states. Behavior is persistent, has a certain time period, and has three major stages: occurrence, impact, and end. Logical behavior is a type of behavior, mainly depicting the logical relationships between behavior and entities, and between behavior and behavior, including influence relationships, causal relationships, dependency relationships, etc. The logical relationships between entities are not depicted in logical behavior modeling.
[0004] The current graphical logical behavior modeling methods mainly include the following: finite state machine, behavior tree, activity diagram, business process flowchart, and Petri net diagram.
[0005] However, the above methods all have certain problems and cannot meet more diversified requirements;
[0006] 1. Lack of code-free executable modeling ability. The current modeling methods mainly adopt graphical modeling techniques that can automatically generate code frameworks and fill in the code inside the implementation logic. It is a support for low-code modeling. Model diagrams without code implementation do not have the ability to be executed. Therefore, code-free graphical executable modeling has not been achieved.
[0007] 2. Lack of the ability to express complex concurrent logic. The behavior tree is a tree structure, which is a specialized structure of the network structure. The description ability of the tree structure is limited compared to the network structure and can only describe behaviors with a limited action space. Although the finite state machine can perform hierarchical decoupling when describing complex behaviors and use state diagrams at different levels to represent state transitions, there are still problems such as state space explosion and complex and chaotic state transition connection lines. The activity diagram only describes the activity flow relationship and lacks the description of operations on numerical objects. The business process flowchart and the Petri net diagram adopt network structures, and the description ability has been improved, but the types of basic graphical elements in the two modeling methods are relatively simple, lacking logical encapsulation behind them, and the description of complex logic is limited.
[0008] 3. Lack of graphical description of the relationship between entities and behaviors. The fundamental requirement of behavior modeling is to depict the behavior triggering rules and the impact rules of behaviors on entity states. Currently, the mainstream logical behavior modeling methods generally adopt the "blackboard mechanism", and behaviors such as data flow and state change are carried out by reading and writing the blackboard, without graphical explicit representation. For the same behavior in different scenarios or conditions, the operations on values may also be different. Therefore, it is necessary to graphically describe the relationship between entities and behaviors to complete the logical behavior information encapsulated inside the behavior nodes. Summary of the Invention
[0009] Based on this, in view of the above technical problems, it is necessary to provide a logical behavior modeling method based on entity activity diagrams, which can realize the graphical, rapid and agile construction of multi-granularity logical behavior models.
[0010] A logical behavior modeling method based on entity activity diagrams includes:
[0011] According to the modeling task, establish an entity activity diagram of the logical behavior; the basic elements of the entity activity diagram include nodes, node labels, connections, and layout elements; the types of the entity activity diagram include activity template diagrams and activity implementation diagrams;
[0012] According to the basic elements of the entity activity diagram, model the activity template diagram to obtain a first node architecture attribute diagram, a first node label architecture attribute diagram, a first connection architecture attribute diagram, and a first layout element architecture attribute diagram;
[0013] According to the basic elements of the entity activity diagram, model the activity implementation diagram to obtain a second node architecture attribute diagram, a second node label architecture attribute diagram, a second connection architecture attribute diagram, and a second layout element architecture attribute diagram;
[0014] According to the first node architecture attribute diagram, the first node label architecture attribute diagram, the first connection architecture attribute diagram, the first layout element architecture attribute diagram, the second node architecture attribute diagram, the second node label architecture attribute diagram, the second connection architecture attribute diagram, and the second layout element architecture attribute diagram, model the logical behavior of the modeling task.
[0015] In one embodiment, the nodes include: reference nodes, constant nodes, entity nodes, attribute nodes, activity nodes, inactive nodes, and interface nodes.
[0016] In one embodiment, the node labels include: interface labels, name labels, description labels, activity trigger labels, default labels, attribute type labels, data type labels, and scope of action labels.
[0017] In one embodiment, the connections include: reference connections, control connections, data connections, assignment connections, combination connections, and instance connections.
[0018] In one embodiment, the layout elements include: combo boxes, dividers, and comment boxes.
[0019] In one embodiment, the active nodes include: combined activities and atomic activities; the atomic activities include: control activities, judgment activities, variable value activities, delay activities, and synchronization activities.
[0020] In one embodiment, the control connections include: trigger connections, pause connections, stop connections, and continue connections.
[0021] A logical behavior modeling device based on an entity activity diagram, comprising:
[0022] An entity activity diagram establishment module, configured to establish an entity activity diagram of a logical behavior according to a modeling task; the basic elements of the entity activity diagram include nodes, node labels, connections, and layout elements; the types of the entity activity diagram include an activity template diagram and an activity implementation diagram;
[0023] An activity template diagram establishment module, configured to model the activity template diagram according to the basic elements of the entity activity diagram to obtain a first node architecture attribute diagram, a first node label architecture attribute diagram, a first connection architecture attribute diagram, and a first layout element architecture attribute diagram;
[0024] An activity implementation diagram establishment module, configured to model the activity implementation diagram according to the basic elements of the entity activity diagram to obtain a second node architecture attribute diagram, a second node label architecture attribute diagram, a second connection architecture attribute diagram, and a second layout element architecture attribute diagram;
[0025] A modeling module, configured to model the logical behavior of the modeling task according to the first node architecture attribute diagram, the first node label architecture attribute diagram, the first connection architecture attribute diagram, the first layout element architecture attribute diagram, the second node architecture attribute diagram, the second node label architecture attribute diagram, the second connection architecture attribute diagram, and the second layout element architecture attribute diagram.
[0026] A computer device, comprising a memory and a processor, where the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:
[0027] Establish an entity activity diagram of a logical behavior according to a modeling task; the basic elements of the entity activity diagram include nodes, node labels, connections, and layout elements; the types of the entity activity diagram include an activity template diagram and an activity implementation diagram;
[0028] Model the activity template diagram according to the basic elements of the entity activity diagram to obtain a first node architecture attribute diagram, a first node label architecture attribute diagram, a first connection architecture attribute diagram, and a first layout element architecture attribute diagram;
[0029] Model the activity implementation diagram according to the basic elements of the entity activity diagram to obtain a second node architecture attribute diagram, a second node label architecture attribute diagram, a second connection architecture attribute diagram, and a second layout element architecture attribute diagram;
[0030] Model the logical behavior of the modeling task according to the first node architecture attribute diagram, the first node label architecture attribute diagram, the first connection architecture attribute diagram, the first layout element architecture attribute diagram, the second node architecture attribute diagram, the second node label architecture attribute diagram, the second connection architecture attribute diagram, and the second layout element architecture attribute diagram.
[0031] A computer-readable storage medium having a computer program stored thereon, the computer program, when executed by a processor, implementing the following steps:
[0032] Establish an entity activity diagram of the logical behavior according to the modeling task; the basic elements of the entity activity diagram include nodes, node labels, connections, and layout elements; the types of the entity activity diagram include an activity template diagram and an activity implementation diagram;
[0033] Model the activity template diagram according to the basic elements of the entity activity diagram to obtain a first node architecture attribute diagram, a first node label architecture attribute diagram, a first connection architecture attribute diagram, and a first layout element architecture attribute diagram;
[0034] Model the activity implementation diagram according to the basic elements of the entity activity diagram to obtain a second node architecture attribute diagram, a second node label architecture attribute diagram, a second connection architecture attribute diagram, and a second layout element architecture attribute diagram;
[0035] Model the logical behavior of the modeling task according to the first node architecture attribute diagram, the first node label architecture attribute diagram, the first connection architecture attribute diagram, the first layout element architecture attribute diagram, the second node architecture attribute diagram, the second node label architecture attribute diagram, the second connection architecture attribute diagram, and the second layout element architecture attribute diagram.
[0036] The above-mentioned logical behavior modeling method, device, equipment, and medium based on the entity activity diagram perform logical behavior modeling in a user-friendly and graphical way, integrating entities, entity attributes, and activities into one view, defining the basic elements of the entity activity view and their meanings, and highlighting the dynamic relationships between activities, between entities and activities. Through different combinations of elements, flexible and convenient parallel activity modeling can be achieved, and concurrent behaviors can be more effectively displayed and edited. At the same time, while controlling complexity, relevant information is shown as much as possible. There is a significant improvement in the flexibility and efficiency of graphical modeling of logical behaviors compared to previous methods. The entity activity diagram established using this method can build an executable modeling framework, with all the information and capabilities required for executable modeling, providing a basis for code-free executable modeling, that is, supporting executable modeling. The logical behavior model established on this basis can contain all execution information, so after steps such as executable conversion (which can be implemented using existing technologies), code-free executable modeling can be achieved. This modeling method is a domain-independent modeling technology, and this technology and system can be widely applied in fields such as system simulation and system simulation, bringing social and economic value. BRIEF DESCRIPTION OF THE DRAWINGS
[0037] Figure 1 is a schematic flowchart of a logical behavior modeling method based on an entity activity diagram in an embodiment;
[0038] Figure 2 is a schematic diagram of architecture attributes in an embodiment;
[0039] Figure 3 is a schematic diagram of node architecture attributes in an embodiment;
[0040] Figure 4 is a schematic diagram of node label architecture attributes in an embodiment;
[0041] Figure 5 is a schematic diagram of connection architecture attributes in an embodiment;
[0042] Figure 6 is a schematic diagram of layout element architecture attributes in an embodiment;
[0043] Figure 7 is a schematic diagram of the style convention of basic elements in an embodiment;
[0044] Figure 8 is a schematic diagram of the overall architecture of an entity activity view in an embodiment;
[0045] Figure 9 is a schematic diagram of a resource usage activity template in an embodiment;
[0046] Figure 10Schematic diagram of reference to attributes of a set of available resources in an embodiment;
[0047] Figure 11 Schematic diagram of reference to activities that consume available resources in an embodiment;
[0048] Figure 12 Schematic diagram of reference to activities that replenish available resources in an embodiment;
[0049] Figure 13 Schematic diagram of reference to activities for judging resource availability in an embodiment;
[0050] Figure 14 Schematic diagram of the main activity based on the resource usage activity template in an embodiment;
[0051] Figure 15 Structural block diagram of a logical behavior modeling device based on an entity activity diagram in an embodiment;
[0052] Figure 16 Internal structure diagram of a computer device in an embodiment. Detailed implementation manners
[0053] In order to make the objectives, technical solutions and advantages of the present application clearer and more understandable, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.
[0054] As Figure 1 shown, a logical behavior modeling method based on an entity activity diagram provided by the present application, in one embodiment, includes the following steps:
[0055] Step 102: According to the modeling task, establish an entity activity diagram of the logical behavior; the basic elements of the entity activity diagram include nodes, node labels, connections, and layout elements; the types of entity activity diagrams include activity template diagrams and activity implementation diagrams.
[0056] Step 104: According to the basic elements of the entity activity diagram, model the activity template diagram to obtain a first node architecture attribute diagram, a first node label architecture attribute diagram, a first connection architecture attribute diagram, and a first layout element architecture attribute diagram.
[0057] Step 106: According to the basic elements of the entity activity diagram, model the activity implementation diagram to obtain a second node architecture attribute diagram, a second node label architecture attribute diagram, a second connection architecture attribute diagram, and a second layout element architecture attribute diagram.
[0058] Step 108: Model the logical behavior of the modeling task according to the first node architecture attribute diagram, the first node label architecture attribute diagram, the first connection architecture attribute diagram, the first layout element architecture attribute diagram, the second node architecture attribute diagram, the second node label architecture attribute diagram, the second connection architecture attribute diagram, and the second layout element architecture attribute diagram.
[0059] This method uses architecture attribute diagrams to describe the basic elements of the entity activity diagram. The basic elements are of four types, namely nodes, node labels, connections, and layout elements, and their architecture attributes are as Figure 2 shown.
[0060] The explanations of the basic elements are as follows:
[0061] Node: The most basic element that makes up the entity activity diagram, which can represent the types or instances of entities, activities, and attributes, and has multiple node types.
[0062] Node label: A systematic and discrete description of a node. A node can be attached with multiple labels. Among them, the data type label does not support set operations and Map mapping object operations for the time being, which simplifies the data type description.
[0063] Connection: Describes the relationship between nodes and has multiple connection types.
[0064] Layout element: An auxiliary element introduced to improve the human-computer interaction.
[0065] As Figures 3 to 6 shown is a detailed description diagram of the architecture attributes of each element.
[0066] As Figure 7 shown is an explanatory diagram of the style convention of the basic elements.
[0067] Table 1 Types of Connections
[0068] Connection type Connection description Trigger connection When the predecessor node is activated or completed, trigger the successor node to execute Pause connection When the predecessor node is completed, trigger the successor composite activity node to pause the activity Continue connection When the predecessor node is completed, trigger the successor composite activity node to continue the activity Stop connection When the predecessor node is completed, trigger the successor composite activity node to stop the activity Reference connection The end node is the reference relationship of the start node, and the end node is the start node Composite connection The end node is a part of the start node, and they are in a composite relationship with each other Data connection The connection for outputting the activity result, and output the activity result data to the end node Assignment connection Activate the constant node and change the property node of the constant node to this value Instance connection The constant node and the parent property node are in an instance relationship
[0069] For the convenience of connection identification, the connection type in the entity activity diagram is determined by the type of the starting node of the connection. To avoid ambiguity, the mapping relationship between nodes and connections is clearly shown in Table 2.
[0070] Table 2 Mapping Relationship between Nodes and Connections
[0071]
[0072] Based on the basic elements, an activity template diagram and an activity implementation diagram are established;
[0073] Activity template diagram: The activity template diagram is a type of entity activity diagram. The main objects it describes are the types of node elements, such as airplanes, vehicles, etc. The activity template diagram has interface nodes in modeling. Due to having interfaces, it can be combined with other models during the modeling process, thus realizing template reuse.
[0074] Activity implementation diagram: The activity implementation diagram is a type of entity activity diagram. The main objects it describes are the instances of node elements, that is, specific types, such as airplane 1, airplane 2, etc. The activity implementation diagram does not have external interface nodes. It can use the activity template diagram for combined model reuse and pass in specific model instances to realize entity activity diagram modeling.
[0075] The above-mentioned logical behavior modeling method, device, equipment and medium based on entity activity diagrams perform logical behavior modeling in a user-friendly and graphical way. It integrates entities, entity attributes and activities into one view, defines the basic elements of the entity activity view and their meanings, and focuses on depicting the dynamic relationships between activities, and between entities and activities. Through different combinations of elements, it can achieve flexible and convenient parallel activity modeling, and can more effectively display and edit concurrent behaviors. At the same time, while controlling complexity, it shows associated information as much as possible. There is a significant improvement in the flexibility and efficiency of logical behavior modeling compared to previous methods. The established logical behavior model can contain all execution information, thus realizing model-free executable modeling. This modeling method is a domain-independent modeling technology, and this technology and system can be widely applied in fields such as system simulation and system simulation, bringing social and economic value.
[0076] It should be understood that although Figure 1 the steps in the flowchart of Figure 1 are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear indication in this article, the execution of these steps does not have a strict order limit, and these steps can be executed in other orders. Moreover,
[0077] In one embodiment, the nodes include: reference nodes, constant nodes, entity nodes, attribute nodes, activity nodes, inactive nodes and interface nodes.
[0078] In one embodiment, the node labels include: interface label, name label, description label, activity trigger label, default label, attribute type label, data type label, and scope label.
[0079] In one embodiment, the connections include: reference connection, control connection, data connection, assignment connection, combination connection, and instance connection.
[0080] In one embodiment, the layout elements include: combo box, divider line, and comment box.
[0081] In one embodiment, the activity nodes include: combined activity and atomic activity; the atomic activities include: control activity, judgment activity, value-changing activity, delay activity, and synchronization activity.
[0082] In one embodiment, the control connections include: trigger connection, pause connection, stop connection, and continue connection.
[0083] In a specific embodiment, the method process of entity activity diagram modeling is shown.
[0084] Taking the activities of vehicle assembly in a vehicle final assembly plant as the background for logical behavior modeling, the entities involved are vehicles, support personnel for vehicle assembly activities, support organizations, support sites, and support equipment, etc., and an assembly activity diagram is established. To illustrate the specific method, the vehicle assembly activity is simplified into two sub-activities: frame assembly and engine assembly, and the types of required support resources are also simplified.
[0085] As Figure 8 shown, the overall architecture of the established entity activity view, and the entity activity diagram includes: activity template diagram and activity implementation diagram.
[0086] The activity template diagram mainly refers to the resource usage activity template diagram, specifically as Figure 9 shown.
[0087] In the activity implementation diagram, taking the activity implementation diagram of frame assembly as an example for modeling explanation. There are four sub-diagrams inside the frame assembly activity diagram, namely: available resource set attribute reference diagram, consume available resource activity reference diagram, replenish available resource activity reference diagram, and resource availability judgment activity reference diagram, specifically as Figures 10 to 13 shown. The main activity diagram based on the resource usage activity template is as Figure 14 shown.
[0088] As Figure 15 shown, in one embodiment, a logical behavior modeling device based on an entity activity diagram is provided, including: entity activity diagram establishment module 1502, activity template diagram establishment module 1504, activity implementation diagram establishment module 1506, and modeling module 1508, where:
[0089] The entity activity diagram creation module 1502 is used to create an entity activity diagram of logical behavior according to a modeling task; the basic elements of the entity activity diagram include nodes, node labels, connections, and layout elements; the types of the entity activity diagram include an activity template diagram and an activity implementation diagram;
[0090] The activity template diagram creation module 1504 is used to model the activity template diagram according to the basic elements of the entity activity diagram, and obtain a first node architecture attribute diagram, a first node label architecture attribute diagram, a first connection architecture attribute diagram, and a first layout element architecture attribute diagram;
[0091] The activity implementation diagram creation module 1506 is used to model the activity implementation diagram according to the basic elements of the entity activity diagram, and obtain a second node architecture attribute diagram, a second node label architecture attribute diagram, a second connection architecture attribute diagram, and a second layout element architecture attribute diagram;
[0092] The modeling module 1508 is used to model the logical behavior of the modeling task according to the first node architecture attribute diagram, the first node label architecture attribute diagram, the first connection architecture attribute diagram, the first layout element architecture attribute diagram, the second node architecture attribute diagram, the second node label architecture attribute diagram, the second connection architecture attribute diagram, and the second layout element architecture attribute diagram.
[0093] In one embodiment, the entity activity diagram creation module 1502 is further used for the nodes to include: reference nodes, constant nodes, entity nodes, attribute nodes, activity nodes, inactive nodes, and interface nodes.
[0094] In one embodiment, the entity activity diagram creation module 1502 is further used for the node labels to include: interface labels, name labels, description labels, activity trigger labels, default labels, attribute type labels, data type labels, and scope of action labels.
[0095] In one embodiment, the entity activity diagram creation module 1502 is further used for the connections to include: reference connections, control connections, data connections, assignment connections, combination connections, and instance connections.
[0096] In one embodiment, the entity activity diagram creation module 1502 is further used for the layout elements to include: combo boxes, dividers, and comment boxes.
[0097] In one embodiment, the entity activity diagram creation module 1502 is further used for the activity nodes to include: combined activities and atomic activities; the atomic activities include: control activities, judgment activities, value-changing activities, delay activities, and synchronization activities.
[0098] In one embodiment, the entity activity diagram building module 1502 is further configured such that the control connection lines include: trigger connection lines, pause connection lines, stop connection lines, and resume connection lines.
[0099] For the specific limitations on the logical behavior modeling device based on the entity activity diagram, reference can be made to the limitations on the logical behavior modeling method based on the entity activity diagram in the foregoing text, which will not be elaborated herein. Each module in the above-mentioned logical behavior modeling device based on the entity activity diagram can be implemented in whole or in part by software, hardware, and their combination. The above-mentioned modules can be embedded in the processor in the computer device in hardware form or be independent of it, or be stored in the memory in the computer device in software form, so that the processor can call and execute the operations corresponding to each of the above modules.
[0100] In one embodiment, a computer device is provided. The computer device can be a terminal, and its internal structural diagram can be as Figure 16 shown. The computer device includes a processor, a memory, a network interface, a display screen, and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, it implements a logical behavior modeling method based on the entity activity diagram. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen. The input device of the computer device can be a touch layer covering the display screen, or a button, a trackball, or a touchpad provided on the housing of the computer device, or an external keyboard, touchpad, or mouse, etc. The computer device can be an emulation device. The input device inputs relevant information to the emulation device, and the processor executes the program in the memory for combined emulation, and the display screen displays the relevant emulation results.
[0101] Those skilled in the art can understand that Figure 16 the structure shown in
[0102] is only a block diagram of a part of the structure related to the solution of this application, and does not constitute a limitation on the computer device to which the solution of this application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different component layout.
[0103] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method in the above embodiment are implemented.
[0104] Those of ordinary skill in the art can understand that all or part of the processes in the above embodiment methods can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, storage, database, or other medium used in the various embodiments provided in this application can include non-volatile and / or volatile memories. Non-volatile memories can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memories can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and Rambus dynamic RAM (RDRAM), etc.
[0105] The technical features of the above embodiments can be combined arbitrarily. For the sake of concise description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope described in this specification.
[0106] The above-described embodiments merely represent several implementation manners of this application. Their descriptions are relatively specific and detailed, but they should not be construed as limiting the scope of the invention patent. It should be noted that for those of ordinary skill in the art, without departing from the concept of this application, several modifications and improvements can still be made, and these all belong to the protection scope of this application. Therefore, the protection scope of the patent of this application should be subject to the appended claims.
Claims
1. A method for logical behavior modeling based on an entity activity diagram, characterized in that, including: According to the modeling task, an entity activity diagram of logical behavior is established; the basic elements of the entity activity diagram include nodes, node labels, connections, and layout elements; Nodes can represent types or instances of entities, activities, and attributes; node labels are systematic and discrete descriptions of nodes; connections describe the relationships between nodes; Layout elements are auxiliary elements introduced to facilitate improving human-computer interaction; the types of the entity activity diagram include activity template diagrams and activity implementation diagrams; the activity template diagram is a type of entity activity diagram, and the description object is the type of node elements; The activity template diagram has interface nodes in modeling, and can be combined with other models during the modeling process to achieve template reuse; the activity implementation diagram is a type of entity activity diagram, and the description object is the specific type of node elements; the activity implementation diagram has no external interface nodes, can use the activity template diagram for combined model reuse, and pass in specific model instances to achieve entity activity diagram modeling; According to the basic elements of the entity activity diagram, model the activity template diagram to obtain a first node architecture attribute diagram, a first node label architecture attribute diagram, a first connection architecture attribute diagram, and a first layout element architecture attribute diagram; According to the basic elements of the entity activity diagram, model the activity implementation diagram to obtain a second node architecture attribute diagram, a second node label architecture attribute diagram, a second connection architecture attribute diagram, and a second layout element architecture attribute diagram; According to the first node architecture attribute diagram, the first node label architecture attribute diagram, the first connection architecture attribute diagram, the first layout element architecture attribute diagram, the second node architecture attribute diagram, the second node label architecture attribute diagram, the second connection architecture attribute diagram, and the second layout element architecture attribute diagram, model the logical behavior of the modeling task.
2. The method according to claim 1, characterized in that, The nodes include: reference nodes, constant nodes, entity nodes, attribute nodes, activity nodes, inactive nodes, and interface nodes.
3. The method according to claim 2, characterized in that, The node labels include: interface labels, name labels, description labels, activity trigger labels, default labels, attribute type labels, data type labels, and scope of action labels.
4. The method according to claim 3, characterized in that, The connections include: reference connections, control connections, data connections, assignment connections, combination connections, and instance connections.
5. The method according to claim 4, characterized in that, The layout elements include: combo boxes, dividers, and comment boxes.
6. The method according to any one of claims 2 to 5, characterized in that, The activity nodes include: combined activities and atomic activities; The atomic activities include: control activities, judgment activities, value-changing activities, delay activities, and synchronization activities.
7. The method according to claim 4 or 5, characterized in that, The control connections include: trigger connections, pause connections, stop connections, and continue connections.
8. A logical behavior modeling device based on an entity activity diagram, characterized in that, including: An entity activity diagram establishment module, configured to establish an entity activity diagram of logical behavior according to the modeling task; the basic elements of the entity activity diagram include nodes, node labels, connections, and layout elements; nodes can represent types or instances of entities, activities, and attributes; node labels are systematic and discrete descriptions of nodes; connections describe the relationships between nodes; Layout elements are auxiliary elements introduced to facilitate improving human-computer interaction; the types of the entity activity diagram include activity template diagrams and activity implementation diagrams; the activity template diagram is a type of entity activity diagram, and the description object is the type of node elements; The activity template diagram has interface nodes in modeling, which can realize combination with other models during the modeling process, so as to achieve template reuse; the activity implementation diagram is a kind of entity activity diagram, and the described object is the specific type of node elements; the activity implementation diagram has no external interface nodes, can use the activity template diagram for combined model reuse, and pass in specific model instances to realize entity activity diagram modeling; An activity template diagram building module, configured to model the activity template diagram according to the basic elements of the entity activity diagram, to obtain a first node architecture attribute diagram, a first node label architecture attribute diagram, a first connection architecture attribute diagram, and a first layout element architecture attribute diagram; An activity implementation diagram building module, configured to model the activity implementation diagram according to the basic elements of the entity activity diagram, to obtain a second node architecture attribute diagram, a second node label architecture attribute diagram, a second connection architecture attribute diagram, and a second layout element architecture attribute diagram; A modeling module, configured to model the logical behavior of the modeling task according to the first node architecture attribute diagram, the first node label architecture attribute diagram, the first connection architecture attribute diagram, the first layout element architecture attribute diagram, the second node architecture attribute diagram, the second node label architecture attribute diagram, the second connection architecture attribute diagram, and the second layout element architecture attribute diagram.
9. A computer device, comprising a memory and a processor, the memory storing a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.
10. A computer-readable storage medium, on which a computer program is stored, characterized in that, When the computer program is executed by the processor, it implements the steps of the method according to any one of claims 1 to 7.
Citation Information
Patent Citations
Entity object relevance based automatic human-computer interface generating method
CN106227527A
Method and system for automatic generation of numerical simulation graphical user interface
CN109144511A