Low-code development platform construction method based on data service modeling engine

Abstract

The invention provides a low-code development platform construction method based on a data service modeling engine, and belongs to the technical field of low-code development, and the method comprises the steps: obtaining an engine application scene, determining an existing user group according to the engine application scene, determining a corresponding existing demand, and constructing a low-code development platform. The method comprises the following steps of: obtaining a core function of the platform, disassembling the core function to obtain a plurality of sub-functions, developing a data model according to the sub-functions, constructing an overall framework of the low-code development platform, performing dependency relationship analysis on the data model, integrating the data model, and determining a business model by combining the overall framework and an integration result; the application scene template is selected based on the business model, the template parameter is configured, the data field in the business model and the template parameter are mapped, and the business model is published to the low-code development platform, so that the development efficiency is improved, non-technical users can quickly construct and publish the application and flexibly cope with the change of business requirements; and innovation and response speed are promoted.

Description

Technical Field

[0001] The present invention relates to the field of low-code development technology, and in particular to a method for constructing a low-code development platform based on a data business modeling engine. Background Art

[0002] As digital transformation accelerates, enterprises are increasingly demanding rapid development and deployment of applications. Traditional software development methods often require a lot of time and resources, and require developers to have a high level of technical skills, making it difficult for non-technical personnel to participate in application development, thus limiting the speed and flexibility of business innovation.

[0003] Therefore, the present invention provides a method for constructing a low-code development platform based on a data business modeling engine. Summary of the invention

[0004] The present invention provides a method for building a low-code development platform based on a data business modeling engine. The method obtains engine application scenarios, identifies user groups and their needs, determines core functions, decomposes core functions into sub-functions, develops corresponding data models, and performs dependency analysis and integration. Finally, the method selects and configures application scenario templates based on the business model, realizes dynamic mapping and publishes them to the low-code platform, thereby improving development efficiency, lowering technical barriers, enabling non-technical users to quickly build and publish applications, flexibly respond to changes in business needs, and promoting innovation and response speed.

[0005] The present invention provides a method for constructing a low-code development platform based on a data business modeling engine, comprising: Step 1: Obtain the engine application scenario, determine the existing user group according to the engine application scenario, determine the corresponding existing needs based on the existing user group, and then derive the core functions of the platform; Step 2: Decompose the core function to obtain multiple sub-functions, develop a data model based on the sub-functions, and then build the overall architecture of the low-code development platform; Step 3: Analyze the dependency of the data model, integrate the data model according to the dependency, and determine the business model in combination with the overall architecture and the integration result; Step 4: Select an application scenario template based on the business model and configure the template parameters, map the data fields in the business model with the template parameters, and publish the business model to the low-code development platform based on the mapping results.

[0006] The present invention provides a method for constructing a low-code development platform based on a data business modeling engine, obtaining an engine application scenario, determining an existing user group according to the engine application scenario, determining corresponding existing needs based on the existing user group, and then deriving the core functions of the platform, including: Obtain relevant products in the current market, analyze market trends based on the relevant products, determine engine application scenarios using market trend analysis results, and determine existing user groups based on the engine application scenarios and the market trends; A first division is performed on the existing user groups according to the company size to obtain a first monomer; a second division is performed on the existing user groups according to the user roles to obtain a second monomer; A feature analysis is performed on the first monomer and the second monomer, and the existence needs of different user groups are determined according to the feature analysis results, and then the corresponding platform core functions are determined.

[0007] The present invention provides a method for constructing a low-code development platform based on a data business modeling engine, which decomposes the core function to obtain multiple sub-functions, develops a data model according to the sub-functions, and then constructs the overall architecture of the low-code development platform, including: Decomposing the workflow of the core function, determining the sub-functions corresponding to the core function, and identifying the achievable sub-functions among all sub-functions based on the function realization table; Determine the architecture design principles according to the engine application scenario, determine the platform architecture style based on the architecture design principles, and determine the hierarchical division of the platform according to the platform architecture style; Use the hierarchical division results to locate the achievable sub-functions, and develop the corresponding data model based on the location results; The overall architecture of the low-code development platform is determined by comprehensive hierarchical division and data model.

[0008] The present invention provides a method for constructing a low-code development platform based on a data business modeling engine, determining an architecture design principle according to an engine application scenario, and determining a platform architecture style based on the architecture design principle, including: Create multiple usage scenarios based on the engine application scenario, create corresponding user stories for each usage scenario according to the user role, extract principle conditions from the user stories, and determine the architecture design principles by combining all principle conditions; Evaluate different architectural styles based on architectural design principles, analyze the focus of different architectural styles for each usage scenario, and then determine the platform architectural style of the low-code development platform.

