Development method and device of low-code platform, electronic equipment and storage medium

Abstract

The invention provides a development method and device of a low-code platform, electronic equipment and a storage medium. The low-code platform provides an interactive interface. The method comprises the steps that development demand information input by a user is received, and a development component library conforming to the development demand information is displayed on an interactive interface; in response to a dragging operation for the development component library, determining a target component selected by a user; creating a business model by using a full-stack business model architecture based on the target component; and generating a project file of the business code according to the business model, and generating an application system based on the project file of the business code. Therefore, according to the development demand information input by the user and the dragging operation on the component, the service model conforming to the development demand can be created by using the full-stack model architecture constructed in the low-code platform, and then the application system is developed by the model-driven low-code platform. Therefore, the purposes of quickly developing the application system and improving the development efficiency can be achieved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a development method, device, electronic device and storage medium for a low-code platform. Background Art

[0002] Low-code development is a rapid development method that allows developers to quickly complete application software development using very little or even zero code. Low-code development platforms are mostly based on classic model-driven architectures. The richness and completeness of the model are a concentrated reflection of the core capabilities of a low-code development platform, such as abstract modeling and rapid development. However, the modeling process in existing low-code development platforms is complex, and the model building system is imperfect, resulting in high learning costs and learning barriers for users to use low-code development platforms, and low development efficiency. Summary of the invention

[0003] In view of this, the purpose of this application is to provide a development method, device, electronic device and storage medium of a low-code platform, which can use the full-stack model architecture built in the low-code platform to create a business model that meets the development requirements based on the development requirement information input by the user and the drag and drop operation of the components, and then develop an application system by the model-driven low-code platform. In this way, the purpose of quickly developing an application system and improving development efficiency can be achieved.

[0004] The embodiment of the present application provides a development method of a low-code platform, wherein the low-code platform provides an interactive interface; the development method includes:

[0005] Receiving development requirement information input by a user, and displaying a development component library that matches the development requirement information on the interactive interface;

[0006] In response to a drag operation on the development component library, determining a target component selected by a user;

[0007] Based on the target component, a business model is created using a full-stack business model architecture; wherein the full-stack business model architecture is a four-layer metamodel architecture, including a meta-metamodel layer, a metamodel layer, a model layer, and an object layer;

[0008] Generate a project file of the business code according to the business model, and generate an application system based on the project file of the business code.

[0009] Furthermore, the meta-metamodel layer is used to describe the common grammatical definitions of basic semantic elements in each metamodel;

[0010] The metamodels included in the metamodel layer are instances of concepts in the meta-metamodel layer, and are pre-created based on the meta-metamodels in the meta-metamodel layer as standards;

[0011] The models included in the model layer are instances of concepts in the metamodel layer, and are pre-developed according to business domains based on the metamodels in the metamodel layer;

[0012] The object layer is a data structure obtained by instantiating the model included in the model layer.

[0013] Furthermore, there is a mapping relationship between the components in the development component library and the models in the model layer; based on the target component, a business model is created using a full-stack business model architecture, including:

[0014] Based on the target component and the mapping relationship, retrieve the target original model corresponding to the target component from the model layer;

[0015] In response to the configuration operation on the target component, determining business data related to the target component;

[0016] At the object layer, the target original model is instantiated according to the business data related to the target component and / or the business data pre-configured in the full-stack business model architecture to integrate and obtain the business model.

[0017] Further, receiving development requirement information input by a user, and displaying a development component library that matches the development requirement information on the interactive interface, including:

[0018] Receive business domain labels input by users;

[0019] Filtering candidate models corresponding to the business domain labels from the model layer;

[0020] The components corresponding to the candidate models are displayed in the development component library of the interactive interface.

[0021] Further, the generating of the engineering file of the business code according to the business model, and generating the application system based on the engineering file of the business code, includes:

[0022] Convert the business model into a DSL engineering file of business code;

[0023] Call the DSL parser to parse the DSL project file into components;

[0024] For the parsed target component, the component service and the runtime frame and operation framework supporting the model operation are called as dependencies to generate the application system.

[0025] The embodiment of the present application also provides a development device of a low-code platform, wherein the low-code platform provides an interactive interface; the development device includes:

[0026] A receiving module, used to receive development requirement information input by a user, and display a development component library that matches the development requirement information on the interactive interface;

[0027] A determination module, configured to determine a target component selected by a user in response to a drag operation on the development component library;

[0028] A creation module, used to create a business model based on the target component using a full-stack business model architecture; wherein the full-stack business model architecture is a four-layer metamodel architecture; the full-stack business model architecture includes a meta-metamodel layer, a metamodel layer, a model layer, and an object layer;

[0029] A generation module is used to generate an engineering file of a business code according to the business model, and to generate an application system based on the engineering file of the business code.

[0030] Furthermore, the meta-metamodel layer is used to describe the common grammatical definitions of basic semantic elements in each metamodel;

[0031] The metamodels included in the metamodel layer are instances of concepts in the meta-metamodel layer, and are pre-created based on the meta-metamodels in the meta-metamodel layer as standards;

[0032] The models included in the model layer are instances of concepts in the metamodel layer, and are pre-developed according to business domains based on the metamodels in the metamodel layer;

[0033] The object layer is a data structure obtained by instantiating the model included in the model layer.

[0034] Furthermore, there is a mapping relationship between the components in the development component library and the models in the model layer; when the creation module is used to create a business model based on the target component using the full-stack business model architecture, the creation module is used to:

[0035] Based on the target component and the mapping relationship, retrieve the target original model corresponding to the target component from the model layer;

[0036] In response to the configuration operation on the target component, determining business data related to the target component;

[0037] At the object layer, the target original model is instantiated according to the business data related to the target component and / or the business data pre-configured in the full-stack business model architecture to integrate and obtain the business model.

[0038] An embodiment of the present application also provides an electronic device, including: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the memory communicate through the bus, and when the machine-readable instructions are executed by the processor, the steps of a low-code platform development method as described above are performed.

[0039] An embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of a low-code platform development method as described above are executed.

[0040] The embodiments of the present application provide a method, device, electronic device and storage medium for developing a low-code platform, which determines a business model that meets the development requirements through a full-stack model architecture built in the low-code platform, and then develops an application system through the model-driven low-code platform. In this way, the purpose of rapidly developing an application system can be achieved.

[0041] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0043] Figure 1 A flowchart of a method for developing a low-code platform provided in an embodiment of the present application is shown;

[0044] Figure 2 A schematic diagram of a full-stack business model architecture provided by an embodiment of the present application is shown;

[0045] Figure 3 A schematic diagram showing a process of generating an application system provided in an embodiment of the present application;

[0046] Figure 4 A schematic diagram of a method for developing a low-code platform provided in an embodiment of the present application is shown;

[0047] Figure 5 A schematic diagram of the structure of a low-code platform development device provided in an embodiment of the present application is shown;

[0048] Figure 6A schematic structural diagram of an electronic device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0049] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application usually described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, each other embodiment obtained by those skilled in the art without making creative work belongs to the scope of protection of the present application.

[0050] Research has found that low-code development is a rapid development method that allows developers to quickly complete application software development using very little or even zero code. Low-code development platforms are mostly based on classic model-driven architectures. The richness and completeness of the model are a concentrated reflection of the core capabilities of a low-code development platform, such as abstract modeling and rapid development. However, the modeling process in existing low-code development platforms is complex, and the model building system is imperfect, resulting in high learning costs and learning barriers for users to use low-code development platforms, and low development efficiency.

[0051] Based on this, the embodiments of the present application provide a method, device, electronic device and storage medium for developing a low-code platform, which can use the full-stack model architecture built in the low-code platform to create a business model that meets the development requirements based on the development requirement information input by the user and the drag and drop operation of the components, and then develop an application system by the model-driven low-code platform. In this way, the purpose of quickly developing an application system and improving development efficiency can be achieved.

[0052] The model in the embodiment of the present application is a reusable business model that is formed by abstracting and precipitating the description definitions of the user interface, interface flow, business components, data entity access, etc. required for the operation of the application software system. In the low-code modeling system, the model is also called metadata.

