A system service page generation method and system, electronic equipment and storage medium

Abstract

The application provides a system service page generation method and system, electronic equipment and a storage medium, and relates to the technical field of data processing. By obtaining service requirement information, and on this basis, system analysis, data structure design and service page design are performed, automatic programming processing is finally realized based on service page design information, and a system service page corresponding to the service requirement information is obtained. The method effectively solves the problems of semantic conflict, inconsistent data structuring standards, type mismatch and logic interruption errors caused thereby in the prior art, greatly improves the generation efficiency and accuracy of the system service page, thereby reducing the development and debugging cost of the system service page, and ensuring that the generated system service page can accurately reflect the business requirements, promote the smooth execution of cross-department business processes, and thus improve the operation efficiency and decision-making quality of the enterprise.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and more specifically, to a method for generating system business pages, a system, an electronic device, and a storage medium. Background Technology

[0002] In the wave of enterprise digital transformation, rapidly responding to business needs and efficiently generating customized system business pages have become key to enhancing enterprise competitiveness. However, in the complex environment of automating the generation of cross-departmental business systems, existing technologies face many challenges.

[0003] First, within an enterprise's internal knowledge base, the same business entity, such as "core customer," often has multiple definitions from different business lines (e.g., sales and customer service). These definitions may contain semantic conflicts or inconsistencies. For example, the sales department might define "core customer" as "a customer with annual sales exceeding one million," while the customer service department might define it as "a customer with a complaint rate of less than 1% and high activity." This semantic conflict can lead to ambiguity in the early stages of business logic development, subsequently affecting data model design and front-end / back-end code generation.

[0004] Finally, when the aforementioned conflicts and inconsistencies are not effectively identified, reconciled, and unified, cascading type mismatches and logic interruption errors are highly likely to occur during the business logic construction, data model design, and front-end and back-end code generation stages. These errors not only increase development and debugging costs, but more seriously, they may cause the generated system business pages to fail to accurately reflect business requirements, or even hinder the smooth execution of cross-departmental business processes, thereby affecting the company's operational efficiency and decision-making quality.

[0005] There is currently no effective technical solution to the above problems. Summary of the Invention

[0006] The purpose of this application is to provide a method, system, electronic device, and storage medium for generating system business pages, aiming to solve the problems of semantic conflicts, inconsistent data structuring standards, and the resulting type mismatches and logical interruption errors encountered in the prior art when automatically generating cross-departmental business systems.

[0007] This application provides a method for generating system business pages, including the following steps: Obtain business requirements information; Based on the aforementioned business requirements information, system analysis is performed to obtain system analysis information; Based on the system analysis information, data structure design is performed to obtain data structure design information; Based on the business requirements information, combined with the system analysis information and the data structure design information, the business page is designed to obtain the business page design information; Automatic programming processing is performed based on the business page design information to obtain the system business page corresponding to the business requirement information.

[0008] This technical solution enables fully automated generation from business requirements to system business pages, effectively solving the problems of low development efficiency and frequent errors caused by semantic conflicts and inconsistent data structuring standards in existing technologies, and significantly improving the response speed and accuracy of system development.

[0009] Optionally, the system business page generation method is applied to a smart terminal, which has preset instant messaging software installed, and the step of obtaining business requirement information includes: Obtain the messages received by the instant messaging software; Detect whether the message contains preset business requirement keywords; If the message contains preset business requirement keywords, then the message is identified as the business requirement information.

[0010] This technical solution enables intelligent identification and acquisition of business requirements, reducing the cost and error rate of manual intervention and improving the real-time performance and accuracy of business requirement capture.

[0011] Optionally, the business requirement information includes business object information and context information corresponding to the business object information. The step of performing system analysis based on the business requirement information to obtain system analysis information includes: Identify the business object information contained in the business requirement information; When it is identified that the business object information has multiple definition information across business domains in the preset business reference information set, the context information corresponding to the business object information is extracted from the business requirement information; Determine the domain indication features based on the context information, and use the domain indication features to determine the target business domain corresponding to the business object information; Extract target definition information corresponding to the target business domain from the business reference information set; Based on the target definition information, determine the business entity parameters; The parameters of the business entity are determined as the system analysis information.

[0012] This technical solution effectively resolves the problem of conflicting business entity definitions across departments. By analyzing context and determining domain indicator features, it ensures the accuracy and consistency of business entity parameters, avoiding semantic ambiguity in subsequent data model design and code generation.

[0013] Optionally, the step of designing a data structure based on the system analysis information to obtain data structure design information includes: Based on the business entity parameters in the system analysis information, business entity attribute identification is performed to obtain business entity attribute information; Based on the preset data requirements information corresponding to the business entity attribute information, attribute classification is performed to obtain the attribute category corresponding to the business entity attribute information. For each of the business entity attribute information, a data table is designed based on the attribute category to obtain the data table corresponding to the business entity attribute information. Generate a data synchronization strategy and attribute access control configuration information corresponding to the attribute information of the business entity based on the data table; The data table, the data synchronization strategy, and the attribute access control configuration information are used as the data structure design information.

[0014] Optionally, the step of designing business pages based on the business requirements information, combined with the system analysis information and the data structure design information, to obtain business page design information includes: Based on the aforementioned business requirement information, obtain a preset general business page template; Based on the system analysis information, business process identification is performed to obtain the target business process corresponding to the business requirement information; Based on the target business process and the attribute access control configuration information in the data structure design information, the target business entity attribute information is filtered out from the data table in the data structure design information. Extract the data requirement information corresponding to the attribute information of the target business entity from the data structure design information; Based on the data requirements, configure the interface element placeholders corresponding to the target business entity attribute information; Based on the interface element placeholders, the interface elements corresponding to the target business entity attribute information are filled into the general business page template to generate business page design information.

[0015] Optionally, the automatic programming processing based on the business page design information to obtain the system business page corresponding to the business requirement information includes: The business page design information is parsed to obtain the interface component description and data interaction logic description; Based on the interface component description and data interaction logic description, establish a business mapping relationship between the interface elements and the business requirement information; Based on the business mapping relationship, the system business page corresponding to the business requirement information is generated using the code snippets corresponding to the interface elements.

[0016] Secondly, this application provides a method for generating system business pages, including: Identify intelligent agents to obtain business requirement information; An analytical agent is used to perform system analysis based on the business requirement information to obtain system analysis information. A data design agent is used to design data structures based on the system analysis information to obtain data structure design information. A page design intelligent agent is used to design business pages based on the business requirement information, combined with the system analysis information and the data structure design information, to obtain business page design information; A programming intelligent agent is used to automatically process programming information based on business page design information to obtain the system business page corresponding to the business requirement information.