[0009] The present invention provides a method for constructing a low-code development platform based on a data business modeling engine, which performs dependency analysis on data models, integrates data models according to the dependencies, and determines a business model in combination with the overall architecture and the integration results, including: Constructing a data matrix based on the data model, setting a scoring system, and determining the dependency relationship between the data model according to the data matrix and the scoring system; Determine business requirements based on core functions, assign different weights to each dependency based on the importance of business requirements and corresponding data models, calculate the total weight of each data model and identify key models; A model integration plan is formulated based on the key model of the dependency judgment result, the data model is integrated according to the model integration plan, and then the business model is determined in combination with the overall architecture.

[0010] The present invention provides a method for constructing a low-code development platform based on a data business modeling engine, and formulates a model integration plan based on a key model of a dependency judgment result, including: Build a dependency graph based on the dependency judgment result and the key model, use the key model as the first sorting model, calculate the in-degree of the remaining data models, record the data model with in-degree 0 as the second-level sorting model, and the data model with in-degree non-0 as the third-level sorting model; After integrating the first-level sorting model and the second-level sorting model into the dependency graph, recalculate the in-degree of the third-level sorting model to obtain a new second-level sorting model, and integrate the new second-level sorting model into the dependency graph until the number of third-level sorting models becomes 0, then the sorting ends; The model integration plan is derived based on the sorting results and the dependency graph.

[0011] The present invention provides a method for constructing a low-code development platform based on a data business modeling engine, selecting an application scenario template based on a business model, configuring template parameters, mapping data fields in the business model with template parameters, and publishing the business model to the low-code development platform according to the mapping result, including: Select an application scenario template from the business-scenario template library based on the business requirements corresponding to the business model, and set template parameters according to the business requirements; Identify data fields in the business model, screen the data fields based on the business requirements, and determine the fields to be mapped; Based on the fields to be mapped and the template parameters, mapping is performed, and then the business template is published to the low-code development platform.

[0012] The present invention provides a method for constructing a low-code development platform based on a data business modeling engine, which maps the to-be-mapped fields with template parameters, including: ,in, Represents the mapping result at time t; Represents data conversion function g The derivative of f Indicates the field to be mapped With template parameters The mapping function of Indicates the field to be mapped at time t; Represents dynamic parameters; Represents the template parameters at time t; Indicates the rate of change of the field to be mapped over time t; Indicates that while keeping other variables unchanged, the template parameters The degree of impact on the mapping results; Indicates that the fields to be mapped remain unchanged while keeping other variables unchanged. The degree of impact on the mapping results; Indicates the dynamic change of the i-th template parameter over time; Represents the i-th parameter in the template parameter.

[0013] Compared with the existing technology, the beneficial effects of this application are as follows: by obtaining engine application scenarios, identifying user groups and their needs, determining core functions, breaking down core functions into sub-functions, developing corresponding data models, and performing dependency analysis and integration, finally selecting and configuring application scenario templates based on business models, realizing dynamic mapping and publishing to low-code platforms, improving development efficiency, lowering technical barriers, enabling non-technical users to quickly build and publish applications, flexibly responding to changes in business needs, and promoting innovation and response speed.

[0014] Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or understood by practicing the present invention. The purpose and other advantages of the present invention can be realized and obtained by the structures particularly pointed out in the written description and the accompanying drawings.

[0015] The technical solution of the present invention is further described in detail below through the accompanying drawings and embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The accompanying drawings are used to provide a further understanding of the present invention and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the present invention and do not constitute a limitation of the present invention. In the accompanying drawings: Figure 1 It is a flow chart of a method for building a low-code development platform based on a data business modeling engine provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0017] The preferred embodiments of the present invention are described below in conjunction with the accompanying drawings. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present invention, and are not used to limit the present invention.

[0018] Embodiment 1: The embodiment of the present invention provides a method for constructing a low-code development platform based on a data business modeling engine, such as Figure 1 As shown, including: Step 1: Obtain the engine application scenario, determine the existing user group according to the engine application scenario, determine the corresponding existing needs based on the existing user group, and then derive the core functions of the platform; Step 2: Decompose the core function to obtain multiple sub-functions, develop a data model based on the sub-functions, and then build the overall architecture of the low-code development platform; Step 3: Analyze the dependency of the data model, integrate the data model according to the dependency, and determine the business model in combination with the overall architecture and the integration result; Step 4: Select an application scenario template based on the business model and configure the template parameters, map the data fields in the business model with the template parameters, and publish the business model to the low-code development platform based on the mapping results.

[0019] In this embodiment, the engine application scenario refers to a product application scenario determined based on market trends and user needs, such as internal enterprise development tools, customer relationship management systems, data analysis dashboards, etc.

[0020] In this embodiment, the user group refers to a set of users who have potential demand for products or services, such as IT teams of small and medium-sized enterprises, developers of start-up companies, business analysts, etc.

[0021] In this embodiment, the existing demand is the specific demand of the user group in a specific scenario, for example, small business developers need simplified API integration functions and template libraries.

[0022] In this embodiment, the core function is the main function of the platform or system, which is usually the part that users are most concerned about. For example, in a low-code development platform, the core function may be "application construction", and the sub-function is that the core function can be broken down into multiple sub-functions to specifically implement a certain aspect of the function. For example, in "application construction", the sub-functions may include "user interface design", "data connection", "business logic implementation", etc.

[0023] In this embodiment, the data model is a model that describes data structures, relationships, and constraints, and is used to support the functions of the system. For example, in a low-code platform, the data model may include "user table", "application table", "data connection table", etc.

[0024] In this embodiment, the overall architecture of the low-code development platform is an architectural design of the entire low-code development platform formed by comprehensive hierarchical division and data model. For example, the overall architecture of a low-code platform may include a user interface layer, a business logic layer, and a data layer, and the layers interact with each other through APIs.

[0025] In this embodiment, by disassembling the core functions, the achievable sub-functions are identified, and the architectural design principles are formulated according to the engine application scenarios. The platform architecture style and hierarchical division are determined, and the hierarchical division results are used to locate the achievable sub-functions, and the corresponding data models are developed, so as to integrate these elements to form the overall architecture of the low-code development platform.

[0026] In this embodiment, the dependency relationship is the degree of mutual dependence between different data models, which is usually determined by a data matrix and a scoring system. For example, the order model depends on the customer model and the product model, which is expressed as: customer model (dependency: high), product model (dependency: medium).

[0027] In this embodiment, the business model is an overall architecture that supports business operations by integrating all data models and business requirements. For example, the business model may include a complete customer management system that covers modules such as customer information, order processing, and product management.

[0028] In this embodiment, by constructing a data matrix and setting a scoring system, the dependencies between data models are determined, business requirements are determined based on core functions, and weights are assigned to each dependency. The total weight of the data model is calculated to identify key models, and a model integration plan is formulated based on the key models. The data models are integrated to ultimately form a business model.

[0029] In this embodiment, template parameters are variables or options that can be configured in the application scenario template, which are used to customize the template to meet specific business needs. For example, in the "Order Processing Scenario Template", template parameters may include: payment method (credit card, Alipay, WeChat Pay), delivery method (express delivery, postal service, store pickup), order status (pending payment, shipped, completed).

[0030] In this embodiment, the application scenario template is a predefined template for implementing a specific business scenario, and usually includes structured processes and logic. For example, a "customer registration scenario template" may include a user information collection form, verification logic, and a feedback process after successful registration.

[0031] In this embodiment, a data field is a basic unit for storing data in a business model, and usually corresponds to a column in a database table. For example, in an "order model", data fields may include: order ID, customer ID, product ID, etc.

[0032] In this embodiment, by analyzing the business requirements corresponding to the business model, a suitable application scenario template is selected from the business-scenario template library, and the template parameters are set according to the requirements, the data fields in the business model are identified, the fields to be mapped are screened out, the fields to be mapped are mapped with the template parameters, and finally the business template is published to the low-code development platform.

[0033] The working principle and beneficial effects of the above technical solution are: by obtaining the engine application scenario, identifying user groups and their needs, determining the core functions, breaking down the core functions into sub-functions, developing corresponding data models, and performing dependency analysis and integration, and finally selecting and configuring application scenario templates based on the business model, dynamic mapping is achieved and published to the low-code platform, which improves development efficiency, lowers technical barriers, enables non-technical users to quickly build and publish applications, flexibly respond to changes in business needs, and promotes innovation and response speed.

[0034] Embodiment 2: The embodiment of the present invention provides a method for constructing a low-code development platform based on a data business modeling engine, obtaining an engine application scenario, determining an existing user group according to the engine application scenario, determining corresponding existing needs based on the existing user group, and then deriving the core functions of the platform, including: Obtain relevant products in the current market, analyze market trends based on the relevant products, determine engine application scenarios using market trend analysis results, and determine existing user groups based on the engine application scenarios and the market trends; A first division is performed on the existing user groups according to the company size to obtain a first monomer; a second division is performed on the existing user groups according to the user roles to obtain a second monomer; A feature analysis is performed on the first monomer and the second monomer, and the existence needs of different user groups are determined according to the feature analysis results, and then the corresponding platform core functions are determined.

[0035] In this embodiment, related products in the current market refer to products that are similar or related to the target product in a specific market. For example, if the goal is to develop a low-code development platform, related products may include other low-code platforms (such as OutSystems, Mendix) or automation tools (such as Zapier).

[0036] In this embodiment, market trends refer to the development direction and changes of products, services or technologies in the market. For example, market trends for low-code development platforms may include increasing demand for rapid development, visual interfaces and integration capabilities.

[0037] In this embodiment, the first division is a preliminary classification of user groups according to company size, for example, users are divided into small enterprises, medium-sized enterprises and large enterprises, and the first monomer is a subset of the user group obtained by the first division, for example, a small enterprise user group.

[0038] In this embodiment, the second division is a further classification of the user group according to user roles, for example, small business users are further divided into developers, project managers and business analysts, and the second monomer is a subset of the user group obtained by the second division, for example, developers in a small business.

[0039] In this embodiment, feature analysis is an in-depth analysis of the characteristics of the user group to understand their needs and behaviors, such as analyzing the skill level, usage frequency, and functional requirements of small business developers when using a low-code platform.

[0040] In this embodiment, the feature analysis results are conclusions and insights obtained through feature analysis, for example, small business developers are more inclined to use drag-and-drop interfaces and quick integration functions.

[0041] The working principle and beneficial effects of the above technical solution are: by analyzing relevant products on the market and identifying market trends, the engine application scenarios are determined, user groups are divided according to company size and user roles to form different entities, and user needs are identified through feature analysis, thereby clarifying the core functions of the platform, ensuring that the platform functions are closely aligned with market demand, and improving user satisfaction and market adaptability.

[0042] Embodiment 3: The embodiment of the present invention provides a method for constructing a low-code development platform based on a data business modeling engine, which decomposes the core function to obtain multiple sub-functions, develops a data model according to the sub-functions, and then constructs the overall architecture of the low-code development platform, including: Decomposing the workflow of the core function, determining the sub-functions corresponding to the core function, and identifying the achievable sub-functions among all sub-functions based on the function realization table; Determine the architecture design principles according to the engine application scenario, determine the platform architecture style based on the architecture design principles, and determine the hierarchical division of the platform according to the platform architecture style; Use the hierarchical division results to locate the achievable sub-functions, and develop the corresponding data model based on the location results; The overall architecture of the low-code development platform is determined by comprehensive hierarchical division and data model.

[0043] In this embodiment, the function implementation table is a document or table that lists all functions and their implementation status. For example, the table may contain "user interface design" that has been implemented, "data connection" that is under development, and "business logic implementation" that has not started.

[0044] In this embodiment, the achievable sub-functions are sub-functions that are identified from the function realization table and can be actually developed and realized. For example, if "user interface design" has been realized and "data connection" is being developed, then these two are achievable sub-functions.

[0045] In this embodiment, the architecture design principles are basic rules or standards guiding the system architecture design. For example, common architecture design principles include "modularity", "scalability", "maintainability", etc.

[0046] In this embodiment, the platform architecture style is a system architecture type or style determined according to architecture design principles, such as microservice architecture, monolithic architecture, event-driven architecture, etc.

[0047] In this embodiment, hierarchical division is to divide the system functions or architecture into different levels for easy management and development. For example, in a low-code platform, it can be divided into "presentation layer", "business logic layer" and "data access layer".

[0048] In this embodiment, function positioning is to determine the specific position and role of each achievable sub-function in the platform based on the hierarchical division results. For example, "user interface design" may be located in the "presentation layer" and "data connection" may span the "business logic layer" and "data access layer".

[0049] In this embodiment, the positioning result is a specific implementation path or structure of each sub-function formed based on the analysis of function positioning and hierarchical division. For example, "user interface design" in the presentation layer needs to call the "data connection" function to obtain data.

[0050] In this embodiment, the core function is decomposed to obtain multiple sub-functions. This modular design allows users to build applications by combining and configuring different functional modules without having to write code from scratch.

[0051] The working principle and beneficial effects of the above technical solution are: by disassembling the core functions, identifying the achievable sub-functions, and formulating architectural design principles according to the engine application scenarios, determining the platform architecture style and hierarchical division, and using the hierarchical division results to locate the achievable sub-functions, and developing the corresponding data model, these elements are integrated to form the overall architecture of the low-code development platform, thereby improving development efficiency and maintainability, and promoting the ability to quickly iterate and adapt to business changes.

