A low-code generation method and system for multi-end programs

Abstract

The application discloses a kind of low code generation method and system for multi-terminal program, it is related to software development field, solve the problem of low code generation business program matching degree, method includes: set functional requirement form and non-functional requirement form, user fills out functional requirement form and non-functional requirement form and obtains the business function requirement and server performance data corresponding to business program;Component type of business program corresponding business program backend is set based on business function requirement, and alternative scheme is obtained based on component type division;According to the test result, actual alternative low code component is selected based on the module running test of core function module to the scheme content of alternative scheme;The API interface of business program front end interface is adjusted based on the API interface reserved in business program backend, and business program backend and front end interface are embedded, and the business program of multi-terminal is obtained, and the customized construction of business program is realized by the application.

Description

Technical Field

[0001] This invention belongs to the field of software development technology, specifically a low-code generation method and system for multi-platform programs. Background Technology

[0002] Multi-platform applications refer to application systems that can run on multiple terminal devices, adapting to different platform operating environments through a single core codebase or design logic. Their core objective is "develop / design once, deploy across multiple platforms," ​​solving the high cost problem of developing separate applications for each platform in traditional development. Low-code, on the other hand, is a visual application development methodology that delivers applications with less code and faster speed, automating the code that programmers don't want to develop. Low-code is also a digital technology tool platform that uses more efficient methods such as graphical drag-and-drop and parameterized configuration to achieve rapid building, data orchestration, ecosystem connectivity, and middleware services. It enables innovative application scenarios in digital transformation through minimal or no code.

[0003] However, at present, when building business applications through low-code, they are often processed on a uniform template instead of being customized based on actual business actors and business use cases, resulting in a low degree of matching between the actual business application and the business application expected by the user.

[0004] Therefore, this invention proposes a low-code generation method and system for multi-terminal programs. Summary of the Invention

[0005] The purpose of this invention is to propose a low-code generation method and system for multi-terminal programs to solve the problems mentioned in the background art.

[0006] To achieve the above objectives, the present invention adopts the following technical solution:

[0007] A low-code generation method for multi-platform applications, the method comprising:

[0008] Step S1: Set up functional requirements table and non-functional requirements table. The user fills in the functional requirements table and non-functional requirements table to obtain the business function requirements and server performance data corresponding to the business program.

[0009] Step S2: Based on business function requirements, set the component types of the backend of the business program corresponding to the business program, and obtain alternative solutions based on the component types.

[0010] Step S3: Based on the content of the alternative solutions, perform module operation tests on the core functional modules, and select the actual alternative low-code components based on the test results.

[0011] Step S4: Adjust the API interface of the business program front-end interface based on the API interface reserved in the business program back-end, and embed the business program back-end and front-end interface to obtain a multi-terminal business program.

[0012] Further, step S1 includes the following sub-steps:

[0013] Step S11: Confirm all business participants using the determination rules corresponding to the business participants;

[0014] Step S12: Set up a functional requirements table and confirm the corresponding business function requirements of business participants based on the functional requirements table.

[0015] Step S13: Set up a non-functional requirement collection table and obtain server performance data for the expected operation of the business program based on the non-functional requirement collection table.

[0016] Furthermore, the rules for determining the business participants are as follows:

[0017] Rule 1: Identify the users to whom the business process is intended;

[0018] Rule 2: Identify the user's role in the interaction of the business process;

[0019] Rule 3: Confirm the user who installed the service program;

[0020] Rule 4: Confirm the user who starts and stops the business process;

[0021] Rule 5: Identify the user responsible for maintaining the business processes;

[0022] Rule 6: Confirm whether the business process interacts with other business processes;

[0023] All entities identified under Rules 1 through 6 are recorded as business participants.

[0024] Furthermore, step S2 includes the following sub-steps:

[0025] Step S21: Obtain the business function requirements of the business programs corresponding to multiple terminals, and identify multiple front-end function requirements of the front-end interface corresponding to the business programs based on the business function requirements.

[0026] Step S22: Based on multiple front-end functional requirements, determine the component type required for the corresponding position coordinates, and obtain the component name of the corresponding component based on the component type;

[0027] Among them, the component types include basic UI components and composite components, and composite components are composed of multiple sub-components;

