An executable view system modeling method, device, equipment and medium

Abstract

The present application relates to an executable view modeling method, apparatus, device and medium, the method comprising: establishing a domain requirement-related layer architecture view according to the requirements of the modeling task; the domain requirement-related layer architecture view includes different view systems, and the view system includes modeling boundary information, modeling granularity information and modeling resolution information; establishing a domain-independent layer architecture view according to the modeling boundary information; the domain-independent layer architecture view includes an architecture attribute diagram and an entity activity diagram; splitting the modeling task into different modeling objects according to the modeling granularity information and the modeling resolution information; establishing a domain implementation-related layer architecture view for the modeling object according to the architecture attribute diagram and the entity activity diagram; and performing view modeling according to the domain-related layer architecture view. This method can realize the graphical, rapid and agile construction of lightweight systems and systems based on the three-layer view decoupling method.

Description

Technical Field

[0001] The present application relates to the technical field of system modeling and simulation, and in particular to an executable view system modeling method, apparatus, device and medium. Background Art

[0002] Modeling and simulation is an emerging discipline. Modeling is the abstraction of real-world data, processes, limitations, etc. into various models, while simulation is the execution of the models.

[0003] In terms of simulation modeling languages and standard specifications, there are multiple view architectures for different application fields, such as UML, SysML, OPM and DoDaf.

[0004] However, these methods all have certain problems. They are limited in modeling objects and applicable fields, and cannot meet the increasing demand for lightweight, integrated, and executable modeling:

[0005] 1. The view model lacks the ability to describe in layers. The current mainstream approach primarily organizes and categorizes views by view type or perspective. Views cannot be organized into a view system, and there is a lack of management methods and means between view systems, resulting in a poor view decoupling of modeled objects.

[0006] 2. View models lack integrated modeling capabilities. Current mainstream modeling methods are mostly three-stage executable modeling, namely, conceptual modeling, program implementation modeling, and scenario modeling. This approach is best used for object modeling of complex architectures, but is not suitable for lightweight modeling objects that require rapid iteration.

[0007] 3. Lack of fine-grained model language expression capabilities. Current mainstream modeling languages are relatively top-level, describing relationships as "dependency" or "influence." They lack more atomic graphical languages such as "supplement," "consume," "AND gate," and "OR gate," thus limiting the executable capabilities of model views.

[0008] 4. The view model is too complex, and the modeling cost is too high. Currently, mainstream modeling views include a large number of different diagrams and rules, resulting in an overly complex modeling approach. This leads to a high learning curve, and the resulting modeling views are complex, hindering rapid adoption and agile iteration. Summary of the Invention

[0009] Based on this, it is necessary to provide an executable view system modeling method to address the above technical issues, which can achieve fast and agile graphical construction of lightweight systems based on a three-layer view decoupling method.

[0010] An executable view system modeling method, comprising:

[0011] Establishing a domain requirement-related layer architecture view based on the requirements of the modeling task; the domain requirement-related layer architecture view includes different view systems, and the view system includes modeling boundary information, modeling granularity information, and modeling resolution information;

[0012] Establishing a domain-independent layer architecture view based on the modeling boundary information; the domain-independent layer architecture view includes an architecture attribute diagram and an entity activity diagram;

[0013] The modeling task is divided into different modeling objects according to the modeling granularity information and the modeling resolution information; and domain-implementation-related layer architecture views are established for the modeling objects according to the architecture attribute diagram and the entity activity diagram;

[0014] Perform view modeling based on the domain-related layer architecture view.

[0015] In one embodiment, the domain requirement-related layer is decoupled from the requirement boundary to establish a view system; the domain-independent layer is decoupled from the presentation form to establish a view type; and the domain implementation-related layer is decoupled from the scene object to establish a view object.

[0016] In one embodiment, entity nodes and entity attribute nodes can be transferred between view systems to unify the namespace of objects and perform entity reuse.

[0017] In one embodiment, the architecture attribute diagram includes: an entity architecture attribute diagram and an activity architecture attribute diagram.

[0018] In one embodiment, the architectural property diagram is used to model information declarations.

[0019] In one embodiment, the entity activity diagram includes: an activity template diagram and an activity implementation diagram.

[0020] In one embodiment, the entity activity diagram is used for modeling implementation, wherein the activity template diagram is used to provide activity combinations, and the activity implementation diagram is used to form activity instances.

[0021] An executable view system modeling device, comprising:

[0022] The domain requirement related layer module is used to establish a domain requirement related layer architecture view according to the requirements of the modeling task; the domain requirement related layer architecture view includes different view systems, and the view system contains modeling boundary information, modeling granularity information and modeling resolution information;

[0023] The domain-independent layer module is used to establish a domain-independent layer architecture view based on the modeling boundary information; the domain-independent layer architecture view includes an architecture attribute diagram and an entity activity diagram;

[0024] A domain implementation related layer module is used to split the modeling task into different modeling objects according to the modeling granularity information and the modeling resolution information; and to establish a domain implementation related layer architecture view for the modeling object according to the architecture attribute diagram and the entity activity diagram;

[0025] The modeling module is used to perform view modeling based on the domain-related layer architecture view.

[0026] A computer device includes a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0027] Establishing a domain requirement-related layer architecture view based on the requirements of the modeling task; the domain requirement-related layer architecture view includes different view systems, and the view system includes modeling boundary information, modeling granularity information, and modeling resolution information;

[0028] Establishing a domain-independent layer architecture view based on the modeling boundary information; the domain-independent layer architecture view includes an architecture attribute diagram and an entity activity diagram;

[0029] The modeling task is divided into different modeling objects according to the modeling granularity information and the modeling resolution information; and domain-implementation-related layer architecture views are established for the modeling objects according to the architecture attribute diagram and the entity activity diagram;

[0030] Perform view modeling based on the domain-related layer architecture view.

[0031] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the following steps:

[0032] Establishing a domain requirement-related layer architecture view based on the requirements of the modeling task; the domain requirement-related layer architecture view includes different view systems, and the view system includes modeling boundary information, modeling granularity information, and modeling resolution information;

[0033] Establishing a domain-independent layer architecture view based on the modeling boundary information; the domain-independent layer architecture view includes an architecture attribute diagram and an entity activity diagram;

[0034] The modeling task is divided into different modeling objects according to the modeling granularity information and the modeling resolution information; and domain-implementation-related layer architecture views are established for the modeling objects according to the architecture attribute diagram and the entity activity diagram;

[0035] Perform view modeling based on the domain-related layer architecture view.

[0036] The above-mentioned executable view system modeling method, device, equipment and medium perform executable model system architecture modeling in a humanized and graphical manner, decoupling from three levels: domain requirement related layer, domain independent layer, and domain implementation related layer, minimizing the amount of information and complexity of one-time human-computer interaction, and providing view establishment methods and means for different objects, innovating technical approaches, and improving lightweight modeling efficiency. The architecture view established by this method can build an executable modeling framework, which can include all types and information of execution information required for executable modeling, and classify them according to different levels and view systems, that is, support executable modeling. Therefore, after steps such as executable conversion (which can be implemented using existing technologies), code-free executable, integrated, and fine-grained modeling can be achieved. This modeling method is a domain-independent modeling technology. This technology and system can be widely used in fields such as system simulation and system simulation, and play a social and economic role. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 A flowchart of a view modeling method that can be executed in one embodiment;

[0038] Figure 2 A schematic diagram of a three-layer view architecture in one embodiment;

[0039] Figure 3 This is a general architectural view in one embodiment;

[0040] Figure 4 Schematic diagram of view association relationship in one embodiment;

[0041] Figure 5 A schematic diagram of modeling results of a vehicle assembly system in one embodiment;

[0042] Figure 6 is a structural block diagram of an executable view modeling device in one embodiment;

[0043] Figure 7 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0044] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0045] like Figure 1 As shown, the present application provides an executable view system modeling method, which, in one embodiment, includes the following steps:

[0046] Step 102: Establish a domain requirement related layer architecture view according to the requirements of the modeling task; the domain requirement related layer architecture view includes different view systems, and the view system includes modeling boundary information, modeling granularity information, and modeling resolution information.

[0047] Step 104: Establish a domain-independent layer architecture view based on the modeling boundary information; the domain-independent layer architecture view includes an architecture attribute diagram and an entity activity diagram.

[0048] Step 106: split the modeling task into different modeling objects according to the modeling granularity information and the modeling resolution information; and establish a domain implementation-related layer architecture view for the modeling objects according to the architecture attribute diagram and the entity activity diagram.

[0049] Step 108: Perform view modeling based on the domain-related layer architecture view.

[0050] The architecture of this method is designed based on the idea of "rapid trial and error, rapid iteration", strictly controlling the knowledge volume and complexity of the view. The three-layer view architecture is as follows: Figure 2 shown.

[0051] Domain requirement related layer: Decoupling of modeling object boundaries, modeling granularity, modeling resolution and other levels is performed based on the purpose, requirements and main problems to be solved of modeling.

[0052] Domain-independent layer: constrains the presentation of views, including the types, functions, and usage of view elements, and provides formal human-computer interactivity.

[0053] Domain implementation related layer: According to the modeling resolution and granularity, it is divided into different modeling objects, and object views are established for each object to further split and decouple complexity.

[0054] The overall architecture view based on three-layer decoupling is as follows Figure 3 shown.

[0055] The domain requirement related layer refers to the purpose and scope of modeling, and constrains the objects, granularity, and resolution of modeling abstractions;

[0056] The domain-independent layer is a general method for system modeling, such as view classification and view language, which is a general modeling technology;

[0057] The domain implementation layer performs domain modeling based on the requirements of the above two levels. The result of modeling is the domain model, which is the final output.

[0058] There is a reference relationship between elements between views, which are identified by name to associate content and eventually form a global view. Figure 4 shown.

[0059] Entity nodes and entity attribute nodes can be transferred between view systems, unifying the namespace of objectively existing objects and enabling entity reuse. Within the view system, entity architecture attribute diagrams and activity architecture attribute diagrams declare information such as names and types. Entity activity diagrams are used to associate specific implementations. Activity templates provide reusable activity combinations within a given scenario, while activity implementation diagrams input scenario information to form activity instances.

[0060] The view system is an organic whole composed of a series of different types of views, which can meet certain simulation requirements; among them:

[0061] The architecture attribute diagram is a view that describes the static descriptive information between entities and activities. It constrains the inheritance relationship, attribute fields, attribute field composition relationship, attribute values, and other contents of entities and activities. It is a static view.

[0062] The entity activity diagram is a view that describes the dynamic changes in information between entities and activities. It constrains the interaction between entities and activities and can provide business logic such as information transmission and event triggering. It is a dynamic view.

[0063] The above-mentioned executable view system modeling method, apparatus, equipment, and media model the executable model system architecture in a user-friendly, graphical manner, decoupling the three layers of domain requirement-related, domain-independent, and domain implementation-related. This minimizes the amount of information and complexity of one-time human-computer interaction, provides methods and means for establishing views for different objects, innovates technical approaches, and improves lightweight modeling efficiency. The established entity activity diagram can contain all execution information, thus achieving code-free executable modeling. This modeling method is a domain-independent modeling technology. This technology and system can be widely used in fields such as system simulation and system simulation, and exert social and economic value.

[0064] It should be understood that although Figure 1 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. In addition, Figure 1 At least part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.

[0065] In one embodiment, the domain requirement-related layer is decoupled from the requirement boundary to establish a view system; the domain-independent layer is decoupled from the presentation form to establish a view type; and the domain implementation-related layer is decoupled from the scene object to establish a view object.

[0066] In one embodiment, entity nodes and entity attribute nodes can be transferred between view systems to unify the namespace of objects and perform entity reuse.

[0067] In one embodiment, the architecture attribute graph includes: an entity architecture attribute graph and an activity architecture attribute graph.

[0068] In one embodiment, the architectural property diagram is used to model information declarations.

[0069] In one embodiment, the entity activity diagram includes: an activity template diagram and an activity implementation diagram.

