JP6840966B2 - Reference information output program, reference information output method, and reference information output device - Google Patents

Description

This case, the reference information output program, FYI information output method, and a reference information output device.

Static analysis of source code is known (see, for example, Patent Document 1). Static analysis reveals various quality problems such as potential bugs in source code and violations of coding standards.

Japanese Unexamined Patent Publication No. 2013-134521

By the way, the various problems mentioned above are fed back to the source code developer as the check result of static analysis. The check results may contain not only useful points but also useless points. Useless points include, for example, points that are not important to the developer and points that do not need to be modified due to project circumstances.

For useless indications, the developer can apply for exclusion from the next check result. However, there is a problem that the developer has to check the check result individually and decide whether or not the exclusion application is necessary, which is troublesome.

Accordingly, in one aspect, an object of the invention to provide reference information output program that can output the information that can help with respect to exclusion applicant, FYI information output method, and the reference information output device.

In one embodiment, the reference information output program acquires the analysis result of the static analysis for the program layered by a plurality of layers, and the specific check contents included in the acquired analysis result correspond to the program. When displaying in association with the part to be checked, the storage unit in which the information of the exclusion application of the past check contents is stored is referred to, the exclusion application of the same type of check contents as the specific check contents is specified, and the same type of check contents is specified. According to the application result of the exclusion application of the check contents of the above, and the difference between the position of the specific check contents in the plurality of layers in the program and the position of the check contents of the same type in the plurality of layers. It is a reference information output program characterized by having a computer execute a process that outputs reference information regarding an exclusion application for a specific check content.

In one embodiment, the reference information output method acquires the analysis result of the static analysis for the program layered by a plurality of layers, and the specific check contents included in the acquired analysis result correspond to the program. When displaying in association with the part to be checked, the storage unit in which the information of the exclusion application of the past check contents is stored is referred to, the exclusion application of the same type of check contents as the specific check contents is specified, and the same type of check contents is specified. According to the application result of the exclusion application of the check contents and the difference between the position of the specific check contents in the plurality of layers and the position of the check contents of the same type in the plurality of layers in the program. This is a reference information output method characterized in that a computer executes a process that outputs reference information regarding an exclusion application for a specific check content.

In one embodiment, the reference information output device acquires the analysis result of the static analysis for the program layered by a plurality of layers, and the specific check contents included in the acquired analysis result correspond to the program. When displaying in association with the part to be checked, the storage unit in which the information of the exclusion application of the past check contents is stored is referred to, the exclusion application of the same type of check contents as the specific check contents is specified, and the same type of check contents is specified. According to the application result of the exclusion application of the check contents and the difference between the position of the specific check contents in the plurality of layers and the position of the check contents of the same type in the plurality of layers in the program. It is a reference information output device having a processing unit that executes processing, which outputs reference information regarding an exclusion application for a specific check content.

It is possible to output reference information regarding the exclusion application.

FIG. 1 is a diagram for explaining an example of a reference information output system. FIG. 2 is an example of the hardware configuration of the second server. FIG. 3 is an example of a functional block diagram of the first server. FIG. 4 is an example of a functional block diagram of the second server. FIG. 5 is an example of the check result table. FIG. 6 is an example of the exclusion rule table. FIG. 7 is an example of a functional block diagram of the development terminal. FIG. 8 is a flowchart showing an example of the operation of the first server. FIG. 9 is a flowchart showing an example of the operation of the second server. FIG. 10 is a flowchart showing an example of the operation of the development terminal. FIG. 11 is an example of an editor screen. FIG. 12 is a flowchart showing an example of the operation of the second server. FIG. 13 is a flowchart showing an example of the history analysis process. FIG. 14 is an example of a diagram illustrating the history analysis process. FIG. 15 is another example of the figure for explaining the history analysis process. FIG. 16 is a flowchart showing an example of the operation of the development terminal. FIG. 17 is an example of the exclusion application screen. FIG. 18 is a flowchart showing an example of the operation of the second server. FIG. 19 is a flowchart showing an example of the operation of the administrator terminal. FIG. 20 is an example of the exclusion application list screen. FIG. 21 is an example of the exclusion application confirmation screen.

Hereinafter, a mode for carrying out this case will be described with reference to the drawings.

FIG. 1 is a diagram for explaining an example of the reference information output system S. The reference information output system S is a computer system that outputs reference information that can be used as a reference for the exclusion application. The reference information output system S includes a plurality of development terminals 100, a first server 200, a second server 300 as a reference information output device, and an administrator terminal 400. Although the personal computer (PC) is shown as an example of the development terminal 100 and the administrator terminal 400 in FIG. 1, it may be a smart device such as a tablet terminal. Further, although a plurality of development terminals 100 are shown in FIG. 1, the number of development terminals 100 may be one. Further, a part of the plurality of development terminals 100 may be arranged in different buildings (for example, a building in a remote place).

The development terminal 100, the first server 200, the second server 300, and the administrator terminal 400 are connected to each other via the communication network NW. The communication network NW includes, for example, a wired network such as the Internet or a Local Area Network (LAN). A wireless network using radio waves may be used as a part of the communication network NW.

The development terminal 100 is used by a developer who creates source code. When the developer finishes creating or modifying the source code, the development terminal 100 transmits the source code to the first server 200 according to the instruction from the developer. The first server 200 executes static analysis on the source code. More specifically, when the source code is transmitted from the development terminal 100, the first server 200 receives and stores the source code. After receiving, the first server 200 periodically or irregularly executes static analysis on the source code by using various static analysis functions installed in itself, and checks the electronic file representing the analysis result. To upload to the second server 300.

The second server 300 stores the check result uploaded from the first server 200. In addition, the second server 300 outputs reference information that can be used as a reference for the exclusion application to the development terminal 100. More specifically, when the development terminal 100 requests the development terminal 100 to provide the check contents (specifically, the indication message), the second server 300 responds to the exclusion application made to the check result and the past check result. The reference information is specified by using the above, and the check contents and the specified reference information are combined and output to the development terminal 100. The developer confirms the check contents and reference information output to the development terminal 100, and determines whether or not to request the administrator to exclude the check contents. In particular, the reference information includes exclusion application recommendations and amendment recommendations. Exclusion application recommendations are information that recommends exclusion applications for specific check results. Correction recommendation is information that recommends correction of the corresponding part of the source code associated with a specific check result without making an exclusion application.