[0028] Step S23: Identify multiple components with the same name corresponding to each basic UI component in the preset component library, and sort the multiple components with the same name in descending order of usage rate, and select the one ranked first as the selected UI component corresponding to the basic UI component.

[0029] Step S24: Obtain the molecular component corresponding to each composite component, select the molecular component with the largest area ratio in the composite component as the main component of the composite component, identify the corresponding component with the same name in the preset component library, select the component with the same name with the highest usage rate as the main component, and select the component with the same name corresponding to the molecular component with the highest combination rate with the selected main component as the selected molecular component.

[0030] Furthermore, step S2 also includes the following sub-steps:

[0031] Step S25: Select the molecular component and the main component to form a selection composite component. Multiple selection composite components and selection UI components form the front-end interface of the multi-terminal business program.

[0032] Step S26: Identify multiple backend functional requirements of the business program based on business functional requirements, obtain multiple core functional modules based on backend functional requirements and business use case mapping, and record the backend functions of the corresponding core functional modules.

[0033] Step S27: Select multiple sets of backend low-code blocks corresponding to the core functional modules based on the backend functions of the core functional modules. Arrange the backend low-code components with the same functions as the backend low-code blocks in descending order of usage rate, and select the backend low-code components in the first t positions as candidate low-code components.

[0034] Step S28: Record the backend low-code blocks in the core functional module as independent permutation items, count the number of candidate low-code components corresponding to the permutation items and record it as the total number of elements of the corresponding permutation items, calculate the number of combinations of the corresponding permutation items based on the expected number of low-code components to be selected, sum all the combination numbers corresponding to the core functional module to obtain the number of candidate schemes X corresponding to the core functional module; record the combination of different candidate low-code components as the scheme content of each candidate scheme corresponding to the core functional module; number the candidate schemes as i, i = 1, 2, ..., X.

[0035] Further, step S3 includes the following sub-steps:

[0036] Step S31: Obtain multiple core functional modules, and identify the content of multiple sets of alternative solutions based on the core functional modules;

[0037] Step S32: Select mobile phone, PC and tablet as the module running test platform, and select the top three device types with the highest ownership rate on mobile phone, PC and tablet respectively, and record the corresponding device types as the module running test environment.

[0038] Step S33: Obtain the solution content of multiple alternative solutions corresponding to the core functional module, and construct the corresponding core functional module to be tested based on the solution content of any one alternative solution.

[0039] Step S34: Perform compatibility testing on the core functional module based on the content of multiple alternative solutions corresponding to the core functional module.

[0040] Furthermore, step S3 also includes:

[0041] Step S35: Based on the content of all alternative solutions corresponding to the core functional module, perform compatibility testing on the core functional module to obtain the compatibility test results of multiple sets of alternative solutions.

[0042] Step S36: Based on the content of multiple alternative solutions corresponding to the core functional module, perform a responsiveness test on the core functional module to obtain the responsiveness test results of multiple alternative solutions.

[0043] Step S37: Iterate through the response test results and compatibility test results corresponding to the core functional modules in sequence, select the alternative solutions whose difference value and response test time are both less than the corresponding threshold as the actual alternative low-code components of the core functional modules, and obtain the actual business program backend.

[0044] Furthermore, the specific testing process for the compatibility test is as follows:

[0045] Step S341: Select any simulated test environment and run the core functional module in the simulated test environment;

[0046] Step S342: Obtain the API of the core functional module, call the API of the core functional module, input the relevant data, and jump to the compatibility test front-end interface after the core functional module runs.

[0047] Step S343: Treat the compatibility test front-end interface as an image, and divide the compatibility test front-end interface into multiple interface partitions according to the equal-spacing segmentation method; obtain the estimated image of the compatibility test front-end interface and record it as the comparison interface; divide the comparison interface according to the same segmentation method as the compatibility test front-end interface to obtain multiple comparison partitions.

[0048] Step S344: The interface partitions and comparison partitions at the same location are assigned the same number j, j = 1, 2, ..., z; z is a positive integer;

[0049] Step S345: Calculate the difference value CXj between the interface partition corresponding to the unified number and the comparison partition;

[0050] Step S346: Add the difference values ​​of all numbered interface partitions and comparison partitions, sum them, and take the average to obtain the difference value of the corresponding compatibility test front-end interface; similarly, run the core functional module in all simulated test environments, and output the difference values ​​of multiple sets of compatibility test front-end interfaces as compatibility test results.

