A method of generating a development assistance document, an electronic device, and a program development method

Abstract

The application relates to the technical field of data processing, and discloses a method for generating a development auxiliary document, an electronic device and a program development method. According to the application, design drawing data of different data types / input sources can be automatically parsed, and the extraction efficiency and extraction accuracy of design drawing content are improved; the first data obtained through extraction can be subjected to page structure recognition, interactive logic inference and function point decomposition, efficient and scientific extraction of page-related data is realized, and the risks of omission and understanding deviation existing in manual analysis are greatly reduced; finally, accurate and unified structured auxiliary documents can be generated by comprehensively integrating various detailed data, and the generation efficiency and accuracy of the documents are improved.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a method for generating development support documents, an electronic device, and a program development method. Background Technology

[0002] In mobile or multi-platform application development, developers typically need to implement pages and functions based on UI design mockups (such as screenshots of mockups, design drafts produced by design tools such as Figma).

[0003] The current practice is for developers to manually review the design drafts, understand the page structure, layout hierarchy, component types, interaction logic, data display, and state changes from them, and then code based on the product requirements document (if applicable). However, because there are significant differences between the design drafts and the code implementation, developers need to spend a considerable amount of time understanding the design drafts, and there is a high risk of missing or misunderstanding information in the drafts.

[0004] Another approach is for product or design personnel to provide a clear PRD (Product Requirements Document) or design specifications. However, the PRD focuses on describing business requirements and acceptance criteria, and developers still need to extract the necessary information for implementation from the design drawings (such as which parts are lists, which are clickable, where the data comes from, and what boundary states exist). For developers, translating the design drawings into code presents significant development challenges. While design tools (such as Figma) can provide design data and collaboration capabilities, the information regarding page structures and layout hierarchies in the UI design drawings still relies on the developers' understanding of the drawings, which can easily lead to information omissions or misunderstandings.

[0005] It is evident that providing a corresponding solution is crucial to address the issues of time-consuming understanding of design information and the susceptibility to errors and omissions in information comprehension during the code implementation process based on UI design drawings in existing technologies. Summary of the Invention

[0006] This invention provides a method for generating development auxiliary documents, an electronic device, and a program development method, which can realize the process-oriented and standardized decomposition of design drawing information, and improve the efficiency and accuracy of design drawing information parsing.

[0007] The first aspect of this invention discloses a method for generating development support documentation, the method comprising: Determine the data type corresponding to the design drawing data, and parse the design drawing data according to the data parsing method matching the data type to obtain the first data; the data type includes image type or link type; Perform page type identification, region decomposition, component identification and hierarchy determination operations on the first data respectively to obtain the page structure analysis results for the first data; The interaction logic inference operation and function point decomposition operation are performed on the page structure analysis results respectively to obtain the interaction logic inference result and function point decomposition result based on the page structure analysis results; Determine first document construction information and second document construction information corresponding to the first data and the page structure analysis results. The first document construction information includes at least one of the following: data model, data source, update conditions, page state, and component state. The second document construction information includes anomaly identification information and document boundary information. According to the preset document template, the page structure analysis results, the interaction logic inference results, the function point decomposition results, the first document construction information, and the second document construction information are respectively subjected to format conversion operation, integrity check operation, coherence check operation, and information filling operation to obtain a structured auxiliary document for the first data.

[0008] As an optional implementation, in the first aspect of the present invention, the step of parsing the design drawing data according to a data parsing method matching the data type to obtain the first data includes: When the data type is the image type, an image parsing operation is performed on the image to be processed included in the design drawing data to obtain UI element information for the design drawing data, which is used as the first data; When the data type is the link type, the links to be identified included in the design data are parsed to obtain the parsing result for the design data. Furthermore, based on the interfaces included in the design data, target link data matching the parsing result is obtained as the first data. The parsing result includes a file identifier and an optional node identifier. The target link data includes the page hierarchy structure, page layout attributes, and page text content corresponding to the parsing result.

[0009] As an optional implementation, in the first aspect of the present invention, the step of performing page type identification, region decomposition, component identification, and hierarchy determination operations on the first data to obtain page structure analysis results for the first data includes: Perform a page type identification operation on the first data to obtain a page type identification result for the first data. The page type identification result is used to indicate at least the page type of the page corresponding to the first data. Perform a region decomposition operation on the first data to obtain a region decomposition result for the first data. The region decomposition result is used to decompose the first data into multiple predefined functional regions. Perform a component identification operation on the region disassembly results to obtain component identification results for the region disassembly results. The component identification operation is used to identify the component category corresponding to each UI component included in each functional region and the component features corresponding to each UI component. Based on the component identification results, perform position identification operations and / or hierarchy relationship determination operations on each UI component to obtain position identification results and / or hierarchy relationships for each UI component; The page type identification result, the region breakdown result, the component identification result, the position identification result for each UI component, and / or the hierarchical relationship are determined as the page structure analysis result for the first data.

[0010] As an optional implementation, in the first aspect of the present invention, the step of performing interaction logic inference operations and function point decomposition operations on the page structure analysis results to obtain interaction logic inference results and function point decomposition results for the page structure analysis results includes: For each UI component, based on the component category and component characteristics corresponding to the UI component, at least one interactive logic and its corresponding annotation information that are adapted to the UI component are determined as the interactive logic inference result. The annotation information corresponding to each interactive logic is used to indicate the degree of adaptation between the interactive logic and the UI component. Based on the page type identification result, the region decomposition result, the component identification result, and all the interaction logic corresponding to each UI component, all functional points to be implemented, the functional type, functional priority, and dependency relationship corresponding to each functional point are determined as functional point decomposition results; the functional type corresponding to each functional point includes any one of UI type, logic type, and interface type; the dependency relationship corresponding to each functional point is used to indicate the dependency order of that functional point and all other functional points it depends on.

[0011] As an optional implementation, in the first aspect of the present invention, the data model is used to define the model required for the page corresponding to the first data, and the data model includes models corresponding to field names, types, descriptions, and example values; The data source includes any one of the following: interface-based source, local source based on local resources, computation source based on preset computation operations, and static source based on static resources. The update conditions are used to define the triggering conditions for the page to perform a page update; the page state includes any one of the following: loading state, normal state, empty data state, and error state.

