A software development method and system based on a low-code platform

Abstract

The present invention belongs to the field of software engineering, and discloses a software development method and system based on a low-code platform, including automatically generating an initial project through project requirements; designing a workflow based on the initial project through predefined workflow nodes and a graphical interface; real-time synchronizing and recording all changes to the workflow; conducting experimental development of sub-branches based on the change records, reviewing the experimental development of sub-branches, and merging them into a new workflow according to the review results; starting the new workflow for testing, debugging based on the test results to obtain the final workflow; deploying the final workflow to the production environment, real-time monitoring the running status of the final workflow, and continuously iterating and improving the final workflow based on the monitoring data and user feedback. By conducting experimental development of sub-branches based on change records, reviewing, and real-time synchronizing and recording all changes to the workflow, the present invention improves the team collaboration efficiency and version control ability.

Description

Technical Field

[0001] The present invention belongs to the technical field of software engineering, and particularly relates to a software development method and system based on a low-code platform. Background Art

[0002] In recent years, with the continuous growth of software development requirements and the rapid development of technology, low-code platforms, as an efficient software development tool, have gradually received wide attention. By providing a visual development environment and a predefined component library, low-code platforms enable non-professional developers to quickly build complex application programs. These platforms usually support functions such as drag-and-drop interface design, automated script generation, real-time synchronization, and change management, greatly improving development efficiency and reducing development costs. In addition, low-code platforms also provide rich integration capabilities and extensibility, enabling developers to easily integrate various services and systems into the workflow.

[0003] Although existing low-code platforms perform well in improving development efficiency, when dealing with complex business logics and functional requirements, they often lack sufficient flexibility and customizability. Although the predefined components and templates provided by many platforms can meet basic needs, their support for specific industries or complex application scenarios is limited, resulting in developers needing to perform a large amount of manual coding and debugging when implementing certain advanced functions. This not only increases the development difficulty but also prolongs the development cycle. This not only affects development efficiency but may also lead to serious errors and delays. Summary of the Invention

[0004] To solve the above problems, the present invention provides a software development method and system based on a low-code platform, which solves the problems of insufficient flexibility and customizability in the prior art and improves development efficiency and system stability.

[0005] The software development method based on a low-code platform according to the present invention includes the following steps:

[0006] S1. Automatically generate an initial project according to project requirements;

[0007] S2. Based on the initial project, design a workflow through predefined workflow nodes and a graphical interface;

[0008] S3. Real-time synchronize and record all changes to the workflow;

[0009] S4. Based on the change record, conduct experimental development of sub-branches, review the experimental development of sub-branches, and merge them into a new workflow according to the review results;

[0010] S5. Start testing the new workflow, perform debugging based on the test results, and obtain the final workflow;

[0011] S6. Deploy the final workflow to the production environment, monitor the running status of the final workflow in real time, and continuously iterate and improve the final workflow based on the monitoring data and user feedback.

[0012] As a preferred solution of the software development method based on the low-code platform described in the present invention, wherein: S1 is specifically as follows:

[0013] Collect and organize into a requirements document through kick-off meetings, requirements research, analysis of existing processes, determination of business processes, and discussion of technical requirements;

[0014] Based on the requirements document, clarify the project objectives, list the functional requirements and describe their input / output and processing logic, determine the technical architecture and performance metrics, and consider security and compliance requirements, and finally obtain the project requirements;

[0015] Use an automated script to automatically generate an initial project through the project requirements.

[0016] As a preferred solution of the software development method based on the low-code platform described in the present invention, wherein: S2 is specifically as follows:

[0017] Conduct business requirements analysis, refer to industry standards, determine common business processes and functional requirements, design the specific functions, input / output parameters, and configuration options of each node, write front-end visualization components and back-end logic code, and conduct integration testing to ensure correct functionality and stable performance;

[0018] Encapsulate the nodes into reusable components and standardize the interfaces, write user documentation and developer documentation, and create a predefined workflow node library;

[0019] Based on the initial project, through the predefined workflow node library in the low-code platform, add the workflow nodes required by the project from the predefined workflow node library to the graphical area, configure the parameters of each node according to the functional requirements and business logic of the workflow nodes, and use connection lines to connect the various nodes to generate a coherent workflow.