[0051] Furthermore, the specific testing process for the responsiveness test is as follows:

[0052] Step S361: Select any simulated test environment and run the core functional module in the simulated test environment;

[0053] Step S362: Input test data, call the API interface of the core function module, mark the current time as the first time; record the time when the test data is sent out through the API interface as the second time; record the time when the test data is queried and feedback data is generated to the core function module as the third time; record the time when the core function module receives the feedback data and renders the front-end interface as the fourth time.

[0054] Step S363: Subtract the first time from the second time to obtain the operation response time, subtract the second time from the third time to obtain the feedback response time, and subtract the third time from the fourth time to obtain the rendering response time.

[0055] Step S364: Calculate the response test duration of the corresponding alternative scheme using the formula, as follows:

[0056] Response test duration = First coefficient × Operation response duration + Second coefficient × Feedback response duration + Third coefficient × Rendering response duration; where, Second coefficient > Third coefficient > First coefficient;

[0057] Step S365: Run the core functional modules in all simulated test environments to obtain the response test duration of multiple alternative solutions and record it as the response test result, and then output it.

[0058] The present invention also provides a low-code generation system for multi-terminal programs, including a data acquisition module, a component classification module, a component testing module, a program generation module, and a debugging terminal;

[0059] The data acquisition module is used to collect the business function requirements and server performance data corresponding to the business program, and send the business function requirements to the component classification module and the server performance data to the debugging terminal.

[0060] The component classification module is used to set the component types of the front-end interface and back-end of the business program based on the business function requirements, obtain alternative solutions based on the component type classification, and send the alternative solutions to the component testing module; and send the front-end interface to the program generation module.

[0061] The component testing module is used to perform module operation tests on the core functional modules based on the content of the alternative solutions, and select the actual alternative low-code components according to the test results and send them to the program generation module.

[0062] The debugging terminal is used to access multi-terminal business programs and perform functional tests through actual business participants, and to adjust and release the multi-terminal business programs based on the functional test results and server performance data.

[0063] In summary, due to the adoption of the above technical solution, the beneficial effects of the present invention are:

[0064] 1. This invention first sets up a functional requirement table and a non-functional requirement table. Users fill in the functional requirement table and the non-functional requirement table to obtain the business function requirements and server performance data corresponding to the business program; thus realizing the collection of the pre-requirements of the business program.

[0065] 2. This invention first sets the component types of the backend of the business program corresponding to the business function requirements, and obtains alternative solutions based on the component types; then, it performs module operation tests on the core functional modules based on the content of the alternative solutions, and selects the actual alternative low-code components according to the test results. This invention realizes the determination of the components corresponding to the business program.

[0066] 3. This invention adjusts the API interface of the business program front-end interface based on the API interface reserved in the business program back-end, and embeds the business program back-end and front-end interface to obtain a multi-terminal business program, thereby realizing the customized construction of multi-terminal business programs. Attached Figure Description

[0067] To facilitate understanding by those skilled in the art, the present invention will be further described below with reference to the accompanying drawings.

[0068] Figure 1 This is a flowchart of the method of the present invention;

[0069] Figure 2 This is the business logic diagram corresponding to step S1 in this invention;

[0070] Figure 3 This is a diagram illustrating the overall framework of the business process in this invention.

[0071] Figure 4 This is a system block diagram of the low-code generation system in this invention. Detailed Implementation

[0072] The technical solution of the present invention will be clearly and completely described below with reference to the embodiments. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0073] Example 1: Please refer to Figures 1-3 As shown, the technical solution provided by the present invention is: a low-code generation method for multi-terminal programs, wherein the multi-terminal programs include web terminals, mobile terminals, mini-program terminals and desktop terminals, and the low-code is a development method that quickly builds applications through graphical interfaces, component drag and drop and a small amount of code;

[0074] The method involves setting a domain-specific language for the business program, determining the component types of the front-end interface corresponding to the business program at different coordinates, selecting the actual components based on the abnormal situations of different component combinations, and combining them to obtain the front-end interface. Then, business participants and business use cases are collected, and the back-end code of the core functional modules is constructed by combining the business participants and business use cases. The back-end code and the front-end interface are then embedded through API to obtain a multi-terminal business program, which is then tested and released.

[0075] In this invention, the low-code generation method includes the following steps:

[0076] Step S1: Set up functional requirements table and non-functional requirements table. The user fills in the functional requirements table and non-functional requirements table to obtain the business function requirements and server performance data corresponding to the business program.

[0077] The functional requirements table is used to confirm the business function requirements of the business program; the non-functional requirements table is used to confirm the server performance data expected to run the business program, and then to carry out targeted performance optimization.

[0078] In this invention, step S1 includes the following sub-steps:

[0079] Step S11: Confirm all business participants using the determination rules corresponding to the business participants;

[0080] The specific rules for determining business participants are as follows:

[0081] Rule 1: Identify the users to whom the business process is intended;

[0082] Rule 2: Identify the user's role in the interaction of the business process;

[0083] Rule 3: Confirm the user who installed the service program;

[0084] Rule 4: Confirm the user who starts and stops the business process;

[0085] Rule 5: Identify the user responsible for maintaining the business processes;

[0086] Rule 6: Confirm whether the business process interacts with other business processes;

[0087] All entities identified under Rules 1 through 6 are recorded as business participants;

[0088] In this context, a business participant is a role that directly interacts with the abstraction of external entities of business programs, subsystems, or intra-system classes generated by the visual editing model. Therefore, a business participant can be a person or a transaction. At the same time, a business participant does not refer to the person or transaction itself, but rather the role played by the person or transaction.

[0089] For example, someone is an administrator of an e-commerce business program who participates in the interaction of the e-commerce management system. Therefore, he can participate in the management system as an administrator, and at the same time, he can also access or modify his own information as a user. Thus, the corresponding person has two different participant identities at the same time.

[0090] Step S12: Set up a functional requirements table and confirm the corresponding business function requirements of business participants based on the functional requirements table.

[0091] In this invention, business use cases can be identified by considering the following questions:

[0092] Question 1: Why do business participants need to use the corresponding business procedures?

[0093] Question 2: Do business participants need to use the CRUD (Create, Read, Update, Delete) functions in the business program? If so, how can they perform these operations?

[0094] Question 3: Will business participants introduce content from outside the business process into the business process?

[0095] Question 4: Will the business process send certain internal content to the corresponding business participants?

[0096] Step S13: Set up a non-functional requirement collection table and obtain server performance data for the expected operation of the business program based on the non-functional requirement collection table.

[0097] The functional requirements collection form is as follows:

[0098]

[0099] The non-functional requirements collection form is as follows:

[0100]

[0101] Step S2: Based on business function requirements, set the component types of the backend of the business program corresponding to the business program, and obtain alternative solutions based on the component types.

[0102] The business function requirements are specifically the user requirements input by users on different terminals, and are the business functions required by the business program.

[0103] In this invention, step S2 includes the following sub-steps:

[0104] Step S21: Obtain the business function requirements of the business programs corresponding to multiple terminals, and identify multiple front-end function requirements of the front-end interface corresponding to the business programs based on the business function requirements.

[0105] Among them, the front-end interface is the interface that users see when using the business program. Users interact with the business program by operating different components on the front-end interface.

[0106] In reality, the front-end interface is composed of different components, which can be search box components, button components, or image display components. Therefore, the front-end functional requirements are: image display, buttons, search box, and form submission, etc.

[0107] Step S22: Based on multiple front-end functional requirements, determine the component type required for the corresponding position coordinates, and obtain the component name of the corresponding component based on the component type;

[0108] Among them, the component types include basic UI components and composite components. Composite components are composed of multiple sub-components. Specifically, the component names of the basic UI components and the component names of the corresponding sub-components of the composite components can be identified.

[0109] It should be noted that a single basic UI component can fulfill the front-end functional requirements, while composite components require multiple components to be nested to fulfill the front-end functional requirements.

[0110] Step S23: Identify multiple components with the same name corresponding to each basic UI component in the preset component library, and sort the multiple components with the same name in descending order of usage rate, and select the one ranked first as the selected UI component corresponding to the basic UI component.