[0012] As an optional implementation, in the first aspect of the present invention, the anomaly identification information is used to define all the abnormal scenarios existing on the page, and all the abnormal scenarios include at least the abnormal scenarios corresponding to network error, empty data, loading timeout, insufficient permissions, input validation failure, and image loading failure. The anomaly identification information also includes anomaly handling suggestions for each of the anomaly scenarios; The document boundary information is used at least to define the text length and the number of lists on the page.

[0013] As an optional implementation, in the first aspect of the present invention, the step of performing format conversion operations, integrity checks, coherence checks, and information filling operations on the page structure analysis results, the interaction logic inference results, the function point decomposition results, the first document construction information, and the second document construction information according to a preset document template to obtain a structured auxiliary document for the first data, including: According to the preset document template, a format conversion operation is performed on the page structure analysis results, the interaction logic inference results, the function point decomposition results, the first document construction information, and the second document construction information to obtain the format conversion results for the page structure analysis results, the interaction logic inference results, the function point decomposition results, the first document construction information, and the second document construction information; Summarize all the interaction logic to be confirmed included in the inference results of the interaction logic to obtain summary information; Based on the summarized information, perform integrity checks and coherence checks on the format conversion results to obtain integrity check results for the integrity check operation and coherence check results for the coherence check operation. When both the integrity check result and the coherence check result indicate that the check has passed, document meta-information for the format conversion result is added according to the preset document template; The integrity check results, the coherence check results, the format conversion results, and the document metadata are filled into the preset document template according to the preset document format requirements to obtain a structured auxiliary document for the first data.

[0014] A second aspect of the present invention discloses an apparatus for generating development support documentation, the apparatus comprising: The data parsing module is used to determine the data type corresponding to the design drawing data, and to parse the design drawing data according to the data parsing method matching the data type to obtain the first data; the data type includes image type or link type; The page structure analysis module is used to perform page type identification, region decomposition, component identification and hierarchy determination operations on the first data to obtain the page structure analysis results for the first data. The logic inference and function point decomposition module is used to perform interactive logic inference operations and function point decomposition operations on the page structure analysis results respectively, so as to obtain the interactive logic inference results and function point decomposition results for the page structure analysis results. The information determination module is used to determine first document construction information and second document construction information corresponding to the first data and the page structure analysis result. The first document construction information includes at least one of the following: data model, data source, update conditions, page state, and component state. The second document construction information includes anomaly identification information and document boundary information. The document generation module is used to perform format conversion, integrity check, coherence check, and information filling operations on the page structure analysis results, interaction logic inference results, function point decomposition results, first document construction information, and second document construction information according to a preset document template, so as to obtain a structured auxiliary document for the first data.

[0015] As an optional implementation, in a second aspect of the present invention, the method by which the data parsing module parses the design drawing data according to a data parsing method matching the data type to obtain the first data specifically includes: When the data type is the image type, an image parsing operation is performed on the image to be processed included in the design drawing data to obtain UI element information for the design drawing data, which is used as the first data; When the data type is the link type, the links to be identified included in the design data are parsed to obtain the parsing result for the design data. Furthermore, based on the interfaces included in the design data, target link data matching the parsing result is obtained as the first data. The parsing result includes a file identifier and an optional node identifier. The target link data includes the page hierarchy structure, page layout attributes, and page text content corresponding to the parsing result.

[0016] As an optional implementation, in the second aspect of the present invention, the page structure analysis module performs page type identification, region decomposition, component identification, and hierarchy determination operations on the first data to obtain page structure analysis results for the first data. Specifically, this includes: Perform a page type identification operation on the first data to obtain a page type identification result for the first data. The page type identification result is used to indicate at least the page type of the page corresponding to the first data. Perform a region decomposition operation on the first data to obtain a region decomposition result for the first data. The region decomposition result is used to decompose the first data into multiple predefined functional regions. Perform a component identification operation on the region disassembly results to obtain component identification results for the region disassembly results. The component identification operation is used to identify the component category corresponding to each UI component included in each functional region and the component features corresponding to each UI component. Based on the component identification results, perform position identification operations and / or hierarchy relationship determination operations on each UI component to obtain position identification results and / or hierarchy relationships for each UI component; The page type identification result, the region breakdown result, the component identification result, the position identification result for each UI component, and / or the hierarchical relationship are determined as the page structure analysis result for the first data.

[0017] As an optional implementation, in the second aspect of the present invention, the logic inference and function point decomposition module performs interactive logic inference operations and function point decomposition operations on the page structure analysis results respectively, and obtains interactive logic inference results and function point decomposition results for the page structure analysis results in the following specific ways: For each UI component, based on the component category and component characteristics corresponding to the UI component, at least one interactive logic and its corresponding annotation information that are adapted to the UI component are determined as the interactive logic inference result. The annotation information corresponding to each interactive logic is used to indicate the degree of adaptation between the interactive logic and the UI component. Based on the page type identification result, the region decomposition result, the component identification result, and all the interaction logic corresponding to each UI component, all functional points to be implemented, the functional type, functional priority, and dependency relationship corresponding to each functional point are determined as functional point decomposition results; the functional type corresponding to each functional point includes any one of UI type, logic type, and interface type; the dependency relationship corresponding to each functional point is used to indicate the dependency order of that functional point and all other functional points it depends on.

[0018] As an optional implementation, in a second aspect of the present invention, the data model is used to define the model required for the page corresponding to the first data, and the data model includes models corresponding to field names, types, descriptions, and example values; The data source includes any one of the following: interface-based source, local source based on local resources, computation source based on preset computation operations, and static source based on static resources. The update conditions are used to define the triggering conditions for the page to perform a page update; the page state includes any one of the following: loading state, normal state, empty data state, and error state.

[0019] As an optional implementation, in the second aspect of the present invention, the anomaly identification information is used to define all the abnormal scenarios existing on the page, and all the abnormal scenarios include at least the abnormal scenarios corresponding to network error, empty data, loading timeout, insufficient permissions, input validation failure, and image loading failure. The anomaly identification information also includes anomaly handling suggestions for each of the anomaly scenarios; The document boundary information is used at least to define the text length and the number of lists on the page.