[0017] Optionally, when the data design agent performs data structure design based on the system analysis information to obtain data structure design information, it specifically executes the following: Based on the business entity parameters in the system analysis information, business entity attribute identification is performed to obtain business entity attribute information; Based on the preset data requirements information corresponding to the business entity attribute information, attribute classification is performed to obtain the attribute category corresponding to the business entity attribute information. For each of the business entity attribute information, a data table is designed based on the attribute category to obtain the data table corresponding to the business entity attribute information. Generate a data synchronization strategy and attribute access control configuration information corresponding to the attribute information of the business entity based on the data table; The data table, the data synchronization strategy, and the attribute access control configuration information are used as the data structure design information.

[0018] Thirdly, this application provides an electronic device, including a processor and a memory, the memory storing computer-readable instructions, which, when executed by the processor, perform the steps of a system business page generation method as described in any of the preceding claims.

[0019] Fourthly, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the steps of a system business page generation method as described in any of the preceding claims.

[0020] As described above, the system, electronic device, and storage medium provided in this application generate system business pages by acquiring business requirement information and performing system analysis, data structure design, and business page design based on this information. Ultimately, it achieves automatic programming processing based on the business page design information to obtain the system business page corresponding to the business requirement information. This method effectively solves problems such as semantic conflicts, inconsistent data structure standards, and the resulting type mismatches and logical interruption errors existing in the prior art. Specifically, through in-depth analysis of business requirement information, business entity parameters can be accurately identified, and refined data structure design can be performed according to the different data requirements of different business departments, thereby avoiding data redundancy or missing data. Furthermore, by combining system analysis information and data structure design information for business page design, and performing automatic programming processing based on the design information, the generation efficiency and accuracy of system business pages are greatly improved, thereby reducing the development and debugging costs of system business pages and ensuring that the generated system business pages accurately reflect business requirements, promoting the smooth execution of cross-departmental business processes, and thus improving the operational efficiency and decision-making quality of enterprises.

[0021] Other features and advantages of this application will be set forth in the following description, and will be apparent in part from the description, or may be learned by practicing embodiments of this application. The objectives and other advantages of this application may be realized and obtained by means of the structures particularly pointed out in the written description and the accompanying drawings. Attached Figure Description

[0022] Figure 1 A flowchart illustrating a system business page generation method provided in this application embodiment.

[0023] Figure 2 This is a schematic diagram of the structure of the system for generating business pages provided in the embodiments of this application.

[0024] Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0025] Labeling Explanation: 21. Identification Agent; 22. Analysis Agent; 23. Data Design Agent; 24. Page Design Agent; 25. Programming Agent; 13. Electronic Device; 1301. Processor; 1302. Memory; 1303. Communication Bus. Detailed Implementation

[0026] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0027] It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. Furthermore, in the description of this application, terms such as "first," "second," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0028] Please refer to Figure 1 This application provides a method, system, electronic device, and storage medium for generating system business pages, which can effectively solve the semantic conflicts, inconsistent data structuring standards, and the resulting type mismatches and logical interruption errors existing in the prior art, thereby achieving efficient and accurate generation of system business pages and improving the operational efficiency and decision-making quality of enterprises.

[0029] This application provides a method for generating system business pages, including the following steps: Step S1: Obtain business requirement information; Step S2: Perform system analysis based on business requirements information to obtain system analysis information; Step S3: Design the data structure based on the system analysis information to obtain the data structure design information; Step S4: Based on business requirements information, combined with system analysis information and data structure design information, design business pages to obtain business page design information; Step S5: Perform automatic programming processing based on the business page design information to obtain the system business page corresponding to the business requirement information.

[0030] This method is primarily applied to smart terminals, which can be computers, tablets, or any terminal device with computing and communication capabilities. Pre-installed instant messaging software, such as WeChat Work or DingTalk, can be installed on the smart terminal to receive and process business-related information.

[0031] "Business requirements information" refers to the specific requirements put forward by users or business departments regarding system functions, data processing, interface display, etc. For example, a sales department may request "a customer management system that can record basic customer information, follow-up records, and order status."

[0032] "System analysis information" is a detailed description of system functions, data flow, business logic, etc., obtained after in-depth analysis of business requirements information. It includes "business entity parameters" corresponding to the business requirements information. For example, in a customer management system, business entity parameters may include "customer name," "contact information," and "customer type."

[0033] "Data structure design information" refers to the result of structured design of the data that the system needs to store, based on system analysis information, including data tables, field types, and relationships.

[0034] "Business page design information" refers to the design results of the layout, form elements, and interaction logic of the system's business pages based on business requirements, system analysis, and data structure design information. It includes "business form design" and "user interface (UI) design."

[0035] "Automatic programming processing" refers to generating system business page code using automated tools based on business page design information.

[0036] First, business requirement information can be obtained by calling the application programming interface (API) provided by the instant messaging software or by listening to specific message channels. This allows for the real-time acquisition of text, voice, or other message content sent or received by users in the instant messaging software, and the automatic identification of business requirement information from the message content (the specific process is detailed below).

[0037] Secondly, after obtaining the business requirement information, it needs to be analyzed in depth to understand its internal logic and data relationships. One approach is to directly identify the business entity parameters contained in the business requirement information through text recognition or semantic recognition. For example, if the business requirement information is "managing customer information," the system will identify business entity parameters such as "customer name," "contact information," and "customer type" based on the preset keyword "customer." These identified business entity parameters are then used as system analysis information. Another approach is for the system to utilize Natural Language Processing (NLP) technology to perform text analysis on the business requirement information and automatically identify the business entity parameters. For example, through keyword matching and entity recognition technologies, structured business entity parameters can be extracted from unstructured business requirement text.

[0038] Next, after clarifying the business entity parameters, it is necessary to design corresponding data structures to store these parameters. One approach is to design data table structures based on the business entity parameters in the system analysis information. For example, design a string field for "Customer Name," a string field for "Contact Information," and an enumeration field for "Customer Type," etc. Then, organize these designed data tables and field types into data structure design information. Another approach is for the system to provide a data model design tool, allowing users to input the structure design information corresponding to the business entity parameters into the tool through drag-and-drop, configuration, etc. Based on the user-input structure design information and the business entity parameters, the tool automatically generates data table structure information, and then generates corresponding data structure design information based on this data table structure information. The data table structure information can be used to determine the data table structure for the business entity parameters, allowing the data model design tool to automatically infer field types, lengths, and other attributes based on the data table structure and preset data structure design rules, and automatically generate the data structure design information corresponding to the business entity parameters based on the automatically inferred attributes. This data model design tool can automatically infer field types, lengths, and other attributes based on preset data structure design rules, and generate corresponding data structure design information.

[0039] After the data structure design is complete, the user interface needs to be designed to facilitate user interaction with the system. One approach is to automatically generate prototypes and wireframes of the business pages based on business requirements, system analysis, and data structure design information. For example, based on business entity parameters, corresponding input boxes, dropdown lists, buttons, and other interface elements are laid out on the page, and their display format and interaction logic are designed. Then, these designed page layouts, form elements, and interaction logic are compiled into business page design information. Another approach is for the system to provide a visual page designer. Users can automatically generate business page design information based on business requirements, system analysis, and data structure design information by dragging and dropping components and configuring properties. This designer can automatically generate form fields based on the data structure and allow users to customize the layout and style.

[0040] Finally, after the business page design is completed, it needs to be transformed into an executable system business page. Specifically, by parsing the business page design information, front-end and back-end code can be automatically generated. For example, based on the system's preset code format (such as JSON format), corresponding input component code can be generated according to the form fields as front-end code, and API call code can be generated according to the data interaction logic as back-end code. Thus, the system business page can be quickly generated using the input component code and API call code.

[0041] The core innovation of this application lies in its introduction of automated and intelligent processing mechanisms to organically integrate business requirement information, system analysis information, data structure design information, and business page design information, achieving end-to-end automated generation from requirements to pages. Specifically, through system analysis, this application effectively identifies business entity parameters in the business requirement information, providing accurate input for subsequent data structure and page design. In the data structure design phase, this application can generate a reasonable data table structure based on the business entity parameters, avoiding data redundancy or missing data caused by unreasonable data structures in traditional methods. In the business page design phase, this application can automatically generate business page design information that conforms to business logic and user experience by combining business requirement information, system analysis information, and data structure design information, reducing the workload and error rate of manual design. Finally, through automated programming, this application can quickly transform business page design information into executable system business pages, greatly shortening the development cycle and improving development efficiency.

[0042] Therefore, the system business page generation method proposed in this application can not only effectively solve the problems of low efficiency, information bias and semantic conflict in traditional methods, but also significantly improve the generation efficiency and accuracy of system business pages, providing strong technical support for enterprise digital transformation.

[0043] In some implementations, the system business page generation method is applied to a smart terminal, which has a preset instant messaging software installed. The method for obtaining business requirement information includes: obtaining messages received by the instant messaging software; detecting whether the message contains preset business requirement keywords; and if the message contains preset business requirement keywords, then identifying the message as business requirement information.

[0044] In this context, acquiring messages received by instant messaging software refers to the system capturing, in real-time, the text, voice, or other message content sent or received by users within the instant messaging software by calling the application programming interface (API) provided by the instant messaging software or by listening to specific message channels. The purpose is to capture potential business needs expressed.

[0045] Furthermore, detecting whether the message contains preset business requirement keywords refers to the system performing text analysis or semantic understanding on the acquired message to determine whether it contains one or more predefined sets of keywords. These keywords are specific words or phrases related to business page generation, such as "create page," "generate form," and "require a customer management interface." This detection process aims to accurately identify content related to business requirements from the message.

[0046] If a message contains preset business requirement keywords, it is identified as business requirement information. This means that when a message is identified as containing business requirement keywords, the entire content of the message is recognized by the system as valid business requirement information.

[0047] This application's solution combines the system's business page generation method with instant messaging software on smart terminals, enabling the automatic identification of business requirement information from users' daily communication. Specifically, the smart terminal serves as the platform, and the instant messaging software as the information entry point. The system can monitor and parse messages sent by users in the instant messaging software in real time. Through intelligent detection using preset business requirement keywords, business requirement information is automatically confirmed from the message content in instant messaging. This mechanism makes the capture of business requirements more natural, immediate, and automated, effectively solving the problems of low efficiency and reliance on manual intervention in traditional methods.

[0048] Through the above technical solution, this application can achieve automated and intelligent acquisition of business requirement information, significantly reducing the workload and time cost of manually entering or submitting business requirements. Users only need to express their requirements in daily instant messaging, and the system can automatically identify and initiate the business page generation process, greatly improving user experience and system response efficiency, making the generation of business pages more convenient and timely.

[0049] The following is a concrete example to illustrate this. Suppose a sales manager uses enterprise instant messaging software (such as DingTalk) on their smart device (e.g., smartphone) to communicate with team members. The manager sends a message in DingTalk: "Please help me quickly generate a customer visit record page, which needs to include the customer name, visit time, visit content, and follow-up plan." At this moment, the system's business page generation method running on the smart terminal will receive this message from DingTalk in real time. The system will inspect the message and find that it contains preset business requirement keywords such as "generate...page", "customer visit record", "customer name", "visit time", "visit content", and "follow-up plan". Because these keywords are detected, the system will identify this complete message as business requirement information. Subsequently, this business requirement information will be automatically passed to the subsequent system analysis agent, data design agent, and page design agent, thereby initiating the automated generation process of the customer visit record page, without requiring additional manual operation by the sales manager or submission of requirements through other systems.

[0050] In some implementations, the business requirement information includes business object information and context information corresponding to the business object information. System analysis is performed based on the business requirement information to obtain system analysis information, including: identifying the business object information contained in the business requirement information; when the business object information is identified to have multiple definitions across business domains in a preset business reference information set, extracting the context information corresponding to the business object information from the business requirement information; determining domain indication features based on the context information, and using the domain indication features to determine the target business domain corresponding to the business object information; extracting target definition information corresponding to the target business domain from the business reference information set; determining business entity parameters based on the target definition information; and determining the business entity parameters as system analysis information.

[0051] In this context, business object information can be understood as entities with inherent attributes and behaviors within a business domain, such as "customer," "order," and "product." Business entity parameters are the specific attributes that provide a structured description of these business objects, such as the customer's name and contact information.

[0052] Furthermore, when it is identified that business object information has multiple definitions across business domains within a pre-defined business reference information set, the contextual information corresponding to the business object information is extracted from the business requirement information. The business reference information set can be a knowledge base or database containing various business objects and their definitions in different business domains. Multiple definitions across business domains refer to the fact that the same business object may have different attributes, meanings, or focuses in different business scenarios or departments. For example, in business domains such as hotel services, restaurants, or hotels, the definition of "menu" refers to a list including the names of various dishes and their prices. However, in business domains such as software interfaces or functional systems, the definition of "menu" refers to specific functions, options, or operation methods. Contextual information refers to other text, keywords, or structured data that appears around the business object information. This information helps to clarify the specific context of the business object in the current business requirement.

[0053] Subsequently, domain indication features are determined based on contextual information, and the preset business domain corresponding to the domain indication features is identified as the target business domain corresponding to the business object information. The domain indication features are domain feature information derived from contextual information analysis. This domain feature information may include parameters such as keywords, phrases, or semantic patterns that clearly point to a specific business domain; this embodiment does not impose limitations on this. For example, if the contextual information contains words such as "sales volume" or "customer follow-up," the domain indication features may point to the business domain of "sales," thus "sales" can be identified as the target business domain.

[0054] Next, target definition information corresponding to the target business domain is extracted from the business reference information set. Specifically, the domain indicator feature can be matched with the domain features corresponding to each definition in the reference information set to determine the target definition information based on the matching results. For example, the domain indicator feature can be compared with the domain features corresponding to each definition in the reference information set. If the domain feature corresponding to a certain definition in the reference information set is the same as the domain indicator feature, then the domain indicator feature is considered to match the domain feature corresponding to that definition, and a matching result can be generated based on that definition. Then, based on this matching result, the preset definition information corresponding to the domain indicator feature can be determined as the target definition information. If the domain features corresponding to all definitions in the reference information set are different from the domain indicator feature, then the domain indicator feature is considered to not match the preset domain features in the reference information set. In this case, a mismatch prompt can be generated for the domain indicator feature, prompting the user to input the definition information corresponding to the business entity parameters for the domain indicator feature. Upon receiving the user's input definition information, this user-input definition information can be directly determined as the target definition information. This matching ensures that the extracted definition information is most relevant to the current business requirements.

[0055] Finally, based on the target definition information, the business entity parameters corresponding to the business object information are determined. For example, if the target definition information is "customer," then in the sales domain, its business entity parameters can be determined to include: customer name (string type), contact information (string type), customer type (enumeration type, e.g., potential customer, active customer, dormant customer), department (string type, e.g., sales department, customer service department), and business process association (list type, e.g., customer follow-up, order processing, customer care), etc. These parameters will collectively constitute the system analysis information.

[0056] This application's solution effectively resolves the ambiguity caused by multiple definitions of business objects across different business domains by introducing in-depth analysis of the context of business object information. Specifically, during system analysis, if the system identifies multiple cross-business domain definitions of business object information within a pre-defined set of business reference information, it proactively extracts the corresponding context information for that business object. Based on this context information, domain indicator features are determined, and the target business domain of the business object under the current business requirement is accurately identified according to these features. Thus, the system no longer blindly selects from all definitions but can selectively extract target definition information matching the target business domain from the business reference information set. This mechanism ensures that the determination of business entity parameters is based on the most accurate and relevant business context, thereby avoiding system analysis bias caused by definition confusion.

[0057] Through the aforementioned technical solution, this application significantly improves the accuracy and intelligence level of the system analysis phase. Especially when processing business object information with multiple definitions, the introduction of context analysis and domain matching mechanisms effectively avoids system analysis errors caused by information ambiguity, ensuring accurate identification of business entity parameters. This not only increases the automation level of the system's business page generation process but also reduces the cost of manual intervention and correction, thereby improving the efficiency and reliability of the entire system's business page generation method. Furthermore, this solution enables the system to better adapt to complex and ever-changing business scenarios, providing a solid foundation for generating highly customized and accurate business pages for different business domains.

[0058] In some preferred embodiments, it is assumed that the business requirement information received by the system includes the business object information of "customer". If the system analyzes based solely on the word "customer", it may be unable to determine its specific meaning, because "customer" may refer to "potential customer" in the sales department and "customer already served" in the customer service department. In this case, the method of this application extracts the contextual information corresponding to "customer" from the business requirement information. For example, if the contextual information contains keywords such as "sales lead" or "business opportunity", the domain indication feature may be determined as "sales domain". Based on this, the system will extract the target definition information of "customer" in the sales domain from the business reference information set, such as "customer name: string type, contact information: string type, customer type: enumeration type (potential customer, active customer), department: sales department, business process association: customer follow-up, order processing". Thus, the system analysis information can accurately contain the customer entity parameters under the sales domain, providing an accurate basis for subsequent page generation. If the context information contains keywords such as "service request" or "complaint handling," the domain indicator feature may be identified as "customer service domain." The system will extract the target definition information of "customer" in the customer service domain, such as "customer name: string type, contact information: string type, customer type: enumeration type (active customer, dormant customer), department: customer service department, business process association: service record, satisfaction survey." In this way, regardless of the context in which the business object appears, the system can accurately understand its meaning and determine the corresponding business entity parameters.

[0059] In some implementations, data structure design is performed based on system analysis information to obtain data structure design information, including: identifying business entity attributes based on business entity parameters in the system analysis information to obtain business entity attribute information; classifying attributes according to preset data requirements corresponding to the business entity attribute information to obtain attribute categories corresponding to the business entity attribute information; designing data tables based on attribute categories for each business entity attribute information to obtain data tables corresponding to the business entity attribute information; generating data synchronization strategies and attribute access control configuration information corresponding to the business entity attribute information based on the data tables; and using the data tables, data synchronization strategies, and attribute access control configuration information as data structure design information.

[0060] Specifically, after receiving the system analysis information, the system uses a data design agent to parse the business entity parameters (e.g., "customer") contained within, and identifies the business entity attributes represented by these parameters (business entity attributes refer to the various attribute information describing a specific "business entity"). This yields the business entity attribute information; for example, the business entity attribute information corresponding to "customer" includes attributes such as "customer ID," "customer name," "contact information," "customer address," "potential customer rating," "service satisfaction rating," and "customer service history." This step aims to refine the specific data attributes that constitute these entities from the macroscopic business entity parameters.

[0061] Subsequently, based on the preset data requirements (including data granularity and update frequency) corresponding to the business entity attribute information, attribute classification can be performed to obtain the attribute categories corresponding to the business entity attribute information. These attribute categories can be divided into core shared attribute categories and specific attribute categories. Specifically, based on the differentiated requirements of different business departments (e.g., sales department, customer service department) regarding the data granularity and update frequency of these business entity attribute information (e.g., "customer address"), the business entity attribute information is classified. For example, the sales department might only require province and city for the data granularity of "customer address," while the customer service department might need details down to the house number. Similarly, the sales department might require "weekly updates to customer status" for "customer address," while the customer service department might require "real-time updates to service records." This allows for a clear classification of these business entity attribute information into "core shared attribute information" (universally applicable and consistently required by all departments, such as "customer ID") corresponding to the core shared attribute category and "department-specific attribute information" (only relevant to specific departments or subject to special requirements, such as "customer service history") corresponding to the specific attribute category. This classification serves as the logical starting point for subsequent hierarchical data structure design, aiming to provide refined guidance for subsequent data table design to meet the data management needs of different business scenarios.

