CN117875885A

CN117875885A - Project declaration data processing method, device, equipment and storage medium

Info

Publication number: CN117875885A
Application number: CN202311868757.8A
Authority: CN
Inventors: 黄倪莎; 王振; 朱艳秋; 汪冬雪; 刘江; 张友国
Original assignee: Digital Anhui Co ltd; Iflytek Information Technology Co Ltd
Current assignee: Digital Anhui Co ltd; Iflytek Information Technology Co Ltd
Priority date: 2023-12-28
Filing date: 2023-12-28
Publication date: 2024-04-12

Abstract

The application provides a project declaration data processing method, a device, equipment and a storage medium, wherein the method comprises the following steps: acquiring an item declaration file corresponding to an item to be checked; based on preset auditing dimensions and auditing strategies corresponding to the auditing dimensions of each item, auditing reporting information corresponding to the auditing dimensions of each item in an item application file; the auditing strategies corresponding to the auditing dimensions of each item are determined based on auditing requirements of the item to be audited; and generating project audit reports based on audit results of the reporting information corresponding to each project audit dimension. The method and the device are used for solving the problems of long time consumption, low efficiency and poor accuracy generated when project reporting and auditing work is carried out in the prior art, and realizing the automatic, rapid and accurate auditing of the project reporting book.

Description

Project declaration data processing method, device, equipment and storage medium

Technical Field

The present invention relates to the field of data processing technologies, and in particular, to a method, an apparatus, a device, and a storage medium for processing project declaration data.

Background

In the technical field of project declaration, because of the problems of large difference in project field, complex data types and more redundant data, manual auditing of project declaration books is time-consuming. In order to solve the problem of time consumption of manual auditing, the prior art utilizes an artificial intelligence (Artificial Intelligence, AI for short) technology to extract information of project declaration books so as to assist manual auditing and improve auditing efficiency.

However, in the current project declaration and audit work, only the artificial intelligence technology is used for extracting information of the project declaration, and the whole audit of the project declaration is mainly finished by manpower, so that the problems of long time consumption, low efficiency and poor accuracy remain in the audit of the whole project declaration.

Disclosure of Invention

The application provides a project declaration data processing method, device, equipment and storage medium, which are used for solving the problems of long time consumption, low efficiency and poor accuracy generated when project declaration auditing work is carried out in the prior art, and realizing the automatic, rapid and accurate auditing of a project declaration book.

According to a first aspect of an embodiment of the present application, there is provided an item declaration data processing method, including:

Acquiring an item declaration file corresponding to an item to be checked;

based on preset auditing dimensions and auditing strategies corresponding to the auditing dimensions of each item, auditing declaration information corresponding to the auditing dimensions of each item in the item application file;

the auditing strategies corresponding to the auditing dimensions of each item are determined based on auditing requirements of the item to be audited;

and generating project audit reports based on audit results of the reporting information corresponding to each project audit dimension.

According to the method for processing project declaration data provided in the first aspect of the present application, the auditing of declaration information corresponding to each project audit dimension in the project application file is performed based on preset audit dimensions of each project and audit policies corresponding to each project audit dimension, including:

based on a first project audit dimension and an audit policy corresponding to the first project audit dimension, auditing declaration information corresponding to the first project audit dimension in the project application file;

and when the reporting information corresponding to the first project audit dimension passes, auditing the reporting information corresponding to the second project audit dimension in the project application file based on the second project audit dimension and an audit strategy corresponding to the second project audit dimension.

According to the project declaration data processing method provided in the first aspect of the present application, based on a project audit dimension and an audit policy corresponding to the project audit dimension, audit is performed on declaration information corresponding to the project audit dimension in the project application file, including:

extracting declaration information corresponding to the project audit dimension from the project application file;

and auditing the reporting information corresponding to the project audit dimension based on the audit policy corresponding to the project audit dimension.

According to the project declaration data processing method provided in the first aspect of the present application, the auditing of declaration information corresponding to a project audit dimension is performed based on an audit policy corresponding to the project audit dimension, including:

generating an audit instruction comprising audit strategies corresponding to the project audit dimension and reporting information corresponding to the project audit dimension;

inputting the auditing instruction into a pre-trained large language model, so that the large language model can audit the reporting information corresponding to the item auditing dimension in the auditing instruction according to the auditing strategy corresponding to the item auditing dimension in the auditing instruction.

According to the project declaration data processing method provided in the first aspect of the application, the project audit dimension comprises: a project necessity dimension, a project realizability dimension, a project rationality dimension, and a project integrity dimension;

The auditing sequence of the project auditing dimension comprises the following steps: the auditing priority of the project necessity dimension is greater than the auditing priority of the project realizability dimension, the auditing priority of the project realizability dimension is greater than the auditing priority of the project rationality dimension, and the auditing priority of the project rationality dimension is greater than the auditing priority of the project integrity dimension.

According to the method for processing project declaration data provided in the first aspect of the present application, when the project audit dimension includes the project necessity dimension, based on an audit policy corresponding to the project necessity dimension, the method for processing the declaration information corresponding to the project necessity dimension includes:

extracting construction basis information from first project information, wherein the first project information comprises declaration information corresponding to the project necessity dimension;

determining whether a construction basis file corresponding to the construction basis information exists or not;

and under the condition that the construction basis file exists, auditing the first project information based on the construction basis file.

According to the project declaration data processing method provided in the first aspect of the application, the project realizability dimension includes: project construction intensive dimension, project data sharing dimension, project requirement definiteness dimension and project scheme feasibility dimension;

Under the condition that the project audit dimension comprises the project realizability dimension, auditing the declaration information corresponding to the project realizability dimension based on an audit policy corresponding to the project realizability dimension comprises the following steps:

respectively extracting project construction information corresponding to the project construction intensive dimension, data sharing information corresponding to the project data sharing dimension, project requirement information corresponding to the project requirement definiteness dimension and project feasibility information corresponding to the project scheme feasibility dimension from second project information, wherein the second project information comprises declaration information corresponding to the project realizability dimension;

and respectively auditing the project construction information, the data sharing information, the project demand information and the project feasibility information based on the auditing strategies corresponding to the project realizability dimension.

According to the project declaration data processing method provided in the first aspect of the present application, when the project audit dimension includes a project rationality dimension, audit is performed on declaration information corresponding to the project rationality dimension based on an audit policy corresponding to the project rationality dimension, including:

Extracting project resource information corresponding to the project rationality dimension from third project information, wherein the third project information comprises declaration information corresponding to the project rationality dimension;

and auditing the project resource information based on the auditing strategies corresponding to the project rationality dimensions.

According to the project declaration data processing method provided in the first aspect of the present application, when the project audit dimension includes the project integrity dimension, audit is performed on declaration information corresponding to the project integrity dimension based on an audit policy corresponding to the project integrity dimension, including:

extracting project design information corresponding to the project integrity dimension from fourth project information, wherein the fourth project information comprises declaration information corresponding to the project integrity dimension;

and auditing the project design information based on the auditing strategies corresponding to the project integrity dimensions.

According to the project declaration data processing method provided in the first aspect of the present application, based on an audit policy corresponding to a project audit dimension, audit is performed on declaration information corresponding to the project audit dimension, including:

vectorizing reporting information corresponding to the project auditing dimension to obtain a reporting information vector;

Searching a reporting information vector matched with the reporting information vector from a preset project reporting vector library; the project reporting vector library comprises at least one reporting information vector of each project auditing dimension corresponding to the project that is audited;

and when the reporting information vector matched with the reporting information vector is retrieved from the project reporting vector library, determining that the reporting information corresponding to the project auditing dimension passes.

According to a second aspect of the embodiments of the present application, there is provided an item declaration data processing apparatus, including:

the acquisition module is used for acquiring an item declaration file corresponding to the item to be checked;