[0020] As a preferred solution of the software development method based on the low-code platform described in the present invention, wherein: S3 is specifically as follows:

[0021] Modify the workflow connection lines, node configurations, front-end visualization components, back-end logic code, and user permissions through the collaborative editing function;

[0022] The low-code platform automatically enables the real-time synchronization function. When multiple team members edit the same workflow simultaneously, it updates the views of each team member in real time to ensure that all team members can see the latest workflow status on the same graphical area;

[0023] If multiple team members edit the same node simultaneously, the low-code platform locks this part when a team member edits a node through the real-time synchronization function, preventing other team members from editing simultaneously. When the team member finishes editing and saves, the lock is released, and other team members can continue editing;

[0024] The low-code platform records every operation of team members through the logging function, generating operation logs and change logs, recording the time, content, changer, and change description of each change.

[0025] As a preferred solution of the software development method based on the low-code platform described in the present invention, wherein: S4 is specifically:

[0026] Derive a sub-branch from the main workflow branch through the project management interface. In the visual workflow editing interface, select the created sub-branch, design and modify the workflow based on the change record according to the experimental requirements, select new nodes from the predefined workflow node library to the graphical area, configure the parameters of each node, and connect the various nodes with connection lines to form a coherent workflow;

[0027] Initiate a review request for the experimental development of the sub-branch. By calculating the overall quality score of the experimental development of the sub-branch, conduct a review, and the expression is:

[0028] ;

[0029] Wherein, is the overall quality score of the experimental development of the sub-branch, is the serial number of the change, is the total number of changes, is the weight of the th change, is the th priority of the change, which is a positive integer representing the importance and urgency of the change, is the th complexity of the change, is the th data volume of the change;

[0030] Based on the project requirements and standards, set a threshold ;

[0031] When it means that the change passes the review;

[0032] When it means that the change does not pass the review and needs to be further modified or re-evaluated;

[0033] Experimentally develop the sub-branch to be approved and merge it with the main branch of the workflow to form a new workflow.

[0034] As a preferred solution of the software development method based on the low-code platform described in the present invention, wherein: S5 is specifically:

[0035] Generate a test environment on the low-code platform based on the production environment, deploy the new workflow to the test environment using an automated deployment tool, write test cases according to the functional requirements and business logic of the new workflow, run the test cases one by one in the test environment, and test the new workflow. The expression is:

[0036] ;

[0037] Wherein, represents the test score, represents the total number of test cases, represents the accuracy weight coefficient, represents the th test case's accuracy score, represents the coverage weight coefficient, represents the th test case's coverage score, is the serial number of the test case;

[0038] Based on historical data and team experience, set the threshold ;

[0039] When it means the new workflow passes the test;

[0040] When it means that further debugging and optimization are required;

[0041] Based on the test results, use the debugging tools provided by the low-code platform to gradually check each step of the workflow, adjust the node parameters and optimize the logic to make the process more efficient and stable, and obtain the final workflow.

[0042] As a preferred solution of the software development method based on the low-code platform described in the present invention, wherein: S6 is specifically:

[0043] Formulate a deployment plan by selecting a low-load time period and a rollback strategy, and perform automated deployment using a CD tool;

[0044] View various monitoring metrics in real time through the monitoring dashboard, regularly check the monitoring data, automatically collect and store the monitoring data using Splunk, send a satisfaction questionnaire to users through the process automation function, and collect feedback from users on the final workflow;

[0045] Analyze the collected user feedback through data analysis tools and visualization dashboards to understand user experience issues during use, analyze the collected monitoring data, and discover performance issues, functional issues, and stability issues during use;

[0046] Based on the user feedback and the analysis results of the monitoring data, formulate improvement measures and continuously iterate and improve.

[0047] The present invention also provides a software development system based on a low-code platform, including a project initialization module, a design and editing module, a change management module, a change review module, a testing and debugging module, and a monitoring and continuous improvement module; The project initialization module is used to automatically generate an initialization project through project requirements; The design and editing module is used to design a workflow based on the initialization project through predefined workflow nodes and a graphical interface; The change management module is used to synchronize all changes of the workflow in real time and record them; The change review module is used to conduct experimental development of sub-branches based on the change records, review the experimental development of sub-branches, and merge them into a new workflow according to the review results; The testing and debugging module is used to start testing the new workflow, conduct debugging based on the test results, and obtain the final workflow; The monitoring and continuous improvement module is used to deploy the final workflow to the production environment, monitor the running status of the final workflow in real time, and continuously iterate and improve the final workflow based on the monitoring data and user feedback.

[0048] The beneficial effects of the present invention are as follows: Through the steps of conducting experimental development of sub-branches based on change records and reviewing them, the present invention realizes flexible testing and verification in an independent environment, ensuring that only high-quality changes can be merged into the main branch, thereby improving development efficiency and system stability; At the same time, through the step of synchronizing all changes of the workflow in real time and recording them, the present invention supports multi-person collaboration, prevents editing conflicts, and provides a detailed change history, improving team collaboration efficiency and version control capabilities. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for description in the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0050] Figure 1 It is a flowchart of the software development method based on the low-code platform in Embodiment 1;

[0051] Figure 2 It is a structural schematic diagram of the software development system based on the low-code platform in Embodiment 1;

[0052] Figure 3 This is a comparison chart of the workflow node generation efficiency between the present invention and traditional coding methods;

[0053] Figure 4 This is a comparison chart of the collaborative development mode between the present invention and traditional development modes;

[0054] Figure 5 This is a schematic diagram of the quality control of the present invention. Detailed implementation manners

[0055] To make the above objects, features, and advantages of the present invention more apparent and understandable, the following will describe the detailed implementation manners of the present invention with reference to the accompanying drawings of the specification.

[0056] In the following description, many specific details are set forth to facilitate a thorough understanding of the present invention. However, the present invention may be implemented in other ways different from those described herein. Those skilled in the art can make similar generalizations without departing from the spirit of the present invention. Therefore, the present invention is not limited by the specific embodiments disclosed below.

[0057] Secondly, the so-called "one embodiment" or "embodiment" herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation manner of the present invention. The phrase "in one embodiment" appearing in different places in this specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment that is mutually exclusive with other embodiments.

[0058] Embodiment 1, as Figure 1 shown, the present invention provides a software development method based on a low-code platform, including the following steps:

[0059] S1. Automatically generate an initialization project based on project requirements.

[0060] Furthermore, through kick-off meetings, requirement investigations, analysis of existing processes, determination of business processes, and discussions on technical requirements, collect and organize them into a requirement document;

[0061] Based on the requirement document, clarify the project objectives, list the functional requirements and describe their input / output and processing logics, determine the technical architecture and performance indicators, and consider security and compliance requirements, and finally obtain the project requirements;

[0062] Use an automated script to automatically generate an initialization project based on project requirements;

[0063] It should be noted that the automated script is written using Shell scripts based on the functions required for creating a project;

[0064] It should also be noted that the functions required to create a project include creating a project directory structure, generating configuration files, initializing a version control system (such as Git), installing dependency libraries, and configuring the development environment.

[0065] S2. Based on the initialized project, design a workflow through predefined workflow nodes and a graphical interface.

[0066] Furthermore, conduct a business requirements analysis, refer to industry standards, determine common business processes and functional requirements, design the specific functions, input and output parameters, and configuration options of each node, write front-end visualization components and back-end logic code, and conduct integration testing to ensure correct functionality and stable performance;

[0067] It should be noted that the specific functions of each node include business logic, data storage, integration capabilities, error handling, and configuration options;

[0068] Encapsulate the nodes into reusable components and standardize the interfaces, write user documentation and developer documentation, and create a predefined workflow node library;

[0069] Based on the initialized project, through the predefined workflow node library in the low-code platform, add the workflow nodes required for the project from the predefined workflow node library to the graphical area, configure the parameters of each node according to the functional requirements and business logic of the workflow nodes, and use connection lines to connect the nodes to generate a coherent workflow;

[0070] It should be noted that the functional requirements of the workflow nodes include user interface, data input and output, data storage, data processing, integration performance requirements, and security requirements;

[0071] It should also be noted that the business logic of the workflow nodes includes data verification, business rules, data processing, and permission management.

[0072] S3. Real-time synchronize all changes to the workflow and record them.

[0073] Through the collaborative editing function, make changes to the workflow connection lines, node configurations, front-end visualization components, back-end logic code, and user permissions;

[0074] Furthermore, the low-code platform automatically enables the real-time synchronization function. When multiple team members edit the same workflow simultaneously, it updates the views of each team member in real time to ensure that all team members can see the latest workflow status on the same graphical area;

[0075] It should be noted that the real-time synchronization function is achieved through the collaborative editing engine, locking mechanism, notification system, and efficient front-end and back-end communication technologies built into the low-code platform;

[0076] If multiple team members edit the same node simultaneously, the low-code platform locks this part when a team member edits a node through the real-time synchronization function, preventing other team members from editing simultaneously. When the team member finishes editing and saves, the lock is released, and other team members can continue editing;

[0077] The low-code platform records every operation of team members through the logging function, generating operation logs and change logs, recording the time, content, changer, and change description of each change;

[0078] It should also be noted that the logging function is implemented through the built-in logging module, event listener, log storage, and user interface of the low-code platform, used to record every operation and change of users, ensuring that all changes are traceable.

[0079] S4. Based on the change records, conduct experimental development on the sub-branch, review the experimental development of the sub-branch, and merge it into a new workflow according to the review results.

[0080] Furthermore, derive a sub-branch from the main branch of the workflow through the project management interface. In the visual workflow editing interface, select the created sub-branch, design and modify the workflow based on the change records according to the experimental requirements, select new nodes from the predefined workflow node library to the graphical area, configure the parameters of each node, and use connection lines to connect the nodes to form a coherent workflow;

[0081] It should be noted that the main branch of the workflow is generated during project initialization and is used as the main development line of the project by default, used to store stable and tested code;

[0082] Initiate a review request for the experimental development of the sub-branch. Conduct a review by calculating the overall quality score of the experimental development of the sub-branch. The expression is:

[0083] ;

[0084] where is the overall quality score of the experimental development of the sub-branch, is the serial number of the change, is the total number of changes, is the weight of the th change, is the th change's priority, which is a positive integer representing the importance and urgency of the change, is the th change's complexity, is the th change's data volume;

[0085] It should be noted that the calculation process of the expression is as follows. For each change , calculate the ratio of its complexity to the data volume and the ratio of the weight to the priority , then multiply these two ratios and take the logarithm , and finally add up the scores of all changes and divide by the total number of changes to obtain the overall quality score .

[0086] Based on the project requirements and standards, set a threshold ;

[0087] When , it means that the change passes the review;

[0088] When , it means that the change fails the review and needs to be further modified or re-evaluated;

[0089] Experimentally develop the sub-branch that passes the review and merge it with the main branch of the workflow into a new workflow;

[0090] S5. Start the new workflow for testing, debug based on the test results, and obtain the final workflow.

[0091] Furthermore, based on the production environment, generate a test environment on the low-code platform, deploy the new workflow to the test environment using an automated deployment tool, write test cases according to the functional requirements and business logic of the new workflow to ensure that the test cases cover various possible inputs and boundary conditions, and run the test cases one by one in the test environment to test the new workflow. The expression is:

[0092] It should be noted that the test cases include input data, expected output, and verification points;

[0093] ;

[0094] Among them, represents the test score, represents the total number of test cases, represents the accuracy weight coefficient, represents the th accuracy score of the test case, represents the coverage weight coefficient, represents the th coverage score of the test case, is the serial number of the test case;

[0095] It should also be noted that the calculation process of the expression is as follows. Calculate the accuracy score multiplied by the weight coefficient , calculate the coverage score Multiply by the weight coefficient Sum up the scores of all test cases and divide the sum by the total number of test cases , to obtain the final test score .

[0096] Based on historical data and team experience, set a reasonable threshold ,

[0097] When , it indicates that the new workflow passes the test;

[0098] When , it indicates that further debugging and optimization are required;

[0099] Based on the test results, use the debugging tools provided by the low-code platform to gradually check each step of the workflow, adjust the node parameters and optimize the logic to make the process more efficient and stable, and obtain the final workflow;

[0100] It should also be noted that the debugging tools provided by the low-code platform include log viewing, breakpoint debugging, variable monitoring, and exception capture.

[0101] S6. Deploy the final workflow to the production environment, monitor the running status of the final workflow in real time, and continuously iterate and improve the final workflow based on the monitoring data and user feedback.

[0102] Furthermore, formulate a deployment plan by selecting low-load time periods and rollback strategies, and use CD tools for automated deployment;

[0103] It should be noted that the rollback strategy is formulated through backup mechanisms, version control, real-time monitoring and alerting, gradual deployment, defining rollback conditions, automated scripts, and manual rollback plans;

[0104] View various monitoring metrics in real time through the monitoring dashboard, regularly check the monitoring data, use Splunk to automatically collect and store the monitoring data, use the process automation function to send a satisfaction questionnaire to users, and collect user feedback on the final workflow;

[0105] Analyze the collected user feedback through data analysis tools and visualization dashboards to understand user experience issues during use, analyze the collected monitoring data, and discover performance issues, functional issues, and stability issues during use;

[0106] Based on the user feedback and the analysis results of the monitoring data, formulate improvement measures and continuously iterate and improve to ensure that the workflow is always in the best state.

[0107] It should also be noted that formulating improvement measures includes:

[0108] Improve the user experience by optimizing the interface, interaction, and response time;

[0109] Optimize the performance by optimizing the code, database, cache strategy, and load balancing;

[0110] Improve the functions by adding new functions, fixing bugs, and enhancing functions;

[0111] Improve the stability by improving the error handling mechanism, introducing redundant design, and enhancing the logging function.

[0112] This embodiment also provides a software development system based on a low-code platform, as Figure 2 shown, including: a project initialization module, a design and editing module, a change management module, a change review module, a test and debugging module, and a monitoring and continuous improvement module;

[0113] The project initialization module is used to automatically generate an initialization project based on project requirements;

[0114] The design and editing module is used to design a workflow based on the initialization project through predefined workflow nodes and a graphical interface;

[0115] The change management module is used to synchronize and record all changes to the workflow in real time;

[0116] The change review module is used to conduct experimental development on sub-branches based on the change records, review the experimental development on sub-branches, and merge them into a new workflow according to the review results;

[0117] The test and debugging module is used to start testing the new workflow, debug based on the test results, and obtain the final workflow;

[0118] The monitoring and continuous improvement module is used to deploy the final workflow to the production environment, monitor the running status of the final workflow in real time, and continuously iterate and improve the final workflow based on the monitoring data and user feedback.

[0119] The following conducts relevant experiments to further verify the effectiveness of the technical solution of the present invention.

[0120] (1) Comparison of the generation efficiency of workflow nodes.

[0121] Experimental Background: In the software development process, generating and configuring workflow nodes is a crucial step in implementing business logic. Traditional coding methods require developers to write a large amount of code to implement the functional logic and parameter configuration of each node, which is often time-consuming and laborious. This experiment verifies the advantages of the low-code platform in automated configuration by comparing the differences in node generation efficiency between the low-code platform and traditional coding methods.

[0122] Experimental Method: As Figure 3 shown, use the low-code platform and traditional coding methods to generate 0 to 100 nodes respectively, with the number of generated nodes increasing by 10 each time. Record the total time taken to generate and configure nodes for each method, and depict the generation efficiency curve with time data.

[0123] Result Analysis: The experimental data shows that as the number of nodes increases, the time consumed by the low-code platform in generating and configuring nodes is significantly lower than that of traditional coding methods. Specifically, when the number of generated nodes is 50, the low-code platform takes about 15 seconds, while traditional coding methods take about 45 seconds. When the number of generated nodes increases to 100, the low-code platform takes only about 23 seconds, while traditional coding methods take up to 65 seconds.

[0124] Conclusion: The generation speed of the low-code platform is about 3 times faster than that of traditional coding methods, significantly shortening the development time. This indicates that the low-code platform has obvious advantages in node generation and configuration automation.

[0125] (2) Comparison of collaborative development models.

[0126] Experimental Background: In modern software development, collaborative development is a common scenario. Especially when multiple developers work on the same project, real-time synchronization and version management become key factors. Traditional development models usually lack real-time synchronization mechanisms, and developers need to communicate and coordinate manually continuously, which is prone to conflicts and synchronization delays. This experiment verifies the real-time synchronization advantages of the low-code platform in multi-person collaboration scenarios by comparing the low-code platform and the manual coordination mode without a synchronization mechanism.

[0127] Experimental Method: As Figure 4 shown, simulate the real-time editing scenario of three team members in the same workflow, and compare the real-time synchronization mechanism of the low-code platform with the non-synchronization mechanism (manual communication method). Record the average synchronization time under different numbers of editing sessions.

[0128] Result Analysis: The experimental results show that the real-time synchronization mechanism of the low-code platform greatly reduces the collaboration latency among team members. In the editing environment of 3 sessions, the average synchronization latency of the low-code platform is 0.6 seconds, while the average latency of manual synchronization without a synchronization mechanism is 30 seconds. As the number of editing sessions increases, the low-code platform maintains low latency, and the latency hardly increases with the increase in the number of sessions, while the latency increase of the non-synchronization mechanism is more significant.

[0129] Conclusion: In multi-person collaborative development, the low-code platform significantly improves collaboration efficiency through real-time synchronization, avoids editing conflicts and delays, and effectively meets the high-efficiency collaboration needs of modern development.

[0130] (3) Change Review and Quality Control.

[0131] Experimental Background: In complex projects, branch management and change review are the core to ensure code quality. Especially for experimental development, a good change review mechanism can ensure that only code meeting quality requirements is merged into the main branch, thereby improving the stability and reliability of the system. This experiment compares the quality review results of the main branch and sub-branches of the low-code platform to verify its effectiveness in change management and quality control.

[0132] Experimental Method: As Figure 5 shown, experimental development is carried out on the main branch and 5 sub-branches of the project, and quality review is conducted after each sub-branch is completed. The quality review comprehensively calculates scores based on factors such as the change weight, priority, complexity, and data volume of the branch. Record the quality scores of each branch and analyze the merging quality of the main branch and sub-branches.

[0133] Result Analysis: The quality scores of the main branch and each sub-branch show that the change review mechanism of the low-code platform can effectively guarantee branch quality. The quality score of the main branch is 93, meeting the preset quality requirements of the project. The quality scores of each sub-branch are 89, 91, 92, 95, and 90 points respectively, all reaching the set merging quality threshold.

[0134] Conclusion: The low-code platform performs excellently in quality control. Its branch review and change management functions ensure the stability and high quality of the main branch.

[0135] The software development method and system based on the low-code platform of the present invention significantly improve development efficiency, collaboration ability, and the accuracy of change management. The experimental results show that the solution of the present invention has good support for complex business logics and multi-person collaboration scenarios, can effectively reduce development costs, and improve system stability and scalability.

[0136] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit them. Although the present invention has been described in detail with reference to the preferred embodiments, those of ordinary skill in the art should understand that the technical solutions of the present invention can be modified or equivalently replaced without departing from the spirit and scope of the technical solutions of the present invention, and they should all be covered within the scope of the claims of the present invention.

Claims

1. A software development method based on a low-code platform, characterized in that: The following steps are involved: S1. Automatically generate initialization projects based on project requirements; S2. Based on the initialization project, design the workflow through predefined workflow nodes and graphical interface; S3. Synchronize and record all changes in the workflow in real time; specifically: Through collaborative editing, changes can be made to workflow connections, node configurations, front-end visual components, back-end logic codes, and user permissions; The low-code platform automatically enables the real-time synchronization function. When multiple team members edit the same workflow at the same time, each team member's view is updated in real time to ensure that all team members see the latest workflow status in the same graphical area; If multiple team members edit the same node at the same time, the low-code platform uses the real-time synchronization function to lock this part when a team member edits a node, preventing other team members from editing at the same time. When the team member completes the editing and saves, the lock will be released and other team members can continue editing. The low-code platform uses the log function to record every operation of team members, generate operation logs and change logs, and record the time, content, changer, and change description of each change; S4. Based on the change record, conduct experimental development of sub-branches, review the experimental development of sub-branches, and merge them into a new workflow based on the review results; specifically: Derive a sub-branch from the main branch of the workflow through the project management interface. In the visual workflow editing interface, select the created sub-branch. Based on the change record, design and modify the workflow according to the experimental requirements. Select new nodes from the predefined workflow node library to the graphical area, configure the parameters of each node, and use connecting lines to connect the nodes to form a coherent workflow. Initiate a sub-branch experimental development review request, and perform the review by calculating the overall quality score of the sub-branch experimental development. The expression is: ； in, is the overall quality score of the experimental development of the subbranch, is the serial number of the change, is the total number of changes, For the The weight of the change, For the The priority of a change is a positive integer that indicates the importance and urgency of the change. For the The complexity of the change, For the The amount of data changed; Set a threshold based on project requirements and standards ; when When it is displayed, it means that the change has passed the review; when When the change is not reviewed, it means that the change has not passed the review and needs further modification or re-evaluation; Merge the experimental development of the sub-branch that has passed the review and the main branch of the workflow into a new workflow; S5. Start the new workflow for testing, debug based on the test results, and get the final workflow; specifically: Generate a test environment on the low-code platform based on the production environment, use the automated deployment tool to deploy the new workflow to the test environment, write test cases based on the functional requirements and business logic of the new workflow, run the test cases one by one in the test environment, and test the new workflow. The expression is: ； in, Represents the test score, Represents the total number of test cases, represents the accuracy weight coefficient, Indicates The accuracy score of the test cases, represents the coverage weight coefficient, Indicates The coverage score of the test cases, is the serial number of the test case; Set thresholds based on historical data and team experience ; when , it means the new workflow has passed the test; when When , it indicates that further debugging and optimization are needed; Based on the test results, use the debugging tools provided by the low-code platform to check each step of the workflow step by step, adjust node parameters and optimize logic to obtain the final workflow; S6. Deploy the final workflow to the production environment, monitor the running status of the final workflow in real time, and continuously iterate and improve the final workflow based on monitoring data and user feedback.

2. According to a software development method based on a low-code platform according to claim 1, it is characterized in that: S1 is specifically: Collect and organize requirements documents through kick-off meetings, demand research, existing process analysis, business process determination and technical requirements discussion; Based on the requirements document, clarify the project goals, list the functional requirements and describe their input, output and processing logic, determine the technical architecture and performance indicators, and consider security and compliance requirements to finally obtain the project requirements; Use automation scripts to automatically generate initialization projects based on project requirements.

3. According to a software development method based on a low-code platform according to claim 2, it is characterized in that: S2 is specifically: Conduct business needs analysis and refer to industry standards to determine common business processes and functional requirements, design specific functions, input and output parameters, and configuration options for each node, write front-end visual components and back-end logic code, and perform integration testing to ensure correct functionality and stable performance; Encapsulate nodes into reusable components and standardize interfaces, write user and developer documentation, and create a library of predefined workflow nodes; Based on the initialization project, through the predefined workflow node library in the low-code platform, add the workflow nodes required by the project from the predefined workflow node library to the graphical area, configure the parameters of each node according to the functional requirements and business logic of the workflow node, and use connecting lines to connect the nodes to generate a coherent workflow.

4. According to a software development method based on a low-code platform according to claim 1, it is characterized in that: S6 is specifically: Develop deployment plans by selecting low-load time periods and rollback strategies, and use CD tools to automate deployments; View various monitoring indicators in real time through the monitoring dashboard, check monitoring data regularly, use Splunk to automatically collect and store monitoring data, use the process automation function to send satisfaction surveys to users, and collect user feedback on the final workflow; Analyze the collected user feedback through data analysis tools and visual dashboards to understand the user experience problems during use, and analyze the collected monitoring data to find performance problems, functional problems, and stability problems during use; Based on user feedback and monitoring data analysis results, we formulate improvement measures and continuously iterate and improve.

5. A software development system based on a low-code platform, characterized in that: Used to implement the method described in any one of claims 1 to 4, comprising a project initialization module, a design and editing module, a change management module, a change review module, a test and debugging module, and a monitoring and continuous improvement module; The project initialization module is used to automatically generate an initialization project according to project requirements; The design and editing module is used to design a workflow based on an initialization project through predefined workflow nodes and a graphical interface; The change management module is used to synchronize and record all changes in the workflow in real time; The change review module is used to perform sub-branch experimental development based on the change record, review the sub-branch experimental development, and merge into a new workflow based on the review results; The testing and debugging module is used to start a new workflow for testing, debug based on the test results, and obtain the final workflow; The monitoring and continuous improvement module is used to deploy the final workflow into the production environment, monitor the running status of the final workflow in real time, and continuously iterate and improve the final workflow based on monitoring data and user feedback.

Images