[0020] As an optional implementation, in the second aspect of the present invention, the document generation module performs format conversion, integrity check, coherence check, and information filling operations on the page structure analysis results, the interaction logic inference results, the function point decomposition results, the first document construction information, and the second document construction information according to a preset document template, to obtain a structured auxiliary document for the first data. Specifically, this includes: According to the preset document template, a format conversion operation is performed on the page structure analysis results, the interaction logic inference results, the function point decomposition results, the first document construction information, and the second document construction information to obtain the format conversion results for the page structure analysis results, the interaction logic inference results, the function point decomposition results, the first document construction information, and the second document construction information; Summarize all the interaction logic to be confirmed included in the inference results of the interaction logic to obtain summary information; Based on the summarized information, perform integrity checks and coherence checks on the format conversion results to obtain integrity check results for the integrity check operation and coherence check results for the coherence check operation. When both the integrity check result and the coherence check result indicate that the check has passed, document meta-information for the format conversion result is added according to the preset document template; The integrity check results, the coherence check results, the format conversion results, and the document metadata are filled into the preset document template according to the preset document format requirements to obtain a structured auxiliary document for the first data.

[0021] A third aspect of the present invention discloses an electronic device, the electronic device comprising: Memory containing executable program code; A processor coupled to the memory; The processor calls the executable program code stored in the memory to execute some or all of the steps in the method for generating development auxiliary documents according to any of the first aspects of the present invention.

[0022] The fourth aspect of the present invention discloses a method for developing an application, wherein the application is developed according to a structured auxiliary document generated by the method for generating development auxiliary documents as described in any of the first aspects of the present invention, and the application is installed in an electronic device as described in the third aspect of the present invention, and the application is able to access file information in a network-attached storage device communicatively connected to the electronic device.

[0023] Compared with the prior art, the present invention has the following beneficial effects: This invention provides a method, electronic device, and program development method for generating development auxiliary documents. Implementing this invention enables automated parsing of design drawing data from different data types / input sources, improving the efficiency and accuracy of design drawing content extraction. Furthermore, it allows for page structure identification, interaction logic inference, and functional point decomposition of the extracted first data, achieving efficient and scientific extraction of page-related data and significantly reducing the risks of omissions and misunderstandings inherent in manual analysis. Finally, it integrates detailed data from multiple aspects to generate accurate and unified structured auxiliary documents, improving the efficiency and accuracy of document generation. Attached Figure Description

[0024] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0025] Figure 1 This is a flowchart illustrating a method for generating development auxiliary documents disclosed in an embodiment of the present invention; Figure 2 This is a flowchart illustrating another method for generating development auxiliary documents disclosed in an embodiment of the present invention; Figure 3 This is a schematic diagram of the structure of an apparatus for generating development auxiliary documents disclosed in an embodiment of the present invention; Figure 4 This is a schematic diagram of the structure of an electronic device disclosed in an embodiment of the present invention. Detailed Implementation

[0026] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0027] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this invention are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, apparatus, product, or end that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or ends.

[0028] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of the invention. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0029] This invention discloses a method, electronic device, and program development method for generating development auxiliary documents. It can automatically parse design drawing data of different data types / input sources, improving the efficiency and accuracy of extracting design drawing content. Furthermore, it can perform page structure recognition, interaction logic inference, and functional point decomposition on the extracted first data, achieving efficient and scientific extraction of page-related data and greatly reducing the risks of omissions and misunderstandings inherent in manual analysis. Finally, it can integrate detailed data from multiple aspects to generate accurate and unified structured auxiliary documents, improving the efficiency and accuracy of document generation. These will be described in detail below.

[0030] Example 1 Please see Figure 1 , Figure 1This is a flowchart illustrating a method for generating development auxiliary documents disclosed in an embodiment of the present invention. Figure 1 The described method for generating development auxiliary documents can be applied to an apparatus for generating development auxiliary documents, and the embodiments of the present invention are not limited thereto. Figure 1 As shown, the method for generating development support documentation may include the following operations: 101. Determine the data type corresponding to the design drawing data, and parse the design drawing data according to the data parsing method that matches the data type to obtain the first data.

[0031] In this embodiment of the invention, the data type includes image type or link type; wherein, after acquiring / receiving design drawing data, when it is determined that the design drawing data includes an image / screenshot, the data type corresponding to the design drawing data is image type; when it is determined that the design drawing data includes a link or identifier corresponding to a design tool (such as Figma), the data type corresponding to the design drawing data is link type.

[0032] In this embodiment of the invention, by executing step 101, accurate and intelligent parsing of design drawing data is achieved, efficient extraction of design drawing content is realized, and it can also well adapt to the multi-source input requirements of design drawing data.

[0033] 102. Perform page type identification, region decomposition, component identification and hierarchy determination operations on the first data respectively to obtain the page structure analysis results for the first data.

[0034] In this embodiment of the invention, by executing step 102, the original layout, component division and nesting relationship of the design drawing can be analyzed hierarchically, eliminating the problem of inconsistency between the document and the design drawing structure caused by human misunderstanding.

[0035] 103. Perform interaction logic inference and function point decomposition operations on the page structure analysis results to obtain the interaction logic inference results and function point decomposition results based on the page structure analysis results.

[0036] In this embodiment of the invention, the interaction logic (such as jump, trigger, feedback) is automatically inferred based on the page structure analysis results, which can effectively avoid developers from missing hidden or cross-regional interaction behaviors when manually analyzing the design drawings, and improve the accuracy of the interaction logic inference results.

[0037] In this embodiment of the invention, the function point decomposition operation can reduce the common functional omissions or redundant descriptions that occur during manual decomposition, and ensure that the subsequently generated development documents can cover all business functions carried by the design drawings, thereby improving the comprehensiveness and accuracy of the function point decomposition results.

[0038] 104. Determine the first document construction information and the second document construction information corresponding to the first data and page structure analysis results.

[0039] In this embodiment of the invention, the first document construction information includes at least one of the following: data model, data source, update conditions, page state, and component state; the second document construction information includes anomaly identification information and document boundary information.

[0040] In this embodiment of the invention, the data model is used to define the model required for the page corresponding to the first data, and the data model includes models corresponding to field names, types, descriptions, and example values.

[0041] In this embodiment of the invention, the data source includes any one of the following: interface source based on interface, local source based on local resources, calculation source based on preset calculation operation, and static source based on static resources.

[0042] In this embodiment of the invention, the first document constructs information to provide developers with a basis for designing data and status, which facilitates alignment with backend interfaces and local status management.

[0043] In this embodiment of the invention, the update condition is used to define the triggering condition for the page to perform a page update; the page state includes any one of the following: loading state, normal state, empty data state, and error state.

