CN117111935A - Industrial software low-code platform and metadata architecture thereof - Google Patents
Industrial software low-code platform and metadata architecture thereof Download PDFInfo
- Publication number
- CN117111935A CN117111935A CN202311016108.5A CN202311016108A CN117111935A CN 117111935 A CN117111935 A CN 117111935A CN 202311016108 A CN202311016108 A CN 202311016108A CN 117111935 A CN117111935 A CN 117111935A
- Authority
- CN
- China
- Prior art keywords
- metadata
- service
- module
- code platform
- layer
- 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
- 238000013507 mapping Methods 0.000 claims abstract description 24
- 238000012795 verification Methods 0.000 claims abstract description 12
- 238000012545 processing Methods 0.000 claims description 9
- 230000004044 response Effects 0.000 claims description 9
- 230000003068 static effect Effects 0.000 claims description 6
- 230000008520 organization Effects 0.000 claims description 3
- 238000011161 development Methods 0.000 abstract description 15
- 238000000034 method Methods 0.000 description 15
- 239000008186 active pharmaceutical agent Substances 0.000 description 13
- 238000013499 data model Methods 0.000 description 9
- 230000008569 process Effects 0.000 description 8
- 238000010276 construction Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 4
- 238000013475 authorization Methods 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 2
- 238000013523 data management Methods 0.000 description 2
- 238000013524 data verification Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000007689 inspection Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000009877 rendering Methods 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 238000010200 validation analysis Methods 0.000 description 2
- 238000012800 visualization Methods 0.000 description 2
- 238000007792 addition Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000007788 liquid Substances 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
- G06F8/44—Encoding
- G06F8/447—Target code generation
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses an industrial software low-code platform and a metadata architecture thereof, wherein the low-code platform comprises a metadata definition module: defining metadata types and attributes; metadata mapping module: mapping metadata into an actual application or service on the industrial software low-code platform; metadata verification module: verifying the matching between the metadata and the actual application or service; and a metadata updating module. The metadata architecture includes: the first metadata of the model layer is converted into second metadata of the service layer through the metadata mapping module, and the second metadata of the service layer is converted into third metadata of the page layer through the metadata mapping module. Constructing a multidimensional metadata structure, supporting complex logic and improving development efficiency; the metadata structure is divided into a model layer, a service layer and a page layer, metadata of different levels are used for different use scenes, and availability and readability of the metadata are improved.
Description
Technical Field
The invention relates to the technical field of metadata, in particular to an industrial software low-code platform and a metadata architecture thereof.
Background
Metadata refers to data describing an application or system component; it includes information such as data model of application program, user interface, business logic, database configuration, flow definition, etc. The low-code development software is a software development tool, and by simplifying the coding process, non-professional developers can create application programs, and the platforms generally comprise a visual interface and predefined components, so that the developers do not need to manually write codes to realize basic functions, and the low-code development platform can improve the development efficiency and reduce the development technical threshold of the application programs.
In the field of low-code development platforms, the existing low-code software technology tends to be mature, but functions generally only support basic forms, cannot realize excessively complex business logic, and have low support for personalized development. The metadata is used by the low code development platform to define objects, fields, configurations, code, logic and page layout, and automatically generate the data structures of the system and the user interfaces and automation logic of the application programs based on the metadata. Typical metadata generally only contains data structure definitions and page forms, and for complex function implementation, front-end and back-end code implementation is required, and technical requirements for developers are high.
Disclosure of Invention
The invention provides an industrial software low-code platform and a metadata framework thereof, which are used for constructing a multi-dimensional metadata structure, supporting complex logic and improving development efficiency, and aims to solve the problem that the metadata framework of the industrial software low-code platform in the prior art only supports a basic form and the technical capability of a developer is required to be relied on to improve the logic complexity.
In order to achieve the above purpose, the present invention adopts the following technical scheme:
an industrial software low code platform, the low code platform comprising a metadata definition module: defining metadata types and attributes; metadata mapping module: mapping metadata into an actual application or service on the industrial software low-code platform; metadata verification module: and verifying the matching between the metadata and the actual application program or service. By arranging the metadata definition module, the metadata mapping module and the metadata verification module on the low-code platform, in the data modeling stage, the metadata mapping module of the low-code platform is used for carrying out metadata mapping to generate a back-end code, so that the process of creating, combining and modifying an application program or service in the industrial low-code platform is simplified.
Preferably, the system further comprises a metadata storage module, wherein the metadata storage module is in communication connection with the metadata definition module and stores metadata types and attributes defined in the metadata definition module. The metadata is defined by the metadata definition module, so that the mapped metadata can be conveniently called by the items after the low-code platform configuration.
Preferably, the metadata verification module obtains the accuracy of the metadata by comparing the matching between the metadata and the actual application or service. And by verifying the matching between the metadata and the actual application program or service, the consistency and accuracy of the metadata are further ensured.
Preferably, the system further comprises a metadata updating module, wherein the metadata updating module is in communication connection with the metadata definition module, and the metadata updating module updates the metadata types and attributes defined in the metadata definition module. And updating the metadata according to the requirement, so as to improve the maintainability of the metadata.
An industrial software low code platform metadata architecture, applied to any of the industrial software low code platforms described above, comprising: the first metadata of the model layer is converted into second metadata of the service layer through the metadata mapping module, and the second metadata of the service layer is converted into third metadata of the page layer through the metadata mapping module. The second metadata is mapped by the first metadata, the second metadata comprises POJO, controller, service and Dao metadata, the third metadata is mapped by the second metadata, and the third metadata comprises Service application interface metadata, namely ServiceAPI, and web application program interface metadata, namely WebAPI.
Preferably, the model layer: describing the organization and architecture of metadata; the service layer: the system comprises a component for processing business logic in an application program, and has the functions of receiving a request, processing the request and returning a response; the page layer: including static metadata: describing a user interface; the dynamic metadata includes dynamic data dictionary and rights information. The model layer comprises: the model, the fields, the relations and the constraints, and the fields refer to data describing the attributes of each field in the model, wherein each field attribute data comprises a name, a type, a length, whether filling is needed or not, and the like. Model layer metadata is used for data management, data conversion, and data verification to ensure consistency of data. The service layer refers to a component for processing service logic in an application program, and comprises interface definition, service logic processing, data access and other parts. The Service layer metadata is divided into two layers, wherein the first layer is POJO, controller, service and Dao metadata formed by mapping a data model, and the Service layer converts the POJO, controller, service and Dao metadata again to convert the metadata of a Service application program interface (ServiceAPI) which can be called by a page layer and a third party and a web API (Web API) which is a metadata structure of a web page application program interface.
Preferably, the third metadata includes service application interface metadata and web page application program interface metadata, and the application interface metadata format includes JSON format; the format of the metadata of the application program interface comprises JSON and XML formats.
The service application program interface metadata, namely ServiceAPI, includes information including: service name and version number, API endpoint URL and HTTP method, supported request and response data format, authentication and authorization mechanism, error handling mode, data type of request parameter and return value and its value range. Wherein the supported request and response data formats include JSON and XML. By defining the serviceAPI metadata structure, a developer can conveniently understand and use the serviceAPI, and the readability, maintainability and reusability of the API are improved.
The web application program interface metadata, webAPI, includes information including: the API is the name, version number, list of parameters, return type, request and response format, validation requirements of the application program interface. Metadata is provided in JSON format, has structure and functionality that assists developers in understanding APIs, and performs verification and inspection when writing client code. The metadata has the functions of scenes such as automatic document generation, API test and code generation.
Preferably, the service layer comprises a code generation template and a page configuration tool, and the model layer comprises a database tool. The low-code platform generates the codes of the application programs by using the POJO, dao, service and Controller metadata of the Service layer through the code generation module, so that the development efficiency is improved, human errors are reduced, the logic complexity of the code generator is greatly reduced, and the automatic code generation efficiency is improved. The code generation template can be iteratively updated according to the subsequent requirement, the updated template can be combined with metadata to generate codes again, and the regenerated codes have new functions after template updating, so that repeated code updating operation of developers is reduced.
Page configuration tool: and dragging the visualization to perform page layout and configuration of the patterns through binding the metadata interface, completing the patterns of a webpage and the configuration submitted to a background process through the page event binding template, generating dynamic and static metadata of a page layer, storing the metadata into a database, and rendering the metadata and a front end frame to form a page during operation. The method and the system enable developers to easily modify page contents and realize quick iteration, meanwhile, the page layer can dynamically render pages when application services run based on metadata, the mobility of the metadata can support hot updating after page configuration, and configuration of the pages can take effect in real time.
The database tool is used for generating a database table structure, a table construction statement can be generated according to a table construction SQL template through metadata definition of a data model, the table construction statement is executed in a corresponding database to generate a table structure corresponding to metadata, the SQL template can form different templates according to different database types, and a required database can be selected to generate SQL corresponding to database grammar. Therefore, the data can be better managed and the data quality can be ensured, meanwhile, the low-code platform corresponding to the method supports various database development, a developer does not need to consider database compatibility when building a data model, and metadata and the low-code platform can automatically process the database compatibility problem.
In summary, the invention has the following beneficial effects: (1) And a low-code platform adopting a metadata architecture is constructed, a multidimensional metadata structure is constructed, complex logic can be supported, and development efficiency is improved. (2) And a metadata definition module, a metadata mapping module and a metadata verification module are arranged, metadata mapping is carried out through the metadata mapping module of the low-code platform in a data modeling stage to generate a back-end code, and the process of creating, combining and modifying an application program or service in the industrial low-code platform is simplified. (3) The metadata structure is divided into a model layer, a service layer and a page layer, metadata of different levels are used for different use scenes, and availability and readability of the metadata are improved.
Drawings
FIG. 1 is a block diagram of an industrial software low code platform according to an embodiment of the present invention.
FIG. 2 is a diagram of an industrial software low-code platform metadata architecture according to an embodiment of the present invention.
In the figure: 1. model layer 2, service layer 3, page layer.
Detailed Description
The invention is further described below with reference to the drawings and detailed description.
Examples:
the embodiment discloses an industrial software low-code platform and a metadata architecture thereof, as shown in fig. 1, a system architecture of the low-code platform includes: metadata definition module: for defining metadata types and attributes that can be used on industrial software low code platforms;
a metadata storage module: the metadata definition module is in communication connection with the metadata and is used for storing metadata types and attributes defined in the metadata definition module;
metadata mapping module: for mapping metadata to actual applications or services on the industrial software low code platform;
metadata verification module: the metadata verification module is used for verifying the matching between the metadata and the actual application program or service, and the metadata verification module is used for ensuring the accuracy of the metadata by comparing the matching between the metadata and the actual application program or service;
metadata update module: and the metadata definition module is in communication connection with the metadata definition module and is used for updating the metadata types and attributes defined in the metadata definition module according to the requirements.
Based on the system architecture of the low code platform, the process of creating, combining, and modifying applications or services is simplified while maintaining consistency and accuracy of metadata.
The metadata architecture comprises a model layer 1, a service layer 2 and a page layer 3, wherein the model layer 1 comprises a model, fields, relations and constraints, the model is used for describing organization and structure of data, the fields refer to data for describing field attributes in the model, and the field attribute data comprise names, types, lengths, whether filling is needed or not and the like. The model layer 1 metadata is used for data management, data verification, data conversion and other operations to ensure the correctness and consistency of the data. Metadata of the model fields are converted into POJO, controller, service and Dao metadata of the Service layer 2 through metadata of the model layer 1 in a metadata mapping module through metadata mapping.
Service layer 2 refers to a component in an application program for processing business logic, which is responsible for receiving a request, processing the request and returning a response, and the service layer 2 station comprises interface definition, business logic processing, data access and other parts. The metadata of the Service layer 2 is divided into two layers, wherein the first layer is POJO, controller, service and Dao metadata formed by mapping a data model, and the metadata of the POJO, controller, service and Dao are converted again in the Service layer 2 to convert the metadata of a Service application program interface (ServiceAPI) which can be called by the page layer 3 and a third party and a webAPI (web application program interface) into metadata structures.
The WebAPI, web application interface metadata structure, includes: the API is the name, version number, list of parameters, return type, request and response format, validation requirements of the application program interface. Metadata is provided in JSON format, has structure and functionality that assists developers in understanding APIs, and performs verification and inspection when writing client code. The metadata has the functions of scenes such as automatic document generation, API test, code generation and the like; the ServiceAPI, the service application interface metadata structure, contains information including: service name and version number, API endpoint URL and HTTP method, supported request and response data format, authentication and authorization mechanism, error handling mode, data type of request parameter and return value and its value range. Wherein the supported request and response data formats include JSON and XML. By defining the serviceAPI metadata structure, a developer can conveniently understand and use the serviceAPI, and the readability, maintainability and reusability of the API are improved.
The page layer 3 metadata structure is divided into static metadata and dynamic metadata, wherein the static metadata refers to components used for describing a user interface, including page layout, control, event and other elements, and the dynamic metadata refers to dynamic data except for liquid level layout, including dynamic data dictionary, authority information and the like.
By setting the metadata structure, firstly, a table structure of a low-code development platform for realizing service by configuring a data model through configuration model fields is provided, basic adding, deleting and checking code logic is generated, code generation of adding, deleting and checking is facilitated through the metadata structure of the service layer 2, and meanwhile, converted API metadata provides a structure with higher readability for front-end and third party calling.
The application of metadata support of the low-code platform provided by the embodiment comprises:
automatically generating codes: the low-code platform generates the codes of the application program through metadata and corresponding code generation templates by using the POJO, dao, service and Controller metadata of the Service layer 2, so that the development efficiency is improved, human errors are reduced, meanwhile, the logic complexity of a code generator is greatly reduced, and the automatic code generation efficiency is improved. The code generation template can be iteratively updated according to the subsequent requirement, the updated template can be combined with metadata to generate codes again, and the regenerated codes have new functions after template updating, so that repeated code updating operation of developers is reduced.
Page configuration: the method comprises the steps of providing a page configuration tool through service layer 2 structure metadata, carrying out page layout and configuration of patterns through dragging visualization through a binding metadata interface, completing the patterns of a webpage and the configuration submitted to a background process through a page event binding template, generating page layer 3 dynamic and static metadata, and rendering through metadata and a front end frame to form a page when running after the metadata are stored in a database. The method and the device enable developers to easily modify page content and realize quick iteration, meanwhile, the page layer 3 can dynamically render pages when application services run based on metadata, the mobility of the metadata can support the configuration of the pages, and the configuration of the pages can be realized in real time through hot updating.
Database design: the metadata of the data model layer 1 can also be used for generating a database table structure, a table construction statement can be generated according to a template by combining metadata definition of a data model with a table construction SQL template, the table construction statement is executed in a corresponding database to generate the table structure corresponding to the metadata, the SQL template can form different templates according to different database types, and a required database can be selected to generate SQL corresponding to database grammar. Therefore, the data can be better managed and the data quality can be ensured, meanwhile, the low-code platform corresponding to the method supports various database development, a developer does not need to consider database compatibility when building a data model, and metadata and the low-code platform can automatically process the database compatibility problem.
Maintenance and upgrade: the metadata records the configuration and the function of the service, so that the maintenance and the upgrade are easier and controllable, the upgrade of the public function only needs to upgrade the low-code platform or upgrade the metadata, and the complete metadata structure of the invention also supports the environment migration of the developed service without additional configuration.
The specific embodiments described herein are offered by way of example only to illustrate the spirit of the invention. Those skilled in the art may make various modifications or additions to the described embodiments or substitutions thereof without departing from the spirit of the invention or exceeding the scope of the invention as defined in the accompanying claims.
Although metadata, low code development platforms, model layers, service layers, page layers, and the like are used more herein, the possibility of using other terms is not precluded. These terms are used merely for convenience in describing and explaining the nature of the invention; they are to be interpreted as any additional limitation that is not inconsistent with the spirit of the present invention.
Claims (8)
1. An industrial software low code platform, wherein the low code platform comprises a metadata definition module: defining metadata types and attributes; metadata mapping module: mapping metadata into an actual application or service on the industrial software low-code platform; metadata verification module: and verifying the matching between the metadata and the actual application program or service.
2. The industrial software low-code platform of claim 1, further comprising a metadata storage module communicatively coupled to the metadata definition module, the metadata storage module storing metadata types and attributes defined in the metadata definition module.
3. The industrial software low-code platform of claim 2, wherein the metadata verification module obtains the accuracy of the metadata by comparing the matching between the metadata and the actual application or service.
4. The industrial software low-code platform of claim 3, further comprising a metadata update module communicatively coupled to the metadata definition module, the metadata update module updating metadata types and attributes defined in the metadata definition module.
5. A metadata architecture for an industrial software low code platform, the application being with the industrial software low code platform of any one of claims 1-4, comprising: the first metadata of the model layer is converted into second metadata of the service layer through the metadata mapping module, and the second metadata of the service layer is converted into third metadata of the page layer through the metadata mapping module.
6. The metadata architecture for an industrial software low-code platform of claim 5, wherein the model layer: describing the organization and architecture of metadata; the service layer: the system comprises a component for processing business logic in an application program, and has the functions of receiving a request, processing the request and returning a response; the page layer: including static metadata: describing a user interface; the dynamic metadata includes dynamic data dictionary and rights information.
7. The metadata architecture for an industrial software low-code platform of claim 6, wherein the third metadata comprises service application interface metadata and web application interface metadata, the application interface metadata format comprising JSON format; the format of the metadata of the application program interface comprises JSON and XML formats.
8. The metadata architecture for an industrial software low-code platform of claim 5, 6 or 7, wherein the service layer comprises code generation templates and page configuration tools, and wherein the model layer comprises database tools.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311016108.5A CN117111935A (en) | 2023-08-14 | 2023-08-14 | Industrial software low-code platform and metadata architecture thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311016108.5A CN117111935A (en) | 2023-08-14 | 2023-08-14 | Industrial software low-code platform and metadata architecture thereof |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117111935A true CN117111935A (en) | 2023-11-24 |
Family
ID=88812032
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311016108.5A Pending CN117111935A (en) | 2023-08-14 | 2023-08-14 | Industrial software low-code platform and metadata architecture thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117111935A (en) |
-
2023
- 2023-08-14 CN CN202311016108.5A patent/CN117111935A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110825362B (en) | Low-code application software development system and method | |
| US7424485B2 (en) | Method and apparatus for generating user interfaces based upon automation with full flexibility | |
| US9465590B2 (en) | Code generation framework for application program interface for model | |
| US7047518B2 (en) | System for software application development and modeling | |
| US8448132B2 (en) | Systems and methods for modifying code generation templates | |
| US7363578B2 (en) | Method and apparatus for mapping a data model to a user interface model | |
| CN103383645A (en) | Code generation method and system | |
| CN111784108B (en) | Modeling method and device of main data management platform | |
| US20060026506A1 (en) | Test display module for testing application logic independent of specific user interface platforms | |
| CN111125064B (en) | Method and device for generating database schema definition statement | |
| JP2018514878A (en) | A computer-implemented method for displaying software-type applications based on design specifications | |
| CN111581920A (en) | Document conversion method, device, equipment and computer storage medium | |
| CN112506505A (en) | Method for producing program code by code template engine | |
| CN112463135A (en) | Code generation method, code generator, electronic device, and storage medium | |
| EP2610740A1 (en) | Declarative View Objects | |
| CN112083919A (en) | YAML template-based target service code generation method and device | |
| US20100088671A1 (en) | Project scopes for configuration based computer application projects | |
| CN116755669A (en) | Low code development method and tool based on DSL language operation model | |
| EP3005087A1 (en) | Declarative configuration elements | |
| D'Ambrogio et al. | A MDA-based approach for the development of DEVS/SOA simulations | |
| US11977473B2 (en) | Providing a pseudo language for manipulating complex variables of an orchestration flow | |
| CN101055521B (en) | Mapping rule visualized generation method and system | |
| CN117111935A (en) | Industrial software low-code platform and metadata architecture thereof | |
| CN115599361A (en) | Software development method, device, equipment and medium | |
| CN114692055A (en) | Form processing method and device, storage medium and electronic equipment |
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 |