A system secondary development method, device, equipment and medium

Abstract

The embodiment of the specification discloses a system secondary development method, device, equipment and medium, comprising: creating single document information corresponding to each single document name in the database, the single document information comprising a single document association relationship; when generating a single document file of a specified single document name in the secondary development of a specified system, obtaining single document information corresponding to the specified single document name; generating the single document file of the specified single document name according to the single document information corresponding to the specified single document name, so as to modify the single document file of the specified single document name according to a preset secondary development requirement, and complete the secondary development of the specified system. The embodiment of the specification automatically generates a single document file, improves the development efficiency, reduces the manual error, enhances the adaptability and maintainability of the system, helps to speed up the secondary development process, reduces the development cost, and improves the system quality.

Description

Technical Field

[0001] This specification relates to the field of computer technology, and in particular to a method, apparatus, equipment and medium for secondary development of a system. Background Technology

[0002] In highly customizable ERP systems, clients or agents often need to perform secondary development. This requires clients or agents to have a clear understanding of the system's technical solutions, design concepts, and business processes, necessitating the provision of more in-depth and detailed development documentation than the user manual. Development documentation often needs to be manually written by developers, involving thousands of functional documents, and the design documents are complex, detailed, and demanding. Summary of the Invention

[0003] This specification provides one or more embodiments of a system secondary development method, apparatus, device, and medium to solve the technical problems raised in the background art.

[0004] One or more embodiments of this specification employ the following technical solutions:

[0005] This specification provides a system secondary development method according to one or more embodiments, including:

[0006] Create document information corresponding to each document name in the database, the document information including document association relationships;

[0007] When generating a document file with a specified document name during secondary development of a specified system, obtain the document information corresponding to the specified document name;

[0008] Based on the document information corresponding to the specified document name, a document file with the specified document name is generated, and the document file with the specified document name is modified according to preset secondary development requirements to complete the secondary development of the specified system.

[0009] This specification provides one or more embodiments of a system secondary development apparatus, the apparatus comprising:

[0010] The document information creation unit creates document information corresponding to each document name in the database, and the document information includes document association relationships;

[0011] The document information acquisition unit acquires the document information corresponding to the specified document name when a document file with a specified document name is generated during secondary development of the specified system.

[0012] The document file generation unit generates a document file with the specified document name based on the document information corresponding to the specified document name, so as to modify the document file with the specified document name according to the preset secondary development requirements and complete the secondary development of the specified system.

[0013] This specification provides one or more embodiments of a system secondary development device, comprising:

[0014] At least one processor; and,

[0015] A memory communicatively connected to the at least one processor; wherein,

[0016] The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to:

[0017] Create document information corresponding to each document name in the database, the document information including document association relationships;

[0018] When generating a document file with a specified document name during secondary development of a specified system, obtain the document information corresponding to the specified document name;

[0019] Based on the document information corresponding to the specified document name, a document file with the specified document name is generated, and the document file with the specified document name is modified according to preset secondary development requirements to complete the secondary development of the specified system.

[0020] This specification provides one or more embodiments of a non-volatile computer storage medium storing computer-executable instructions, which, when executed by a computer, can perform the following:

[0021] Create document information corresponding to each document name in the database, the document information including document association relationships;

[0022] When generating a document file with a specified document name during secondary development of a specified system, obtain the document information corresponding to the specified document name;

[0023] Based on the document information corresponding to the specified document name, a document file with the specified document name is generated, and the document file with the specified document name is modified according to preset secondary development requirements to complete the secondary development of the specified system.

[0024] The above-described at least one technical solution adopted in the embodiments of this specification can achieve the following beneficial effects:

[0025] The embodiments in this specification can create document information in the database and automatically generate document files based on this information. This automated generation can greatly reduce the workload of developers manually writing document files and improve development efficiency. Developers only need to focus on making necessary modifications and customizations to the generated files, without having to create the files from scratch.

[0026] The embodiments in this manual demonstrate that automatically generating document files can greatly reduce human error. Manually writing documents can easily lead to problems such as spelling errors, missing fields, and inconsistent formats. By automatically generating them, these potential errors can be reduced, and the accuracy of the documents can be improved.

[0027] The embodiments in this specification ensure consistency between the document file and the data in the database by retrieving document information from the database. This means that the generated file reflects the latest state of the database, reducing the risk of data inconsistency.

[0028] The embodiments in this specification improve system maintainability by creating and automatically generating document information. When the document structure or business rules change, only the information in the database needs to be updated, without having to manually modify all related files. This reduces maintenance costs.

[0029] The embodiments in this specification can adapt to different documents and different secondary development needs. By simply updating the document information in the database, document files that meet different needs can be generated, thus enhancing the flexibility of the system.

[0030] The document files automatically generated in the embodiments of this specification can be submitted along with the development code, which facilitates version management. This ensures that developers can easily track the change history of the files, thereby better managing the evolution of the system.

[0031] The embodiments in this specification reduce repetitive manual work, enabling developers to generate and modify document files more quickly, thereby improving development efficiency. This is crucial for rapid project iteration and delivery. Attached Figure Description

[0032] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings:

[0033] Figure 1 A flowchart illustrating a system secondary development method provided for one or more embodiments of this specification;

[0034] Figure 2 A schematic diagram of the structure of a system secondary development device provided for one or more embodiments of this specification;

[0035] Figure 3 This is a structural schematic diagram of a system secondary development device provided for one or more embodiments of this specification. Detailed Implementation

[0036] This specification provides a system secondary development method, apparatus, equipment, and medium through its embodiments.

[0037] As China's informatization construction deepens, more and more enterprises, especially manufacturing companies, are embarking on their own digital transformation and customizing ERP management software to suit their specific business scenarios. This places higher demands on the convenience and efficiency of secondary development of the system. Providing complete development documentation enables customers to achieve more efficient personalized customization. This necessitates that ERP systems require convenient, timely, accurate, and easy-to-use development documentation for writing and maintaining.

[0038] In highly customizable ERP systems, clients or agents often need to perform secondary development. This requires clients or agents to have a clear understanding of the system's technical solutions, design concepts, and business processes, necessitating the provision of more in-depth and detailed development documentation than the user manual. Development documentation often needs to be manually written by developers, involving thousands of functional documents. The design documents are complex, detailed, and require high-level drawing skills. Furthermore, when the system changes, the graphics need to be redrawn, and it's difficult to completely update the changed content. This results in a very large workload, is time-consuming and labor-intensive, and is prone to omissions and errors.

[0039] Most existing ERP software development documentation is manually written by developers, resulting in a large number of documents to be written, each with a huge workload. This leads to the following problems:

[0040] a) When writing the document, subtle errors are difficult to detect.

[0041] b) Different people write in different styles, and the content is brief, making it difficult for non-professional developers to perform secondary development based on the documents.

[0042] c) Updates often lag behind system changes, making timely updates difficult and often resulting in omissions as it is difficult to cover all updated content.

[0043] d) Even minor changes to the charts require a complete redrawing, resulting in a huge amount of repetitive work.

[0044] e) Once the document is written, it can only be used internally, and it is difficult for customers to view it, so it cannot be used for secondary development.

[0045] f) After multiple personnel changes and functional handovers, the documents gradually became difficult to maintain.

[0046] Based on the above requirements, the embodiments in this specification aim to realize the automatic and dynamic generation of design documents in the ERP system, solving the problems of time-consuming, error-prone, and repetitive work in manually writing documents. This frees designers from the tedious task of organizing design documents, allowing them to focus on the design itself, improving their work efficiency, and also avoiding manual document organization, thus increasing the accuracy of design documents.

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

[0048] Figure 1 This diagram illustrates a system secondary development method provided in one or more embodiments of this specification. This process can be executed by a system secondary development system. Certain input parameters or intermediate results in the process can be manually adjusted to help improve accuracy.

[0049] The method flow steps of the embodiments in this specification are as follows:

[0050] S102, Create document information corresponding to each document name in the database, the document information including document association relationships.

[0051] In the embodiments of this specification, the document association relationship may include the association relationship between the table header and the table body, the foreign key mapping relationship between the document table and the basic data table, the data flow relationship between documents, the sequential relationship of document operation functions, and the verification content.

[0052] The relationship between table headers and bodies: This refers to the relationship between the header and body sections of a document. In an ERP system, some documents may have header information and multiple body sections (e.g., a purchase order header and multiple purchase order details in a purchase order). This relationship needs to be recorded in the database so that the system understands how to link these data together.

[0053] Foreign key mapping between document tables and base data tables: An ERP system may include base data such as products, customers, and suppliers. Documents may need to be associated with these base data tables to obtain necessary information. Foreign key mapping describes the connection between document tables and base data tables.

[0054] Data flow relationships between documents: This refers to the data flow between documents, that is, how the data in one document affects another. For example, a sales order may generate a shipping order; these are two different documents, and there is a data flow relationship between them.

[0055] The sequential relationship of document operation functions: Documents in an ERP system can include various operations, such as creation, modification, approval, and cancellation. These operations need to be executed in a specific order to ensure the correctness of the business process. Therefore, it is necessary to record the sequential relationship of each operation.

[0056] Verification Content: During document processing, various verifications may be required to ensure data integrity and accuracy. These verifications should also be recorded so that the system can perform the corresponding verification operations when processing documents.

[0057] In the embodiments described in this specification, a table can be created in the database to store document relationships. A table named "Document Information" can be created, including the following fields:

[0058] Document Name

[0059] Relationship between table header and table body

[0060] Foreign key mapping relationship between document table and basic data table

[0061] Data flow relationship between documents

[0062] Sequential relationship of document operation functions

[0063] Verification content

[0064] At the same time, for each document, populate the corresponding information, including the document relationships mentioned above. This can be done using a database management tool (such as SQL Server Management Studio or MySQL Workbench), or by writing SQL scripts to insert data.

[0065] Next, it is necessary to ensure that the relationships between documents are correctly established in the database. This includes establishing foreign key relationships and defining the sequential relationships of data flow and operation functions.

[0066] Next, the validation content and documentation are recorded. For the validation content, triggers or stored procedures can be defined in the database to execute the corresponding validation rules when the document is processed. For the documentation, detailed information about the relationships between each document, data flow, operation sequence, and validation content can be recorded so that team members can understand and maintain these relationships.

[0067] By following the steps above, document information corresponding to each document name can be created in the database, including various relationships, to support the development and maintenance of the ERP system. This will help the system understand and manage the complex relationships between documents, improving the system's maintainability and scalability.

[0068] Furthermore, in the embodiments of this specification, when creating document information corresponding to each document name, the following can be achieved: A header-body association relationship can be created for each document name, whereby the header stores preset basic information of the document and the body stores preset detailed information; a foreign key mapping relationship can be created between the document table and the basic data table corresponding to each document name, whereby the foreign key mapping relationship establishes an association between the document and preset basic data; a data flow relationship can be created between documents corresponding to each document name, whereby the data flow relationship between documents stores the data flow relationship between different documents; a sequence relationship can be created between document operation functions corresponding to each document name, whereby the sequence relationship between document operation functions stores the sequence relationship between document operation functions; and verification content can be created for each document name, whereby the verification content is used to verify the document data.

[0069] It's important to note that the relationship between the table header and body is used to store the structure of documents in the database. Typically, a document can be divided into two main parts: a header and a body. The header stores basic information about the document, such as the document number, date, and customer, while the body stores detailed information such as the product, quantity, and price. Creating this relationship helps the system understand and process the document structure, and also supports linking the data in the header and body, enabling them to work together during operations.

[0070] It's important to note that the foreign key mapping between the document table and the base data table is used to establish a link between documents and pre-defined base data. In ERP systems, documents typically reference base data, such as products, customers, and suppliers. Foreign key mapping allows linking certain fields in a document with corresponding fields in the base data table to obtain necessary information. This ensures that documents remain synchronized with the base data table, guaranteeing data consistency and accuracy.

[0071] It's important to note that the data flow relationships between documents can be used to store the data transfer relationships between different documents. In an ERP system, data from one document may trigger or affect another. For example, a sales order can trigger the generation of a delivery note, or a purchase order can trigger the generation of a payment invoice. Recording these data flow relationships helps the system track data movement and ensures correct business processes.

[0072] It's important to note that regarding the sequential relationships of document operation functions, documents in an ERP system typically include various operation functions, such as creation, modification, approval, and cancellation. These operations need to be executed in a specific order to ensure the correctness of the business process. Establishing sequential relationships helps define and manage the execution order of operation functions and ensures that operations are performed in the correct sequence.

[0073] It should be noted that validation content is used to verify document data to ensure its integrity and accuracy. These validation rules can include data format, range restrictions, and required fields. Recording these validation details helps the system perform appropriate validation operations when processing documents, preventing non-compliant data input.

[0074] In summary, establishing the aforementioned relationships and information helps the ERP system better understand and manage document structure, the correlation of basic data, data flow, operation sequence, and data validation. This is crucial for the system's stability, maintainability, and the correctness of business processes.

[0075] S104, when generating a document file with a specified document name during secondary development of a specified system, obtain the document information corresponding to the specified document name.

[0076] In the embodiments described in this specification, secondary development is performed on a specified system to generate document files with specified document names, and in the process, document information corresponding to the specified document names is obtained. The specific implementation steps are as follows:

[0077] System Analysis: First, a detailed analysis of the specified system is required to understand its architecture, data storage methods, and data structures related to the documents. This analysis phase will help determine how to obtain information about the specified documents.

[0078] Database query: Based on the results of system analysis, write corresponding database query statements to retrieve document information corresponding to a specified document name from the system's database. This may include header information, body information, and associated basic data.

[0079] Data Retrieval: Execute a database query to retrieve the document information corresponding to the specified document name. This document information can be stored in a data structure for subsequent processing and document file generation.

[0080] S106, Based on the document information corresponding to the specified document name, generate a document file with the specified document name, so as to modify the document file with the specified document name according to the preset secondary development requirements, and complete the secondary development of the specified system.

[0081] In the embodiments of this specification, the document information of the specified document name can be analyzed first to obtain the analysis results; then, a document file of the specified document name can be created based on the analysis results; then, the document file of the specified document name can be modified according to the preset secondary development requirements to obtain a modified document file; finally, the secondary development of the specified system can be performed based on the modified document file.