[0044] In this embodiment of the invention, the anomaly identification information is used to define all the abnormal scenarios that exist on the page. All abnormal scenarios include at least the abnormal scenarios corresponding to network errors, empty data, loading timeout, insufficient permissions, input validation failure, and image loading failure.

[0045] In this embodiment of the invention, the anomaly identification information also includes anomaly handling suggestions for each anomaly scenario.

[0046] In this embodiment of the invention, the document boundary information is used at least to define the text length and the number of lists on the page.

[0047] In this embodiment of the invention, by using the anomaly identification information and document boundary information in the second document construction information, it is possible to automatically mark the parts that are not covered or have ambiguity in the design drawings, which can effectively prevent developers from having an excessive or incorrect understanding of the design intent. At the same time, it can also remind developers to consider anomalies and boundaries during implementation, reducing experience problems caused by omissions after going live.

[0048] 105. According to the preset document template, perform format conversion, integrity check, coherence check and information filling operations on the page structure analysis results, interaction logic inference results, function point decomposition results, first document construction information and second document construction information respectively to obtain a structured auxiliary document for the first data.

[0049] In this embodiment of the invention, by executing steps 101-105, developers no longer need to manually disassemble the structure, interaction, and data flow from the design drawings. The automatically generated structured document covers information such as page structure, interaction logic, functional implementation points, data flow, and boundary conditions, allowing developers to understand it uniformly before coding, reducing omissions and misunderstandings. At the same time, the structured auxiliary document produced has a consistent document structure, which facilitates alignment and version tracking when collaborating with multiple terminals or members, and can also reduce rework caused by inconsistent understanding.

[0050] It is evident that implementation Figure 1 The described method for generating development support documents can automatically parse design drawing data of different data types / input sources, improving the efficiency and accuracy of extracting design drawing content; it can also perform page structure recognition, interaction logic inference, and function point decomposition on the extracted first data, achieving efficient and scientific extraction of page-related data, greatly reducing the risks of omissions and misunderstandings that may occur in manual analysis; finally, it can integrate detailed data from multiple aspects to generate accurate and unified structured support documents, improving the efficiency and accuracy of document generation.

[0051] In an optional embodiment, the method of parsing the design drawing data to obtain the first data according to the data parsing method matching the data type in step 101 specifically includes: When the data type is image, perform image parsing operation on the image to be processed included in the design drawing data to obtain UI element information for the design drawing data, which is used as the first data; When the data type is a link type, the process involves parsing the links to be identified within the design data to obtain the parsing results. Then, based on the interfaces included in the design data, the process retrieves the target link data that matches the parsing results, serving as the first data. The parsing results include file identifiers and optional node identifiers. The target link data includes the page hierarchy, page layout attributes, and page text content corresponding to the parsing results. Optionally, the target link data may also include visual attributes corresponding to the parsing results.

[0052] As can be seen, in this optional embodiment, a data parsing mechanism is set for two different data sources. When the design drawing is an image, UI element information (such as controls, icons, text blocks, etc.) is directly obtained through image parsing. Compared with the traditional method of manually annotating and recording element attributes of images, this image parsing operation can improve the efficiency and intelligence of element information extraction for image-type data sources. When the design drawing is a link, file identifiers and optional node identifiers are obtained by parsing the links, and the corresponding page hierarchy, layout attributes, and text content are obtained according to the interface. Through this flexible and differentiated data parsing mechanism, the flexibility and accuracy of parsing the first data are improved, as well as the parsing efficiency, intelligence, and accuracy of parsing the first data.

[0053] Example 2 Please see Figure 2 , Figure 2 This is a flowchart illustrating another method for generating development auxiliary documents disclosed in an embodiment of the present invention. Figure 2 The described method for generating development auxiliary documents can be applied to an apparatus for generating development auxiliary documents, and the embodiments of the present invention are not limited thereto. Figure 2 As shown, the method for generating development support documentation may include the following operations: 201. Determine the data type corresponding to the design drawing data, and parse the design drawing data according to the data parsing method that matches the data type to obtain the first data.

[0054] 202. Perform page type identification, region decomposition, component identification and hierarchy determination operations on the first data respectively to obtain the page structure analysis results for the first data.

[0055] 203. Perform interaction logic inference and function point decomposition operations on the page structure analysis results to obtain the interaction logic inference results and function point decomposition results based on the page structure analysis results.

[0056] 204. Determine the first document construction information and the second document construction information corresponding to the first data and page structure analysis results.

[0057] 205. According to the preset document template, perform format conversion operations on the page structure analysis results, interaction logic inference results, function point decomposition results, first document construction information, and second document construction information to obtain the format conversion results for the page structure analysis results, interaction logic inference results, function point decomposition results, first document construction information, and second document construction information.

[0058] In this embodiment of the invention, the format conversion operation is used to convert data such as the page structure analysis results, interaction logic inference results, function point decomposition results, first document construction information, and second document construction information into an easy-to-read pre-set document format (such as tables, lists, and process descriptions), thereby improving the readability of the data.

[0059] 206. Summarize all the interaction logic to be confirmed included in the inference results of the interaction logic to obtain summary information.

[0060] In this embodiment of the invention, by summarizing all interaction logic to be confirmed into an independent information set, developers can quickly locate interaction behaviors with unclear design intent or requiring further confirmation when reviewing documents, thus avoiding the neglect of items to be confirmed scattered throughout the document.

[0061] 207. Based on the summarized information, perform integrity checks and consistency checks on the format conversion results to obtain integrity check results for the integrity check operation and consistency check results for the consistency check operation.

[0062] In this embodiment of the invention, the integrity check operation is used to check whether the content of each chapter is complete. If a chapter is empty (e.g., "Input Validation Rules" is empty when there is no input box), supplementary explanations are provided to avoid misunderstanding as omissions.

[0063] In this embodiment of the invention, by performing an integrity check, it is possible to accurately identify whether there are missing fields (such as data source, update conditions, anomaly identification information, etc.) in the document construction information, and by performing a coherence check, it is possible to verify the logical connection between different analysis results, ensuring that the content of each chapter is consistent. For example, the click event mentioned in "interaction logic" has a corresponding functional item in "functional implementation point", reducing the problem of document content breakage caused by omissions or contradictions in intermediate analysis links.

[0064] 208. When both the integrity check and the consistency check result indicate that the check has passed, add document meta-information for the format conversion result according to the preset document template.

[0065] In this embodiment of the invention, the added document metadata (such as generation time, data source identifier, template version, etc.) can be used for subsequent document tracing, version comparison, and document management in automated toolchains.

