CN115617756A - Method, system, terminal device and storage medium for detecting requirement document - Google Patents

Method, system, terminal device and storage medium for detecting requirement document Download PDF

Info

Publication number
CN115617756A
CN115617756A CN202211243301.8A CN202211243301A CN115617756A CN 115617756 A CN115617756 A CN 115617756A CN 202211243301 A CN202211243301 A CN 202211243301A CN 115617756 A CN115617756 A CN 115617756A
Authority
CN
China
Prior art keywords
document
configuration information
detection
file
requirement
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202211243301.8A
Other languages
Chinese (zh)
Inventor
余洁
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Bank Co Ltd
Original Assignee
Ping An Bank Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ping An Bank Co Ltd filed Critical Ping An Bank Co Ltd
Priority to CN202211243301.8A priority Critical patent/CN115617756A/en
Publication of CN115617756A publication Critical patent/CN115617756A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/103—Formatting, i.e. changing of presentation of documents
    • G06F40/117—Tagging; Marking up; Designating a block; Setting of attributes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/30—Semantic analysis

Abstract

The invention relates to the field of document detection, and the embodiment of the invention discloses a method, a system, a terminal device and a storage medium for detecting a required document, wherein the method comprises the following steps: receiving a document list and a detection command from a client, and reading document numbers of all required documents in the document list; establishing data connection with a detection path according to the pre-configured detection path, and scanning all document contents corresponding to the document number under the detection path; reading document configuration information corresponding to each document, matching the document configuration information with the document content, detecting whether each document meets preset requirements or not, and sending a detection result to the client. The whole detection process is automated, and differential inspection can be performed according to different paths and different requirements of the requirement documents.

Description