the auditing module is used for auditing the reporting information of each item auditing dimension corresponding to the item auditing dimension in the item application file based on preset auditing dimensions and auditing strategies corresponding to each item auditing dimension;

the generation module is used for generating project audit reports based on audit results of reporting information corresponding to each project audit dimension.

According to a third aspect of embodiments of the present application, there is provided an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the method for processing project declaration data according to any one of the above-mentioned methods when executing the program.

According to a fourth aspect of embodiments of the present application, there is provided a non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements a method of item declaration data processing as described in any of the above.

The embodiment of the application provides a method, a device, equipment and a storage medium for processing project declaration data, which are implemented by acquiring a project declaration file corresponding to a project to be checked; based on preset auditing dimensions and auditing strategies corresponding to the auditing dimensions of each item, auditing reporting information corresponding to the auditing dimensions of each item in an item application file; the auditing method comprises the steps that each item auditing dimension and the auditing strategy corresponding to each item auditing dimension are determined based on auditing requirements of the item to be audited, and accordingly, the auditing of each item auditing dimension of the item reporting file is automatically carried out according to the auditing requirements of the item to be audited; furthermore, based on the auditing results of the reporting information corresponding to each item auditing dimension, the item auditing report is generated, so that the whole auditing process and the item auditing report generating process do not need manual operation, are quick, convenient and high in accuracy, and effectively solve the problems of long time consumption, low efficiency and poor accuracy caused by manual auditing of the item reporting file in the prior art.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present application, and that other drawings may be obtained according to the provided drawings without inventive effort to a person skilled in the art.

FIG. 1 is a schematic flow chart of a method for processing project declaration data provided in the present application;

FIG. 2 is a second flow chart of the project declaration data processing method provided in the present application;

FIG. 3 is a third flow chart of the project declaration data processing method provided in the present application;

FIG. 4 is a specific dimension illustration of project construction intensive dimensions provided herein;

FIG. 5 is a flowchart of a method for processing project declaration data provided in the present application;

FIG. 6 is a fifth flow chart of the project declaration data processing method provided in the present application;

FIG. 7 is a flowchart of a method for processing project declaration data provided in the present application;

FIG. 8 is a flow chart of a method for processing project declaration data provided in the present application;

FIG. 9 is a flowchart eighth of the project declaration data processing method provided in the present application;

FIG. 10 is a specific dimension illustration of an item provided herein requiring an explicit dimension;

FIG. 11 is a flowchart illustrating a method for processing project declaration data provided in the present application;

FIG. 12 is a schematic flow chart of a method for processing project declaration data provided in the present application;

FIG. 13 is a flowchart of an eleventh item declaration data processing method provided herein;

FIG. 14 is a flowchart of a method for processing project declaration data provided in the present application;

FIG. 15 is a flowchart of a method for processing project declaration data provided in the present application;

FIG. 16 is a flowchart of a method for processing project declaration data provided in the present application;

FIG. 17 is a flowchart of a method for processing project declaration data provided herein;

FIG. 18 is a flowchart of a method for processing project declaration data provided herein;

FIG. 19 is a flowchart of a method for processing project declaration data provided herein;

FIG. 20 is a flowchart of a method for processing project declaration data provided herein;

FIG. 21 is a schematic diagram of a project declaration data processing apparatus provided herein;

fig. 22 is a schematic structural diagram of an electronic device provided in the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

In order to clearly illustrate the present application, further problems are described below with respect to the auditing of project declaration data in the prior art.

In the current project declaration and audit work, even if the project declaration is subjected to information extraction by using an artificial intelligence technology, certain defects exist.

For example, the element information extraction technology in the prior art is not flexible enough, and the extracted element information has poor effect. Therefore, there is a need to improve the effect of extracting element information by constantly maintaining and developing the prior art. However, continuous maintenance and development lead to redundancy of the extraction technology, so that the extraction time is reduced, and the redundancy of the extraction technology leads to entanglement of effects, so that the accuracy of element information extraction is reduced. Further, the accuracy of the final project declaration is poor.

Exemplary implementation Environment

The project declaration data processing method is applicable to various projects, such as engineering projects, natural science projects, mathematics and computer science projects, social science projects, environment and resource projects, industry and energy projects, medical and health projects and the like.

The method and the device can audit the project declaration book for various projects.

Exemplary method

The embodiment of the application provides a project declaration data processing method which can be applied to intelligent terminals, such as mobile phones, computers, tablets and the like, and also can be applied to servers. The method is applied to a server as an example, but the method is merely illustrative and is not intended to limit the scope of the present application. Some other descriptions of the embodiments of the present application are also illustrative, and are not intended to limit the scope of the present application, and are not described in detail below.

As shown in fig. 1, the method includes:

step 101, acquiring an item declaration file corresponding to the item to be checked.

Wherein, different to-be-inspected items correspond to different item declaration templates, and the item declaration file is obtained based on the item declaration model corresponding to the to-be-inspected item.

Wherein, the project declaration file comprises: project name and project specific content.

Specifically, it is also necessary to acquire presenter information of the project declaration file, a presentation unit, a presentation time, and project names of other projects associated with the projects in the project declaration file.

And 102, auditing declaration information corresponding to each item audit dimension in the item application file based on preset each item audit dimension and audit strategies corresponding to each item audit dimension.

The auditing strategies corresponding to the auditing dimensions of each item are determined based on auditing requirements of the item to be audited.

Wherein the declaration information is derived based on project specific content.

Wherein, different to-be-checked items correspond to different item checking dimensions, and a first corresponding relation between the to-be-checked items and the item checking dimensions is preset.

Wherein, different project audit dimensions correspond to different audit strategies, and a second corresponding relation between the project audit dimensions and the audit strategies is preset.

According to the method and the device, the project application files are automatically audited based on the first corresponding relation and the second corresponding relation, manual participation is not needed, labor cost is saved, and user experience is improved.

And step 103, generating project audit reports based on audit results of reporting information corresponding to each project audit dimension.

Wherein, the auditing result includes: and generating a failing reason when the auditing result is that the auditing is failed, and finally obtaining a project auditing report.

The embodiment of the application provides a project declaration data processing method, which comprises the steps of obtaining a project declaration file corresponding to a project to be checked; based on preset auditing dimensions and auditing strategies corresponding to the auditing dimensions of each item, auditing reporting information corresponding to the auditing dimensions of each item in an item application file; the auditing method comprises the steps that each item auditing dimension and the auditing strategy corresponding to each item auditing dimension are determined based on auditing requirements of the item to be audited, and accordingly, the auditing of each item auditing dimension of the item reporting file is automatically carried out according to the auditing requirements of the item to be audited; furthermore, based on the auditing results of the reporting information corresponding to each item auditing dimension, the item auditing report is generated, so that the whole auditing process and the item auditing report generating process do not need manual operation, are quick, convenient and high in accuracy, and effectively solve the problems of long time consumption, low efficiency and poor accuracy caused by manual auditing of the item reporting file in the prior art.

In a specific embodiment, based on preset auditing dimensions of each item and auditing strategies corresponding to the auditing dimensions of each item, the specific implementation of auditing the reporting information corresponding to the auditing dimensions of each item in the item application file includes:

based on the first project audit dimension and the audit policy corresponding to the first project audit dimension, auditing the reporting information corresponding to the first project audit dimension in the project application file; and when the reporting information corresponding to the first item auditing dimension passes, auditing the reporting information corresponding to the second item auditing dimension in the item application file based on the second item auditing dimension and an auditing strategy corresponding to the second item auditing dimension.

Specifically, the auditing of the project declaration file is performed according to the auditing sequence of each project auditing dimension, and the auditing sequence is also determined based on the auditing requirements of the project to be audited.