[0066] 209. Fill the integrity check results, coherence check results, format conversion results, and document metadata into the preset document template according to the preset document format requirements to obtain a structured auxiliary document for the first data.

[0067] In this embodiment of the invention, the preset document format requirements may be table alignment requirements, chapter separation requirements, keyword bolding, etc.

[0068] For further descriptions of steps 201-204 in this embodiment of the invention, please refer to the other specific descriptions of steps 101-104 in Embodiment 1. These descriptions will not be repeated in this embodiment of the invention.

[0069] It is evident that implementation Figure 2 The described method for generating development support documents ensures consistency in format, content completeness, and logical coherence of the generated structured support documents by performing format conversion, completeness checks, coherence checks, and interaction logic summarization on multiple types of analysis results, and then uniformly filling in the template after adding document meta-information. This helps improve the accuracy of the generated structured support documents. At the same time, it can also centrally expose the interaction logic to be confirmed, making it easier for developers to view and reducing the decision-making risks caused by missing or contradictory information during the development phase.

[0070] In an optional embodiment, step 202 above performs page type identification, region decomposition, component identification, and hierarchy determination operations on the first data to obtain the page structure analysis results for the first data. Specifically, this includes: Perform a page type identification operation on the first data to obtain a page type identification result for the first data. The page type identification result is used to indicate at least the page type of the page corresponding to the first data. Perform a region decomposition operation on the first data to obtain the region decomposition result for the first data. The region decomposition result is used to decompose the first data into multiple predefined functional regions. Perform component identification operation on the region decomposition results to obtain component identification results for the region decomposition results. The component identification operation is used to identify the component category corresponding to each UI component included in each functional region and the component characteristics corresponding to each UI component. Based on the component identification results, perform position identification and / or hierarchy determination operations on each UI component to obtain the position identification results and / or hierarchy relationships for each UI component; The page type identification results, region breakdown results, component identification results, position identification results for each UI component, and / or hierarchical relationships are determined as the page structure analysis results for the first data.

[0071] In this optional embodiment, by performing a page type identification operation on the first data, an identification result indicating at least the page type (such as list page, detail page, form page, settings page, pop-up window, etc.) is obtained, providing prior constraints based on page category for subsequent interaction logic inference and function point decomposition, which is conducive to improving the execution efficiency and accuracy of subsequent interaction logic inference and function point decomposition.

[0072] In this optional embodiment, the first data is divided into multiple predefined functional areas (such as navigation area, content area, bottom operation area, etc.) through a region decomposition operation, so that the subsequent component identification and hierarchy determination operations are limited to be performed within a local area, which can help reduce the probability of cross-regional component misassociation.

[0073] In this optional embodiment, a component identification operation is performed on the region decomposition results to obtain the category (such as text, image, button, input box, switch, list, card) and component characteristics (such as size, style, text, whether there are arrow icon child nodes, whether there are switch controls, etc.) of the UI components in each functional area, which improves the detail of the final determined page structure analysis results.

[0074] In this optional embodiment, based on the component identification results, position identification and / or hierarchy determination operations are performed on each UI component to obtain the spatial coordinates of the component on the page or the occlusion relationship between upper and lower layers. This enables the page structure analysis results to accurately reflect the layout order and visual hierarchy in the design drawings, avoiding deviations in the front-end layout caused by missing hierarchy.

[0075] In this optional embodiment, the page structure analysis results can ultimately be displayed as a text list of components (e.g., in Markdown format), for example: Cell 1: Left icon + main title "Account and Security" + right arrow icon; Cell 2: Left-side icon + main title "Notification Settings" + right-side toggle control; Cell 3: Left icon + main title "Clear Cache" + right subtitle "45.2MB" + right arrow icon.

[0076] In this optional embodiment, the display format of the component list can be adjusted according to the actual situation, and the present invention does not limit it.

[0077] As can be seen, in this optional embodiment, by sequentially performing page type identification, functional area decomposition, component category and feature identification, and component position / hierarchical relationship determination on the first data, a page structure analysis result containing page type, area division, component granularity, and spatial hierarchical relationship is systematically, standardized, and procedurally constructed. This improves the accuracy and completeness of the page structure analysis result, while providing a clear, uniformly granular, and complete layout information analysis foundation for subsequent interaction logic inference and functional point decomposition.

[0078] In another optional embodiment, step 203 above performs interaction logic inference operations and function point decomposition operations on the page structure analysis results, respectively, to obtain the interaction logic inference results and function point decomposition results based on the page structure analysis results. Specifically, this includes: For each UI component, based on the component category and component characteristics corresponding to the UI component, at least one interaction logic and its corresponding annotation information that are adapted to the UI component are determined as the interaction logic inference result. The annotation information corresponding to each interaction logic is used to indicate the degree of adaptation between the interaction logic and the UI component. Based on the page type identification results, region decomposition results, component identification results, and all interaction logic corresponding to each UI component, determine all functional points to be implemented, the functional type, functional priority, and dependency relationships corresponding to each functional point, as the functional point decomposition results; the functional type corresponding to each functional point includes any one of UI type, logic type, and interface type; the dependency relationship corresponding to each functional point is used to indicate the dependency order of that functional point and all other functional points it depends on.

[0079] In this optional embodiment, for each UI component, based on its category (such as button, input box) and characteristics (such as size, text, style, presence of arrow icon child nodes, presence of switch controls, etc.), one or more interactive logics (such as click to jump, input validation, long press to delete, pop-up, switch toggle, information display, etc.) are determined to be adapted. A label indicating the degree of adaptation is generated for each interactive logic, so that subsequent developers can distinguish between "highly recommended" and "optional" interactive schemes and avoid introducing inapplicable or poorly adapted interactive logic into the documentation.

[0080] In this optional embodiment, when determining all functional points to be implemented, the page type identification results, region decomposition results, component identification results, and all interaction logic corresponding to each UI component can be integrated, so that the source of the functional point can be traced back to the specific component and its interaction behavior under the specific page type constraint, reducing the functional omissions caused by ignoring cross-component or cross-regional interactions during manual decomposition, and improving the accuracy and reliability of the determination of the functional point.

[0081] In this optional embodiment, a function type (UI type, logic type, or interface type) can be assigned to each function point, and the function priority and dependency relationship can be determined. This avoids confusion in the development plan caused by mixed function types, unclear priorities, and ambiguous dependencies, and improves the accuracy of subsequent development based on the relevant information of the function point.

[0082] In this optional embodiment, the functionalities corresponding to the UI type may include: functionalities related to page rendering, visual display, and animation effects. The functionalities corresponding to the logic type may include: functionalities related to interactive response, state management, route navigation, and data processing. The functionalities corresponding to the interface type may include: functionalities related to network requests, data acquisition, and state synchronization.

[0083] In this optional embodiment, the function priority can be set to P0 (required): core function, the page cannot be used normally if it is not implemented; P1 (important): important function, which affects the user experience but does not block the main process; P2 (optional): optimization function, which can be added in subsequent iterations. These three priorities are not limited in this embodiment of the invention.

[0084] In this optional embodiment, the dependencies corresponding to the function points can be as follows: F2 (list rendering) depends on F5 (data parsing): the setting item data must be parsed before the list can be rendered; F3 (click to jump) depends on F2 (list rendering) and F8 (route configuration): click to jump, etc. can only be responded to after the list is rendered and the route configuration is ready.

[0085] In this optional embodiment, the above-mentioned intelligent decomposition process for functional points can help developers clarify the implementation order (for example, first implement basic functions without dependencies such as F1, F7, and F8, and then implement high-level functions that depend on these basic functions such as F2, F3, and F4), and reasonably schedule and divide tasks (prioritize the implementation of P0 function, while P1 and P2 functions can be implemented in parallel or in subsequent iterations).

[0086] As can be seen, in this optional embodiment, by matching each UI component with interaction logic labeled with adaptability, and integrating page type, region, component and interaction logic to decompose functional points, while clarifying the type classification, priority and dependency order of each functional point, the interaction logic inference results have quantitative adaptability information, and the functional point decomposition results have structured characteristics that are arrangable, traceable and sortable, which greatly improves the accuracy and scientificity of the obtained interaction logic inference results and functional point decomposition results.

[0087] Example 3 Please see Figure 3 , Figure 3 This is a schematic diagram of the structure of an apparatus for generating development auxiliary documents, as disclosed in an embodiment of the present invention. Figure 3 As shown, the device for generating development auxiliary documents may include a data parsing module 301, a page structure analysis module 302, a logic inference and function point decomposition module 303, an information determination module 304, and a document generation module 305, wherein: The data parsing module 301 is used to determine the data type corresponding to the design drawing data to be analyzed, and to parse the design drawing data according to the data parsing method that matches the data type to obtain the first data; the data type includes image type or link type.

[0088] The page structure analysis module 302 is used to perform page type identification, region decomposition, component identification and hierarchy determination operations on the first data to obtain the page structure analysis results for the first data.

[0089] The logic inference and function point decomposition module 303 is used to perform interactive logic inference operations and function point decomposition operations on the page structure analysis results, respectively, to obtain the interactive logic inference results and function point decomposition results based on the page structure analysis results.

[0090] The information determination module 304 is used to determine the first document construction information and the second document construction information corresponding to the first data and the page structure analysis results. The first document construction information includes at least one of the following: data model, data source, update conditions, page state, and component state. The second document construction information includes anomaly identification information and document boundary information.

[0091] In this embodiment of the invention, the data model is used to define the model required for the page corresponding to the first data, and the data model includes models corresponding to field names, types, descriptions, and example values.

[0092] In this embodiment of the invention, the data source includes any one of the following: interface source based on interface, local source based on local resources, calculation source based on preset calculation operation, and static source based on static resources.

[0093] In this embodiment of the invention, the update condition is used to define the triggering condition for the page to perform a page update; the page state includes any one of the following: loading state, normal state, empty data state, and error state.

[0094] In this embodiment of the invention, the anomaly identification information is used to define all the abnormal scenarios that exist on the page. All abnormal scenarios include at least the abnormal scenarios corresponding to network errors, empty data, loading timeout, insufficient permissions, input validation failure, and image loading failure.

[0095] In this embodiment of the invention, the anomaly identification information also includes anomaly handling suggestions for each anomaly scenario.

[0096] In this embodiment of the invention, the document boundary information is used at least to define the text length and the number of lists on the page.

[0097] The document generation module 305 is used to perform format conversion, integrity check, coherence check and information filling operations on the page structure analysis results, interaction logic inference results, function point decomposition results, first document construction information and second document construction information according to the preset document template, so as to obtain a structured auxiliary document for the first data.

[0098] It is evident that implementation Figure 3 The described device for generating development support documents can automatically parse design drawing data of different data types / input sources, improving the efficiency and accuracy of extracting design drawing content; it can also perform page structure recognition, interaction logic inference, and function point decomposition on the extracted first data, achieving efficient and scientific extraction of page-related data, greatly reducing the risks of omissions and misunderstandings that may occur in manual analysis; finally, it can integrate detailed data from multiple aspects to generate accurate and unified structured support documents, improving the efficiency and accuracy of document generation.

[0099] In an optional embodiment, the data parsing module 301 parses the design drawing data according to a data parsing method matching the data type to obtain the first data, specifically including: When the data type is image, perform image parsing operation on the image to be processed included in the design drawing data to obtain UI element information for the design drawing data, which is used as the first data; When the data type is a link type, the links to be identified included in the design data are parsed to obtain the parsing results for the design data. Based on the interfaces included in the design data, the target link data that matches the parsing results is obtained as the first data. The parsing results include file identifiers and optional node identifiers. The target link data includes the page hierarchy structure, page layout attributes, and page text content corresponding to the parsing results.

[0100] As can be seen, in this optional embodiment, a data parsing mechanism is set for two different data sources. When the design drawing is an image, UI element information (such as controls, icons, text blocks, etc.) is directly obtained through image parsing. Compared with the traditional method of manually annotating and recording element attributes of images, this image parsing operation can improve the efficiency and intelligence of element information extraction for image-type data sources. When the design drawing is a link, file identifiers and optional node identifiers are obtained by parsing the links, and the corresponding page hierarchy, layout attributes, and text content are obtained according to the interface. Through this flexible and differentiated data parsing mechanism, the flexibility and accuracy of parsing the first data are improved, as well as the parsing efficiency, intelligence, and accuracy of parsing the first data.