[0052] Embodiment 4: The embodiment of the present invention provides a method for constructing a low-code development platform based on a data business modeling engine, determining an architecture design principle according to an engine application scenario, and determining a platform architecture style based on the architecture design principle, including: Create multiple usage scenarios based on the engine application scenario, create corresponding user stories for each usage scenario according to the user role, extract principle conditions from the user stories, and determine the architecture design principles by combining all principle conditions; Evaluate different architectural styles based on architectural design principles, analyze the focus of different architectural styles for each usage scenario, and then determine the platform architectural style of the low-code development platform.

[0053] In this embodiment, the usage scenario describes a specific scenario in which a user uses the system in a specific environment, typically including tasks, environment, and goals. For example, scenario 1: a user uses a low-code platform in the office to create a new customer management application, scenario 2: a user uses a mobile device to modify certain settings of an application while out.

[0054] In this embodiment, the user story describes the functions that the user hopes to achieve from the user's perspective, usually in the format of "as a [role], wanting [goal], so as to [benefit]". For example, the user story of scenario 1: as a sales manager, you want to quickly create a customer management application so that you can track customer information efficiently. The user story of scenario 2: as a project manager, you want to modify the application settings on the mobile device so that you can keep the application up to date when you are on a business trip.

[0055] In this embodiment, the principle conditions are specific requirements or constraints extracted from the user stories, which are usually conditions that need to be followed when implementing functions. For example, the principle conditions of scenario 1: the application must support multi-user collaboration, and the interface should be simple and easy to use; the principle conditions of scenario 2: the application needs to be responsive on mobile devices and support offline access.

[0056] In this embodiment, the architecture design principles are basic rules for guiding the system architecture design that are comprehensively extracted from all the principles and conditions. For example, Principle 1: The system must support high availability to meet the needs of multiple users at the same time. Principle 2: The system should have a good user experience to ensure smooth use on different devices.

[0057] In this embodiment, the architectural style is a system architecture type or style evaluated based on architectural design principles, such as microservice architecture: suitable for scenarios that require high scalability and independent deployment, and monolithic architecture: suitable for scenarios where a small team needs to develop and deploy quickly.

[0058] In this embodiment, the focus is on analyzing specific aspects emphasized by the architectural style for different usage scenarios. For example, in scenario 1, the focus of the microservice architecture may be distributed storage and processing of data to support multi-user access, while in scenario 2, the focus of the monolithic architecture may be rapid development and simplified maintenance.

[0059] In this embodiment, determining the platform architecture style of the low-code development platform is to comprehensively consider all analysis results and select the architecture style that best suits the low-code development platform. For example, according to the analysis, if multi-user collaboration and rapid development are the main requirements, a microservice architecture may be selected to facilitate expansion and maintenance. If rapid development and simple deployment are emphasized, a monolithic architecture may be selected.

[0060] The working principle and beneficial effects of the above technical solution are: by creating multiple usage scenarios based on the engine application scenario, and writing user stories for each scenario, principle conditions are extracted from them. After integrating these conditions, the architectural design principles are formed, different architectural styles are evaluated, and their focus in each usage scenario is analyzed, so as to determine the architectural style of the low-code development platform, improve the flexibility and scalability of the system, enhance the user experience, and promote the adaptability and sustainable development of the platform.

[0061] Embodiment 5: The embodiment of the present invention provides a method for constructing a low-code development platform based on a data business modeling engine, which performs dependency analysis on data models, integrates data models according to the dependencies, and determines a business model in combination with the overall architecture and the integration results, including: Constructing a data matrix based on the data model, setting a scoring system, and determining the dependency relationship between the data model according to the data matrix and the scoring system; Determine business requirements based on core functions, assign different weights to each dependency based on the importance of business requirements and corresponding data models, calculate the total weight of each data model and identify key models; A model integration plan is formulated based on the key model of the dependency judgment result, the data model is integrated according to the model integration plan, and then the business model is determined in combination with the overall architecture.

[0062] In this embodiment, the data matrix is ​​a structured table that shows the relationship and attributes between different data models. A data matrix may contain a "customer model", an "order model" and a "product model", and show the dependency relationship between them. If the data corresponding to the order model and the customer model is 2, it means that the order model has a high dependency on the customer model.

[0063] In this embodiment, the scoring system is a system for evaluating and scoring the importance and dependency of data models, usually based on multiple evaluation indicators. For example, the scoring system may include the following indicators: data integrity (1-10 points), access frequency (1-10 points), business impact (1-10 points). For example, the score of a customer model may be 8 (data integrity) + 7 (access frequency) + 9 (business impact) = 24 points.

[0064] In this embodiment, the business requirements are specific requirements that need to be implemented based on the core functions, which are usually a combination of business goals and user needs. For example, business requirements may include "improving customer satisfaction" and "optimizing order processing procedures".