[0111] Step S24: Obtain the molecular component corresponding to each composite component, select the molecular component with the largest area ratio in the composite component as the main component of the composite component, identify the component with the same name corresponding to the main component in the preset component library, select the component with the same name with the highest usage rate as the main component, and select the component with the same name corresponding to the molecular component with the highest combination rate with the selected main component as the selected molecular component.

[0112] Specifically, the area ratio of a component is obtained by dividing the molecular area of ​​the corresponding molecular component by the composite area of ​​the composite component. Since most components are rectangular, the ratio can be obtained by multiplying the length of the corresponding molecular component or composite component by its width.

[0113] Step S25: Select the molecular component and the main component to form a selection composite component. Multiple selection composite components and selection UI components form the front-end interface of the multi-terminal business program.

[0114] Step S26: Identify multiple backend functional requirements of the business program based on business functional requirements, obtain multiple core functional modules based on backend functional requirements and business use case mapping, and record the backend functions of the corresponding core functional modules.

[0115] Among them, the core functional modules are used to describe the specific functions of the backend code corresponding to the business program; specifically, the core functional modules can be the creation, deletion, modification and query of data in the database, classification and tag management, media file upload and inventory management, etc.

[0116] Step S27: Select multiple sets of backend low-code blocks corresponding to the core functional modules based on the backend functions of the core functional modules. Arrange the backend low-code components with the same functions as the backend low-code blocks in descending order of usage rate, and select the backend low-code components in the first t positions as candidate low-code components; preferably, t is 3.

[0117] Step S28: Record the backend low-code blocks in the core functional module as independent permutation items, count the number of candidate low-code components corresponding to the permutation items and record it as the total number of elements of the corresponding permutation items, calculate the number of combinations of the corresponding permutation items based on the expected number of low-code components to be selected, sum all the combination numbers corresponding to the core functional module to obtain the number of candidate schemes X corresponding to the candidate schemes of the core functional module; record the combination of different candidate low-code components as the scheme content of each candidate scheme corresponding to the core functional module; number the candidate schemes as i, i = 1, 2, ..., X;

[0118] For example, a core functional module consists of three backend low-code blocks, each of which corresponds to t candidate low-code components, meaning there are t ways to select a backend low-code block. Therefore, the number of combinations for each low-code block is C(1, t). Thus, the number X of the candidate solutions for the core functional module is:

[0119] X = C(1, t) × C(1, t) × C(1, t); where C(1, t) is the product of the factorial of t divided by the factorial of 1 and the factorial of (t-1); that is:

[0120] C(1, t) = t! / (1! × (t-1)!) where ! represents factorial;

[0121] Step S28: Similarly, calculate the number of alternative solutions for all core functional modules and obtain the solution content of the alternative solutions for the corresponding core functional modules.

[0122] Step S3: Based on the content of the alternative solutions, perform module operation tests on the core functional modules, and select the actual alternative low-code components based on the test results.

[0123] In this invention, step S3 includes the following sub-steps:

[0124] Step S31: Obtain multiple core functional modules, and identify the content of multiple sets of alternative solutions based on the core functional modules;

[0125] Step S32: Select mobile phone, PC and tablet as the module running test platform, and select the top three device types with the highest ownership rate on mobile phone, PC and tablet respectively, and record the corresponding device types as the module running test environment.

[0126] Step S33: Obtain the solution content of multiple alternative solutions corresponding to the core functional module, and construct the corresponding core functional module to be tested based on the solution content of any one alternative solution.

[0127] Specifically, in the low-code engine, drag and drop the content of the alternative solution corresponding to the alternative low-code component to the area where the core functional module is integrated, and you can obtain the corresponding core functional module to be tested based on the content of the alternative solution.

[0128] Step S34: Based on the content of multiple alternative solutions corresponding to the core functional module, perform compatibility testing on the core functional module. The specific testing process is as follows:

[0129] Step S341: Select any simulated test environment and run the core functional module in the simulated test environment;

[0130] Step S342: Obtain the API of the core functional module, call the API of the core functional module, input the relevant data, and jump to the compatibility test front-end interface after the core functional module runs.

[0131] Taking the login function module as an example, if the correct username and password are entered, the login will be successful after calling the API and the user will proceed to the next screen; if the wrong username or password is entered, a corresponding error message will be generated.