[0101] In another optional embodiment, the page structure analysis module 302 performs page type identification, region decomposition, component identification, and hierarchy determination operations on the first data to obtain the page structure analysis results for the first data. Specifically, the methods include: Perform a page type identification operation on the first data to obtain a page type identification result for the first data. The page type identification result is used to indicate at least the page type of the page corresponding to the first data. Perform a region decomposition operation on the first data to obtain the region decomposition result for the first data. The region decomposition result is used to decompose the first data into multiple predefined functional regions. Perform component identification operation on the region decomposition results to obtain component identification results for the region decomposition results. The component identification operation is used to identify the component category corresponding to each UI component included in each functional region and the component characteristics corresponding to each UI component. Based on the component identification results, perform position identification and / or hierarchy determination operations on each UI component to obtain the position identification results and / or hierarchy relationships for each UI component; The page type identification results, region breakdown results, component identification results, position identification results for each UI component, and / or hierarchical relationships are determined as the page structure analysis results for the first data.

[0102] As can be seen, in this optional embodiment, by sequentially performing page type identification, functional area decomposition, component category and feature identification, and component position / hierarchical relationship determination on the first data, a page structure analysis result containing page type, area division, component granularity, and spatial hierarchical relationship is systematically, standardized, and procedurally constructed. This improves the accuracy and completeness of the page structure analysis result, while providing a clear, uniformly granular, and complete layout information analysis foundation for subsequent interaction logic inference and functional point decomposition.

[0103] In another optional embodiment, the logic inference and function point decomposition module 303 performs interactive logic inference operations and function point decomposition operations on the page structure analysis results, respectively, to obtain the interactive logic inference results and function point decomposition results based on the page structure analysis results. The specific methods include: For each UI component, based on the component category and component characteristics corresponding to the UI component, at least one interaction logic and its corresponding annotation information that are adapted to the UI component are determined as the interaction logic inference result. The annotation information corresponding to each interaction logic is used to indicate the degree of adaptation between the interaction logic and the UI component. Based on the page type identification results, region decomposition results, component identification results, and all interaction logic corresponding to each UI component, determine all functional points to be implemented, the functional type, functional priority, and dependency relationships corresponding to each functional point, as the functional point decomposition results; the functional type corresponding to each functional point includes any one of UI type, logic type, and interface type; the dependency relationship corresponding to each functional point is used to indicate the dependency order of that functional point and all other functional points it depends on.

[0104] As can be seen, in this optional embodiment, by matching each UI component with interaction logic labeled with adaptability, and integrating page type, region, component and interaction logic to decompose functional points, while clarifying the type classification, priority and dependency order of each functional point, the interaction logic inference results have quantitative adaptability information, and the functional point decomposition results have structured characteristics that are arrangable, traceable and sortable, which greatly improves the accuracy and scientificity of the obtained interaction logic inference results and functional point decomposition results.

[0105] In another optional embodiment, the document generation module 305 performs format conversion, integrity check, coherence check, and information filling operations on the page structure analysis results, interaction logic inference results, function point decomposition results, first document construction information, and second document construction information according to a preset document template, to obtain a structured auxiliary document for the first data. Specifically, this includes: According to the preset document template, perform format conversion operations on the page structure analysis results, interaction logic inference results, function point decomposition results, first document construction information, and second document construction information to obtain the format conversion results for the page structure analysis results, interaction logic inference results, function point decomposition results, first document construction information, and second document construction information; The summary information is obtained by summarizing all the interaction logic to be confirmed, including the inference results of the interaction logic. Based on the summarized information, perform integrity checks and coherence checks on the format conversion results to obtain integrity check results for the integrity check operation and coherence check results for the coherence check operation. When both the integrity check and the consistency check result indicate that the check has passed, add document meta-information for the format conversion result according to the preset document template; The integrity check results, coherence check results, format conversion results, and document metadata are filled into the preset document template according to the preset document format requirements to obtain a structured auxiliary document for the first data.

[0106] As can be seen, in this optional embodiment, by performing format conversion, integrity checks, coherence checks, and interaction logic summarization on multiple types of analysis results, and adding document meta-information to uniformly fill the template, the consistency of the generated structured auxiliary documents in terms of format, content completeness, and logical coherence is ensured, which is conducive to improving the accuracy of the generated structured auxiliary documents; at the same time, it can also centrally expose the interaction logic to be confirmed, making it convenient for developers to view, which helps to reduce the decision-making risks caused by missing or contradictory information during the development stage.

[0107] Example 4 Please see Figure 4 , Figure 4 This is a schematic diagram of the structure of an electronic device disclosed in an embodiment of the present invention. Figure 4 As shown, the electronic device may include: Memory 401 storing executable program code; Processor 402 coupled to memory 401; The processor 402 calls the executable program code stored in the memory 401 to execute some or all of the steps in any of the methods for generating development auxiliary documents described in Embodiment 1 or Embodiment 2 of the present invention.

[0108] Example 5 This invention discloses a method for developing an application. The method for developing the application is based on a structured auxiliary document generated by a method for generating development auxiliary documents as described in any one of the embodiments of this invention. The application is installed in an electronic device as described in Embodiment 4 of this invention, and the application is able to access file information in a network-attached storage device that is communicatively connected to the electronic device.

[0109] The system embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0110] Through the detailed description of the above embodiments, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, including read-only memory (ROM), random access memory (RAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), one-time programmable read-only memory (OTPROM), electrically-Erasable Programmable Read-Only Memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, disk storage, magnetic tape storage, or any other computer-readable medium that can be used to carry or store data.

[0111] Finally, it should be noted that the above embodiments are merely preferred embodiments of the present invention and are only used to illustrate the technical solutions of the present invention, not to limit them. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the various embodiments of the present invention.

Claims

1. A method for generating development auxiliary documents, characterized in that, The method includes: Determine the data type corresponding to the design drawing data, and parse the design drawing data according to the data parsing method matching the data type to obtain the first data; the data type includes image type or link type; Perform page type identification, region decomposition, component identification and hierarchy determination operations on the first data respectively to obtain the page structure analysis results for the first data; The interaction logic inference operation and function point decomposition operation are performed on the page structure analysis results respectively to obtain the interaction logic inference result and function point decomposition result based on the page structure analysis results; Determine first document construction information and second document construction information corresponding to the first data and the page structure analysis results. The first document construction information includes at least one of the following: data model, data source, update conditions, page state, and component state. The second document construction information includes anomaly identification information and document boundary information. According to the preset document template, the page structure analysis results, the interaction logic inference results, the function point decomposition results, the first document construction information, and the second document construction information are respectively subjected to format conversion operation, integrity check operation, coherence check operation, and information filling operation to obtain a structured auxiliary document for the first data.