[0065] In this embodiment, importance is to evaluate business requirements and data models to determine their importance in achieving core functions. For example, the importance of a customer model may be evaluated as high because it directly affects customer satisfaction.

[0066] In this embodiment, the total weight is a comprehensive weight calculated for each data model based on dependency and importance. For example, the total weight of the customer model may be 30 (importance weight) + 10 (dependency weight) = 40 points.

[0067] In this embodiment, the key model is the model that is most important to the business needs among all data models, which is identified based on the total weight. For example, if the customer model and the order model have the highest total weight, they are considered key models.

[0068] In this embodiment, the model integration plan is an integration and coordination strategy developed for key models to ensure that data models can work together effectively. For example, the model integration plan may include "integrating the customer model with the order model through an API to facilitate real-time updating of customer information."

[0069] In this embodiment, by constructing a dependency graph, the key model is determined as the first sorting model, the in-degree of other data models is calculated, the model with an in-degree of 0 is used as the second-level sorting model, and the model with a non-zero in-degree is used as the third-level sorting model. After the dependency graph is integrated with the first-level and second-level models, the in-degree of the third-level model is recalculated, the second-level sorting model is updated, and this process is repeated until the number of third-level models is 0, thereby forming a final model integration plan.

[0070] The working principle and beneficial effects of the above technical solution are: by constructing a data matrix and setting a scoring system, the dependencies between data models are judged, business requirements are determined based on core functions, and weights are assigned to each dependency. The total weight of the data model is calculated to identify key models, and a model integration plan is formulated based on the key models. The data models are integrated and finally a business model is formed, which improves the degree of satisfaction of business requirements, optimizes the model integration process, enhances the overall performance and maintainability of the system, and promotes the efficient operation of business processes.

[0071] Embodiment 6: The embodiment of the present invention provides a method for constructing a low-code development platform based on a data business modeling engine, and formulates a model integration plan based on a key model of a dependency judgment result, including: Build a dependency graph based on the dependency judgment result and the key model, use the key model as the first sorting model, calculate the in-degree of the remaining data models, record the data model with in-degree 0 as the second-level sorting model, and the data model with in-degree non-0 as the third-level sorting model; After integrating the first-level sorting model and the second-level sorting model into the dependency graph, recalculate the in-degree of the third-level sorting model to obtain a new second-level sorting model, and integrate the new second-level sorting model into the dependency graph until the number of third-level sorting models becomes 0, then the sorting ends; The model integration plan is derived based on the sorting results and the dependency graph.

[0072] In this embodiment, the dependency judgment result is an analysis result of determining the dependency between different data models, which is usually based on a data matrix and a scoring system. For example, assuming there are three data models: a customer model, an order model, and a product model, the dependency judgment result may be: the order model depends on the customer model and the product model, and the product model has no dependency.

[0073] In this embodiment, in-degree refers to the number of nodes (data models) that a node (data model) depends on in graph theory. An in-degree of 0 means that no other model depends on the model. For example, for the above example: the in-degree of the customer model is 0 (no other model depends on it), the in-degree of the order model is 2 (depends on the customer model and the product model), and the in-degree of the product model is 1 (depends on the order model).

[0074] In this embodiment, the first sorting model is the most important model determined based on the dependency judgment result in the dependency graph, usually a model with an in-degree of 0. For example, in the above example, the customer model is the first sorting model because its in-degree is 0.

[0075] In this embodiment, the second-level sorting model is a model group formed by calculating the model with an in-degree of 0 after the first sorting model is integrated into the dependency graph. For example, after the customer model is integrated, assuming that the in-degree of the order model becomes 0, the order model becomes the second-level sorting model.

[0076] In this embodiment, the third-level sorting model is a data model with non-zero in-degree in the dependency graph, which is usually a model that depends on the first and second-level sorting models. For example, in the above example, the product model may become the third-level sorting model because its in-degree is non-zero (it depends on the order model).

[0077] In this embodiment, the model integration plan is an integration and coordination strategy formulated based on the sorting results and the dependency graph to ensure that the data models can work together effectively. For example, the model integration plan may include: integrating the customer model with the order model through an API to facilitate real-time updating of customer information, and integrating the order model with the product model to automatically obtain product information when processing an order.

[0078] In this embodiment, a model integration plan is formulated based on the dependency judgment results. This automated integration process reduces the need for manual coding, allowing users to focus on business logic rather than technical details.

[0079] The working principle and beneficial effects of the above technical solution are: by constructing a dependency graph, the key model is determined as the first sorting model, and the in-degree of other data models is calculated. The model with an in-degree of 0 is used as the second-level sorting model, and the model with a non-zero in-degree is used as the third-level sorting model. After integrating the first-level and second-level models, the in-degree of the third-level model is recalculated, the second-level sorting model is updated, and this process is repeated until the number of third-level models is 0, thereby forming a final model integration plan, improving the efficiency and accuracy of the integration, ensuring the stability and scalability of the final business model, and promoting the flexibility and responsiveness of the overall system.

