Model-based interface design methods, systems, media, and devices

Abstract

This application relates to a model-based interface design method, system, medium, and device, comprising: a client receiving operation information from developers defining modules, selecting a preset application metamodel, setting module attributes of the application metamodel, and generating communication ports in the application metamodel, thereby generating a module definition model; the client receiving operation information from developers defining interface data, selecting a preset basic data metamodel, and setting data attributes of the basic data metamodel, thereby generating an interface data definition model; and the client receiving operation information from developers designing interconnection relationships, retrieving stored interface data definition models and model definition models, and binding them. This application has the effect of reusing related interface designs and improving interface design efficiency.

Description

Technical Field

[0001] This application relates to the field of complex embedded system integration design, and in particular to model-based interface design methods and systems. Background Technology

[0002] Interface design typically occurs during the preliminary design phase of software development. The preliminary design involves dividing the software into modules based on requirements, and interfaces need to be defined to enable communication between these modules. Therefore, interface design is crucial in software development.

[0003] The data related to interface design is usually recorded and managed through a database-based interface data recording and management system. The data related to interface design is entered into the interface database as a whole model for storage and management.

[0004] Regarding the aforementioned technologies, since the interface data is entered into the interface database, the information recipient, information sender, and information name are bound to the overall model. When developers define other related overall models, the data in the previously defined overall model cannot be retrieved and used. When multiple interfaces need to be designed, there are defects such as duplicate definitions and low efficiency. Summary of the Invention

[0005] To improve the efficiency of interface design, this application provides a model-based interface design method and system.

[0006] The model-based interface design method provided in this application adopts the following technical solution: A model-based interface design method, comprising: Receive module definition operation information, generate a module definition model based on the module definition operation information, and store the module definition model in the data repository; Receive interface data definition operation information, generate an interface data definition model based on the interface data definition operation information, and store the interface data definition model in the data repository; Receive interconnection design operation information, and based on the interconnection design operation information, associate the module definition model and the interface data definition model to generate an integrated design model.

[0007] By adopting the above technical solution, a model is generated from the module definition and interface data definition in the interface design process. The generated model can be called up and used when designing interconnection relationships, thereby improving the efficiency of interface design.

[0008] Preferably, before defining the operation information of the receiving interface data, the method further includes: Receive the selection information of the preset basic data meta-model; Based on the selected basic data elements, the basic data element model is retrieved and displayed for users to define interface data.

[0009] By adopting the above technical solution, after receiving the selection information of the basic data meta-model from the developer, an operation window for defining interface data is displayed, which achieves the effect of facilitating the definition of interface data by the developer.

[0010] Preferably, before the receiving module defines the operation information, it further includes: Receive the selection information of the preset application meta-model; Based on the selected application metamodel information, the application metamodel is retrieved and displayed for the user to perform module definition operations.

[0011] By adopting the above technical solution, after receiving the selection information of the application metamodel from the developer, the operation window for defining the module is displayed, which achieves the effect of facilitating the developer to define the module.

[0012] Preferably, the step of generating a module definition model based on the module definition operation information includes: Based on the port creation information in the module definition operation information, a communication port is generated in the selected application metamodel.

[0013] By adopting the above technical solution, by selecting the application meta-model built into the software, and generating communication ports in the application meta-model based on the operator information created by the developer's port, a module definition model is generated, thereby achieving the effect of modeling the module definition for use.

[0014] Preferably, generating the interface data definition model based on the interface data definition operation information includes: Based on the data attribute information in the interface data definition operation information, set the data attributes of the basic data meta-model.

[0015] By adopting the above technical solution, by selecting the basic data meta-model built into the software, and setting the data attributes of the basic data meta-model according to the data attribute information input by the developers, an interface data definition model is generated, thereby achieving the effect of modeling the interface design definition for use.

[0016] Preferably, associating the module definition with the interface data definition model includes: Based on the model selection information in the interconnection design operation information, select the module definition model in the data repository; Based on the binding information in the interconnection design operation information, the communication ports of the interface data definition model and the module definition model are bound together.

[0017] By adopting the above technical solution, by selecting a module definition model, and binding the communication ports of the interface data definition model and the module definition model according to the binding operation information of the developer's interface data model, an integrated design model is generated, thereby achieving the effect of defining the data transmission channel between module ports.

[0018] Preferably, the interface data definition model includes data type definitions and its commonly used bus protocol components, and the module definition model includes application attributes and port definition components.