Therefore, if the exclusion application recommendation is output to the development terminal 100, the developer judges that it is highly likely that the exclusion application will be approved if the exclusion application is requested from the administrator because it is a useless indication. Will be done. On the contrary, if the correction recommendation is output to the development terminal 100, the developer judges that it is highly likely that the exclusion application will be returned even if the exclusion application is requested from the administrator because it is a useful indication, and the exclusion application is excluded. You will be able to correct the corresponding parts without making an application. This makes it possible to improve the quality of the source code at an early stage of development.

When the exclusion application is made on the development terminal 100, the development terminal 100 transmits the application content of the exclusion application to the second server 300. When the second server 300 receives the application content of the exclusion application, the second server 300 stores the received application content in a registration format called temporary registration. The administrator who manages the quality of the source code operates the administrator terminal 400 to display the application contents of the temporary registration on the administrator terminal 400, and approves and receives the application contents, or inserts without approval. Decide whether to return.

When the administrator performs an operation of approving the application contents to the administrator terminal 400, the administrator terminal 400 transmits information indicating approval to the second server 300. Then, when the second server 300 receives the information indicating approval, the application content of the provisional registration is updated to the application content of the main registration. Specifically, the second server 300 rewrites the registered contents from temporary registration to receipt. On the contrary, when the administrator performs an operation of returning the application contents to the administrator terminal 400, the administrator terminal 400 transmits information indicating the remand to the second server 300. Then, when the second server 300 receives the information indicating the remand, the second server 300 similarly updates the application content of the provisional registration to the application content of the main registration. Specifically, the second server 300 rewrites the registered contents from temporary registration to remand. As a result, the check result including receipt or remand is accumulated as a history in the second server 300 as a response to the exclusion application. Then, since this history is used as a past check result in the next exclusion application, highly accurate reference information is output as the number of times of use increases.

Hereinafter, the details of the development terminal 100, the first server 200, the second server 300, and the administrator terminal 400 described above will be described with reference to the drawings.

FIG. 2 is an example of the hardware configuration of the second server 300. Since the development terminal 100, the first server 200, and the administrator terminal 400 basically have the same configuration as the second server 300, the description thereof will be omitted.

The second server 300 includes at least a Central Processing Unit (CPU) 300A, a Random Access Memory (RAM) 300B, a Read Only Memory (ROM) 300C, and a network I / F (interface) 300D. The second server 300 may include at least one of a Hard Disk Drive (HDD) 300E, an input I / F 300F, an output I / F 300G, an input / output I / F 300H, and a drive device 300I, if necessary. The CPU 300A to the drive device 300I are connected to each other by the internal bus 300J. A computer is realized by at least the CPU 300A and the RAM 300B collaborating with each other.

An input device 710 is connected to the input I / F 300F. The input device 710 includes, for example, a keyboard and a mouse.
A display device 720 is connected to the output I / F 300G. The display device 720 includes, for example, a liquid crystal display.
A semiconductor memory 730 is connected to the input / output I / F 300H. Examples of the semiconductor memory 730 include a Universal Serial Bus (USB) memory and a flash memory. The input / output I / F 300H reads programs and data stored in the semiconductor memory 730.
The input I / F 300F and the input / output I / F 300H include, for example, a USB port. The output I / F 300G includes, for example, a display port.

A portable recording medium 740 is inserted into the drive device 300I. Examples of the portable recording medium 740 include removable discs such as Compact Disc (CD) -ROM and Digital Versatile Disc (DVD). The drive device 300I reads programs and data recorded on the portable recording medium 740.
The network I / F 300D includes, for example, a port and a Physical Layer Chip (PHY chip). The second server 300 is connected to the communication network NW via the network I / F 300D.

In the RAM 300B described above, the program stored in the ROM 300C or the HDD 300E is stored by the CPU 300A. The program recorded on the portable recording medium 740 is stored in the RAM 300B by the CPU 300A. When the CPU 300A executes the stored program, the second server 300 realizes various functions described later, and also executes various processes described later. The program may be adapted to the flowchart described later.

Subsequently, the function of the first server 200 will be described with reference to FIG.

FIG. 3 is an example of a functional block diagram of the first server 200. As shown in FIG. 3, the first server 200 includes a Git 210, a continuous integration unit 220, and a first information processing unit 230. In particular, the continuous integration unit 220 includes a static analysis unit 221 and the static analysis unit 221 includes a first static analysis unit 221A and a second static analysis unit 221B. On the other hand, the first information processing unit 230 includes the third static analysis unit 231.

Git210 is a type of version control system or repository. Therefore, when the source code SC is transmitted from the development terminal 100, the Git 210 stores the source code SC.
The continuous integration unit 220 provides functions such as source code inspection for improving quality at the time of source code creation and shortening the delivery time of the source code. Examples of the continuous integration unit 220 include Jenkins and Hudson (registered trademark). The continuous integration unit 220 acquires the source code SC from the Git 210 periodically or irregularly, and stores the acquired source code SC in the static analysis unit 221. For example, the continuous integration unit 220 acquires the source code SC when the source code SC is stored in the Git 210, or acquires the source code SC at a specific set time.

The first static analysis unit 221A and the second static analysis unit 221B execute different static analysis on the source code SC. For example, the first static analysis unit 221A discovers a coding standard violation by executing static analysis, and the second static analysis unit 221B discovers a defect such as a bug by executing static analysis. The first static analysis unit 221A includes, for example, CheckStyle (registered trademark). The second static analysis unit 221B includes, for example, FindBugs (registered trademark). The first static analysis unit 221A and the second static analysis unit 221B output the Extensible Markup Language (XML) format electronic files F1 and F2 representing the analysis results of the static analysis to the second server 300 as check results.

On the other hand, the first information processing unit 230 duplicates and acquires the source code SC stored in the static analysis unit 221. The third static analysis unit 231 executes a static analysis different from the above-mentioned first static analysis unit 221A and second static analysis unit 221B on the source code SC. The third static analysis unit 231 outputs a Comma-Separated Values (CSV) format electronic file F3 representing the analysis result of the static analysis to the second server 300 as a check result.

Subsequently, the functions of the development terminal 100 and the second server 300 will be described with reference to FIGS. 4 to 7.

FIG. 4 is an example of a functional block diagram of the second server 300. FIG. 5 is an example of the check result table T1. FIG. 6 is an example of the exclusion rule table T2. FIG. 7 is an example of a functional block diagram of the development terminal 100.

First, as shown in FIG. 4, the second server 300 includes a second information processing unit 310, a check result table T1, and an exclusion rule table T2. In particular, the second information processing unit 310 includes a check result registration unit 311, a check result search unit 312, a check result exclusion unit 313, an exclusion rule history analysis unit 314, an exclusion application provisional registration unit 315, and an exclusion application registration unit 316. I'm out.

The check result registration unit 311 stores the check result transmitted from the first server 200 in the check result table T1. As described above, since the check results are electronic files F1, F2, F3 in different formats, the check result registration unit 311 first collects the electronic files F1, F2, F3, and formats the electronic files F1, F2, F3. After preparing, it is stored in the check result table T1. As a result, the check result table T1 stores the check result of the static analysis executed for the source code SC.

More specifically with reference to FIG. 5, the check result table T1 includes various items related to the check result as constituent elements. Explaining each item, the execution time represents the time when the static analysis was executed. The project name represents the name of the project in which the source code SC is used. The project name is obtained on or from the screen using the Application Programming Interface (API). The source path represents the path of the source code SC. Packages, classes, and methods represent the structure of Java®. Interfaces and members may be added in addition to these structures. The line represents the line number of the source code SC. The tool name is an abbreviation for a static analysis tool. For example, the tool name "FB" represents the above-mentioned FindBugs (registered trademark). The rule ID represents identification information that uniquely indicates the check item of the static analysis tool. The message represents a static analysis point. For example, if a defect or defect in the source code SC is found by static analysis, a message such as "Please correct" is stored. The project name represents, for example, the name of the company that is the target of the project. The status represents the recommended status, and either the exclusion application recommendation (denoted as exclusion recommendation in FIG. 5) or the correction recommendation is stored as the recommended status by the process of updating the recommended status described later. Therefore, before the process of updating the recommended status is performed, the exclusion recommendation and the modification recommendation are not stored in the status, and null is stored. In other words, the check result table T1 immediately after storing the check result contains components other than the recommended status.

Returning to FIG. 4, the exclusion rule table T2 stores the application contents of the past exclusion application and the exclusion rule indicating the correspondence to the application contents. Specifically, as shown in FIG. 6, the exclusion rule table T2 includes various items related to the exclusion rule as constituent elements. Hereinafter, the components of the exclusion rule will be described, but the description of the components having the same check results as described above will be omitted. First, the application date, the applicant, the team, and the reason for application represent the application date of the exclusion application, the name of the applicant, the team to which the applicant belongs, and the reason for making the exclusion application. The status shows the response status to the exclusion request. For example, when an applicant makes an exclusion application, the application contents are first stored in the exclusion rule in the form of temporary registration. Then, when the administrator approves the exclusion application, the status in the exclusion rule is rewritten from provisional registration to receipt. Conversely, when the administrator remands the exclusion request, the status in the exclusion rule is rewritten from temporary registration to remand. The comment shows the reason why the administrator approved or remanded. The responder and the response date represent the date of correspondence with the person who responded to the exclusion application, respectively. The line number of the source code SC may be included in the exclusion rule table T2. In this way, the response made to the exclusion request by the exclusion rule table T2 is managed as a history, and the past response tendency to the exclusion request according to the package, class, method, static analysis tool, etc. is the exclusion rule table T2. Accumulate in.

Next, as shown in FIG. 7, the development terminal 100 includes the integrated development environment unit 110. The integrated development environment unit 110 is realized by, for example, Eclipse (registered trademark), Visual Studio, WideStudio, or the like. The integrated development environment unit 110 includes a third information processing unit 111, and in particular, the third information processing unit 111 includes a plug-in execution unit 111A, a screen display unit 111B, and an exclusion application unit 111C.

When the plug-in execution unit 111A detects that a specific operation has been performed on a specific character string displayed on the editor screen 10, the plug-in execution unit 111A executes the plug-in. Details will be described later, but for example, a plug-in is executed that a specific operation (for example, left-clicking) for instructing the character string is performed on the character string representing the static analysis tool displayed on the editor screen 10. When the unit 111A detects, the project name on the editor screen 10 or the editor screen 10 is acquired and transmitted to the second server 300. The second server 300 executes various information processing described later using the project name, and outputs a set of reference information such as exclusion application recommendation and correction recommendation and check contents. The screen display unit 111B outputs the check contents and reference information output from the second server 300 on the editor screen 10. As a result, the check contents and reference information such as exclusion application recommendation and correction recommendation appear in the vicinity of the corresponding part of the source code SC displayed on the editor screen 10, and the exclusion application screen 20 is started and displayed. A marker is displayed.

Further, when a specific operation (for example, right-clicking) for instructing the marker is performed on the marker displayed on the editor screen 10, the exclusion application screen 20 is displayed on the development terminal 100. Further, when a specific operation for instructing the application is performed by inputting the reason for applying on the exclusion application screen 20, the exclusion application unit 111C detects the specific operation and displays it on the exclusion application screen 20. The application contents and the like are transmitted to the second server 300.

Returning to FIG. 4, when the project name is transmitted from the development terminal 100, the check result search unit 312 searches the check result table T1 based on the received project name. The check result exclusion unit 313 acquires the check result as the search result by the check result search unit 312. Further, the check result search unit 312 searches the exclusion rule table T2 based on the received project name. The check result exclusion unit 313 acquires an exclusion rule as a search result by the check result search unit 312. The check result exclusion unit 313 excludes (filters) a part of the check result by using the acquired exclusion rule, and outputs the excluded check result and the exclusion rule to the exclusion rule history analysis unit 314. That is, the check result exclusion unit 313 excludes the check results that do not correspond to the exclusion rule from the subsequent processing targets, and narrows down the check results to be used in the subsequent processing.

The exclusion rule history analysis unit 314 updates the recommended status in the excluded check result by using the excluded check result and the exclusion rule. As a result, reference information such as exclusion application recommendation and correction recommendation is stored in the excluded check result. After the update, the exclusion rule history analysis unit 314 converts the excluded check result whose recommended status has been updated into a plug-in format type, and outputs the result to the check result search unit 312. The exclusion rule history analysis unit 314 will be described in more detail later. The check result search unit 312 converts the excluded check result converted to the plug-in format type into the JSON format, and outputs the check contents and reference information included in the excluded check result converted to the JSON format to the development terminal 100. To do. As a result, the screen display unit 111B described above can output the check contents and reference information on the editor screen 10.

The exclusion application temporary registration unit 315 registers the application contents and the like sent from the development terminal 100 in the exclusion rule table T2 with the status of temporary registration. On the other hand, the exclusion rule history analysis unit 314 described above acquires and holds all the exclusion rules from the exclusion rule table T2 based on the instruction from the administrator terminal 400. Further, the exclusion rule history analysis unit 314 extracts and holds an exclusion rule similar to the application content based on another instruction from the administrator terminal 400. The administrator terminal 400 acquires the exclusion rule held by the exclusion rule history analysis unit 314 together with the application content. As a result, the administrator terminal 400 can display the application content and the exclusion rule similar to the application content. When the exclusion application registration unit 316 detects an instruction regarding the response to the application content, the exclusion rule is updated to the status corresponding to the response. Specifically, when the exclusion application registration unit 316 approves the application contents, the provisional registration of the exclusion rule is rewritten as receipt. On the contrary, when the exclusion application registration unit 316 remands the application contents, the provisional registration of the exclusion rule is rewritten as remand.

Subsequently, the operations of the development terminal 100, the first server 200, the second server 300, and the administrator terminal 400 will be described with reference to FIGS. 8 to 21.

First, the process of registering the check result will be described with reference to FIGS. 8 and 9. FIG. 8 is a flowchart showing an example of the operation of the first server 200. FIG. 9 is a flowchart showing an example of the operation of the second server 300. First, as shown in FIG. 8, the Git 210 of the first server 200 waits until the source code SC is received (step S101: NO). When the Git 210 receives the source code SC (step S101: YES), the Git 210 stores the source code SC (step S102). When the process of step S102 is completed, the continuous integration unit 220 then acquires the source code SC stored in the Git 210 (step S103). When the process of step S103 is completed, the first information processing unit 230 then duplicates the source code SC acquired by the continuous integration unit 220 (step S104).

When the process of step S104 is completed, the first static analysis unit 221A and the second static analysis unit 221B each execute static analysis on the source code SC acquired by the continuous integration unit 220, and the third static analysis unit 221A and the second static analysis unit 221B respectively perform static analysis. The target analysis unit 231 executes static analysis on the source code SC duplicated by the first information processing unit 230 (step S105). When the process of step S105 is completed, the first static analysis unit 221A, the second static analysis unit 221B, and the third static analysis unit 231 upload the analysis results of the static analysis to the second server 300 as check results, respectively. (Step S106), the process ends.

On the other hand, as shown in FIG. 9, the check result registration unit 311 of the second server 300 waits until the check result is uploaded (step S201: NO). When the check result is uploaded (step S201: YES), the check result registration unit 311 stores the check result in the check result table T1 (step S202), and ends the process. As a result, the check result table T1 stores the check result of the static analysis for the source code SC.

Next, the process of displaying the reference information on the editor screen 10 will be described with reference to FIGS. 10 to 12.

FIG. 10 is a flowchart showing an example of the operation of the development terminal 100. FIG. 11 is an example of the editor screen 10. FIG. 12 is a flowchart showing an example of the operation of the second server 300.

First, as shown in FIG. 10, the plug-in execution unit 111A waits until a specific operation is detected (step S301: NO). Specifically, as shown in FIG. 11, the plug-in execution unit 111A performs a specific operation (for example, CodeG) on a specific character string (for example, CodeG) representing a static analysis tool displayed on the menu bar of the editor screen 10. Wait until it detects that a click) has taken place. When the plug-in execution unit 111A detects a specific operation (step S301: YES), the plug-in execution unit 111A executes the plug-in (step S302). Specifically, the plug-in execution unit 111A acquires the project name (not shown) of the editor screen 10 and transmits it to the second server 300. As a result, the check contents and reference information for the source code SC displayed on the editor screen 10 start to be output. When the process of step S302 is completed, the screen display unit 111B waits until the check contents and the like (specifically, the check contents and the reference information) are received (step S303: NO).

On the other hand, as shown in FIG. 12, the check result search unit 312 of the second server 300 waits until the plug-in is executed (step S401: NO). More specifically, the check result search unit 312 waits until the project name is transmitted from the plug-in execution unit 111A. When the check result search unit 312 determines that the plug-in has been executed (step S401: YES), the check result search unit 312 searches the check result table (step S402). More specifically, the check result search unit 312 searches the check result table T1 based on the project name. When the process of step S402 is completed, the check result exclusion unit 313 acquires the check result (step S403). More specifically, the check result exclusion unit 313 acquires the check result according to the project name from the check result table.

When the process of step S403 is completed, the check result search unit 312 then searches the exclusion rule table T2 (step S404). More specifically, the check result search unit 312 searches the exclusion rule table T2 based on the project name. When the process of step S404 is completed, the check result exclusion unit 313 acquires the exclusion rule (step S405). More specifically, the check result exclusion unit 313 acquires the exclusion rule according to the project name from the exclusion rule table T2.

When the process of step S405 is completed, the check result exclusion unit 313 then excludes a part of the check result by using the exclusion rule (step S406). For example, the acquired check result and the corresponding components of the exclusion rule are compared with each other, and the check results that match the components are narrowed down. Components include, for example, packages, classes, methods, and the like. That is, the check result exclusion unit 313 filters some check results for which the exclusion rule cannot be used, and outputs the excluded check results. When the process of step S406 is completed, the exclusion rule history analysis unit 314 executes the history analysis process (step S407). The history analysis process is a process of analyzing the past correspondence history made for the exclusion rule of the same type as the excluded check result and registering reference information in the recommended status of the excluded check result. The history analysis process will be described in detail later.

When the process of step S407 is completed, the exclusion rule history analysis unit 314 converts the check result (step S408). More specifically, the exclusion rule history analysis unit 314 converts the excluded check result to the plug-in format type, and the check result search unit 312 converts the excluded check result converted to the plug-in format type into JSON format. .. When step S408 is completed, the check result search unit 312 outputs the check contents and reference information (step S409). More specifically, the check result search unit 312 transmits the check contents and reference information included in the excluded check results converted to the JSON format to the development terminal 100.

Returning to FIG. 10, when the check content and the reference information are transmitted from the second server 300, the screen display unit 111B of the development terminal 100 receives the check content and the reference information (step S303: YES), and the check content and the reference information. Display the information (step S304). More specifically, the screen display unit 111B displays a message as a check content and reference information in combination at the corresponding part of the source code SC displayed on the editor screen 10, and displays a marker in the vicinity of the corresponding part. Display it. As a result, as shown in FIG. 11, for example, immediately below the 6th line of the source code SC, one set including a specific message "Please do ~ ~ ~" by static analysis and a set that the exclusion application is recommended. The inside of the image area IM1 appears. Then, the marker M1 appears on the left side of the line number on the sixth line of the source code SC. Similarly, for example, immediately below the 15th line of the source code SC, one image area IM2 including a set of a specific message "Please do ~ ~ ~" by static analysis and a correction recommendation appears. Then, the marker M2 appears on the left side of the line number on the 15th line of the source code SC.

As a result, the developer does not judge whether to apply for exclusion only by the message by static analysis, but also confirms the reference information (specifically, recommendation for exclusion application or recommendation for correction) output together with the message and excludes it. Decide whether to apply. For example, if an exclusion request recommendation is output, the developer determines that the message for that line is useless and that it is highly likely that the exclusion request will be approved, and the exclusion request will be made. On the contrary, if the correction recommendation is output, the developer judges that the message for that line is a useful point and there is a high possibility that it will be returned if an exclusion request is made, and the source code SC should be corrected. become.

Therefore, the developer does not have to individually check the check result message to decide whether or not the exclusion application is necessary, and the time and effort for the exclusion application is reduced. In particular, if a large amount of check results are fed back at the end of development, such as near the delivery date, the developer's motivation for development may be discouraged. To. Therefore, the developer can efficiently modify the source code SC and suppress the deterioration of the quality of the source code SC.

Here, the history analysis process described above will be described in more detail with reference to FIGS. 13 to 15.

FIG. 13 is a flowchart showing an example of the history analysis process. FIG. 14 is an example of a diagram illustrating the history analysis process. FIG. 15 is another example of the figure for explaining the history analysis process. When the process of step S406 described with reference to FIG. 12 is completed, as shown in FIG. 13, the exclusion rule history analysis unit 314 generates a hierarchical character string for each of the check result and the exclusion rule (step S501). For example, as shown in FIG. 14A, the exclusion rule history analysis unit 314 has a character string a. A hierarchical character string in which b (for example, com.fujitsu), a character string c for a class (for example, Bclass), and a character string d for a method (for example, copy) are joined by dots. b. c. Generate d. If only the package is used, the process of step S501 is skipped.

When the process of step S501 is completed, as shown in FIG. 13, the exclusion rule history analysis unit 314 divides the hierarchical character string of the check result and the hierarchical character string of the exclusion rule, respectively (step S502). For example, as shown in FIG. 14B, the character string is divided into dots from the lowest layer to the highest layer in order, and is stored in a storage area such as a main memory.

When the process of step S502 is completed, the exclusion rule history analysis unit 314 then counts the number of exclusion application receipts and the number of exclusion application remand of the exclusion rule for each hierarchical character string (step S503). More specifically, first, the exclusion rule history analysis unit 314 extracts one exclusion rule with a rule ID that matches the rule ID of the first check result. Next, if the provisional registration is stored in the status of the extracted exclusion rule, the exclusion rule history analysis unit 314 extracts one of the following exclusion rules. On the other hand, the exclusion rule history analysis unit 314 increments the number of exclusion application receipts if the receipt is stored in the status, and increments the number of exclusion application remand if the remand is stored. Then, one of the following exclusion rules is extracted. The exclusion rule history analysis unit 314 performs the same processing for all exclusion rules whose rule IDs match the first excluded check result. Further, when the processing for the first excluded check result is completed, the exclusion rule history analysis unit 314 performs the same processing for the second and subsequent check results. As a result, as shown in FIG. 14C, the number of exclusion application receipts and the number of exclusion application remand are counted for each hierarchical character string in the exclusion table.

When the process of step S503 is completed, the exclusion rule history analysis unit 314 then calculates the receipt probability point P1 (step S504), and then calculates the remand probability point P2 (step S505). More specifically with reference to FIG. 15A, the exclusion rule history analysis unit 314 first calculates a calculation table T3 for calculating the receipt probability point P1 and a calculation table for calculating the return probability point P2. Generate T4. Next, the exclusion rule history analysis unit 314 maps the same hierarchical character string in the column direction as the item x and maps it in the row direction as the item y for each of the calculation tables T3 and T4. Then, the exclusion rule history analysis unit 314 calculates the receipt probability basic point P1'and the return probability basic point P2'for all the locations where the hierarchical difference exists. Finally, the exclusion rule history analysis unit 314 calculates the sum of the row directions of the receipt probability basic points P1'as the receipt probability points P1, and sets the sum of the row directions of the remand probability basic points P2' as the remand probability points P2. calculate.

Here, the exclusion rule history analysis unit 314 calculates both the receipt probability basic point P1'and the return probability basic point P2'using a predetermined calculation function f (x, y). The calculation function f (x, y) is expressed by the following formula.
Calculation function f (x, y) = (layer rise coefficient ^ layer rise number)
× (Hierarchical descent coefficient ^ Hierarchical descent number)
× (Number of receipts or remand of x)