[0080] Embodiment 7: The embodiment of the present invention provides a method for constructing a low-code development platform based on a data business modeling engine, selecting an application scenario template based on a business model, configuring template parameters, mapping data fields in the business model with template parameters, and publishing the business model to the low-code development platform according to the mapping result, including: Select an application scenario template from the business-scenario template library based on the business requirements corresponding to the business model, and set template parameters according to the business requirements; Identify data fields in the business model, screen the data fields based on the business requirements, and determine the fields to be mapped; Based on the fields to be mapped and the template parameters, mapping is performed, and then the business template is published to the low-code development platform.

[0081] In this embodiment, the business-scenario template library is a library that stores various business scenario templates for developers or business personnel to choose and use to meet specific business needs. For example, a business-scenario template library of an e-commerce platform may include the following templates: customer registration scenario template, order processing scenario template, and product recommendation scenario template.

[0082] In this embodiment, the fields to be mapped are data fields that need to be mapped with template parameters and are screened out according to business needs. For example, in the "order processing" scenario of the e-commerce platform, the fields to be mapped may be: order amount (mapped to the "payment amount" in the template parameters), order status (mapped to the "current status" in the template parameters).

[0083] In this embodiment, filtering is to select fields that meet business needs from data fields according to specific conditions. For example, in the "order model", fields related to "payment" may be filtered out, such as: order amount, payment method, order status, etc.

[0084] In this embodiment, the user can identify and filter the data fields in the business model and map them with the template parameters. This dynamic mapping method enables the user to quickly adapt to changing business needs without having to deeply understand the underlying code implementation.

[0085] The working principle and beneficial effects of the above technical solution are: by analyzing the business requirements corresponding to the business model, selecting the appropriate application scenario template from the business-scenario template library, setting the template parameters according to the requirements, identifying the data fields in the business model, screening out the fields to be mapped, mapping the fields to be mapped with the template parameters, and finally publishing the business template to ensure efficient docking between business requirements and templates, reducing the complexity of manual configuration, improving development efficiency, and promoting rapid response and optimization of business processes.

[0086] Embodiment 8: An embodiment of the present invention provides a method for constructing a low-code development platform based on a data business modeling engine, which maps the to-be-mapped fields with template parameters, including: ,in, Represents the mapping result at time t; Represents data conversion function g The derivative of f Indicates the field to be mapped With template parameters The mapping function of Indicates the field to be mapped at time t; Represents dynamic parameters; Represents the template parameters at time t; Indicates the rate of change of the field to be mapped over time t; Indicates that while keeping other variables unchanged, the template parameters The degree of impact on the mapping results; Indicates that the fields to be mapped remain unchanged while keeping other variables unchanged. The degree of impact on the mapping results; Indicates the dynamic change of the i-th template parameter over time; Represents the i-th parameter in the template parameter.

[0087] In this embodiment, the specific form of g depends on business requirements and can be linear, square or other forms.

[0088] In this embodiment, dynamic parameters allow users to adjust template parameters based on real-time data and demand changes. This flexibility is a major advantage of low-code platforms.

[0089] The working principle and beneficial effect of the above technical solution are: by defining the relationship between the mapping result and the field to be mapped and the template parameter, the dynamic change of the mapping function is analyzed by using the derivative of the data conversion function. f The relationship between the fields to be mapped and the template parameters is described. The change rate of dynamic parameters and template parameters affects the mapping results. By analyzing the sensitivity of each parameter to the mapping results, the mapping process is optimized, the accuracy and flexibility of the mapping results are improved, real-time adjustment and optimization are supported, and the responsiveness and adaptability of the system are enhanced.

[0090] Finally, 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 aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for constructing a low-code development platform based on a data business modeling engine, characterized in that: include: Step 1: Obtain the engine application scenario, determine the existing user group according to the engine application scenario, determine the corresponding existing needs based on the existing user group, and then derive the core functions of the platform; Step 2: Decompose the core function to obtain multiple sub-functions, develop a data model based on the sub-functions, and then build the overall architecture of the low-code development platform; Step 3: Analyze the dependency of the data model, integrate the data model according to the dependency, and determine the business model in combination with the overall architecture and the integration result; Step 4: Select an application scenario template based on the business model and configure the template parameters, map the data fields in the business model with the template parameters, and publish the business model to the low-code development platform based on the mapping results.

