JP6665576B2 - Support device, support method, and program - Google Patents

Description

  The present invention relates to a support device, a support method, and a program.

  In software development, a source code static verification tool may be used. In this case, the verification of the source code using the static verification tool is performed as follows, for example. The source code is modified by the developer based on the result of the verification by the static verification tool. Then, after the source code is corrected, verification is again performed by the static verification tool as necessary, and it is confirmed that the problem pointed out by the static verification tool has been corrected.

  Patent Literature 1 describes a technology related to a determination work support system. In the determination work support system described in Patent Literature 1, information relating to the occurrence of a problem such as an assignment process or a conditional branch is extracted for each indication based on information considered to be a clone code for the indication of the verification result. Then, in the determination work support system described in Patent Document 1, the similar indications of the verification results are unified in advance by using the processing related to the similarity of the code and the occurrence of the problem, and when the user examines the indications, the similar indications are the same. Processed to result in scrutiny.

  Patent Literature 2 describes a technique related to a program improvement support system. The system described in Patent Literature 2 easily and, in some cases, with an appropriate evaluation, corrects a specific program correction method capable of eliminating a warning based on a static analysis result of an arbitrarily created program. Be able to grasp.

  Patent Literature 3 describes a technique relating to a static analysis device of a source code. In the apparatus described in Patent Literature 3, an analysis target source code generation unit generates a re-analysis source code in which a corrected portion is extracted from the target source code with reference to an analysis result obtained in a previous analysis, and performs static analysis. The section performs analysis of the source code for re-analysis.

JP 2012-256220A JP 2013-20519 A JP 2013-149134 A

  When the source code is corrected based on the result of the verification by the static verification tool, a new defect may occur due to the correction. The newly generated defect may be detected when the verification is performed again by the static verification tool.

  However, in the technology described in each patent document, when a new defect occurs due to the correction of the source code, information on indication of a static verification tool related to the correction that caused the defect is not provided. . That is, information indicating whether a new defect has occurred due to correction of any of the indications included in the initial verification result is not provided. Therefore, it may be difficult to efficiently correct or analyze a defect included in the source code using the technology described in each patent document.

  The present invention has been made to solve the above problems, and has as its main object to provide a support device or the like that enables efficient correction and analysis of a defect included in a source code.

  The support device according to one aspect of the present invention includes a first verification result and the corrected source based on a first verification result verified by a static verification tool on a source code and a corrected source code. First indication information generating means for generating first indication information including correspondence information indicating a correspondence with a code, and a correction related to a second verification result verified by the static verification tool on the corrected source code Second pointing information generating means for generating second pointing information including post information, and analyzing means for analyzing the association between the corresponding information and the corrected information based on the first and second pointing information. Prepare.

  The support method according to one aspect of the present invention includes a first verification result and a corrected source code based on a first verification result verified by a static verification tool on source code and a corrected source code. Generating first indication information indicating a correspondence with the code, generating second indication information including corrected information on a second verification result verified by the static verification tool on the corrected source code; The association between the correspondence information and the corrected information is analyzed based on the first and second indication information.

  The program according to one aspect of the present invention has the computer verify and correct the first verification result based on the first verification result verified by the static verification tool on the source code and the corrected source code. A process of generating first indication information including correspondence information indicating a correspondence with a source code, and a second process including corrected information on a second verification result obtained by a static verification tool verifying the corrected source code. And a process of analyzing the association between the correspondence information and the corrected information based on the first and second indication information.

  According to the present invention, it is possible to provide a support device or the like that enables efficient correction and analysis of a defect included in a source code.

It is a figure showing composition of a support device in a 1st embodiment of the present invention. It is a figure showing other composition of a support device in a 1st embodiment of the present invention. It is a figure showing the example of the 1st indication information generated by the support device in a 1st embodiment of the present invention. FIG. 5 is a diagram illustrating an example of second indication information generated by the support device according to the first embodiment of the present invention. 5 is a flowchart illustrating an operation of the support device according to the first exemplary embodiment of the present invention. It is a flowchart which shows operation | movement of the 1st indication information generation part with which the support apparatus in the 1st Embodiment of this invention is provided. It is a flowchart which shows operation | movement of the 2nd indication information production part with which the support apparatus in the 1st Embodiment of this invention is provided. 5 is a flowchart illustrating an operation of an analysis unit included in the support device according to the first embodiment of the present invention. FIG. 4 is a diagram illustrating an example of analyzed indication information generated by the support device according to the first embodiment of the present invention. FIG. 1 is a diagram illustrating an example of an information processing device that realizes a support device and the like in an embodiment of the present invention.

  Each embodiment of the present invention will be described with reference to the accompanying drawings. In each embodiment of the present invention, each component of each device (system) indicates a block of a functional unit. Some or all of the components of each device (system) are realized by, for example, an arbitrary combination of an information processing device 500 and a program as shown in FIG. The information processing device 500 includes, for example, the following configuration.

・ CPU (Central Processing Unit) 501
・ ROM (Read Only Memory) 502
・ RAM (Random Access Memory) 503
A program 504 loaded into the RAM 503
A storage device 505 for storing the program 504
A drive device 507 for reading and writing the recording medium 506
A communication interface 508 connected to the communication network 509
An input / output interface 510 for inputting / outputting data
A bus 511 for connecting each component
Each component of each device in each embodiment is realized by the CPU 501 acquiring and executing a program 504 that realizes these functions. The program 504 for realizing the function of each component of each device is stored in advance in, for example, the storage device 505 or the RAM 503, and is read by the CPU 501 as necessary. The program 504 may be supplied to the CPU 501 via the communication network 509, or may be stored in the recording medium 506 in advance, and the drive device 507 may read the program and supply it to the CPU 501.

  There are various modifications of the method of realizing each device. For example, each device may be realized by an arbitrary combination of a separate information processing device 500 and a program for each component. Also, a plurality of components included in each device may be realized by an arbitrary combination of one information processing device 500 and a program.

  In addition, a part or all of each component of each device is realized by a general-purpose or dedicated circuit, a processor, or a combination thereof. These may be constituted by a single chip, or may be constituted by a plurality of chips connected via a bus. Some or all of the components of each device may be realized by a combination of the above-described circuit and the like and a program.

  When a part or all of each component of each device is realized by a plurality of information processing devices or circuits, the plurality of information processing devices or circuits may be centrally arranged or distributed. Is also good. For example, the information processing device, the circuit, and the like may be realized as a form in which each is connected via a communication network, such as a client and server system or a cloud computing system.

  First, a first embodiment of the present invention will be described. FIG. 1 is a diagram illustrating a support device according to the first embodiment of the present invention.

  As shown in FIG. 1, the support device 100 according to the first embodiment of the present invention includes a first indication information generation unit 110, a second indication information generation unit 120, and an analysis unit 130. The first indication information generation unit 110 generates the first verification result and the corrected source code based on the first verification result verified by the static verification tool on the source code and the corrected source code. And generating first indication information including correspondence information indicating the correspondence with the first point. The second indication information generation unit 120 generates second indication information including post-correction information relating to a second verification result of the corrected source code verified by the static verification tool. The analysis unit 130 analyzes the association between the correspondence information and the corrected information based on the first and second indication information.

  In the present embodiment, each of the first verification result 11 and the second verification result 12 includes a result obtained by performing a verification on a source code by a static verification tool (not shown). The static verification tool is a tool for mainly analyzing a source code of a program and analyzing for a problem. The static verification tool refers to the source flow of the program and verifies the data flow of the program, the set data, values, structure, and the like, thereby verifying whether there is a problem in the program. That is, the static verification tool verifies whether there is a problem in the program without executing the executable file of the program. In the static verification tool, a technique called a formal method is used.

  Each of the first verification result 11 and the second verification result 12 includes an indication indicating details of each of the problems detected by the static verification tool. The indication is composed of an identification number for distinguishing the problem, the type of the problem, information on a location in the source code that caused the problem, and the like. The information of the location causing the problem includes, for example, a file name, a line number, a function name, and a variable name of the source code, but may be other information. The number of indications included in each of the first verification result 11 and the second verification result 12 is not particularly limited.

  Note that the support device 100 may have a configuration as shown in FIG. That is, the support device 100 includes a first indication information storage unit 111 and a second indication information storage unit 121 in addition to the configuration illustrated in FIG. The first indication information storage unit 111 stores the first indication information described above. The second indication information storage unit 121 stores the above-mentioned second indication information. The first indication information storage unit 111 and the second indication information storage unit 121 are each realized by the storage device 505 included in the information processing apparatus 500 illustrated in FIG. 10 described above.

  Next, each component of the support device 100 according to the first embodiment of the present invention will be described.

  The first indication information generation unit 110 generates first indication information based on the first verification result 11 and the corrected source code. The first verification result 11 is a result of the verification performed by the static verification tool on the source code to be verified. Further, the corrected source code is a source code in which a defect pointed out by a static verification tool has been corrected with respect to the source code to be verified.

  In the present embodiment, it is assumed that the information on the correction of the corrected source code is managed by the configuration management information 12 shown in FIG. That is, the configuration management information 12 includes the source code and its source code name to be verified by the static verification tool, and information about the location where the source code is corrected and its line number when the source code is corrected. included. The information relating to the corrected portion of the source code includes, for example, a difference between the corrected source code and the source code before the correction. Then, the first indication information generation unit 110 generates the first indication information by using, as an example, information on a correction location managed by the configuration management information 12 as the corrected source code. The configuration management information 12 may be managed by, for example, a source code version management system or the like.

  The first indication information indicates a correspondence between each indication included in the first verification result and the corrected source code. The first indication information includes correspondence information that is information on the correspondence. That is, when the source code is corrected according to each of the problems in the source code indicated by the indication included in the first verification result 11, the corresponding information included in the first verification result 11 The following shows the correspondence with the corrected part of the source code. Note that the number of pieces of correspondence information included in the first indication information is not particularly limited, and changes according to the indication included in the first indication information 11.

  FIG. 3 shows an example of the first indication information. The first indication information shown in FIG. 3 is the first indication information relating to one indication among the first verification results 11 verified by the static verification tool. That is, the first indication information shown in FIG. 3 includes one piece of correspondence information. In the example of the first indication information illustrated in FIG. 3, each item of “file name”, “function name”, and “variable name” is information mainly included in the first verification result 11. The “line added by modification” and “line number” items are mainly information on the modified source code. When a plurality of indications are included in the first verification result 11, the same first indication information is generated for each of the plurality of indications.

  In the example illustrated in FIG. 2, “file name” indicates a file name of a source code in which a location causing a problem corresponding to the indication exists. Similarly, the “function name” indicates the name of the function in which the part causing the problem exists. The “variable name” indicates a variable name of a variable related to the question. The “line added by the correction” indicates a portion corrected in the source code when the problem is corrected in response to the indication. The source code indicated in this column may be a portion where the original source code is changed when the problem is corrected, or a portion newly added to the source code to correct the problem. “Line number” indicates the number of the place where the above-mentioned “line added by correction” exists in the corrected source code. The "variable use presence / absence" indicates whether the variable indicated in the "variable name" column is used for each "line added by correction" of the source code. Whether or not a variable is used is determined based on whether the variable indicated in the column of “variable name” is referred to or substituted in each of the “line added by modification”. In the example illustrated in FIG. 3, in the line with the line number “10”, there is a reference to the variable str indicated as “variable name”, and thus “variable use” is set to “Yes”. Further, in the rows with the row numbers “11” and “12”, there is no assignment or reference to the variable str indicated as “variable name”, so “variable use presence” is set to “none”.

  The first indication information generation unit 110 generates the first indication information based on the correspondence between the identification number of the indication detected by the static verification tool and the identification number given to the correction of the source code. Generate. That is, when the identification number of the indication detected by the static verification tool matches the identification number assigned to the correction of the source code, the first indication information generation unit 110 Based on this, the corresponding information of the first indication information as described above is generated.

  As an example, when the identification numbers match, the first indication information generation unit 110 determines, based on the first verification result 11, the “file name”, The information about each term of "function name" and "variable name" is generated. In addition, the first indication information generation unit 110, based on the information related to the correction of the corrected source code included in the configuration management information 12, among the corresponding information included in the first indication information, “added by correction. Generate information about the "line" and "line number" terms.

  At the same time, the first indication information generating unit 110 refers to the information on the “variable name” and the “line added by modification” to generate information on the “variable use presence / absence” term. In other words, the first indication information generation unit 110 sets “variable use presence” to “Yes” when the variable indicated by “variable name” is used in “line added by correction”. . When the variable indicated by “variable name” is not used in the “line added by modification”, the first indication information generating unit 110 sets “variable use presence” to “none”. .

  In the present embodiment, when the source code is corrected, it is assumed that the identification number of the indication corresponding to the correction is attached to each of the correction points of the source code. As an example, when the corrected source code is committed to the version control system, the identification number is described as a comment at the time of commit by the person in charge of modification or the person in charge of commit.

  The first indication information generated by the first indication information generation unit 110 is appropriately sent to the analysis unit 130 described later. Further, as shown in FIG. 2, when the first indication information storage unit 111 is provided, the first indication information generation unit 110 stores the first indication information in the first indication information storage unit. 111. In this case, the analysis unit 130 reads and uses the first indication information stored in the first indication information storage unit 111 as necessary.

  The second indication information generation unit 120 generates second indication information based on the second verification result 13. The second indication information includes corrected information on each of the indications included in the second verification result 13. The second verification result 13 is a result of verification performed by the static verification tool on the corrected source code when the source code is corrected based on the first verification result 11. The second verification result 13 includes the same type of information as the first verification result 11. The number of post-correction information included in the second indication information changes according to the indication included in the second verification result 13.

  Each of the information included in the second indication information includes the same information as the indication included in the second verification result 13. In addition, each of the post-correction information included in the second indication information includes, as to the variable that caused the problem corresponding to each of the indications included in the second verification result 13, information on whether or not the variable is used. Is included.

  FIG. 4 shows an example of the second indication information. The second indication information shown in FIG. 4 is the corrected information on one indication among the second verification results 13 verified by the static verification tool. In the example of the second indication information illustrated in FIG. 4, each item except the item of “variable use presence / absence” is information mainly included in the second verification result 13. In addition, in the example of the second indication information illustrated in FIG. 4, each item except “pointing trace” and “variable usage” indicates the same information as the item of the same name included in the first indication information. .

  The “pointing trace” section indicates a part of the source code related to the pointing contained in the second verification result 13. Specifically, the “pointing trace” indicates a part of the source code related to the assignment or reference of the value to the variable indicated by the pointing included in the second verification result 13. The "variable use presence / absence" section indicates whether or not the variable indicated in the "variable name" column is used for each "pointing trace" of the source code. Whether or not a variable is used is determined based on whether or not a variable is referenced or substituted in the “pointing trace”, as in the “variable usage” section in the first indication information.

  The second indication information generation unit 120, based on the indication included in the second verification result 13, relates to each of the post-correction information included in the second indication information, except for the term “variable use”. Generate information. In addition, the second indication information generation unit 120 generates information regarding the “variable use presence / absence” term based on the “variable name” and “indication trace” terms of the corrected information included in the second indication information. I do.

  The second indication information generated by the second indication information generation unit 120 is appropriately sent to the analysis unit 130. As shown in FIG. 2, when the second indication information storage unit 121 is provided, the first indication information generation unit 120 stores the second indication information in the second indication information storage unit. 121. In this case, the analysis unit 130 reads and uses the second indication information stored in the second indication information storage unit 121.

  The analysis unit 130 analyzes the association between the first indication information and the second indication information. That is, the analysis unit 130 analyzes whether or not there is corresponding information related to the first indication information for each of the post-correction information included in the second indication information. For each piece of correspondence information included in the second indication information, if there is corresponding information of the related first indication information, the correspondence information is caused by the correction of the source code based on the first verification result 11. Can be determined to be related to the malfunction that has occurred.

  As an example, the analysis unit 130 determines, for each of the post-correction information included in the second indication information, whether or not the relationship between the indication and the indication included in the first indication information satisfies a predetermined condition. Then, it is analyzed whether or not there is an indication related to the first indication information. That is, the analyzing unit 130 determines the predetermined relationship for each of the post-correction information included in the second indication information by determining whether or not there is corresponding information of the first indication information that matches each item of the indication. It is determined whether or not the condition is satisfied.

  As an example, the analysis unit 130 determines whether the contents of the corresponding information of the first indication information shown in FIG. 3 and the items having the same name of the corrected information of the second indication information shown in FIG. 4 match each other. I do. In addition, the analysis unit 130 adds the “line added by correction” included in the first indication information shown in FIG. 3 to the content of the “indication trace” included in the second indication information shown in FIG. It is determined whether or not the contents of the item are included. Then, when the contents match for all items, the analysis unit 130 analyzes that the indication included in the second indication information is a defect caused by the correction of the source code based on the first verification result.

  Note that, in the present embodiment, the analysis unit 130 analyzes a defect related to the same variable caused by the correction of the source code.

  FIG. 9 illustrates an example in which the analysis unit 130 determines the correspondence information included in the first indication information illustrated in FIG. 3 and the corrected information included in the second indication information illustrated in FIG. The analysis unit 130 first determines whether the file names match. In the example illustrated in FIG. 9, the “file name” included in the corresponding information of the first indication information and the “file name” included in the corrected information of the second indication information are both “a.java”. Yes, matches. Therefore, the analysis unit 130 determines that the file names match, for example. Similarly, the analysis unit 130 determines that the items of “function name” and “variable name” also match.

  In the “pointing trace” in the information after the modification of the second pointing information, there is a line included in the “line pointed out by the correction” in the corresponding information of the first pointing information. Therefore, the analysis unit 130 determines that the “pointed-out trace” includes a line included in the “line pointed out by the correction” in the first pointed-out information. When the analysis unit 130 determines that a line included in the “line pointed out by the correction” exists in the “pointed-out trace”, the analysis unit 130 determines “line number” and “variable usage” for the information of the line to be determined. "Existence" is determined. In the example illustrated in FIG. 9, for the line “if (str == null) ｛”, it is determined that the “line number” matches the “variable use presence”. In this case, the analysis unit 130 determines that both match.

  That is, in the example shown in FIG. 9, the contents of the corresponding information included in the corresponding information included in the first indication information shown in FIG. 3 and the corresponding items of the post-correction information included in the second indication information shown in FIG. I do. Therefore, the analyzing unit 130 analyzes the post-correction information included in the second indication information shown in FIG. 4 that the first indication information includes the corresponding information. That is, the analysis unit 130 determines that the post-correction information included in the second indication information shown in FIG. 4 is a defect resulting from the correction of the source code based on the first verification result shown in FIG.

  At the time of the above-described analysis, the analysis unit 130 analyzes the corrected information, which is determined to be a defect resulting from the correction of the source code based on the first verification result, among the corrected information included in the second indication information. Specified as pointed information. The identified analyzed indication information is separated from other corrected information included in the second indication information. The analyzed indication information is stored in, for example, a buffer (not shown) or the like. The analysis unit 130 may output, in the form of a list, the analyzed pointed information determined to be a defect resulting from the correction of the source code based on the first verification result.

  For example, the analysis unit 130 may output a file in which a list of analyzed indication information determined to be a defect resulting from the correction of the source code based on the first verification result is described. Alternatively, the analysis unit 130 may output, to a display device (not shown), a list of analyzed indication information determined to be a defect resulting from the correction of the source code based on the first verification result. The analysis unit 130 may output a list of the post-correction information together with the indication output from the static verification tool.

  Next, an example of the operation of the support apparatus 100 according to the first embodiment of the present invention will be described using the flowcharts shown in FIGS. First, the outline of the operation of the support device 100 in the present embodiment will be described using the flowchart shown in FIG.

  First, the first indication information generation unit 110 generates first indication information (Step S11). When the support device 100 includes the first indication information storage unit 111, the generated first indication information may be stored in the first indication information storage unit 111 as needed. An example of a detailed operation of the first indication information generation unit 110 in this step will be described later.

  Next, the second indication information generation unit 120 generates first indication information (Step S12). When the support device 100 includes the second indication information storage unit 121, the generated second indication information may be stored in the second indication information storage unit 121 as needed. An example of the detailed operation of the second indication information generation unit 120 in this step will be described later.

  Next, the analysis unit 130 analyzes the association between the first indication information generated in step S11 and the second indication information generated in step S12 (step S13). An example of a detailed operation of the analysis unit 130 in this step will be described later. In addition, the result of the analysis is output as necessary via an output unit (not shown).

  Next, an example of the operation of the first indication information generation unit 110 included in the support device 100 according to the present embodiment will be described with reference to the flowchart illustrated in FIG.

  First, the first indication information generation unit 110 acquires a first verification result output when the static verification tool verifies the source code (step S101). Then, the first indication information generating unit 110 acquires each indication information included in the first verification result.

  Subsequently, the first indication information generation unit 110 acquires information on the corrected source code (Step S102). That is, the first indication information generation unit 110 obtains information on the corrected part of the source code from the configuration management information 12.

  Subsequently, the first indication information generation unit 110 generates first indication information based on the indication information included in the first verification result and the information on the correction part of the source code (Step S103). The first indication information generation unit 110 obtains correspondence between the indication information included in the first verification result and the corrected part of the source code based on the identification number or the like, and obtains the correspondence information included in the first indication information. Generate each of

  When the support device 100 includes the first indication information storage unit 111, the first indication information generation unit 110 may store the first indication information generated in step S103 as necessary in the first indication information. The information is stored in the indication information storage unit 111 (step S104). When the support device 100 does not include the first indication information storage unit 111, the first indication information generation unit 110 may not perform the process of this step.

  Next, an example of the operation of the second indication information generation unit 120 included in the support device 100 according to the present embodiment will be described using the flowchart illustrated in FIG.

  First, the second indication information generating unit 120 acquires the second verification result 13 output when the static verification tool verifies the corrected source code (step S201).

  Subsequently, the second indication information generation unit 120 generates second indication information based on the second verification result obtained in step S201 (step S202).

  When the support device 100 includes the second pointing information storage unit 121, the second pointing information generating unit 120 may store the second pointing information generated in step S202 as needed in the second pointing information storage unit 121. It is stored in the indication information storage unit 121 (step S203). When the support device 100 does not include the second indication information storage unit 121, the second indication information generation unit 120 may not perform the process of this step.

  Next, an example of the operation of the analysis unit 130 included in the support device 100 according to the present embodiment will be described using the flowchart illustrated in FIG.

  The analysis unit 130 acquires the first indication information generated by the first indication information generation unit 110 (Step S301). As illustrated in FIG. 2, when the support device 100 includes the first indication information storage unit 111, the analysis unit 130 acquires the first indication information stored in the first indication information storage unit 111. You may.

  Subsequently, the analysis unit 130 acquires the second indication information generated by the second indication information generation unit 120 (Step S302). As illustrated in FIG. 2, when the support device 100 includes the second indication information storage unit 121, the analysis unit 130 acquires the second indication information stored in the first indication information storage unit 121. You may.

  Subsequently, the analysis unit 130 analyzes whether the relationship between the first indication information and the second indication information satisfies a predetermined condition (step S303). That is, the analysis unit 130 determines, for each of the indications included in the second indication information, whether or not there is an indication of the first indication information that matches each item of the indication.

  When the relationship between the first indication information and the second indication information satisfies a predetermined condition (Step S303: Yes), the analysis unit 130 proceeds to the processing of Step S304. That is, when there is an indication of the first indication information that matches each item of the indication with respect to the indication included in the second indication information, the analysis unit 130 analyzes the second indication by the analyzed indication. Classify the information and update the analyzed indication information. When the processing of step S304 ends, the analysis unit 130 subsequently performs the processing of step S305.

  When the relationship between the first indication information and the second indication information satisfies a predetermined condition (step S303: No), the analysis unit 130 does not perform the processing of step S304. Step S305 is performed.

  In step S305, when the analysis has been completed for all of the first indication information and the second indication information (step S306: Yes), the analysis unit 130 outputs the analyzed indication information to an output unit (not shown) or the like. (Step S307). When the analysis of all the information is not completed (Step S306: No), the analysis unit 130 returns to Step S301 and repeats the analysis again for the other first indication information.

  As described above, in the support device 100 according to the first embodiment of the present invention, the analysis unit 130 analyzes the association with the first and second indication information based on the first and second indication information. In other words, the support apparatus 100 determines and classifies, among the second indication information, information in which the first indication information and the content of each item included in each indication match.

  As described above, the first indication information indicates a relationship between a verification result by the static verification tool and a correction made to the source code according to the verification result. The second verification result indicates the verification result of the corrected source code by the static verification tool. That is, the classified indication is a defect resulting from the correction of the source code based on the first verification result. By dividing the second verification result, the source code is corrected based on the verification result of the static verification tool, and if the corrected source code is verified again by the static verification tool, the source code is corrected. This makes it possible to determine the fault that has occurred.

  Therefore, the support device 100 according to the present embodiment enables efficient correction and analysis of a defect included in the source code.

  As described above, the present invention has been described with reference to the exemplary embodiments. However, the present invention is not limited to the exemplary embodiments. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention. The configurations in the embodiments can be combined with each other without departing from the scope of the present invention.

11 first pointed information 12 configuration management information 13 second verification result 14 analyzed pointed information 100 support device 110 first pointed information generator 111 first pointed information storage 120 second pointed information generator 121 2 pointed information storage unit 130 analysis unit 500 information processing device 501 CPU
502 ROM
503 RAM
504 program 505 storage device 506 recording medium 507 drive device 508 communication interface 509 communication network 510 input / output interface 511 bus

Claims (8)

Based on a first verification result verified by a static verification tool on a source code and a corrected source code, correspondence information indicating a correspondence between the first verification result and the corrected source code is generated. First indication information generating means for generating first indication information including:
Aforementioned related to each of the static verification tool is the second indicating the location of at least modified more than a corresponding to the result of verification the verification result, positions and the modified one of the modifications to the modified source code A second indication information generating means for generating second indication information including post-correction information indicating the content of the part ;
An assisting apparatus comprising: an analyzing unit configured to analyze a relationship between the correspondence information and the corrected information based on the first and second indication information.   The support device according to claim 1, wherein the correspondence information indicates a correspondence with a corrected portion of the source code corrected according to the indication included in the first verification result.   The first indication information generating means is configured to determine a correspondence between identification information for identifying the indication included in the first verification result and an identification number assigned to the corrected portion of the corrected source code. The support device according to claim 2, wherein the first indication information is generated based on the first indication information.   The support device according to claim 1, wherein the analysis unit analyzes the association based on whether or not respective items of the correspondence information and the corrected information match.   The method according to claim 2, wherein the analysis unit determines that the corrected information indicates a defect caused by the correction of the corrected source code when the items of the correspondence information and the corrected information match. The support device as described.   The support device according to claim 5, wherein the analysis unit outputs the post-correction information determined to indicate a defect resulting from the correction of the corrected source code. Based on a first verification result verified by a static verification tool on a source code and a corrected source code, correspondence information indicating a correspondence between the first verification result and the corrected source code is generated. Generating first indication information including :
Aforementioned related to each of the static verification tool is the second indicating the location of at least modified more than a corresponding to the result of verification the verification result, positions and the modified one of the modifications to the modified source code Generating the second indication information including the corrected information indicating the content of the section ,
A support method for analyzing a relation between the correspondence information and the corrected information based on the first and second indication information. On the computer,
Based on a first verification result verified by a static verification tool on a source code and a corrected source code, correspondence information indicating a correspondence between the first verification result and the corrected source code is generated. Generating first indication information including:
Aforementioned related to each of the static verification tool is the second indicating the location of at least modified more than a corresponding to the result of verification the verification result, positions and the modified one of the modifications to the modified source code Processing for generating second indication information including post-correction information indicating the content of the part ;
A program for executing a process of analyzing a relationship between the correspondence information and the post-correction information based on the first and second indication information.

Images