CN114064421B

CN114064421B - Alarm processing method and device

Info

Publication number: CN114064421B
Application number: CN202111351188.0A
Authority: CN
Inventors: 罗昆元; 董文华
Original assignee: Spreadtrum Communications Shanghai Co Ltd
Current assignee: Spreadtrum Communications Shanghai Co Ltd
Priority date: 2021-11-16
Filing date: 2021-11-16
Publication date: 2022-04-22
Anticipated expiration: 2041-11-16
Also published as: CN114064421A

Abstract

The application provides an alarm processing method and device, wherein the method comprises the following steps: acquiring alarm information in first data of a version to be released through a scanning tool; merging the same alarms in the alarm information of the version to be released, and adding module information in the alarm information of the version to be released; comparing whether the same alarm appears in the alarm information of the version to be released and the alarm information of the historical version, if so, adding a research and development analysis conclusion to a row corresponding to the same alarm in the alarm information of the version to be released; if the same alarm does not appear, the alarm appearing in the version to be released is reserved; and determining the alarm information analyzed by the person to be responsible in the first data of the version to be issued. The method provided by the application not only can effectively improve the problem of excessive repeated alarm in the alarm information, but also can automatically allocate the responsible person, so that the responsible person corresponding to the alarm information can be traced.

Description

Alarm processing method and device

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for processing an alarm.

Background

Generally, when a developer completes a software project, in order to effectively detect a defect in the software, the software may be scanned by using a scan analysis tool, so as to find the defect in the software.

For example, after the scan analysis tool performs analysis, an original alarm file is output, so that a developer performs analysis or modification and the like according to the original alarm file.

Therefore, how to output an effective alarm is an ongoing problem for those skilled in the art.

Disclosure of Invention

The application provides an alarm processing method and device, which not only can effectively solve the problem of excessive repeated alarms in alarm information (namely the efficiency of outputting effective alarms is higher), but also can automatically allocate responsible persons, so that the responsible persons corresponding to the alarm information can be traced.

In a first aspect, an embodiment of the present application provides an alarm processing method, where the method includes:

acquiring alarm information in first data of a version to be released through a scanning tool, wherein the scanning tool is used for scanning defects in the first data, the alarm information is used for representing alarms appearing in at least one line of the first data, and the alarm information corresponds to the line of the alarms appearing in the first data;

merging the same alarms in the alarm information of the version to be issued, and adding module information in the alarm information of the version to be issued, wherein the module information comprises information of responsible persons corresponding to the row in which the alarm appears in the first data;

comparing whether the same alarm appears in the alarm information of the to-be-released version and the alarm information of the historical version, if the same alarm appears in the alarm information of the to-be-released version and the alarm information of the historical version, adding a research and development analysis conclusion to a row corresponding to the same alarm in the alarm information of the to-be-released version, wherein the research and development analysis conclusion is contained in the alarm information of the historical version; if the alarm information of the version to be released and the alarm information of the historical version do not have the same alarm, the alarm in the version to be released is reserved;

and outputting the alarm information to be analyzed by the responsible person in the first data of the version to be issued.

In the embodiment of the application, the same alarms can be combined through secondary processing (such as combining or adding module information) of the alarm information, and the alarms in the version to be issued, which are the same as the historical version, can be combined through comparing the historical version with the version to be issued, so that repeated alarms are effectively reduced, and the excessive manpower for researching, developing and analyzing the repeated alarms is avoided. In addition, by adding the responsible person corresponding to the alarm, the alarm processing device can be automatically distributed to the corresponding research and development personnel according to the distributed responsible person, so that the research and development personnel can analyze the alarm, and the efficiency of distributing the research and development personnel is effectively improved.

In a possible implementation manner, the merging the same alarms in the alarm information of the to-be-released version includes:

merging the same alarms in the alarm information of the version to be issued according to first information, wherein the first information comprises any one or more of a file name, a line number or an alarm number;

the step of comparing whether the alarm information of the to-be-released version is the same as the alarm information of the historical version comprises:

and comparing whether the same alarm occurs in the alarm information of the version to be issued and the alarm information of the historical version according to second information, wherein the second information comprises a file name and/or an alarm number.

In a possible implementation manner, before the comparing whether the alarm information of the to-be-released version and the alarm information of the historical version have the same alarm, the method further includes:

merging the alarms belonging to the same version in the historical version according to the first information;

merging the alarms belonging to different versions in the historical version according to the second information, simultaneously determining whether the responsible person corresponding to the alarm belonging to the newer version in the different versions in the historical version needs to be updated, and updating the responsible person corresponding to the alarm belonging to the newer version in the different versions in the historical version under the condition that the responsible person needs to be updated;

and determining the alarm information of the historical version.

In a possible implementation manner, the information of the responsible person corresponding to the line in which the alarm occurs in the first data includes any one or more of the following items:

the method comprises the steps of obtaining first data, wherein the first data comprises a submitter of a line with an alarm in the first data, a responsible person of the line with the alarm in the first data, the type of the responsible person of the line with the alarm in the first data, and the type of the submitter corresponding to the line with the alarm in the first data.

It is understood that the type of the principal or the type of the submitter shown in the embodiment of the present application may be a job type or a work division type of the principal when the principal is responsible for the version to be released, and the embodiment of the present application does not limit this.

In one possible implementation, the module information further includes any one or more of the following:

the function of the row where the alarm appears in the first data, the modification time of the row where the alarm appears in the first data, and the engineering field of the row where the alarm appears in the first data.

In one possible implementation, the method further includes:

determining whether a modification time of a line in the first data in which an alarm occurs is within one year;

if the number of the line in which the alarm appears in the first data is not within one year, determining the latest submitter of the line in which the alarm appears in the first data, and if the latest submitter meets preset conditions, configuring whether to search a next-time submitter of the line in which the alarm appears in the first data, wherein the preset conditions comprise any one or more of people who leave the job, people who are appointed to fail to submit or people located at a target job;

if the second-time new submitter of the row with the alarm in the first data is searched for in a configuration mode, determining the second-time new submitter of the row with the alarm in the first data;

if the second new submitter does not meet the preset condition, determining that the second new submitter is a responsible person corresponding to the row with the alarm in the first data;

