JP2008293486A - Source code analysis device, analysis program, and analysis method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To analyze source codes of a program and to effectively display its result according to the purpose. <P>SOLUTION: The source codes are analyzed to obtain a function call relationship and an inclusion relationship between the functions and modules to prepare a inter-module call relationship diagram displayed in set module units. The module having the inclusion relationship with an object to be extracted from the inter-module call relationship diagram, the module calling only the module in the inclusion relationship, and the module called only from the module in the inclusion relationship, are extracted to prepare the inter-module call relationship diagram showing the extracted modules and connection symbols between the extracted modules in a set display form. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a technique for analyzing a source code of a program and displaying the result.

  2. Description of the Related Art In recent years, higher functions have been advanced in program embedded systems such as digital televisions and hard disk recorders, personal computers, and business server systems, and the scale of programs has become enormous. Along with that, program defects are increasing. In addition, frequent changes to program specifications tend to be incompletely reflected in the specifications, so it is necessary to read the source code instead of the specifications in order to accurately understand the current program operation. Yes.

  As a conventional technique for solving this problem, for example, Patent Document 1 discloses a source code analysis support apparatus. If this technology is used, analysis can be performed at the source code creation stage of the program to verify the operation of the program, so that a defect can be found and corrected before the operating environment is constructed or before the operation test. Moreover, by displaying graphically the call relationship between functions and related argument / variable information in the analysis target source code, it is possible to understand the program operation more efficiently than reading the source code only with character information.