[0019] By adopting the above technical solution, the interface data definition model, which includes data type definitions and common bus protocols, can restrict the data type and direction of data transmission by the module port after binding it with the module port. The module definition model includes application attributes and port definitions. This allows developers to freely choose between the interface data definition model and the module definition model based on the functionality required by the designed interface.

[0020] This application also provides a model-based interface design system.

[0021] The graphical modeling interface module provides a graphical human-computer interaction interface to facilitate developers in carrying out related interface design work. The data meta-model module is used to provide the data meta-models required to generate module definition models, interface data definition models, and integration design models. The model management module is used to generate module definition models, interface data definition models, and integration design models; The data storage module is used to store the generated module definition model, interface data definition model, and integration design model.

[0022] This application also provides a computer-readable storage medium.

[0023] A computer-readable storage medium storing a computer program that, when executed by a processor, causes the processor to implement a model-based interface design method.

[0024] This application also provides a computer device, which adopts the following technical solution: It includes a memory and a processor, wherein the memory stores information that can be loaded and executed by the processor. The computer program developed using the distributed version control model described above.

[0025] In summary, this application includes at least one of the following beneficial technical effects: 1. By modeling module definitions and interface data definitions, and storing the module definition models and interface data definition models in a data repository for later retrieval, the goal is to help developers flexibly reuse data during the interface design process. 2. By providing a graphical user interface, developers can design relevant interfaces through a visual graphical interface, thereby enabling them to better view and understand the data integration and interaction relationships through graphical display. Attached Figure Description

[0026] Figure 1 This is a flowchart of a model-based interface design method according to an embodiment of this application.

[0027] Figure 2 This is a schematic diagram illustrating an application scenario of a model-based interface design method according to an embodiment of this application.

[0028] Figure 3 This is a block diagram of a model-based interface design system according to an embodiment of this application.

[0029] Explanation of reference numerals in the attached diagram: 1. Graphical modeling interface module; 2. Data element model module; 3. Model management module; 4. Data storage module. Detailed Implementation

[0030] This application discloses a model-based interface design method. (Refer to...) Figure 1 and Figure 2 A model-based interface design method includes the following steps: S11: Receive the application metamodel selection operation information, and retrieve and display the application metamodel according to the operation information; The application metamodel refers to the metamodel required for module definition, including components such as application attributes and port definitions.

[0031] Specifically, after receiving the selection information from the application metamodel icon button, the software client accesses the data storage area where the application metamodel is stored, reads the stored data in the data storage area, and displays all the application metamodel information in the first operation window based on the stored data.

[0032] The information in the application metamodel includes icon descriptions, text descriptions, and the data access channels of the application metamodel.

[0033] For example, after a developer selects the data access channel for the corresponding application metamodel by clicking with the mouse, the software client displays the attribute information editing window of the selected application metamodel. The developer can modify the data of the application metamodel by entering information in the attribute information editing window.

[0034] S12: Receive module definition operation information and generate a module definition model based on the operation information; Specifically, the model definition module based on the operation information includes the following steps: S121: Select the application meta-model built into the software based on the application meta-model selection information; Specifically, after receiving the selection information of the application metamodel in the first operation window, the software client accesses the data storage area storing the selected application metamodel, retrieves the application metamodel corresponding to the selection information, and establishes the correspondence between the application metamodel and the selection information by matching the same or related numerical or symbolic information. Simultaneously, the data information of the selected application metamodel is displayed in the third operation window.

[0035] The data information of the selected application metamodel includes module attribute information, port information, and the information channel corresponding to the selected application metamodel.

[0036] For example, developers can edit the port information of the selected application meta-module by inputting data through the information channel corresponding to the selected application meta-model.

[0037] S122: Based on the port creation information in the operation information, generate the communication port of the application meta-model to obtain the module definition model; Specifically, after the second operation window is displayed, the software client enters the state of receiving data input confirmation information. If the data input confirmation information is received, the port data information entered in the second operation window is read and the read data is entered into the port data definition storage area of ​​the application metamodel to complete the definition of the application metamodel port.

[0038] S123: Store the module definition model in the data repository; Specifically, after the application meta-model data is entered, a module definition model is formed. All data of the module definition model is entered into the data repository and saved separately, while the data in the definition storage area is cleared.

[0039] S13: Receive basic data meta-model selection operation information, retrieve and display the basic data meta-model according to the operation information; The basic data element model includes components such as data type definitions and commonly used bus protocols.

[0040] Specifically, after receiving the selection information from the basic data meta-model icon button, the software client accesses the data storage area where the basic data meta-model is stored, reads the stored data in the data storage area, and displays the information of all basic data meta-models on the third operation window based on the stored data.

[0041] The information in the basic data meta-model includes icon descriptions, text descriptions, and the data access channels of the basic data meta-model.

[0042] For example, after a developer selects the corresponding application metamodel data access channel by clicking with the mouse, the software client displays the attribute information editing window of the selected basic data metamodel. The developer can modify the data of the basic data metamodel by entering information in the attribute editing window.

[0043] S14: Receive interface data definition operation information and generate an interface data definition model based on the operation information; Specifically, generating the interface data definition model based on the operation information includes the following steps: S141: Select the built-in basic data element model based on the basic data element model selection information; Specifically, after receiving the selection information of the basic data meta-model in the third operation window, the software client accesses the data storage area storing the selected basic data meta-model, retrieves the basic data meta-model corresponding to the selection information, and establishes the correspondence between the basic data meta-model and the selection information by matching the same or related numerical or symbolic information. Simultaneously, the data information of the selected basic data meta-model is displayed in the fourth operation window.

[0044] The data information of the selected basic data element model includes data attribute information and the information channel corresponding to the selected basic data element model.

[0045] For example, developers can edit the data attribute information of the selected basic data meta-model by inputting data information through the information channel corresponding to the selected basic data meta-model.

[0046] S142: Based on the data attribute setting information in the operation information, set the data attributes of the basic data element model to obtain the interface data definition model; Specifically, after the fourth operation window is displayed, the software client enters the state of receiving data input confirmation information. If the data input confirmation information is received, the software reads the data attribute data information entered in the fourth operation window and enters the read data into the definition storage area of ​​the data attribute data of the basic data element model to complete the definition of the interface data.

[0047] The data attribute data includes: specific data types, specific bus protocols, and specific format standards for receiving or sending data.

[0048] S143: Store the interface data definition model in the data repository; Specifically, after the basic data meta-model data is entered, an interface data definition model is formed. All data of the interface data definition model is entered into the data repository and saved separately, while the data in the definition storage area is cleared.

[0049] S15: Receive interconnect design operation information and generate an integrated design model based on the operation information; The integrated design model refers to the model obtained by linking the module definition model and the interface data definition model.

[0050] Specifically, generating an integrated design model based on operational information includes the following steps: S151: Based on the model selection information, select the module to define the model; Specifically, after receiving the selection information from the module definition model icon button, the software client accesses the data storage area storing the module definition models in the data repository, reads the stored data from the data storage area, and displays the information of all module definition models in the fifth operation window based on the stored data. Upon receiving the selection information from the module definition model, the software client accesses the data storage area storing the selected module definition, reads the stored data from the data storage area, displays the icon information of the selected module definition model on the software client interface, and simultaneously displays the data access channel of the selected module definition model, thereby obtaining the module instance.

[0051] The information of the module definition model includes icon descriptions, text descriptions, and data access channels.

[0052] For example, a developer can right-click the project button in the project panel on the left side of the software client, and then click "Create Module Instance" in the displayed options bar. After a window pops up in the software client interface showing the stored module definition model, the developer can click to select the module definition model to create a module instance on the software client interface, and simultaneously generate a button for the module instance in the project panel on the left side of the software client.

[0053] S152: Based on the binding information, select the interface data model and bind it to the communication port of the created module instance.

[0054] Specifically, after receiving the operation information to bind interface data to a module instance, the software client accesses the data storage area in the data repository that stores the interface data definition models, reads the stored data in the data storage area, and displays the information of all interface data definition models in the sixth operation window based on the stored data. After receiving the selection information for the interface data definition model, the software client accesses the data storage area that stores the selected interface data definition model, reads the stored data in the data storage area, and binds the selected interface data definition model to the port of the module instance. The binding relationship between the selected interface data definition model and the module instance port can be established by creating a mapping table.

[0055] The information in the interface data definition model includes icon descriptions, text descriptions, and the data access channels of the module definition model.

[0056] For example, a developer can select two module instances in the software client interface by clicking with the mouse, right-click the selected module instance, and choose "Bind Interface" from the pop-up options bar. The software client then displays a list of stored interface data definition models. The developer can then select the interface data definition model to bind. After the developer selects the interface data definition model to bind, the software client establishes a mapping table between the port information of the two module instances and the storage location of the interface data definition models. This mapping table can be attached to the interface data definition models. When module instance A sends data X through its port, the software client maps the valid data information in the interface data definition model to the output information of module instance A's output port. Similarly, when module instance B receives data X through its port, the software client maps the valid data information in the interface data definition model corresponding to data X to the input information of module instance B's receiving port. Through this process, data sent from one module instance is processed by the interface data definition model and can then be sent to the specified module instance.