[0053] See also Figure 1 , Figure 1 A flowchart of a method for developing a low-code platform provided in an embodiment of the present application. Here, the low-code platform can provide a visual interactive interface to interact with the user, receive information input by the user through the visual interface, and display graphical components and models to the user; Figure 1As shown in, the development method provided in the embodiment of the present application includes:

[0054] S101, receiving development requirement information input by a user, and displaying a development component library that matches the development requirement information on the interactive interface.

[0055] Here, the development requirement information indicates information about the business model that the user expects to create and information about the application system to be developed, such as indicating the business domain to which the business model is applicable, and the application scenarios and architecture requirements to which the application system is applicable.

[0056] S102: In response to a drag operation on the development component library, determine a target component selected by a user.

[0057] In this step, the interactive interface may display a development component library and an editing canvas; a component list is displayed in the development component library; and the user may select a target component by dragging a component in the component list of the development component library to the editing canvas.

[0058] S103. Based on the target component, create a business model using a full-stack business model architecture.

[0059] In terms of specific implementation, the low-code development platform includes a modeling standard (UIML-Standard) that is independent of the development language, a basic framework (CAF-Framework) for developing microservice applications, a built-in full-stack business model (UIML-Models) based on the UIML standard, and provides development services and kits (UIML-SDK) that can interact with the model throughout its life cycle, as well as a runtime framework (UIML-Runtime) that supports model operation.

[0060] Among them, the development service and kit (UIML-SDK) receives the development requirement information input by the user, and interacts with the full-stack business model (UIML-Models) to build the business model according to the specific modeling standard (UIML-Standard).

[0061] See also Figure 2 , Figure 2 A schematic diagram of a full-stack business model architecture provided by an embodiment of the present application. Figure 2 As shown in , the full-stack business model architecture is a four-layer metamodel architecture, including a meta-metamodel layer, a metamodel layer, a model layer, and an object layer. This is the core mechanism of UIML domain modeling, has perfect self-description capabilities, and has good openness and extensibility.

[0062] Among them, the meta-metamodel layer is used to describe the common grammatical definition of basic semantic elements in each metamodel. The meta-metamodel is the schema of the metamodel, the most basic element in UIML, and the architectural basis of the UIML standard; the metamodel included in the metamodel layer is an instance of the concept in the meta-metamodel layer, and is also the schema of the model, which is pre-created based on the meta-metamodel in the meta-metamodel layer as the standard; the model included in the model layer is an instance of the concept in the metamodel layer, which is pre-developed according to the business field based on the metamodel in the metamodel layer, and is also the schema of the object; the object layer is a data structure obtained by instantiating the model included in the model layer, that is, the real data when the program is running, and the instantiation process is realized through runtime assignment.

[0063] In a possible implementation, there is a mapping relationship between the components in the development component library and the models in the model layer; step S103 may include:

[0064] Based on the target component and the mapping relationship, the target original model corresponding to the target component is retrieved from the model layer; in response to the configuration operation on the target component, the business data related to the target component is determined; at the object layer, the target original model is instantiated according to the business data related to the target component and / or the business data pre-configured in the full-stack business model architecture, and the business model is integrated.

[0065] In addition, the newly created business model can also be stored in the full-stack business model architecture for quick call next time.

[0066] Accordingly, because the models in the model layer are pre-developed according to the business domain, in a possible implementation, step S101 may include:

[0067] Receive a business domain label input by a user; filter out candidate models corresponding to the business domain label from the model layer; and display components corresponding to the candidate models in the development component library of the interactive interface.

[0068] In this way, users can quickly find candidate models that match their business domain to improve development efficiency.

[0069] The following is an example to illustrate the full-stack business model architecture.

[0070] Taking the BusinessEntity metamodel as an example, the corresponding meta-metamodel is the Schema of BusinessEntity, the corresponding model is SalesOrder.be&&SalesOrder.java / SalesOrder.cs, and the corresponding object is SalesOrder.getFirstRow().

[0071] The common syntax definition that describes all types of metamodels (such as BusinessEntity) is the meta-metamodel: the meta-metamodel breaks down the structure and capabilities of the metamodel, deconstructs and describes it in a fine-grained manner, and forms basic semantic elements. Taking the "field" structure in the BE "metamodel" as an example, the "meta-metamodel" provides the ability to describe the "field" structure, such as limiting which elements and attributes can be used to describe a "field" (Element and Attribute are taken from the concepts of "node" and "attribute" in XSD)