2. The method for generating development auxiliary documents according to claim 1, characterized in that, The step of parsing the design drawing data according to a data parsing method matching the data type to obtain the first data includes: When the data type is the image type, an image parsing operation is performed on the image to be processed included in the design drawing data to obtain UI element information for the design drawing data, which is used as the first data; When the data type is the link type, the links to be identified included in the design data are parsed to obtain the parsing result for the design data. Furthermore, based on the interfaces included in the design data, target link data matching the parsing result is obtained as the first data. The parsing result includes a file identifier and an optional node identifier. The target link data includes the page hierarchy structure, page layout attributes, and page text content corresponding to the parsing result.

3. The method for generating development auxiliary documents according to claim 1 or 2, characterized in that, The step of performing page type identification, region decomposition, component identification, and hierarchy determination operations on the first data respectively yields page structure analysis results for the first data, including: Perform a page type identification operation on the first data to obtain a page type identification result for the first data. The page type identification result is used to indicate at least the page type of the page corresponding to the first data. Perform a region decomposition operation on the first data to obtain a region decomposition result for the first data. The region decomposition result is used to decompose the first data into multiple predefined functional regions. Perform a component identification operation on the region disassembly results to obtain component identification results for the region disassembly results. The component identification operation is used to identify the component category corresponding to each UI component included in each functional region and the component features corresponding to each UI component. Based on the component identification results, perform position identification operations and / or hierarchy relationship determination operations on each UI component to obtain position identification results and / or hierarchy relationships for each UI component; The page type identification result, the region breakdown result, the component identification result, the position identification result for each UI component, and / or the hierarchical relationship are determined as the page structure analysis result for the first data.

4. The method for generating development auxiliary documents according to claim 3, characterized in that, The interaction logic inference operation and function point decomposition operation are performed on the page structure analysis results respectively to obtain the interaction logic inference result and function point decomposition result based on the page structure analysis results, including: For each UI component, based on the component category and component characteristics corresponding to the UI component, at least one interactive logic and its corresponding annotation information that are adapted to the UI component are determined as the interactive logic inference result. The annotation information corresponding to each interactive logic is used to indicate the degree of adaptation between the interactive logic and the UI component. Based on the page type identification result, the region decomposition result, the component identification result, and all the interaction logic corresponding to each UI component, all functional points to be implemented, the functional type, functional priority, and dependency relationship corresponding to each functional point are determined as functional point decomposition results; the functional type corresponding to each functional point includes any one of UI type, logic type, and interface type; the dependency relationship corresponding to each functional point is used to indicate the dependency order of that functional point and all other functional points it depends on.

5. The method for generating development auxiliary documents according to claim 1, 2, or 4, characterized in that, The data model is used to define the model required for the page corresponding to the first data, and the data model includes models corresponding to field names, types, descriptions, and example values; The data source includes any one of the following: interface-based source, local source based on local resources, computation source based on preset computation operations, and static source based on static resources. The update conditions are used to define the triggering conditions for the page to perform a page update; the page state includes any one of the following: loading state, normal state, empty data state, and error state.

6. The method for generating development auxiliary documents according to claim 5, characterized in that, The anomaly identification information is used to define all the abnormal scenarios that exist on the page. All the abnormal scenarios include at least the abnormal scenarios corresponding to network error, empty data, loading timeout, insufficient permissions, input validation failure, and image loading failure. The anomaly identification information also includes anomaly handling suggestions for each of the anomaly scenarios; The document boundary information is used at least to define the text length and the number of lists on the page.

7. The method for generating development auxiliary documents according to claim 4, characterized in that, The process involves performing format conversion, integrity checks, coherence checks, and information filling operations on the page structure analysis results, interaction logic inference results, functional point decomposition results, first document construction information, and second document construction information, respectively, according to a preset document template, to obtain a structured auxiliary document for the first data, including: According to the preset document template, a format conversion operation is performed on the page structure analysis results, the interaction logic inference results, the function point decomposition results, the first document construction information, and the second document construction information to obtain the format conversion results for the page structure analysis results, the interaction logic inference results, the function point decomposition results, the first document construction information, and the second document construction information; Summarize all the interaction logic to be confirmed included in the inference results of the interaction logic to obtain summary information; Based on the summarized information, completeness check and consistency check operations are performed on the format conversion results to obtain completeness check results for the completeness check operation and consistency check results for the consistency check operation. When both the integrity check result and the coherence check result indicate that the check has passed, document meta-information for the format conversion result is added according to the preset document template; The integrity check results, the coherence check results, the format conversion results, and the document metadata are filled into the preset document template according to the preset document format requirements to obtain a structured auxiliary document for the first data.

8. An apparatus for generating development auxiliary documents, characterized in that, The device includes: The data parsing module is used to determine the data type corresponding to the design drawing data, and to parse the design drawing data according to the data parsing method matching the data type to obtain the first data; the data type includes image type or link type; The page structure analysis module is used to perform page type identification, region decomposition, component identification and hierarchy determination operations on the first data to obtain the page structure analysis results for the first data. The logic inference and function point decomposition module is used to perform interactive logic inference operations and function point decomposition operations on the page structure analysis results respectively, so as to obtain the interactive logic inference results and function point decomposition results for the page structure analysis results. The information determination module is used to determine first document construction information and second document construction information corresponding to the first data and the page structure analysis result. The first document construction information includes at least one of the following: data model, data source, update conditions, page state, and component state. The second document construction information includes anomaly identification information and document boundary information. The document generation module is used to perform format conversion, integrity check, coherence check, and information filling operations on the page structure analysis results, interaction logic inference results, function point decomposition results, first document construction information, and second document construction information according to a preset document template, so as to obtain a structured auxiliary document for the first data.

9. An electronic device, characterized in that, The electronic device includes: Memory containing executable program code; A processor coupled to the memory; The processor calls the executable program code stored in the memory to execute the method for generating development auxiliary documents as described in any one of claims 1-7; Alternatively, the electronic device may be used to install an application and perform corresponding operations based on instructions from the application.

10. A method for developing an application, characterized in that, The application is developed using a structured auxiliary document generated by the method for generating development auxiliary documents as described in any one of claims 1-7, and the application is installed in the electronic device as described in claim 9, and the application is able to access file information in a network-attached storage device that is communicatively connected to the electronic device.

Images