and if the second-time new submitter meets the preset condition, determining that the previous-level concerned person of the latest submitter is the responsible person corresponding to the row with the alarm in the first data.

In a possible implementation manner, before outputting the alarm information to be analyzed by the responsible person in the first data of the version to be published, the method further includes:

and deleting the alarm conclusion in the alarm information of the version to be distributed, which is a false alarm or an ignored alarm.

In a second aspect, an embodiment of the present application provides an alarm processing apparatus, which includes means for implementing the method in the first aspect and any possible implementation manner thereof.

In a third aspect, an embodiment of the present application provides an alarm processing apparatus, which includes a processor and a memory, where the processor and the memory are connected to each other, and the memory is used for storing a computer program, and the computer program includes program instructions, and the processor is configured to call the program instructions to execute the method according to the first aspect.

In a fourth aspect, an embodiment of the present application provides a chip, where the chip includes a processor and an interface, and the processor and the interface are coupled; the interface is for receiving or outputting signals and the processor is for executing code instructions for performing a method as described in the first aspect.

In a fifth aspect, an embodiment of the present application provides a module device, where the module device includes a communication module, a power module, a storage module, and a chip module, where: the power module is used for providing electric energy for the module equipment; the storage module is used for storing data and instructions; the communication module is used for carrying out internal communication of the module equipment or is used for carrying out communication between the module equipment and external equipment; the chip module is used for executing the method of the first aspect.

In a sixth aspect, the present application provides a computer-readable storage medium storing a computer program, the computer program comprising program instructions that, when executed by a processor, cause the processor to perform the method according to the first aspect.

In a seventh aspect, this application provides a computer program, and when the computer program is executed, the method in the first aspect is executed.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments or the background art of the present application, the drawings used in the embodiments or the background art of the present application will be briefly described below.

Fig. 1 is a schematic flowchart of an alarm processing method according to an embodiment of the present application;

fig. 2 is a schematic flowchart of another alarm processing method provided in the embodiment of the present application;

FIG. 3 is a flowchart illustrating a method for determining a responsible person corresponding to an alarm line according to an embodiment of the present disclosure;

FIG. 4 is a flowchart illustrating another method for determining a responsible person corresponding to an alarm line according to an embodiment of the present disclosure;

fig. 5 is a schematic structural diagram of an alarm processing apparatus according to an embodiment of the present application;

FIG. 6 is a schematic structural diagram of another alarm processing device provided in an embodiment of the present application;

fig. 7 is a schematic structural diagram of another alarm processing apparatus according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more clear, the present application will be further described with reference to the accompanying drawings.

The terms "first" and "second," and the like in the description, claims, and drawings of the present application are used solely to distinguish between different objects and not to describe a particular order. Furthermore, the terms "comprising" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions. Such as a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.

Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those skilled in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments.

In this application, "at least one" means one or more, "a plurality" means two or more, "at least two" means two or three and three or more, "and/or" for describing an association relationship of associated objects, which means that there may be three relationships, for example, "a and/or B" may mean: only A, only B and both A and B are present, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one item(s) below" or similar expressions refer to any combination of these items. For example, at least one (one) of a, b, or c, may represent: a, b, c, "a and b," a and c, "" b and c, "or" a and b and c.

In general, static analysis tools may be used to analyze defects in C and C + + source code. For example, the static analysis tool may include a PC-lint plus or the like. For convenience of description, the method and apparatus provided in the present application will be described below by taking a PC-lint plus scan tool as an example.

The PC-lint plus scan tool can generate the original alarm file by modules, namely, each module has an alarm file stored in the form of xml. However, these alarms have the following problems: too many repeated alarms, unretraceable data, incapability of automatically allocating owners, incapability of removing the overlooked alarms in research and development, repeated research and development investment and analysis, too much manpower without attention to the alarms and the like. In view of the above problems, the method provided by the present application may import effective alarm information into a database or excel, so as to implement visualization and centralized management of alarm information (as shown in fig. 1 and fig. 2 below).

It is understood that the method described in this application may be applied to an alarm processing device, for example, the alarm processing device may be any device capable of running software codes, or may be any tool capable of scanning software for defects by using a scanning tool, and the present application does not limit the specific form of the alarm processing device. However, all devices capable of implementing the alarm processing method provided by the present application belong to the scope of protection of the present application. It is understood that the description of the alarm processing device will not be described in detail below.

Fig. 1 is a schematic flowchart of an alarm processing method provided in an embodiment of the present application, and as shown in fig. 1, the method includes:

101. and acquiring the alarm information in the first data of the version to be released through a scanning tool.

The scanning tool is used for scanning defects in the first data, the alarm information is used for representing alarms appearing in at least one line of the first data, and the alarm information corresponds to the line of the first data where the alarms appear. The first data may be software code for realizing a certain function. The embodiment of the present application does not limit the code type of the first data. Illustratively, the code type of the first data may be c language, c + + or python (for example only), and the like. The scanning tool may be used to analyze c language, c + + or python, etc. to find defects in the c language software code or c + + software code or python software code. For example, the scan tool may be a static analysis function, such as a PC-lint plus scan tool. The alarm information may be understood as a general term for alarms occurring in the first data, such as alarms occurring in a certain line or certain lines in software code such as c or c + +, python, or the like. The alarm information shown in the present application corresponds to the row in which the alarm occurs in the first data. For example, the alarm information refers to a general term of alarms of an error row in the first data.

The to-be-released version refers to a stage where software for implementing a certain function or certain functions through source code such as c, c + +, python, or the like is not put into use or is not confirmed, for example, a stage where a developer performs a test or a stage of checking an alarm, and the like, which is not limited in this embodiment of the present application.

102. Merging the same alarms in the alarm information of the version to be issued, and adding module information in the alarm information of the version to be issued, wherein the module information comprises information of responsible persons corresponding to the row in which the alarm appears in the first data.

Generally, if the first data is scanned through the PC-lint plus, repeated alarms may occur in the generated alarm information, thereby causing excessive labor for the research and development personnel to invest in repeated analysis. That is, the alarm information output by the alarm processing device may have a large number of contents to be duplicated, resulting in inefficient output of the alarm information. However, in the embodiment of the present application, the alarm information may be processed for the second time, for example, the alarm processing apparatus may combine the same alarms in the alarm information of the version to be issued according to the first information. That is, the same alarms may be merged according to the first information, and if the first information corresponding to the alarms in different rows is the same, the alarms in the different rows may be merged. If the first information comprises any one or more of a file name (file _ name), a line number (line _ id) or an alarm number (ward _ id). For example, a multi-level dictionary with a file name, a line number and an alarm number as keys is used as alarm information. Optionally, a multi-level dictionary with a file name, an alarm number, an alarm description, and a line number as a key may be used as the alarm information. Optionally, the first information may also be a file name, an alarm number, a line number, and value = [ description, details, project name, module name ].

The alarm processing device can effectively improve the efficiency of the device for outputting alarm information by combining the same alarms, effectively reduce the continuous processing of repeated alarms by research personnel, and improve the efficiency of the research personnel for processing the alarms.

In this embodiment, the alarm processing apparatus may further add module information to each alarm, where the module information may include information of a responsible person corresponding to a line in which an alarm occurs in the first data, and the information of the responsible person corresponding to the line in which the alarm occurs in the first data includes a submitter of the line in which the alarm occurs in the first data, a responsible person in which the alarm occurs in the first data, a type of the responsible person in which the alarm occurs in the first data, or a type of the submitter of the alarm line in the first data. Wherein, the submitter refers to a person who submits the first data (such as the software code), such as a developer who may be the software code, etc.; the person in charge may be a developer of the software code, etc. It is understood that the type of the principal or the type of the submitter shown in the embodiment of the present application may be a job type or a work division type of the principal when the principal is responsible for the version to be released, and the embodiment of the present application does not limit this.

Optionally, the module information further includes any one or more of the following:

the method comprises the following steps of a function (module) where a row with an alarm in the first data is located, modification time (modification date) of the row with the alarm in the first data, an engineering field (project) where the row with the alarm in the first data is located, and a module name (module). For example, the first data may implement the function to be implemented by the software code through a plurality of functions, and therefore, in the embodiment of the present application, by adding the function where the first data is located to the row of the alarm, the alarm may be located more accurately. For example, by adding the modification time of the row of the alarm in the first data, the person responsible for the first data can be more accurately positioned. For example, when software code is shared, even different projects or projects may use the same code, so by adding the project field where the row of the alarm is located in the first data, the alarm can be located more accurately. For example, the first data may be software code consisting of a plurality of modules, so that the alarm may be more accurately located by adding the module name of the row of the alarm to the first data.

It is understood that the detailed description of step 102 may also refer to step 201 in the method shown in fig. 2, which is not described in detail herein.

103. Comparing whether the same alarm appears in the alarm information of the version to be released and the alarm information of the historical version, and if the same alarm appears in the alarm information of the version to be released and the alarm information of the historical version, adding a research and development analysis conclusion to a row corresponding to the same alarm in the alarm information of the version to be released; if the alarm information of the version to be released and the alarm information of the historical version do not have the same alarm, the alarm in the version to be released is reserved.

In the embodiment of the application, when the same alarm appears in the alarm information of the to-be-released version and the alarm information of the historical version, it is indicated that the analyzed alarm appears in the alarm information of the to-be-released version. Therefore, the research and development analysis conclusion about the same alarm in the alarm information of the historical version can be added to the alarm information of the version to be released. Thus, it is indicated that the relevant developer (e.g., the identified responsible person) need not repeatedly analyze the same alarm. That is, the research and development analysis conclusion added to the alarm information of the version to be released is included in the alarm information of the historical version.

For example, comparing whether the alarm information of the version to be released and the alarm information of the historical version have the same alarm includes: and comparing whether the same alarm appears in the alarm information of the version to be released and the alarm information of the historical version according to second information, wherein the second information comprises a file name and/or an alarm number. Generally, the corresponding lines of the software codes of different versions are different, so the line number may not be included in the second information. It is understood that the description of the second information may also refer to the first information and will not be described in detail here.

Optionally, before comparing whether the alarm information of the to-be-released version and the alarm information of the historical version have the same alarm, the method shown in fig. 1 further includes:

and determining the alarm information of the historical version.

That is to say, the method provided in the embodiment of the present application may further merge the alarm information of the historical version, and obtain the alarm information without repeated alarms by performing secondary processing on the alarm information of the historical version. Generally, the submitter or the responsible person of the software code of different versions may be different, and therefore, the embodiment of the present application may also update the responsible person corresponding to the alarm appearing in the newer version. It is understood that the above is referred to for the explanation of the responsible person, and the following (fig. 3 and 4) is referred to for the explanation of the responsible person, which is not detailed here. The method of handling the same alarm may also refer to the description elsewhere in this application and will not be described in detail here.

Through the step 102, the alarm repeatedly appearing in the version to be released can be effectively deleted, and through the step 103, the alarm repeatedly appearing in the version to be released and the historical version can be effectively deleted. Therefore, repeated alarms are effectively reduced, and the time for distributing the alarms by the alarm processing device can be effectively reduced.

104. And outputting the alarm information analyzed by the person to be responsible in the first data of the version to be issued.

In the embodiment of the present application, through the steps 102 to 103, not only the alarm repeatedly appearing in the to-be-released version but also the alarm repeatedly appearing in the to-be-released version and the alarm repeatedly appearing in the historical version can be combined. Therefore, the alarm processing device can obtain the alarm information after the merging processing of the version to be issued. In turn, it may assign an alarm occurring in the to-be-published version to the corresponding responsible person (e.g., the responsible owner or submitter, etc.). It is understood that reference may be made to fig. 3 and 4 with respect to the specific method of assignment to the respective responsible person, which will not be described in detail herein.

The outputting of the alarm information analyzed by the person to be responsible in the first data of the version to be published may include: outputting alarm information analyzed by the person to be responsible in the first data of the version to be issued through a display screen; or sending the alarm information analyzed by the person to be responsible in the first data of the version to be distributed to a terminal device or an electronic mailbox corresponding to the person to be responsible.

Optionally, before outputting the alarm information analyzed by the person to be responsible in the first data of the version to be issued, the method shown in fig. 1 further includes:

and deleting the alarm conclusion in the alarm information of the version to be distributed, wherein the alarm conclusion is a false alarm or an ignored alarm.

Generally, the false alarm or the ignored alarm does not need to be analyzed by the research and development personnel, so that the alarm information finally obtained by the alarm processing device can be really analyzed by the research and development personnel by deleting the alarm of which the alarm conclusion is the false alarm or the ignored alarm in the alarm information of the version to be issued. The efficiency of the alarm processing device for outputting the alarm information can be improved, the workload of research and development personnel can be effectively reduced, and the user satisfaction can be improved.

In the embodiment of the application, the same alarms can be combined through secondary processing (such as combining or adding module information) of the alarm information, and the alarms in the version to be issued, which are the same as the historical version, can be combined through comparing the historical version with the version to be issued, so that repeated alarms are effectively reduced, and the excessive manpower for researching, developing and analyzing the repeated alarms is avoided.

Fig. 2 is a schematic flowchart of another alarm processing method provided in the embodiment of the present application, and as shown in fig. 2, the method includes:

201. and scanning the first data of the version to be released by a PC-lint plus scanning tool.

Namely, scanning the software code of the version to be released, and analyzing the defects of the software code.

202. And generating an aloa.

Namely, the alarm processing device can scan the software code of the version to be released by a PC-lint plus scanning tool, so as to generate an original alarm file according to different modules. That is, in the embodiment of the present application, the alarm file may be stored according to different modules. For example, the software code may include one or more modules, whereby the alarm processing device may store the original alarm file from module to module. For example, different modules correspond to different alarm files. For another example, different modules generate different element alarm files, so that the element alarm files can be output to an Excel table according to different modules.

Optionally, in the embodiment of the present application, all alarms may also be output to an excel table. And outputting the alarm appearing in the version to be released into an Excel table (shown as a dotted line part in fig. 2) according to the generated original alarm file of aloa. In this case, different research and development personnel (such as a responsible person and the like) can find the alarm belonging to the research and development personnel.

203. And merging the same alarms of different rows and outputting the same alarms to an Excel table. Namely, the secondary processing of the alarm information and the merging and displaying of the similar alarm information.

For example, the alarm processing device may read alarm files under various modules (such as different modules in the software code of the version to be released) and store the alarm files in the dictionary. Such as a multi-level dictionary with file name, row number, alarm number as key, value = [ description, details, project name, module name ]. It is understood that a dictionary may be understood as a data type. That is, data types indicating that the above [ description, detail, project name, module name ] is stored in the form of value and is a dictionary.

For example, in the embodiment of the present application, a git frame-e or svn frame-v command may be used to obtain the latest code submitter (submitter), commit _ id, function name (func _ name), and modified code time (modified _ date) of the alarm line, and of course, a source code (source) may also be included. And accurately positioning the owner of the alarm line code according to submitter. It is understood that, regarding the determination method of the person in charge or the submitter, reference may be made to fig. 3, which will not be described in detail herein.

Then, a multi-level dictionary with the file name, the line number and the alarm number as keys can be used for judging whether two alarms are one alarm. Meanwhile, module information, such as alarm owner, commit id, source, function, modify date, project information, may be added to each alarm and output to the excel table.

Optionally, a multi-level dictionary with the file name, the alarm number, the alarm description and the object pointed by 'a' as key can be used for judging whether the two alarms are the same alarm, and meanwhile, department information of each alarm owner can be added and output to an excel table. It is understood that the description of the method for determining whether the alarms are the same may refer to the method shown in fig. 1, and will not be described in detail here. It can be understood that the 'a' mentioned above is used to point to the place where the scanning is wrong, i.e. to indicate that the alarm appears in the corresponding line in the scanned alarm information.

204. And performing accumulative analysis on the alarm information of the historical version to obtain the alarm information of the historical version.

In the embodiment of the present application, the accumulated analysis of the alarm information of the historical version may include accumulated analysis of the same version and accumulated analysis of different versions. As described in detail below.

Alternatively, cumulative analysis for the same version may be as follows:

in the embodiment of the application, the alarm information of the historical version can be output to an Excel table, and since each research and development personnel can analyze the alarm information, research and development analysis conclusions of the research and development personnel can be contained in the alarm information of the historical version.

And traversing a form fed back by a version developer, and searching whether the same alarm exists on the original alarm form (namely the original alarm form of the version) according to the module, the file _ name, the line _ id and the war _ id. If so, adding the alarm conclusion of research and development analysis into the corresponding alarm, simultaneously judging whether the Cr _ assigner column has content, if not, updating Cr _ owner (such as an responsible person) to the suffix name of the EXCEL table of research and development feedback, updating own _ type (the responsible person type) to EXCEL _ FILE, otherwise, updating own _ type to EXCEL _ CELL.

Alternatively, the cumulative analysis for the different versions may be as follows:

traversing the alarm of the research and development analysis conclusion accumulated by one version in the historical version, wherein the number of lines after code adjustment changes, so that whether the function name and the code content in the historical accumulated alarm (such as the alarm in the version before the version) are the same or not can be judged by using a multi-level dictionary with the file name, the alarm number and the commit _ id as keys; if the same, updating the owner (the updating method can refer to fig. 3 and fig. 4), if different, the alarm of which one version has the research and development analysis conclusion is accumulated in the alarm information of the historical version, and the alarms of which all versions have the research and development analysis conclusion are accumulated circularly, so that the alarm information of the historical version is obtained.

205. And acquiring the alarm to be analyzed according to the alarm information of the version to be released and the alarm information of the historical version.

Acquiring an alarm table of a to-be-released version (such as the table acquired according to the step 203) and an alarm table (namely alarm information of a historical version and also can be an alarm table of the historical version) of all research and development analysis conclusions accumulated in the item acquired in the step 204, traversing the alarm table of the to-be-released version, and judging whether function names and code contents in the alarm table of the historical version are the same by using a multi-level dictionary with file names, alarm numbers and commit _ id as keys; if the alarm tables are the same, adding the research and development analysis results in the alarm tables of the historical versions in the alarm tables of the to-be-released versions; if not, the corresponding alarm is reserved. And taking the file name, the alarm number, the description and the object pointed by the ^ number as a multi-level dictionary of the key, and combining the same alarms according to the multi-level dictionary. Meanwhile, the alarm with the alarm conclusion of 'false alarm' or 'neglect' is removed. Through the steps, the alarm information to be analyzed of the current version (namely the version to be released) is finally obtained and presented in the form of an execl table.

206. The responsible person according to the alarm line code automatically distributes the alarm to the corresponding responsible person (such as the corresponding research and development personnel).

In the embodiment of the present application, the alarm information (which may also be referred to as an original alarm file) generated by the PC-lint plus scan may include a file name, a line number, an alarm number, a description, and a code location for reporting an error. Meanwhile, the embodiment of the application carries out secondary processing on the obtained alarm information. After the secondary processing, information of each alarm adding module (module), such as an alarm line code submitter (submitter), a commit _ id, a function (function) where the alarm line code is located, an alarm line code final person (cr _ owner), an alarm line code final person type (owner _ type), an alarm line code modification time (modification _ date) and an engineering (project) field, can be automatically allocated to an owner, automatically filter out the alarms which are not concerned in research and development and merge repeated alarms, and reduce a large amount of manpower input in research and development.

Fig. 3 is a flowchart illustrating a method for determining a responsible person corresponding to a row of an alarm according to an embodiment of the present disclosure. It is understood that the method shown below is exemplified by the first data of the to-be-released version shown in the present application, and the method of determining the person responsible for the historical version and the like is also applicable to the method shown in fig. 3. As shown in fig. 3, the method includes:

301. determining whether the modification time of the line in the first data in which the alarm occurs is within one year (as abbreviated as whether the modification time of the line in which the alarm occurs is within one year in fig. 3); if not within one year (no as shown in fig. 3 with respect to step 301), then step 305 is performed; if within one year (yes as shown in fig. 3 with respect to step 301), step 302 is performed.

Generally, when the code is not modified within one year, the person responsible for the code may be out of work, etc.; when the code is modified within a year, it is stated that the person responsible for the code may not be out of position, etc. Therefore, in the embodiment of the application, by determining whether the modification time of the line with the alarm is within one year, the person responsible for the line with the alarm can be determined more efficiently.

It is understood that the step of the latest owner of the row in which the alarm occurs shown in fig. 3 may be before step 301, before step 302, and the like, and the embodiment of the present application is not limited thereto.

302. Determining whether the latest owner meets a preset condition (e.g., whether to leave, high leader, or designate a person who cannot submit as shown in fig. 3), and if the preset condition is met (y as shown in fig. 3 with respect to step 302), performing step 303; otherwise (no as shown in fig. 3 with respect to step 302), step 311 is performed.

Generally, even if the time of modification of the code is within one year, it may occur that the person in charge of the code may have left the job, or is at the target job position, or is designated as a person who cannot submit (it may also be understood as a designated person who cannot be a person in charge). Therefore, in the embodiment of the application, by judging whether the latest owner meets the preset condition, the person responsible for the first data can be more accurately located.

It is understood that the person at the target position shown in the embodiment of the present application may be a high-level leader, for example. Alternatively, the target position may correspond to the type of responsible person, and if the type of responsible person is determined according to the position type when the version to be released is responsible, the target position may be a person in a higher position in the position types. The embodiment of the present application does not limit the specific determination method of the target position.

303. The last level of attention of the latest winner.

If the latest owner is a person who has left the job, or a high-level leader, etc., it indicates that the latest owner cannot continue to analyze the software code (such as the first data) of the version to be released, etc., and therefore, by executing the method provided by the embodiment of the present application, the person responsible for the first data of the version to be released can be further located. For example, the previous person concerned by the latest owner may be a previous leader of the latest owner, or an immediate leader of the latest owner, or a person concerned by the previous owner about the version to be released, or a person in charge of the latest owner, and the like, which is not limited in this embodiment of the application.

304. Whether the last level of interest of the latest owner meets a preset condition (e.g., whether to leave, high level leader, or designate a person who cannot submit as shown in fig. 3), if so (y as shown in fig. 3 with respect to step 304), executing step 305; otherwise ("no" as shown in fig. 3 with respect to step 304), step 311 is performed.

305. The latest submitter of the row in the first data where the alarm occurred (abbreviated as the latest submitter of the row where the alarm occurred in fig. 3) is determined.

The latest submitter of the first data may be determined if the superior stakeholder of the latest owner has also left the job, etc. I.e. by determining the latest submitter it is possible to avoid not finding the responsible person for the first data without configuration.

It can be understood that the methods shown in the embodiments of the present application are all exemplified by the latest submitter of the row in which the alarm occurs. Optionally, the version of the first data to be released may be the latest submitter of the first data of the version to be released; or, the version is the latest submitter of the software code of the version to be released; or, the module is the latest submitter of the module corresponding to the row with the alarm; or the latest submitter of the file corresponding to the software code, and the like. For example, if certain modules of the software code are all developed by the same developer, step 305 may be the latest submitter of the module corresponding to the row for which the alarm occurred. Also for example, typically, the submission is in whole software code (e.g., in the form of a file), and thus the most recent submitter of the first data can be determined. In this case, the latest submitter of the line in which the alarm occurs is the same as the latest submitter of the first data. Regarding the description of step 305, the following related steps are also applicable (such as step 308 or 311), and also fig. 4 shown below is also applicable, which is not described in detail below.

306. Determining whether the latest submitter meets preset conditions (e.g., whether to leave job, high level leader, or designate a person who cannot submit as shown in fig. 3); if so (yes as shown in FIG. 3 with respect to step 306), go to step 307; otherwise ("no" as shown in fig. 3 with respect to step 306), step 311 is performed.

In the embodiment of the present application, the preset condition includes any one or more of a person who has left the job, a person who is designated as a non-submittal person, or a person who is located at the target job. If the latest submitter is any one or more of a person who is out of position, a high level leader, or a person who specifies not to submit, then step 304 is performed; otherwise, step 305 is performed.

307. Configuring whether to search for the second new submitter of the row with the alarm in the first data (as shown in fig. 3 by way of example, whether to search for the second new submitter of the row with the alarm), if yes, executing step 308; otherwise, step 310 is performed.

In the embodiment of the application, whether the second new submitter is searched or not is configured, so that not only the responsible person can be located, but also the responsible person closely related to the first data can be located.

It can be understood that the method shown in the embodiment of the present application is exemplified by the next submitter of the row in which the alarm occurs. Optionally, the system can also be a second-time submitter of the first data of the version to be released; or, the version is the next submitter of the software code of the version to be released; or, the module is the next submitter of the module corresponding to the row with the alarm; or a next submitter of a file corresponding to the software code, and the like. For the description of step 307, reference may also be made to step 305 above, which is not described in detail here.

308. The next-to-new submitter of the line in the first data where the alarm occurred is determined (as illustrated in fig. 3 by the next-to-new submitter of the line where the alarm occurred).

It is understood that the newest submitter and the next-to-newest submitter are determined based on the submission time of the first data. For example, the latest submitter corresponds to the latest submission time of the first data, and the next latest submitter corresponds to the next latest submission time of the first data.

309. Determining whether the next submitter meets a preset condition (e.g., whether the submitter leaves employment, a high level leader, or a designated submitter that cannot be submitted as shown in fig. 3), and if so (y as shown in fig. 3 with respect to step 309), performing step 310; otherwise ("no" as shown in fig. 3 with respect to step 309), step 311 is performed.

310. The next highest degree of interest of the latest submitter is determined (as illustrated in fig. 3 by way of example for the next highest degree of interest of the latest submitter, i.e. the next highest degree of interest of the latest submitter representing the row in which the alarm occurred).

Optionally, the first data to be released (i.e. the software code shown in the embodiment of the present application) may also be a higher-level caretaker of the latest submitter; or, the software code to be released is the last level of the concerned person of the latest submitter of the software code to be released; or, the module is the last level of the concerned person of the latest submitter of the module corresponding to the row with the alarm; or the upper level concerned person of the latest submitter of the file corresponding to the software code, and the like. For the description of step 310, reference may also be made to step 305 above, which is not described in detail here.

311. It is determined that the responsible person corresponds to the line in the first data where the alarm occurred (as illustrated in fig. 3 for the example of determining the cr _ owner of the alarm).

By the method provided by the embodiment of the application, the person responsible for the first data of the version to be issued can be more accurately positioned, the positioned person responsible can be a person closely related to the first data of the version to be issued, and the accuracy of automatic alarm allocation of the alarm processing device to the corresponding person responsible for the first data is effectively improved.

The above is a method for determining a responsible person provided by the embodiment of the present application, however, in some cases, a person of the most recent submitter who is the last person of interest may be out of work, and the like, and thus, another method for determining a responsible person is provided by the embodiment of the present application.

Fig. 4 is a flowchart illustrating another method for determining a responsible person corresponding to an alarm line according to an embodiment of the present application, where as shown in fig. 4, the method includes:

401. determining whether the modification time of the line in the first data in which the alarm occurs is within one year (as abbreviated as whether the modification time of the line in which the alarm occurs is within one year in fig. 4); if not within one year (no as shown in fig. 4 with respect to step 401), then step 405 is performed; if within one year (no as shown in fig. 4 with respect to step 401), step 402 is performed.

It is understood that fig. 4 shows an illustration of whether or not the description is provided, and reference may be made to fig. 3, and the embodiments of the present application are not described in detail.

402. Determining whether the latest owner meets a preset condition (such as whether the owner leaves the job, a high-level leader or a person who cannot submit is designated as shown in fig. 4), and if the latest owner meets the preset condition, executing step 403; otherwise, step 411 is executed.

It is understood that the description of the relationship of the preset condition to the departure, the high level leader or the designated person who cannot submit can be referred to fig. 3, and the method shown in fig. 4 is not described in detail. The same applies as for

steps

404, 406, 409, 412 and 415 shown in fig. 4 in relation to the above description.

403. The last level of attention of the latest winner.

It is understood that step 403 shown in fig. 4 and step 303 shown in fig. 3 can also be understood as determining the upper level of interest of the latest winner.

404. Whether the last level of attention of the latest owner meets the preset conditions or not, if so, executing the step 405; otherwise, step 411 is executed.

405. The latest submitter of the line in the first data where the alarm occurred (abbreviated as the latest submitter of the line where the alarm occurred in fig. 4) is determined.

406. If the latest submitter meets the preset conditions, executing step 407; otherwise, step 411 is executed.

407. Configuring whether to search a second-time new submitter of the row with the alarm in the first data (as shown in fig. 4, whether to search a second-time new submitter of the row with the alarm), if yes, executing step 408; otherwise, step 410 is performed.

408. The next-to-new submitter of the line in the first data where the alarm occurred (fig. 4 is abbreviated as the next-to-new submitter of the line where the alarm occurred) is determined.

It can be understood that the method shown in the embodiment of the present application is exemplified by the next submitter of the row in which the alarm occurs. Optionally, the system can also be a second-time submitter of the first data of the version to be released; or, the version is the next submitter of the software code of the version to be released; or, the module is the next submitter of the module corresponding to the row with the alarm; or a next submitter of a file corresponding to the software code, and the like. For the description of step 408, reference may also be made to fig. 3, which is not described in detail here. It will be appreciated that the following applies equally to this description.

409. Determining whether the second new submitter meets the preset condition, and if so, executing step 410; otherwise, step 411 is executed.

410. The previous-level stakeholder of the latest submitter (abbreviated as the previous-level stakeholder of the latest submitter as in fig. 4) is determined.

411. It is determined that the responsible person corresponds to the line in the first data where the alarm occurred (as illustrated in fig. 4 for the example of determining the cr _ owner of the alarm).

412. Determining whether the upper-level concerned person of the latest submitter meets a preset condition, and if so, executing a step 412; otherwise, step 411 is executed.

413. Configuring whether to search the last level of interest of the second-time new submitter of the row with the alarm in the first data (for example, fig. 4 is the last level of interest of the second-time new submitter of the row with the alarm in the first data, if yes, executing step 414; otherwise, step 416 is performed.

414. The superior stakeholder of the next submitter of the row in the first data for which an alarm occurred is determined.

415. Whether the previous level of attention of the next submitter meets the preset conditions or not, if so, executing step 416; otherwise, step 411 is executed.

416. The most recent submitter of the current level directory of rows in the first data for which alarms occurred.

It will be appreciated that the present level targets for the rows shown above where alarms occur may also be replaced with: the current level target of the module corresponding to the row with the alarm; or, the present level object of the first data, etc., for this description, reference may be made to the description of 305, which is not detailed here.

417. Whether the latest submitter of the current-level catalog meets the preset condition or not, if so, executing step 418; otherwise, step 411 is executed.

418. The project principal or the person specifying the allocation of the version of the first data to be published (fig. 4 is illustrated by way of example as a software project principal or person specifying the allocation).

It is understood that the specific description of fig. 4 may refer to fig. 3 and will not be described in detail here.

Fig. 5 is a schematic structural diagram of an alarm processing apparatus according to an embodiment of the present application. The device can be any form of computer, or computer capable of running software codes, or a device in the computer, or a device capable of being matched with the computer for use. The alert processing apparatus 500 shown in fig. 5 may include a processing unit 501 and a communication unit 502. The processing unit 501 is configured to perform data processing. The communication unit 502 is integrated with a receiving unit and a transmitting unit. The communication unit 502 may also be referred to as a transceiving unit. Alternatively, communication section 502 may be divided into a reception section and a transmission section. The following processing unit 501 and communication unit 502 are similar, and are not described in detail below. Wherein:

a processing unit 501, configured to obtain alarm information in first data of a to-be-released version by using a scanning tool, where the scanning tool is configured to scan defects in the first data, the alarm information is used to indicate an alarm occurring in at least one line of the first data, and the alarm information corresponds to the line in which the alarm occurs in the first data;

the processing unit 501 is further configured to combine the same alarms in the alarm information of the version to be issued, and add module information to the alarm information of the version to be issued, where the module information includes information of responsible persons corresponding to the row in which the alarm occurs in the first data;

the processing unit 501 is further configured to compare whether the same alarm occurs in the alarm information of the to-be-released version and the alarm information of the historical version, and if the same alarm occurs, add a research and development analysis conclusion to a row corresponding to the same alarm in the alarm information of the to-be-released version; if the same alarm does not appear, the alarm appearing in the version to be released is reserved;

the processing unit 501 is further configured to output alarm information to be analyzed by the responsible person in the first data of the version to be issued.

Optionally, the processing unit 501 may be configured to output, through the communication unit 502, alarm information to be analyzed by the responsible person in the first data of the version to be issued.

For example, the processing unit may output the alarm information analyzed by the person to be responsible to a corresponding terminal device or a corresponding electronic mailbox through the communication unit.

Optionally, the processing unit 501 may also be configured to output, through the display screen, alarm information to be analyzed by the responsible person in the first data of the version to be issued. The display screen may be included in the alarm processing device (not shown in fig. 5) shown in fig. 5, or may be a display screen of another device, and the like, which is not limited in this embodiment of the application.

Optionally, the processing unit 501 is configured to merge the same alarms in the alarm information of the to-be-released version, where the merging includes: merging the same alarms in the alarm information of the version to be issued according to first information, wherein the first information comprises any one or more of a file name, a line number or an alarm number;

the processing unit 501, configured to compare whether the alarm information of the to-be-released version and the alarm information of the historical version have the same alarm, includes: and comparing whether the alarm information of the version to be released and the alarm information of the historical version have the same alarm or not according to second information, wherein the second information comprises a file name and/or an alarm number.

Optionally, the processing unit 501 is further configured to merge the alarms belonging to the same version in the historical versions according to the first information; merging the alarms belonging to different versions in the historical version according to the second information, simultaneously determining whether the responsible person corresponding to the alarm belonging to the newer version in different versions in the historical version needs to be updated, and updating the responsible person corresponding to the alarm belonging to the newer version in different versions in the historical version under the condition that the responsible person needs to be updated; and determining the alarm information of the historical version.

Optionally, the processing unit 501 is further configured to determine whether the modification time of the line in which the alarm occurs in the first data is within one year; if the number of the line in which the alarm appears in the first data is not within one year, determining the latest submitter of the line in which the alarm appears in the first data, and if the latest submitter meets preset conditions, configuring whether to search a next-time submitter of the line in which the alarm appears in the first data, wherein the preset conditions comprise any one or more of people who leave the job, people who are appointed to fail to submit or people located at a target job; if the second-time new submitter of the row with the alarm in the first data is searched for in a configuration mode, determining the second-time new submitter of the row with the alarm in the first data; if the second-time new submitter does not meet the preset condition, determining that the second-time new submitter is a responsible person corresponding to the row with the alarm in the first data; and if the next new submitter meets the preset condition, determining that the previous-level concerned person of the latest submitter is the responsible person corresponding to the row with the alarm in the first data.

Optionally, the processing unit 501 is further configured to delete the alarm that the alarm conclusion in the alarm information of the to-be-distributed version is false alarm or ignored alarm.

It is understood that the above descriptions of the processing unit 501 and the communication unit 502 are only examples, and reference may also be made to the above descriptions for the specific descriptions of the respective units, which are not repeated herein.

Fig. 6 is a schematic structural diagram of another alarm processing apparatus according to an embodiment of the present application, which is used to implement the methods shown in fig. 1 to fig. 4. The alert processing apparatus 600 may be a computer or an apparatus for a computer. The apparatus for a computer may be a system-on-a-chip or a chip. The chip system may be composed of a chip, or may include a chip and other discrete devices.

The alarm processing apparatus 600 includes at least one processor 620, which is configured to implement the alarm processing method provided in the embodiment of the present application. The apparatus 600 may further include a communication interface 610 for implementing transceiving operations of a computer in the method provided by the embodiment of the present application. In the embodiment of the present Application, the Processor 620 may be a Central Processing Unit (CPU), and the Processor may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field-Programmable Gate arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. In an embodiment of the present application, the communication interface 610 may be a transceiver, circuit, bus, module, or other type of communication interface for communicating with other devices over a transmission medium. For example, communication interface 610 enables an apparatus in apparatus 600 to communicate with other devices. The processor 620 utilizes the communication interface 610 to send and receive data (e.g., obtain the first data of the version to be released through the communication interface 610, etc.), and is configured to implement the method described in fig. 1 to fig. 4 of the above method embodiments.

The alert processing apparatus 600 may also include at least one memory 630 for storing program instructions and/or data. The memory 630 is coupled to the processor 620. The coupling in the embodiments of the present application is an indirect coupling or a communication connection between devices, units or modules, and may be an electrical, mechanical or other form for information interaction between the devices, units or modules. The processor 620 may operate in conjunction with the memory 630. Processor 620 may execute program instructions stored in memory 630. At least one of the at least one memory may be included in the processor.

Alternatively, when the alarm processing device 600 is powered on, the processor 620 may read the software program in the memory 630, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor 620 performs baseband processing on the data to be sent, and outputs a baseband signal to a radio frequency circuit (not shown), and the radio frequency circuit performs radio frequency processing on the baseband signal and sends the radio frequency signal to the outside in the form of electromagnetic waves through an antenna. When data is transmitted to the apparatus 600, the rf circuit receives an rf signal through the antenna, converts the rf signal into a baseband signal, and outputs the baseband signal to the processor 620, and the processor 620 converts the baseband signal into data and processes the data.

In another implementation, the rf circuit and antenna may be provided independently of the processor 620 performing baseband processing, for example, in a distributed scenario, the rf circuit and antenna may be arranged remotely from the alarm processing device.

The specific connection medium among the communication interface 610, the processor 620 and the memory 630 is not limited in the embodiments of the present application. In the embodiment of the present application, the memory 630, the processor 620, and the communication interface 610 are connected by the bus 640 in fig. 6, the bus is represented by a thick line in fig. 6, and the connection manner between other components is merely illustrative and not limited. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 6, but this is not intended to represent only one bus or type of bus.

It should be noted that, the alarm processing apparatus may perform the relevant steps in the foregoing method embodiments, and specific reference may be made to implementation manners provided by the foregoing steps, which are not described herein again.

For each device and product applied to or integrated with the alarm processing device, each module included in the device and product may be implemented by hardware such as a circuit, different modules may be located in the same component (e.g., a chip, a circuit module, etc.) or different components in the terminal, or at least a part of the modules may be implemented by a software program running on a processor integrated in the terminal, and the rest (if any) part of the modules may be implemented by hardware such as a circuit.

The memory may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of Random Access Memory (RAM) are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and direct bus RAM (DR RAM).

The embodiment of the application provides a chip. The chip includes: a processor and a memory. The number of processors may be one or more, and the number of memories may be one or more. The processor may perform the above-described methods as shown in fig. 1-4, and the steps performed by the related embodiments, by reading instructions and data stored on the memory.

As shown in fig. 7, fig. 7 is a schematic structural diagram of a module device according to an embodiment of the present disclosure. The modular apparatus 700 can perform the relevant steps in the foregoing method embodiments, and the modular apparatus 700 includes: a communication module 701, a power module 702, a memory module 703 and a chip module 704. The power module 702 is used for providing power for the module device; the storage module 703 is used for storing data and instructions; the communication module 701 is used for performing internal communication of module equipment or for performing communication between the module equipment and external equipment; the chip module 704 may perform the method described above with reference to fig. 1-4.

It is understood that the detailed description of the chip module 704 may refer to the method shown in fig. 1 to 4, or may refer to the alarm processing device shown in fig. 5, and will not be described in detail here.

The embodiment of the application also provides a computer readable storage medium. The computer readable storage medium stores a computer program comprising program instructions that, when executed by a processor, perform the method of fig. 3 or 4, and the steps performed by the related embodiments.

The computer readable storage medium may be an internal storage unit of the terminal device or the network device according to any of the foregoing embodiments, for example, a hard disk or a memory of the device. The computer readable storage medium may also be an external storage device of the terminal device or the network device, such as a plug-in hard disk, a Smart Memory Card (SMC), a Secure Digital (SD) card, a flash card (flash card), and the like, which are equipped on the device. Further, the computer-readable storage medium may also include both an internal storage unit and an external storage device of the terminal device or the network device. The computer-readable storage medium is used for storing the computer program and other programs and data required by the terminal device or the network device. The computer readable storage medium may also be used to temporarily store data that has been output or is to be output. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more collections of available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a Digital Video Disk (DVD)), or a semiconductor medium. The semiconductor medium may be a solid state disk.