The above-mentioned hierarchical ascending coefficient and hierarchical descending coefficient represent the degree of hierarchy (for example, distance), and a larger value is set for the hierarchical descending coefficient than for the hierarchical ascending coefficient. For example, if 0.1 is set for the hierarchy ascending coefficient, 0.5 is set for the hierarchy descending coefficient. That is, the higher the hierarchical character string, the more different hierarchical character strings are added to the lower level of the hierarchical character string, and the degree of relevance becomes weaker. On the contrary, the lower the hierarchical character string, the less the hierarchical character strings that are different from each other below the hierarchical character string, and the higher the degree of relevance. Therefore, a larger value is set for the hierarchical descending coefficient than for the hierarchical ascending coefficient.

In addition, the number of hierarchical ascending and the number of hierarchical descending represents the number of rearward mismatched layers of the hierarchical character string. For example, a hierarchical character string a expanded in the column direction and a hierarchical character string a expanded in the row direction. In b, the number of rearward mismatch layers is 1, and when the hierarchical character string a is used as a reference, the hierarchical character string a. In b, it is lower. Since b is connected, the hierarchy is descending. For example, a hierarchical character string expanded in the column direction a. b. c. The hierarchical character string a expanded in the line direction with d has a number of backward mismatched layers of 3, and the hierarchical character string a. b. c. When d is used as a reference, the hierarchical character string a is elevated because nothing is combined at the lower level. Therefore, as shown in FIG. 15A, the calculation tables T3 and T4 are roughly classified into a hierarchical ascending zone Z1 and a hierarchical descending zone Z2. Then, the number of received cases or the number of remand cases of x corresponds to the number of cases of exclusion application received and the number of cases of exclusion application remand calculated in the process of step S503. Through the above processing, the exclusion rule history analysis unit 314 calculates the receipt probability point P1 and the return probability point P2. The exclusion rule history analysis unit 314 may output the calculation tables T3 and T4 that map the item x and the item y, and further, the calculation table T3 including the calculated receipt probability point P1 and the return probability point P2. , T4 may be output.

Returning to FIG. 13, when the process of step S505 is completed, the exclusion rule history analysis unit 314 then determines whether or not the receipt probability point P1 is larger than the remand probability point P2 (step S506). When the exclusion rule history analysis unit 314 determines that the receipt probability point P1 is larger than the remand probability point P2 (step S506: YES), it further determines whether or not the receipt probability point P1 exceeds the threshold value (step S507). ). When the exclusion rule history analysis unit 314 determines that the receipt probability point P1 exceeds the threshold value (step S507: YES), updates the recommended status of the excluded check result to exclusion recommendation (step S508), and ends the process. .. On the other hand, when the exclusion rule history analysis unit 314 determines that the receipt probability point P1 does not exceed the threshold value (step S507: NO), the process of step S508 is skipped and the process is terminated.

On the contrary, when the exclusion rule history analysis unit 314 determines that the receipt probability point P1 is equal to or less than the remand probability point P2 (step S506: NO), whether or not the remand probability point P2 exceeds the threshold value. Is determined (step S509). When the exclusion rule history analysis unit 314 determines that the remand probability point P2 exceeds the threshold value (step S509: YES), updates the recommended status of the excluded check result to the correction recommendation (step S510), and ends the process. To do. On the other hand, when the exclusion rule history analysis unit 314 determines that the remand probability point P2 does not exceed the threshold value (step S509: NO), the process of step S510 is skipped and the process is terminated.

That is, as shown in FIG. 15B, the magnitude relationship between the receipt probability point P1 and the return probability point P2 is determined, and the one with the larger point value is selected. Then, if the selected one exceeds a predetermined threshold value (for example, 10 points), the selected one is adopted. In FIG. 15B, since the receipt probability point P1 is adopted and exceeds the threshold value, the exclusion application is recommended. On the contrary, if the remand accuracy point P2 is adopted and exceeds the threshold value, it is recommended to correct. Become.

In this way, the history analysis process utilizes the tendency that the number of indications of static analysis is biased depending on the hierarchy such as packages. The receipt probability point P1 and the remand probability point P2 are calculated by comparing the degree of relevance between the hierarchical character string for which exclusion is applied and the past hierarchical character string for which the same type of indication is output.

Subsequently, the exclusion application and its approval / disapproval judgment will be described with reference to FIGS. 16 to 21 and the like.

FIG. 16 is a flowchart showing an example of the operation of the development terminal 100. FIG. 17 is an example of the exclusion application screen 20. FIG. 18 is a flowchart showing an example of the operation of the second server 300. FIG. 19 is a flowchart showing an example of the operation of the administrator terminal 400. FIG. 20 is an example of the exclusion application list screen 30. FIG. 21 is an example of the exclusion application confirmation screen 40.

First, as shown in FIG. 16, the exclusion application unit 111C waits until the operation of the markers M1 and M2 is detected (step S601: NO). When the exclusion application unit 111C detects the operation of the markers M1 and M2 (step S601: YES), the exclusion application screen 20 is displayed (step S602).

More specifically with reference to FIG. 17, a specific operation (for example, right-clicking) for instructing the markers M1 and M2 is performed on the markers M1 and M2 displayed on the editor screen 10 (see FIG. 11). Then, as shown in FIG. 17, the exclusion application unit 111C displays the exclusion application screen 20. The exclusion application screen 20 includes a display field Bx1 for displaying the tool name, rule ID, package, class, method, message, team name, and name, an input field Bx2 for inputting the reason for application, and an application button Bt1 and a cancel button Bt2. I'm out. When the exclusion application unit 111C detects a specific operation instructing the markers M1 and M2, the tool name to the name associated with the instructed marker M1 (or marker M2) are displayed in the corresponding display fields Bx1. Therefore, the developer who applies for exclusion using the exclusion application screen 20 inputs the reason for applying for exclusion in the input field Bx2.

Returning to FIG. 16, when the process of step S602 is completed, the exclusion application unit 111C waits until the application button press is detected (step S603: NO). Specifically, as shown in FIG. 17, the exclusion application unit 111C waits until the operation of pressing the application button Bt1 included in the exclusion application screen 20 is detected. When the exclusion application unit 111C detects that the application button is pressed (step S603: YES), the exclusion application unit 111C transmits the application content (step S604). That is, the exclusion application unit 111C sends the application contents including the items displayed in the display field Bx1, the items input in the input field Bx2, and other items (for example, application date, line number, project name, etc.) to the second server 300. Send.

On the other hand, as shown in FIG. 18, the exclusion application provisional registration unit 315 of the second server 300 waits until the application content is received (step S701: NO). When the exclusion application provisional registration unit 315 receives the application content (step S701: YES), the exclusion application provisional registration unit 315 temporarily registers the application content in the exclusion rule table T2 (step S702). When the process of step S702 is completed, the exclusion rule history analysis unit 314 waits until the activation of the list screen is detected (step S703: NO). The list screen represents the exclusion application list screen described later. When the exclusion rule history analysis unit 314 detects the activation of the list screen (step S703: YES), it acquires all the exclusion rules from the exclusion rule table T2 (step S704). When the exclusion rule history analysis unit 314 acquires all the exclusion rules, it retains all the acquired exclusion rules.

On the other hand, as shown in FIG. 19, the fourth information processing unit (not shown) included in the administrator terminal 400 waits until the list screen is activated (step S801: NO). When the list screen is started (step S801: YES), the fourth information processing unit acquires all exclusion rules from the second server 300 (more specifically, the exclusion rule history analysis unit 314) (step S802). When the process of step S802 is completed, the fourth information processing unit displays the exclusion application list screen (step S803).

When the exclusion application list screen 30 is specifically described with reference to FIG. 20, some components of the exclusion rule acquired by the fourth information processing unit appear on the exclusion application list screen 30. For example, the project name, team name, application date, applicant, tool name, and rule ID in the exclusion rule appear. The content and number of components may be changed as appropriate. Further, a selection button Bt3 is associated with a line representing a part of the components of the exclusion rule that appears. As a result, the administrator can grasp the application status of the exclusion application.

Returning to FIG. 19, when the process of step S803 is completed, the fourth information processing unit waits until the selection button Bt3 is pressed (step S804: NO). Further, as shown in FIG. 18, when the processing of step S704 is completed, the exclusion rule history analysis unit 314 waits until the press of the selection button Bt3 is detected (step S705: NO).

Here, when the exclusion rule history analysis unit 314 detects that the selection button Bt3 is pressed (step S705: YES), the exclusion rule that is similar to the application content associated with the selection button Bt3 is selected from the exclusion rules that it holds. Extract (step S706). When the process of step S706 is completed, the exclusion rule history analysis unit 314 holds the extracted exclusion rule.

On the other hand, as shown in FIG. 19, when the selection button Bt3 is pressed (step S804: YES), the fourth information processing unit acquires the application content and the exclusion rule similar to the application content from the second server (step S804: YES). S805). When the process of step S805 is completed, the fourth information processing unit displays the exclusion application confirmation screen (step S806).

When the exclusion application confirmation screen 40 is specifically described with reference to FIG. 21, the application content 41 and the exclusion rule 42 acquired by the fourth information processing unit appear on the exclusion application confirmation screen 40. Further, on the exclusion application confirmation screen 40, a selection button Bt4 for selecting approval or remand of the exclusion application, a comment input field Bx3, a registration button Bt5, and a cancel button Bt6 appear. The administrator confirms the receipt status and the remand status of the past exclusion application history similar to the application content 41 on the exclusion application confirmation screen 40, and selects approval or remand as a response to the application content 41 by the selection button Bt4. At that time, the administrator inputs the reason for selecting approval or remand in the input field Bx3 as a comment, and presses the registration button Bt5.

Here, as shown in FIG. 19, the fourth information processing unit waits until the registration button Bt5 is pressed (step S807: NO), and when the registration button Bt5 is pressed (step S807: YES), it is approved or approved. The remand is transmitted (step S808). More specifically, the fourth information processing unit transmits the correspondence of the one selected by the selection button Bt4 to the second server 300.

On the other hand, as shown in FIG. 18, the exclusion application registration unit 316 waits until the approval or the like is received from the administrator terminal 400 (step S707: NO), and when the approval or the like is received (step S707: YES), the application content is displayed. This registration is performed (step S708). That is, when approval is selected for the target exclusion application, the exclusion application registration unit 316 rewrites the status of the exclusion rule including the application content of the exclusion application from provisional registration to receipt. On the contrary, when the remand is selected for the target exclusion application, the exclusion application registration unit 316 rewrites the status of the exclusion rule including the application content of the exclusion application from the provisional registration to the remand. As a result, exclusion rules that store receipts and remand in the status are accumulated. Since this exclusion rule is used when outputting the next reference information, the output accuracy of appropriate reference information is improved.

In this way, the administrator does not have to confirm the reason for the application each time by calling the developer who made the exclusion application, for example, and it is possible to reduce unnecessary communication between the administrator and the developer.

Although the preferred embodiment of the present invention has been described in detail above, it is not limited to the specific embodiment of the present invention, and various modifications are made within the scope of the gist of the present invention described in the claims.・ Can be changed. For example, in the present embodiment, specific character strings (exclusion application recommendation and correction recommendation) are displayed as reference information, but for example, the reference information may be displayed by symbols such as ○ and ×.

The following additional notes will be further disclosed with respect to the above description.
(Appendix 1) When the analysis results of a program layered by a plurality of layers are acquired and the specific check contents included in the acquired analysis results are displayed in association with the corresponding parts of the program in the past. With reference to the storage unit in which the information of the check content exclusion application is stored, the exclusion application of the same type of check content as the specific check content is specified, and the application result of the exclusion application of the same type of check content and the above Reference information regarding the exclusion application for the specific check content according to the difference between the position of the specific check content in the plurality of layers and the position of the check content of the same type in the plurality of layers in the program. A reference information output program that outputs and causes a computer to execute processing.
(Appendix 2) The reference information is characterized in that it includes an exclusion application recommendation display that recommends an exclusion application for the specific check content, or a correction recommendation display that recommends correction of the corresponding part of the program. The reference information output program described in Appendix 1.
(Appendix 3) When displaying the specific check content, the user's attribute is specified, and among the check contents included in the analysis result, only other check contents corresponding to the specified attribute are displayed. The reference information output program described in Appendix 1 or 2.
(Appendix 4) When an exclusion request is received for a specific check content included in the analysis result of a program layered by a plurality of layers, the storage unit in which the information of the exclusion application of the past check content is stored is referred to, and the above The exclusion application of the same type of check content as the specific check content is specified, the application result of the exclusion application of the same type of check content, the position of the specific check content in the plurality of layers, and the check content of the same type. A reference information output program characterized by causing a computer to execute a process that outputs reference information regarding approval / disapproval judgment of an exclusion application for the specific check contents according to the difference from the positions in the plurality of layers. ..
(Appendix 5) The reference information output program according to Appendix 4, wherein the reference information regarding the approval / disapproval judgment is a selection of approval or remand.
(Appendix 6) When an exclusion request is received for a specific check content included in the analysis result of a program layered by a plurality of layers, the storage unit in which the information of the exclusion application of the past check content is stored is referred to, and the above The same type of check content as the specific check content was specified, and the information indicating the specific check content and the information indicating the same type of check content were mapped to the corresponding positions in the plurality of layers. An output program that outputs a diagram and causes a computer to perform processing.
(Appendix 7) When acquiring the analysis results of a program layered by a plurality of layers and displaying the specific check contents included in the acquired analysis results in association with the corresponding parts of the program, the past With reference to the storage unit in which the information of the check content exclusion application is stored, the exclusion application of the same type of check content as the specific check content is specified, and the application result of the exclusion application of the same type of check content and the above Reference information regarding the exclusion application for the specific check content according to the difference between the position of the specific check content in the plurality of layers and the position of the check content of the same type in the plurality of layers in the program. A reference information output method characterized in that a computer executes a process to be output.
(Appendix 8) When an exclusion request is received for a specific check content included in the analysis result of a program layered by a plurality of layers, the storage unit in which the information of the exclusion application of the past check content is stored is referred to, and the above The exclusion application of the same type of check content as the specific check content is specified, the application result of the exclusion application of the same type of check content, the position of the specific check content in the plurality of layers, and the check content of the same type. A reference information output method characterized in that a computer executes a process of outputting reference information regarding approval / disapproval judgment of an exclusion application for the specific check contents according to the difference from the positions in the plurality of layers. ..
(Appendix 9) When acquiring the analysis results of a program layered by a plurality of layers and displaying the specific check contents included in the acquired analysis results in association with the corresponding parts of the program, the past. With reference to the storage unit in which the information of the check content exclusion application is stored, the exclusion application of the same type of check content as the specific check content is specified, and the application result of the exclusion application of the same type of check content and the above Reference information regarding the exclusion application for the specific check content according to the difference between the position of the specific check content in the plurality of layers and the position of the check content of the same type in the plurality of layers in the program. A reference information output device having a processing unit that outputs and executes processing.
(Appendix 10) The reference information is characterized in that it includes an exclusion application recommendation display that recommends an exclusion application for the specific check content, or a correction recommendation display that recommends correction of the corresponding portion of the program. The reference information output device according to Appendix 9.
(Appendix 11) When displaying the specific check content, the processing unit identifies the user's attribute and displays only the other check content corresponding to the specified attribute among the check content included in the analysis result. The reference information output device according to Appendix 9 or 10, wherein the reference information output device is characterized.
(Appendix 12) When an exclusion request is received for a specific check content included in the analysis result of a program layered by a plurality of layers, the storage unit in which the information of the exclusion application of the past check content is stored is referred to, and the above The exclusion application of the same type of check content as the specific check content is specified, the application result of the exclusion application of the same type of check content, the position of the specific check content in the plurality of layers, and the check content of the same type. A reference information output device having a processing unit for executing processing, which outputs reference information regarding approval / disapproval determination of an exclusion application for the specific check contents according to the difference from the positions in the plurality of layers.
(Appendix 13) The reference information output device according to Appendix 12, wherein the reference information regarding the approval / disapproval determination is a selection of approval or remand.

S Reference information output system 100 Development terminal 200 1st server 300 2nd server 310 2nd information processing unit 311 Check result registration unit 312 Check result search unit 313 Check result exclusion unit 314 Exclusion rule history analysis unit 315 Exclusion application provisional registration unit 316 Exclusion application registration department 400 Administrator terminal T1 Check result table T2 Exclusion rule table

Claims (5)

Obtain the analysis result of static analysis for a program layered by multiple layers,
When displaying the specific check contents included in the acquired analysis result in association with the corresponding parts of the program, the specific check contents are referred to the storage unit in which the information of the exclusion application of the past check contents is stored. Identify the exclusion application for the same type of check content as the check content,
Depending on the application result of the exclusion application of the same type of check content and the difference between the position of the specific check content in the plurality of layers and the position of the check content of the same type in the plurality of layers in the program. Also, output reference information regarding the exclusion application for the specific check contents.
A reference information output program characterized by having a computer execute processing. The reference information includes an exclusion application recommendation display that recommends an exclusion application for the specific check content, or a modification recommendation display that recommends modification of the corresponding portion of the program.
The reference information output program according to claim 1. The static analysis finds a problem related to the quality of the program, feeds back the analysis result including a message indicating an indication corresponding to the problem as the check content, and feeds back the analysis result.
The specific check contents are related to useless indications.
The reference information output program according to claim 1. Obtain the analysis result of static analysis for a program layered by multiple layers,
When displaying the specific check contents included in the acquired analysis result in association with the corresponding parts of the program, the specific check contents are referred to the storage unit in which the information of the exclusion application of the past check contents is stored. Identify the exclusion application for the same type of check content as the check content,
Depending on the application result of the exclusion application of the same type of check content and the difference between the position of the specific check content in the plurality of layers and the position of the check content of the same type in the plurality of layers in the program. Also, output reference information regarding the exclusion application for the specific check contents.
A reference information output method characterized in that a computer executes processing. Obtain the analysis result of static analysis for a program layered by multiple layers,
When displaying the specific check contents included in the acquired analysis result in association with the corresponding parts of the program, the specific check contents are referred to the storage unit in which the information of the exclusion application of the past check contents is stored. Identify the exclusion application for the same type of check content as the check content,
Depending on the application result of the exclusion application of the same type of check content and the difference between the position of the specific check content in the plurality of layers and the position of the check content of the same type in the plurality of layers in the program. Also, output reference information regarding the exclusion application for the specific check contents.
A reference information output device having a processing unit that executes processing.

Images