[0072] BusinessEntity is a metamodel: the metamodel uses the meta-metamodel to provide the "ability to describe the field structure" to describe the "field", that is, it defines what a field is. For example, "BE field" is derived from Property (Property is a basic semantic element node in Common-Core, an Element), and a Property is implemented in the BE metamodel. BE can also add some extended information of its own BE field based on the Property, such as "whether the field enables the default value, whether the field is referenced, whether the field enables internationalization", etc. These extended information are also described by basic semantic elements such as "Attribute" and "PrimitiveType" in the meta-metamodel.

[0073] SalesOrder.be&&SalesOrder.java / SalesOrder.cs is a model: a model is an instance of a metamodel. The "field list" in SalesOrder.be uses the structured "field" template provided by the metamodel BE. In a specific "sales order" business scenario, a specific field list is instantiated. For example, SalesOrder.be contains three actual fields: "Id, Code, Description". This process is the process of instantiating and assigning values ​​to the "field" (actually "field list") structure in the BE metamodel.

[0074] SalesOrder.getFirstRow() is an object: Based on the above content, the "model" defines how many specific fields the entity in SalesOrder.be can have, and the "object" can be understood as follows: the model defines the class structure of the SalesOrder entity, and the object is based on the class structure provided by the model, and performs the actual "class instantiation" operation on the entity class of the specific programming language SalesOrder.Java / cs, that is, according to the class "SalesOrder", "New" a SalesOrder memory instance is created, and the Id, Code, Description and other fields in SalesOrder.be have actual values ​​through this process.

[0075] It should be noted that the relationship between a model and the code generated by the model is not the relationship between a model and an object. For example, SalesOrder.be is a DSL description of a sales order, and SalesOrder.java / cs is a Java / C# or other high-level programming language description of a sales order. When converting from DSL to Java / C#, only the description form of the "sales order" changes, and the instantiation process (actual assignment) of SalesOrder.be does not occur. Therefore, the process of generating code from the model does not convert the "model" into a real "object".

[0076] S103: Generate an engineering file of the business code according to the business model, and generate an application system based on the process file of the business code.

[0077] The application system provided in the embodiment of the present application includes: a presentation layer, a business logic layer and a data access layer; the presentation layer provides functional processing related to interactive users and external system interfaces, the business layer provides the core functions of various business logic implementations of the system, and the data layer provides data persistence access related functions required by the business layer. In order to support more complex functions, the above three large logical levels are subdivided into responsibilities to support software quality indicators such as maintainability and scalability during the development and operation of large systems. Therefore, the presentation layer includes the UI layer and the BFF layer; the business logic layer includes: the API layer, the business process layer and the domain service layer; the data access layer refers to the data storage layer.

[0078] Based on the logical hierarchical division of the above application system, the application system is abstracted to form various metadata running in the full-stack business model architecture.

[0079] In specific implementation, step S104 may include: converting the business model into a DSL project file of business code; calling a DSL parser to perform component parsing on the DSL project file, and finally outputting it in the form of a JSON file; for the parsed target component, calling runtime data services, such as component services and a runtime frame (UIML-Runtime) and an operating framework (Spring Boot) supporting the model operation as dependencies, to generate the application system.

[0080] See also Figure 3 , Figure 3 This is a schematic diagram of the process of generating an application system provided in an embodiment of the present application. Figure 3 As shown in the figure, during the design, the created business model (model) is packaged to generate a model package, the business model generates business code (generated code), and the business code is compiled to obtain a source code package (program package); for the parsed target component, the component service is called, and the runtime frame and operation framework supporting the model operation are used as dependencies. Based on the source code package and model package, an application system including UI, Restful Api, Business logic and Datapersistence is generated.

[0081] See also Figure 4 , Figure 4 A schematic diagram of a method for developing a low-code platform provided in an embodiment of the present application. Figure 4 As shown in , users send development requirement information to the low-code platform; development services and suites retrieve or create business models based on the development requirement information and modeling standards; business code is generated according to the business model, and the application system is generated based on the runtime frame and operation framework.