[0070] In one embodiment, the entity activity diagram is used for modeling implementation, wherein the activity template diagram is used to provide activity combinations, and the activity implementation diagram is used to form activity instances.

[0071] In a specific embodiment, the results of executable view architecture modeling are presented.

[0072] This visual architecture modeling exercise is based on the vehicle assembly activities at a final assembly plant. The entities involved are the vehicles, the support personnel, support organizations, support locations, and support equipment involved in the vehicle assembly activity. An assembly activity diagram is created. To illustrate the methodology, the vehicle assembly activity is simplified into two sub-activities: frame assembly and engine assembly. The required support resources are also simplified.

[0073] The results of the executable view architecture modeling of the vehicle assembly system are as follows: Figure 5 shown.

[0074] like Figure 6 As shown, in one embodiment, an executable view system modeling device is provided, including: a domain requirement related layer module 602, a domain independent layer module 604, a domain implementation related layer module 606 and a modeling module 608, wherein:

[0075] The domain requirement related layer module 602 is used to establish a domain requirement related layer architecture view according to the requirements of the modeling task; the domain requirement related layer architecture view includes different view systems, and the view system includes modeling boundary information, modeling granularity information, and modeling resolution information;

[0076] The domain-independent layer module 604 is used to establish a domain-independent layer architecture view based on the modeling boundary information; the domain-independent layer architecture view includes an architecture attribute diagram and an entity activity diagram;

[0077] The domain implementation related layer module 606 is used to split the modeling task into different modeling objects according to the modeling granularity information and the modeling resolution information; and to establish a domain implementation related layer architecture view for the modeling objects according to the architecture attribute diagram and the entity activity diagram;

[0078] The modeling module 608 is used to perform view modeling based on the domain-related layer architecture view.

[0079] In one embodiment, the domain requirement related layer module 602, the domain independent layer module 604 and the domain implementation related layer module 606 are also used to decouple the domain requirement related layer from the requirement boundary and establish a view system; decouple the domain independent layer from the expression form and establish a view type; and decouple the domain implementation related layer from the scene object and establish a view object.

[0080] In one embodiment, the domain requirement related layer module 602 is also used to transfer entity nodes and entity attribute nodes between view systems, unify the namespace of objects, and perform entity reuse.

[0081] In one embodiment, the domain-independent layer module 604 is further used for the architecture attribute diagram to include: an entity architecture attribute diagram and an activity architecture attribute diagram.

[0082] In one embodiment, the domain-independent layer module 604 is further used in the architecture property diagram to model information declaration.

[0083] In one embodiment, the domain-independent layer module 604 is also used for the entity activity diagram to include: an activity template diagram and an activity implementation diagram.

[0084] In one embodiment, the domain-independent layer module 604 is also used for the entity activity diagram to model implementation, wherein the activity template diagram is used to provide activity combinations, and the activity implementation diagram is used to form activity instances.

[0085] The specific definition of the executable view system modeling device can be found in the definition of the executable view system modeling method above and will not be repeated here. The various modules in the above-mentioned executable view system modeling device can be implemented in whole or in part through software, hardware, or a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in hardware form, or can be stored in the memory of the computer device in software form, so that the processor can call and execute the corresponding operations of the above modules.

[0086] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 7As shown. The computer device includes a processor, memory, network interface, display screen and input device connected via a system bus. 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 computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, an executable view modeling method is implemented. The display screen of the computer device can be a liquid crystal display 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, trackball or touchpad provided on the computer device housing, or an external keyboard, touchpad or mouse. The computer device can be a simulation device, the input device inputs relevant information to the simulation device, the processor executes the program in the memory to perform combined simulation, and the display screen displays relevant simulation results.

[0087] Those skilled in the art will understand that Figure 7 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0088] In one embodiment, a computer device is provided, including a memory and a processor. The memory stores a computer program, and the processor implements the steps of the method in the above embodiment when executing the computer program.

[0089] 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.

[0090] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the 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-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory 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 (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0091] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, 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, they should be considered to be within the scope of this specification.

[0092] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person skilled in the art could make various modifications and improvements without departing from the spirit of the present application, all of which fall within the scope of protection of the present application. Therefore, the scope of protection of the present patent application shall be determined by the appended claims.

Claims

1. An executable view system modeling method, characterized in that: include: According to the requirements of the modeling task, establish the layer architecture view related to the domain requirements; The domain requirement related layer architecture view includes different view systems, and the view system includes modeling boundary information, modeling granularity information and modeling resolution information; The domain requirement related layer decouples the modeling object boundary, modeling granularity, and modeling resolution level according to the modeling purpose, requirements, and main problems to be solved; Based on the modeling boundary information, establish a domain-independent layer architecture view; The domain-independent layer architecture view includes an architecture attribute diagram and an entity activity diagram; the domain-independent layer constrains the presentation of the view, including the type, function, and usage of view elements, and provides formal human-computer interactivity; The architecture attribute diagram is a view that describes the static descriptive information between entities and activities. It constrains the inheritance relationship, attribute fields, attribute field composition relationship, and attribute value content of entities and activities. It is a static view. The entity activity diagram is a view that describes the dynamic changes between entities and activities. It constrains the interaction between entities and activities and can provide information transmission and event-triggered business logic. It is a dynamic view. The modeling task is divided into different modeling objects according to the modeling granularity information and the modeling resolution information; and domain-implementation-related layer architecture views are established for the modeling objects according to the architecture attribute diagram and the entity activity diagram; The domain implementation layer is divided into different modeling objects based on the modeling resolution and granularity, and object views are established for each object to further split and decouple complexity; Implement relevant layer architecture views according to the domain and perform view modeling.

2. The method according to claim 1, characterized in that The domain requirement related layer is decoupled from the requirement boundary to establish a view system; the domain-independent layer is decoupled from the expression form to establish a view type; the domain implementation related layer is decoupled from the scene object to establish a view object.

3. The method according to claim 2, characterized in that Entity nodes and entity attribute nodes can be transferred between view systems to unify the object namespace and perform entity reuse.

4. The method according to any one of claims 1 to 3, characterized in that The architecture attribute graph includes: an entity architecture attribute graph and an activity architecture attribute graph.

5. The method according to any one of claims 1 to 3, characterized in that The architectural property diagram is used to model information declarations.

6. The method according to any one of claims 1 to 3, characterized in that The entity activity diagram includes: an activity template diagram and an activity implementation diagram.

7. The method according to claim 6, characterized in that The entity activity diagram is used for modeling implementation, wherein the activity template diagram is used for providing activity combinations, and the activity implementation diagram is used for forming activity instances.

8. An executable view system modeling device, characterized in that: include: The domain requirement related layer module is used to establish the domain requirement related layer architecture view according to the requirements of the modeling task; The domain requirement related layer architecture view includes different view systems, and the view system includes modeling boundary information, modeling granularity information and modeling resolution information; The domain requirement related layer decouples the modeling object boundary, modeling granularity, and modeling resolution level according to the modeling purpose, requirements, and main problems to be solved; The domain-independent layer module is used to establish a domain-independent layer architecture view based on the modeling boundary information; The domain-independent layer architecture view includes an architecture attribute diagram and an entity activity diagram; the domain-independent layer constrains the presentation of the view, including the type, function, and usage of view elements, and provides formal human-computer interactivity; The architecture attribute diagram is a view that describes the static descriptive information between entities and activities. It constrains the inheritance relationship, attribute fields, attribute field composition relationship, and attribute value content of entities and activities. It is a static view. The entity activity diagram is a view that describes the dynamic changes between entities and activities. It constrains the interaction between entities and activities and can provide information transmission and event-triggered business logic. It is a dynamic view. A domain implementation related layer module is used to split the modeling task into different modeling objects according to the modeling granularity information and the modeling resolution information; and to establish a domain implementation related layer architecture view for the modeling object according to the architecture attribute diagram and the entity activity diagram; The domain implementation layer is divided into different modeling objects based on the modeling resolution and granularity, and object views are established for each object to further split and decouple complexity; The modeling module is used to implement the relevant layer architecture view according to the domain and perform view modeling.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images