[0062] Based on this, for each business entity's attribute information, data tables are designed according to attribute categories to obtain the corresponding data tables for the business entity's attribute information. These data tables can be divided into core data tables and extended data tables. The core data table is the basic view of the business entity, containing core shared attributes common to all departments, such as basic customer information (customer ID, customer name, etc.). Extended data tables are used to store department-specific attributes, such as the sales department's "potential customer rating" and the customer service department's "service satisfaction score." This hierarchical design helps reduce data redundancy and improves the flexibility and scalability of data management.

[0063] Subsequently, data synchronization strategies and corresponding attribute access control configuration information for business entity attribute information are generated based on the data tables. The data synchronization strategy aims to ensure data consistency between the core data table and each extended data table, for example, through scheduled synchronization or event-triggered synchronization. The attribute access control configuration information defines the read, write, and modify permissions for different users or roles on different business entity attribute information based on attribute categories and the permission requirements of business departments, thereby ensuring data security and compliance.

[0064] Ultimately, the data tables, data synchronization strategies, and attribute access control configuration information were used as data structure design information. These elements together constitute a complete and refined data structure design scheme, providing a solid foundation for subsequent business page design and automated programming processing.

[0065] This application's solution effectively addresses the limitations of traditional data structure design in handling complex business scenarios by introducing business entity attribute identification, attribute classification based on data requirement information, hierarchical data table design, and the generation of data synchronization strategies and attribute access control configuration information. Specifically, by meticulously identifying the attributes of business entity parameters, a comprehensive understanding of the data items required by the business can be achieved. Furthermore, based on the differences in data granularity and update frequency requirements among different business departments, business entity attribute information is divided into core shared attribute categories and specific attribute categories, enabling the data structure design to accurately match actual business needs. Thus, data tables are designed for different attribute categories, resulting in data tables corresponding to the business entity attribute information. These tables include core data tables and extended data tables, avoiding the problem of a single data table structure failing to balance generality and specificity, effectively reducing data redundancy, and improving the flexibility of the data model. Simultaneously, the generation of data synchronization strategies ensures data consistency across data tables, while attribute access control configuration information fundamentally guarantees data security and compliance, preventing unauthorized access and modification, thereby constructing a highly efficient and secure data management foundation.

[0066] Through the above technical solutions, this application enables a more refined and flexible data structure design. Specifically, by classifying the attribute information of business entities and designing hierarchical core and extended data tables accordingly, the problem of a single data structure being unable to adapt to changing business needs is effectively solved, significantly reducing data redundancy and improving the scalability and maintainability of the data model. Furthermore, the introduction of a data synchronization strategy ensures data consistency across different business views, while attribute access control configuration information greatly enhances data security and compliance, enabling different departments or users to access and operate the required data according to their permissions. This improves the overall data management efficiency and security of the system, providing more robust and reliable data support for subsequent business page generation.

[0067] The following is a concrete example to illustrate this. Suppose a company needs to build a Customer Relationship Management (CRM) system, which involves two main departments: the sales department and the customer service department.

[0068] First, the system will identify business entity attributes based on the business entity parameters (such as "customer") in the system analysis information, and obtain business entity attribute information such as "customer ID", "customer name", "contact information", "customer address", "potential customer rating", "service satisfaction score" and "customer service history".

[0069] Next, attributes are categorized based on the data requirements of the sales and customer service departments for these business entity attribute information. For example, "Customer ID," "Customer Name," and "Contact Information" might be classified as core shared attribute categories because all departments need the core shared attribute information corresponding to these categories, and consistency is required. "Customer Address" might only require province and city information (coarse data granularity) in the sales department, while the customer service department needs details down to the house number (fine data granularity). "Potential Customer Rating" is an attribute specific to the sales department; "Service Satisfaction Rating" and "Customer Service History" are attributes specific to the customer service department. These unique attributes corresponding to the business entity attribute information are categorized as special attribute categories.

[0070] Then, data tables are designed based on these attribute categories. A "Core Customer Information Table" is designed to store core shared attributes, such as customer ID, customer name, and contact information. Meanwhile, a "Sales Extension Table" is designed to store attributes specific to the sales department, such as "Potential Customer Rating," and a "Customer Service Extension Table" is designed to store attributes specific to the customer service department, such as "Service Satisfaction Rating" and "Customer Service History." For attributes like "Customer Address," which have different granularity requirements across different departments, a general granularity (such as province and city) can be stored in the core table, while a more detailed granularity (such as house number) can be stored in the department extension table.

[0071] Subsequently, the system generates a data synchronization strategy. For example, when the "Contact Information" field in the core customer information table is updated, the synchronization strategy is automatically triggered to ensure that all extended tables that depend on this information can obtain the latest data. Simultaneously, attribute access control configuration information is generated. For instance, sales department users can view and modify "Potential Customer Ratings," but only have viewing permissions for "Customer Service History"; customer service department users can view and modify "Service Satisfaction Ratings" and "Customer Service History," but only have viewing permissions for "Potential Customer Ratings."

[0072] Ultimately, these data tables, data synchronization strategies, and attribute access control configuration information together constitute the data structure design information of the CRM system, providing flexible, secure, and efficient data support for the subsequent generation of business pages.

[0073] In some implementations, the steps for designing business pages based on business requirements information, combined with system analysis information and data structure design information, to obtain business page design information include: obtaining a preset general business page template based on the business requirements information; identifying the business process based on the system analysis information to obtain the target business process corresponding to the business requirements information; filtering the target business entity attribute information from the data table in the data structure design information based on the target business process and the attribute access control configuration information in the data structure design information; extracting the data requirement information corresponding to the target business entity attribute information from the data structure design information; configuring interface element placeholders corresponding to the target business entity attribute information according to the data requirement information; and filling the interface elements corresponding to the target business entity attribute information into the general business page template according to the interface element placeholders to generate the business page design information.

[0074] To obtain a pre-set generic business page template based on business requirement information, the process involves: determining the requirement keywords based on the business requirement information, and then retrieving a generic business page template corresponding to those keywords from a pre-set template library. For example, a sales department might request a customer management system. Natural language processing (NLP) is used to parse the business requirement information, determining the keyword as "customer," and then retrieving a generic business page template related to "customer" from the pre-set template library. Similarly, a warehouse department might request an "item management system." NLP is used to parse the business requirement information, determining the keyword as "item," and then retrieving a generic business page template related to "item" from the pre-set template library.

[0075] Specifically, business process identification refers to determining the specific operation sequence or workflow corresponding to the current business requirement based on business entity parameters contained in the system analysis information, such as "customer follow-up," "order processing," or "customer care." The target business process is the currently executed business process, and its purpose is to clarify the core business logic and user interaction path that the page needs to support.