[0082] In this way, based on the development requirement information input by the user and the drag-and-drop operation of the components, the full-stack model architecture built in the low-code platform can be used to create a business model that meets the development requirements, and then the application system can be developed by the model-driven low-code platform. In this way, the purpose of quickly developing the application system and improving development efficiency can be achieved.

[0083] See also Figure 5 , Figure 5 This is a schematic diagram of a low-code platform development device provided in an embodiment of the present application. Figure 5 As shown in , the low-code platform provides an interactive interface; the development device 500 includes:

[0084] The receiving module 510 is used to receive development requirement information input by a user, and display a development component library that matches the development requirement information on the interactive interface;

[0085] A determination module 520, configured to determine a target component selected by a user in response to a drag operation on the development component library;

[0086] A creation module 530 is used to create a business model based on the target component using a full-stack business model architecture; wherein the full-stack business model architecture is a four-layer metamodel architecture; the full-stack business model architecture includes a meta-metamodel layer, a metamodel layer, a model layer, and an object layer;

[0087] The generation module 540 is used to generate a project file of a business code according to the business model, and generate an application system based on the project file of the business code.

[0088] Furthermore, the meta-metamodel layer is used to describe the common grammatical definitions of basic semantic elements in each metamodel;

[0089] The metamodels included in the metamodel layer are instances of concepts in the meta-metamodel layer, and are pre-created based on the meta-metamodels in the meta-metamodel layer as standards;

[0090] The models included in the model layer are instances of concepts in the metamodel layer, and are pre-developed according to business domains based on the metamodels in the metamodel layer;

[0091] The object layer is a data structure obtained by instantiating the model included in the model layer.

[0092] Further, there is a mapping relationship between the components in the development component library and the models in the model layer; when the creation module 530 is used to create a business model based on the target component using the full-stack business model architecture, the creation module 530 is used to:

[0093] Based on the target component and the mapping relationship, retrieve the target original model corresponding to the target component from the model layer;

[0094] In response to the configuration operation on the target component, determining business data related to the target component;

[0095] At the object layer, the target original model is instantiated according to the business data related to the target component and / or the business data pre-configured in the full-stack business model architecture to integrate and obtain the business model.

[0096] Furthermore, the receiving module 510 is used to receive development requirement information input by a user, and to display a development component library that matches the development requirement information on the interactive interface. The receiving module 510 is used to:

[0097] Receive business domain labels input by users;

[0098] Filtering candidate models corresponding to the business domain labels from the model layer;

[0099] The components corresponding to the candidate models are displayed in the development component library of the interactive interface.

[0100] Furthermore, when the generating module 540 is used to generate a project file of a business code according to the business model and to generate an application system based on the project file of the business code, the generating module 540 is used to:

[0101] Convert the business model into a DSL engineering file of business code;

[0102] Call the DSL parser to parse the DSL project file into components;

[0103] For the parsed target component, the component service and the runtime frame and operation framework supporting the model operation are called as dependencies to generate the application system.

[0104] See also Figure 6 , Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 6 As shown in , the electronic device 700 includes a processor 710 , a memory 720 and a bus 730 .

[0105] The memory 720 stores machine-readable instructions executable by the processor 710. When the electronic device 700 is running, the processor 710 communicates with the memory 720 via the bus 730. When the machine-readable instructions are executed by the processor 710, the above-mentioned Figure 1 The steps of a method for developing a low-code platform in the method embodiment shown, the specific implementation method can be found in the method embodiment, and will not be repeated here.

[0106] The present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the computer program can execute the above-mentioned Figure 1 The steps of a method for developing a low-code platform in the method embodiment shown, the specific implementation method can be found in the method embodiment, and will not be repeated here.

[0107] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0108] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of devices or units can be electrical, mechanical or other forms.

