Page generation method and device, electronic equipment and computer readable storage medium
By allowing users to directly input product requirement documents and edit the structured parsing results in the editing area, the problem of inconvenient requirement adjustment in existing AI-assisted development tools is solved, achieving more efficient and accurate page generation.
Patent Information
- Application Number
- CN202511784164.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-28
- Publication Date
- 2026-03-03
AI Technical Summary
Existing AI-assisted development tools require users to repeatedly adjust requirements through dialogue when generating code and products, resulting in low ease of use and efficiency.
Users directly input product requirement documents, which are then parsed using a model. The structured parsing results are displayed in the editing area of the interactive interface, allowing users to flexibly edit the parsing results and ultimately generate the target page.
It improves the flexibility and efficiency of users modifying their requirements, enhances the accuracy and efficiency of target page generation, and simplifies the development process.
Smart Images

Figure CN121597212A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of computer technology, and in particular to a page generation method, apparatus, electronic device, and computer-readable storage medium. Background Technology
[0002] With the rapid development of artificial intelligence (AI) technology, AI-assisted development tools have gradually emerged. These tools can assist front-end product developers in writing code and generating corresponding products, aiming to improve development efficiency. Summary of the Invention
[0003] According to some embodiments of this disclosure, a page generation method is provided, comprising: responding to a user inputting a product requirement document, parsing the product requirement document using a model, and displaying a structured parsing result of the product requirement document in an editing area of an interactive interface, wherein the parsing result includes information on technical elements used to generate a target page, the information on technical elements including information on one or more modules and information on one or more interfaces, and the information on each module including information on components associated with each module; responding to a user editing operation on the parsing result in the editing area, displaying the edited parsing result; and responding to a user triggering a target page generation function, generating the target page based on the edited parsing result.
[0004] According to some other embodiments of this disclosure, a page generation apparatus is provided, comprising: a first display module configured to, in response to a user inputting a product requirement document, parse the product requirement document using a model, and display a structured parsing result of the product requirement document in an editing area of an interactive interface, wherein the parsing result includes information on technical elements used to generate a target page, the information on technical elements including information on one or more modules and information on one or more interfaces, and the information on each module including information on components associated with each module; a second display module configured to, in response to a user editing operation on the parsing result in the editing area, display the edited parsing result; and a generation module configured to, in response to a user triggering a target page generation function, generate the target page based on the edited parsing result.
[0005] According to further embodiments of the present disclosure, an electronic device is provided, including: a memory; and a processor coupled to the memory, the processor being configured to execute a page generation method of any embodiment of the present disclosure based on instructions stored in the memory.
[0006] According to further embodiments of the present disclosure, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, performs a page generation method according to any embodiment of the present disclosure.
[0007] Other features, aspects, and advantages of this disclosure will become clear from the following detailed description of exemplary embodiments with reference to the accompanying drawings. Attached Figure Description
[0008] Embodiments of this disclosure are described below with reference to the accompanying drawings. It should be understood that the drawings described below are merely illustrative of some embodiments of this disclosure and are not intended to limit the scope of this disclosure. In the drawings:
[0009] Figure 1 A flowchart illustrating a page generation method according to some embodiments of this disclosure is shown;
[0010] Figures 2-9B A schematic diagram illustrating the interactive interface of some embodiments of this disclosure;
[0011] Figure 10 A flowchart illustrating a page generation method according to other embodiments of this disclosure is shown;
[0012] Figure 11 A flowchart illustrating a page generation method according to some embodiments of the present disclosure is shown;
[0013] Figure 12 This diagram illustrates the structure of a page generation apparatus according to some embodiments of the present disclosure;
[0014] Figure 13 This invention discloses schematic diagrams of the structure of electronic devices according to some embodiments of the present disclosure;
[0015] Figure 14 A schematic diagram of the structure of an electronic device according to other embodiments of the present disclosure is shown. Detailed Implementation
[0016] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. It should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein.
[0017] It should be understood that the various steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect. Unless otherwise specifically stated, the relative arrangement of steps set forth in these embodiments should be interpreted as merely exemplary and does not limit the scope of this disclosure.
[0018] As used in this disclosure, the term "comprising" and its variations are open-ended terms that include at least the following elements / features but do not exclude other elements / features, i.e., "including but not limited to". The term "based on" means "at least partially based on".
[0019] It should be noted that the concepts of "first," "second," etc., used in this disclosure are used only to distinguish different devices, modules, or units, and are not intended to define the order of functions performed by these devices, modules, or units or their interdependencies. Unless otherwise specified, the concepts of "first," "second," etc., are not intended to imply that the objects described herein must be in a given temporal, spatial, rank, or any other given order.
[0020] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".
[0021] The embodiments of this disclosure are described in detail below with reference to the accompanying drawings; however, this disclosure is not limited to these specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. Furthermore, in one or more embodiments, specific features, structures, or characteristics can be combined in any suitable manner that will be apparent to those skilled in the art from this disclosure.
[0022] AI-assisted development tools can assist developers in creating front-end products. Currently, most AI-assisted development tools interact with users through dialogue. For example, users can input their requirements in the dialogue interface of the AI-assisted development tool, and the tool will generate code and products based on those requirements. If the user is not satisfied with the generated code or product and needs to make adjustments, or if the user needs to modify their requirements, they must re-enter the adjustment information in the dialogue interface, clearly and accurately describing the parts that need to be modified and how to modify them, so that the AI-assisted development tool can accurately regenerate the code and product.
[0023] This development method, which relies on users interacting with AI-assisted development tools, places high demands on the accuracy of the user's input. In many cases, users have to repeatedly adjust the dialogue information for the AI-assisted development tools to accurately understand their needs, which reduces the ease of use and development efficiency for users.
[0024] To address the aforementioned issues, this disclosure proposes a page generation method. Users can directly input product requirement documents, which are then parsed using a model. The structured parsing results are displayed in the editing area of the interactive interface. Furthermore, users can directly edit the parsing results in the editing area, displaying the edited results. Subsequently, in response to user-triggered target page generation, the target page is generated based on the edited parsing results. Based on this page generation method, users can directly input product requirement documents without needing to input requirement information through a dialog. An intermediate parsing result is generated for the product requirement document. This parsing result includes information on the technical elements used to generate the target page, and is structured, making it more readable and facilitating quick location of technical elements by the user. The parsing results displayed in the editing area can be flexibly and quickly edited by the user. Users can edit key technical elements such as modules, interfaces, and components without needing to input editing commands through a dialog, improving the flexibility, efficiency, and accuracy of modifying requirements. Furthermore, the target page can be easily and quickly generated based on the edited parsing results, improving the efficiency and accuracy of target page generation. The overall solution is designed to assist users in developing target pages, thereby improving the efficiency and accuracy of target page development.
[0025] The following is combined Figures 1-11 This disclosure describes a page generation method. This page generation method can be executed by a page generation device, electronic device, or the like. The page generation device can be implemented in software and / or hardware. For example, the page generation device can be an entity that can interact with a user and implement the page generation method, such as application software, an agent, or a bot.
[0026] Figure 1 Flowcharts of some embodiments of the method for generating pages according to this disclosure. For example... Figure 1 As shown, the page generation method of this embodiment includes steps S102 to S106.
[0027] In step S102, in response to the user input of a product requirement document, the model is used to parse the product requirement document, and the structured parsing results of the product requirement document are displayed in the editing area of the interactive interface.
[0028] A Product Requirement Document (PRD) includes the product's requirements. For example, a product might consist of one or more pages. The PRD can include descriptions of each page, such as global information, functional descriptions of elements, style information for elements, and design diagrams (reference images) for one or more pages and modules. Further design information can include interface configuration information, such as the name, unique path, and brief description of each interface. Additionally, the PRD can include the product's architecture, background, and application scenarios, among other things. Interface configuration information can also be a separate document, such as a separate backend technical solution document containing interface configuration information. If the backend technical solution document and the PRD are two separate documents, users can input both documents, and the model can parse them to obtain structured results. For example, an interactive interface can be displayed, including input and editing areas. When a user inputs the PRD through the input area, the model can parse the PRD. For example, in the first state, the interface displays an input area. In response to the user inputting a product requirement document into the input area, triggering the product requirement document parsing function, and using a model to parse the product requirement document, the interface switches to the second state, displaying both the input and editing areas. The structured parsing results are displayed in the editing area. The display method of the interface is not limited to the example given.
[0029] For example, a user can directly paste a product requirement document into the input area. Alternatively, the input area can display a document upload control; in response to the user triggering the document upload control, one or more candidate folders and one or more candidate files in the current folder are displayed; and in response to the user selecting a product requirement document, the product requirement document is retrieved. Another example is a target function trigger control in the input area, used to trigger the function of generating a page based on the product requirement document; in response to the user triggering the target function trigger control, a document upload interface is displayed, including a first input sub-area; in response to the user entering the address information (link) of the product requirement document in the first input sub-area, the product requirement document is retrieved. The ways users input product requirement documents are not limited to the examples above.
[0030] For example, after obtaining the product requirements document, the model can be used to parse the product requirements document directly, or it can respond to the user's input of instructions in the input area or trigger specific controls to instruct the generation of a page based on the product requirements document and use the model to parse the product requirements document, and so on.
[0031] For example, the model can be a machine learning model, a neural network model, a large language model, etc., and is not limited to the examples given. The model can be used to perform natural language understanding and parsing of product requirement documents, extracting key information and generating structured parsing results. For example, the structured parsing results can be displayed in Markdown (a lightweight markup language).
[0032] The parsing result can be understood as a technical solution described from a front-end development perspective for generating the target page. For example, the parsing result includes information about the technical elements used to generate the target page. This information includes one or more modules and one or more interfaces. Each module's information includes information about its associated components. For instance, the target page might include a filtering module, a list display module, etc. The filtering module includes input components, selection components, search components, etc., and one or more interfaces include a query event list interface, a create basic event interface, etc. In the structured parsing structure, the information of multiple technical elements is laid out according to their hierarchical relationship.
[0033] In step S104, in response to the user's editing operation on the parsing result in the editing area, the edited parsing result is displayed.
[0034] The parsing results in the editing area of the interactive interface can be directly edited, and the editing process and the resulting parsing results can be displayed in the editing area. For example, users can add, modify, and delete technical elements in the editing area. For instance, users can change any interface or component, add interfaces or components, or delete interfaces or components.
[0035] In step S106, in response to the user triggering the target page generation function, the target page is generated based on the edited parsing results.
[0036] For example, a generation control can be displayed in the editing or input area. In response to the user triggering the generation control, the target page is generated based on the parsed results after editing. Users can also trigger the target page generation function in other ways, such as entering a command to generate the target page in the input area, etc., not limited to the examples given.
[0037] In the method of the above embodiments, users can directly input product requirement documents, parse the product requirement documents using a model, and display the structured parsing results of the product requirement documents in the editing area of the interactive interface. Furthermore, users can directly edit the parsing results in the editing area, displaying the edited parsing results. Then, in response to the user triggering the target page generation function, the target page is generated based on the edited parsing results. Based on the page generation method of the above embodiments, users can directly input product requirement documents without needing to input requirement information through a dialogue. An intermediate parsing result is generated for the product requirement document. This parsing result includes information on the technical elements used to generate the target page, and is structured information, making it more readable and easier for users to quickly locate the technical elements in the parsing result. The parsing results displayed in the editing area can be edited flexibly and quickly by the user. Users can edit key technical elements such as modules, interfaces, and components without needing to input editing commands through a dialogue, improving the flexibility, efficiency, and accuracy of user requirement modification. Furthermore, the target page can be generated conveniently and quickly based on the edited parsing results, improving the efficiency and accuracy of target page generation. The overall solution is designed to assist users in developing target pages, thereby improving the efficiency and accuracy of target page development.
[0038] The following describes some methods for using models to parse product requirement documents and displaying the structured parsing results of the product requirement documents in the editing area of the interactive interface.
[0039] In some embodiments, in response to a user inputting a product requirement document, the model is used to parse the product requirement document. Displaying the structured parsing result of the product requirement document in the editing area of the interactive interface includes: displaying the interactive interface, wherein the interactive interface includes an input area, a session information display area, and an editing area; in response to a user inputting a product requirement document through the input area, the model is used to parse the product requirement document; process information of parsing the product requirement document is displayed in the session information display area; and the structured parsing result of the product requirement document is displayed in the editing area.
[0040] The input area receives user input, while the conversation information display area displays dialogue information generated based on that input. The input area and the conversation information display area can constitute a dialogue area. For example, the dialogue information displayed in the conversation information display area might include process information related to parsing a product requirements document, such as the thought process involved in parsing the document, information requiring user confirmation during the parsing process, the multiple steps involved in parsing the document, and the results of each step. The conversation information display area and the editing area are used to display different types of response information generated based on user input.
[0041] like Figure 2 As shown, the interactive interface 200 includes an input area 201, a session information display area 202, and an editing area 203. The structure and layout of the interactive interface are not limited to... Figure 2 Examples given. For example... Figure 2 As shown, a target function trigger control (“PRD generation page”) 204 can be displayed above the input area 201. In response to the user triggering the target function, the target function trigger control 204 can display... Figure 3 The interface shown.
[0042] like Figure 3 As shown, in response to the user triggering the target function trigger control 204, the document upload interface 300 is displayed. The document upload interface 300 displays a first input sub-area 301 for entering the address information (link) of the product requirement document. If the product requirement document includes interface configuration information or a backend technical solution, only the address information of the product requirement document needs to be entered. If the product requirement document and the interface configuration information (or backend technical solution) are two separate documents, the address information (link) of the interface configuration information (or backend technical solution) can be entered in the second input sub-area 302. The document upload interface 300 can be displayed in the form of a window, panel, overlay, etc., and is not limited to these forms. Figure 3 Examples provided.
[0043] The method described in the above embodiments divides the interactive interface into an input area, a conversation information display area, and an editing area. The conversation information display area can be used to engage in dialogue with the user in a more natural and conversational manner, while the editing area can be used to display structured parsing results and other technical solutions. The overall display effect is clearer and more accurate. The division of different functional areas allows users to quickly locate different content and helps them understand different content. Furthermore, users can engage in dialogue through the input area and the conversation information display area, edit parsing results through the editing area, and perform different interactions in different functional areas, thereby improving the accuracy of the interaction and enhancing the user's operating experience.
[0044] In some embodiments, parsing a product requirement document using a model includes: parsing basic information of the product requirement document using a model, wherein the basic information includes at least one of one or more pages, one or more application scenarios, and one or more reference images corresponding to the product requirement document; displaying process information for parsing the product requirement document in a session information display area includes: displaying options corresponding to the basic information in the session information display area, wherein the options corresponding to the basic information include at least one of options for one or more pages, options for one or more application scenarios, and options for processing methods of one or more reference images; in response to the user confirming at least one of the target page, target application scenario, and target processing method of one or more reference images based on the options corresponding to the basic information, displaying a confirmation status for at least one of the target page, target application scenario, and target processing method of one or more reference images.
[0045] The product requirements document can be preliminarily analyzed using a model to confirm with the user the page to be generated (target page), the product's application scenario (target scenario), and the required processing method for one or more reference images (target processing method). For example, the process information for parsing the product requirements document includes at least one of the following: options corresponding to basic information, the target page with confirmed status, the target application scenario, and the target processing method for one or more reference images.
[0046] The session information display area can display at least one of the following options: options for one or more pages, options for one or more application scenarios, and options for processing one or more reference images. Users can confirm at least one of the target page, target application scenario, and target processing method for one or more reference images through at least one option.
[0047] like Figure 2As shown, the session information display area 202 displays options 205 and 206 for multiple pages, options 208 and 209 for multiple scenarios, and options 211, 212, and 213 for multiple processing methods. Sub-input areas 207, 210, and 214 can also be displayed for different basic information to receive user input instructions. For example, a user can trigger options 205 or 206 to select a target page, or input the target page to be parsed and generated through sub-input area 207; a user can trigger options 208 or 209 to select a target scenario, or input the target scenario of the product application through sub-input area 210; a user can trigger options 207, 210, or 214 to select a target processing method, or input the desired target processing method through sub-input area 214. For example, after a user triggers an option, that option can be displayed with a preset effect, indicating a confirmed state. The session information display area 202 can also display a confirmation control 215 to confirm the target page, target application scenario, and target processing method. If the user does not select or enter at least one of the target page, target application scenario, and target processing method, the default option can be used as the user's confirmation option. For example, the option to display the first page, the option to display the first application scenario, and the option to display the first processing method can be used as the default option.
[0048] The method described in the above embodiments uses a model to perform preliminary analysis of the product requirement document, displays options corresponding to basic information, and allows the user to confirm the target page, target application scenario, and target processing method of one or more reference images. This helps to more accurately analyze the product requirement document and generate analysis results and target pages more accurately in the future.
[0049] In some embodiments, parsing a product requirement document using a model further includes: parsing the product requirement document based on at least one of a target page, a target application scenario, and a target processing method for one or more reference images, wherein the target processing method for one or more reference images includes a first processing method that preferentially generates a target page based on one or more reference images, a second processing method that preferentially generates a target page based on the text of the product requirement document, or a third processing method that generates a target page based solely on the text.
[0050] After identifying the target page, target application scenario, and target processing method, the product requirements document is further analyzed based on these criteria. For example, the model is used to identify content in the product requirements document related to the target page, and semantic understanding is performed on this content based on the target application scenario and target processing method to generate structured parsing results. For example... Figure 2As shown, in response to the user triggering the confirmation control 215, the product requirements document is parsed based on at least one of the target page, target application scenario, and target processing method of one or more reference images.
[0051] One or more reference images can include at least one of the following: reference images for one or more pages, reference images for one or more modules, or reference images for one or more components. The product requirements document includes both text and reference images, and users can choose a specific target processing method from several options. For example, the first processing method could indicate that the model prioritizes referencing the content of one or more reference images to generate the parsing results and target page; if the text and the content of one or more reference images are inconsistent, the parsing results and target page are generated primarily based on the content of one or more reference images. The second processing method could indicate that the model prioritizes referencing the text in the product requirements document to generate the parsing results and target page. The third processing method indicates that the model generates the parsing results and target page solely based on the text in the product requirements document. Figure 2 As shown, users can also input different processing methods for different reference images through sub-input area 214.
[0052] The method described in the above embodiments further parses the product requirement document based on the target page, target application scenario, and target processing method of one or more reference images confirmed by the user, which can improve the accuracy of the parsing results and improve the accuracy and efficiency of target page generation.
[0053] In some embodiments, the product requirement document is parsed using a model. The structured parsing result of the product requirement document is displayed in the editing area of the interactive interface, which includes: parsing the product requirement document using a model, determining multiple technical elements and the relationships and hierarchies between the multiple technical elements, and generating structured parsing results based on the relationships and hierarchies between the multiple technical elements.
[0054] For example, technical elements can be categorized into page-level, module-level, interface-level, component-level, and interface field-level. Page-level technical elements can be displayed at the top of the parsed results. Module-level and interface-level elements can be set to the same level, while different modules can have different module levels. The parsed content for different modules can be laid out according to their nesting relationships and levels. The component level and the corresponding interface field level are lower than the module level. For any module, the parsed content for that module and its contained components and interface fields can be laid out based on the components and interface fields it includes.
[0055] The method described in the above embodiments uses a model to parse product requirement documents, identify multiple technical elements, and lay out the multiple technical elements according to the relationships and hierarchies between them to generate structured parsing results. This allows users to more clearly and accurately understand the relationships and hierarchies between multiple technical elements, locate different technical elements more quickly, and improve the accuracy and convenience of operation.
[0056] In some embodiments, the product requirement document is parsed using a model. The structured parsing results of the product requirement document are displayed in the editing area of the interactive interface, including: parsing multiple functional descriptions in the product requirement document, the corresponding interface configuration information and component library using the model; generating structured parsing results based on the matching results of multiple functional descriptions with one or more interfaces in the interface configuration information and the matching results of multiple functional descriptions with components in the component library; and displaying the structured parsing results in the editing area.
[0057] The interface configuration information corresponding to the product requirements document can be in a separate document or be part of the product requirements document. The component library can be pre-built and include multiple components. Using a model to semantically understand the product requirements document, one or more required interfaces and one or more required components are identified. Matching is performed between the interface configuration information and the component library to determine one or more interfaces and the components associated with each module in the parsed results. The parsed results display the functional descriptions and identifiers of one or more interfaces, as well as the functional descriptions and identifiers of the components associated with each module. The parsed results can also display controls for each interface and each component. In response to a user triggering a control on an interface, information about that interface, such as output parameters and input parameters, can be displayed. In response to a user triggering a control on a component, information about that component, such as styles and reference images, can be displayed. The functional descriptions of one or more interfaces and the functional descriptions of the components associated with each module displayed in the parsed results can be the same as the corresponding functional descriptions in the product requirements document, or the corresponding functional descriptions in the product requirements document can be converted into more concise and standardized functional descriptions.
[0058] An interface management platform or library can be configured. This platform or library stores and manages information related to each interface, such as its functional description and parameter configuration. The parameter configuration information for each interface includes the fields, types, and explanations of its input and output parameters. The interface configuration information (or backend technical solution) can initially only briefly describe the interface. However, by matching the interface configuration information with the stored information for each interface, detailed configuration information for each interface can be determined.
[0059] The method described in the above embodiments associates multiple functional descriptions in the PRD with one or more interfaces in the interface configuration information and with components in the component library to generate structured parsing results. This achieves automatic association between the product requirement document, interface configuration information, and existing components, making it easier for users to edit the parsing results and improving the efficiency and accuracy of subsequent target page generation.
[0060] In some embodiments, for each component, in response to the existence of a call relationship between the component and the interface, the component, the component's functional description information, and the interface field corresponding to the component are associated, wherein the component's information includes the component's identifier, functional description information, and the interface field corresponding to the component.
[0061] If a component needs to call an interface, the corresponding interface fields for that component are further determined based on its functional description and interface configuration information. The parsing result displays the component's identifier, functional description, and corresponding interface fields. The parsing result can also display controls for each interface field. In response to a user triggering a control for a specific interface field, the result can display information about the interface corresponding to that field.
[0062] The method in the above embodiments automatically associates each component with the corresponding interface field in response to the existence of a call relationship between the component and the interface. This facilitates the user's editing of the parsing results and improves the efficiency and accuracy of subsequent target page generation.
[0063] In some embodiments, the model selects a target code template from a code template library based on the semantic information of the product requirements document, and displays the target code template's information in the parsing results. For example, a control for displaying the target code template can be used to display detailed information about the target code template in response to user activation.
[0064] Target pages can be generated based on target code templates. By automatically matching target code templates to product requirement documents, it is easier for users to view and edit code templates, thus improving the efficiency and accuracy of subsequent target page generation.
[0065] The following describes the method for displaying structured parsing results and the method for displaying edited parsing results based on user editing operations.
[0066] In some embodiments, the information of the technical elements may also include at least one of the following: global configuration information of the target page, reference image of the target page, reference image of one or more modules, and information of one or more code templates. The information of the components associated with each module includes the identifier and interface field of the components associated with each module.
[0067] For example, the global configuration information of the target page includes at least one of the following: the target page title, navigation information, routing information, access control information, layout information, and function description information. Each code template, each component, each interface, and each interface field can be configured with corresponding controls for easy editing and operation by users.
[0068] like Figure 2 As shown, the editing area 203 includes global configuration information for the target page, information about related interfaces, and information about one or more modules. The information about related interfaces includes information about multiple interfaces. Each interface's information can include its name, functional description, and corresponding controls; for example, displaying control 218 for a specific interface. The information about each module includes its functional description, related components, and the corresponding interface fields. For each component, the component's name, functional description, and controls can be displayed. If the component needs to call an interface, the controls for the corresponding interface fields can be displayed. For example, displaying control 219 for a specific component and control 220 for its corresponding interface fields. Figure 2 As shown, for a given code template, a control 216 can be displayed; for a given reference image, a thumbnail of that reference image can be displayed, etc.
[0069] like Figure 2 As shown, a directory corresponding to the parsed results can also be generated. This directory can include options for multiple modules, and can be further expanded to include options for multiple interfaces, multiple components, etc. In response to triggering an option, the content corresponding to that option is located in the editing area.
[0070] The method described above parses the product requirement document into multiple technical elements and displays them in a structured manner, enabling users to quickly and accurately locate different types of technical elements, thereby improving the efficiency of editing operations and enhancing development efficiency.
[0071] Users can directly add, delete, and modify the parsed results. For example, they can modify the global configuration information of the target page, such as the title, navigation information, routing information, access control information, layout information, and function description information. If a certain global configuration information is missing, it can be added, or some global configuration information can be deleted, such as access control information.
[0072] In some embodiments, in response to a user's editing operation on the parsing result in the editing area, displaying the edited parsing result includes: in response to a user's operation of replacing a first element in the technical elements with a second element, replacing the first element with the second element, and displaying the information of the second element in the edited parsing result, wherein the first element and the second element are of the same category, the first element includes at least one of a first component, a first interface field, a first interface, a first reference image, and a first code template, and the second element includes at least one of a second component, a second interface field, a second interface, a second reference image, and a second code template.
[0073] Editing the parsed results includes replacing the first element with the second element in a technical element. Users can choose to replace a specific technical element. They can either directly delete the first element and enter the second element to replace it, or trigger the control for the first element and select the second element in the selection interface to replace the first element. The specific operation method can be configured according to requirements.
[0074] Based on the method described in the above embodiments, users can modify technical elements more conveniently and quickly without having to describe the modification method through dialogue, which improves operational efficiency and accuracy, and also improves the efficiency and accuracy of subsequent target page generation.
[0075] In some embodiments, in response to a user's operation of replacing a first element in a technical element with a second element, replacing the first element with the second element and displaying the information of the second element in the edited parsing result includes: in response to a user triggering a change to the first component, displaying information of one or more candidate components in the component library; in response to a user selecting a second component among one or more candidate components, replacing the first component with the second component and displaying the information of the second component in the parsing result, wherein the first element includes the first component and the second element includes the second component; and / or in response to a user triggering a change to the first interface field, displaying information of one or more candidate interfaces; in response to a user selecting a first candidate interface among one or more candidate interfaces, displaying the information of the interface field corresponding to the first candidate interface; in response to a user selecting a second interface field among the interface fields corresponding to the first candidate interface, replacing the first interface field with the second interface field and displaying the information of the second interface field in the parsing result, wherein the first element includes the first interface field and the second element includes the second interface field; and / or in response to a user triggering a change to the first interface, displaying an input area for interface information. In response to a user entering the link information of a second interface or the route identifier, branch identifier, and method name of a second interface in the interface information input area, the first interface is replaced with the second interface, and the information of the first interface is displayed in the parsing result, wherein the first element includes the first interface and the second element includes the second interface; and / or in response to a user triggering a change to the first reference image, one or more candidate images are displayed, or an image upload entry is displayed, in response to a user selecting a second reference image from one or more candidate images, or in response to a user uploading a second reference image through the image upload entry, the first reference image is replaced with the second reference image, and the second reference image is displayed in the parsing result, wherein the first element includes the first reference image and the second element includes the second reference image; and / or in response to a user triggering a change to the first code template, information of one or more candidate templates is displayed, in response to a user selecting a second code template from one or more candidate templates, the first code template is replaced with the second code template, and the information of the second code template is displayed in the parsing result, wherein the first element includes the first code template and the second element includes the second code template.
[0076] For example, in a scenario where the first component is replaced with the second component, such as... Figure 4As shown, in response to the user triggering the control of the first component (triggering the replacement of the first component), a component selection interface 400 is displayed, showing multiple candidate components 401-406 from the component library. When there are many candidate components, they can be displayed on different pages, and the number of components displayed on each page can be adjusted using control 407. For each candidate component, its style, name, description, etc., can be displayed. The user can click on any candidate component as the second component to select. The component selection interface 400 can be displayed in various forms such as a window, panel, or overlay, and is not limited to the example shown.
[0077] For example, in a scenario where the first interface field is replaced with the second interface field, such as... Figure 5 As shown, in response to the user triggering the control of the first interface field (triggering a change to the first interface field), the interface selection interface 500 is displayed. The first area of the interface selection interface 500 can display information about multiple candidate interfaces from the interface configuration information, such as candidate interface information 501 and 502. The current interface, i.e., the first candidate interface selected by the user (by default, the interface corresponding to the first interface field), can be displayed as selected, for example, using a selection box or highlighting effect. The second area of the interface selection interface 500 displays the parameter configuration information (output parameters and input parameters) of the current interface, including multiple interface fields. The user can click any interface field as the second interface field to select. The interface selection interface 500 can be displayed in various forms such as a window, panel, or overlay, and is not limited to the example shown.
[0078] For example, in a scenario where the first interface is changed to the second interface, in response to the user triggering the control for the first interface (triggering the change of the first interface), an interface selection interface 500 can be displayed, where the user can select the second interface in the first area of the interface selection interface 500. Or, as... Figure 6As shown, in response to the user triggering the control of the first interface (triggering the change of the first interface), the interface addition interface 600 is displayed. The interface addition interface 600 may include input areas for one or more interface information. For example, the input areas for multiple interface information include a link information input area 601, a route identifier input area 602, a branch identifier input area 603, and a method name input area 604. For example, the link information input area 601 can be used to input address information such as the link to the interface management platform or interface library, which can be used to store and manage relevant information for each interface; the route identifier input area 602 can be used to input route identifiers such as PSM (Project Service Module); the branch identifier input area 603 can be used to input the identifiers of branches such as environment branches and version branches; and the method name input area 604 can be used to input the method name of the interface. The second interface can be uniquely located by inputting the link information of the second interface or by inputting the route identifier, branch identifier, and method name of the second interface.
[0079] For example, in a scenario where the first reference image is replaced by the second reference image, such as... Figure 7 As shown, in response to a user triggering a first reference image (triggering a change of the first reference image), an image selection interface 700 is displayed. The first area of the image selection interface 700 displays the currently selected candidate image 701, and other candidate images, such as candidate image 702, can also be displayed in the second area of the image selection interface 700. For example, the user can switch the currently selected candidate image by triggering switching controls 703 and 704, or by dragging the switching slider 705, and is not limited to the examples given. An image upload entry can also be displayed in the image selection interface. In response to a user triggering the image upload entry, one or more images in the target folder are displayed, and the user can select a second reference image from these one or more images.
[0080] For example, in a scenario where the first code template is replaced with the second code template, in response to the user triggering the control for the first code template (triggering the replacement of the first code template), a template selection interface 800 is displayed. The template selection interface 800 displays information 801 and 802 of multiple candidate templates from the template library. For example, the information for each candidate template includes its name, image, and functional description. The template selection interface 800 may also display a search area 803. In response to the user entering the identifier of the second code template in the search area 803, the search for the second code template is initiated, and if the second code template is found, its information is displayed.
[0081] like Figure 7As shown, the component selection interface, interface selection interface, template selection interface, and image selection interface can be multiple tabs on the same interface, which can be accessed through these tabs. Figure 7 In the interface shown, you can select different tabs to choose from the component selection interface, interface selection interface, template selection interface, image selection interface, etc. Figures 4-8 Each interface can display multiple tabs corresponding to the component selection interface, interface selection interface, template selection interface, and image selection interface, making it convenient for users to adjust different elements. This will not be elaborated further here.
[0082] The method described in the above embodiments makes it convenient for users to replace the first element with the second element, improving the efficiency and accuracy of editing the parsing results, thereby enhancing the efficiency and accuracy of development.
[0083] In some embodiments, in response to a user's editing operation on the parsing result in the editing area, displaying the edited parsing result includes: in response to a user's operation of adding a third element in a technical element, displaying the parsing result after adding the information of the third element as the edited parsing result, wherein the third element includes at least one of a third component, a third interface field, a third interface, a third reference image, and a third code template; and / or in response to a user's operation of deleting a fourth element in a technical element, displaying the parsing result after deleting the information of the fourth element as the edited parsing result, wherein the fourth element includes at least one of a fourth component, a fourth interface field, a fourth interface, a fourth reference image, and a fourth code template.
[0084] Editing operations on the parsed results include at least one of adding a third element or deleting a fourth element. Users can directly enter information about the third element or delete information about the fourth element in the editing area, or they can trigger interfaces such as component selection, interface selection, template selection, and image selection to select and add a third element through specified operations. The specific operation method can be configured according to requirements.
[0085] Based on the method described in the above embodiments, users can more conveniently and quickly add or delete technical elements without having to describe the elements to be added or deleted in a dialogue manner, thus improving operational efficiency and accuracy, and improving the efficiency and accuracy of subsequent target page generation.
[0086] In some embodiments, in response to a user's operation of adding a third element to a technical element, displaying the parsing result after adding the third element's information as the edited parsing result includes: in response to a user's trigger operation of adding a component to a first target module in the technical element, displaying one or more candidate components in a component library; in response to a user selecting a third component among one or more candidate components, displaying the parsing result after adding the third component's information as the edited parsing result, wherein the third element includes the third component; and / or in response to a user's trigger operation of adding an interface field to a target component in the technical element, displaying information about one or more candidate interfaces; in response to a user selecting a second candidate interface among one or more candidate interfaces, displaying the interface field corresponding to the second candidate interface; in response to a user selecting a third interface field among the interface fields corresponding to the second candidate interface, displaying the parsing result after adding the third interface field's information as the edited parsing result, wherein the third element includes the third interface field; and / or in response to a user's trigger operation of adding an interface to a technical element, displaying the input of the interface information. In response to a user entering link information for a third interface or its route identifier, branch identifier, and method name in the interface information input area, the parsing result after adding the third interface information is displayed as the edited parsing result, where the third element includes the third interface; and / or in response to a user's triggering operation of adding a reference image to a target page or one or more second target modules, one or more candidate images are displayed, or an image upload entry is displayed. In response to a user selecting a third reference image from one or more candidate images, or in response to a user uploading a third reference image through the image upload entry, the parsing result after adding the third reference image is displayed as the edited parsing result, where the third element includes the third reference image; and / or in response to a user's triggering operation of adding a code template in a technical element, information on one or more candidate templates is displayed. In response to a user selecting a third code template from one or more candidate templates, the parsing result after adding the third code template is displayed as the edited parsing result, where the third element includes the third code template.
[0087] For example, in a scenario where a third component is added, the component selection interface 400 is displayed in response to the user entering a specified symbol (e.g., @) within the display area of the information in the first target module. The user can then select the third component from the component selection interface 400. The user can also trigger the display of the component selection interface 400 in other ways, not limited to the examples given.
[0088] For example, in a scenario where a third interface field is added, the interface selection interface 500 is displayed in response to the user entering a specified symbol (e.g., @) in the display area of the target component's information. The user can then select the third interface field in the interface selection interface 500. The user can also trigger the display of the interface selection interface 500 in other ways, not limited to the examples given.
[0089] For example, in a scenario where a third interface is added, in response to the user entering a specified symbol (e.g., @) in the display area of the relevant interface information, interface selection interface 500 is displayed. The user can select the third interface in interface selection interface 500. Alternatively, in response to the user entering a specified symbol (e.g., @) in the display area of the relevant interface information, interface addition interface 600 is displayed, where the user can add the route identifier, branch identifier, and method name of the third interface. The user can also trigger the display of interface selection interface 500 and interface addition interface 600 in other ways, not limited to the examples given.
[0090] For example, in a scenario where a third reference image is added, in response to the user entering a specified symbol (e.g., @) within the display area of the global configuration information on the target page or within the display area of the information in the second target module, an image selection interface 700 is displayed. The user can select or upload a third reference image in the image selection interface 700. The user can also trigger the display of the image selection interface 700 in other ways, not limited to the examples given.
[0091] For example, in the scenario of adding a third code template, in response to the user entering a specified symbol (e.g., @) in the code template display area, the code template selection interface 800 is displayed, where the user can select a third code template or upload a third code template.
[0092] The method described above facilitates users in adding third elements, improves the efficiency and accuracy of editing parsing results, and thus enhances development efficiency and accuracy.
[0093] During the process of parsing product requirements documents using the model, it is also possible to determine whether there are any missing technical elements and to alert the user.
[0094] In some embodiments, displaying the structured parsing results of a product requirement document includes: in response to not finding an interface in the interface configuration information that matches the first functional description information in the product requirement document, displaying first indication information for the missing interface matching the first functional description information in the structured parsing results, wherein the product requirement document includes multiple functional description information entries, and the multiple functional description information entries include the first functional description information; and / or in response to not finding a component in the component library that matches the second functional description information, displaying second indication information for the missing component matching the second functional description information in the structured parsing results, wherein the multiple functional description information entries include the second functional description information; and / or in response to not finding an interface field in the interface configuration information that matches the third functional description information, displaying third indication information for the missing interface field corresponding to the third functional description information in the structured parsing results, wherein the multiple functional description information entries include the third functional description information.
[0095] By matching the functional descriptions in the product requirements document, the backend technical solutions (interface configuration information), and the component library, it can be determined whether there are any missing interfaces, missing components, or missing interface fields, and the user can be prompted to make corrections.
[0096] like Figure 2 As shown, in the event that a certain interface is missing, a first instruction message 221 can be displayed for that interface. This first instruction message 221 can be displayed as a control. In response to the user triggering the first instruction message 221, an interface addition interface 600 is displayed. The user can add an interface through the interface addition interface 600. Of course, the user can also create new interfaces, which will not be elaborated here.
[0097] If a component is missing, a second instruction can be displayed for that component. This second instruction can be displayed as a control. In response to the user triggering the second instruction, a component selection interface 400 is displayed. The user can add components through the component selection interface 400. Of course, the user can also create new components, which will not be elaborated here.
[0098] If a certain interface field is missing, a third instruction can be displayed for that interface field. This third instruction can be displayed as a control. In response to the user triggering the third instruction, the interface selection interface 500 is displayed. The user can add interface fields through the interface selection interface 500. Of course, the user can also create new interfaces and interface fields, which will not be elaborated here.
[0099] like Figure 2As shown, if a certain interface, component, or interface field is missing, indicator marks 223 and 224 can be displayed on the page and module corresponding to the missing technical element in the directory area, so that users can quickly locate the location of the missing technical element, and can quickly locate the module where the missing technical element is located through the module options in the directory.
[0100] The method described in the above embodiments automatically identifies missing technical elements and prompts the user, which can help the user check for problems in the generated target page, assist the user in adding missing technical elements, and improve the efficiency and accuracy of generating the target page.
[0101] The following describes how to generate the target page based on the edited parsing results.
[0102] In some embodiments, generating a target page based on the edited parsing result includes: generating and displaying the code for the target page based on the edited parsing result; and generating and displaying the target page based on the code for the target page.
[0103] The model can generate the code for the target page based on the edited parsing results. This code can be displayed in the editing area, and the generated target page can be previewed there. The editing area can include multiple sub-areas, which can correspond to multiple tabs, but is not limited to the example given. These sub-areas can be used to display the parsing results, code, and the generated target page, respectively.
[0104] The method described in the above embodiments automatically generates the code for the target page based on the edited parsing results, and then generates the target page based on the code. Users can adjust the displayed code in the editing area, preview the target page, and try out its features. This improves development efficiency and enhances user convenience. Users can participate in the target page generation process, adjust the parsing results and code at any time to improve the accuracy of the generated target page, without needing to perform too many complex operations, thus improving overall development efficiency.
[0105] In some embodiments, generating a target page based on the edited parsing result includes: determining whether to store the parsing result of the previous version corresponding to the target page, wherein the edited parsing result is used as the parsing result of the current version, and the parsing result of each version is stored after the code for generating the target page is generated based on the parsing result of each version; in response to the stored parsing result of the previous version corresponding to the target page, using a model to compare the parsing result of the previous version with the parsing result of the current version, and determining a modification scheme for the code corresponding to the parsing result of the previous version; and generating the target page based on the modification scheme and the code corresponding to the parsing result of the previous version.
[0106] The system can store the corresponding parsing results and generate a version number for each generated target page code. Users may modify the parsing results or product requirement documents multiple times for the same page, resulting in multiple versions of the parsing results. By comparing the parsing results of the previous version of the target page with the current version, the system can determine the code modification plan corresponding to the previous version's parsing results. Modifications can then be made directly to the code corresponding to the previous version's parsing results to generate the target page.
[0107] The method described in the above embodiments can improve code generation efficiency and target page generation efficiency for pages that are updated and iterated multiple times.
[0108] In some embodiments, the page generation method further includes: displaying the modification scheme and the code file corresponding to the modification scheme in the session information display area of the interactive interface; and / or, in response to the user triggering the code tracing function, displaying the modified code according to the modification scheme in the code corresponding to the parsing result of the previous version, wherein the modified code is displayed with a preset effect.
[0109] For example, such as Figure 2 As shown, development control 222 can be displayed in editing area 203. In response to user triggering of development control 222, the following can be displayed: Figure 9A The interface shown. (As shown) Figure 9A As shown, the session information display area 202 displays the modification plan and its corresponding code file 901. Users can quickly locate and view the modified code file by referring to the code file corresponding to the modification plan. Figure 9A As shown, the generated target page 902 can be previewed in the editing area 203. Users can operate on the target page 902 to see if the various functions on the target page 902 meet their needs.
[0110] like Figure 9AAs shown, the editing area includes multiple sub-areas, each corresponding to different tabs and tags. For example, the first sub-area displays the generated code, with the corresponding tag 903. The generated code is displayed when the user triggers the code tag 903. The second sub-area previews the generated target page, with the corresponding tag 904. The target page is displayed when the user triggers the preview tag 903. The third sub-area tracks modified code in real-time, with the corresponding tag 905. When the user triggers the real-time tracking tag 905, the modified code from the previous version's parsing results is displayed, showing a preset effect. For example, modified and unmodified code are displayed in different colors. The code modification process can be dynamically displayed in the third sub-area. The fourth sub-area displays the parsing results, with the corresponding tag 906. The parsing results are displayed when the user triggers the requirements analysis tag 906.
[0111] The method described in the above embodiments displays the modification plan and its corresponding code file in the session information display area, making it convenient for users to view the modification plan and locate the corresponding code file. If users have questions about the modification plan or believe that the modification plan needs adjustment, they can enter questions or adjustment information in the input area. If users want to view the code file corresponding to the modification plan, they can directly open the code file for viewing, improving user convenience and efficiency, increasing the efficiency and accuracy of code generation, and thus improving development efficiency and accuracy. Based on the real-time tracking function, the modified code according to the modification plan is displayed in the code corresponding to the parsing results of the previous version, allowing users to more clearly and accurately locate the modified code, improving the user experience.
[0112] In some embodiments, in response to generating the code for the target page, the version number of the edited parsing result is determined and stored; the version number of the target page code is determined and stored; the product requirement document is updated based on the edited parsing result; the version number of the updated product requirement document is determined and stored; and the storage locations of the edited parsing result, the target page code, and the updated product requirement document are displayed.
[0113] It can automatically update and save the parsing results, code, and product requirement documents, and display the storage location of the edited parsing results, the code of the target page, and the updated product requirement documents, making it convenient for users to view and improving operational efficiency and convenience.
[0114] Users can modify the parsing results in the editing area, and can also modify the parsing results and regenerate the target page through a dialog box.
[0115] In some embodiments, the interactive interface includes an input area, a session information display area, and an editing area. The page generation method further includes: in response to a user inputting an adjustment instruction in the input area, displaying the parsing result adjusted based on the adjustment instruction in the editing area; and in response to a user triggering the target page generation function, regenerating the target page based on the adjusted parsing result.
[0116] For example, adjustment instructions include functional description information. This functional description information may include at least one of the following: functional logic and interaction method. Adjustment instructions are described using natural language.
[0117] For example, the model can be used to perform semantic understanding of adjustment instructions, determine the elements to be adjusted corresponding to the adjustment instructions, and update the parsing results based on the elements to be adjusted. For example, the elements to be adjusted may include at least one of the following: the component to be adjusted, the interface field to be adjusted, the interface to be adjusted, the reference image to be adjusted, and the code template to be adjusted.
[0118] like Figure 9B As shown, the interactive interface may include an input area 201, a session information display area 202, an editing area 203, and a result preview area 907. Relative to... Figure 9A and Figure 2 , Figure 9B The editing area for displaying the parsed results will be a separate area, allowing you to display the code or the generated target page, as well as the parsed results, simultaneously. For example... Figure 9B As shown, the result preview area 907 includes multiple sub-areas, such as the first sub-area corresponding to the code tag 903, the second sub-area corresponding to the preview tag 904, and the third sub-area corresponding to the real-time tracking tag 905. (See reference...) Figure 9A The description is omitted.
[0119] like Figure 9B As shown, the user can enter an adjustment command in the input area 201 and click the send control 909. The adjustment command 908 is displayed as a message in the session information display area 202. The session information display area 202 can also display the parsing process (thought process) based on the adjustment command 908. A model can be used to recognize the intent of the adjustment command, confirming that the user's input is an adjustment command, and identifying the elements to be adjusted. The editing area 203 can display updated parsing results based on the adjustment command 908, and the result preview area 907 can display updated target pages or code based on the adjustment command 908.
[0120] It can also update the PRD document according to the adjustment command, and can display the address information of the updated PRD document. Users can trigger the address information to view the updated document.
[0121] Users can update the generated target page in several ways. For example, a user can directly modify the PRD (Programming Document Request). In response to the input of the modified PRD, the model analyzes the differences between the modified PRD and the previous version, updates the parsing results based on these differences, displays the updated parsing results, and, in response to the user triggering the target page generation function, generates the target page based on the updated parsing results. Alternatively, the parsing results can be saved. A user can directly modify the saved parsing results. In response to the input of the modified parsing results, the model analyzes the differences between the modified parsing results and the previous version, updates the parsing results based on these differences, displays the updated parsing results, and, in response to the user triggering the target page generation function, generates the target page based on the updated parsing results.
[0122] For example, a user can update the relevant information of an interface in the interface management platform (interface library). In response to the update of the relevant information of the interface in the interface management platform (interface library), the model analyzes whether to update the parsing result. In response to the determination to update the parsing result, the updated parsing result is displayed. In response to the user triggering the target page generation function, the target page is generated based on the updated parsing result.
[0123] For example, when a user updates the PRD version, in response to inputting the new version of the PRD, the model analyzes the differences between the new version of the PRD and the previous version of the PRD, updates the analysis results based on the differences, displays the updated analysis results, and in response to the user triggering the target page generation function, generates the target page based on the updated analysis results.
[0124] For example, users can edit the parsing results through the editing area, as detailed in the aforementioned embodiments, which will not be repeated here. For example, users can update the parsing results and the target page by inputting adjustment commands, as detailed in the aforementioned embodiments, which will not be repeated here.
[0125] Based on the method disclosed herein, users can update the parsing results and target pages in various ways, which facilitates user operations, meets different user needs, improves the efficiency and accuracy of page updates, and enhances user experience.
[0126] The following is combined Figure 10 and 11 Describe the overall process of page generation.
[0127] Figure 10 Flowcharts for some other embodiments of the page generation method disclosed herein. For example... Figure 10As shown, the page generation method in this embodiment includes steps S1001 to S1007. The page generation device may include two parts: a chatbot and a PRD agent. The chatbot is mainly used to handle dialogue with the user, and the PRD agent is used to implement the process related to generating pages using the PRD.
[0128] In step S1001, the chatbot receives information input by the user.
[0129] In step S1002, the chatbot performs intent recognition on the user's input information. If the intent is to generate a page based on the PRD and obtain the user's PRD, then step S1005 is executed.
[0130] In step 1003, the user's trigger operation on the target function trigger control (the button on the PRD generation page) is received.
[0131] In step 1004, the PRD-related information entered by the user on the document upload interface is received, and the PRD is obtained.
[0132] In step 1005, the chatbot is switched to the PRD agent.
[0133] In step 1006, the PRD agent performs preliminary parsing of the PRD (parsing of basic information).
[0134] For example, determine whether the PRD conforms to the preset PRD template, determine the multiple pages included in the PRD, determine the content corresponding to each page, determine the requirement scenario (application scenario), and determine the relationship between reference images and text, etc.
[0135] In step 1007, the chatbot displays options corresponding to basic information so that the user can confirm the target page, target application scenario, and target processing method for one or more reference images.
[0136] It can also display one or more reference images in the PRD for user confirmation. If the PRD matches the preset PRD template, confirmation is not required.
[0137] Figure 11 Flowcharts for further embodiments of the page generation method disclosed herein. For example... Figure 11 As shown, the page generation method of this embodiment includes steps S1008 to S1027. Steps S1008 to S1026 can be executed after step S1007.
[0138] In step S1008, the PRD agent generates a structured parsed structure.
[0139] Furthermore, step S1008 includes steps S1020 to S1023.
[0140] In step S1020, the PRD agent acquires scenario-related knowledge. Scenario-related knowledge includes material knowledge, template knowledge, business background, default conventions, and parsing result templates.
[0141] Material knowledge includes component libraries, template knowledge includes code template libraries, and parsing result templates can serve as examples of parsing results to make the generated parsing results more compliant with requirements in terms of format and content.
[0142] In step S1021, the PRD agent analyzes the content associated with the target page in the PRD.
[0143] In step S1022, the PRD agent performs association analysis based on scene knowledge and the content associated with the target page in the PRD.
[0144] In step S1022, the functional description information of components on the target page can be associated and matched with components in the component library for material retrieval; the content associated with the target page can be associated and matched with templates in the code template library for template retrieval; the backend technical solution (interface configuration information) can be analyzed, and the functional description information of the interface can be associated and matched with the interface in the backend technical solution; the target processing method based on one or more reference images can be analyzed for one or more reference images; missing technical elements and erroneous content can be analyzed, etc. Step 1002 can complete the retrieval of relevant information of the interface in the interface management platform (or interface library).
[0145] In step S1023, the PRD agent generates a structured parsing result based on the recall result of the interface management platform.
[0146] In step S1009, the structured parsing results are displayed in the editing area.
[0147] In step S1010, the PRD agent receives the user's modification operation (edit operation) on the parsing result in the editing area.
[0148] In step S1011, the PRD agent asks a question based on the parsing results of the PRD.
[0149] For example, if there are uncertain, unclear, or incorrect contents during the parsing process, questions can be asked to the user.
[0150] In step S1012, the PRD agent receives feedback information from the user regarding the question.
[0151] In step S1013, the PRD agent modifies the parsing result based on the feedback information.
[0152] In step S1014, the modified parsing result is displayed.
[0153] In step S1015, the PRD agent generates a code generation task based on the modified parsing results.
[0154] Step S1015 includes steps S1024 to S1027.
[0155] In step S1024, the difference information is determined based on the parsing results of the previous version and the parsing results of the current version.
[0156] In step S1025, it is determined whether there is a conflict between the parsing result of the previous version and the parsing result of the current version. If so, step S1026 is executed; otherwise, step S1027 is executed.
[0157] In step S1026, the user's decision information regarding the conflict is received.
[0158] In step S1027, the task of generating the current version of the code is determined based on the difference information and the code of the previous version.
[0159] In step S1016, the PRD agent is switched to the code generation agent.
[0160] In step S1017, the code-generating agent generates the code for the target page.
[0161] In step S1018, the target page is generated based on the code of the target page.
[0162] In step S1019, the target page for preview is displayed.
[0163] The method described in the above embodiments describes the overall process of generating a target page based on a PRD. The entire process does not require much user intervention, which facilitates the modification of the parsing results and improves the overall development efficiency and accuracy of the target page.
[0164] This disclosure also provides a page generation apparatus, which is described below in conjunction with... Figure 12 Describe it.
[0165] Figure 12 Structural diagrams of some embodiments of the page generation apparatus disclosed herein. For example... Figure 12 As shown, the device 120 in this embodiment includes: a first display module 1210, a second display module 1220, and a generation module 1230.
[0166] The first display module 1210 is configured to respond to user input of a product requirement document, parse the product requirement document using a model, and display the structured parsing results of the product requirement document in the editing area of the interactive interface. The parsing results include information on technical elements used to generate the target page. The information on technical elements includes information on one or more modules and information on one or more interfaces. The information on each module includes information on the components associated with each module.
[0167] The second display module 1220 is configured to display the edited parsing result in response to the user's editing operation on the parsing result in the editing area.
[0168] The generation module 1230 is configured to generate the target page in response to a user triggering the target page generation function, based on the edited parsing results.
[0169] The page generation device of the above embodiments allows users to directly input product requirement documents, parse the product requirement documents using a model, and display the structured parsing results of the product requirement documents in the editing area of the interactive interface. Furthermore, users can directly edit the parsing results in the editing area, displaying the edited parsing results. Then, in response to the user triggering the target page generation function, the target page is generated based on the edited parsing results. Based on the page generation method of the above embodiments, users can directly input product requirement documents without needing to input requirement information through dialogue. An intermediate parsing result is generated for the product requirement document. This parsing result includes information on the technical elements used to generate the target page, and is structured information, making it more readable and easier for users to quickly locate the technical elements in the parsing result. The parsing results displayed in the editing area can be flexibly and quickly edited by the user. Users can edit key technical elements such as modules, interfaces, and components without needing to input editing commands through dialogue, improving the flexibility, efficiency, and accuracy of user requirement modification. Furthermore, the target page can be easily and quickly generated based on the edited parsing results, improving the efficiency and accuracy of target page generation. The entire device is designed to assist users in developing target pages, thereby improving the efficiency and accuracy of target page development.
[0170] In some embodiments, the information of the technical elements may also include at least one of the following: global configuration information of the target page, reference image of the target page, reference image of one or more modules, and information of one or more code templates. The information of the components associated with each module includes the identifier and interface field of the components associated with each module.
[0171] In some embodiments, the second display module 1220 is configured to, in response to a user's operation of replacing the first element in the technical elements with the second element, replace the first element with the second element and display the information of the second element in the edited parsing result, wherein the first element and the second element are of the same category, the first element includes at least one of a first component, a first interface field, a first interface, a first reference image, and a first code template, and the second element includes at least one of a second component, a second interface field, a second interface, a second reference image, and a second code template.
[0172] In some embodiments, the second display module 1220 is configured to, in response to a user triggering a replacement of the first component, display information of one or more candidate components in a component library; in response to a user selecting a second component from one or more candidate components, replace the first component with the second component and display information of the second component in the parsing result, wherein the first element includes the first component and the second element includes the second component; and / or, in response to a user triggering a replacement of the first interface field, display information of one or more candidate interfaces; in response to a user selecting a first candidate interface from one or more candidate interfaces, display information of the interface field corresponding to the first candidate interface; in response to a user selecting a second interface field from the interface field corresponding to the first candidate interface, replace the first interface field with the second interface field and display information of the second interface field in the parsing result, wherein the first element includes the first interface field and the second element includes the second interface field; and / or, in response to a user triggering a replacement of the first interface, display an input area for interface information; and in response to a user inputting information of the second interface in the input area for interface information, display the interface information input area. The system can: link information or input the routing identifier, branch identifier, and method name of the second interface; replace the first interface with the second interface and display the information of the first interface in the parsing result; wherein the first element includes the first interface and the second element includes the second interface; and / or, in response to the user triggering the replacement of the first reference image, display one or more candidate images, or display an image upload entry; in response to the user selecting a second reference image from one or more candidate images, or in response to the user uploading a second reference image through the image upload entry, replace the first reference image with the second reference image and display the second reference image in the parsing result; wherein the first element includes the first reference image and the second element includes the second reference image; and / or, in response to the user triggering the replacement of the first code template, display information of one or more candidate templates; in response to the user selecting a second code template from one or more candidate templates, replace the first code template with the second code template and display the information of the second code template in the parsing result; wherein the first element includes the first code template and the second element includes the second code template.
[0173] In some embodiments, the second display module 1220 is configured to, in response to a user's operation of adding a third element to a technical element, display the parsing result after adding the information of the third element as the edited parsing result, wherein the third element includes at least one of a third component, a third interface field, a third interface, a third reference image, and a third code template; and / or, in response to a user's operation of deleting a fourth element to a technical element, display the parsing result after deleting the information of the fourth element as the edited parsing result, wherein the fourth element includes at least one of a fourth component, a fourth interface field, a fourth interface, a fourth reference image, and a fourth code template.
[0174] In some embodiments, the second display module 1220 is configured to, in response to a user's trigger operation of adding a component to the first target module in the technical element, display one or more candidate components in the component library; in response to a user selecting a third component among one or more candidate components, display the parsing result after adding the information of the third component as the edited parsing result, wherein the third element includes the third component; and / or, in response to a user's trigger operation of adding an interface field to the target component in the technical element, display information of one or more candidate interfaces; in response to a user selecting a second candidate interface among one or more candidate interfaces, display the interface field corresponding to the second candidate interface; in response to a user selecting a third interface field among the interface fields corresponding to the second candidate interface, display the parsing result after adding the information of the third interface field as the edited parsing result, wherein the third element includes the third interface field; and / or, in response to a user's trigger operation of adding an interface in the technical element, display an input area for interface information; and in response to a user inputting information in the input area for interface information... The link information of the third interface, or the route identifier, branch identifier, and method name of the third interface are entered. The parsing result after adding the information of the third interface is displayed as the edited parsing result. The third element includes the third interface. And / or in response to the user's trigger operation of adding a reference image to the target page or one or more second target modules, one or more candidate images are displayed, or an image upload entry is displayed. In response to the user selecting a third reference image from one or more candidate images, or in response to the user uploading a third reference image through the image upload entry, the parsing result after adding the third reference image is displayed as the edited parsing result. The third element includes the third reference image. And / or in response to the user's trigger operation of adding a code template in the technical element, information of one or more candidate templates is displayed. In response to the user selecting a third code template from one or more candidate templates, the parsing result after adding the third code template is displayed as the edited parsing result. The third element includes the third code template.
[0175] In some embodiments, the first display module 1210 is configured to display an interactive interface, wherein the interactive interface includes an input area, a session information display area, and an editing area; in response to a user inputting a product requirement document through the input area, the product requirement document is parsed using a model; process information of parsing the product requirement document is displayed in the session information display area; and structured parsing results of the product requirement document are displayed in the editing area.
[0176] In some embodiments, the first display module 1210 is configured to parse basic information of a product requirement document using a model, wherein the basic information includes at least one of one or more pages, one or more application scenarios, and one or more reference images corresponding to the product requirement document; display options corresponding to the basic information in a session information display area, wherein the options corresponding to the basic information include at least one of options for one or more pages, one or more application scenarios, and one or more processing methods for reference images; and display a confirmation status of at least one of the target page, target application scenario, and target processing method for one or more reference images based on the options corresponding to the basic information.
[0177] In some embodiments, the first display module 1210 is configured to, in response to the absence of an interface matching the first functional description information in the interface configuration information, display first indication information of the missing interface matching the first functional description information in the structured parsing result, wherein the product requirement document includes multiple functional description information, the multiple functional description information including the first functional description information; and / or, in response to the absence of a component matching the second functional description information in the component library, display second indication information of the missing component matching the second functional description information in the structured parsing result, wherein the multiple functional description information includes the second functional description information; and / or, in response to the absence of an interface field matching the third functional description information in the interface configuration information, display third indication information of the missing interface field corresponding to the third functional description information in the structured parsing result, wherein the multiple functional description information includes the third functional description information.
[0178] In some embodiments, the generation module 1230 is configured to determine whether to store the parsing result of the previous version corresponding to the target page, wherein the edited parsing result is used as the parsing result of the current version, and the parsing result of each version is stored after the code of the target page is generated based on the parsing result of each version; in response to the stored parsing result of the previous version corresponding to the target page, the model is used to compare the parsing result of the previous version with the parsing result of the current version to determine the modification scheme for the code corresponding to the parsing result of the previous version; and the target page is generated according to the modification scheme and the code corresponding to the parsing result of the previous version.
[0179] In some embodiments, the page generation apparatus further includes a third display module 1240 configured to display the modification scheme and the code file corresponding to the modification scheme in the session information display area of the interactive interface; and / or, in response to the user triggering the code tracing function, to display the modified code according to the modification scheme in the code corresponding to the parsing result of the previous version, wherein the modified code is displayed with a preset effect.
[0180] In some embodiments, the generation module 1230 is configured to generate the code of the target page based on the edited parsing result; and to generate the target page based on the code of the target page. The page generation apparatus further includes a fourth display module 1250 configured to display the code of the target page in response to the generation of the target page code, and to display the target page in response to the generation of the target page.
[0181] This disclosure also provides an electronic device, which is described below in conjunction with... Figure 13 and 14 Describe it. Figure 13 A block diagram of an electronic device according to some embodiments of the present disclosure is shown.
[0182] like Figure 13 As shown, the electronic device 13 includes a processor 132; and a memory 131 coupled to the processor 132 for storing instructions, which, when executed by the processor 132, cause the processor 132 to perform a page generation method as described in any embodiment of this disclosure.
[0183] In the electronic device described in the above embodiments, users can directly input product requirement documents, parse the product requirement documents using a model, and display the structured parsing results of the product requirement documents in the editing area of the interactive interface. Furthermore, users can directly edit the parsing results in the editing area, displaying the edited parsing results. Then, in response to the user triggering the target page generation function, the target page is generated based on the edited parsing results. Based on the page generation method of the above embodiments, users can directly input product requirement documents without needing to input requirement information through dialogue. An intermediate parsing result is generated for the product requirement document. This parsing result includes information on the technical elements used to generate the target page, and is structured information, making it more readable and easier for users to quickly locate the technical elements in the parsing result. The parsing results displayed in the editing area can be flexibly and quickly edited by the user. Users can edit key technical elements such as modules, interfaces, and components without needing to input editing commands through dialogue, improving the flexibility, efficiency, and accuracy of user requirement modification. Furthermore, the target page can be easily and quickly generated based on the edited parsing results, improving the efficiency and accuracy of target page generation. The electronic device assists users in developing target pages, improving the efficiency and accuracy of target page development.
[0184] Memory 131 is used to store one or more computer-readable instructions. Memory 131 may include any combination of various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory, including but not limited to random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), read-only memory (ROM), and flash memory. Memory 131 may, for example, store operating systems, application programs, bootloaders, databases, and other programs, as well as various application programs and various data.
[0185] The processor 132 is configured to execute computer-readable instructions to implement the page generation method of any of the foregoing embodiments. Specific implementations of each step of the method can be found in the above embodiments; repeated details will not be elaborated here.
[0186] Processor 132 can be configured to execute the steps of the page generation method. Processor 132 can be various processing devices, such as a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The central processing unit (CPU) can be an x86 or ARM architecture, etc.
[0187] The processor 132 and the memory 131 can communicate with each other directly or indirectly. For example, the processor 132 and the memory 131 can communicate via a network. The network can include a wireless network, a wired network, and / or any combination of wireless and wired networks. The processor 132 and the memory 131 can also communicate with each other via a system bus, which is not limited in this disclosure.
[0188] It should be noted that Figure 13 The components of the electronic device 13 shown are merely exemplary and not limiting; the electronic device 13 may have other components as needed for the actual application. The processor 132 can control other components in the electronic device 13 to perform desired functions.
[0189] Electronic device 13 can be implemented by software, firmware and / or hardware, and can be integrated into a device with relevant applications installed.
[0190] Figure 14 Block diagrams of electronic devices according to other embodiments of the present disclosure are shown.
[0191] Figure 14 The electronic device 14 shown can be a computer system with a dedicated hardware structure, which can perform corresponding functions when the relevant application is installed.
[0192] Electronic devices include, but are not limited to, mobile terminals such as smartphones, laptops, personal digital assistants (PDAs), tablet computers (PCs), PMPs (portable multimedia players), in-vehicle terminals (such as in-vehicle navigation terminals), wearable devices, and fixed terminals such as digital televisions and desktop computers.
[0193] like Figure 14 As shown, the Central Processing Unit (CPU) 141 performs various processes based on a program stored in the Read-Only Memory (ROM) 142 or a program loaded from the Storage Section 148 into the Random Access Memory (RAM) 143. The RAM 143 stores data required as needed when the CPU 141 performs various processes, etc. The CPU is merely exemplary; it could also be other types of processors, such as the various processors described above. The ROM 142, RAM 143, and Storage Section 148 can be various forms of computer-readable storage media. It should be noted that although... Figure 14The image shows ROM 142, RAM 143 and storage section 148 respectively, but one or more of them may be combined or located in the same or different memory or storage modules.
[0194] CPU 141, ROM 142 and RAM 143 are interconnected via bus 144. Input / output interface 145 is also connected to bus 144.
[0195] The following components are connected to the input / output interface 145: input section 146, such as a touchscreen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; output section 147, including displays such as cathode ray tube (CRT), liquid crystal display (LCD), speakers, vibrators, etc.; storage section 148, including hard disk, magnetic tape, etc.; and communication section 149, including network interface cards such as LAN cards, modems, etc. The communication section 149 allows communication processing to be performed via a network such as the Internet. It is easy to understand that, although... Figure 14 The portion of the electronic device 14 shown communicates via bus 144, but it may also communicate via a network or other means, wherein the network may include a wireless network, a wired network, and / or any combination of wireless and wired networks.
[0196] As needed, drive 1410 is also connected to input / output interface 145. Removable media 1411, such as disks, optical disks, magneto-optical disks, semiconductor memories, etc., are installed on drive 1410 as needed, so that computer programs read from them can be installed into storage section 148 as needed.
[0197] When the above series of processes are implemented through software, the program constituting the software can be installed from a network such as the Internet or a storage medium such as a removable medium 1311.
[0198] According to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, some embodiments of this disclosure include a computer program product that, when run on a computer, causes the computer to perform the methods of any of the foregoing embodiments. The computer program product includes computer instructions carried on a computer-readable medium, comprising program code for performing the methods shown in the flowcharts. In such embodiments, the computer instructions can be downloaded and installed from a network via communication section 149, or installed from storage section 148, or installed from ROM 142. When the computer program is executed by CPU 141, the methods of embodiments of this disclosure are performed.
[0199] This disclosure also provides a computer-readable storage medium having a computer program stored thereon that, when executed by a processor, implements the page generation method of any embodiment of this disclosure.
[0200] The computer-readable storage medium of the above embodiments allows users to directly input product requirement documents, parse the product requirement documents using a model, and display the structured parsing results of the product requirement documents in the editing area of the interactive interface. Furthermore, users can directly edit the parsing results in the editing area, displaying the edited parsing results. Then, in response to the user triggering the target page generation function, the target page is generated based on the edited parsing results. Based on the page generation method of the above embodiments, users can directly input product requirement documents without needing to input requirement information through a dialogue. An intermediate parsing result is generated for the product requirement document. This parsing result includes information on the technical elements used to generate the target page, and is structured information, making it more readable and easier for users to quickly locate the technical elements in the parsing result. The parsing results displayed in the editing area can be flexibly and quickly edited by the user. Users can edit key technical elements such as modules, interfaces, and components without needing to input editing commands through a dialogue, improving the flexibility, efficiency, and accuracy of user requirement modification. Furthermore, the target page can be easily and quickly generated based on the edited parsing results, improving the efficiency and accuracy of target page generation. Computer-readable storage media are used to assist users in developing target pages, thereby improving the efficiency and accuracy of target page development.
[0201] It should be noted that, in the context of this disclosure, a computer-readable medium can be a tangible medium that may contain or store programs for use by or in conjunction with an instruction execution system, apparatus, or device.
[0202] A computer-readable medium may be a computer-readable storage medium, a computer-readable signal medium, or any combination thereof.
[0203] Computer-readable storage media include, but are not limited to, systems, apparatuses, or devices that are electrical, magnetic, optical, electromagnetic, infrared, or semiconductor, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to, electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, a computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. Computer instructions are stored on the computer-readable storage medium that, when executed by a processor, implement the methods described in any of the foregoing embodiments.
[0204] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, capable of sending, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.
[0205] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.
[0206] In some embodiments, a computer program is also provided, comprising: instructions that, when executed by a processor, cause the processor to perform the methods described in any of the foregoing embodiments. For example, the instructions may be embodied in computer program code.
[0207] In embodiments of this disclosure, computer program code for performing the operations of this disclosure can be written in one or more programming languages or a combination thereof. These programming languages include, but are not limited to, object-oriented programming languages such as Java, Smalltalk, and C++, as well as conventional procedural programming languages such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network (including a local area network (LAN) or a wide area network (WAN)), or it can be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0208] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.
[0209] The functions described above can be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary hardware logic components that can be used include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.
[0210] While specific embodiments of this disclosure have been described in detail by way of example, those skilled in the art should understand that the examples are for illustrative purposes only and not intended to limit the scope of this disclosure. Those skilled in the art should understand that modifications can be made to the above embodiments without departing from the scope and spirit of this disclosure. The scope of this disclosure is defined by the appended claims.
Claims
1. A page generation method, comprising: In response to user input of a product requirement document, the model is used to parse the product requirement document. In the editing area of the interactive interface, the structured parsing result of the product requirement document is displayed. The parsing result includes information on technical elements used to generate the target page. The information on technical elements includes information on one or more modules and information on one or more interfaces. The information on each module includes information on the components associated with each module. In response to the user's editing operation on the parsing result in the editing area, the edited parsing result is displayed; In response to the user triggering the target page generation function, the target page is generated based on the edited parsing result.
2. The page generation method according to claim 1, wherein, The information of the technical elements also includes at least one of the following: global configuration information of the target page, reference image of the target page, reference image of the one or more modules, and information of one or more code templates. The information of the components associated with each module includes the identifier and interface field of the components associated with each module.
3. The page generation method according to claim 2, wherein, The response to the user's editing operation on the parsing result in the editing area, displaying the edited parsing result includes: In response to the user's operation of replacing the first element in the technical elements with the second element, the second element replaces the first element, and the information of the second element is displayed in the edited parsing result. The first element and the second element are of the same category. The first element includes at least one of the following: a first component, a first interface field, a first interface, a first reference image, and a first code template. The second element includes at least one of the following: a second component, a second interface field, a second interface, a second reference image, and a second code template.
4. The page generation method according to claim 3, wherein, In response to the user's operation of replacing the first element in the technical element with the second element, the second element is used to replace the first element, and the information of the second element is displayed in the edited parsing result, including: In response to the user triggering a replacement of the first component, information on one or more candidate components in the component library is displayed; in response to the user selecting the second component from the one or more candidate components, the first component is replaced with the second component, and information on the second component is displayed in the parsing result, wherein the first element includes the first component, and the second element includes the second component; and / or In response to the user triggering a change to the first interface field, information on one or more candidate interfaces is displayed. In response to the user selecting a first candidate interface from the one or more candidate interfaces, information on the interface field corresponding to the first candidate interface is displayed. In response to the user selecting a second interface field from the interface fields corresponding to the first candidate interface, the first interface field is replaced with the second interface field, and information on the second interface field is displayed in the parsing result. The first element includes the first interface field, and the second element includes the second interface field; and / or In response to the user triggering a change of the first interface, an input area for interface information is displayed. In response to the user inputting link information for the second interface or inputting the routing identifier, branch identifier, and method name of the second interface in the input area, the first interface is replaced with the second interface, and the information of the first interface is displayed in the parsing result. The first element includes the first interface, and the second element includes the second interface; and / or In response to the user triggering a replacement of the first reference image, one or more candidate images are displayed, or an image upload entry is displayed. In response to the user selecting the second reference image from the one or more candidate images, or in response to the user uploading the second reference image through the image upload entry, the first reference image is replaced with the second reference image, and the second reference image is displayed in the parsing result. The first element includes the first reference image, and the second element includes the second reference image; and / or In response to the user triggering a change to the first code template, information on one or more candidate templates is displayed. In response to the user selecting the second code template from the one or more candidate templates, the first code template is replaced with the second code template, and information on the second code template is displayed in the parsing result, wherein the first element includes the first code template, and the second element includes the second code template.
5. The page generation method according to claim 2, wherein, The response to the user's editing operation on the parsing result in the editing area, displaying the edited parsing result includes: In response to the user's operation of adding a third element to the technical element, the parsing result after adding the third element is displayed as the edited parsing result, wherein the third element includes at least one of a third component, a third interface field, a third interface, a third reference image, and a third code template; and / or In response to the user's operation of deleting the fourth element in the technical elements, the parsing result after deleting the information of the fourth element is displayed as the edited parsing result, wherein the fourth element includes at least one of the following: a fourth component, a fourth interface field, a fourth interface, a fourth reference image, and a fourth code template.
6. The page generation method according to claim 5, wherein, The step of responding to the user's operation of adding a third element to the technical element and displaying the parsing result after adding the information of the third element as the edited parsing result includes: In response to the user's triggering operation to add a component to the first target module in the technical element, one or more candidate components in the component library are displayed. In response to the user selecting the third component from the one or more candidate components, the parsing result after adding the information of the third component is displayed as the edited parsing result, wherein the third element includes the third component; and / or In response to the user's triggering operation of adding an interface field to the target component in the technical element, information on one or more candidate interfaces is displayed. In response to the user selecting a second candidate interface from the one or more candidate interfaces, the interface field corresponding to the second candidate interface is displayed. In response to the user selecting a third interface field from the interface fields corresponding to the second candidate interface, the parsing result after adding the information of the third interface field is displayed as the edited parsing result, wherein the third element includes the third interface field; and / or In response to the user's triggering operation of adding an interface to the technical element, an input area for interface information is displayed. In response to the user inputting the link information of the third interface or the route identifier, branch identifier, and method name of the third interface in the input area, the parsing result after adding the third interface information is displayed as the edited parsing result. The third element includes the third interface; and / or In response to the user's triggering operation of adding a reference image to the target page or a second target module in one or more modules, one or more candidate images are displayed, or an image upload entry is displayed. In response to the user selecting the third reference image from the one or more candidate images, or in response to the user uploading the third reference image through the image upload entry, the parsing result after adding the third reference image is displayed as the edited parsing result, wherein the third element includes the third reference image; and / or In response to the user's triggering operation of adding a code template in the technical element, information on one or more candidate templates is displayed. In response to the user selecting the third code template from the one or more candidate templates, the parsing result after adding the third code template is displayed as the edited parsing result, wherein the third element includes the third code template.
7. The page generation method according to claim 1, wherein, The step of responding to user input of a product requirement document, parsing the product requirement document using a model, and displaying the structured parsing results of the product requirement document in the editing area of the interactive interface includes: The interactive interface is displayed, wherein the interactive interface includes an input area, a session information display area, and an editing area; In response to the user inputting the product requirement document through the input area, the model is used to parse the product requirement document; The process information for parsing the product requirement document is displayed in the session information display area; The structured parsing results of the product requirements document are displayed in the editing area.
8. The page generation method according to claim 7, wherein: The process of parsing the product requirements document using the model includes: The model is used to parse the basic information of the product requirement document, wherein the basic information includes at least one of one or more pages corresponding to the product requirement document, one or more application scenarios, and one or more reference images; The process information for parsing the product requirement document displayed in the session information display area includes: The options corresponding to the basic information are displayed in the session information display area. The options corresponding to the basic information include at least one of the options of the one or more pages, the one or more application scenarios, and the processing method of the one or more reference images. In response to the user confirming at least one of the target processing methods of the target page, the target application scenario, and the one or more reference images based on the options corresponding to the basic information, the confirmation status of at least one of the target processing methods of the target page, the target application scenario, and the one or more reference images is displayed.
9. The page generation method according to any one of claims 1-8, wherein, The structured parsing results of the product requirements document include: In response to the absence of an interface matching the first functional description information in the product requirements document in the interface configuration information, a first indication message indicating the missing interface matching the first functional description information is displayed in the structured parsing results. The product requirements document includes multiple functional description messages, including the first functional description information; and / or In response to the absence of a component matching the second functional description information in the component library, a second indication of the missing component matching the second functional description information is displayed in the structured parsing result, wherein the plurality of functional description information includes the second functional description information; and / or In response to the absence of an interface field matching the third function description information in the interface configuration information, a third indication information for the missing interface field corresponding to the third function description information is displayed in the structured parsing result, wherein the multiple function description information includes the third function description information.
10. The page generation method according to any one of claims 1-8, wherein, The step of generating the target page based on the edited parsing result includes: Determine whether to store the parsing result of the previous version corresponding to the target page, wherein the edited parsing result is used as the parsing result of the current version, and the parsing result of each version is stored after the code of the target page is generated based on the parsing result of each version; In response to the stored parsing results of the previous version corresponding to the target page, the model is used to compare the parsing results of the previous version with the parsing results of the current version to determine the code modification scheme corresponding to the parsing results of the previous version; The target page is generated based on the modified scheme and the code corresponding to the parsing result of the previous version.
11. The page generation method according to claim 10, further comprising: The modification scheme and the corresponding code file are displayed in the session information display area of the interactive interface; and / or In response to the user triggering the code tracing function, the modified code according to the modification scheme is displayed in the code corresponding to the parsing result of the previous version, wherein the modified code is displayed with a preset effect.
12. The page generation method according to any one of claims 1-8, wherein, The interactive interface includes an input area, a session information display area, and the editing area; the page generation method further includes: In response to the user entering an adjustment command in the input area, the parsing result adjusted based on the adjustment command is displayed in the editing area; In response to the user triggering the target page generation function, the target page is regenerated based on the adjusted parsing results.
13. A page generation apparatus, comprising: The first display module is configured to respond to a user input of a product requirement document, parse the product requirement document using a model, and display the structured parsing result of the product requirement document in the editing area of the interactive interface. The parsing result includes information on technical elements used to generate the target page. The information on the technical elements includes information on one or more modules and information on one or more interfaces. The information on each module includes information on the components associated with each module. The second display module is configured to display the edited parsing result in response to the user's editing operation on the parsing result in the editing area; The generation module is configured to generate the target page in response to the user triggering the generation function of the target page, based on the edited parsing result.
14. An electronic device, comprising: Memory; and A processor coupled to the memory, the processor being configured to execute the page generation method of any one of claims 1 to 12 based on instructions stored in the memory.
15. A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the page generation method of any one of claims 1 to 12.