2. According to claim 1, a method for constructing a low-code development platform based on a data business modeling engine is characterized in that: Obtain engine application scenarios, determine existing user groups based on the engine application scenarios, determine corresponding existing needs based on the existing user groups, and then derive the core functions of the platform, including: Obtain relevant products in the current market, analyze market trends based on the relevant products, determine engine application scenarios using market trend analysis results, and determine existing user groups based on the engine application scenarios and the market trends; A first division is performed on the existing user groups according to the company size to obtain a first monomer; a second division is performed on the existing user groups according to the user roles to obtain a second monomer; A feature analysis is performed on the first monomer and the second monomer, and the existence needs of different user groups are determined according to the feature analysis results, and then the corresponding platform core functions are determined.

3. According to claim 1, a method for constructing a low-code development platform based on a data business modeling engine is characterized in that: The core functions are disassembled to obtain multiple sub-functions, and data models are developed based on the sub-functions to build the overall architecture of the low-code development platform, including: Decomposing the workflow of the core function, determining the sub-functions corresponding to the core function, and identifying the achievable sub-functions among all sub-functions based on the function realization table; Determine the architecture design principles according to the engine application scenario, determine the platform architecture style based on the architecture design principles, and determine the hierarchical division of the platform according to the platform architecture style; Use the hierarchical division results to locate the achievable sub-functions, and develop the corresponding data model based on the location results; The overall architecture of the low-code development platform is determined by comprehensive hierarchical division and data model.

4. A method for constructing a low-code development platform based on a data business modeling engine according to claim 3, characterized in that: Determine the architecture design principles based on the engine application scenario, and determine the platform architecture style based on the architecture design principles, including: Create multiple usage scenarios based on the engine application scenario, create corresponding user stories for each usage scenario according to the user role, extract principle conditions from the user stories, and determine the architecture design principles by combining all principle conditions; Evaluate different architectural styles based on architectural design principles, analyze the focus of different architectural styles for each usage scenario, and then determine the platform architectural style of the low-code development platform.

5. According to claim 1, a method for constructing a low-code development platform based on a data business modeling engine is characterized in that: Analyze the dependency relationships of the data models, integrate the data models according to the dependencies, and determine the business model based on the overall architecture and the integration results, including: Constructing a data matrix based on the data model, setting a scoring system, and determining the dependency relationship between the data model according to the data matrix and the scoring system; Determine business requirements based on core functions, assign different weights to each dependency based on the importance of business requirements and corresponding data models, calculate the total weight of each data model and identify key models; A model integration plan is formulated based on the key model of the dependency judgment result, the data model is integrated according to the model integration plan, and then the business model is determined in combination with the overall architecture.

6. A method for constructing a low-code development platform based on a data business modeling engine according to claim 5, characterized in that: Develop a model integration plan based on the dependency relationship judgment results and key models, including: Construct a dependency graph based on the dependency judgment result and the key model, use the key model as the first sorting model, calculate the in-degree of the remaining data models, record the data model with in-degree 0 as the second-level sorting model, and the data model with in-degree non-0 as the third-level sorting model; After integrating the first-level sorting model and the second-level sorting model into the dependency graph, recalculate the in-degree of the third-level sorting model to obtain a new second-level sorting model, and integrate the new second-level sorting model into the dependency graph until the number of third-level sorting models becomes 0, then the sorting ends; The model integration plan is derived based on the sorting results and the dependency graph.

7. A method for constructing a low-code development platform based on a data business modeling engine according to claim 3, characterized in that: Select an application scenario template based on the business model, configure template parameters, map the data fields in the business model with the template parameters, and publish the business model to the low-code development platform based on the mapping results, including: Select an application scenario template from the business-scenario template library based on the business requirements corresponding to the business model, and set template parameters according to the business requirements; Identify data fields in the business model, screen the data fields based on the business requirements, and determine the fields to be mapped; Based on the fields to be mapped and the template parameters, mapping is performed, and then the business template is published to the low-code development platform.

8. According to claim 7, a method for constructing a low-code development platform based on a data business modeling engine is characterized in that: Mapping is performed based on the to-be-mapped field and the template parameter, including: ,in, Represents the mapping result at time t; Represents data conversion function g The derivative of f Indicates the field to be mapped With template parameters The mapping function of Indicates the field to be mapped at time t; Represents dynamic parameters; Represents the template parameters at time t; Indicates the rate of change of the field to be mapped over time t; Indicates that while keeping other variables unchanged, the template parameters The degree of impact on the mapping results; Indicates that the fields to be mapped remain unchanged while keeping other variables unchanged. The degree of impact on the mapping results; Indicates the dynamic change of the i-th template parameter over time; Represents the i-th parameter in the template parameter.

Images