[0109] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0110] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0111] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present application can essentially be embodied in the form of a software product, or in other words, the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0112] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solutions of the present application, rather than to limit them. The protection scope of the present application is not limited thereto. Although the present application is described in detail with reference to the above-mentioned embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-mentioned embodiments within the technical scope disclosed in the present application, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A method for developing a low-code platform, characterized in that: The low-code platform provides an interactive interface; The development method comprises: Receiving development requirement information input by a user, and displaying a development component library that matches the development requirement information on the interactive interface; In response to a drag operation on the development component library, determining a target component selected by a user; Based on the target component, a business model is created using a full-stack business model architecture; wherein the full-stack business model architecture is a four-layer metamodel architecture, including a meta-metamodel layer, a metamodel layer, a model layer, and an object layer; Generate a project file of the business code according to the business model, and generate an application system based on the project file of the business code.

2. The development method according to claim 1, characterized in that: The meta-metamodel layer is used to describe the common grammatical definitions of basic semantic elements in each metamodel; The metamodels included in the metamodel layer are instances of concepts in the meta-metamodel layer, and are pre-created based on the meta-metamodels in the meta-metamodel layer as standards; The models included in the model layer are instances of concepts in the metamodel layer, and are pre-developed according to business domains based on the metamodels in the metamodel layer; The object layer is a data structure obtained by instantiating the model included in the model layer.

3. The development method according to claim 2, characterized in that: There is a mapping relationship between the components in the development component library and the models in the model layer; based on the target component, a business model is created using a full-stack business model architecture, including: Based on the target component and the mapping relationship, retrieve the target original model corresponding to the target component from the model layer; In response to the configuration operation on the target component, determining business data related to the target component; At the object layer, the target original model is instantiated according to the business data related to the target component and / or the business data pre-configured in the full-stack business model architecture to integrate and obtain the business model.

4. The development method according to claim 3, characterized in that: Receiving development requirement information input by a user, and displaying a development component library that matches the development requirement information on the interactive interface, including: Receive business domain labels input by users; Filtering candidate models corresponding to the business domain labels from the model layer; The components corresponding to the candidate models are displayed in the development component library of the interactive interface.

5. The development method according to claim 1, characterized in that: The step of generating a project file of a business code according to the business model, and generating an application system based on the project file of the business code includes: Convert the business model into a DSL engineering file of business code; Call the DSL parser to parse the DSL project file into components; For the parsed target component, the component service and the runtime frame and operation framework supporting the model operation are called as dependencies to generate the application system.

6. A development device for a low-code platform, characterized in that: The low-code platform provides an interactive interface; The development device comprises: A receiving module, used to receive development requirement information input by a user, and display a development component library that matches the development requirement information on the interactive interface; A determination module, configured to determine a target component selected by a user in response to a drag operation on the development component library; A creation module, used to create a business model based on the target component using a full-stack business model architecture; wherein the full-stack business model architecture is a four-layer metamodel architecture; the full-stack business model architecture includes a meta-metamodel layer, a metamodel layer, a model layer, and an object layer; A generation module is used to generate an engineering file of a business code according to the business model, and to generate an application system based on the engineering file of the business code.

7. The development device according to claim 6, characterized in that: The meta-metamodel layer is used to describe the common grammatical definitions of basic semantic elements in each metamodel; The metamodels included in the metamodel layer are instances of concepts in the meta-metamodel layer, and are pre-created based on the meta-metamodels in the meta-metamodel layer as standards; The models included in the model layer are instances of concepts in the metamodel layer, and are pre-developed according to business domains based on the metamodels in the metamodel layer; The object layer is a data structure obtained by instantiating the model included in the model layer.

8. The development device according to claim 7, characterized in that: There is a mapping relationship between the components in the development component library and the models in the model layer; when the creation module is used to create a business model based on the target component using the full-stack business model architecture, the creation module is used to: Based on the target component and the mapping relationship, retrieve the target original model corresponding to the target component from the model layer; In response to the configuration operation on the target component, determining business data related to the target component; At the object layer, the target original model is instantiated according to the business data related to the target component and / or the business data pre-configured in the full-stack business model architecture to integrate and obtain the business model.

9. An electronic device, characterized in that: include: A processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor and the memory communicate through the bus. When the processor is running, the machine-readable instructions are executed according to the steps of a method for developing a low-code platform as described in any one of claims 1 to 5.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of a method for developing a low-code platform as described in any one of claims 1 to 5 are executed.

Images