[0082] It should be noted that the secondary development of the specified system in the embodiments of this specification can be achieved by generating a document file based on the document information of a specified document name and modifying it according to preset secondary development requirements. The specific implementation steps are as follows:

[0083] Analyze document information: You can retrieve document information based on a specified document name. This may involve database queries; follow the steps mentioned earlier to obtain the information for the specified document. Analyze this information, including the structure of the table header and body, basic data relationships, data flow relationships, operation function sequence, and validation content.

[0084] Create document files: Based on the analysis results, you can create document files with specified document names. This can be done by creating an initial version of the file based on the document's structure and format, or by using templates or automatic generation tools to generate basic document files.

[0085] Modifying document files: This step allows you to modify the generated document files according to pre-defined secondary development requirements. This may include adding, deleting, or modifying fields, applying custom styles, and automatically populating data based on specific rules. The purpose of this step is to customize the document file to meet specific business processes or style requirements.

[0086] Testing and Verification: After modifying the document, test and verify it to ensure the revised document meets expectations. Verification includes ensuring the modified content is consistent with requirements, the document format is correct, and the data is valid.

[0087] Secondary development integration: Integrating the modified document files into a designated system so that users can access and use them within the system. This may require modifying the system's interface or workflow to accommodate the new document files.

[0088] Documentation: Create documentation to record changes, the purpose of documents, and how to use them within the system. This will help other developers or system users understand and utilize this functionality.

[0089] Deployment: Deploy the modified system to make the changes take effect, ensuring that all users can access and use the new document files and functions.

[0090] By following the steps above, you can complete the secondary development of the specified system, including generating and modifying document files based on document information with specified document names, to meet pre-defined secondary development needs. This will make the system more adaptable to specific business requirements and improve user work efficiency.

[0091] Furthermore, in the embodiments of this specification, when performing secondary development of the designated system based on the modified document file, the association relationship between the table header and table body in the modified document file can be analyzed to determine the associated fields and association rules between the table header and table body. Based on the association rules, corresponding tables and fields can be created in the designated system. The foreign key mapping relationship between the document table and the basic data table in the modified document file can be analyzed to determine the associated fields between the foreign key fields in the document table and the basic data table, and corresponding foreign key relationships can be created in the designated system. The data flow relationship between documents in the modified document file can be analyzed to determine the data flow rules and logic between documents, and corresponding processes and logic can be set in the designated system. The sequential relationship of document operation functions in the modified document file can be analyzed to determine the order and flow of document operations, and corresponding interfaces and functional modules can be set in the designated system. The verification content in the modified document file can be analyzed to determine the verification rules and verification conditions of the documents, and corresponding verification rules can be added in the designated system.

[0092] It should be noted that the above content describes the analysis and implementation steps for various relationships and rules required to modify document files when performing secondary development of a specified system. The following are the specific understanding and implementation steps:

[0093] Analyzing the relationship between table headers and bodies: First, it's necessary to carefully examine the modified document to understand the relationship between the table headers and bodies. This may involve reviewing the document's structure and fields to determine the relationships between them.

[0094] Implementation steps: Based on the analysis results, create the corresponding database tables in the specified system, including table headers and bodies. Then, define the related fields and association rules to ensure that the data relationships between them are correct. This may involve creating foreign key relationships or other appropriate database constraints.

[0095] Analyze the foreign key mapping relationships between document tables and base data tables: Analyze the document files to determine which base data tables the document tables need to be mapped to using foreign keys. Understand which fields in the document tables are associated with the related fields in the base data tables.

[0096] Implementation steps: Create foreign key relationships in the specified system, connecting the foreign key fields in the document table with the related fields in the base data table. This way, when a document is created or modified, the system can automatically associate and retrieve the corresponding base data information.

[0097] Analyze the data flow relationships between documents: Analyze document files to determine the data flow rules and logic between different documents. Understand which operations trigger data flow, and the conditions that trigger data flow.

[0098] Implementation steps: Set up appropriate processes and logic in the designated system to ensure that when the data in one document changes, it triggers data updates or generation in related documents. This may require defining mechanisms such as workflows or triggers.

[0099] Analyze the sequential relationships of document operation functions: Understand the execution order of various operation functions in the document file, including creation, modification, approval, etc.

[0100] Implementation steps: Configure the interface and functional modules in the designated system to ensure that document operations are performed in the correct sequence. This may involve developing a user interface, defining operation permissions, and implementing workflow controls.

[0101] Analyze and verify the content: Analyze the verification rules and conditions in the document files to understand which data needs to be verified to ensure its integrity and accuracy.

[0102] Implementation steps: Add appropriate validation rules and conditions to the specified system to ensure the compliance of document data. This may include field format validation, range restrictions, and mandatory fields.

[0103] By following the steps above, secondary development can be performed in the designated system according to the needs of the modified document files. This includes setting up relationships, foreign key mappings, data flow rules, operation function sequences, and validation rules to ensure that the system can correctly process and manage document files. This will help improve the system's adaptability and functionality to meet specific business needs.