The above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product comprises one or more computer instructions or computer programs. The procedures or functions according to the embodiments of the present application are wholly or partially generated when the computer instructions or the computer program are loaded or executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire or wirelessly.

It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

In the several embodiments provided in the present application, it should be understood that the disclosed method, apparatus and system may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative; for example, the division of the unit is only a logic function division, and there may be another division manner in actual implementation; for example, various elements or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be physically included alone, or two or more units may be integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute some steps of the methods according to the embodiments of the present invention.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.

While the foregoing is directed to embodiments of the present invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof, and the scope thereof is determined by the claims that follow.

Claims

1. An alarm processing method, characterized in that the method comprises:

2. The method according to claim 1, wherein the merging the same alarms in the alarm information of the to-be-released version comprises:

3. The method according to claim 1 or 2, wherein before the comparing whether the same alarm occurs in the alarm information of the to-be-released version and the alarm information of the historical version, the method further comprises:

and determining the alarm information of the historical version.

4. The method according to claim 1 or 2, wherein the information of the responsible person corresponding to the line in the first data where the alarm occurs comprises any one or more of the following items:

5. The method of claim 1 or 2, wherein the module information further comprises any one or more of:

6. The method according to claim 1 or 2, characterized in that the method further comprises:

7. The method according to claim 1 or 2, wherein before outputting the alarm information to be analyzed by the responsible person in the first data of the to-be-published version, the method further comprises:

and deleting the alarm conclusion in the alarm information of the version to be issued, wherein the alarm conclusion is a false alarm or an ignored alarm.

8. An alert processing apparatus, characterized in that the apparatus comprises means for performing the method according to any of claims 1-7.

9. An alarm processing device, characterized in that the device comprises a processor and a memory, the processor and the memory being interconnected, wherein the memory is adapted to store a computer program, and the processor is configured to invoke the computer program such that the method according to any of claims 1 to 7 is performed.

10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a processor, causes the processor to carry out the method according to any one of claims 1 to 7.