Document inspection method and device, electronic equipment and storage medium

Abstract

The application provides a document checking method and device, electronic equipment and storage medium. The method comprises the following steps: in response to a checking instruction, obtaining documents of multiple development stages in a software development life cycle; based on a preset vocabulary, checking the documents of each development stage to determine whether there is consistency between the document of the previous development stage and the document of the next development stage of each two adjacent development stages; if it is determined that there is no consistency between the document of the previous development stage and the document of the next development stage of any two adjacent development stages, obtaining a missing keyword between the document of the previous development stage and the document of the next development stage of the inconsistency, and modifying the document of the next development stage of the any two adjacent development stages based on the missing keyword. The method of the application can improve the accuracy of the checking result.

Description

Technical Field

[0001] This application relates to document inspection technology, and more particularly to a document inspection method, apparatus, electronic device, and storage medium. Background Technology

[0002] During software development, it is typically necessary to review security-related documentation to ensure consistency across different development phases. Consistency across development phases indicates that testing based on this documentation will yield accurate results. Inconsistencies prompt relevant users to adjust the security-related documentation.

[0003] Typically, documents are checked manually by specialized inspectors, which can easily lead to inaccurate results. Summary of the Invention

[0004] This application provides a document inspection method, apparatus, electronic device, and storage medium to solve the technical problem in the prior art where manual inspection easily leads to inaccurate inspection results.

[0005] Firstly, this application provides a method for examining documents, including:

[0006] Responding to inspection commands, retrieve documentation for multiple development phases throughout the software development lifecycle;

[0007] Based on a pre-defined thesaurus, the documents of each development stage are checked to determine whether there is consistency between the documents of the previous development stage and the documents of the next development stage in each pair of adjacent development stages.

[0008] If it is determined that there is no consistency between the documents of the previous development stage and the documents of the next development stage in any pairwise adjacent development stages, then the missing keywords between the documents of the previous development stage and the documents of the next development stage under the inconsistency are obtained, and the documents of the next development stage in any pairwise adjacent development stages are modified based on the missing keywords.

[0009] In one embodiment, checking the documentation for each development phase to determine whether there is consistency between the documentation of the previous development phase and the documentation of the next development phase for each pair of adjacent development phases includes:

[0010] Based on the chronological order in which the development phase documents were obtained, identify multiple adjacent development phases within each of the aforementioned development phases;

[0011] Check whether all keywords in the documents of the previous development stage of each pair of adjacent development stages that match the preset thesaurus can be found in the documents of the corresponding next development stage. The keywords in the preset thesaurus are determined based on R&D safety standards.

[0012] If it is determined that all keywords can be found in the corresponding documents of the next development stage, then it is determined that there is consistency between the documents of the previous development stage and the documents of the next development stage of each pair of adjacent development stages.

[0013] If it is determined that at least one keyword cannot be found in the document of the corresponding next development stage, then it is determined that there is no consistency between the documents of the previous development stage and the documents of the next development stage in each pair of adjacent development stages.

[0014] In one embodiment, the keywords in the preset thesaurus have multiple lengths. Therefore, checking whether all keywords matching the preset thesaurus in the documents of the previous development stage of each pair of adjacent development stages can be found in the documents of the corresponding next development stage includes:

[0015] According to the preset checking strategy from longest to shortest, starting with the longest keyword in the preset thesaurus, the system checks whether all keywords in the documents of the previous development stage of each pair of adjacent development stages that match the preset thesaurus can be found in the documents of the corresponding next development stage.

[0016] In one embodiment, if it is determined that there is no consistency between the documents of the previous development stage and the documents of the next development stage in any pairwise adjacent development stages, then the missing keywords between the documents of the previous development stage and the documents of the next development stage under the inconsistency are obtained, and the documents of the next development stage in any pairwise adjacent development stages are modified based on the missing keywords, including:

[0017] If it is determined that there is no consistency between the documents of the previous development stage and the documents of the next development stage of any two adjacent development stages, then the missing keywords in the documents of the previous development stage of any two adjacent development stages that could not be found in the documents of the corresponding next development stage will be recorded in the maintenance log.

[0018] The maintenance log is sent to the operator's terminal to trigger the terminal to add the missing keyword to the document of the next development stage of any two adjacent development stages, based on the maintenance log.

[0019] In one embodiment, the plurality of development phases include: a requirements definition phase, a system design phase, a development phase, and a testing phase.

[0020] In one embodiment, the preset thesaurus includes multiple keywords, including keywords that are the same as or associated with the de-identified transmission and keywords that are the same as or associated with the de-identified storage.

[0021] Secondly, this application provides a document inspection apparatus, comprising:

[0022] The document retrieval module is used to retrieve documents from multiple development stages in the software development lifecycle in response to inspection commands.

[0023] The document inspection module is used to inspect the documents of each development stage based on a preset thesaurus to determine whether there is consistency between the documents of the previous development stage and the documents of the next development stage in each pair of adjacent development stages.

[0024] The document modification module is used to, if it is determined that there is no consistency between the document of the previous development stage and the document of the next development stage in any pairwise adjacent development stages, obtain the missing keywords between the document of the previous development stage and the document of the next development stage under the inconsistency, and modify the document of the next development stage in any pairwise adjacent development stages based on the missing keywords.

[0025] Thirdly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0026] The memory stores computer-executed instructions;

[0027] The processor executes computer execution instructions stored in the memory to implement the method as described in the first aspect.

[0028] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method described in the first aspect.

[0029] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the method described in the first aspect.

[0030] The document inspection method, apparatus, electronic device, and storage medium provided in this application, in response to an inspection instruction, acquire documents from multiple development stages in the software development lifecycle; based on a preset thesaurus, inspect the documents of each development stage to determine whether there is consistency between the documents of the previous development stage and the documents of the next development stage in any pair of adjacent development stages; if it is determined that there is no consistency between the documents of the previous development stage and the documents of the next development stage in any pair of adjacent development stages, then the missing keywords between the documents of the previous development stage and the documents of the next development stage in any pair of adjacent development stages are acquired, and the documents of the next development stage in any pair of adjacent development stages are modified based on the missing keywords. Compared with the prior art of manually checking the consistency of documents, this application automatically checks the consistency of documents through a machine, thereby reducing errors in manual inspection and improving inspection efficiency. Furthermore, the ability to modify the documents of the next development stage in any pair of adjacent development stages based on the acquired missing keywords between the documents of the previous development stage and the documents of the next development stage in any pair of adjacent development stages also effectively improves the accuracy of document modification. Attached Figure Description

[0031] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0032] Figure 1 An application scenario diagram illustrating the document inspection method of this application embodiment;

[0033] Figure 2 This is a flowchart illustrating a document inspection method according to an embodiment of this application;

[0034] Figure 3 This is a flowchart illustrating a document inspection method according to another embodiment of this application;

[0035] Figure 4 A schematic diagram illustrating the structure of the document inspection method implemented in this application;

[0036] Figure 5 This is a schematic diagram of the electronic device used to implement a document inspection method.

[0037] The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to specific embodiments. Detailed Implementation

[0038] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0039] To clearly understand the technical solution of this application, the solutions of the prior art will be described in detail first.

[0040] During software development, it is typically necessary to review security-related documentation to ensure consistency across different development phases. Consistency across development phases indicates that testing based on this documentation will yield accurate results. Inconsistencies prompt relevant users to adjust the security-related documentation.

[0041] Typically, documents are checked manually by specialized inspectors, which can easily lead to inaccurate results.

[0042] Therefore, when faced with the technical problems of existing technologies, the inventors, through creative research, discovered that to improve the accuracy of inspection results, instead of manually checking the consistency of documents, machines automatically check the consistency of documents, thereby reducing errors in manual inspection and improving inspection efficiency. Machine-automated document inspection involves electronic devices responding to inspection commands, acquiring documents from multiple development stages in the software development lifecycle, and checking the documents of each development stage based on a preset thesaurus to determine whether there is consistency between the documents of the previous and next development stages of any two adjacent development stages. This reduces the inaccuracy problems that often occur with manual inspection. Similarly, when modifying documents of any two adjacent development stages in the next development stage using electronic devices, the accuracy of document modifications can also be improved.

[0043] The electronic device can be any device capable of performing document inspection methods, such as a terminal or a server.

[0044] Figure 1 This is an application scenario diagram illustrating the document inspection method of this application embodiment, such as... Figure 1As shown in the embodiment of this application, the document inspection method is applied in a network architecture that includes an electronic device 10 and a terminal 20, which are connected to the electronic device 10. The terminal 20 can be a terminal for maintenance personnel or another terminal that can be used by other relevant personnel to inspect documents. During inspection, the terminal 20 sends an inspection command to the electronic device 10, causing the electronic device 10 to respond to the inspection command and obtain documents from multiple development stages in the software development lifecycle. Based on a preset thesaurus, the documents of each development stage are inspected to determine whether there is consistency between the documents of the previous development stage and the documents of the next development stage in any pair of adjacent development stages. If it is determined that there is no consistency between the documents of the previous development stage and the documents of the next development stage in any pair of adjacent development stages, the missing keywords between the documents of the previous development stage and the documents of the next development stage under the inconsistency are obtained, and the documents of the next development stage in any pair of adjacent development stages are modified based on the missing keywords. After the document inspection method is completed, a command to end the inspection is sent to terminal 20 to indicate that terminal 20 has completed the inspection of documents for each development stage.

[0045] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will be described below with reference to the accompanying drawings.

[0046] Figure 2 This application provides a document inspection method according to an embodiment, such as... Figure 2 As shown, the document inspection method provided in this embodiment is executed by an electronic device. Therefore, the document inspection method provided in this embodiment includes the following steps:

[0047] Step 101: In response to the inspection instruction, retrieve documentation for multiple development phases in the software development lifecycle.

[0048] The inspection instruction is the command that triggers the inspection of documents during the development phase. The Software Life Cycle (SLC) refers to the lifecycle of software from its creation until it is scrapped or ceases to be used. The software development lifecycle typically includes the requirements definition phase, system design phase, development phase, deployment phase, testing phase, and release phase. When inspecting documents throughout the software development cycle in response to inspection instructions, the primary focus is on the documents from the requirements definition phase, system design phase, development phase, and testing phase.

[0049] Before the software development lifecycle enters the online release phase, dedicated inspectors can trigger the aforementioned terminal to generate inspection instructions and send them to electronic devices.

[0050] Step 102: Based on a preset thesaurus, check the documents of each development stage to determine whether there is consistency between the documents of the previous development stage and the documents of the next development stage in each pair of adjacent development stages.

[0051] The preset thesaurus is a pre-set thesaurus that includes multiple words that can be used to perform consistency checks on documents at each stage of development.

[0052] Based on a pre-defined thesaurus, the documents for each development stage are checked. This can be understood as checking the documents for each pair of adjacent development stages. After checking, it can be determined whether there is consistency between the documents of the previous development stage and the documents of the next development stage for each pair of adjacent development stages. For example, if the development stages for each pair of adjacent development stages are the requirements definition stage and the system design stage, then the documents for the requirements definition stage are the documents of the previous development stage, and the documents for the system design stage are the documents of the next development stage. As mentioned above, the software development lifecycle includes multiple development stages, including the requirements definition stage, system design stage, development stage, and testing stage. Therefore, the pairs of adjacent development stages are (requirements definition stage, system design stage), (system design stage, development stage), and (development stage, testing stage).

[0053] Determining whether there is consistency between the documents of the previous development stage and the documents of the next development stage in two adjacent development stages is mainly based on matching the content of the documents of the two adjacent development stages with a preset thesaurus, and determining whether there is consistency based on the matching results.

[0054] Based on a pre-defined thesaurus, this system checks the consistency of documentation across multiple development phases in the software development lifecycle. When documentation across development phases is consistent, it allows for direct testing of each phase, yielding accurate results. Alternatively, if any two development phase documents are inconsistent, the system alerts users to adjust those inconsistent documents to ensure consistency, thus enabling accurate testing results in subsequent iterations.

[0055] Step 103: If it is determined that there is no consistency between the document of the previous development stage and the document of the next development stage of any two adjacent development stages, then obtain the missing keywords between the document of the previous development stage and the document of the next development stage under the inconsistency, and modify the document of the next development stage of any two adjacent development stages based on the missing keywords.

[0056] Here, missing keywords refer to words that cannot be matched in a preset thesaurus between any two adjacent development phase documents (both the preceding and following phases). For example, word A may be found in the preset thesaurus in the preceding development phase document, but word A cannot be found in the following phase document.

[0057] If it is determined that there is no consistency between the documents of the previous development stage and the documents of the next development stage in any pair of adjacent development stages, then first determine at least one missing keyword in the documents of the previous development stage and the documents of the next development stage of the pair of adjacent development stages that are not consistent, and modify the documents of the next development stage of the pair of adjacent development stages based on the missing keyword.

[0058] Before making modifications, it's helpful to first identify the specific manifestations of inconsistencies. Based on these inconsistencies, it can be determined whether modifications are needed for the documentation of the next development stage in any pair of adjacent development stages. For example, if the inconsistency manifests as missing keywords appearing in the previous development stage but not in the next, the modification process would be to add the missing keywords to the next development stage. Alternatively, if the inconsistency is again manifested as missing keywords appearing in the previous development stage but not in the next, then no modifications will be made to the documentation of the next development stage.

[0059] In this application, in response to an inspection instruction, documents from multiple development stages in the software development lifecycle are acquired. Based on a preset thesaurus, the documents of each development stage are inspected to determine whether there is consistency between the documents of the previous development stage and the documents of the next development stage for any two adjacent development stages. If it is determined that there is no consistency between the documents of the previous development stage and the documents of the next development stage for any two adjacent development stages, the missing keywords between the documents of the previous development stage and the documents of the next development stage under the inconsistency are acquired, and the documents of the next development stage for any two adjacent development stages are modified based on the missing keywords. Compared with the prior art of manually checking the consistency of documents, this application automatically checks the consistency of documents by machine, thereby reducing errors in manual inspection and improving inspection efficiency. Furthermore, the ability to modify the documents of the next development stage for any two adjacent development stages based on the acquired missing keywords between the documents of the previous development stage and the documents of the next development stage under the inconsistency also effectively improves the accuracy of document modification.

[0060] As an alternative implementation method, such as Figure 3 As shown, in this embodiment, step 102 includes the following steps:

[0061] Step 201: Based on the chronological order of the documents obtained in each development stage, determine multiple adjacent development stages in each development stage.

[0062] Typically, documentation for a specific development phase is obtained only when the software development lifecycle reaches that phase. Therefore, the chronological order in which development phase documentation is obtained can be understood as the chronological order in which each development phase is generated within the software development lifecycle.

[0063] As mentioned above, the requirements definition phase is the first phase in the software development lifecycle, followed by the system design phase, the development phase, and the testing phase. Therefore, multiple adjacent development phases include (requirements definition phase, system design phase), (system design phase, development phase), and (development phase, testing phase).

[0064] Step 202: Check whether all keywords matching the preset thesaurus in the documents of the previous development stage of each pair of adjacent development stages can be found in the documents of the corresponding next development stage.

[0065] Keywords are terms used to perform consistency checks on documents at each development stage. The pre-defined keyword library is based on R&D security standards. The pre-defined keyword library includes keywords that are the same as or related to de-identified transmission, as well as keywords that are the same as or related to de-identified storage. For example, de-identified transmission includes terms like "starred transmission," "partially masked transmission," "starred delivery," and "partially masked delivery," all with different descriptions. Similarly, de-identified storage includes terms like "starred storage," "partially masked storage," "starred saving," "partially masked saving," "starred storage," and "partially masked storage," all with different descriptions.

[0066] Examine the documents of the previous development stage of each pair of adjacent development stages for multiple keywords that match a preset thesaurus, that is, determine which keywords in the documents of the previous development stage of each pair of adjacent development stages can be found in the preset thesaurus.

[0067] Then, based on the multiple keywords that match the preset thesaurus in the documents of the previous development stage of each pair of adjacent development stages, a search is performed in the documents of the next development stage of each pair of adjacent development stages to determine whether all keywords can be found in the documents of the corresponding next development stage.

[0068] Step 203: If it is determined that all keywords can be found in the corresponding documents of the next development stage, then it is determined that there is consistency between the documents of the previous development stage and the documents of the next development stage of each pair of adjacent development stages.

[0069] If multiple keywords in the documents of the previous development stage of each pair of adjacent development stages that match the preset thesaurus can all be found in the documents of the corresponding next development stage, it indicates that the keywords in the documents of the previous development stage do not exceed the keywords in the documents of the corresponding next development stage, nor are they inconsistent with the keywords in the documents of the corresponding next development stage. This determines that there is consistency between the documents of the previous development stage and the documents of the next development stage of each pair of adjacent development stages.

[0070] Step 204: If it is determined that at least one keyword cannot be found in the document of the corresponding next development stage, then it is determined that there is no consistency between the documents of the previous development stage and the documents of the next development stage of each pair of adjacent development stages.

[0071] If, in each pair of adjacent development stages, at least one of the keywords in the document of the previous development stage that matches the preset thesaurus cannot be found in the document of the corresponding next development stage, it indicates that the keywords in the document of the previous development stage are inconsistent with the keywords in the document of the corresponding next development stage, and / or there are more keywords in the document of the corresponding next development stage. In this case, it is determined that there is no consistency between the documents of the previous development stage and the documents of the next development stage.

[0072] In this embodiment, based on the chronological order of the documents obtained in each development stage, multiple adjacent development stages are identified. It is then checked whether all keywords in the document of the previous development stage of each pair of adjacent development stages that match a preset thesaurus can be found in the document of the corresponding next development stage. The keywords in the preset thesaurus are determined based on R&D safety standards. If all keywords can be found in the document of the corresponding next development stage, then the documents of the previous and next development stages of each pair of adjacent development stages are considered consistent. If at least one keyword cannot be found in the document of the corresponding next development stage, then the documents of the previous and next development stages of each pair of adjacent development stages are considered inconsistent. Since the determination of consistency between the documents of the previous and next development stages of each pair of adjacent development stages is based on whether all keywords in the document of the previous development stage can be found in the document of the corresponding next development stage, this method of determining consistency between the pairs of adjacent development stages is relatively accurate.

[0073] As an optional implementation, in this embodiment, the keywords in the preset thesaurus have multiple lengths. Step 202 specifically includes step 301: according to the preset checking strategy from longest to shortest, starting from the longest keyword in the preset thesaurus, check whether all the multiple keywords in the documents of the previous development stage of each pair of adjacent development stages that match the preset thesaurus can be found in the documents of the corresponding next development stage.

[0074] The preset thesaurus contains multiple keywords, each with different lengths. Keywords of different lengths may contain repeated words. If the matching is checked starting with the shorter keywords, it will lead to repeated matching of the longer keywords. In order to improve the accuracy and efficiency of the matching, a checking strategy is set in advance. The checking strategy is to prioritize checking the longer keywords when checking documents of each pair of adjacent development stages.

[0075] Specifically, according to the preset checking strategy from longest to shortest, starting with the longest keyword in the preset thesaurus, the system checks whether all the keywords in the documents of the previous development stage that match the preset thesaurus can be found in the documents of the corresponding next development stage.

[0076] In this embodiment, according to a preset checking strategy, starting with the longest keyword in the preset thesaurus, the system sequentially checks whether multiple keywords matching the preset thesaurus can be found in the documents of the previous development stage of each pair of adjacent development stages. Since matching starts with the longest keyword, the problem of duplicate matching can be avoided, thereby improving the accuracy and efficiency of the matching.

[0077] As an optional implementation, in this embodiment, step 103 includes the following steps:

[0078] Step 401: If it is determined that there is no consistency between the documents of the previous development stage and the documents of the next development stage of any two adjacent development stages, then the missing keywords in the documents of the previous development stage of any two adjacent development stages that could not be found in the corresponding documents of the next development stage are recorded in the maintenance log.

[0079] That is, the maintenance log stores all the missing keywords.

[0080] Step 402: Send the maintenance log to the operator's terminal to trigger the terminal to add the missing keyword to the document of the next development stage of any two adjacent development stages according to the maintenance log.

[0081] The maintenance log is sent to the operations and maintenance personnel's terminal via email or SMS, without specific limitations. After sending, the terminal can be triggered to add missing keywords to the documents of the next development stage in any two adjacent development stages based on the maintenance log.

[0082] In this embodiment, if it is determined that the documents of the previous development stage and the documents of the next development stage of any pair of adjacent development stages are inconsistent, then the missing keywords in the documents of the previous development stage that cannot be found in the corresponding documents of the next development stage are recorded in the maintenance log. The maintenance log is then sent to the terminal of the operations and maintenance personnel to trigger the terminal to add the missing keywords to the documents of the next development stage of any pair of adjacent development stages according to the maintenance log. Since the missing keywords of the documents of each pair of adjacent development stages may not be exactly the same, storing the missing keywords of the documents of each pair of adjacent development stages in the maintenance log can completely display the missing keywords between the documents of each pair of adjacent development stages. Then, by sending the maintenance log to the terminal of the maintenance personnel, the terminal can be triggered to modify the documents of each next development stage according to the maintenance log.

[0083] Figure 4 This is a schematic diagram of the structure of a document inspection device provided in an embodiment of this application, as shown below. Figure 4 As shown, the document inspection device 40 provided in this embodiment is located in an electronic device. Therefore, the document inspection device 40 provided in this embodiment includes:

[0084] Document acquisition module 41 is used to acquire documents for multiple development stages in the software development lifecycle in response to inspection instructions;

[0085] The document inspection module 42 is used to inspect the documents of each development stage based on a preset thesaurus to determine whether there is consistency between the documents of the previous development stage and the documents of the next development stage in each pair of adjacent development stages.

[0086] The document modification module 43 is used to obtain the missing keywords between the documents of the previous development stage and the documents of the next development stage under the inconsistency if it is determined that there is no consistency between the documents of any two adjacent development stages. Then, it modifies the documents of the next development stage of any two adjacent development stages based on the missing keywords.

[0087] Optionally, the document checking module 42 is specifically used to: determine multiple adjacent development stages in each development stage according to the time sequence of the documents obtained in the development stage; check whether multiple keywords in the document of the previous development stage of each pair of adjacent development stages that match a preset thesaurus can all be found in the document of the corresponding next development stage, wherein the keywords in the preset thesaurus are determined based on R&D security standards; if it is determined that all keywords can be found in the document of the corresponding next development stage, then it is determined that there is consistency between the document of the previous development stage and the document of the next development stage of each pair of adjacent development stages; if it is determined that at least one keyword cannot be found in the document of the corresponding next development stage, then it is determined that there is no consistency between the document of the previous development stage and the document of the next development stage of each pair of adjacent development stages.

[0088] Optionally, the keywords in the preset thesaurus have various lengths. When checking whether all the keywords in the documents of the previous development stage of each pair of adjacent development stages that match the preset thesaurus can be found in the documents of the corresponding next development stage, the document checking module 42 is specifically used to: according to the preset checking strategy from longest to shortest, starting from the longest keyword in the preset thesaurus, check whether all the keywords in the documents of the previous development stage of each pair of adjacent development stages that match the preset thesaurus can be found in the documents of the corresponding next development stage.

[0089] Optionally, the document modification module 43 is specifically used to: if it is determined that there is no consistency between the document of the previous development stage and the document of the next development stage of any two adjacent development stages, record the missing keywords in the document of the previous development stage of any two adjacent development stages that cannot be found in the document of the corresponding next development stage in the maintenance log; send the maintenance log to the terminal of the operation and maintenance personnel to trigger the terminal to add the missing keywords to the document of the next development stage of any two adjacent development stages according to the maintenance log.

[0090] Optionally, the multiple development phases include: requirements definition phase, system design phase, development phase, and testing phase.

[0091] Optionally, the preset thesaurus includes multiple keywords, including keywords that are the same as or related to the desensitized transmission and keywords that are the same as or related to the desensitized storage.

[0092] Figure 5 This is a block diagram illustrating an electronic device according to an exemplary embodiment, the device being as follows: Figure 5As shown, the electronic device includes: a memory 51 and a processor 52; the memory 51 is a memory for storing processor-executable instructions; the processor 52 is used to run computer programs or instructions to implement the document inspection method provided in any of the above embodiments.

[0093] The memory 51 is used to store programs. Specifically, the program may include program code, which includes computer operation instructions. The memory 51 may include high-speed RAM, and may also include non-volatile memory, such as at least one disk storage device.

[0094] The processor 52 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this disclosure.

[0095] Optionally, in specific implementations, if the memory 51 and processor 52 are implemented independently, then the memory 51 and processor 52 can be interconnected via bus 53 to complete mutual communication. Bus 53 can be an Industry Standard Architecture (ISA) bus 53, a Peripheral Component Interconnect (PCI) bus 53, or an Extended Industry Standard Architecture (EISA) bus 53, etc. Bus 53 can be divided into address bus 53, data bus 53, control bus 53, etc. For ease of representation, Figure 5 The bus 53 is represented by a single thick line, but this does not mean that there is only one bus 53 or only one type of bus 53.

[0096] Optionally, in a specific implementation, if the memory 51 and the processor 52 are integrated on a single chip, then the memory 51 and the processor 52 can communicate with each other through an internal interface.

[0097] A non-transitory computer-readable storage medium, wherein instructions in the storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the document inspection method described above.

[0098] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0099] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method for checking documents, characterized in that, The method includes: Responding to inspection commands, retrieve documentation for multiple development phases throughout the software development lifecycle; Based on a pre-defined thesaurus, the documents of each development stage are checked to determine whether there is consistency between the documents of the previous development stage and the documents of the next development stage in each pair of adjacent development stages. If it is determined that there is no consistency between the documents of the previous development stage and the documents of the next development stage in any pairwise adjacent development stages, then the missing keywords between the documents of the previous development stage and the documents of the next development stage under the inconsistency are obtained, and the documents of the next development stage in any pairwise adjacent development stages are modified based on the missing keywords. The step of checking the documents for each development stage to determine whether there is consistency between the documents of the previous development stage and the documents of the next development stage in each pair of adjacent development stages includes: Based on the chronological order in which the development phase documents were obtained, identify multiple adjacent development phases within each of the aforementioned development phases; Check whether all keywords in the documents of the previous development stage of each pair of adjacent development stages that match the preset thesaurus can be found in the documents of the corresponding next development stage. The keywords in the preset thesaurus are determined based on R&D safety standards. If it is determined that all keywords can be found in the corresponding documents of the next development stage, then it is determined that there is consistency between the documents of the previous development stage and the documents of the next development stage of each pair of adjacent development stages. If it is determined that at least one keyword cannot be found in the document of the corresponding next development stage, then it is determined that there is no consistency between the documents of the previous development stage and the documents of the next development stage in each pair of adjacent development stages.

2. The method according to claim 1, characterized in that, The keywords in the preset thesaurus have various lengths. The step of checking whether all keywords matching the preset thesaurus in the documents of the previous development stage of each pair of adjacent development stages can be found in the documents of the corresponding next development stage includes: According to the preset checking strategy from longest to shortest, starting with the longest keyword in the preset thesaurus, the system checks whether all keywords in the documents of the previous development stage of each pair of adjacent development stages that match the preset thesaurus can be found in the documents of the corresponding next development stage.

3. The method according to claim 1, characterized in that, If it is determined that there is no consistency between the documents of the previous development stage and the documents of the next development stage in any pairwise adjacent development stages, then the missing keywords between the documents of the previous development stage and the documents of the next development stage under the inconsistency are obtained, and the documents of the next development stage in any pairwise adjacent development stages are modified based on the missing keywords, including: If it is determined that there is no consistency between the documents of the previous development stage and the documents of the next development stage of any two adjacent development stages, then the missing keywords in the documents of the previous development stage of any two adjacent development stages that could not be found in the documents of the corresponding next development stage will be recorded in the maintenance log. The maintenance log is sent to the operator's terminal to trigger the terminal to add the missing keyword to the document of the next development stage of any two adjacent development stages, based on the maintenance log.

4. The method according to any one of claims 1-3, characterized in that, The multiple development phases include: requirements definition phase, system design phase, development phase, and testing phase.

5. The method according to claim 1, characterized in that, The preset thesaurus includes multiple keywords, including keywords that are the same as or related to the desensitized transmission, and keywords that are the same as or related to the desensitized storage.

6. A document inspection device, characterized in that, The device includes: The document retrieval module is used to retrieve documents from multiple development stages in the software development lifecycle in response to inspection commands. The document inspection module is used to inspect the documents of each development stage based on a preset thesaurus to determine whether there is consistency between the documents of the previous development stage and the documents of the next development stage in each pair of adjacent development stages. The document modification module is used to obtain the missing keywords between the documents of the previous development stage and the documents of the next development stage under the inconsistency if it is determined that there is no consistency between the documents of any two adjacent development stages. Then, it modifies the documents of the next development stage of any two adjacent development stages based on the missing keywords. The document inspection module is specifically used to determine multiple adjacent development stages in each development stage based on the chronological order of the documents obtained in the development stage. Check whether all keywords in the documents of the previous development stage of each pair of adjacent development stages that match the preset thesaurus can be found in the documents of the corresponding next development stage. The keywords in the preset thesaurus are determined based on R&D safety standards. If it is determined that all keywords can be found in the corresponding documents of the next development stage, then it is determined that there is consistency between the documents of the previous development stage and the documents of the next development stage of each pair of adjacent development stages. If it is determined that at least one keyword cannot be found in the document of the corresponding next development stage, then it is determined that there is no consistency between the documents of the previous development stage and the documents of the next development stage in each pair of adjacent development stages.

7. An electronic device, comprising: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-5.

9. A computer program product comprising a computer program that, when executed by a processor, implements the method of any one of claims 1-5.

Images