An automated development method based on design model for low-code development platform

Abstract

The present invention provides an automated development method for a low-code development platform based on a design model, and relates to the field of enterprise management software development. The method comprises step 1: performing UI design, rule design and entity design, and generating a UI model, a rule model and an entity model based on the UI design, rule design and entity design configuration; step 2: automatically completing the mapping configuration of a UI model adapter, a rule model adapter and an entity model adapter based on the UI model, the rule model and the entity model; step 3: automatically creating a component element file of a corresponding low-code platform based on the UI model adapter, the rule model adapter and the entity model adapter, thereby completing the automated development of software system functions. The present invention is based on a standardized design model, combined with a low-code development platform / no-code development platform, to realize the automated development of basic functions and common functions of a software system.

Description

Technical Field

[0001] The present invention relates to the field of enterprise management software development, and in particular to an automated development method based on a design model for a low-code development platform. Background Art

[0002] At present, the customized development links of enterprise management software systems mainly include: demand analysis, system analysis, system design, system development, system testing, and system deployment; among them, the link from system design to system development is mainly achieved through the interpretation and identification of design documents by program developers, and is implemented in two ways: one is to implement software system functions through program coding; the other is to implement software functions on a low-code development platform (or partially codeless development platform).

[0003] The two existing methods have the following defects:

[0004] 1. System design to system development is greatly affected by the personal understanding, technology, and skills of the programmers. It also consumes a lot of time and manpower. In addition, when faced with changing requirements, iterative modifications are costly and prone to errors.

[0005] 2. The emergence of low-code development platforms has alleviated the above problems to a certain extent, but low-code / no-code development platforms still require manual labor such as dragging and dropping and configuration to complete the system design functions, which still consumes a lot of time and manpower. In addition, when faced with changes in requirements, there are also problems such as high modification costs and easy errors. Please refer to Figure 1 . Summary of the invention

[0006] In view of the shortcomings of the prior art mentioned above, the purpose of the present invention is to provide an automated development method based on a design model for a low-code development platform, based on a standardized design model, combined with a low-code development platform / no-code development platform, to achieve automated development of basic functions and common functions of the software system.

[0007] The present invention provides an automated development method for a low-code development platform based on a design model, the method comprising the following steps:

[0008] Step 1: Perform UI design, rule design and entity design, and generate UI model, rule model and entity model based on the UI design, rule design and entity design configuration;

[0009] Step 2: Automatically complete the mapping configuration of the UI model adapter, the rule model adapter, and the entity model adapter based on the UI model, the rule model, and the entity model;

[0010] Step 3: Automatically create the corresponding low-code platform component element files based on the UI model adapter, rule model adapter, and entity model adapter to complete the automated development of software system functions.

[0011] In one embodiment of the present invention, the component elements of the UI design include a form, a list, a calendar, and a tree structure.

[0012] In one embodiment of the present invention, the rule design includes front-end rule design and back-end rule design, and the component elements of the front-end rules and back-end rules respectively include verification rules, calculation rules, control rules and event triggering rules.

[0013] In one embodiment of the present invention, the component elements of the physical design include data tables and files.

[0014] In one embodiment of the present invention, the mapping configuration of the UI model adapter is to adapt the component elements of the UI design to the component elements of the corresponding low-code platform.

[0015] In one embodiment of the present invention, the mapping configuration of the rule model adapter is to adapt the component elements of the rule design to the component elements of the corresponding low-code platform.

[0016] In one embodiment of the present invention, the mapping configuration of the entity model adapter is to adapt the component elements of the entity design to the component elements of the corresponding low-code platform.

[0017] As described above, the automated development method for a low-code development platform based on a design model of the present invention has the following beneficial effects:

[0018] 1. Since low-code development platforms are gradually being adopted by various organizations, unlike traditional coding methods, low-code development platforms have componentized and objectified the component elements of software functions, and their abstraction level is much higher than the coding method. The present invention realizes the automated development of basic functions and common functions of software systems based on low-code development platforms.

[0019] 2. Although the components of different low-code development platforms are different, the elements that make up the system are limited, so you only need to define different model adapters for different low-code development platforms.

[0020] 3. The core difference between the present invention and the existing development model is that the present invention can automatically reconstruct functions when development is automated and changes are needed, rather than modifying functions. Therefore, it can greatly reduce development costs, improve development efficiency, and reduce human error rates and development and change costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1Shown is a development flow chart of an enterprise management software system disclosed in the prior art.

[0022] Figure 2 Shown is a development flow chart of the enterprise management software system disclosed in an embodiment of the present invention.

[0023] Figure 3 Shown as disclosed in the embodiments of the present invention Figure 2 The workflow diagram of B-2.

[0024] Figure 4 Shown is a schematic diagram of the "place order" function disclosed in an embodiment of the present invention.

[0025] Figure 5 Shown is a component element analysis diagram corresponding to the "place order" function disclosed in an embodiment of the present invention.

[0026] Figure 6 Shown is a development flow chart of the "place order" function disclosed in an embodiment of the present invention. DETAILED DESCRIPTION

[0027] The following describes the embodiments of the present invention by specific examples, and those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict.

[0028] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present invention, and thus the drawings only show components related to the present invention rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0029] See also Figure 2 The present invention provides an automated development method for a low-code development platform based on a design model, the method comprising the following steps:

[0030] Step 1: Perform UI design, rule design and entity design, and generate UI model, rule model and entity model based on the UI design, rule design and entity design configuration;

[0031] After manual demand analysis, system analysis, and system design, a series of software system functions will be obtained. These software functions need to be defined by component elements, mainly including UI design, rule design, and entity design;

[0032] Among them, the component elements of the UI design include forms, lists, calendars, and tree structures; the rule design includes front-end rule design and back-end rule design, and the component elements of the front-end rules and back-end rules include verification rules, calculation rules, control rules, and event triggering rules respectively; the component elements of the entity design include data tables and files.

[0033] Specifically, UI design, rule design, and entity design are interrelated. UI design is the way entity design is expressed on the user side. Its expression logic is controlled by rule design, and under the control of rule design, the user-side operation information is persisted to the database. Generally, each component element of UI design has a corresponding component element of entity design.

[0034] The front-end rule design also constrains the user's behavior based on the UI design. For example, the front-end verification rule design constrains the user's data access. The front-end verification rule design can also assist the user to complete some automation functions. For example, the front-end rule design can assist the user to automatically and instantly display the calculation results after entering some content, or automatically obtain some real-time data, etc.

[0035] After the user completes the front-end operations, the back-end rule design can complete the corresponding verification, calculation, control and event processing through the system. For example, the information submitted by the user can be recorded in the component elements of the entity design (data persistence). Generally, the component elements of the back-end rule design are related to the component elements of the entity design, that is, the component elements of the back-end rule design are based on the component elements of the entity design.

[0036] Step 2: Automatically complete the mapping configuration of UI model adapter, rule model adapter and entity model adapter based on UI model, rule model and entity model. Figure 3 ;

[0037] Among them, the mapping configuration of the UI model adapter is to adapt the component elements of the UI design to the component elements of the corresponding low-code platform; the mapping configuration of the rule model adapter is to adapt the component elements of the rule design to the component elements of the corresponding low-code platform; the mapping configuration of the entity model adapter is to adapt the component elements of the entity design to the component elements of the corresponding low-code platform.

[0038] Step 3: Automatically create the corresponding low-code platform component element files based on the UI model adapter, rule model adapter, and entity model adapter to complete the software system function development.

[0039] That is, after automatically completing the mapping configuration of the UI model adapter, rule model adapter and entity model adapter, all component elements of UI design, rule design and entity design are described in accordance with the component element description method of the corresponding low-code development platform to form corresponding component element files. For example: if the component element of the low-code development platform is a JSON file, then the corresponding JSON file is formed according to the low-code development platform specifications; therefore, you only need to automatically create the JSON file according to the low-code development platform specifications and deploy the JSON file to the low-code development platform, and the software functions of the low-code development platform can be automatically created successfully.

[0040] See also Figure 4 The present invention takes the salesperson's "order placement" function as an example to illustrate the method of the present invention:

[0041] (1) Please refer to Figure 5 After manual demand analysis, system analysis, and system design, we obtain the UI design component elements (order entry form, order query list), rule design component elements (customer verification, automatic amount calculation, email notification after submission, etc.), and entity design component elements (customer table, product table, order table, order details table) required for the "place order" function. We also conduct UI analysis, rule analysis, and entity analysis based on the component elements to obtain the UI model, rule model, and entity model.

[0042] (2) Taking the open source low-code development platform JOGET DX as an example, the software system component elements of the low-code development platform JOGET DX include forms, lists, processes, and user interfaces, and the component elements are all defined in the form of JSON files;

[0043] (3) According to the UI model adapter, rule model adapter and entity model adapter of the low-code development platform JOGET DX, the customer form, product form, order entry function form, order query list and corresponding user interface menu elements required for the "place order" function are automatically created in accordance with the platform specifications of the low-code development platform JOGET DX;

[0044] (4) Order entry form, based on the customer's verification rules and email notification rules, adds the JSON attributes of the drop-down option component and the email tool attributes after the form is submitted; at this point, the function development of the order placement function in the software system on the low-code development platform JOGET DX is completed.

[0045] See also Figure 6 On the left are the component elements of the UI design, entity design, and rule design of the "Place Order" function. In the middle is the automatically generated JSON file. On the right are the component elements of the low-code development platform JOGET DX.

[0046] If the business requirements are adjusted, such as adding a new field and verification rules for the field in an order, you only need to add fields to the relevant entity design, add fields to the UI design, and add a new verification rule design, and then re-run the automated development process to complete the update; therefore, the present invention is essentially different from traditional development. In the traditional development model, if there are changes, adjustments and modifications are made to the built functions. The method described in the present invention is reconstruction, that is, automated reconstruction based on standardized design models, which can greatly improve change efficiency, reduce errors and reduce costs.

[0047] In summary, the present invention is based on a standardized design model and combines a low-code development platform / no-code development platform to realize the automated development of basic functions and common functions of a software system. Therefore, the present invention effectively overcomes various shortcomings in the prior art and has a high industrial utilization value.

[0048] The above embodiments are merely illustrative of the principles and effects of the present invention, and are not intended to limit the present invention. Anyone familiar with the art may modify or alter the above embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or alterations made by a person of ordinary skill in the art without departing from the spirit and technical concept disclosed by the present invention shall still be covered by the claims of the present invention.

Claims

1. An automated development method for a low-code development platform based on a design model, characterized in that: The method comprises the following steps: Step 1: Perform UI design, rule design and entity design, and generate UI model, rule model and entity model based on the UI design, rule design and entity design configuration; Step 2: Automatically complete the mapping configuration of the UI model adapter, the rule model adapter, and the entity model adapter based on the UI model, the rule model, and the entity model; Step 3: Automatically create the corresponding low-code platform component element files based on the UI model adapter, rule model adapter, and entity model adapter, thereby completing the automated development of software system functions; The component elements of the UI design include forms, lists, calendars, and tree structures; The rule design includes front-end rule design and back-end rule design, and the component elements of the front-end rules and back-end rules respectively include verification rules, calculation rules, control rules and event triggering rules; The component elements of the physical design include data tables and files; The mapping configuration of the UI model adapter is to adapt the component elements of the UI design to the component elements of the corresponding low-code platform; The mapping configuration of the rule model adapter is to adapt the component elements of the rule design to the component elements of the corresponding low-code platform; The mapping configuration of the entity model adapter is to adapt the component elements of the entity design to the component elements of the corresponding low-code platform; UI design, rule design and entity design are interrelated; UI design is the way entity design is expressed on the user side, and its expression logic is controlled by rule design. Under the control of rule design, the operation information of the user side is persisted to the database; each component element of UI design has a corresponding component element of entity design; front-end rule design constrains the behavior of the user side based on UI design, and can assist the user side to automatically display the calculation results after entering the content, or automatically obtain real-time data; after the user side completes the front-end operation, the back-end rule design completes the verification, calculation, control and event processing through the system; the component elements of the back-end rule design are based on the component elements of the entity design; After automatically completing the mapping configuration of the UI model adapter, rule model adapter, and entity model adapter, all component elements of UI design, rule design, and entity design are described in the component element description method of the corresponding low-code development platform to form corresponding component element files.

Images