[0057] The implementation principle of the model-based interface design method in this application embodiment is as follows: the interface design is divided into three parts: data definition, module definition and integration definition. During the interface design process, the relevant design models of data definition and module definition are modeled and stored for subsequent integration design calls.

[0058] This application also discloses a model-based interface design system.

[0059] Reference Figure 3 A model-based interface design system includes: a graphical modeling interface module 1, a data element model module 2, a model management module 3, and a data storage module 4.

[0060] Graphical Modeling Interface Module 1 is used to provide a graphical human-computer interaction interface to facilitate developers in carrying out related interface design work. Data Metamodel Module 2 is used to provide the data metamodels required to generate module definition models, interface data definition models, and integration design models; Model management module 3 is used to generate module definition models, interface data definition models, and integration design models; Data storage module 4 is used to store the generated module definition model, interface data definition model, and integration design model.

[0061] It should be noted that the system provided in the above embodiments is only illustrated by the division of the above functional modules when implementing its functions. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the model-based interface design system and the model-based interface design method provided in the above embodiments belong to the same concept. For details of its specific implementation process, please refer to the method embodiment, which will not be repeated here.

[0062] Another embodiment of this application also discloses a computer-readable storage medium.

[0063] Specifically, the computer-readable storage medium stores a computer program that can be loaded and executed by a processor, such as the distributed version control-based model development method described above. The computer-readable storage medium includes, for example, various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0064] Another embodiment of this application also discloses a computer device.

[0065] Specifically, the computer device includes a memory and a processor, with the memory storing information capable of... The computer program that is loaded and executed by the processor is based on the distributed version control model development method described above.

[0066] The above are all preferred embodiments of this application, and are not intended to limit the scope of protection of this application. Therefore, all equivalent changes made in accordance with the structure, shape and principle of this application should be covered within the scope of protection of this application.

Claims

1. A model-based interface design method, applied to the client side, characterized in that, include: Receive module definition operation information, generate a module definition model based on the module definition operation information, and store the module definition model in the data repository; Receive interface data definition operation information, generate an interface data definition model based on the interface data definition operation information, and store the interface data definition model in the data repository; Receive interconnection design operation information, and based on the interconnection design operation information, associate the module definition model and the interface data definition model to generate an integrated design model.

2. The model-based interface design method according to claim 1, characterized in that, Before the operation information is defined in the receiving interface data definition, the following is included: Receive the selection information of the preset basic data meta-model; Based on the information selected from the basic data meta-model, the basic data meta-model is retrieved and displayed for users to define interface data.

3. The model-based interface design method according to claim 1, characterized in that, Before the receiving module defines the operation information, it includes: Receive the selection information of the preset application meta-model; Based on the information selected from the application metamodel, the application metamodel is retrieved and displayed for the user to perform module definition operations.

4. The model-based interface design method according to claim 1, characterized in that, The step of generating a module definition model based on the module definition operation information includes the following steps: Based on the port creation information in the module definition operation information, a communication port is generated in the selected application metamodel.

5. The model-based interface design method according to claim 1, characterized in that, The step of generating the interface data definition model based on the interface data definition operation information includes the following steps: Based on the data attribute information in the interface data definition operation information, set the data attributes of the basic data meta-model.

6. The model-based interface design method according to claim 1, characterized in that, The process of associating the module definition with the interface data definition model includes the following steps: Based on the model selection information in the interconnection design operation information, select the module definition model in the data repository; Based on the binding information in the interconnection design operation information, the communication ports of the interface data definition model and the module definition model are bound together.

7. The model-based interface design method according to claim 1, characterized in that, include: The interface data definition model includes data type definitions and its commonly used bus protocol components; The module definition model includes application attributes and port definitions.

8. A system based on the model-based interface design method according to any one of claims 1-7, characterized in that, The system includes: The graphical modeling interface module provides a graphical human-computer interaction interface to facilitate developers in carrying out related interface design work. The data meta-model module is used to provide the data meta-models required to generate module definition models, interface data definition models, and integration design models. The model management module is used to generate module definition models, interface data definition models, and integration design models; The data storage module is used to store the generated module definition model, interface data definition model, and integration design model.

9. A computer storage medium, characterized in that, The computer storage medium stores a plurality of instructions adapted for loading by a processor and executing the steps of the method as described in any one of claims 1-7.

10. An electronic device, characterized in that, include: A processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to execute the steps of the method as claimed in any one of claims 1-7.

Images