Specifically, a current auditing strategy corresponding to the auditing dimension of the current project is obtained; and based on the current auditing policy, auditing the current declaration information corresponding to the auditing dimension of the current project. Under the condition that the current reporting information is checked and passed, determining a next project checking dimension and a next checking strategy corresponding to the next project checking dimension based on the checking sequence of each project checking dimension; based on the next audit policy, auditing the next reporting information corresponding to the next project audit dimension until the last reporting information corresponding to the last project audit dimension passes.

According to the method and the device, under the condition that the reporting information of the corresponding first project audit dimension passes, the reporting information of the second project audit dimension is audited, invalid audit of the project application files is avoided, and audit efficiency of the project application files is effectively improved.

In a specific embodiment, based on preset auditing dimensions of each item and auditing strategies corresponding to the auditing dimensions of each item, auditing reporting information corresponding to the auditing dimensions of each item in an item application file includes: for any item auditing dimension, auditing the reporting information corresponding to the item auditing dimension in the item application file based on the item auditing dimension and the auditing policy corresponding to the item auditing dimension, the specific implementation includes:

extracting declaration information corresponding to the project audit dimension from the project application file; and auditing the reporting information corresponding to the project audit dimension based on the audit policy corresponding to the project audit dimension.

In order to ensure auditing efficiency, the method extracts the declaration information corresponding to the auditing dimension of the project from the project application file, and audits the extracted declaration information, so that the auditing data quantity is reduced, and the auditing speed is improved.

In a specific embodiment, based on an audit policy corresponding to an item audit dimension, a specific implementation of auditing declaration information corresponding to the item audit dimension includes:

generating an audit instruction comprising audit strategies corresponding to the project audit dimension and reporting information corresponding to the project audit dimension; inputting the auditing instruction into a pre-trained large language model, so that the large language model can audit the reporting information corresponding to the item auditing dimension in the auditing instruction according to the auditing strategy corresponding to the item auditing dimension in the auditing instruction.

According to the method and the device, the pre-trained large language model is utilized for auditing the declaration information, so that the auditing efficiency of the declaration information can be effectively improved.

In one particular embodiment, the project audit dimension includes: a project necessity dimension, a project realizability dimension, a project rationality dimension, and a project integrity dimension; the auditing order of the project auditing dimension includes: the auditing priority of the project necessity dimension is greater than the auditing priority of the project realizability dimension, the auditing priority of the project realizability dimension is greater than the auditing priority of the project rationality dimension, and the auditing priority of the project rationality dimension is greater than the auditing priority of the project integrity dimension.

Specifically, the item necessity dimension, the item rationality dimension, and the item integrity dimension are equivalent to switch items, and when any one or more audits are not passed, the audit of the item declaration file is not passed.

Next, the present embodiment is schematically illustrated by fig. 2:

step 201, determining whether the reporting information corresponding to the item necessity dimension passes the audit, if so, executing step 202, otherwise, executing step 206.

Step 202, determining whether the reporting information corresponding to the item realizability dimension passes the audit, if so, executing step 203, otherwise, executing step 206.

Step 203, determining whether the reporting information corresponding to the item rationality dimension passes the audit, if so, executing step 204, otherwise, executing step 206.

Step 204, determining whether the reporting information corresponding to the item integrity dimension passes the audit, if so, executing step 205, otherwise, executing step 206.

Step 205, determining that the project declaration file is approved.

Step 206, determining that the project declaration file audit is not passed.

According to the method and the device, the project declaration files are audited based on the audit sequence of the project audit dimension, so that invalid audit of the project application files is avoided, and the audit efficiency of the project application files is effectively improved.

In a specific embodiment, auditing the reporting information corresponding to the project audit dimension based on the audit policy corresponding to the project audit dimension includes: when the project audit dimension includes the project necessity dimension, audit is performed on the declaration information corresponding to the project necessity dimension based on an audit policy corresponding to the project necessity dimension, and the concrete implementation includes:

extracting construction basis information from the first item information; determining whether a construction basis file corresponding to the construction basis information exists or not; and under the condition that the construction basis file exists, auditing the first project information based on the construction basis file.

The first item information comprises declaration information corresponding to the item necessity dimension.

Specifically, a file library is pre-created, and at least one construction basis file corresponding to the checked item is pre-stored in the file library. Searching the extracted construction basis information in a file library, and determining whether a construction basis file corresponding to the construction basis information can be obtained; under the condition that the construction basis file is determined to be obtained, auditing the first project information based on the construction basis file; and under the condition that the construction basis file cannot be obtained, determining that the audit of the declaration information corresponding to the project necessity dimension is not passed.

Specifically, based on the construction basis file, the specific implementation of auditing the first project information includes:

acquiring construction basis content of a construction basis file; calculating the similarity between the construction basis information and the construction basis content; under the condition that the similarity is larger than the preset similarity, determining that the reporting information corresponding to the item necessity dimension passes the audit; and under the condition that the similarity is smaller than or equal to the preset similarity, determining that the audit of the declaration information corresponding to the item necessity dimension is not passed.

Then, the calculation mode of the similarity can be used for determining whether a construction basis file exists in the file library; under the condition that the similarity is larger than the preset similarity, determining that a construction basis file exists in a file library, and determining that the reporting information auditing corresponding to the project necessity dimension passes; and under the condition that the similarity is smaller than or equal to the preset similarity, if the fact that the construction basis file does not exist in the file library is determined, determining that the audit of the declaration information corresponding to the project necessity dimension is not passed.

Next, the present embodiment is schematically illustrated by fig. 3:

step 301, extracting a construction basis name from the first item information.

Step 302, determining whether the construction basis name is extracted, if yes, executing step 303, otherwise, executing step 308.

The construction basis information comprises construction basis names.

Step 303, based on the construction basis name from the file library, determining whether the retrieval basis file can be retrieved from the file library, if so, executing step 304, otherwise, executing step 308.

Step 304, acquiring contents referenced by the file and project construction contents in the first project information.

Wherein, the construction basis content includes: depending on the content referenced by the file, i.e., depending on the content included in the file.

Wherein, the construction basis information further includes: project construction content.

Step 305, comparing the similarity between the content referenced by the file and the project construction content.

Step 306, determining whether the similarity is greater than a preset similarity, if so, executing step 307, otherwise, executing step 308.

Step 307, determining that the reporting information corresponding to the item necessity dimension is approved.

Step 308, determining that the reporting information audit corresponding to the item necessity dimension is not passed.

Specifically, the weight of the audit indexes of the item necessity dimension can be set, and the audit indexes of the item necessity dimension comprise: see in particular table 1, based on the file presence indicator and based on the file validity indicator (i.e., based on the similarity between the content referenced by the file and the project construction content being greater than a predetermined similarity).

Table 1 item necessity dimension audit indicator weight table

The weights of the audit indexes in table 1 are illustrated, and are not used for limiting the application, and the user can set the audit indexes according to the actual needs of the user.

Specifically, if the basis file can be retrieved from the file library, outputting "1"; if the basis file cannot be retrieved from the file library, outputting 0; if the similarity between the content quoted by the file and the project construction content is greater than the preset similarity, outputting a 1; and outputting 0 according to the similarity of the content referenced by the file and the project construction content being smaller than or equal to the preset similarity.

Specifically, the auditing result of the item necessity dimension can be obtained by the formula (1):

audit results of project necessity dimension = 50% from file presence indicator + 50%....................................... From file validity indicator (1)

According to the method and the device, firstly, the project necessity dimension is audited, and only if the project exists in the necessary condition, the audit dimension of other projects can be audited continuously.

In one particular embodiment, the project realizability dimension includes: project construction intensive dimension, project data sharing dimension, project need definition dimension and project scheme feasibility dimension.

Based on the auditing policy corresponding to the project auditing dimension, auditing the reporting information corresponding to the project auditing dimension comprises: under the condition that the project audit dimension comprises the project realizability dimension, auditing the declaration information corresponding to the project realizability dimension based on an audit policy corresponding to the project realizability dimension, wherein the concrete implementation comprises the following steps:

respectively extracting project construction information corresponding to project construction intensive dimension, data sharing information corresponding to project data sharing dimension, project demand information corresponding to project demand definition dimension and project feasibility information corresponding to project scheme feasibility dimension from second project information; and respectively auditing the project construction information, the data sharing information, the project demand information and the project feasibility information based on the auditing strategies corresponding to the project realizability dimension.

The second item information comprises declaration information corresponding to the item realizability dimension.

Specifically, under the condition that the project construction information is determined to have project hardware facilities, project software facilities and project network facilities corresponding to the auditing requirements, determining that the project construction information is audited; under the condition that the data sharing platform corresponding to the auditing requirement exists in the data sharing information, determining that the data sharing information auditing is passed; under the condition that business requirements, functional requirements, performance requirements, system integration requirements, data requirements and operation requirements corresponding to auditing requirements exist in project requirement information, the project requirement information is determined to pass auditing; and under the condition that the project hardware architecture and the project software architecture corresponding to the auditing requirements exist in the project feasibility information, determining that the project feasibility information auditing is passed.

Specifically, as shown in fig. 4, the project construction intensive dimension includes: a general infrastructure sub-dimension, a non-secret-related business private network sub-dimension, a public application support capability sub-dimension, and a mobile terminal application sub-dimension.

The auditing of the project construction intensive dimension is the auditing of the general infrastructure sub-dimension, the non-secret-related business private network sub-dimension, the public application supporting capability sub-dimension and the mobile terminal application sub-dimension. The method specifically and mainly comprises the following steps: checking whether a newly built machine room, a capacity expansion machine room and a data center exist; whether a private network of the confidential business is newly built; whether there is common application support capability, application, etc.

Specifically, a specific audit process for the generic infrastructure sub-dimension is shown in FIG. 5:

step 501, first sub-information corresponding to a hardware device purchase estimation list is extracted from the second item information.

Wherein, project construction information includes: first sub information.

Step 502, determining whether the first sub-information has a relevant description of the machine room, if so, executing step 503 and step 507, otherwise, executing step 504.

Step 503, determining whether a new machine room exists in the first sub-information, if so, executing step 505, otherwise, executing step 506.

And step 504, outputting an audit result for indicating that the machine room does not exist.

And 505, outputting an auditing result for indicating the existence of the newly built machine room.

And step 506, outputting an audit result for indicating that the newly built machine room does not exist.

Step 507, determining whether there is a capacity expansion machine room in the first sub-information, if yes, executing step 508, otherwise, executing step 509.

And step 508, outputting an audit result for indicating the existence of the capacity expansion machine room.

And 509, outputting an audit result for indicating that the capacity expansion machine room does not exist.

Step 510, determining whether the first sub-information has a description about the data center, if so, performing step 511 and step 515, otherwise, performing step 514.

Step 511, determining whether a new data center exists in the first sub-information, if so, executing step 512, otherwise, executing step 513.

And step 512, outputting an audit result for indicating the existence of the new data center.

And step 513, outputting an audit result for indicating that the newly built data center does not exist.

And step 514, outputting an audit result for indicating that the data center does not exist.

Step 515, determining whether there is a capacity expansion data center in the first sub-information, if yes, executing step 516, otherwise, executing step 517.

And step 516, outputting an audit result for indicating that the capacity expansion data center exists.

And 517, outputting an audit result for indicating that the capacity expansion data center does not exist.

Further, under the condition that the new machine room exists in the first sub-information, determining whether the new machine room meets the preset requirement, if so, outputting an audit result for indicating the existence of the new machine room, otherwise,

and determining that the general infrastructure sub-dimension audit is not passed.

Specifically, a specific auditing process of the non-confidential business private network sub-dimension is shown in fig. 6:

step 601, extracting second sub-information corresponding to the hardware device purchase estimation list and the cloud resource lease fee list from the second item information.

Wherein, project construction information includes: and second sub information.

Step 602, determining whether there is a related description of the private network of the non-confidential business in the second sub-information, if yes, executing step 603, otherwise, executing step 604.

Step 603, determining whether the private network of the non-confidential business meets the preset requirement, if so, executing step 605, otherwise, executing step 606.

Wherein, the preset requirement is in accordance with the special requirements of specific organizations, institutions and even countries.

Step 604, outputting an audit result for indicating non-secret-related information.

Step 605, outputting an audit result for indicating secret related.

Step 606, outputting an audit result indicating that the generic infrastructure sub-dimension audit is not passed.

Specifically, a specific audit process for the common application support capability sub-dimension is shown in FIG. 7:

step 701, extracting third sub-information corresponding to the product software purchase estimation list and the software development estimation list from the second project information.

Wherein, project construction information includes: and third sub information.

Step 702, determining whether a preset component exists in the third information, if yes, executing step 703, otherwise, executing step 704.

The preset components are components in a pre-created component library.

The component is an object after the software method and the data are packaged.

Step 703, outputting an audit result for indicating that the component is repeatedly present.

Step 704, outputting an audit result indicating that the component is repeatedly absent.

Specifically, a specific auditing process of the mobile terminal application sub-dimension is shown in fig. 8:

step 801, extracting third sub-information corresponding to the product software purchase estimation list and the software development estimation list from the second project information.

Step 802, determining whether other application software except the preset application software exists in the third information, if yes, executing step 803, otherwise, executing step 804.

The preset application software is application software corresponding to a specific organization, organization and even country.

Step 803, outputting an audit result for indicating that new application software exists.

Step 804, outputting the auditing result for indicating that no new application software exists.

Specifically, the weight of the audit indicator of the item realizability dimension may be set, where the audit indicator of the item realizability dimension includes: machine room presence indicator for the general infrastructure sub-dimension, data center presence indicator for the general infrastructure sub-dimension, non-confidential private network presence indicator for the non-confidential private network sub-dimension, duplicate component presence indicator for the public application support capability sub-dimension, and new application software presence indicator for the mobile terminal application sub-dimension, see table 2 in particular.

Table 2 item Endurance dimension audit indicator weight table

Specifically, if a machine room exists, outputting a '1'; if the machine room does not exist, outputting 0; if the data center exists, outputting '1'; if the data center does not exist, outputting '0'; if the non-secret-related private network exists, outputting '1'; if no non-secret-related private network exists, outputting 0; if a duplicate component exists, outputting a '1'; if no duplicate component exists, outputting '0'; if new application software exists, outputting '1'; and outputting '0' if no new application software exists.

Specifically, the auditing result of the project realizability dimension can be obtained by the formula (2):

auditing results of project realizability dimension = machine room presence indicator =50% + data center presence indicator ×50% + non-secret-related private network presence indicator ×0+repeated component presence indicator ×0+new application presence indicator ×0 … … … … … … … … … (2)

Specifically, the auditing specific process of the data sharing information comprises the following steps:

the auditing of project data shareability dimensions is specifically illustrated schematically by FIG. 9:

step 901, determining whether the data sharing unique identifier can be extracted from the data sharing information, if so, executing step 902, otherwise, executing step 904.

Step 902, determining whether the extracted data sharing unique identifier exists in the unified sharing interaction platform, if yes, executing step 903, otherwise, executing step 904.

The unified sharing interaction platform is a pre-established data interaction platform.

Step 903, outputting an audit result for indicating that data sharing exists.

Step 904, outputting an audit result for indicating that no data sharing exists.

Specifically, the weight of the audit indicator of the item data sharability dimension may be set, where the audit indicator of the item data sharability dimension includes a data sharing presence indicator, see table 3 for details.

Project audit dimension	Auditing index	Weights of audit indicators
			Project data shareability dimension	Data sharing presence indicator	0

Table 3 item data sharing dimension audit indicator weight table

The weights of the audit indexes in table 3 are illustrated, and are not used for limiting the application, and the user can set the audit indexes according to the actual needs of the user.

Specifically, if there is data sharing, output "1"; if there is no data sharing, a "0" is output.

Specifically, the auditing result of the project data sharing dimension can be obtained by the formula (3):

audit results of project data sharing dimension = data sharing presence indicator 0 … … (3)

Specifically, the auditing specific process of the project demand information comprises the following steps:

as shown in fig. 10, the project need specificity dimensions include: a business requirement sub-dimension, a function requirement sub-dimension, a performance requirement sub-dimension, a system integration requirement sub-dimension, a data requirement sub-dimension, a running requirement sub-dimension, and a security requirement sub-dimension.

Specifically, a specific audit process for the business requirement sub-dimension is schematically described by fig. 11:

step 1101, checking whether the project requirement information includes a service boundary, a service mode, a service scale, a service frequency, a system user, a system management user, a user category and a service flow.

Step 1102, determining whether the project requirement information includes a service boundary, if yes, executing step 1103, otherwise, executing step 1104.

Step 1103, outputting an audit result for indicating existence of a service boundary.

Step 1104, outputting auditing results for indicating that no business boundary exists.

Step 1105, determining whether the project requirement information includes a service mode, if so, executing step 1106, otherwise, executing step 1107.

And 1106, outputting an audit result for indicating the existence of the service mode.

Step 1107, outputting the auditing result for indicating that the service mode does not exist.

Step 1108, determining whether the project requirement information includes a service scale, if so, executing step 1109, otherwise, executing step 1110.

In step 1109, an audit result indicating the presence traffic scale is output.

Step 1110, outputting an audit result indicating that no traffic scale exists.

Step 1111, determining whether the item requirement information includes a service frequency, if yes, executing step 1112, otherwise, executing step 1113.

Step 1112, outputting an audit result indicating the frequency of presence services.

Step 1113, outputting an audit result indicating that there is no traffic frequency.

Step 1114 determines if the system user is included in the project requirement information, if so, then step 1115 is performed, otherwise, step 1116 is performed.

Step 1115, outputting an audit result for indicating that the presence system uses the user.

Step 1116, output an audit result indicating that there is no user for the system to use.

Step 1117, determining whether the project requirement information includes a system management user, if so, executing step 1118, otherwise, executing step 1119.

Step 1118, outputting an audit result indicating that the system management user exists.

Step 1119, outputting an audit result indicating that there is no system management user.

Step 1120, determining whether the project requirement information includes a user category, if yes, executing step 1121, otherwise, executing step 1122.

Step 1121, outputting an audit result indicating that a user category exists.

Step 1122, an audit result is output indicating that no user category exists.

Step 1123, determining whether the project requirement information includes a business process, if yes, executing step 1124, otherwise, executing step 1125.

Step 1124, output the audit result indicating the existence of the business process.

Step 1125, output the audit result indicating that no business process exists.

Specifically, a specific audit process for the functional requirements sub-dimension is schematically depicted by FIG. 12:

step 1201, extracting function requirement information corresponding to the function requirement from the project requirement information.

Step 1202, auditing whether the function requirement information includes a function definition, a boundary definition, a user description and a data description.

Step 1203, determining whether the function requirement information includes a function definition, if yes, executing step 1204, otherwise, executing step 1205.

Step 1204, outputting an audit result indicating that the function definition exists.

Step 1205, outputting an audit result indicating that no function definition exists.

Step 1206 determines whether the functional requirement information includes a boundary definition, if so, step 1207 is performed, otherwise, step 1208 is performed.

Step 1207, outputting an audit result indicating that the boundary definition exists.

Step 1208, outputting an audit result indicating that no boundary definition exists.

Step 1209, determining whether the function requirement information includes a user description, if so, executing step 1210, otherwise, executing step 1211.

Step 1210, outputting an audit result indicating the presence of the user description.

Step 1211, outputting an audit result indicating that there is no user description.

Step 1212, determining whether the function requirement information includes a data description, if so, executing step 1213, otherwise, executing step 1214.

Step 1213, outputting an audit result indicating that the data description exists.

Step 1214, outputting an audit result indicating that no data description exists.

Specifically, a specific audit process for the performance requirement sub-dimension is schematically depicted by FIG. 13:

step 1301, extracting performance requirement information corresponding to the performance requirement sub-dimension from the project requirement information.

Step 1302, auditing whether the performance requirement information includes online users, concurrent users, response time and reliability description.

Step 1303, determining whether the performance requirement information includes an online user, if yes, executing step 1304, otherwise, executing step 1305.

In step 1304, an audit result indicating the presence of the online user is output.

Step 1305, outputting an audit result for indicating that the online user does not exist.

Step 1306, determining whether the performance requirement information includes the number of concurrent users, if yes, executing step 1307, otherwise, executing step 1308.

Step 1307, outputting an audit result for indicating that the concurrent user number exists.

Step 1308, outputting an audit result for indicating that the number of concurrent users does not exist.

Step 1309, determining whether the performance requirement information includes a response time, if so, executing step 1310, otherwise, executing step 1311.

Step 1310, outputting an audit result indicating that there is a response time.

Step 1311, outputting an audit result indicating that there is no response time.

Step 1312 determines whether the performance requirement information includes a reliability description, if so, performs step 1313, otherwise, performs step 1314.

Step 1313, outputting an audit result indicating that a reliability description exists.

And step 1314, outputting an audit result indicating that the reliability description does not exist.

Specifically, a specific audit process for the system integration requirements sub-dimension is schematically depicted by fig. 14:

in step 1401, system integration requirement information corresponding to the system integration requirement sub-dimension is extracted from the project requirement information.

Step 1402, auditing whether the system integration requirement information includes an associated system, an integration requirement and an interface requirement.

Step 1403, determining whether the system integration requirement information includes an associated system, if so, executing step 1404, otherwise, executing step 1405.

Step 1404, outputting an audit result indicating the presence of the associated system.

In step 1405, an audit result is output indicating that no associated system exists.

Step 1406, determining whether the system integration requirement information includes an integration requirement, if so, executing step 1407, otherwise, executing step 1408.

Step 1407, outputting an audit result indicating that the integration requirement exists.

Step 1408, outputting an audit result indicating that there is no integration requirement.

Step 1409, determining whether the system integration requirement information includes integration requirement information, if so, executing step 1410, otherwise, executing step 1411.

Step 1410, outputting an audit result indicating that there is integration requirement information.

Step 1411, outputting an audit result indicating that there is no integrated demand information.

Specifically, a specific audit process for the data demand sub-dimension is schematically depicted by FIG. 15:

step 1501 extracts data requirement information corresponding to the data requirement sub-dimension from the project requirement information.

Step 1502 determines a percentage of data requirement information to be described in relation to the data requirement.

Wherein the description related to the data requirement includes: data sources, data types, data amounts, data storage formats, data structures, data requirement files corresponding to data requirement information, and the like.

In step 1503, it is determined whether the percentage is greater than a preset percentage, if yes, step 1504 is executed, otherwise, step 1505 is executed.

Step 1504, outputting an audit result for indicating that the data requirement information exists.

Step 1505, output the audit result indicating that there is no data demand information.

Specifically, a specific audit process for the run requirements sub-dimension is schematically depicted by FIG. 16:

in step 1601, operation requirement information corresponding to the operation requirement sub-dimension is extracted from the project requirement information.

Step 1602 determines whether the description of the software environment, the hardware environment, and the link environment is included in the operation requirement information, if so, step 1603 is executed, otherwise, step 1604 is executed.

Step 1603, outputting an audit result indicating that the operation requirement information exists.

Step 1604, outputting an audit result indicating that no operational need information exists.

Specifically, a specific audit process for the security requirements sub-dimension is schematically depicted by fig. 17:

step 1701, extracting security requirement information corresponding to the security requirement sub-dimension from the project requirement information.

Step 1702, determining whether security protection information is included in the security requirement, if so, executing step 1703, otherwise, executing step 1704.

Wherein the security protection information includes: network protection level requirements, servers, firewalls, viruses, cryptographic applications, cryptographic evaluations, listings corresponding to cryptographic applications and cryptographic evaluations, and the like.

And 1703, outputting an auditing result for indicating the existence of the safety protection information.

Step 1704, outputting an audit result for indicating that the security protection information does not exist.

Specifically, the weight of the audit indexes of the item requiring the definition dimension can be set, and the audit indexes of the item requiring the definition dimension comprise: the present invention relates to a method for determining a service boundary presence index, a service pattern presence index, a service frequency presence index, a system use user presence index, a system management user presence index, a user category presence index, a function definition presence index, a boundary definition presence index, a user description presence index, a data description presence index, an online user presence index, a concurrent user presence index, a response time presence index, a reliability description presence index, an associated system presence index, an integration requirement presence index, an interface requirement presence index, a data requirement information presence index, an operation requirement information presence index, and a security requirement information presence index, and is specifically described in table 4.

Table 4 items audit metrics weight table requiring a dimension of specificity

The weights of the audit indexes in table 4 are illustrated, and are not used for limiting the application, and the user can set the audit indexes according to the actual needs of the user.

Specifically, for each audit indicator, if the audit indicator is true, outputting a "1"; if the audit index is not established, outputting '0'.

Specifically, the auditing result of the item requiring the explicit dimension can be obtained by the formulas (4) to (10):

auditing result of service demand sub-dimension = service boundary presence indicator 20% + service mode presence indicator 20% + service frequency presence indicator 20% + system usage user presence indicator 15% + system management user presence indicator 15% + user category presence indicator 10%............................... (4)

Audit result of function requirement sub-dimension = function definition presence indicator x 70% + boundary definition presence indicator x 10% + user description presence indicator x 10% + data description presence indicator x 10% > (5)