[0132] Step S343: Treat the compatibility test front-end interface as an image, and divide the compatibility test front-end interface into multiple interface partitions according to the equal-spacing segmentation method; obtain the estimated image of the compatibility test front-end interface and record it as the comparison interface; divide the comparison interface according to the same segmentation method as the compatibility test front-end interface to obtain multiple comparison partitions.

[0133] Step S344: The interface partitions and comparison partitions at the same location are assigned the same number j, j = 1, 2, ..., z; z is a positive integer;

[0134] Step S345: Calculate the difference value CXj between the interface partition corresponding to the unified number and the comparison partition. In this invention, the mean square error of the pixel values ​​of the corresponding pixels in the interface partition and the comparison partition is used as the evaluation standard for the difference value. The smaller the mean square error, the more similar the two are, that is, the smaller the difference.

[0135] Step S346: Add the difference values ​​of all numbered interface partitions and comparison partitions, sum them, and take the average to obtain the difference value of the corresponding compatibility test front-end interface; similarly, run the core functional module in all simulated test environments, and output the difference values ​​of multiple sets of compatibility test front-end interfaces as compatibility test results.

[0136] Step S35: Based on the content of all alternative solutions corresponding to the core functional module, perform compatibility testing on the core functional module to obtain the compatibility test results of multiple sets of alternative solutions.

[0137] Step S36: Based on the content of multiple alternative solutions corresponding to the core functional module, perform responsiveness testing on the core functional module to obtain the responsiveness test results of multiple alternative solutions. The specific testing process is as follows:

[0138] Step S361: Select any simulated test environment and run the core functional module in the simulated test environment;

[0139] Step S362: Input test data, call the API interface of the core function module, mark the current time as the first time; record the time when the test data is sent out through the API interface as the second time; record the time when the test data is queried and feedback data is generated to the core function module as the third time; record the time when the core function module receives the feedback data and renders the front-end interface as the fourth time.

[0140] The test data is input through the front-end interface. The specific business process is as follows: input test data into the front-end interface → send test data to the business program back-end → the business program back-end executes the corresponding function based on the test data and gets the return value back to the front-end.

[0141] Step S363: Subtract the first time from the second time to obtain the operation response time, subtract the second time from the third time to obtain the feedback response time, and subtract the third time from the fourth time to obtain the rendering response time.

[0142] Step S364: Calculate the response test duration of the corresponding alternative scheme using the formula, as follows:

[0143] Response test duration = First coefficient × Operation response duration + Second coefficient × Feedback response duration + Third coefficient × Rendering response duration; where, Second coefficient > Third coefficient > First coefficient;

[0144] Step S365: Similarly, run the core functional modules in all simulated test environments to obtain the response test duration of multiple alternative solutions and record it as the response test result before outputting it.

[0145] Step S37: Iterate through the response test results and compatibility test results corresponding to the core functional modules in sequence, select the alternative solutions whose difference value and response test time are both less than the corresponding threshold as the actual alternative low-code components of the core functional modules, and obtain the actual business program backend.

[0146] It should be noted that if none of the alternative solutions satisfy step S37, multiple sets of alternative solutions will be regenerated and step S3 will be executed again.

[0147] Step S4: Adjust the API interface of the business program front-end interface based on the API interface reserved in the business program back-end, and embed the business program back-end and front-end interface to obtain a multi-terminal business program.

[0148] Example 2: Please refer to Figure 4 As shown, based on another concept of the same invention, a low-code generation system for multi-terminal programs is proposed, including a data acquisition module, a component classification module, a component testing module, a program generation module, and a debugging terminal.

[0149] The data acquisition module is used to collect the business function requirements and server performance data corresponding to the business program, and send the business function requirements to the component classification module and the server performance data to the debugging terminal.

[0150] The component classification module is used to set the component types of the front-end interface and back-end of the business program based on the business function requirements, obtain alternative solutions based on the component type classification, and send the alternative solutions to the component testing module; and send the front-end interface to the program generation module.

[0151] The component testing module is used to perform module operation tests on the core functional modules based on the content of the alternative solutions, and select the actual alternative low-code components according to the test results and send them to the program generation module.

[0152] The debugging terminal is used to access multi-terminal business programs and perform functional tests through actual business participants, and to adjust and release the multi-terminal business programs based on the functional test results and server performance data.

[0153] The preferred embodiments of the present invention disclosed above are merely illustrative of the invention. These preferred embodiments do not exhaustively describe all details, nor do they limit the invention to any specific implementation. Clearly, many modifications and variations can be made based on the content of this specification. This specification selects and specifically describes these embodiments to better explain the principles and practical applications of the invention, thereby enabling those skilled in the art to better understand and utilize the invention. The invention is limited only by the claims and their full scope and equivalents.

Claims

1. A low-code generation method for multi-platform programs, characterized in that, The method includes: Step S1: Set up functional requirements table and non-functional requirements table. The user fills in the functional requirements table and non-functional requirements table to obtain the business function requirements and server performance data corresponding to the business program. Step S2: Based on business function requirements, set the component types of the backend of the business program corresponding to the business program, and obtain alternative solutions based on the component types. Step S2 includes the following sub-steps: Step S21: Obtain the business function requirements of the business programs corresponding to multiple terminals, and identify multiple front-end function requirements of the front-end interface corresponding to the business programs based on the business function requirements. Step S22: Based on multiple front-end functional requirements, determine the component type required for the corresponding component at the corresponding location coordinates, and obtain the component name of the corresponding component based on the component type; wherein, the component type includes basic UI components and composite components, and the composite component is composed of multiple sub-components; Step S23: Identify multiple components with the same name corresponding to each basic UI component in the preset component library, and sort the multiple components with the same name in descending order of usage rate, and select the one ranked first as the selected UI component corresponding to the basic UI component. Step S24: Obtain the molecular component corresponding to each composite component, select the molecular component with the largest area ratio in the composite component as the main component of the composite component, identify the component with the same name corresponding to the main component in the preset component library, select the component with the same name with the highest usage rate as the main component, and select the component with the same name corresponding to the molecular component with the highest combination rate with the selected main component as the selected molecular component. Step S2 further includes the following sub-steps: Step S25: Select the molecular component and the main component to form a selection composite component. Multiple selection composite components and selection UI components form the front-end interface of the multi-terminal business program. Step S26: Identify multiple backend functional requirements of the business program based on business functional requirements, obtain multiple core functional modules based on backend functional requirements and business use case mapping, and record the backend functions of the corresponding core functional modules. Step S27: Select multiple sets of backend low-code blocks corresponding to the core functional modules based on the backend functions of the core functional modules. Arrange the backend low-code components with the same functions as the backend low-code blocks in descending order of usage rate, and select the backend low-code components in the first t positions as candidate low-code components. Step S28: Record the backend low-code blocks in the core functional module as independent permutation items, count the number of candidate low-code components corresponding to the permutation items and record it as the total number of elements of the corresponding permutation items, calculate the number of combinations of the corresponding permutation items based on the expected number of low-code components to be selected, sum all the combination numbers corresponding to the core functional module to obtain the number of candidate schemes X corresponding to the candidate schemes of the core functional module; record the combination of different candidate low-code components as the scheme content of each candidate scheme corresponding to the core functional module; number the candidate schemes as i, i=1,2,...,X; Step S3: Based on the content of the alternative solutions, perform module operation tests on the core functional modules, and select the actual alternative low-code components based on the test results. Step S3 includes the following sub-steps: Step S31: Obtain multiple core functional modules, and identify the content of multiple sets of alternative solutions based on the core functional modules; Step S32: Select mobile phone, PC and tablet as the module running test platform, and select the top three device types with the highest ownership rate on mobile phone, PC and tablet respectively, and record the corresponding device types as the module running test environment. Step S33: Obtain the solution content of multiple alternative solutions corresponding to the core functional module, and construct the corresponding core functional module to be tested based on the solution content of any one alternative solution. Step S34: Based on the content of multiple alternative solutions corresponding to the core functional module, perform compatibility testing on the core functional module. The specific testing process for compatibility testing is as follows: Step S341: Select any simulated test environment and run the core functional module in the simulated test environment; Step S342: Obtain the API of the core functional module, call the API of the core functional module, input the relevant data, and jump to the compatibility test front-end interface after the core functional module runs. Step S343: Treat the compatibility test front-end interface as an image, and divide the compatibility test front-end interface into multiple interface partitions according to the equal-spacing segmentation method; obtain the estimated image of the compatibility test front-end interface and record it as the comparison interface; divide the comparison interface according to the same segmentation method as the compatibility test front-end interface to obtain multiple comparison partitions. Step S344: The interface partitions and comparison partitions at the same location are assigned the same number j, j=1,2,...,z; z is a positive integer; Step S345: Calculate the difference value CXj between the interface partition corresponding to the unified number and the comparison partition; Step S346: Add the difference values ​​of all numbered interface partitions and comparison partitions, sum them, and take the average to obtain the difference value of the corresponding compatibility test front-end interface; similarly, run the core functional module in all simulated test environments, and output the difference values ​​of multiple sets of compatibility test front-end interfaces as compatibility test results. Step S35: Based on the content of all alternative solutions corresponding to the core functional module, perform compatibility testing on the core functional module to obtain the compatibility test results of multiple sets of alternative solutions. Step S36: Based on the content of multiple alternative solutions corresponding to the core functional module, perform responsiveness testing on the core functional module to obtain the responsiveness test results of multiple alternative solutions. The specific testing process for responsiveness testing is as follows: Step S361: Select any simulated test environment and run the core functional module in the simulated test environment; Step S362: Input test data, call the API interface of the core function module, mark the current time as the first time; record the time when the test data is sent out through the API interface as the second time; record the time when the test data is queried and feedback data is generated to the core function module as the third time; record the time when the core function module receives the feedback data and renders the front-end interface as the fourth time. Step S363: Subtract the first time from the second time to obtain the operation response time, subtract the second time from the third time to obtain the feedback response time, and subtract the third time from the fourth time to obtain the rendering response time. Step S364: Calculate the response test duration of the corresponding alternative scheme using the formula, as follows: Response test duration = First coefficient × Operation response duration + Second coefficient × Feedback response duration + Third coefficient × Rendering response duration; where, Second coefficient > Third coefficient > First coefficient; Step S365: Run the core functional modules in all simulated test environments to obtain the response test duration of multiple alternative solutions and record it as the response test result, and then output it. Step S37: Iterate through the response test results and compatibility test results corresponding to the core functional modules in sequence, select the alternative solutions whose difference value and response test time are both less than the corresponding threshold as the actual alternative low-code components of the core functional modules, and obtain the actual business program backend. Step S4: Adjust the API interface of the business program front-end interface based on the API interface reserved in the business program back-end, and embed the business program back-end and front-end interface to obtain a multi-terminal business program.

2. The low-code generation method for multi-terminal programs according to claim 1, characterized in that, Step S1 includes the following sub-steps: Step S11: Confirm all business participants using the determination rules corresponding to the business participants; Step S12: Set up a functional requirements table and confirm the corresponding business function requirements of business participants based on the functional requirements table. Step S13: Set up a non-functional requirement collection table and obtain server performance data for the expected operation of the business program based on the non-functional requirement collection table.

3. The low-code generation method for multi-terminal programs according to claim 2, characterized in that, The specific rules for determining the business participants are as follows: Rule 1: Identify the users to whom the business process is intended; Rule 2: Identify the user's role in the interaction of the business process; Rule 3: Confirm the user who installed the service program; Rule 4: Confirm the user who starts and stops the business process; Rule 5: Identify the user responsible for maintaining the business processes; Rule 6: Confirm whether the business process interacts with other business processes; Those identified in Rules 1 through 6 are all recorded as business participants.

4. A low-code generation system for multi-platform programs, characterized in that, A low-code generation method for multi-terminal programs according to any one of claims 1-3 includes a data acquisition module, a component classification module, a component testing module, a program generation module, and a debugging terminal. The data acquisition module is used to collect the business function requirements and server performance data corresponding to the business program, and send the business function requirements to the component classification module and the server performance data to the debugging terminal. The component classification module is used to set the component types of the front-end interface and back-end of the business program based on the business function requirements, obtain alternative solutions based on the component type classification, and send the alternative solutions to the component testing module; and send the front-end interface to the program generation module. The component testing module is used to perform module operation tests on the core functional modules based on the content of the alternative solutions, and select the actual alternative low-code components according to the test results and send them to the program generation module. The debugging terminal is used to access multi-terminal business programs and perform functional tests through actual business participants, and to adjust and release the multi-terminal business programs based on the functional test results and server performance data.

Images