JP 2006-277206 A (first page, FIG. 2)

  However, in the conventional technology as described above, since all functions including functions that need not be examined are displayed, when the program size, that is, the size of the source code to be analyzed is large, the call relationship diagram between functions is huge and It becomes complicated and it becomes difficult to understand the program operation.

  The present invention has been made in view of the above circumstances, and an object of the present invention is to analyze a source code of a program and to display the result effectively according to the analysis purpose.

  In order to solve the above problems, the source code analysis device, the analysis program, and the analysis method of the present invention analyze the source code, obtain information on the call between functions, and information on the definition and use location of the variable. Set the module unit, which is the granularity to display the analysis results, analyze the source code or setting data to obtain information about the inclusion relationship between the module and function, analyze the calling relationship between modules, and call related between modules Create a diagram.

  Further, the module unit includes a function, a group to which the function belongs, a file in which the function is implemented, a directory in which the file is stored, a class, a component, an object including program information in the file, and It includes at least one of the libraries. Further, the present invention is characterized in that an inclusive relationship between a module and a function mounted, stored, or included in the module is analyzed. Furthermore, information on a call relationship between modules represented by the set module unit is obtained from information on a call between the functions and information on an inclusion relationship between the module and the function.

  Further, the source code analysis device, the analysis program, and the analysis method of the present invention set the extraction information including the extraction target from the call relation diagram between the modules and the display form of the module related to the extraction target, Extract the modules related to the extraction target. Further, the extraction target includes at least one of a variable, a function, a group, a file, a directory, a class, a component, an object, and a library.

  Further, from the set module unit, the inclusion relationship, the calling relationship between the modules, and the set extraction target, the module in the inclusion relationship with the set extraction target is changed to the inclusion relationship. A module that calls a module and a module that is called from a module in the inclusion relationship are extracted. Furthermore, a call relation diagram between modules is created in which the extracted extraction modules and the connection symbols between the extraction modules are displayed in the set display form.

  According to the technique described above, the calling relationship between functions is displayed at an appropriate granularity according to the analysis purpose in order to convert the calling relationship between functions into the calling relationship between modules expressed in units such as classes and libraries. be able to. In addition, in order to change the display form of the module related to the set variable or file, etc., the necessary module is highlighted for the purpose of analysis, the unnecessary module is deleted, the module related to the specific variable is changed to the variable Can be displayed along with values and branch conditions.

  In addition, it is possible to visualize the degree of dependence between groups (the number of calls) with an appropriate granularity.

  As described above, according to the present invention, it is possible to analyze the source code of a program and display the result effectively according to the purpose of analysis.

  According to the present invention, it is possible to analyze the source code of a program and display the result effectively according to the purpose of analysis. This makes it easy to understand the program operation from the source code, makes it easy to find and correct problems before building the operating environment and before the operation test, and makes it easy to examine the division location when making a program into parts, etc. Program development efficiency can be improved, and cost reduction and development time can be shortened.

  Hereinafter, modes for carrying out the present invention will be described.

  First, a schematic configuration of the source code analysis device 1 in the present embodiment will be described with reference to FIG.

  As shown in FIG. 1, the source code analysis device 1 of this embodiment includes a control device 11, a recording device 12, and an input / output device 13.

  The control device 11 is a device that executes the processing program held by the recording device 12 and controls the operation of the entire device.

  The recording device 12 is a device that includes a processing unit that stores a processing program that controls the operation of the source code analysis device 1 and a recording unit that stores data read and written by the processing program. The processing unit of the recording device 12 includes a device control processing unit 121, a module unit setting processing unit 122, an extraction information setting processing unit 123, a group information setting processing unit 129, a function analysis processing unit 124, and an inclusion relationship analysis process. Section 125, module analysis processing section 126, module extraction processing section 127, and related diagram creation processing section 128. The recording unit of the recording device 12 includes a source code recording unit 1201, a setting information recording unit 1202, an analysis result recording unit 1203, and a drawing information recording unit 1204. Examples of the recording device 12 include a disk, a tape, and a semiconductor.

  The device control processing unit 121 is a processing unit that causes each device of the source code analysis device 1 to cooperate and operate as a source code analysis device. The module unit setting processing unit 122 is a processing unit that sets a module unit, which is a granularity when displaying the analysis result.

  The extraction information setting processing unit 123 is a processing unit that sets extraction information including an extraction target from the inter-module call relation diagram and a display form of a module related to the extraction target. The function analysis processing unit 124 is a processing unit that analyzes the source code and obtains the calling relationship between functions, the definition of variables, and the use location. The group information setting processing unit 129 is a processing unit that sets group information including an inclusion relationship between a function and a group.

  The inclusion relationship analysis processing unit 125 is a processing unit that analyzes the source code to obtain the inclusion relationship between the module and the function. The module analysis processing unit 126 is a processing unit that analyzes the calling relationship between modules. The module extraction processing unit 127 is a processing unit that extracts modules related to the extraction target. The related diagram creation processing unit 128 is a processing unit that creates a call related diagram between modules.

  The source code recording unit 1201 records source code file data and build information data such as a storage location of the source code file and a build setting file. The setting information recording unit 1202 records module unit data, extraction information data, and group information data. In the analysis result recording unit 1203, the calling relationship between functions, the function calling relationship data including the definition and usage of variables, the inclusion relationship data that is the information on the inclusion relationship between the module and the function, and the calling relationship between modules are displayed. Module call relation data, which is information, and extraction module data, which is module information related to the extraction target, are recorded. In the drawing information recording unit 1204, module related diagram data which is information of a diagram representing the calling relationship between modules is recorded.

  Here, the module unit means a function, a group to which the function belongs, a file in which the function is implemented, a directory in which the file is stored, and a class, component, or object that includes program information in the file. And show the library.

  The extraction target indicates a variable, a function, a group, a file, a directory, a class, a component, an object, and a library.

  The input / output device 13 is an interface device that allows a user to operate the source code analysis device 1 and obtain information from the source code analysis device 1. Examples of the input / output device 13 include a keyboard, a touch pad, a mouse, a touch panel, and a monitor. However, the present invention is not limited to these. An interface that outputs a signal or information to the source code analysis device 1 by detecting an instruction, an operation issued from the user, a voice, a body movement, or the like. Any face device may be used. For example, an eyeball movement may be detected.

  Next, a schematic operation of the source code analyzing apparatus 1 in the present embodiment will be described with reference to FIG.

The device control processing unit 121 waits until receiving an instruction from the user via the input / output device 13, and if the instruction is received, the instruction is analyzed (step 1001).
If the instruction analyzed in step 1001 is “setting instruction” (branch to “setting instruction” in step 1002), the setting process described later is performed (step 1008), and the process returns to step 1001.

  If the instruction analyzed in step 1001 is an “analysis start instruction” (branch to “analysis start instruction” in step 1002), an analysis process described later is performed (step 1005), and a related chart generation process described later is performed (step 1006). ).

  Next, the device control processing unit 121 reads the module-related diagram data recorded in the drawing information recording unit 1204, displays it on the input / output device 13 (step 1007), and returns to step 1001.

  If the instruction analyzed in step 1001 is an “end instruction” (branch to “end instruction” in step 1002), the process ends.

  Next, the operation of the setting process (step 1008) of the source code analysis device 1 in this embodiment will be described with reference to FIG. When the process in FIG. 10 is completed, the process returns to step 1001 in FIG.

  The device control processing unit 121 analyzes the contents of the setting instruction received from the user (step 4001).

  When the instruction analyzed in step 4001 is “module unit setting instruction” (branch to “module unit setting instruction” in step 4001), the module unit setting processing unit 122 displays the module unit information instructed to set the module unit. Data is recorded in the setting information recording unit 1202 (step 4002), and the process ends.

  When the instruction analyzed in step 4001 is “extraction information setting instruction” (branch to “extraction information setting instruction” in step 4001), the extraction information setting processing unit 123 displays the extraction target and the display form for which setting is instructed. The included extraction information is recorded as extraction information data in the setting information recording unit 1202 (step 4003), and the process ends.

  When the instruction analyzed in step 4001 is “group information setting instruction” (branch to “group information setting instruction” in step 4001), the group information setting processing unit 129 determines the inclusion relation between the function instructed to set and the group. The included group information is recorded in the setting information recording unit 1202 as group information data (step 4004), and the process ends.

  Next, the operation of the analysis process (step 1005) of the source code analysis device 1 in the present embodiment will be described with reference to FIG.

  The device control processing unit 121 determines whether the function analysis has been completed based on the presence / absence of function call relation data in the analysis result recording unit 1203 (step 2001).

  If the function analysis has not been completed (branch to “No” in step 2001), the function analysis processing unit 124 reads the source code file data from the source code recording unit 1201, performs analysis, and determines the call relationship between the functions. Then, the definition and use location of the variable are obtained and recorded in the analysis result recording unit 1203 as function call relation data (step 2002).

  When the function analysis has been completed (branch to “Yes” in step 2001), or after the function call relationship analysis (step 2002) is completed, the device control processing unit 121 includes the inclusion relationship in the analysis result recording unit 1203. It is determined whether or not the inclusion relation analysis has been completed based on the presence or absence of data (step 2003).

  If the inclusion analysis has not been completed (branch to “No” in step 2003), the inclusion relationship analysis processing unit 125 reads the source code file data and the build information data from the source code recording unit 1201, and the setting information recording unit The group information data is read from 1202 and analyzed to obtain an inclusion relationship between the module and a function implemented, stored, or included in the module, and recorded as inclusion relationship data in the analysis result recording unit 1203 (step S1203). 2004). From the build information data, it is possible to obtain an inclusive relationship in which directory a certain file is stored and in which class, component, and object library the program information in the certain file is included after the build. For this reason, the inclusion relationship between each module unit is derived by further combining the inclusion relationship between the function and the file found from the analysis of the source code file data and the inclusion relationship between the function and the group obtained from the group information data. When the inclusion analysis has been completed (branch to “Yes” in step 2003), or after the analysis of the inclusion relationship (step 2004) is finished, the module analysis processing unit 126 reads the module unit data from the setting information recording unit 1202 , The function call relation data and the inclusion relation data of the analysis result recording unit 1203 are read and analyzed to obtain a call relation between modules expressed in units of set modules, and the analysis result is recorded as module call relation data. The information is recorded in the unit 1203 (step 2005).

  Note that step 2003 and step 2004 may be performed before step 2001 and step 2002.

  Next, the operation of the related diagram creation process (step 1006) of the source code analysis device 1 in this embodiment will be described with reference to FIG.

  The device control processing unit 121 determines whether extraction information is set based on the presence or absence of extraction information data in the setting information recording unit 1202 (step 3001).

  If the extraction information is not set (branch to “No” in step 3001), the related diagram creation processing unit 128 reads the module call related data in the analysis result recording unit 1203 and creates a call related diagram between modules. Then, it is recorded in the drawing information recording unit 1204 as module related diagram data (step 3002).

  When extraction information is set (branch to “Yes” in step 3001), the module extraction processing unit 127 reads module unit data and extraction target data from the setting information recording unit 1202, and includes the analysis result recording unit 1203. Reads relation data and module call relation data, extracts modules that are in inclusion relation with the extraction target, modules that call only modules that are in the inclusion relation, and modules that are called only from modules that are in the inclusion relation, and extracts modules The data is recorded in the analysis result recording unit 1203 (step 3003).

  Next, the related diagram creation processing unit 128 reads the display form data from the setting information recording unit 1202, reads the extraction module data and module call relation data of the analysis result recording unit 1203, and extracts the extraction module and the connection symbol between the extraction modules. Is created in the display format set, and a call related diagram between modules is created and recorded in the drawing information recording unit 1204 as module related diagram data (step 3004).

  Next, an example of the setting information recording unit 1202 of the recording device 12 in this embodiment will be described with reference to FIG.

  As shown in FIG. 5, the setting information recording unit 1202 includes module unit data composed of module units 12021, extraction information data composed of extraction targets 12022 and display forms 12023, group information composed of functions 12026 and groups 12027. Data is recorded. In the display form 12023, the display form is set separately for the module 12024 corresponding to the extraction target and the module 12025 not corresponding to the extraction target.

  Here, the module corresponding to the extraction target refers to a module that is included in the set extraction target 12022 among the modules represented by the set module unit 12021. In the example of FIG. 5, for a class that is in an inclusive relationship with the function B, the frame of the corresponding class is represented in red, and an arrow that connects the classes is represented by a solid black line. In addition, the frame of the non-corresponding class is represented in gray, and the arrow used for connection with the non-corresponding class is represented by a gray dotted line.

  In the example of FIG. 5, the functions B and C are included in the group P and the function D is included in the group Q.

  Next, an example of the analysis result recording unit 1203 of the recording device 12 in this embodiment will be described with reference to FIG.

  As shown in FIG. 6, the analysis result recording unit 1203 includes function call relation data including a caller function 12031 and a callee function 12032, a function 12033, a group 12030, a file 12034, a class 12035, and a library 12036. Inclusion relationship data, module call relationship data consisting of the caller module 12037 and callee module 12038, and extraction module data consisting of the extraction module 1203 are recorded.

  In the example of FIG. 6, the function call relationship data indicates that the function A is in a relationship of calling the function B and the function C, the function B is calling the function D, and the function C is calling the function E. In the inclusion relation data, function A, function B, and function C are included in group P, function D and function E are included in group Q, function A and function C are included in class X, and function B is included in class Y. Class X and class Y are included in file L, and file L and file M are included in library S.

  Similarly to FIG. 5, the case where the module unit is a class and the extraction target is a function B is taken as an example. In the module call relation data, the class X is the call source module and the class is the call destination module. This indicates that there is a relationship to call Y. In addition, in the extraction module data, it is indicated that the extraction module is a class Y including the function B to be extracted, a class X that is a class Y caller module, and a class Z that is a class Y callee module. ing.

  In FIG. 6, the caller function and the callee function are described as the constituent elements of the function call relation data. However, the constituent elements of the function call relation data are not limited to these, and a variable and the definition of the variable And use points may be included.

  In FIG. 6, functions, groups, files, classes, and libraries have been described as the constituent elements of inclusion relation data. However, the constituent elements of inclusion relation data are not limited to these and include variables and modules. Any two or more elements may be used.

  Next, an example of a module relation diagram output by the input / output device 13 in this embodiment will be described with reference to FIGS. 7, 8, 9, and 11. FIG.

  FIG. 7 shows a case where the module is a function and no extraction information is set as an example 1, a case where the module unit is a class and no extraction information is set, and an example 3 In the case where the unit is class and extraction information is set, an example of each module relation diagram is shown.

  Here, Example 1, Example 2, and Example 3 show module-related diagrams along the contents of the setting information recording unit 1202 shown in FIG. 5 and the contents of the analysis result recording unit 1203 shown in FIG. However, color information is not expressed.

  FIG. 8 shows the module related diagrams for the same program when the module unit is a function and the extraction information is not set as Example 4, and when the module unit is the function and the extraction information is set as Example 5. An example is shown. In Example 5, the extraction target is a function call path between the function B and the function G, and the case where the corresponding module is omitted is shown.

  In FIG. 9, for the same program, as Example 6, the module unit is a function and no extraction information is set, and as Example 7, the module unit is a function and the extraction information is set, and as Example 8, the module is In the case where the unit is a function, the extraction information is set, and the variable value is set, an example of each module related diagram is shown.

  FIG. 9 shows the source code of the assumed program. The function A calls the function C by setting the variable X to 1 when the variable Z is not 0, and setting the variable X to 2 otherwise. Function B calls function C. The function C sets the variable Y by the addition result of the variables X and 4, and calls the function D. Function D calls function E when variable Y is 5, and calls function F when variable Y is 6. The function E outputs the multiplication result of the variable Y and 3. The function F outputs the multiplication result of the variable Y and 2.

  In Example 6, the branch arrow indicates that the function D is in a relationship of calling only one of the function E and the function F.

  In Example 7, the extraction target is the variable Y, and the display form of the non-corresponding module is erased. The variable Y is defined in the function C, and the variable X included in the definition of the variable Y is also extracted, but the function B that is not used because neither the variable X nor the variable Y is defined is not applicable Since it is a module, in the illustration of Example 7, the function B and the connecting arrow from the function B are deleted.

  Next to the function A, there is an indication that the variable X is used in the function and the value is limited to 1 or 2. Next to the function C, there is a display indicating that the variable Y is set by the addition result of the variables X and 4 in the function. In the middle of the branch arrow, there is a display indicating that the function E is called when the variable Y is 5, and the function F is called when the variable Y is 6.

  Example 8 shows a state in which the user sets the value of variable X to 2 from the state of Example 7. Next to function A, variable X is fixed at 2, and next to function C, variable Y is fixed at 6. Since there is no longer a possibility that the variable Y is 5, in the illustration of Example 8, the function E and the connection arrow to the function E are deleted.

  FIG. 11 shows an example in which extraction information is set in a group of set modules for the same program. As an example 9, when the extraction target is the group P and the dependency indicating the number of function call locations between the groups is displayed numerically, and as the example 10, the extraction target is the function B and the dependency is indicated by the number of arrows. In the case of displaying and as an example 11, the example of each module relation diagram is shown for the case where all the extraction targets are the function to be displayed in duplicate.

  In Example 11, the group and function are displayed in duplicate, thereby simultaneously showing the inclusion relationship between the group and the function and the dependency relationship between the groups.

  In this example, the module unit set is a group and the module unit to be displayed in duplicate is a function, but the module unit set is a library and the module unit to be displayed in duplicate is a file. Other module units may be combined.

  Here, Example 9, Example 10, and Example 11 show module-related diagrams along the contents of the setting information recording unit 1202 shown in FIG. 5 and the contents of the analysis result recording unit 1203 shown in FIG. However, color information is not expressed.

  The embodiment of the present invention has been described above.

  In the embodiment of the present invention, each processing unit and each recording unit are described as being recorded in the same recording device 12, but the processing unit and the recording unit may be recorded in different recording devices.

  Further, in the embodiment of the present invention, the group information data is first generated and the inclusion relation data is generated based on the data. However, after the inclusion relation data is generated, the group information data is It may be generated. For example, the inclusion relationship data generated by analyzing the source code may be presented to the user, and the user may set a group to which the function belongs. At this time, in the example of FIG. 6, in the case of setting the file L as the group P and the file M and the file N as the group Q, in addition to the function, the group is set using each module unit such as a file and a library. May be.

  In the embodiment of the present invention, an example in which the dependency relationship between modules is represented by the number of call locations of the functions included in the module has been described. Dependencies may be expressed using other indices such as the number of function combinations, the number of calls, and the number of calls in units other than functions.

  According to the embodiment of the present invention, since the calling relationship between functions is converted into the calling relationship between modules expressed in units such as classes and libraries, the calling relationship of program modules is set with an appropriate granularity according to the analysis purpose. Can be displayed. Further, according to the embodiment of the present invention, in order to change the display form of the module related to the set variable, file, etc., the required module is highlighted or the unnecessary module is deleted according to the analysis purpose. Modules related to specific variables can be displayed together with variable values and branch conditions.

  Further, according to the embodiment of the present invention, it is possible to visualize the degree of dependence between groups (the number of calls) with an appropriate granularity.

  As described above, according to the embodiment of the present invention, the source code of a program can be analyzed, and the result can be effectively displayed according to the analysis purpose.

It is the figure which showed schematic structure of the source code analysis apparatus 1 in embodiment of this invention. It is the flowchart which showed schematic operation | movement of the source code analysis apparatus 1 in embodiment of this invention. It is the flowchart which showed the operation | movement of the analysis process (step 1005) of the source code analysis apparatus 1 in embodiment of this invention. It is the flowchart which showed the operation | movement of the related figure creation process (step 1006) of the source code analysis apparatus 1 in embodiment of this invention. It is the figure which showed the example of the setting information recording part 1202 in embodiment of this invention. It is the figure which showed the example of the analysis result recording part 1203 in embodiment of this invention. It is Example 1, Example 2 and Example 3 of the module relation diagram output by the input / output device 13 in the embodiment of the present invention. It is Example 4 and Example 5 of the module related figure which the input / output device 13 in embodiment of this invention outputs. It is Example 6, Example 7 and Example 8 of the module relation diagram output by the input / output device 13 in the embodiment of the present invention. It is the flowchart which showed the operation | movement of the setting process (step 1008) of the source code analysis apparatus 1 in embodiment of this invention. It is Example 9, Example 10, and Example 11 of the module relation diagram output by the input / output device 13 in the embodiment of the present invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Source code analysis apparatus, 11 ... Control apparatus, 12 ... Recording apparatus, 13 ... Input / output device.

Claims (6)

Function analysis means for obtaining information about calls between functions and information on the definition and use of variables from source code,
Module unit setting means for setting a module unit, which is a granularity for displaying the analysis result,
Inclusion relationship analysis means for obtaining information on inclusion relationships between modules and functions from source code or configuration data;
Module analysis means for analyzing information about calls between modules,
A related diagram creating means for creating a call related diagram between modules;
The module unit includes a function, a group to which the function belongs, a file in which the function is implemented, a directory in which the file is stored, and classes, components, objects, and libraries that include program information in the file. Including at least one of
The inclusion relationship analyzing means analyzes the inclusion relationship between a module and a function implemented, stored, or included in the module,
The module analysis means is set by the module unit setting means based on the information on the call between functions obtained by the function analysis means and the information on the inclusion relation between the module and the function obtained by the inclusion relation analysis means. A source code analysis device characterized by obtaining information on a calling relationship between modules expressed in units of modules. The source code analysis device according to claim 1,
Extraction information setting means for setting extraction information including an extraction target from the inter-module call relation diagram and a display form of a module related to the extraction target;
Module extraction means for extracting a module related to the extraction object;
The extraction target includes at least one of a variable, a function, a group, a file, a directory, a class, a component, an object, and a library,
The module extraction means includes the set extraction target and inclusion relation from the set module unit, the inclusion relation, the calling relation between the modules, and the extraction target set by the extraction information setting means. A module that calls a module that is in the inclusion relationship, a module that is called from the module that is in the inclusion relationship,
The relation diagram creating means is a call relation diagram between modules in which the extraction module extracted by the module extraction means and a connection symbol between the extraction modules are displayed in a display form set by the extraction information setting means. Source code analysis equipment characterized by creating. A function analysis step that obtains information about the call between functions from the source code, information about the definition and use of variables,
A module unit setting step for setting a module unit which is a granularity for displaying the analysis result;
An inclusion relationship analysis step for obtaining information about the inclusion relationship between a module and a function from source code or setting data;
A module analysis step for analyzing information about calls between modules;
A source code analysis program for causing an information processing apparatus to execute a related diagram creating step for creating a call related diagram between modules,
The module unit includes a function, a group to which the function belongs, a file in which the function is implemented, a directory in which the file is stored, a class, a component, an object, and a library that include program information in the file. Including at least one of
The inclusion relationship analysis step analyzes the inclusion relationship between a module and a function implemented, stored, or included in the module,
The module analysis step is set in the module unit setting step based on the information on the call between functions obtained by the function analysis step and the information on the inclusion relationship between the module and the function obtained by the inclusion relationship analysis step. A source code analysis program characterized by obtaining a calling relationship between modules expressed in module units. A source code analysis program according to claim 3,
An extraction information setting step for setting extraction information including an extraction target from the call relation diagram between the modules and a display form of a module related to the extraction target;
A module extraction step of extracting a module associated with the extraction target;
The extraction target includes at least one of a variable, a function, a group, a file, a directory, a class, a component, an object, and a library,
The module extraction step includes the set extraction target and the inclusion relation from the set module unit, the inclusion relation, the calling relation between the modules, and the extraction target set in the extraction information setting step. A module that calls a module that is in the inclusion relationship, a module that is called from the module that is in the inclusion relationship,
In the related diagram creating step, the inter-module call related diagram in which the extraction module extracted in the module extracting step and the connection symbol between the extracted modules are displayed in the display form set in the extraction information setting step. A source code analysis program characterized by creating From the source code, get information about calls between functions, define and use variables,
Set the module unit that is the granularity to display the analysis results,
Analyzing source code or configuration data to obtain the inclusion relationship between modules and functions,
Analyzes information about calls between modules,
A source code analysis method for creating a call relation diagram between modules,
The module unit includes a function, a group to which the function belongs, a file in which the function is implemented, a directory in which the file is stored, a class, a component, an object, and a library that include program information in the file, Including at least one of
Analyze the inclusive relationship between a module and the functions implemented, stored, or included in the module,
A source code analysis method, comprising: obtaining a calling relationship between modules expressed by the set module unit from the calling relationship between the functions and the inclusion relationship. The source code analysis method according to claim 5,
Setting extraction information including an extraction target from the call relation diagram between the modules, and a display form of the module related to the extraction target;
Module extraction for extracting modules related to the extraction target;
The extraction target includes at least one of a variable, a function, a group, a file, a directory, a class, a component, an object, and a library,
Modules that are in the inclusion relationship with the set extraction target from the set module units, the inclusion relationship, the calling relationship between the modules, and the set extraction target And a module called from a module in the inclusion relationship,
A source code analysis method comprising: creating a call relation diagram between modules in which the extracted modules and the connection symbols between the extracted modules are displayed in the set display form.

Images