Auditing results for performance requirements sub-dimension = online user presence indicator x 25% + concurrent user presence indicator x 25% + response time presence indicator x 25% + reliability description presence indicator x 25%, (6

Auditing result of system integration requirement sub-dimension = associated system presence indicator 30% + integration requirement presence indicator 30% + interface requirement presence indicator 40%........................................... (7)

Audit results of run requirements sub-dimension=0 … … … … … … … … … … … … … (8)

Audit results of security requirements sub-dimension=0 … … … … … … … … … … … … … (9)

Audit results of project need definiteness dimension = audit results of business requirement sub-dimension + audit results of function requirement sub-dimension + audit results of performance requirement sub-dimension + audit results of system integration requirement sub-dimension + audit results of running requirement sub-dimension + audit results of security requirement sub-dimension. (10)

Specifically, a specific process of auditing item feasibility information is shown in fig. 18:

step 1801, extracting project hardware architecture, project software architecture and project software development information from the project feasibility information.

Step 1802, determining whether the project hardware architecture includes a design description of a system logic architecture, a system function architecture, and a deployment implementation architecture, if yes, executing step 1803, otherwise, executing step 1804.

Step 1803, outputting an audit result for indicating that the project hardware architecture exists.

Step 1804, outputting an audit result for indicating that no project hardware architecture exists.

Step 1805, determining whether the project software architecture includes a device connection diagram, a system structure topology diagram, a network topology diagram and a physical architecture diagram, if yes, executing step 1806, otherwise, executing step 1807.

Step 1806, outputting an audit result for indicating that the project software architecture exists.

Step 1807, outputting an audit result for indicating that the project software architecture does not exist.

Step 1808, determining whether the project software development information and the information in the software detail list are consistent, if yes, executing step 1809, otherwise, executing step 1810.

Step 1809, outputting an audit result for indicating that the project software development information exists.

Step 1810, outputting an audit result indicating that no project software development information exists.

Specifically, the weight of the audit indicator of the feasibility dimension of the project scheme can be set, and the audit indicator of the feasibility dimension of the project scheme comprises: the existence index of the project hardware architecture, the existence index of the project software architecture and the existence index of the project software development information can be seen in table 5.

Table 5 item Enabled index weight table for feasibility dimension of solution

The weights of the audit indexes in table 5 are illustrated, and are not used for limiting the application, and the user can set the audit indexes according to the actual needs of the user.

Specifically, the auditing result of the feasibility dimension of the project scheme can be obtained by the formula (11):

auditing result of project plan feasibility dimension=project hardware architecture existence index 0+project software development information existence index 0 … … … … … … … (11)

In a specific embodiment, auditing the reporting information corresponding to the project audit dimension based on the audit policy corresponding to the project audit dimension includes: under the condition that the project audit dimension comprises the project rationality dimension, auditing the declaration information corresponding to the project rationality dimension based on the audit policy corresponding to the project rationality dimension, wherein the concrete implementation comprises the following steps:

extracting project resource information corresponding to the project rationality dimension from the third project information; and auditing the project resource information based on the auditing strategies corresponding to the project rationality dimensions.

The third item information comprises declaration information corresponding to the item rationality dimension.

Wherein the project resource information includes: project investment approximation, project investment estimation, project investment amount, etc.

Specifically, the investment approximation (fund source, compilation basis) is subjected to verification of missing items, and the project investment estimation and the project investment amount are subjected to consistency check. The method is mainly used for auditing by comparing the fund source, the compiling basis, the total investment amount of the project, the project investment estimation detailed item amount and the item amount of each part in the project application file.

Specifically, a specific audit process for the project rationality dimension is shown in FIG. 19:

step 1901, extracting project resource information corresponding to the project rationality dimension from the third project information.

Step 1902, determining whether the project resource information includes a description of a funding source and a compilation basis, if so, executing step 1903, otherwise, executing step 1904.

Step 1903, outputting an audit result indicating that there is a funding source and a compilation basis.

In step 1904, an audit result is output indicating that there is no funding source and compilation basis.

Step 1905, determining whether the total investment amount of the project in the project resource information is equal to the sum of the amounts of the various items, if yes, executing step 1906, otherwise, executing step 1907.

Step 1906, outputting an audit result indicating that the first logic is correct.

Step 1907, outputting an audit result indicating the first logic error.

Step 1908, determining whether the item investment estimation detailed item amount and the item amount at each point are consistent, if yes, executing step 1909, otherwise, executing step 1910.

Step 1909, outputting an audit result indicating that the second logic is correct.

Step 1910, outputting an audit result indicating the second logical error.

Specifically, the weight of the audit indexes of the item rationality dimension can be set, and the audit indexes of the item rationality dimension comprise: the investment profile presence indicator, the investment estimate compliance indicator (equivalent to the first logical correct) and the cost compliance indicator (equivalent to the second logical correct), see in particular table 6.

Table 6 audit indicator weight table for item rationality dimension

The weights of the audit indexes in table 6 are illustrated, and are not used for limiting the application, and the user can set the audit indexes according to the actual needs of the user.

Specifically, the auditing result of the project plan feasibility dimension can be obtained by the formula (12):

auditing outcome for project plan feasibility dimension = investment profile presence index x 0+ investment estimate compliance index x 0+ cost compliance index x 0 … … … … … … … … … … … … … … … (12)

In a specific embodiment, auditing the reporting information corresponding to the project audit dimension based on the audit policy corresponding to the project audit dimension includes: under the condition that the project audit dimension comprises the project integrity dimension, auditing the declaration information corresponding to the project integrity dimension based on an audit policy corresponding to the project integrity dimension, wherein the concrete implementation comprises the following steps:

extracting project design information corresponding to the project integrity dimension from the fourth project information; and auditing the project design information based on the auditing strategy corresponding to the project integrity dimension.

The fourth item information comprises declaration information corresponding to the item integrity dimension.

Wherein the project design information includes: project construction period, project implementation progress, project beneficial effect, project evaluation index analysis information, project related policy information, project related technology information, and the like.

Specifically, a specific audit process for the item integrity dimension is shown in FIG. 20:

step 2001, extracting a project declaration list from the project design information.

Step 2002, determining whether the project declaration directory list includes implementation progress, benefit and evaluation index analysis, construction scheme and technical scheme, if yes, executing step 2003, otherwise, executing step 2004.

Step 2003, outputting the auditing result for indicating the scheme is complete.

Step 2004, outputting an audit result indicating that the solution is incomplete.

Specifically, the weight of the audit indicator of the item integrity dimension may also be set, where the audit indicator of the item integrity dimension includes: protocol integrity index, see in particular table 7.

Project audit dimension	Auditing index	Weights of audit indicators
			Item integrity dimension	Scheme integrity index	100％

Table 7 audit metrics weight table for item integrity dimension

The weights of the audit indexes in table 7 are illustrated, and are not used for limiting the application, and the user can set the audit indexes according to the actual needs of the user.

Specifically, the audit result of the item integrity dimension can be obtained by equation (13):

audit results for project integrity dimension = protocol integrity index 100%........... (13)

According to the method and the device, the auditing accuracy of the item to be audited is guaranteed by auditing the item application files in each item auditing dimension, and the whole process is automatically carried out without artificial participation, so that the labor cost is reduced, and the user experience is improved.

In a specific embodiment, auditing the reporting information corresponding to the project audit dimension based on the audit policy corresponding to the project audit dimension includes:

the reporting information corresponding to the audit dimension of the vectorization project is obtained; searching a reporting information vector matched with the reporting information vector from a preset project reporting vector library; and when the reporting information vector matched with the reporting information vector is retrieved from the project reporting vector library, determining that the reporting information corresponding to the project auditing dimension passes.

The project declaration vector library comprises at least one declaration information vector of which the audited project corresponds to each project audit dimension.

Specifically, a reporting vector library is created in advance to audit reporting information corresponding to each item audit dimension.

Specifically, reporting information corresponding to the project audit dimension is converted into a vector capable of expressing the semantics of the reporting information, and the reporting information corresponding to the project audit dimension is audited based on the obtained vector so as to improve the auditing speed of the project application file.

Specifically, the method and the device can audit the declaration information corresponding to the project audit dimension based on a vectorization processing mode, and can audit the declaration information corresponding to the project audit dimension based on a prediction mode of a large language model; and auditing the reporting information corresponding to the project auditing dimension can be performed based on the vectorization processing mode and the prediction mode of the large language model.

In a specific embodiment, in order to increase the auditing speed of the project declaration file, the project declaration file is split according to the project declaration template, and key information is extracted from the split project declaration file to obtain key project information, and the subsequent declaration information corresponding to the project auditing dimension is operated on the key project information.

Specifically, when auditing declaration information corresponding to project audit dimensions is performed in a vectorization processing mode, key project information needs to be vectorized, and the key project information after vectorization processing is directly audited.

The auditing process of the whole project application file and the generating process of the project audit report are automatically executed without manual operation, so that the problems of long time consumption, low efficiency and poor accuracy caused by the need of manually auditing the project application file in the prior art are effectively solved, and the auditing of the project application file is automatically, rapidly and accurately completed.

Exemplary apparatus

Correspondingly, referring to fig. 21, the embodiment of the application also provides an item declaration data processing device.

The acquisition module 2101 is used for acquiring an item declaration file corresponding to the to-be-checked item;

the auditing module 2102 is used for auditing the reporting information corresponding to each item auditing dimension in the item application file based on preset auditing dimensions and auditing strategies corresponding to each item auditing dimension;

the generating module 2103 is configured to generate an item audit report based on audit results of reporting information corresponding to each item audit dimension.

In a specific embodiment, the auditing module 2102 is specifically configured to audit, based on a first project audit dimension and an audit policy corresponding to the first project audit dimension, reporting information corresponding to the first project audit dimension in the project application file; and when the reporting information corresponding to the first item auditing dimension passes, auditing the reporting information corresponding to the second item auditing dimension in the item application file based on the second item auditing dimension and an auditing strategy corresponding to the second item auditing dimension.

In one embodiment, the auditing module 2102 is specifically configured to extract declaration information corresponding to a project auditing dimension from the project application file; and auditing the reporting information corresponding to the project audit dimension based on the audit policy corresponding to the project audit dimension.

In a specific embodiment, the auditing module 2102 is specifically configured to generate an auditing instruction including an auditing policy corresponding to an item auditing dimension and reporting information corresponding to the item auditing dimension; inputting the auditing instruction into a pre-trained large language model, so that the large language model can audit the reporting information corresponding to the item auditing dimension in the auditing instruction according to the auditing strategy corresponding to the item auditing dimension in the auditing instruction.

In one particular embodiment, the project audit dimension includes: a project necessity dimension, a project realizability dimension, a project rationality dimension, and a project integrity dimension;

the auditing order of the project auditing dimension includes: the auditing priority of the project necessity dimension is greater than the auditing priority of the project realizability dimension, the auditing priority of the project realizability dimension is greater than the auditing priority of the project rationality dimension, and the auditing priority of the project rationality dimension is greater than the auditing priority of the project integrity dimension.

In a specific embodiment, the auditing module 2102 is specifically configured to extract construction basis information from first project information, where the first project information includes declaration information corresponding to a project necessity dimension; determining whether a construction basis file corresponding to the construction basis information exists or not; and under the condition that the construction basis file exists, auditing the first project information based on the construction basis file.

In one particular embodiment, the project realizability dimension includes: project construction intensive dimension, project data sharing dimension, project requirement definiteness dimension and project scheme feasibility dimension; the auditing module 2102 is specifically configured to extract, from second item information, item construction information corresponding to an item construction intensive dimension, data sharing information corresponding to an item data sharing dimension, item requirement information corresponding to an item requirement definiteness dimension, and item feasibility information corresponding to an item scheme feasibility dimension, where the second item information includes declaration information corresponding to an item realizability dimension; and respectively auditing the project construction information, the data sharing information, the project demand information and the project feasibility information based on the auditing strategies corresponding to the project realizability dimension.

In a specific embodiment, the auditing module 2102 is specifically configured to extract, from third item information, item resource information corresponding to an item rationality dimension, where the third item information includes declaration information corresponding to the item rationality dimension; and auditing the project resource information based on the auditing strategies corresponding to the project rationality dimensions.

In a specific embodiment, the auditing module 2102 is specifically configured to extract, from fourth item information, item design information corresponding to an item integrity dimension, where the fourth item information includes declaration information corresponding to the item integrity dimension; and auditing the project design information based on the auditing strategy corresponding to the project integrity dimension.

In a specific embodiment, the auditing module 2102 is specifically configured to vector declaration information corresponding to a project auditing dimension to obtain a declaration information vector; searching a reporting information vector matched with the reporting information vector from a preset project reporting vector library; the project reporting vector library comprises at least one reporting information vector of each project auditing dimension corresponding to the project that is audited; and when the reporting information vector matched with the reporting information vector is retrieved from the project reporting vector library, determining that the reporting information corresponding to the project auditing dimension passes.

The project declaration data processing device provided in this embodiment belongs to the same application concept as the project declaration data processing method provided in the above embodiment of the present application, and can execute the project declaration data processing method provided in any of the above embodiments of the present application, and has functional modules and beneficial effects corresponding to executing the project declaration data processing method. Technical details not described in detail in this embodiment may refer to specific processing content of the method for processing project declaration data provided in the foregoing embodiments of the present application, and are not described herein again.

Exemplary electronic device

Another embodiment of the present application further provides an electronic device, referring to fig. 22, including:

a memory 200 and a processor 210;

wherein the memory 200 is connected to the processor 210, and is used for storing a program;

the processor 210 is configured to implement the method for processing project declaration data disclosed in any of the foregoing embodiments by executing a program stored in the memory 200, where the method specifically includes: acquiring an item declaration file corresponding to an item to be checked; based on preset auditing dimensions and auditing strategies corresponding to the auditing dimensions of each item, auditing reporting information corresponding to the auditing dimensions of each item in an item application file; the auditing strategies corresponding to the auditing dimensions of each item are determined based on auditing requirements of the item to be audited; and generating project audit reports based on audit results of the reporting information corresponding to each project audit dimension.

Specifically, the electronic device may further include: a bus, a communication interface 220, an input device 230, and an output device 240.

The processor 210, the memory 200, the communication interface 220, the input device 230, and the output device 240 are interconnected by a bus. Wherein:

a bus may comprise a path that communicates information between components of a computer system.

Processor 210 may be a general-purpose processor such as a general-purpose Central Processing Unit (CPU), microprocessor, etc., or may be an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of programs in accordance with aspects of the present invention. But may also be a Digital Signal Processor (DSP), application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components.

Processor 210 may include a main processor, and may also include a baseband chip, modem, and the like.

The memory 200 stores programs for implementing the technical scheme of the present invention, and may also store an operating system and other key services. In particular, the program may include program code including computer-operating instructions. More specifically, the memory 200 may include read-only memory (ROM), other types of static storage devices that may store static information and instructions, random access memory (random access memory, RAM), other types of dynamic storage devices that may store information and instructions, disk storage, flash, and the like.

The input device 230 may include means for receiving data and information entered by a user, such as a keyboard, mouse, camera, scanner, light pen, voice input device, touch screen, pedometer, or gravity sensor, among others.

Output device 240 may include means, such as a display screen, printer, speakers, etc., that allow information to be output to a user.

The communication interface 220 may include devices using any transceiver or the like for communicating with other devices or communication networks, such as ethernet, radio Access Network (RAN), wireless Local Area Network (WLAN), etc.

The processor 210 executes programs stored in the memory 200 and invokes other devices that may be used to implement the steps of any of the project declaration data processing methods provided in the above-described embodiments of the present application.

Exemplary computer program product and storage Medium

In addition to the methods and apparatus described above, embodiments of the present application may also be a computer program product comprising computer program instructions which, when executed by a processor, cause the processor to perform the steps in an item declaration data processing method according to various embodiments of the present application described in the "exemplary methods" section of this specification, the method specifically including: acquiring an item declaration file corresponding to an item to be checked; based on preset auditing dimensions and auditing strategies corresponding to the auditing dimensions of each item, auditing reporting information corresponding to the auditing dimensions of each item in an item application file; the auditing strategies corresponding to the auditing dimensions of each item are determined based on auditing requirements of the item to be audited; and generating project audit reports based on audit results of the reporting information corresponding to each project audit dimension.

The computer program product may write program code for performing the operations of embodiments of the present application in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server.

Furthermore, embodiments of the present application may also be a storage medium having stored thereon a computer program for execution by a processor of steps in an item declaration data processing method according to various embodiments of the present application described in the above-described "exemplary method" section of the present specification, the method specifically including: acquiring an item declaration file corresponding to an item to be checked; based on preset auditing dimensions and auditing strategies corresponding to the auditing dimensions of each item, auditing reporting information corresponding to the auditing dimensions of each item in an item application file; the auditing strategies corresponding to the auditing dimensions of each item are determined based on auditing requirements of the item to be audited; and generating project audit reports based on audit results of the reporting information corresponding to each project audit dimension.

For the foregoing method embodiments, for simplicity of explanation, the methodologies are shown as a series of acts, but one of ordinary skill in the art will appreciate that the present application is not limited by the order of acts described, as some acts may, in accordance with the present application, occur in other orders or concurrently. Further, those skilled in the art will also appreciate that the embodiments described in the specification are all preferred embodiments, and that the acts and modules referred to are not necessarily required in the present application.

It should be noted that, in the present specification, each embodiment is described in a progressive manner, and each embodiment is mainly described as different from other embodiments, and identical and similar parts between the embodiments are all enough to be referred to each other. For the apparatus class embodiments, the description is relatively simple as it is substantially similar to the method embodiments, and reference is made to the description of the method embodiments for relevant points.

The steps in the method of each embodiment of the application can be sequentially adjusted, combined and deleted according to actual needs, and the technical features described in each embodiment can be replaced or combined.

The modules and sub-modules in the device and the terminal of the embodiments of the present application may be combined, divided, and deleted according to actual needs.

In the embodiments provided in the present application, it should be understood that the disclosed terminal, apparatus and method may be implemented in other manners. For example, the above-described terminal embodiments are merely illustrative, and for example, the division of modules or sub-modules is merely a logical function division, and there may be other manners of division in actual implementation, for example, multiple sub-modules or modules may be combined or integrated into another module, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or modules, which may be in electrical, mechanical, or other forms.

The modules or sub-modules illustrated as separate components may or may not be physically separate, and components that are modules or sub-modules may or may not be physical modules or sub-modules, i.e., may be located in one place, or may be distributed over multiple network modules or sub-modules. Some or all of the modules or sub-modules may be selected according to actual needs to achieve the purpose of the embodiment.

In addition, each functional module or sub-module in each embodiment of the present application may be integrated in one processing module, or each module or sub-module may exist alone physically, or two or more modules or sub-modules may be integrated in one module. The integrated modules or sub-modules may be implemented in hardware or in software functional modules or sub-modules.

Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative elements and steps are described above generally in terms of functionality in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software unit executed by a processor, or in a combination of the two. The software elements may be disposed in Random Access Memory (RAM), memory, read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

Finally, it is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method of processing project declaration data, comprising:

acquiring an item declaration file corresponding to an item to be checked;

2. The method for processing project declaration data according to claim 1, wherein the auditing the declaration information corresponding to each project audit dimension in the project application file based on preset each project audit dimension and an audit policy corresponding to each project audit dimension includes:

3. The method for processing project declaration data according to claim 1, wherein auditing declaration information corresponding to a project audit dimension in the project application file based on the project audit dimension and an audit policy corresponding to the project audit dimension includes:

4. The method for processing project declaration data according to claim 3, wherein the auditing the declaration information corresponding to the project audit dimension based on the audit policy corresponding to the project audit dimension includes:

5. The method of claim 1-4, wherein the project audit dimension comprises: a project necessity dimension, a project realizability dimension, a project rationality dimension, and a project integrity dimension;

6. The method according to claim 5, wherein, in a case where the item audit dimension includes the item necessity dimension, auditing the declaration information corresponding to the item necessity dimension based on an audit policy corresponding to the item necessity dimension, includes:

7. The project declaration data processing method of claim 5, wherein the project realizability dimension includes: project construction intensive dimension, project data sharing dimension, project requirement definiteness dimension and project scheme feasibility dimension;

8. The method according to claim 5, wherein, in the case where the item audit dimension includes an item rationality dimension, auditing the reporting information corresponding to the item rationality dimension based on an audit policy corresponding to the item rationality dimension includes:

9. The method according to claim 5, wherein, in the case where the item audit dimension includes the item integrity dimension, auditing the declaration information corresponding to the item integrity dimension based on an audit policy corresponding to the item integrity dimension, includes:

10. The method according to any one of claims 1 to 4, wherein auditing the reporting information corresponding to the item audit dimension based on the audit policy corresponding to the item audit dimension includes:

11. An item declaration data processing apparatus, comprising:

12. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method for processing claim 1 to 10.

13. A non-transitory computer readable storage medium having stored thereon a computer program, which when executed by a processor implements the item declaration data processing method according to any one of claims 1 to 10.