CN115794717A - Model-based interface design method, system, medium, and apparatus - Google Patents
Model-based interface design method, system, medium, and apparatus Download PDFInfo
- Publication number
- CN115794717A CN115794717A CN202211564787.5A CN202211564787A CN115794717A CN 115794717 A CN115794717 A CN 115794717A CN 202211564787 A CN202211564787 A CN 202211564787A CN 115794717 A CN115794717 A CN 115794717A
- Authority
- CN
- China
- Prior art keywords
- model
- data
- definition
- module
- interface
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The application relates to a model-based interface design method, system, medium and device, comprising: the method comprises the steps that a client receives operation information of a developer definition module, selects a preset application meta-model, sets module attributes of the application meta-model and generates a communication port in the application meta-model, and therefore a module definition model is generated; the method comprises the steps that a client receives operation information of interface data defined by a developer, selects a preset basic data meta-model, and sets data attributes of the basic data meta-model so as to generate an interface data definition model; and the client receives the operation information of the interconnection relationship designed by the developer, calls the stored interface data definition model and the model definition model and binds the interface data definition model and the model definition model. The method and the device have the advantages that related interface designs can be multiplexed, and the efficiency of interface design is improved.
Description
Technical Field
The application relates to the field of complex embedded system integrated design, in particular to a model-based interface design method and system.
Background
Interface design generally appears in the summary design stage of software development, and the summary design needs to divide the module according to the demand, and need define the interface to realize the relation between the module, therefore interface design is very important in software development.
The data related to the interface design is recorded and managed by an interface data recording and managing system based on a database, and the data related to the interface design is recorded into the interface database as an integral model for storage and management.
For the related technologies, interface data is input into an interface database, so that an information receiving party, an information sending party and an information name are bound by an integral model, and when a developer defines other related integral models, data in the previously defined integral model cannot be taken out for use, so that the defects of repeated definition and low efficiency exist when a plurality of interfaces need to be designed.
Disclosure of Invention
In order to improve the efficiency of designing an interface, the application provides a model-based interface design method and system.
The model-based interface design method provided by the application adopts the following technical scheme:
a model-based interface design method, comprising:
receiving module definition operation information, generating a module definition model according to the module definition operation information, and storing the module definition model in a data storage library;
receiving interface data definition operation information, generating an interface data definition model according to the interface data definition operation information, and storing the interface data definition model in a data storage library;
and receiving interconnection design operation information, and associating the module definition model with an interface data definition model according to the interconnection design operation information to generate an integrated design model.
By adopting the technical scheme, the model is generated by defining the module and the interface data in the interface design process, and the generated model can be called out for use when the interconnection relation is designed, so that the efficiency of designing the interface is improved.
Preferably, before the receiving the interface data defines the operation information, the method further includes:
receiving selection information of a preset basic data meta-model;
and calling and displaying the basic data element model according to the selection information of the basic data element so as to allow a user to define interface data.
By adopting the technical scheme, the operation window for defining the interface data is displayed after the selection information of the basic data meta-model of the developer is received, so that the effect of facilitating the definition of the interface data by the developer is achieved.
Preferably, before the receiving module defines the operation information, the method further includes:
receiving selection information of a preset application meta-model;
and calling and displaying the application meta-model according to the selection information of the application meta-model so as to allow a user to define the operation of the module.
By adopting the technical scheme, the operation window of the definition module is displayed after the selection information of the developer application meta-model is received, so that the effect of facilitating the developer to define the module is achieved.
Preferably, the generating a module definition model according to the module definition operation information includes:
and generating a communication port in the selected application meta-model according to the port creation information in the module definition operation information.
By adopting the technical scheme, the communication port is generated in the application meta-model according to the port creation operation information of the developer by selecting the application meta-model built in the software, so that the module definition model is generated, and the effect of modeling the module definition for calling is achieved.
Preferably, the generating an interface data definition model according to the interface data definition operation information includes:
and setting the data attribute of the basic data meta-model according to the data attribute information in the interface data definition operation information.
By adopting the technical scheme, the data attribute of the basic data meta-model is set according to the data attribute information input by the developer by selecting the basic data meta-model built in the software, so that the interface data definition model is generated, and the effect of modeling the interface design definition for calling is achieved.
Preferably, in associating the module definition with the interface data definition model, the method includes:
selecting a module definition model in a data repository according to model selection information in the interconnection design operation information;
and binding the interface data definition model with the communication port of the module definition model according to the binding information in the interconnection design operation information.
By adopting the technical scheme, the interface data definition model and the communication port of the module definition model are bound according to the binding operation information of the interface data model of the developer by selecting the module definition model, so that an integrated design model is generated, and the effect of defining the data transmission channel between the module ports is achieved.
Preferably, the interface data definition model includes data type definitions and common bus protocols thereof, and the module definition model includes application attributes, port definitions and other components.
By adopting the technical scheme, the interface data definition model comprises the data type definition and the common bus protocol, and can limit the transmission data type, the transmission data direction and the like of the module port after the interface data definition model is bound with the module port. The module definition model comprises application attributes and port definitions. The method achieves the purpose that a developer can freely select the interface data definition model and the module definition model according to the functions required to be realized by the designed interface.
The application also provides an interface design system based on the model.
The graphical modeling interface module is used for providing a graphical human-computer operation interface so as to facilitate developers to carry out related interface design work;
the data meta-model module is used for providing a data meta-model required by the generation module definition model, the interface data definition model and the integrated design model;
the model management module is used for generating a module definition model, an interface data definition model and an integrated design model;
and the data storage module is used for storing the generated module definition model, the interface data definition model and the integrated design model.
The present application also provides a computer-readable storage medium.
A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, causes the processor to implement a model-based interface design method.
The application also provides a computer device, which adopts the following technical scheme:
comprises a memory and a processor, wherein the memory is loaded by the processor and executed
Such as the computer program of the distributed version control-based model development method described above.
In summary, the present application includes at least one of the following beneficial technical effects:
1. the module definition and the interface data definition are modeled, and the module definition model and the interface data definition model are stored in the data repository to be called, so that the effect of being beneficial to development personnel to flexibly multiplex data in the interface designing process is achieved;
2. by providing the graphical human-computer operation interface, developers can design related interfaces through the visual graphical operation interface, so that the developers can better look up and understand the effect of the data integration interaction relationship through a graphical display mode.
Drawings
Fig. 1 is a flowchart and a timing diagram of a method for designing a model-based interface according to an embodiment of the present disclosure.
Fig. 2 is a schematic application scenario diagram of a model-based interface design method according to an embodiment of the present application.
FIG. 3 is a block diagram of a system for model-based interface design according to an embodiment of the present application.
Description of reference numerals: 1. a graphical modeling interface module; 2. a data meta-model module; 3. a model management module; 4. and a data storage module.
Detailed Description
The embodiment of the application discloses an interface design method based on a model. Referring to fig. 1 and 2, a model-based interface design method includes the steps of:
s11: receiving application meta-model selection operation information, and calling and displaying an application meta-model according to the operation information;
the application meta-model refers to a meta-model required by module definition, and includes components such as application attributes and port definitions.
Specifically, after receiving the selection information of the application meta-model icon button, the software client accesses a data storage area for storing the application meta-model, reads the storage data in the data storage area, and displays the information of all application meta-models in the first operation window according to the storage data.
The information of the application meta-model comprises icon description information and text description information of the application meta-model, and a data access channel of the application meta-model is displayed at the same time.
For example, after a developer clicks and selects a data access channel of a corresponding application meta-model through a mouse, a software client displays an attribute information editing window of the selected application meta-model, and the developer can modify data of the application meta-model by inputting information in the attribute information editing window.
S12: receiving module definition operation information, and generating a module definition model according to the operation information;
specifically, the generation of the module definition model according to the operation information includes the following steps:
s121: selecting an application meta-model built in the software according to the application meta-model selection information;
specifically, after receiving the selection information of the application meta-model in the first operation window, the software client accesses the data storage area storing the selected application meta-model, and invokes the application meta-model corresponding to the selection information, and the corresponding relationship between the application meta-model and the selection information may be established in a manner of matching the applied same or associated digital information or symbolic information. And simultaneously displaying the data information of the selected application meta model in a third operation window.
The data information of the selected application meta-model comprises module attribute information, port information and an information channel corresponding to the selected application meta-model.
For example, a developer may input data information through an information channel corresponding to the selected application meta-model to edit port information of the selected application meta-module.
S122: generating a communication port of the application meta-model according to port creation information in the operation information to obtain a module definition model;
specifically, after the second operation window is displayed, the software client enters a state of receiving data input confirmation information, and if the data input confirmation information is received, the port data information input in the second operation window is read, and the read data is recorded into a defined storage area of the port data of the application meta-model, so that the definition of the application meta-model port is completed.
S123: storing the module definition model in a data repository;
specifically, after the meta-model data entry is completed, a module definition model is formed, all data of the module definition model are entered into a data storage library for storage, and meanwhile, data in the definition storage region are cleared.
S13: receiving basic data meta-model selection operation information, and calling and displaying the basic data meta-model according to the operation information;
the basic data meta-model comprises data type definitions, common bus protocols and other components.
Specifically, after receiving the selection information of the basic data meta-model icon button, the software client accesses the data storage area for storing the basic data meta-model, reads the storage data in the data storage area, and displays the information of all the basic data meta-models on the third operation window according to the storage data.
The information of the basic data meta-model comprises icon description information and character description information of the basic data meta-model, and a data access channel of the basic data meta-model is displayed at the same time.
For example, after a developer clicks and selects a corresponding application meta-model data access channel through a mouse, the software client displays a property information editing window of the selected basic data meta-model, and the developer inputs information in the property editing window to modify data of the basic data meta-model.
S14: receiving interface data definition operation information and generating an interface data definition model according to the operation information;
specifically, the step of generating the interface data definition model according to the operation information includes the following steps:
s141: selecting a basic data meta-model built in the software according to the basic data meta-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, and invokes the basic data meta-model corresponding to the selection information, and the corresponding relationship between the basic data meta-model and the selection information may be established in a manner of matching applied same or associated digital information or symbolic information. And simultaneously displaying the data information of the selected basic data meta-model in a fourth operation window.
And the data information of the selected basic data meta-model comprises data attribute information and an information channel corresponding to the selected basic data meta-model.
For example, a developer may input data information through an information channel corresponding to the selected base data meta-model to edit data attribute information of the selected base data meta-model.
S142: setting data attributes of the basic data meta-model according to data attribute setting information in the operation information to obtain an interface data definition model;
specifically, after the fourth operation window is displayed, the software client enters a state of receiving data input confirmation information, and if the data input confirmation information is received, the data attribute data information input in the fourth operation window is read, and the read data is recorded into a defined storage area of data attribute data of the basic data meta-model, so that the definition of interface data is completed.
Wherein the data attribute data includes: specific data types, specific bus protocols, specific format standards for receiving or transmitting data, etc.
S143: storing the interface data definition model in a data repository;
specifically, after the basic data meta-model data entry is completed, an interface data definition model is formed, all data of the interface data definition model are entered into a data storage library for storage, and meanwhile, data in the definition storage region are cleared.
S15: receiving interconnection design operation information and generating an integrated design model according to the operation information;
the integrated design model refers to a model obtained by associating a module definition model and an interface data definition model.
Specifically, the generation of the integrated design model according to the operation information includes the following steps:
s151: selecting a module definition model according to the model selection information;
specifically, after receiving the selection information of the module definition model icon button, the software client accesses the data storage area in the data storage library, where the module definition model is stored, reads the storage data in the data storage area, and displays the information of all the module definition models in the fifth operation window according to the storage data. And after receiving the selection information of the module definition model, the software client accesses the data storage area for storing the module definition, reads the storage data of the data storage area, displays the icon information of the selected module definition model on the interface of the software client and simultaneously displays the data access channel of the selected module definition model, thereby obtaining the module example.
The information of the module definition model comprises icon description information and text description information of the module definition model, and a data access channel of the module definition model is displayed at the same time.
For example, the developer presses the engineering project button right in the engineering project bar to the left of the software client and clicks on the create module instance in the displayed option bar. After popping up an operation window for displaying the stored module definition model on the software client interface, a developer can click and select the module definition model through a mouse to complete the creation of a module instance on the software client interface, and meanwhile, a button of the module instance is generated in an engineering project column on the left side of the software client.
S152: and according to the binding information, selecting an interface data model and binding the interface data model with the communication port of the created module instance.
Specifically, after receiving the operation information of binding the interface data for the module instance, the software client accesses the data storage area in the data storage library, where the interface data definition model is stored, reads the stored data in the data storage area, and displays the information of all the interface data definition models in the sixth operation window according to the stored data. After receiving the selection information of the interface data definition model, the software client accesses the data storage area for storing the selected interface data definition model, reads the storage data of the data storage area, and binds the selected interface data definition model with the port of the module instance, and the binding relationship between the selected interface data definition model and the port of the module instance can be established in a mode of creating a mapping relationship table.
The information of the interface data definition model comprises icon description information and text description information of the interface data definition model, and a data access channel of the module definition model is displayed at the same time.
For example, a developer selects two module instances in the software client interface by mouse clicking, the module instance selected by the right button, and the binding interface is selected in the pop-up option bar. The software client now displays a list of stored interface data definition models. The developer can select the interface data definition model to be bound through mouse clicking. After the developer selects the bound interface data definition model, the software client establishes a mapping relation table of the port information of the two module instances and the storage position of the interface data definition model, wherein the mapping relation table can be attached to the interface data definition model. After the module instance a sends the data X through the port, the software client maps the valid data information in the interface data definition model to the output information of the output port of the module instance a. Through the process, the data can be sent to the designated module instance after being sent from one module instance and processed by the interface data definition model.
The implementation principle of the model-based interface design method in the embodiment of the application is as follows: the interface design is divided into three parts, namely data definition, module definition and integration definition, and the related design of the data definition and the module definition is modeled and stored in the interface design process for subsequent integrated design calling.
The embodiment of the application also discloses an interface design system based on the model.
Referring to fig. 3, a model-based interface design system includes: the system comprises a graphical modeling interface module 1, a data meta-model module 2, a model management module 3 and a data storage module 4.
The graphical modeling interface module 1 is used for providing a graphical human-computer operation interface so as to facilitate developers to carry out related interface design work;
the data meta-model module 2 is used for providing a data meta-model required by a generation module definition model, an interface data definition model and an integrated design model;
the model management module 3 is used for generating a module definition model, an interface data definition model and an integrated design model;
and the data storage module 4 is used for storing the generated module definition model, the interface data definition model and the integrated design model.
It should be noted that: in addition, the embodiment of the model-based interface design system and the embodiment of the model-based interface design method provided in the embodiment belong to the same concept, and specific implementation processes thereof are described in the method embodiment and are not described herein again.
Another embodiment of the present application also discloses a computer readable storage medium.
Specifically, the computer-readable storage medium, which stores a computer program that can be loaded by a processor and executes the model development method based on distributed version control as described above, includes, for example: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The application further discloses a computer device.
Specifically, the computer device includes a memory having stored thereon a memory capable of storing a program code and a processor
And the computer program is loaded by the processor and executes the model development method based on the distributed version control.
The above embodiments are preferred embodiments of the present application, and the protection scope of the present application is not limited by the above embodiments, so: all equivalent changes made according to the structure, shape and principle of the present application shall be covered by the protection scope of the present application.
Claims (10)
1. A model-based interface design method is applied to a client side and is characterized by comprising the following steps:
receiving module definition operation information, generating a module definition model according to the module definition operation information, and storing the module definition model in a data repository;
receiving interface data definition operation information, generating an interface data definition model according to the interface data definition operation information, and storing the interface data definition model in a data storage library;
and receiving interconnection design operation information, and associating the module definition model with an interface data definition model according to the operation information of the design interconnection relationship to generate an integrated design model.
2. The method of claim 1, wherein prior to receiving the interface data defining the operation information, comprising:
receiving selection information of a preset basic data meta-model;
and calling and displaying the basic data meta-model according to the basic data meta-model selection information so as to allow a user to carry out interface data defining operation.
3. The method of claim 1, wherein before the receiving module defines the operation information, the method comprises:
receiving selection information of a preset application meta-model;
and calling and displaying the application meta-model according to the application meta-model selection information so as to allow a user to define the operation of the module.
4. A method according to claim 1, wherein generating a module definition model from the module definition operation information comprises:
and generating a communication port in the selected application meta-model according to the port creation information in the module definition operation information.
5. The method of claim 1, wherein generating the interface data definition model according to the interface data definition operation information comprises:
and setting the data attribute of the basic data meta-model according to the data attribute information in the interface data definition operation information.
6. A method of model-based interface design according to claim 1, comprising the steps of, in associating the module definition with an interface data definition model:
selecting a module definition model in a data repository according to model selection information in the operation information for designing the interconnection relationship;
and binding the interface data definition model with the communication port of the module definition model according to the binding information in the interconnection design operation information.
7. A model-based interface design method according to claim 1, comprising:
the interface data definition model comprises data type definition, a common bus protocol and other components;
the module definition model comprises components such as application attributes, port definitions and the like.
8. A system based on the model-based interface design method of any one of claims 1 to 7, the system comprising:
the graphical modeling interface module is used for providing a graphical human-computer operation interface so as to facilitate developers to carry out related interface design work;
the data meta-model module is used for providing a data meta-model required by the generation module definition model, the interface data definition model and the integrated design model;
the model management module is used for generating a module definition model, an interface data definition model and an integrated design model;
and the data storage module is used for storing the generated module definition model, the interface data definition model and the integrated design model.
9. A computer storage medium, characterized in that it stores a plurality of instructions adapted to be loaded by a processor and to perform the method steps according to any one of claims 1 to 7.
10. An electronic device, comprising: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to perform the method steps of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211564787.5A CN115794717A (en) | 2022-12-07 | 2022-12-07 | Model-based interface design method, system, medium, and apparatus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211564787.5A CN115794717A (en) | 2022-12-07 | 2022-12-07 | Model-based interface design method, system, medium, and apparatus |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115794717A true CN115794717A (en) | 2023-03-14 |
Family
ID=85417661
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211564787.5A Pending CN115794717A (en) | 2022-12-07 | 2022-12-07 | Model-based interface design method, system, medium, and apparatus |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115794717A (en) |
-
2022
- 2022-12-07 CN CN202211564787.5A patent/CN115794717A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Kery et al. | mage: Fluid moves between code and graphical work in computational notebooks | |
| CN110325961B (en) | Spreadsheet-based software application development | |
| KR101130525B1 (en) | Method and apparatus for generating forms using form types | |
| US8504981B2 (en) | Application development support device, program, and recording medium | |
| AU2018201198A1 (en) | Collaborative design systems, apparatuses, and methods | |
| US7159209B1 (en) | Inter-application validation tool for use in enterprise architecture modeling | |
| CA2451164A1 (en) | Customizable components | |
| US20110010687A1 (en) | Synchronization of concurrently modified interdependent semi-derived artifacts | |
| US20040268232A1 (en) | Pane Element | |
| CN101460943A (en) | Modifying a chart | |
| US20070282866A1 (en) | Application integration using xml | |
| AU2008288768B2 (en) | Defining an interactive user interface | |
| US20070038947A1 (en) | Method and device for generation of a parametric model associated with a 3D geometry | |
| US9135234B1 (en) | Collaborative generation of digital content with interactive reports | |
| JP2022041865A (en) | Online working system for template-based excel documents | |
| CA2686367A1 (en) | Dynamic native editor code view facade | |
| TWI771832B (en) | Computer-implemented system and method for managing electronic document | |
| US20100122188A1 (en) | Method and device for editing an object represented in a web page | |
| CN115794717A (en) | Model-based interface design method, system, medium, and apparatus | |
| JP2017102872A (en) | Development device, development system, and program | |
| KR100902193B1 (en) | A System For Composing Report, A Method ? A System For Providing A Made-To-Order Report, And A Storage Medium | |
| JPH064280A (en) | Graphical user interface having function of user control for object with wysiwyg type editor | |
| JP2005078119A (en) | Support system and method for software development support, program, and recording medium | |
| KR20050081336A (en) | Method and programm recording medium for customizing a presentation file according to event | |
| JP2009110283A (en) | Associated information management apparatus, associated information management method, and associated information management program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |