Software development method and system based on low-code platform

Abstract

The invention belongs to the field of software engineering, and discloses a software development method and system based on a low-code platform, and the method comprises the steps: automatically generating an initialization project through a project demand; designing a workflow through a predefined workflow node and a graphical interface based on the initialization item; synchronizing and recording all changes of the workflow in real time; performing sub-branch experimental development based on the change record, reviewing the sub-branch experimental development, and combining into a new workflow according to a reviewing result; starting the new workflow for testing, and debugging based on a test result to obtain a final workflow; and deploying the final workflow into a production environment, monitoring the running state of the final workflow in real time, and continuously iterating and improving the final workflow based on monitoring data and user feedback. According to the method, all changes of the workflow are synchronized in real time and recorded by performing sub-branch experimental development and examination based on the change records, so that the team cooperation efficiency and the version control capability are improved.

Description

Technical Field

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

[0002] In recent years, with the growing demand for software development and the rapid development of technology, low-code platforms have gradually attracted widespread attention as an efficient software development tool. Low-code platforms enable non-professional developers to quickly build complex applications by providing a visual development environment and predefined component libraries. These platforms usually support functions such as drag-and-drop interface design, automated script generation, real-time synchronization, and change management, which greatly improves development efficiency and reduces development costs. In addition, low-code platforms also provide rich integration capabilities and scalability, allowing developers to easily integrate various services and systems into workflows.

[0003] Although existing low-code platforms have performed well in improving development efficiency, they often lack sufficient flexibility and customizability when dealing with complex business logic and functional requirements. Although the predefined components and templates provided by many platforms can meet basic needs, they have limited support for specific industries or complex application scenarios, resulting in developers having to perform a lot of manual coding and debugging when implementing certain advanced functions, which not only increases the difficulty of development but also prolongs the development cycle. This not only affects development efficiency, but can 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 deficiencies in flexibility and customizability of the prior art and improves development efficiency and system stability.

[0005] The present invention provides a software development method based on a low-code platform, comprising the following steps: 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; 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; S5. Start the new workflow for testing, debug based on the test results, and 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.

[0006] As a preferred solution of the software development method based on the low-code platform described in the present invention, 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.

[0007] As a preferred solution of the software development method based on the low-code platform described in the present invention, 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.

[0008] As a preferred solution of the software development method based on the low-code platform described in the present invention, S3 is 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 to prevent 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 step of the team members' operations, generate operation logs and change logs, and record the time, content, changer and change description of each change.

[0009] As a preferred solution of the software development method based on the low-code platform described in the present invention, S4 is 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.

[0010] As a preferred solution of the software development method based on the low-code platform described in the present invention, S5 is 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 step through each step of the workflow, adjust node parameters and optimize the logic to make the process more efficient and stable, and obtain the final workflow.

[0011] As a preferred solution of the software development method based on the low-code platform described in the present invention, 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.

[0012] 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 and record all changes to the workflow in real time; the change review module is used to perform experimental development of sub-branches based on change records, review the experimental development of sub-branches, and merge them 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 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.

[0013] The beneficial effects of the present invention are as follows: the present invention realizes flexible testing and verification in an independent environment through the steps of experimental development and review of sub-branches based on change records, 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 steps of synchronizing all changes and recording the workflow in real time, the present invention supports multi-person collaboration, prevents editing conflicts, and provides a detailed change history, thereby improving team collaboration efficiency and version control capabilities. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying creative work.

[0015] Figure 1 A flowchart of the software development method based on the low-code platform in Example 1; Figure 2 This is a schematic diagram of the structure of the software development system based on the low-code platform in Example 1; Figure 3 A comparison chart of workflow node generation efficiency between the present invention and the traditional encoding method; Figure 4 A comparison diagram of the collaborative development mode of the present invention and the traditional development mode; Figure 5 It is a quality control schematic diagram of the present invention. DETAILED DESCRIPTION

[0016] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are described in detail below in conjunction with the accompanying drawings.

[0017] In the following description, many specific details are set forth to facilitate a full understanding of the present invention, but the present invention may also be implemented in other ways different from those described herein, and those skilled in the art may make similar generalizations without violating the connotation of the present invention. Therefore, the present invention is not limited to the specific embodiments disclosed below.

[0018] Secondly, the term "one embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the present invention. The term "in one embodiment" that appears in different places in this specification does not necessarily refer to the same embodiment, nor does it refer to a separate or selective embodiment that is mutually exclusive with other embodiments.

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

[0020] S1. Automatically generate initialization projects based on project requirements.

[0021] Furthermore, through kick-off meetings, demand research, existing process analysis, business process determination and technical requirements discussion, requirements documents are collected and organized; 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 automated scripts to automatically generate initialization projects based on project requirements; It should be noted that the automation script is written by using Shell scripts based on the functions required to create the project; 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 dependent libraries, and configuring a development environment.

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

[0023] Furthermore, we conduct business needs analysis and refer to industry standards to identify 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; It should be noted that the specific functions of each node include business logic, data storage, integration capabilities, error handling, and configuration options; 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, add the workflow nodes required by the project from the predefined workflow node library in the low-code platform 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; It should be noted that the functional requirements of workflow nodes include user interface, data input and output, data storage, data processing, integration performance requirements, and security requirements; It should also be noted that the business logic of the workflow node includes data validation, business rules, data processing and permission management.

[0024] S3. Synchronize and record all changes in the workflow in real time.

[0025] Through collaborative editing, changes can be made to workflow connections, node configurations, front-end visual components, back-end logic codes, and user permissions; Furthermore, the low-code platform automatically enables real-time synchronization, which updates each team member’s view in real time when multiple team members are editing the same workflow at the same time, ensuring that all team members see the latest workflow status on the same graphical area; It should be noted that the real-time synchronization function is achieved through the low-code platform’s built-in collaborative editing engine, locking mechanism, notification system, and efficient front-end and back-end communication technology; 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 to prevent 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 step of the team members' operations, generate operation logs and change logs, and record the time, content, changer, and change description of each change; It should also be noted that the logging function is implemented through the low-code platform's built-in logging module, event listener, log storage and user interface, which is used to record every operation and change of the user to ensure that all changes can be traced.

[0026] 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.

[0027] Furthermore, a sub-branch is derived from the main branch of the workflow through the project management interface. In the visual workflow editing interface, the created sub-branch is selected. Based on the change record, the workflow is designed and modified according to the experimental requirements. New nodes are selected from the predefined workflow node library to the graphical area, the parameters of each node are configured, and the nodes are connected using connecting lines to form a coherent workflow; It should be noted that the workflow main branch is generated when the project is initialized. It is used as the main development line of the project by default and is used to store stable and tested code. 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; 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 amount of data and the ratio of weight to 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 , get the overall quality score .

[0028] 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;

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

[0030] Furthermore, a test environment is generated on the low-code platform based on the production environment, and the new workflow is deployed to the test environment using automated deployment tools. Test cases are written according to the functional requirements and business logic of the new workflow to ensure that the test cases cover all possible inputs and boundary conditions. The test cases are run one by one in the test environment to test the new workflow. The expression is: It should be noted that test cases include input data, expected outputs, and verification points; ; 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; It should also be noted that the calculation process of the expression is as follows, and the accuracy score is calculated Multiply by the weight factor , calculate the coverage score Multiply by the weight factor The sum of all test case scores divided by the total number of test cases , get the final test score .

[0031] Set a reasonable threshold 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 make the process more efficient and stable, and obtain the final workflow; 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.

[0032] 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.

[0033] Going a step further, you can create a deployment plan by selecting low-load time periods and rollback strategies, and use CD tools to automate deployment; It should be noted that the rollback strategy is developed through backup mechanisms, version control, real-time monitoring and alerting, gradual deployment, definition of rollback conditions, automated scripts, and manual rollback plans; 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 develop improvement measures, continuously iterate and improve to ensure that the workflow is always in optimal condition.

[0034] It should also be noted that the development of improvement measures includes: Improve user experience through interface optimization, interaction optimization and response time optimization; Optimize performance through code optimization, database optimization, cache strategy and load balancing; Improve functionality through new features, feature fixes, and enhancements; Improved stability through improved error handling, redundant design, and enhanced logging.