[0104] Furthermore, in the embodiments of this specification, when generating a document file with a specified module name during secondary development of a specified system, all document names under the specified module name can be obtained first, and the document information corresponding to all document names can be obtained; then, based on the document information corresponding to all document names, a document file with the specified module name can be generated, so as to modify the document file with the specified module name according to the preset secondary development requirements and complete the secondary development of the specified system.

[0105] It should be noted that the above describes a method for generating a document file with a specified module name when performing secondary development on a specified system. This includes obtaining all document names and corresponding document information under that module, then generating and modifying the document file based on this information. The specific implementation steps are as follows:

[0106] To retrieve all document names and information under a specified module name: First, it's necessary to obtain all document names under the specified module name from the specified system. This can be done through system database queries or API calls. Simultaneously, it's necessary to retrieve the document information corresponding to each document name, including the relationship between the table header and body, the foreign key mapping between the document table and the basic data table, data flow relationships, the order of operation functions, and validation content.

[0107] Implementation steps: Write a query or API call to retrieve all document names and corresponding document information under the specified module. Store this information in a data structure for subsequent processing.

[0108] Generate document files with specified module names: Based on the obtained document information, code needs to be written to dynamically generate document files with specified module names. This may require using a template engine or document generation tool to ensure that the generated file format and structure meet the preset secondary development requirements.

[0109] Implementation steps: Based on the obtained document information, use appropriate tools or programming languages ​​to write code to generate a document file with the specified module name. Ensure that it includes header information, body information, associated basic data, data flow rules, operation function sequence, and validation rules.

[0110] Modify document files to meet pre-defined secondary development requirements: Once document files are generated, they need to be modified according to pre-defined secondary development requirements. This may include adding, deleting, or modifying specific fields, adjusting the interface layout, defining operation permissions, etc.

[0111] Implementation steps: Based on the secondary development requirements, make necessary modifications to the generated document files. This may involve front-end interface development, back-end logic programming, and database table structure updates.

[0112] Testing and debugging: After modification, the generated document files and corresponding functions need to be tested and debugged to ensure that they work properly.

[0113] Implementation steps: Create test cases to test the generated document files and related functions. Resolve any problems or errors found to ensure the system functions as expected.

[0114] Deployment and integration: Once testing and debugging are complete, deploy the modified document file to the designated system and ensure its integration with the rest of the system.

[0115] Implementation steps: Deploy the generated document files to the designated system, ensuring they are accessible and usable, and that they work in conjunction with other system components.

[0116] Documentation and User Guide: Finally, document and user guide to document the entire process of generating and modifying document files, as well as how to use this function in the system.

[0117] Implementation steps: Create detailed documentation so that other developers or system users can understand and use this feature. Provide clear guidelines and examples.

[0118] By following the steps above, you can generate document files with specified module names during the secondary development of a designated system and modify them according to pre-defined requirements. This will help meet specific business needs and enhance the system's functionality and adaptability.

[0119] Furthermore, in the embodiments of this specification, when the document information corresponding to each document name in the database changes, the change information can be determined first; then, the document file of the specified document name can be updated according to the change information to obtain an updated document file; finally, the updated document file can be modified according to the preset secondary development requirements to complete the secondary development of the specified system.

[0120] It should be noted that the above describes how to update the document file with a specified document name based on changes to the document information corresponding to each document name in the database, and then modify the updated document file to complete the secondary development of the specified system. The specific implementation steps are as follows:

[0121] Identifying Change Information: First, it's necessary to determine which document names have undergone changes, and the specific details of those changes. This can be determined by monitoring database changes, reviewing change requests, or other methods.

[0122] Implementation steps: Based on the change information, record which document names need to be updated and the specific changes. This may include modifications to the relationship between table headers and bodies, changes to foreign key mappings, adjustments to data flow rules, changes to the order of operation functions, and updates to validation rules.

[0123] Updating document files: Existing document files can be modified to reflect identified changes. This may require modifications to the file's structure, format, or content.

[0124] Implementation steps: Update existing document files accordingly based on the change information. This may require using document editing tools, code generation tools, or template engines to ensure that the generated files match the new document information.

[0125] Modify the updated document files according to pre-defined secondary development requirements: In addition to updating the document files based on change information, further modifications to these files are needed based on pre-defined secondary development requirements. This may include adding new fields, customizing the interface, enhancing logic, etc.

[0126] Implementation steps: Based on the pre-defined secondary development requirements, further modifications will be made to the updated document file. This may require front-end interface development, back-end logic programming, and adjustments to the database table structure.

[0127] Testing and debugging: After the update and modification are completed, the document files and corresponding functions need to be tested and debugged to ensure that they work properly.

[0128] Implementation steps: Create test cases to test the updated document files and related functions. Resolve any problems or errors found to ensure the system functions as expected.