[0076] Based on the target business process and the attribute access control configuration information in the data structure design information, the target business entity attribute information is selected from the data tables in the data structure design information.

[0077] Attribute access control configuration information refers to the access permission rules set for each business entity attribute during the data structure design phase, such as which user roles can view, edit, or delete a certain attribute. By combining the target business process and attribute access control configuration, it can be ensured that only business entity attributes related to the current business process and for which users have the corresponding permissions will be filtered out, thereby guaranteeing page relevance and data security. Data tables can be divided into core data tables and extended data tables; the filtering process will extract the required attributes from these data tables.

[0078] Extract the data requirements information corresponding to the attribute information of the target business entity from the data structure design information.

[0079] The data requirements specifically refer to the data granularity and update frequency requirements for business entity attributes. For example, for the "customer address" attribute, the sales department might only need data granularity at the province / city level, while the customer service department might need details down to the house number; for the "customer status" attribute, the sales department might update it weekly, while the customer service department might need real-time updates. Extracting these data requirements provides a basis for the subsequent fine-grained configuration of interface elements.

[0080] Based on the data requirements, configure placeholders for the corresponding UI elements that represent the target business entity attributes. Specifically, this involves configuring the field type, display format, editing permissions, and visibility of these placeholders. For example, if the data requirements indicate that "Customer Contact Information" is a string and needs to be updated in real-time, the corresponding placeholder can be configured as a text input box with appropriate validation rules and editing permissions. If "Customer Type" is an enumeration type, it can be configured as a dropdown selection box. This configuration ensures that the UI elements accurately reflect the data characteristics and business needs.

[0081] Based on the interface element placeholders, the interface elements corresponding to the target business entity attribute information are populated into the general business page template to generate business page design information. For example, the configured interface elements can be populated into the general business page template to generate business page design information that includes dynamically adjusted form fields, user interface layout, and interaction logic. In this way, the general template is concretized into a customized business page design that meets specific business needs, data characteristics, and access control, thus forming the final business page design information.

[0082] This application's solution addresses the shortcomings of traditional business page design in terms of versatility and adaptability by introducing a series of refined design steps. First, a pre-defined general business page template is obtained, providing an efficient and standardized foundation for subsequent customized design. Second, by identifying business processes based on business entity parameters from system analysis information, the target business process corresponding to the current business requirements can be accurately determined, ensuring that the page design closely revolves around the core business logic. Furthermore, by combining the target business process and attribute access control configuration information from the data structure design information, target business entity attribute information is filtered from the data table. This not only ensures the business relevance of the page content but, more importantly, strictly adheres to data access permissions, effectively improving data security. Subsequently, the data requirements corresponding to these target business entity attribute information, such as data granularity requirements and update frequency requirements, are extracted, providing a basis for the refined configuration of interface elements. Finally, based on these data requirements, the field types, display formats, editing permissions, and visibility of interface element placeholders are configured, and the configured interface elements are populated into the general business page template, thereby generating business page design information containing dynamically adjusted form fields, user interface layout, and interaction logic. The entire process achieves a layered refinement and dynamic adaptation from macro-level business requirements to micro-level interface elements, ensuring that the generated business pages can not only meet the needs of specific business scenarios, but also comply with data governance and security standards.

[0083] Through the above technical solution, this application achieves automated and intelligent business page design, significantly improving the efficiency and quality of page generation. Specifically, this solution can dynamically generate highly customized business pages based on different business needs and user permissions, avoiding the limitations of traditional manual design or static templates. Combined with attribute access control configuration information, it effectively ensures data security and compliance, preventing unauthorized data access and operations. This dynamic and intelligent page design method enables the system to quickly respond to business changes, reduces development and maintenance costs, and improves the flexibility and scalability of the entire system.

[0084] The following is a concrete example. Suppose a company needs to generate a "Customer Information Management" business page for its sales department.

[0085] First, the system will obtain a preset general business page template, which may include a standard form layout, a data list area, and an operation button area.

[0086] Next, based on the business entity parameters (such as "customer name", "contact information", "customer type" etc.) in the system analysis information, the system identifies the current target business process as "customer information management", which may include sub-processes such as "add customer", "edit customer", and "view customer details".

[0087] Then, based on the target business process of "customer information management" and combined with the attribute access control configuration information set for the sales department in the data structure design information (for example, sales personnel can view and edit "customer name" and "contact information", but can only view "customer credit rating"), the system filters out the target business entity attribute information needed by the sales department from the data tables (such as the core customer information table and the sales extension information table).

[0088] Subsequently, the system extracts the data requirement information corresponding to the attribute information of these target business entities from the data structure design information. For example, "Customer Name" is required to be a string type with a length limit of 50 characters and a high update frequency; "Customer Type" is an enumeration type (potential customer, active customer) with a medium update frequency; and "Customer Credit Rating" is a read-only numeric type.

[0089] Based on these data requirements, the system configures corresponding placeholders for interface elements. For example, "Customer Name" is configured as a text input box with a maximum length of 50 characters and is editable; "Customer Type" is configured as a drop-down selection box with options "Potential Customer" and "Active Customer" and is editable; and "Customer Credit Rating" is configured as a read-only text box.

[0090] Finally, the system populates these configured interface elements into the general business page template, generating the final "Customer Information Management" business page design information, which includes form fields, layout and interaction logic specific to the sales department, ensuring that the page meets both business requirements and access control.

[0091] In some implementations, automatic programming processing is performed based on business page design information to obtain the system business page corresponding to the business requirement information. This includes: parsing the business page design information to obtain interface component descriptions and data interaction logic descriptions; establishing a business mapping relationship between interface elements and business requirement information based on the interface component descriptions and data interaction logic descriptions; and generating the system business page corresponding to the business requirement information using code snippets corresponding to the interface elements based on the business mapping relationship.

[0092] Specifically, during automated programming, the first step is to parse the business page design information. This information is generated based on business requirements, system analysis, and data structure design. It includes form fields, interface component descriptions, and data interaction logic descriptions, which are used to determine the user interface layout and interaction logic. By parsing this information, the parsing results are obtained, allowing the extraction of interface component descriptions and data interaction logic descriptions. The interface component descriptions can be understood as the detailed specifications of the various visual and non-visual elements that make up the business page, such as input boxes, buttons, dropdown menus, tables, and their layout information. The data interaction logic descriptions specify how these interface components interact with backend data, including rules for data reading, writing, validation, and event triggering.

[0093] Furthermore, based on the obtained interface component descriptions and data interaction logic descriptions, a business mapping relationship is established between interface elements and business requirement information. Interface elements refer to specific interactive components in a business page, such as input boxes and display areas. Business requirement information can be used to determine business processing rules, such as data validation rules and execution conditions for steps in the business process. These rules correspond to the business's data processing logic. Establishing a business mapping relationship means associating interface elements with these business requirement rules and data processing logic, clarifying which interface element corresponds to which business entity parameter, which data validation rules need to be followed, and which business process execution conditions are triggered. For example, a customer name input box might be mapped to the business entity parameter "Customer Name: String type". Then, based on this business entity parameter, it can be associated with the data validation rule "Not Empty Validation". This rule checks whether the input information in the customer name input box is an empty string, determining whether the input information conforms to a preset data input format. If the input information is not an empty string, the specific customer name can be determined based on the input information, and then corresponding business processing can be performed based on the determined customer name, improving business processing efficiency.

[0094] After establishing a business mapping relationship between interface elements and business requirement information, this embodiment of the application can generate a system business page corresponding to the business requirement information based on the established business mapping relationship and using code snippets corresponding to the interface elements. Here, code snippets are predefined, reusable program code modules, each corresponding to the functional implementation of a type of interface element. For example, a text input box interface element may correspond to a code snippet containing HTML input tags, CSS styles, and JavaScript event handling logic. By intelligently combining and filling these code snippets according to the business mapping relationship, a system business page that meets business requirements and has complete functionality and interactive logic can be automatically generated.

[0095] This application's solution involves structured parsing of business page design information, transforming abstract design concepts into programmable interface component descriptions and data interaction logic descriptions. Based on these descriptions, a precise mapping is established between interface elements and business requirement rules. Through this mapping, the system can understand the specific role of each interface element in the business process and the required business logic. Ultimately, based on these explicit mapping relationships, the system can intelligently select and combine pre-defined code snippets to automatically construct complete system business pages. This approach avoids logical errors and inconsistencies that may occur during traditional manual coding, significantly improving development efficiency and page quality.

[0096] The above technical solution enables a high degree of automation and intelligence in the business page generation process. Specifically, by meticulously analyzing the business page design information and establishing business mapping relationships, the system can accurately understand business requirements and transform them into executable code. This significantly reduces the workload of manual coding, shortens the development cycle, and lowers development costs. Furthermore, due to the adoption of standardized code snippets and automated generation mechanisms, the generated system business pages exhibit higher consistency and a lower error rate, thereby improving the overall system quality and user experience.

[0097] like Figure 2 As shown, this application provides a system for generating system business pages, which may specifically include: The system comprises: an identification agent 21 for acquiring business requirement information; an analysis agent 22 for performing system analysis based on the business requirement information to obtain system analysis information; a data design agent 23 for performing data structure design based on the system analysis information to obtain data structure design information; a page design agent 24 for designing business pages based on the business requirement information, combined with system analysis information and data structure design information to obtain business page design information; and a programming agent 25 for performing automatic programming based on the business page design information to obtain the system business page corresponding to the business requirement information.

[0098] In the context of a system business page generation system, an intelligent agent refers to a software module or program with specific functions that can independently or collaboratively complete data processing tasks. The system business page generation system proposed in this application introduces a series of specialized intelligent agents, organically integrating and automating various stages such as business requirement acquisition, system analysis, data structure design, business page design, and automatic programming. Specifically, the identification intelligent agent 21 efficiently captures business requirements, while the analysis intelligent agent 22 accurately parses the requirements and identifies business entity parameters, effectively avoiding semantic conflicts caused by inconsistent understanding of requirements in traditional methods. The data design intelligent agent 23 automatically generates reasonable data structures based on the analysis results, solving the problem of inconsistent data structuring standards across different departments and reducing data redundancy and missing data. The page design intelligent agent 24 automatically generates business page designs that conform to business logic and user experience based on multi-dimensional information, greatly reducing the workload of manual design. Finally, the programming intelligent agent 25 quickly transforms the design information into executable system business pages, thereby shortening the system business page development cycle and improving development efficiency.

[0099] The system business page generation system provided in this embodiment is used to execute the steps in the system business page generation method provided in the first aspect above. The principle of the system business page generation system provided in this embodiment is the same as that of the system business page generation method provided in the first aspect above, and will not be discussed in detail here.

[0100] In some implementations, when the data design agent 23 performs data structure design based on system analysis information to obtain data structure design information, it specifically performs the following: business entity attribute identification based on business entity parameters in the system analysis information to obtain business entity attribute information; attribute classification based on preset data requirements corresponding to the business entity attribute information to obtain attribute categories corresponding to the business entity attribute information; data table design based on attribute categories for each business entity attribute information to obtain the corresponding data table; data synchronization strategy and attribute access control configuration information corresponding to the business entity attribute information generated based on the data table; and the data table, data synchronization strategy, and attribute access control configuration are used as data structure design information.

[0101] This application's solution effectively addresses the limitations of traditional data structure design in handling complex business scenarios by introducing a data design intelligent agent 23 for business entity attribute identification, attribute classification based on data requirement information, hierarchical data table design, and the generation of data synchronization strategies and attribute access control configuration information. Specifically, the data design intelligent agent 23 performs detailed attribute identification of business entity parameters, enabling a comprehensive understanding of the data items required by the business. Furthermore, based on the differences in data granularity and update frequency requirements among different business departments, business entity attribute information is divided into core shared attribute categories and specific attribute categories, allowing the data structure design to accurately match actual business needs. Thus, data tables are designed for different attribute categories, resulting in data tables corresponding to the business entity attribute information. These tables include core data tables and extended data tables, avoiding the problem that a single data table structure cannot adequately address both generality and specificity, effectively reducing data redundancy, and improving the flexibility of the data model. Meanwhile, the generation of data synchronization strategies ensures data consistency across data tables, while attribute access control configuration information fundamentally guarantees data security and compliance, preventing unauthorized access and modification, thus building a data management foundation that is both efficient and secure.

[0102] This embodiment provides a system business page generation system for executing the steps in the system business page generation method provided in the first aspect above: identifying business entity attributes based on business entity parameters in system analysis information to obtain business entity attribute information; classifying attributes according to preset data requirements information corresponding to the business entity attribute information to obtain attribute categories corresponding to the business entity attribute information; designing a data table based on the attribute category for each business entity attribute information to obtain a data table corresponding to the business entity attribute information; generating a data synchronization strategy and attribute access control configuration information corresponding to the business entity attribute information based on the data table; and using the data table, data synchronization strategy, and attribute access control configuration information as data structure design information. The principle of the system business page generation system provided in this embodiment is the same as that of the system business page generation method provided in the first aspect above, and will not be discussed in detail here.

[0103] Please refer to Figure 3 , Figure 3 This application provides a schematic diagram of the structure of an electronic device 13, comprising a processor 1301 and a memory 1302. The processor 1301 and the memory 1302 are interconnected and communicate with each other via a communication bus 1303 and / or other forms of connection mechanism (not shown). The memory 1302 stores computer-readable instructions executable by the processor 1301. When the electronic device is running, the processor 1301 executes the computer-readable instructions to perform any of the optional implementation methods in the above embodiments, thereby achieving the following functions: obtaining business requirement information; performing system analysis based on the business requirement information to obtain system analysis information; performing data structure design based on the system analysis information to obtain data structure design information; performing business page design based on the business requirement information, combined with system analysis information and data structure design information to obtain business page design information; and performing automatic programming processing based on the business page design information to obtain the system business page corresponding to the business requirement information.

[0104] This application provides a computer-readable storage medium storing a computer program thereon. When the computer program is executed by a processor, it performs the method in any optional implementation of the above embodiments to achieve the following functions: obtaining business requirement information; performing system analysis based on the business requirement information to obtain system analysis information; performing data structure design based on the system analysis information to obtain data structure design information; performing business page design based on the business requirement information, combined with the system analysis information and the data structure design information to obtain business page design information; and performing automatic programming processing based on the business page design information to obtain the system business page corresponding to the business requirement information. The computer-readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Red-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0105] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and there may be other division methods in actual implementation. Furthermore, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Additionally, the coupling or direct coupling or communication connection shown or discussed may be through some communication interface; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0106] Furthermore, the units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0107] Furthermore, the functional modules in the various embodiments of this application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0108] In this document, relational terms such as first and second are used only to distinguish one entity or operation from another entity or operation, without necessarily requiring or implying any such actual relationship or order between these entities or operations.

[0109] The above are merely embodiments of this application and are not intended to limit the scope of protection of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A method for generating system business pages, characterized in that, Including the following steps: Obtain business requirements information; Based on the aforementioned business requirements information, system analysis is performed to obtain system analysis information; Based on the system analysis information, data structure design is performed to obtain data structure design information; Based on the business requirements information, combined with the system analysis information and the data structure design information, the business page is designed to obtain the business page design information; Automatic programming processing is performed based on the business page design information to obtain the system business page corresponding to the business requirement information.

2. The system business page generation method according to claim 1, characterized in that, The system business page generation method is applied to a smart terminal, which has pre-installed instant messaging software. The step of obtaining business requirement information includes: Obtain the messages received by the instant messaging software; Detect whether the message contains preset business requirement keywords; If the message contains preset business requirement keywords, then the message is identified as the business requirement information.

3. The system business page generation method according to claim 1, characterized in that, The business requirement information includes business object information and context information corresponding to the business object information. The system analysis based on the business requirement information to obtain system analysis information includes: Identify the business object information contained in the business requirement information; When it is identified that the business object information has multiple definition information across business domains in the preset business reference information set, the context information corresponding to the business object information is extracted from the business requirement information; Determine the domain indication features based on the context information, and use the domain indication features to determine the target business domain corresponding to the business object information; Extract target definition information corresponding to the target business domain from the business reference information set; Based on the target definition information, determine the business entity parameters; The parameters of the business entity are determined as the system analysis information.

4. The system business page generation method according to claim 1, characterized in that, The process of designing a data structure based on the system analysis information to obtain data structure design information includes: Based on the business entity parameters in the system analysis information, business entity attribute identification is performed to obtain business entity attribute information; Based on the preset data requirements information corresponding to the business entity attribute information, attribute classification is performed to obtain the attribute category corresponding to the business entity attribute information. For each of the business entity attribute information, a data table is designed based on the attribute category to obtain the data table corresponding to the business entity attribute information. Generate a data synchronization strategy and attribute access control configuration information corresponding to the attribute information of the business entity based on the data table; The data table, the data synchronization strategy, and the attribute access control configuration information are used as the data structure design information.

5. The system business page generation method according to claim 4, characterized in that, The business page design is performed based on the business requirements information, combined with the system analysis information and the data structure design information, to obtain business page design information, including: Based on the aforementioned business requirement information, obtain a preset general business page template; Based on the system analysis information, business process identification is performed to obtain the target business process corresponding to the business requirement information; Based on the target business process and the attribute access control configuration information in the data structure design information, the target business entity attribute information is filtered out from the data table in the data structure design information. Extract the data requirement information corresponding to the attribute information of the target business entity from the data structure design information; Based on the data requirements, configure the interface element placeholders corresponding to the target business entity attribute information; Based on the interface element placeholders, the interface elements corresponding to the target business entity attribute information are filled into the general business page template to generate business page design information.

6. The system business page generation method according to claim 5, characterized in that, The automatic programming process based on business page design information to obtain the system business page corresponding to the business requirement information includes: The business page design information is parsed to obtain the interface component description and data interaction logic description; Based on the interface component description and data interaction logic description, establish a business mapping relationship between the interface elements and the business requirement information; Based on the business mapping relationship, the system business page corresponding to the business requirement information is generated using the code snippets corresponding to the interface elements.

7. A system for generating system business pages, characterized in that, include: Identify intelligent agents to obtain business requirement information; An analytical agent is used to perform system analysis based on the business requirement information to obtain system analysis information. A data design agent is used to design data structures based on the system analysis information to obtain data structure design information. A page design intelligent agent is used to design business pages based on the business requirement information, combined with the system analysis information and the data structure design information, to obtain business page design information; A programming intelligent agent is used to automatically process programming information based on business page design information to obtain the system business page corresponding to the business requirement information.

8. The system for generating business pages according to claim 7, characterized in that, When the data design agent performs data structure design based on the system analysis information and obtains data structure design information, it specifically executes the following: Based on the business entity parameters in the system analysis information, business entity attribute identification is performed to obtain business entity attribute information; Based on the preset data requirements information corresponding to the business entity attribute information, attribute classification is performed to obtain the attribute category corresponding to the business entity attribute information. For each of the business entity attribute information, a data table is designed based on the attribute category to obtain the data table corresponding to the business entity attribute information. Generate a data synchronization strategy and attribute access control configuration information corresponding to the attribute information of the business entity based on the data table; The data table, the data synchronization strategy, and the attribute access control configuration information are used as the data structure design information.

9. An electronic device, characterized in that, It includes a processor and a memory, the memory storing computer-readable instructions, which, when executed by the processor, perform the steps of a system business page generation method as described in any one of claims 1-6.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it performs the steps in the system business page generation method as described in any one of claims 1-6.

Images