[0035] This embodiment also provides a software development system based on a low-code platform, such as Figure 2 As shown, it includes: project initialization module, design and editing module, change management module, change review module, testing and debugging module and monitoring and continuous improvement module; Project initialization module, used to automatically generate initialization projects based on project requirements; Design and edit module, used to design workflows based on initialization projects through predefined workflow nodes and graphical interfaces; Change management module, used to synchronize and record all changes in workflows in real time; The change review module is used to conduct experimental development of sub-branches based on change records, review the experimental development of sub-branches, and merge them 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 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.

[0036] The following is a further verification of the effect of the technical solution of the present invention through relevant experiments.

[0037] (1) Comparison of workflow node generation efficiency.

[0038] Experimental background: In the software development process, generating and configuring workflow nodes is a key step in implementing business logic. Traditional coding methods require developers to write a lot 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 low-code platforms in automated configuration by comparing the differences in node generation efficiency between low-code platforms and traditional coding methods.

[0039] Experimental method: Figure 3 As shown in the figure, 0 to 100 nodes are generated using the low-code platform and traditional coding methods, and the number of nodes generated increases by 10 each time. The total time taken to generate and configure nodes in each method is recorded, and the generation efficiency curve is drawn with time data.

[0040] Result analysis: Experimental data shows that as the number of nodes increases, the time spent on generating and configuring nodes by the low-code platform is significantly lower than that of the traditional coding method. Specifically, when the number of generated nodes is 50, the low-code platform takes about 15 seconds, while the traditional coding method takes about 45 seconds. When the number of generated nodes increases to 100, the low-code platform takes only about 23 seconds, while the traditional coding method takes 65 seconds.

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

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

[0043] 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, which is prone to conflicts and synchronization delays. This experiment verifies the real-time synchronization advantages of low-code platforms in multi-person collaboration scenarios by comparing low-code platforms with manual coordination modes without synchronization mechanisms.

[0044] Experimental method: Figure 4 As shown in the figure, a real-time editing scenario of three team members in the same workflow is simulated to compare the real-time synchronization mechanism of the low-code platform with the no synchronization mechanism (manual communication method). The average synchronization time under different numbers of editing sessions is recorded.

[0045] Results analysis: The experimental results show that the real-time synchronization mechanism of the low-code platform greatly shortens the collaboration delay between team members. In the editing environment of three sessions, the average synchronization delay of the low-code platform is 0.6 seconds, while the average delay 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 without a synchronization mechanism increases significantly.

[0046] 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 efficient collaboration needs of modern development.

[0047] (3) Change review and quality control.

[0048] Experimental background: In complex projects, branch management and change review are the core of ensuring code quality. Especially for experimental development, a good change review mechanism can ensure that only code that meets 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-branch of the low-code platform to verify its effectiveness in change management and quality control.

[0049] Experimental method: Figure 5 As shown in the figure, experimental development is carried out on the main branch and five sub-branches of the project, and a quality review is conducted after each sub-branch is completed. The quality review is based on the branch's change weight, priority, complexity, data volume and other factors to calculate the score. The quality score of each branch is recorded, and the quality of the merger between the main branch and the sub-branch is analyzed.

[0050] 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 ensure the quality of the branch. The quality score of the main branch is 93, which meets 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 merge quality threshold.

[0051] Conclusion: The low-code platform performs well in quality control, and its branch review and change management capabilities ensure the stability and high quality of the main branch.

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

[0053] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that the technical solutions of the present invention may be modified or replaced by equivalents without departing from the spirit and scope of the technical solutions of the present invention, which should all be included in 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; 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; S5. Start the new workflow for testing, debug based on the test results, and 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. A software development method based on a low-code platform according to claim 3, characterized in that: S3 is 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 step of the team members' operations, generate operation logs and change logs, and record the time, content, changer and change description of each change.

5. A software development method based on a low-code platform according to claim 4, characterized in that: S4 is 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 indicating 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 , 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.

6. A software development method based on a low-code platform according to claim 5, characterized in that: S5 is as follows: 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 step through each step of the workflow, adjust node parameters and optimize the logic to obtain the final workflow.

7. A software development method based on a low-code platform according to claim 6, 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.

8. 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 7, 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