Method, system, terminal device and storage medium for detecting requirement document
Technical Field
The present invention relates to the field of document detection, and in particular, to a method, a system, a terminal device, and a storage medium for detecting a document.
Background
Document compiling and reviewing in the system research and development process are indispensable links, particularly in the field of financial science and technology, and documents (including original requirement documents, requirement analysis, requirement review, system design, design review, test cases and the like) are important data for system development and later maintenance and need to be managed. Especially for a system with complex financial business rules, documents can record business processes, rules, indexes, apertures, fields and special processing logics, and the documents are used as important reference data for subsequent iteration and maintenance of the system and need to be managed in a key mode. And the basis of document management is to identify whether a document is missing.
Most companies use a data document management tool jira to perform demand management, but all companies and research and development teams have different completeness requirements on required documents, some require 4 documents and some require 9 documents, and because of differentiation, the completeness detection of the documents is performed through manual detection, which wastes time and labor.
Disclosure of Invention
In view of the above, the present invention provides a method, a system, a terminal device and a storage medium for detecting a document required in the fields of financial technology and the like.
In a first aspect, the present application provides a method for detecting a requirement document, which is applied to a server, and includes:
receiving a document list from a client, and reading document numbers of all required documents in the document list;
scanning all document contents corresponding to the document numbers under a detection path according to the preset detection path;
reading corresponding document configuration information according to each document number, matching the document configuration information with the document content to detect whether each document meets preset requirements, and sending a detection result to the client.
Further, the document configuration information includes a required file name in each of the requirement documents;
the reading of the document configuration information corresponding to each document, matching the document configuration information with the document content, and detecting whether each document meets preset requirements includes:
reading all file names in the required document, matching the read file names with the required file names in the document configuration information, if the read file names contain all the required file names, determining that the required document is complete, otherwise, determining that the required document has a file indeed;
and if the files are missing, determining that the corresponding requirement documents are unqualified, and if the files are complete, determining that the corresponding requirement documents are qualified.
Further, the method also comprises the following steps:
and when an error occurs in the detection process, determining that the required document is failed to be detected, feeding the failure log back to the client side, and continuing to detect.
Further, when the requirement document is judged to be qualified, the method further comprises the following steps:
acquiring corresponding file configuration information according to the name of each file;
reading the file content of each file in the required document, matching the file content with the file configuration information, and judging whether the data of each file content is lost or not;
and if the file content is missing relative to the file configuration information, determining that the corresponding file is unqualified.
In a second aspect, the present application further provides a method for detecting a requirement document, which is applied to a client and includes:
generating a document list according to the number of the required document and a preset format;
sending the document list to a server so that the server scans all document contents corresponding to the document numbers under a detection path according to the detection path configured in advance; matching the corresponding document configuration information with the document content to detect whether each document meets the preset requirement;
receiving a detection result fed back from the server;
and respectively displaying the detection result of each demand document according to the number of each demand document.
Further, the method also comprises the following steps:
generating document configuration information of each demand document according to the generation rule of the demand document;
and storing the document configuration information and the number of the required document in a correlation manner, and sending the document configuration information to the server, wherein the document configuration information is used for detecting whether each document meets the preset requirement.
Further, the method also comprises the following steps: and when the storage path of the requirement document is changed, sending the changed path to the server as a new detection path.
In a third aspect, the present application further provides a requirement document detecting system, including: a server and a client;
the client is used for generating a document list according to the number of the required document and a preset format;
the client is also used for sending the document list to a server;
the server is used for receiving a document list from a client and reading document numbers of all required documents in the document list;
the server is also used for scanning all document contents corresponding to the document numbers under the detection path according to the pre-configured detection path;
the server is also used for reading corresponding document configuration information according to each document number, matching the document configuration information with the document content to detect whether each document meets the preset requirement or not, and sending the detection result to the client;
and the client is also used for respectively displaying the detection result of each demand document according to the number of each demand document.
In a fourth aspect, the present application further provides a terminal device, which includes a processor and a memory, where the memory stores a computer program, and the computer program executes the method for detecting a requirement document when running on the processor.
In a fifth aspect, the present application further provides a readable storage medium storing a computer program, which when executed on a processor performs the method for detecting a requirement document.
The embodiment of the invention discloses a method, a system, a terminal device and a storage medium for detecting a demand document, wherein the method comprises the following steps: receiving a document list and a detection command from a client, and reading document numbers of all required documents in the document list; establishing data connection with a detection path according to the pre-configured detection path, and scanning all document contents corresponding to the document number under the detection path; reading document configuration information corresponding to each document, matching the document configuration information with the document content, detecting whether each document meets preset requirements or not, and sending a detection result to the client. The whole detection process is automated, and differential inspection can be performed according to different paths and different requirements of the requirement documents.
Drawings
In order to more clearly illustrate the technical solution of the present invention, the drawings required to be used in the embodiments will be briefly described below, and it should be understood that the following drawings only illustrate some embodiments of the present invention, and therefore should not be considered as limiting the scope of the present invention. Like components are numbered similarly in the various figures.
FIG. 1 is a system diagram illustrating a method for detecting a requirement document according to an embodiment of the present application;
FIG. 2 is a flow chart illustrating a method for detecting a requirement document according to an embodiment of the present disclosure;
FIG. 3 is a flow chart of a method for detecting a requirement document according to an embodiment of the present application;
FIG. 4 is a timing diagram illustrating a method for demand document detection according to an embodiment of the present application;
FIG. 5 is a diagram illustrating a flow of updating requirement document configuration information according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments.
The components of embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present invention, presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present invention without making any creative effort, shall fall within the protection scope of the present invention.
Hereinafter, the terms "including", "having", and their derivatives, which may be used in various embodiments of the present invention, are only intended to indicate specific features, numbers, steps, operations, elements, components, or combinations of the foregoing, and should not be construed as first excluding the existence of, or adding to, one or more other features, numbers, steps, operations, elements, components, or combinations of the foregoing.
Furthermore, the terms "first," "second," "third," and the like are used solely to distinguish one from another and are not to be construed as indicating or implying relative importance.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which various embodiments of the present invention belong. The terms (such as those defined in commonly used dictionaries) should be interpreted as having a meaning that is consistent with their contextual meaning in the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein in various embodiments of the present invention.
In the field of financial technology, it may be desirable to compile and detect a required document. The present application provides a requirement document detection system, as shown in fig. 1, comprising a server 20 and a client 10. The client 10 is configured to upload data such as a required document number or document configuration information to be detected to a server according to a requirement of a user, and a required document detection tool in the server 20 detects the required document. Because the requirement documents can be stored in any designated place, the storage device 30 may be a server such as an svn or a git, may be local to a personal computer, or may be a storage device in another path, and thus, after data connection is established between the server 20 and the storage locations, corresponding detection operations are performed, thereby implementing automatic detection of the requirement documents.
The technical solution of the present application will be described below with specific examples.
Example 1
As shown in fig. 2, the method for detecting a requirement document of the present application includes the following steps:
and S100, generating a document list according to the number of the required document and a preset format.
In this embodiment, the client may be an intelligent terminal such as a smart phone or a personal computer, which is used by a user, and provides a basic operation interface for the user, so that the user can perform operations related to document detection, such as uploading a document number and maintaining a document detection function, on the operation interface.
The requirement documents are documents for requirement planning written during project development, and each document has a number to indicate the name and category of the document. For example, a ten-digit number, which may be the first three characters representing the type of the document, the last 7 digits representing the serial number of the document, and so on.
The requirement document is a document formed according to certain requirements and formats, and is a document written for a specific development project or event project, and the content composition requirements of different company organizations or groups on the requirement document are different, so that different standards are required to be detected for different requirement documents.
The number of the requirement document is used for distinguishing different requirement documents, and a plurality of requirement documents may be detected in one detection, so that the numbers need to be generated into a document list according to a preset format so as to facilitate a detection tool to read the numbers.
For example, the numbers are separated by a separator of score, and each number occupies one row on its own, to form the final document list.
It can be understood that the document archive is not necessarily a file in doc format, and may be written in excel form, or in text format such as txt, and the written content only needs to conform to a preset format. The user can input the numbers of the required documents into the interface in a disordered mode, the interface automatically identifies the numbers, and the numbers are arranged to form corresponding format files.
And step S200, sending the document list and the detection command to a server, and receiving a detection result fed back by the server.
After the client generates the document list, the client needs to send the document list and a detection command to the server to instruct the server to perform detection. It is understood that the detection command is determined by the user to be issued, the document list may be sent from the client to the server where the detection tool is located by ftp or the like, and the detection command is issued according to the instruction of the user.
After the detection instruction is sent out, the detection result from the server can be waited, and the specific detection process is in the server.
Step S300, receiving a document list and a detection command from the client, and reading the document number of each required document in the document list.
After receiving the document list and the detection command from the client, the server knows that detection needs to be performed according to the list, and therefore the document list needs to be analyzed first, and each number needs to be read.
Step S400, according to a preset detection path, establishing data connection with the detection path, and scanning all document contents corresponding to the document number under the detection path.
The paths and positions stored in the requirement documents are according to specific service requirements, and the specified positions which may be stored by different departments are different, so that the stored paths also need to be configured in the server in advance, and when the numbers of the requirement documents are analyzed, the requirement documents can be searched according to the detection paths.
In this embodiment, these requirement documents may be maintained by jira, or may be simply stored in a server database such as svn, but paths exist regardless of the storage manner, and therefore these storage paths need to be configured in advance in the server for the detection tool to use.
Specifically, the requirement documents may be stored in different categories according to the types of the requirement documents, the requirement documents may be directly stored in the same path, or the requirement documents may be stored in different terminal devices in a distributed manner.
After obtaining the detection paths, data connection can be established according to the detection paths so as to access the file data under the paths.
During detection, only the documents recorded in the document list need to be detected, so the documents in the paths need to be scanned according to the numbers to find out the matched documents, and the documents with the consistent numbers are the required documents to be detected.
After finding the corresponding required document, the files in the documents need to be further scanned, and when the files are scanned, the names and the contents of the files are obtained, so that the following detection and judgment are facilitated.
Step S500, reading the document configuration information corresponding to each document, matching the document configuration information with the document content, detecting whether each document meets the preset requirement, and sending the detection result to the client.
It is understood that the requirement document may include a plurality of files, each of which needs to record different contents, some of the files are necessary, and the necessary files are the files recorded in the document configuration information and the document configuration information configured in the server.
Each document has a document configuration information, which can be found correspondingly according to the number, and if the document configuration information is found, matching can be performed in the corresponding document configuration information by combining the file name acquired in step 400. If all the file names in the document configuration information are matched with the file names acquired in the required document, the required document is qualified.
Specifically, the files a, b, and c necessary in a requirement document are actually scanned, and the requirement document is found to contain the files a, b, c, and d. It is known that the three files a, b and c are all provided, and the d file is added, but because necessary files exist, the requirement document is considered to be complete and qualified even if other files are added. If the contained files are a, b and d, and c files are lacked, the requirement document is incomplete.
Through the above judging mode, the required documents are detected, and whether the documents are qualified or not is judged, so that the detection result is generated.
In addition, the content in each file may be further detected, and it is understood that, if the requirement document is found to be unqualified in the above detection step, it is not necessary to continue checking the content, so that in the case that the requirement document is detected to be qualified in the above step, as shown in fig. 3, the method further includes:
step S510 reads all file names in the requirement document, and matches the read file names with the required file names in the document configuration information.
The file configuration information here may also be configured by the user through the client, and for each file, the corresponding content needs to be described therein and written in a certain format, so that the file configuration of each file can be set according to the writing requirements to form the file configuration information.
The file name and the corresponding file configuration information are stored in a correlated manner, so that the corresponding file configuration information can be found through the name of each file.
In step S520, if the read file names include all the required file names, it is determined that the required document is complete, otherwise, it is determined that the required document has file missing.
The matching in this step is used for matching corresponding contents, and for these contents, corresponding matching can be performed according to keywords, title positions, or after semantic analysis is performed on the file contents, whether the content of the corresponding contents in the file configuration information is sufficient is judged, and if so, the file is qualified.
In step S530, if there is a file missing, it is determined that the corresponding demand document is not qualified, and if the files are complete, it is determined that the corresponding demand document is qualified.
On the contrary, if the content recorded in the file is found to be missing or insufficient compared with the file configuration information, for example, the number of words does not meet the standard, the file is considered to be unqualified.
In addition, in the detection process, the detection program may report an error due to a system error or other various reasons, so that the detection process is stopped, the errors may be caused by bug of the detection program itself, or may be caused by external reasons or the reasons of the requirement files, for this reason, in the case of a system error, an error log is returned to the client, and then, according to the current state, the detection may be continued, or the detection may be stopped, and an operation instruction of the user is waited.
And S600, sorting the detection results, and respectively displaying the detection results of the required documents according to the numbers of the required documents.
The detection results are generated in the detection process of each document and are disordered, so that the detection results need to be gathered and sorted to generate the detection results suitable for reading and understanding of the user.
It can be understood that the lack of the file content and the lack of the file in the document are two unqualified cases, so for the specific unqualified reason, the classified description is required to be clear, and the specific unqualified reason is clearly described, for example, if a certain file is lacked, the document lacked in the detection result of the required document is labeled, which indicates that the document lacked. If the corresponding elements are absent in the file, marking the corresponding file and the absent elements, and explaining the reason, if the corresponding elements are absent, the corresponding elements are not found by remarks, and if the content is less and does not reach the standard, insufficient key content description can be recorded, and the like.
FIG. 4 shows a timing chart of the document detection method of the present application.
When the user needs to perform detection, the user provides the numbers of the corresponding requirement documents at the client, and then the numbers and the test commands are sent to the server, so that the server can perform subsequent detection operation.
After receiving the command, the server finds the required documents represented by the numbers through the numbers provided by the client and the preset detection path, scans the required documents to find the files in the required documents, finds corresponding document configuration information in the server according to the types of the required documents, judges whether the documents are complete or not through matching the document configuration information and the file names, and can further judge whether the content of the files meets the requirements under the condition of judging the completeness of the documents, thereby having comprehensive detection and judgment on the quality of the required documents. And then returning the judgments to the client as detection results.
The method for detecting the required documents specially detects the documents by arranging the server which is independent of the documents for storing the required documents, so that the whole detection tool does not need to rely on any document maintenance program, for a client, any document maintenance program or an inapplicable document maintenance program can be used for detecting by using the method for detecting the required documents, and the method has extremely high compatibility. Meanwhile, the whole detection process is automated, differential examination can be performed according to different paths and different requirements of the requirement document, and a specific detection result is fed back, so that a user can know the problem more clearly.
Example 2
As shown in fig. 5, the method for detecting a requirement document of the present application further includes the following steps:
step S700, generating document configuration information of each requirement document according to the generation rule of the requirement document.
The client can also upload the configuration information of the required document. As mentioned above, the requirement document has a certain format and requirement, that is, the document must include some specified files, which are the configuration of the document, and the configuration of different types of requirement documents is different, so that different document configuration information needs to be configured according to the type of the requirement document.
Step S800, the document configuration information and the serial number of the required document are stored in an associated mode and sent to the server, and therefore the setting of the required document detection conditions is completed.
And then storing the document configuration information and the number of the corresponding requirement document in an associated manner. It is understood that the associated number is a type number, so that each type of requirement document is stored with the respective configuration binding and then uploaded to the server through the client, so that the detection tool on the server has the detection criteria. And the detection tool in the subsequent server can detect the required document according to the document configuration information.
It can be understood that, in addition to the above document configuration information, where the required documents are specifically stored, how to connect, and the blocking password need to be stored in the server and used by the detection tool in the server, for this reason, these storage paths will be uploaded to the server as detection paths, and if the storage paths are changed, the corresponding updated storage paths are uploaded as detection paths for detection.
The application also provides a terminal device, which comprises a processor and a memory, wherein the memory stores a computer program, and the computer program executes the method for detecting the requirement document when running on the processor.
The terminal devices can be intelligent devices such as computers and mobile phone tablets.
The present application also provides a readable storage medium storing a computer program which, when run on a processor, performs the method for demand document detection.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method can be implemented in other ways. The apparatus embodiments described above are merely illustrative and, for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, each functional module or unit in each embodiment of the present invention may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention or a part of the technical solution that contributes to the prior art in essence can be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a smart phone, a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention.