[0129] Deployment and integration: Once testing and debugging are complete, deploy the updated document files to the designated system and ensure that they integrate with the rest of the system.

[0130] Implementation steps: Deploy the updated document files to the designated system, ensuring they are accessible and available, and that they work in conjunction with other system components.

[0131] Documentation and User Guide: Finally, document and user guide the entire process of updating and modifying document files, as well as how to use this feature in the system.

[0132] Implementation steps: Create detailed documentation so that other developers or system users can understand and use the updated document files. Provide clear guidelines and examples.

[0133] By following the steps above, you can update document files with specified document names based on changes in the document information corresponding to each document name in the database, and modify them according to pre-defined secondary development requirements. This will help ensure that the system's document files remain synchronized with the information in the database, meet specific business needs, and enhance the system's functionality and adaptability.

[0134] It should be noted that the embodiments in this specification improve development efficiency, reduce human error, and enhance the adaptability and maintainability of the system by automating the generation of document files. This helps to accelerate the secondary development process, reduce development costs, and improve system quality. However, the implementation of this method requires ensuring that the document information in the database is accurate and complete to ensure that the generated document files meet the expected requirements.

[0135] It should be noted that the greatest advantage of the embodiments in this specification lies in the following aspects:

[0136] 1. Automatically generate design documents based on the information in the current document, reducing the workload of writing.

[0137] 2. When the system is updated, the documents can be automatically regenerated based on the changes, without the need for manual maintenance.

[0138] 3. The documentation is highly readable and can be submitted along with the development code, facilitating version control and reducing maintenance costs.

[0139] 4. The document's graphic content is editable, eliminating the need to redraw when making modifications.

[0140] 5. The document supports web page display and can be integrated into product pages for easy reference by customers during secondary development.

[0141] It should be noted that the method for automatically generating design documents in an ERP system, as proposed in the embodiments of this specification, can conveniently and automatically generate document design documents, ensuring timely and accurate updates, supporting version management, and achieving low-cost maintenance and use. This greatly improves business efficiency and reduces the probability of errors.

[0142] It should be noted that the embodiments in this specification provide the following technical solutions:

[0143] Based on the given document name, the system retrieves the associated tables, fields, and corresponding business and approval workflows from the database. After summarizing these, it uses Markdown syntax to generate a Markdown document containing table structures, class diagrams, process flowcharts, and sequence diagrams. This document is then converted to a corresponding PDF file. The Markdown document can be directly embedded into system pages. When the system is modified, it can be regenerated. Details of the generated content can also be manually refined.

[0144] The plan can be divided into the following two aspects:

[0145] 1. The database records the relationships between each document, including the relationship between the table header and body, the foreign key mapping relationship between the document table and the basic data table, the data flow relationship between documents, the sequential relationship of document operation functions, and the intermediate verification content.

[0146] 2. Based on the given document table names, retrieve the corresponding content from the database, summarize it, create charts and graphs in Markdown format, and generate a design document in .md format. Convert it to PDF or .docx format if necessary.

[0147] This manual describes a method for automatically generating design documents using an ERP system, which is explained in detail step by step below:

[0148] Step 1

[0149] When creating a database document, it is necessary to record the mapping relationship between the table header and table body, as well as the mapping relationship between foreign keys. The document data flow, business flow, i.e., the sequence of each operation and the data related to the document's circulation process, also need to be recorded in the data table.

[0150] Step Two:

[0151] Provide the name of the application document or module that needs to generate the design document, as well as the database connection method. When the module name is provided, the names of all application documents under the module can be automatically obtained.

[0152] Step 3:

[0153] Based on the application document name, the corresponding table relationships, data flow, and business flow are retrieved. Following Markdown syntax, the corresponding data table structure information table, program flowchart, class diagram, business sequence diagram, and description document are generated.

[0154] Step Four:

[0155] The above steps complete over 90% of the work; only minor manual additions to some descriptive details are required. If needed, the completed document can be directly converted to PDF format or embedded into the product interface for easier customer viewing and use.

[0156] Figure 2 This is a schematic diagram of the structure of a system secondary development device provided in one or more embodiments of this specification. The device includes: a document information creation unit 202, a document information acquisition unit 204, and a document file generation unit 206.

[0157] The document information creation unit 202 creates document information corresponding to each document name in the database, and the document information includes document association relationships.

[0158] The document information acquisition unit 204 acquires the document information corresponding to the specified document name when a document file with a specified document name is generated during secondary development of the specified system.

[0159] The document file generation unit 206 generates a document file with the specified document name based on the document information corresponding to the specified document name, so as to modify the document file with the specified document name according to the preset secondary development requirements and complete the secondary development of the specified system.

[0160] Figure 3 A schematic diagram of a system secondary development device provided for one or more embodiments of this specification includes:

[0161] At least one processor; and,

[0162] A memory communicatively connected to the at least one processor; wherein,

[0163] The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to:

[0164] Create document information corresponding to each document name in the database, the document information including document association relationships;

[0165] When generating a document file with a specified document name during secondary development of a specified system, obtain the document information corresponding to the specified document name;

[0166] Based on the document information corresponding to the specified document name, a document file with the specified document name is generated, and the document file with the specified document name is modified according to preset secondary development requirements to complete the secondary development of the specified system.

[0167] This specification provides one or more embodiments of a non-volatile computer storage medium storing computer-executable instructions, which, when executed by a computer, can perform the following:

[0168] Create document information corresponding to each document name in the database, the document information including document association relationships;

[0169] When generating a document file with a specified document name during secondary development of a specified system, obtain the document information corresponding to the specified document name;

[0170] Based on the document information corresponding to the specified document name, a document file with the specified document name is generated, and the document file with the specified document name is modified according to preset secondary development requirements to complete the secondary development of the specified system.

[0171] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments of apparatus, devices, and non-volatile computer storage media are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0172] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0173] The above description is merely one or more embodiments of this specification and is not intended to limit this specification. Various modifications and variations can be made to the one or more embodiments of this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of one or more embodiments of this specification should be included within the scope of the claims of this specification.

Claims

1. A method for secondary development of a system, characterized in that, The method includes: Create document information corresponding to each document name in the database. The document information includes document relationships. The document relationships include the relationship between the table header and the table body, the foreign key mapping relationship between the document table and the basic data table, the data flow relationship between documents, the sequential relationship of document operation functions, and the validation content. When generating a document file with a specified document name during secondary development of a specified system, obtain the document information corresponding to the specified document name; Based on the document information corresponding to the specified document name, a document file with the specified document name is generated, and the document file with the specified document name is modified according to the preset secondary development requirements to complete the secondary development of the specified system. The creation of document information corresponding to each document name includes: creating the association relationship between the table header and table body corresponding to each document name, wherein the association relationship between the table header and table body is used to store preset basic information of the document in the table header and preset detailed information in the table body; creating the foreign key mapping relationship between the document table and the basic data table corresponding to each document name, wherein the foreign key mapping relationship between the document table and the basic data table is used to establish the association between the document and the preset basic data; creating the data flow relationship between documents corresponding to each document name, wherein the data flow relationship between documents is used to store the data flow relationship between different documents; creating the sequential relationship of the document operation functions corresponding to each document name, wherein the sequential relationship of the document operation functions is used to store the sequential relationship between the operation functions of the documents; and creating the verification content corresponding to each document name, wherein the verification content is used to verify the document data. The step of generating a document file with the specified document name based on the document information corresponding to the specified document name, and modifying the document file with the specified document name according to preset secondary development requirements to complete the secondary development of the specified system, includes: analyzing the document information of the specified document name to obtain analysis results; creating a document file with the specified document name based on the analysis results; modifying the document file with the specified document name according to preset secondary development requirements to obtain a modified document file; and performing secondary development of the specified system based on the modified document file.

2. The method according to claim 1, characterized in that, The secondary development of the specified system based on the modified document file includes: Analyze the relationship between the table header and table body in the modified document file, determine the associated fields and association rules between the table header and table body, and create the corresponding table and fields in the specified system according to the association rules. Analyze the foreign key mapping relationship between the document table and the basic data table in the modified document file, determine the foreign key fields in the document table and the associated fields in the basic data table, and create the corresponding foreign key relationship in the specified system; Analyze the data flow relationship between documents in the modified document file, determine the data flow rules and logic between documents, and set the corresponding process and logic in the specified system; Analyze the sequential relationship of document operation functions in the modified document file, determine the order and process of document operations, and set up the corresponding interface and functional modules in the specified system; Analyze the verification content in the modified document file, determine the verification rules and conditions of the document, and add the corresponding verification rules in the specified system.

3. The method according to claim 1, characterized in that, When generating a document file with a specified module name during secondary development of a specified system, the method further includes: Get all document names under the specified module name, and get the document information corresponding to all document names; Based on the document information corresponding to all the document names, a document file with the specified module name is generated. The document file with the specified module name is then modified according to preset secondary development requirements to complete the secondary development of the specified system.

4. The method according to claim 1, characterized in that, When the document information corresponding to each document name in the database is changed, the method further includes: Confirm the change information; The document file with the specified document name is updated according to the change information to obtain an updated document file. The updated document file is then modified according to the preset secondary development requirements to complete the secondary development of the specified system.

5. A system secondary development device, characterized in that, The device includes: The document information creation unit creates document information corresponding to each document name in the database. The document information includes document association relationships. The document association relationships include the association relationship between the table header and the table body, the foreign key mapping relationship between the document table and the basic data table, the data flow relationship between documents, the sequential relationship of document operation functions, and the verification content. The document information acquisition unit acquires the document information corresponding to the specified document name when a document file with a specified document name is generated during secondary development of the specified system. The document file generation unit generates a document file with the specified document name based on the document information corresponding to the specified document name, so as to modify the document file with the specified document name according to the preset secondary development requirements and complete the secondary development of the specified system. The creation of document information corresponding to each document name includes: creating the association relationship between the table header and table body corresponding to each document name, wherein the association relationship between the table header and table body is used to store preset basic information of the document in the table header and preset detailed information in the table body; creating the foreign key mapping relationship between the document table and the basic data table corresponding to each document name, wherein the foreign key mapping relationship between the document table and the basic data table is used to establish the association between the document and the preset basic data; creating the data flow relationship between documents corresponding to each document name, wherein the data flow relationship between documents is used to store the data flow relationship between different documents; creating the sequential relationship of the document operation functions corresponding to each document name, wherein the sequential relationship of the document operation functions is used to store the sequential relationship between the operation functions of the documents; and creating the verification content corresponding to each document name, wherein the verification content is used to verify the document data. The step of generating a document file with the specified document name based on the document information corresponding to the specified document name, and modifying the document file with the specified document name according to preset secondary development requirements to complete the secondary development of the specified system, includes: analyzing the document information of the specified document name to obtain analysis results; creating a document file with the specified document name based on the analysis results; modifying the document file with the specified document name according to preset secondary development requirements to obtain a modified document file; and performing secondary development of the specified system based on the modified document file.

6. A system secondary development device, characterized in that, include: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to: Create document information corresponding to each document name in the database. The document information includes document relationships. The document relationships include the relationship between the table header and the table body, the foreign key mapping relationship between the document table and the basic data table, the data flow relationship between documents, the sequential relationship of document operation functions, and the validation content. When generating a document file with a specified document name during secondary development of a specified system, obtain the document information corresponding to the specified document name; Based on the document information corresponding to the specified document name, a document file with the specified document name is generated, and the document file with the specified document name is modified according to the preset secondary development requirements to complete the secondary development of the specified system. The creation of document information corresponding to each document name includes: creating the association relationship between the table header and table body corresponding to each document name, wherein the association relationship between the table header and table body is used to store preset basic information of the document in the table header and preset detailed information in the table body; creating the foreign key mapping relationship between the document table and the basic data table corresponding to each document name, wherein the foreign key mapping relationship between the document table and the basic data table is used to establish the association between the document and the preset basic data; creating the data flow relationship between documents corresponding to each document name, wherein the data flow relationship between documents is used to store the data flow relationship between different documents; creating the sequential relationship of the document operation functions corresponding to each document name, wherein the sequential relationship of the document operation functions is used to store the sequential relationship between the operation functions of the documents; and creating the verification content corresponding to each document name, wherein the verification content is used to verify the document data. The step of generating a document file with the specified document name based on the document information corresponding to the specified document name, and modifying the document file with the specified document name according to preset secondary development requirements to complete the secondary development of the specified system, includes: analyzing the document information of the specified document name to obtain analysis results; creating a document file with the specified document name based on the analysis results; modifying the document file with the specified document name according to preset secondary development requirements to obtain a modified document file; and performing secondary development of the specified system based on the modified document file.

7. A non-volatile computer storage medium, characterized in that, It stores computer-executable instructions, which, when executed by a computer, can achieve the following: Create document information corresponding to each document name in the database. The document information includes document relationships. The document relationships include the relationship between the table header and the table body, the foreign key mapping relationship between the document table and the basic data table, the data flow relationship between documents, the sequential relationship of document operation functions, and the validation content. When generating a document file with a specified document name during secondary development of a specified system, obtain the document information corresponding to the specified document name; Based on the document information corresponding to the specified document name, a document file with the specified document name is generated, and the document file with the specified document name is modified according to the preset secondary development requirements to complete the secondary development of the specified system. The creation of document information corresponding to each document name includes: creating the association relationship between the table header and table body corresponding to each document name, wherein the association relationship between the table header and table body is used to store preset basic information of the document in the table header and preset detailed information in the table body; creating the foreign key mapping relationship between the document table and the basic data table corresponding to each document name, wherein the foreign key mapping relationship between the document table and the basic data table is used to establish the association between the document and the preset basic data; creating the data flow relationship between documents corresponding to each document name, wherein the data flow relationship between documents is used to store the data flow relationship between different documents; creating the sequential relationship of the document operation functions corresponding to each document name, wherein the sequential relationship of the document operation functions is used to store the sequential relationship between the operation functions of the documents; and creating the verification content corresponding to each document name, wherein the verification content is used to verify the document data. The step of generating a document file with the specified document name based on the document information corresponding to the specified document name, and modifying the document file with the specified document name according to preset secondary development requirements to complete the secondary development of the specified system, includes: analyzing the document information of the specified document name to obtain analysis results; creating a document file with the specified document name based on the analysis results; modifying the document file with the specified document name according to preset secondary development requirements to obtain a modified document file; and performing secondary development of the specified system based on the modified document file.

Images