Claims (10)

1. A method for detecting a requirement document is applied to a server and comprises the following steps:
receiving a document list from a client, and reading document numbers of all required documents in the document list;
scanning all document contents corresponding to the document numbers under the detection path according to a preset detection path;
reading corresponding document configuration information according to each document number, matching the document configuration information with the document content to detect whether each document meets preset requirements, and sending a detection result to the client.
2. The method according to claim 1, wherein the document configuration information includes a desired file name in each of the desired documents;
the reading of the corresponding document configuration information and the matching of the document configuration information and the document content to detect whether each document meets preset requirements includes:
reading all file names in the required document, and matching the read file names with the required file names in the document configuration information;
if the read file names contain all the required file names, determining that the required file is complete, otherwise, determining that the required file has file loss;
and if the files are missing, determining that the corresponding requirement documents are unqualified, and if the files are complete, determining that the corresponding requirement documents are qualified.
3. The method of claim 1, further comprising:
and when an error occurs in the detection process, determining that the required document is failed to be detected, feeding the failure log back to the client side, and continuing to detect.
4. The method of claim 2, wherein when the requirement document is judged to be qualified, the method further comprises:
acquiring corresponding file configuration information according to the name of each file;
reading the file content of each file in the required document, matching the file content with the file configuration information, and judging whether the data of each file content is lost or not;
and if the file content is missing relative to the file configuration information, determining that the corresponding file is unqualified.
5. A method for detecting a requirement document is applied to a client and comprises the following steps:
generating a document list according to the document number of the required document and a preset format;
sending the document list to a server so that the server scans all document contents corresponding to the document numbers under a detection path according to the detection path configured in advance; matching the corresponding document configuration information with the document content to detect whether each document meets the preset requirement;
receiving a detection result fed back from the server;
and respectively displaying the detection result of each demand document according to the number of each demand document.
6. The method of claim 5, further comprising:
generating document configuration information of each demand document according to the generation rule of the demand document;
and storing the document configuration information and the number of the required document in a correlation manner, and sending the document configuration information to the server, wherein the document configuration information is used for detecting whether each document meets the preset requirement.
7. The method of claim 5, further comprising: and when the storage path of the requirement document is changed, sending the changed path to the server as a new detection path.
8. A demand document detection system, comprising: a server and a client;
the client is used for generating a document list according to the number of the required document and a preset format;
the client is also used for sending the document list to a server;
the server is used for receiving a document list from a client and reading document numbers of all required documents in the document list;
the server is also used for scanning all document contents corresponding to the document numbers under the detection path according to the pre-configured detection path;
the server is also used for reading corresponding document configuration information according to each document number, matching the document configuration information with the document content to detect whether each document meets the preset requirement or not, and sending the detection result to the client;
and the client is also used for respectively displaying the detection result of each demand document according to the number of each demand document.
9. A terminal device comprising a processor and a memory, the memory storing a computer program which, when run on the processor, performs the method of demand document detection of any one of claims 1 to 7.
10. A readable storage medium storing a computer program which, when executed on a processor, performs the requirement document detection method of any one of claims 1 to 7.
CN202211243301.8A 2022-10-11 2022-10-11 Method, system, terminal device and storage medium for detecting requirement document Pending CN115617756A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211243301.8A CN115617756A (en) 2022-10-11 2022-10-11 Method, system, terminal device and storage medium for detecting requirement document

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211243301.8A CN115617756A (en) 2022-10-11 2022-10-11 Method, system, terminal device and storage medium for detecting requirement document

Publications (1)

Publication Number Publication Date
CN115617756A true CN115617756A (en) 2023-01-17

Family

ID=84861709

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211243301.8A Pending CN115617756A (en) 2022-10-11 2022-10-11 Method, system, terminal device and storage medium for detecting requirement document

Country Status (1)

Country Link
CN (1) CN115617756A (en)

Similar Documents

Publication Publication Date Title
CN101770470B (en) File type identifying and analyzing method and system
US20180075138A1 (en) Electronic document management using classification taxonomy
US7386566B2 (en) External metadata processing
JP5126541B2 (en) Information classification device, information classification method, and information classification program
CN104317713A (en) Automatic testing tool and method on basis of templates
CN109063178B (en) Method and device for automatically expanding self-help analysis report
CN113688288B (en) Data association analysis method, device, computer equipment and storage medium
CN111885051B (en) Data verification method and device and electronic equipment
CN113298497A (en) Drawing review method and system based on building information model
CN112799722A (en) Command recognition method, device, equipment and storage medium
CN115438984A (en) AI-based big data processing method and server
CN110990055B (en) Pull Request function classification method based on program analysis
CN111966339B (en) Buried point parameter input method and device, computer equipment and storage medium
KR101415528B1 (en) Apparatus and Method for processing data error for distributed system
CN115617756A (en) Method, system, terminal device and storage medium for detecting requirement document
CN113138974B (en) Method and device for detecting database compliance
CN115756486A (en) Data interface analysis method and device
JP2008198123A (en) Fault detection system and fault detection program
CN113868137A (en) Method, device and system for processing buried point data and server
CN116303104B (en) Automated process defect screening management method, system and readable storage medium
CN113704122B (en) UI (user interface) automatic test system and method based on standard interface
CN112882721B (en) Software package compiling method and device
CN111625582B (en) Data warehouse system
KR101900026B1 (en) Cross-validation system for mobile forensic solution that can prevent false detection and improve integrity
CN115185915A (en) Data sharing processing method and system based on Internet and cloud platform

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination