JP7085938B2 - Change impact analyzer - Google Patents

Description

The present invention relates to a change impact analyzer that analyzes the effect of a specific functional change on the entire software.

Patent Document 1 discloses a change impact analyzer that extracts other specification elements, functions, and change impact priorities affected by a change in any of the specification elements constituting the software specification. is doing. The change impact analyzer extracts other specification elements, functions, and change impact priorities that are affected by the change, allowing the user to efficiently modify the software.

Japanese Unexamined Patent Publication No. 2016-110330

The change effect analyzer of Patent Document 1 calculates the change effect priority based on "the number of times the function to be changed is referred to by another function". However, the change impact priority does not comprehensively consider the function to be changed and the related functions. Specifically, "the number of times the function to be changed refers to another function", "the number of times to refer to another function that has a direct reference relationship with the function to be changed", and "the number of times the function to be changed refers to another function". It does not take into account the number of times a function that has a direct reference relationship is referenced by another function. Further, the change effect analysis device of Patent Document 1 does not display the function to be changed in association with the process and the function that realizes the function. By not taking these things into account, the user may not be able to adequately understand the impact of a particular feature change on the software as a whole.

The present invention provides a change impact analyzer that appropriately analyzes and displays the degree of influence that a change of a specific function has on the entire software.

The change effect analysis device according to one aspect of the present invention is a device that analyzes the source code and outputs software effect information showing the effect of the function to be changed on the entire software based on the source code. The change impact analyzer includes a control unit. The control unit includes a first source code reverse unit, a second source code reverse unit, a mapping unit, a function designation unit, and a change effect analysis unit. The first source code reverse unit generates an object list in which each function included in the source code is described from the source code. The second source code reverse part generates a process specification that describes the input, processing, and output of each process realized by each function from the object list. The mapping part generates a functional specification that describes the processing of the process to be changed that realizes the function to be changed from the process specification and the dependency information of the function that defines each function realized by each process. do. The function specification unit generates affected function information in which other functions affected by the function to be changed are described from the source code. The change impact analysis unit generates and outputs software impact information from the functional specifications and the affected function information.

By referring to the software impact information, the user can better understand the impact of a particular functional change on the software as a whole. As a result, the user can efficiently divert and develop the software in consideration of the influence.

The block diagram which shows the structure of the change influence analysis apparatus which concerns on Embodiment 1. Diagram showing data input / output to the components of the change impact analyzer Diagram showing data input / output to the components of the change impact analyzer Diagram showing data input / output to the components of the change impact analyzer Flow chart showing the operation of the first source code reverse section Flow chart showing the operation of the first source code reverse section Diagram showing an example of source code Diagram showing an example of an object list Flow chart showing the operation of the second source code reverse section Diagram to explain the process of creating process specifications Diagram to explain the process of creating process specifications Flowchart showing the operation of the mapping unit Diagram showing an example of function dependency information Diagram showing an example of functional specifications The figure for demonstrating the operation of the mapping part by a user. The figure for demonstrating the operation of the mapping part by a user. Flowchart showing the operation of the function specification part Flowchart showing the operation of the function specification part Figure showing an example of affected function information Diagram for explaining the operation of the function specification part by the user Flow chart showing the operation of the change impact analysis unit A diagram showing an example of change impact information on a function Diagram illustrating another source code Diagram illustrating another object list Diagram illustrating another process specification Diagram illustrating another process specification Diagram illustrating another process specification Diagram illustrating another process specification Diagram illustrating another process specification Diagram illustrating another functional specification Another diagram illustrating the affected function information Another diagram exemplifying the change impact information on the function Diagram to illustrate the relationship between the function being modified and the function affected The figure which shows the input / output of the data to the component of the change influence analysis apparatus which concerns on Embodiment 2. A flowchart showing the operation of the change impact analysis unit according to the second embodiment. Diagram showing an example of function, process, and function correspondence information The figure for demonstrating the modification of Embodiment 2

Each of the plurality of embodiments and variations thereof described below has a characteristic configuration. The characteristic configuration or behavior in one form is also applicable in other forms, and the invention is not limited to the forms exemplified below.

Embodiment 1.
1. 1. Configuration Figure 1 is a block diagram showing the configuration of the change impact analysis device 10 according to the first embodiment. The change impact analysis device 10 is a device that reads a source code or the like including a function to be changed and calculates the degree of influence that the change of the function has on the entire software (hereinafter referred to as the change impact degree). The change effect analysis device 10 includes a processor 20, a storage unit 30, a display unit 40, and an operation unit 50. The processor 20 is an example of a control unit.

The processor 20 can be realized by a central processing unit (CPU), an MPU, a DSP, a microcomputer, an FPGA, an ASIC, or the like. The processor 20 realizes various functions by reading an OS, an application program, and various data and executing arithmetic processing. The processor 20 includes, as a functional configuration, a first source code reverse unit 21, a second source code reverse unit 22, a mapping unit 23, a function designation unit 24, and a change effect analysis unit 25.

The storage unit 30 is composed of a flash memory, an SSD (Solid State Device), a hard disk, and the like. The storage unit 30 stores programs and data necessary for realizing various functions of the change effect analysis device 10.

The display unit 40 displays a character string or an image described later based on an operation by the user. The display unit 40 is composed of a liquid crystal display, an organic EL display, and the like.

The operation unit 50 is composed of a keyboard, a mouse, and the like. The user operates the change influence analysis device 10 via the operation unit 50.

2. 2. Operation The operation of the change effect analyzer 10 configured as described above will be described with reference to FIGS. 1 to 33.

In FIG. 1, the first source code reverse unit 21, the second source code reverse unit 22, and the mapping unit 23 input the source code 60 to be analyzed and the function dependency information 63, and the functional specifications are based on the input. Generate 64. On the other hand, the function designation unit 24 inputs the source code 60 and generates the affected function information 65 based on the source code 60. After that, the change influence analysis unit 25 inputs the functional specification 64 and the affected function information 65, and generates the change influence degree information 66 for the function based on the input. The change impact information 66 for the function is an example of software impact information.

FIG. 2 is a diagram showing data input / output to the first source code reverse unit 21, the second source code reverse unit 22, and the mapping unit 23. The first source code reverse unit 21 inputs the source code 60 to be analyzed, reverses it using a reverse engineering technique based on the source code 60, generates an object list 61, and stores it in the storage unit 30.

The source code 60 includes the function to be changed. The source code 60 is written in C language. The source code 60 includes comments written in Japanese based on a predetermined format. The source code 60 is created in advance by the user and stored in the storage unit 30.

The object list 61 includes identifiers (hereinafter, referred to as “labels”) such as variable names and function names included in the source code 60, and their Japanese descriptions. The change effect analysis device 10 manages the labels and their Japanese descriptions in association with each other by using the object list 61.

Next, the second source code reverse unit 22 inputs the source code 60 and the object list 61, generates a process specification 62 based on the input code 60, and stores it in the storage unit 30.

The process specification 62 is data representing the process of each function included in the source code 60, that is, the flow of input, processing, and output. The process specification 62 includes three fields, an input field, a processing field, and an output field. The process specification 62 is written in a language that can be understood by humans, in this example, Japanese.

Next, the mapping unit 23 inputs the process specification 62 and the function dependency information 63, generates the functional specification 64 based on the input, and stores it in the storage unit 30.

The function dependency information 63 is data in a list format in which the name of the function realized by the function included in the source code 60 and the function block included in the function are associated with each other. The function dependency information 63 is created in advance by the user and stored in the storage unit 30.

The functional specification 64 is data in which the name of the function to be changed and the process for realizing the function are described. The function to be changed is realized including the function to be changed.

FIG. 3 is a diagram showing data input / output to the function designation unit 24. The function designation unit 24 inputs the source code 60, generates the affected function information 65 based on the source code 60, and stores it in the storage unit 30.

The affected function information 65 is data in which the functions affected by changing the function to be changed are described in a list format.

FIG. 4 is a diagram showing data input / output to the change impact analysis unit 25. The change influence analysis unit 25 inputs the functional specification 64 and the affected function information 65, generates change influence degree information 66 for the function based on the input, and stores it in the storage unit 30.

The change influence degree information 66 for the function is data in which the change influence degree is described. The degree of change impact is equal to the number of functions described in the affected function information 65.

2-1. Operation of the First Source Code Reverse Unit As shown in FIG. 2, the first source code reverse unit 21 inputs the source code 60, generates an object list 61 based on the input code 60, and stores the object list 61 in the storage unit 30. 5 and 6 are flowcharts showing the operation of the first source code reverse unit 21. FIG. 7 is a diagram showing an example of the source code 60 created in advance by the user. FIG. 8 is a diagram showing an object list 61a generated from the source code 60a as shown in FIG. 7 by the first source code reverse unit 21.

Hereinafter, the operation of the first source code reverse unit 21 will be described with reference to FIGS. 5 and 6.

In FIG. 5, first, the first source code reverse unit 21 reads the source code 60 from the storage unit 30 (S401). For example, the first source code reverse unit 21 reads the source code 60a of FIG. 7.

After that, the first source code reverse unit 21 inputs the Japanese description of the file name of the source code 60 into the file name field of the object list 61 (S402). In the example of FIG. 7, the first source code reverse unit 21 inputs the Japanese description “source code 1” of the file name of the source code 60a into the file name field of the object list 61a as shown in FIG.

After that, the first source code reverse unit 21 inputs the file name of the source code 60 excluding the extension into the label field of the file name of the object list 61 (S403). In the example of FIG. 7, the first source code reverse unit 21 sets the “sourcecode 1” obtained by removing the extension “.c” from the file name “sourcecode1.c” of the source code 60a, and sets the object list 61a as shown in FIG. Enter in the label field of the file name of.

After that, the first source code reverse unit 21 inputs information about the function included in the source code 60 into the object list 61 (S404 to S407).

Specifically, the first source code reverse unit 21 inputs 1 to the variable m (S404).

When the first source code reverse unit 21 determines that the source code 60 includes the m-th function (Yes in S405), the first source code reverse unit 21 inputs information about the m-th function into the object list 61 (S406). In the example of FIG. 7, when m = 1, the first source code reverse unit 21 inputs information about the first function xxxxxx included in the source code 60a into the object list 61a as shown in FIG. The details of this process will be described later.

After that, the first source code reverse unit 21 adds 1 to the variable m (S407).

On the other hand, when the first source code reverse unit 21 determines that the m-th function is not included in the source code 60 (No in S405), the first source code reverse unit 21 ends this process. In the example of FIG. 7, when m = 2, the first source code reverse unit 21 determines that the source code 60a does not include the second function, and ends this process.

FIG. 6 is a flowchart showing the details of the process (S406) of inputting the object related to the m-th function of FIG. 5 into the object list 61.

First, the first source code reverse unit 21 inputs the Japanese description of the function name of the m-th function of the source code 60 into the function field of the object list 61 (S408). In the example of FIG. 7, when m = 1, the Japanese description "xxxxxx function" of the function name of the first function of the source code 60a is input to the function field of the object list 61a as shown in FIG.

After that, the first source code reverse unit 21 inputs the function name of the m-th function of the source code 60 into the label field of the function of the object list 61 (S409). In the example of FIG. 7, when m = 1, the function name “xxxxxx” of the first function of the source code 60a is input to the label field of the function of the object list 61a as shown in FIG.

After that, the first source code reverse unit 21 inputs the Japanese description of the input variable of the m-th function of the source code 60 into the input field of the object list 61 (S410). In the example of FIG. 7, when m = 1, the Japanese description “outside air temperature” and “operation mode” of the input variables of the first function of the source code 60a are set in the input fields of the object list 61a as shown in FIG. Enter in.

After that, the first source code reverse unit 21 inputs the input variable name of the m-th function of the source code 60 into the input label field of the object list 61 (S411). In the example of FIG. 7, when m = 1, the input variable names “outdoor_temp” and “drive_mode” of the first function of the source code 60a are input to the input label field of the object list 61a as shown in FIG. ..

After that, the first source code reverse unit 21 inputs the Japanese description of the input value to the input variable of the m-th function of the source code 60 into the input attribute field of the object list 61 (S412). In the example of FIG. 7, when m = 1, the Japanese description “10 ° C.” of the input value to the input variable “object_temp” of the first function of the source code 60a and the input value to the input variable “drive_mode”. Enter the Japanese description "cooling" in the input attribute field of the object list 61 as shown in FIG.

After that, the first source code reverse unit 21 inputs the input value to the input variable of the m-th function of the source code 60 into the input attribute label field of the object list 61 (S413). In the example of FIG. 7, when m = 1, the input value “10” to the input variable “object_temp” of the first function of the source code 60a and the input value “col” to the input variable “drive_mode” are set. , As shown in FIG. 8, input in the label field of the input attribute of the object list 61, respectively.

After that, the first source code reverse unit 21 inputs the Japanese description of the output variable name of the m-th function of the source code 60 into the output field of the object list 61 (S414). In the example of FIG. 7, when m = 1, the Japanese description “measurement state” of the output variable name of the first function of the source code 60a is input to the output field of the object list 61a as shown in FIG.

After that, the first source code reverse unit 21 inputs the output variable name of the m-th function of the source code 60 into the output label field of the object list 61 (S415). In the example of FIG. 7, when m = 1, the output variable name “measured_st” of the first function of the source code 60a is input to the output label field of the object list 61a as shown in FIG.

After that, the first source code reverse unit 21 inputs the Japanese description of the character string assigned to the output variable of the m-th function of the source code 60 in the output attribute field of the object list 61 (S416). In the example of FIG. 7, when m = 1, the Japanese description “start” of the assigned character string to the output variable “measured_st” of the first function of the source code 60a is set to the object list 61a as shown in FIG. Enter in the output attribute field.

After that, the first source code reverse unit 21 inputs the character string assigned to the output variable of the m-th function of the source code 60 into the label field of the output attribute of the object list 61 (S417). In the example of FIG. 7, when m = 1, the assigned character string “START” to the output variable “metered_st” of the first function of the source code 60a is set to the output attribute label of the object list 61a as shown in FIG. Enter in the field. As described above, the object list 61 is generated from the source code 60 and stored in the storage unit 30.

2-2. Operation of the Second Source Code Reverse Section As shown in FIG. 2, the second source code reverse section 22 inputs the source code 60 and the object list 61, generates a process specification 62 based on the input, and stores the process specification 62 in the storage section 30. Remember. FIG. 9 is a flowchart showing the operation of the second source code reverse unit 22. 10 and 11 are diagrams for explaining a process in which the process specification 62 is generated by the second source code reverse unit 22. Note that FIG. 10 is a diagram conceptually explaining the process specification 62 in an intermediate state generated in the process of processing by the second source code reverse unit 22 for convenience of explanation. The information shown in FIG. 10 is stored in the storage unit 30. Finally, the second source code reverse unit 22 outputs the information shown in FIGS. 11A and 11B as the process specification 62.

Hereinafter, the operation of the second source code reverse unit 22 will be described according to the flowchart of FIG.

In FIG. 9, first, the second source code reverse unit 22 reads the source code 60 and the object list 61 from the storage unit 30 (S601). For example, the second source code reverse unit 22 reads the source code 60a of FIG. 7 and the object list 61a of FIG.

After that, the second source code reverse unit 22 generates the process specification 62 corresponding to each character string in the function column of the object list 61 and stores it in the storage unit 30 (S602). In the examples of FIGS. 7 and 8, since the character string in the function column is only the "xxxxxx function", only the process specifications corresponding to the "xxxxxx function" are generated.

After that, the second source code reverse unit 22 inputs each character string in the function column of the object list 61 into the uppermost column of the corresponding process specification 62 (S603). In the examples of FIGS. 7 and 8, the character string “xxxxxx function” in the function column of the object list 61a is input to the uppermost column of the process specification 62a1 as shown in FIG. 10 (A).

After that, the second source code reverse unit 22 inputs each character string in the input field of the object list 61 into the input field of the corresponding process specification 62 (S604). In the examples of FIGS. 7 and 8, the character strings “outside air temperature” and “operation mode” in the input field of the object list 61a are input to the input field of the process specification 62a1 as shown in FIG. 10 (A).

After that, the second source code reverse unit 22 inputs each character string in the output column of the object list 61 into the output column of the corresponding process specification 62 (S605). In the examples of FIGS. 7 and 8, the character string “measurement state” in the output column of the object list 61a is input to the output column of the process specification 62a1 as shown in FIG. 10 (A).

After that, the second source code reverse unit 22 inputs information about the conditional statement included in the source code 60 into the corresponding process specification 62 (S606, S607, S609 to S613).

Specifically, the second source code reverse unit 22 inputs 1 to the variable n (S606).

When the second source code reverse unit 22 determines that the source code 60 includes the nth conditional statement (Yes in S607), the second source code reverse unit 22 inputs the nth conditional statement to the processing column of the corresponding process specification 62. (S609). In the examples of FIGS. 7 and 8, when n = 1, the first conditional statement “(input_temp> 10) & & (drive_mode == cool)” of the source code 60a is processed as shown in FIG. 10 (A). Enter in the processing field of document 62a1.

After that, the second source code reverse unit 22 converts the character string in the processing column of the process specification 62 into a Japanese description (S610). In the examples of FIGS. 7 and 8, when n = 1, "(outdoor_temp> 10) && (drive_mode == cool)" in the processing column of the process specification 62a1 of FIG. 10 (A) is displayed in FIG. 10 (B). Convert to the Japanese description "(outside air temperature> 10 ° C.) and (operation mode = cooling)" as in the process specification 62a2 of.

At this time, "outdoor_temp" and "drive_mode" are converted into "outside air temperature> 10 ° C." and "operation mode", respectively, based on the correspondence between the input label field and the input field of the object list 61a. "10" and "cool" are converted into "10 ° C." and "cooling", respectively, based on the correspondence between the input attribute label column and the input attribute column of the object list 61a. The second source code reverse unit 22 includes conversion rule information that "&&" corresponds to "and", and "&&" is converted to "and" based on the conversion rule information.

Further, "(outside air temperature> 10 ° C.)" in the process specification 62a2 is converted into "(1)" as in the process specification 62a3 in FIG. 10 (C), and "(1) outside air temperature>" in the second line. 10 ° C. ”is input. “(Operation mode = cooling)” in the process specification 62a2 is converted into “(2)” as in the process specification 62a3, and “operation mode = cooling” is input in the third line.

After that, the second source code reverse unit 22 inputs the processing statement included in the nth conditional statement of the source code 60 into the processing column of the corresponding process specification 62 (S611). In the examples of FIGS. 7 and 8, when n = 1, the processing statement “measured_st = START;” corresponding to the first conditional statement of the source code 60a is as shown in the process specification 62a4 of FIG. 10 (D). Enter in the processing field.

After that, the second source code reverse unit 22 converts the character string in the processing column of the process specification 62 into a Japanese description (S612). In the examples of FIGS. 7 and 8, when n = 1, the character string “measured_st = START;” in the processing column of the process specification 62a4 is described in Japanese as in the process specification 62a5 of FIG. 11 (A). Convert to "Measurement status ← Start".

At this time, the second source code reverse unit 22 determines that "measured_st = START;" is a description of the operation, and inputs a symbol "·" indicating that it is a description of the operation at the beginning of the sentence. The "measured_st" is converted into a "measurement state" based on the correspondence between the output column of the object list 61a and the output label column. "START" is converted to "start" based on the correspondence between the output attribute column of the object list 61a and the label column of the output attribute. The second source code reverse unit 22 includes conversion rule information that "=" corresponds to "←", and "=" is converted to "←" based on the conversion rule information.

After that, the second source code reverse unit 22 adds 1 to the variable n (S613).

On the other hand, when the second source code reverse unit 22 determines that the source code 60 does not have the nth conditional statement (No in S607), the second source code reverse unit 22 describes the processing column of the process specification 62 based on the operation by the user. Change (S608). In the examples of FIGS. 7 and 8, when n is 2, the second source code reverse unit 22 determines that the source code 60 does not have the second conditional statement. The user modifies the process specification 62a5 of FIG. 11A to the process specification 62a6 of FIG. 11B via the operation unit 50.

In the process specification 62a6, the user defines the condition "outside air temperature> 10 ° C." as "(1)" and the condition "operation mode = cooling" as "(2)", and the condition "(1) and (2) The state in which ")" is true is defined as "discomfort detection". The process specification 62a6 means that the measurement state is started when the process of the xxxxxx function is in the "discomfort detection" state.

After that, the second source code reverse unit 22 ends this process. As described above, the process specification 62 is generated from the source code 60 and the object list 61 and stored in the storage unit 30.

2-3. Operation of the mapping unit As shown in FIG. 2, the mapping unit 23 inputs the process specification 62 and the function dependency information 63, generates the functional specification 64 based on the input, and stores it in the storage unit 30. FIG. 12 is a flowchart showing the operation of mapping. FIG. 13 is a diagram showing an example of the function dependency information 63 created in advance by the user. FIG. 14 is a diagram showing an example of the functional specification 64 generated by the mapping unit 23. 15 and 16 are diagrams for explaining the operation of the mapping unit 23 by the user.

Hereinafter, the operation of the mapping unit 23 will be described with reference to FIG.

In FIG. 12, first, the mapping unit 23 reads the process specification 62 and the function dependency information 63 from the storage unit 30 (S901). The function dependency information 63 is data created in advance by the user. For example, the mapping unit 23 reads the process specification 62a6 of FIG. 11B and the dependency information 63a of the function of FIG.

After that, the mapping unit 23 selects an arbitrary function name from the function name field of the function dependency information 63 according to the operation by the user, and determines the arrangement of the function name in the functional specification 64 (S902). In the examples of FIGS. 11B and 13, "xxxxxx function" is selected from the function name column of the function dependency information 63a, and is arranged in the uppermost column as in the functional specification document 64a of FIG.

After that, the mapping unit 23 selects the process specification 62 according to the operation by the user, and determines the arrangement of the character string in the processing column of the selected process specification 62 in the functional specification 64 (S903). In the examples of FIGS. 11B and 13, the character string in the processing column of the process specification 62a6 is arranged in the second column from the top as in the functional specification 64a of FIG.

After that, the mapping unit 23 generates the functional specification document 64 and stores it in the storage unit 30 (S904). In the examples of FIGS. 11B and 13, the functional specification 64a of FIG. 14 is generated.

FIG. 15 illustrates an operation by a user in a process of selecting a function name from the function dependency information 63 and determining the arrangement of the function name in the functional specification 64 (S902 in FIG. 12). It is a figure to do.

When the process specification 62a6 and the function dependency information 63a are read, the mapping unit 23 displays the function dependency information 63a on the display unit 40. The user selects an item to be mapped, that is, an item to be arranged in the functional specification 64 via the operation unit 50. FIG. 15A shows a state in which the function name “xxxxxx function” is selected.

When it is detected that the item to be mapped is selected, the mapping unit 23 displays the read process specification 62a6 so as to be selectable from the pull-down menu. FIG. 15B shows a state in which the process specification 62a6 is selected.

When it is detected that the process specification 62a6 is selected, the mapping unit 23 displays the process specification 62a6 on the display unit 40. The user selects a portion of the process specifications 62a6 that he / she wants to map via the operation unit 50. FIG. 15C shows a state in which the character string “xxxxxx function” in the uppermost column of the process specification 62a6 is selected.

FIG. 16 illustrates an operation by a user in a process of selecting a process specification 62 and determining the arrangement of a character string in a processing column of the selected process specification in the functional specification 64 (S903 in FIG. 12). It is a figure for.

When it is detected in FIG. 15C that the character string "xxxxxx function" in the uppermost column of the process specification 62a6 is selected, the mapping unit 23 displays the process specification 62a6 in a selectable manner from the pull-down menu. FIG. 16A shows a state in which the process specification 62a6 is selected.

When it is detected that the process specification 62a6 is selected, the mapping unit 23 displays the process specification 62a6 on the display unit 40. The user selects a portion of the process specifications 62a6 that he / she wants to map via the operation unit 50. FIG. 16B shows a state in which the character strings from the second line to the eighth line in the processing column of the process specification 62a6 are selected.

When it is detected that the location to be mapped is selected, the mapping unit 23 displays the function dependency information 63a on the display unit 40. The user selects a functional block corresponding to the location to be mapped via the operation unit 50. FIG. 16C shows a state in which “discomfort detection” of the function dependency information 63a is selected.

When it is detected that the functional block "discomfort detection" corresponding to the location to be mapped is selected, the mapping unit 23 selects the location to arrange the location to be mapped in the functional specification 64. FIG. 16D shows the second from the top when the head of the place where the place to be mapped is arranged via the operation unit 50 is aligned with the first line of the second column from the top of the functional specification document 64. The first to seventh lines in the column of are selected. When it is detected that the place where the place to be mapped is arranged is selected, the mapping unit 23 generates the functional specification document 64a. As described above, the functional specification 64 is generated from the process specification 62 and the functional dependency information 63 and stored in the storage unit 30.

2-4. Operation of the function designation unit As shown in FIG. 3, the function designation unit 24 inputs the source code 60, generates the affected function information 65 based on the source code 60, and stores it in the storage unit 30. 17 and 18 are flowcharts showing the operation of the function designation unit 24. FIG. 19 is a diagram showing an example of the affected function information 65 generated by the function designation unit 24. FIG. 20 is a diagram for explaining the operation of the function designation unit 24.

Hereinafter, the operation of the function designation unit 24 will be described with reference to FIGS. 17 and 18.

In FIG. 17, first, the function designation unit 24 selects the source code 60 (S1101) and reads it from the storage unit 30 (S1102) according to the operation by the user. For example, the function designation unit 24 selects and reads the source code 60a in FIG. 7.

After that, the function designation unit 24 analyzes the read source code 60 (S1103), and displays the function included in the source code 60 on the display unit 40 so as to be selectable by a user operation (S1104). For example, the function included in the source code 60 may be displayed selectably from a pull-down menu. After that, the function designation unit 24 selects the function to be changed according to the operation by the user (S1105). FIG. 20 shows a state in which the source code 60a is read and the function xxxxxx included in the source code 60a is selected.

After that, the function designation unit 24 generates the affected function information 65 and stores it in the storage unit 30 (S1106), and inputs the function included in the source code 60 into the affected function information 65 (S1107 to S1110).

The function designation unit 24 inputs 1 to the variable k (S1107).

When the function specifying unit 24 determines that the k-th function is included in the source code 60 (Yes in S1107), the function specifying unit 24 inputs information about the k-th function into the affected function information 65 (S1109). Details will be described later.

After that, the function designation unit 24 adds 1 to the variable k (S1110).

On the other hand, when the function designation unit 24 determines that the k-th function is not included in the source code 60 (No in S1108), the function designation unit 24 ends this process.

FIG. 18 is a flowchart showing a process (S1109 of FIG. 17) of inputting information about the k-th function into the affected function information 65.

First, when it is determined that the kth function does not refer to the function to be changed (No in S1111), the function specification unit 24 determines whether or not the function to be changed refers to the kth function. Judgment (S1112). In the example of FIG. 7, when k = 1, it is determined that the first function xxxxxx does not refer to the function xxxxxx to be changed.

After that, when it is determined that the function to be changed does not refer to the kth function (No in S1112), the function specification unit 24 refers to the kth function by the function having a reference relationship with the function to be changed. It is determined whether or not the function is performed (S1113). In the example of FIG. 7, when k = 1, it is determined that the function having a reference relationship with the function to be changed does not refer to the first function xxxxxx.

After that, when it is determined that the function having a reference relationship with the function to be changed does not refer to the kth function (No in S1113), the function specification unit 24 determines that the kth function is the function to be changed. It is determined whether or not the function in the reference relationship is referenced (S1114). In the example of FIG. 7, when k = 1, it is determined that the function having a reference relationship with the function to be changed does not refer to the first function xxxxxx.

After that, when it is determined that the kth function does not refer to the function having a reference relationship with the function to be changed (No in S1114), the function designation unit 24 ends this process. In the example of FIG. 7, when k = 1, the function specification unit 24 determines that the first function xxxxxx does not refer to the function having a reference relationship with the function to be changed, and ends this process. do.

On the other hand, when it is determined that the kth function refers to the function to be changed (Yes in S1111), the function specification unit 24 inputs "1" in the influence classification field of the affected function information 65. (S1115), the function name of the kth function is input in the function field of the affected function information 65 (S1119), and this process is terminated.

When it is determined that the function to be changed refers to the kth function (Yes in S1112), the function specification unit 24 inputs "2" in the influence classification field of the affected function information 65 (S1116). ), Enter the function name of the kth function in the function field of the affected function information 65 (S1119), and end this process.

When it is determined that the function having a reference relationship with the function to be changed refers to the kth function (Yes in S1113), the function specification unit 24 puts "3" in the influence classification column of the affected function information 65. (S1117), enter the function name of the kth function in the function name field of the affected function information 65 (S1119), and end this process.

When it is determined that the kth function refers to a function having a reference relationship with the function to be changed (Yes in S1114), the function specification unit 24 puts "4" in the influence classification column of the affected function information 65. (S1118), enter the function name of the kth function in the function field of the affected function information 65 (S1119), and end this process.

As described above, the affected function information 65 is generated from the source code 60 and stored in the storage unit 30.

2-5. Operation of the change impact analysis unit As shown in FIG. 4, the change impact analysis unit 25 inputs the functional specification 64 and the affected function information 65, generates change impact information 66 for the function based on the input, and stores the function specification 64. Store in 30. FIG. 21 is a flowchart showing the operation of the change influence analysis unit 25. FIG. 22 is a diagram showing an example of the change influence degree information 66 on the function generated by the change influence analysis unit 25.

Hereinafter, the operation of the change effect analysis unit 25 will be described with reference to FIG. 21.

In FIG. 21, first, the change influence analysis unit 25 reads the functional specification 64 and the affected function information 65 from the storage unit 30 (S1601). For example, the change influence analysis unit 25 reads the functional specification 64a of FIG. 14 and the affected function information 65a of FIG.

After that, the change influence analysis unit 25 determines the arrangement of the character string in the uppermost column of the functional specification document 64 in the change influence degree information 66 for the function (S1602). In the examples of FIGS. 14 and 19, the change influence analysis unit 25 arranges the character string "xxxxxx function" in the uppermost column of the functional specification document 64a in the function column of the change influence degree information 66a on the function as shown in FIG. Determine.

After that, the change influence analysis unit 25 calculates the change influence degree, that is, the number of functions included in the affected function information 65 (S1603). In the examples of FIGS. 14 and 19, since the affected function information 65a does not include the function, the change influence analysis unit 25 calculates “0” as the change influence degree.

After that, the change influence analysis unit 25 determines the arrangement of the calculated change influence degree in the change influence degree information 66 with respect to the function (S1604). In the examples of FIGS. 14 and 19, the arrangement of the change influence degree “0” in the change influence degree column of the change influence degree information 66a for the function is confirmed.

After that, the change influence analysis unit 25 generates the change influence degree information 66 for the function and stores it in the storage unit 30 (S1605). In the examples of FIGS. 14 and 19, change influence degree information 66a on the function is generated. As described above, the change influence degree information 66 on the function is generated from the functional specification 64 and the affected function information 65 and stored in the storage unit 30. The processor 20 displays the change influence degree information 66 on the function on the display unit 40 based on the operation by the user via the operation unit 50.

3. 3. Operation example of the change effect analyzer when another source code is read In the above description, the change effect is illustrated by exemplifying the source code 60a in which the function to be changed does not include other functions as shown in FIG. The operation of the analyzer 10 has been described. In the following, the operation of the change effect analysis device 10 will be described by exemplifying the source code 60b in which the function to be changed includes other functions as shown in FIG. 23.

FIG. 23 is a diagram illustrating another source code 60b. FIG. 24 shows an object list 61b generated from the source code 60b. Compared to the source code 60a, the source code 60b further includes functions 1 to 4. Therefore, the first source code reverse unit 21 inputs the information about the functions 1 to 4 into the object list 61b in addition to the information about the functions xxxxxx (S404 to S407 in FIG. 5). At this time, the first source code reverse unit 21 inputs the Japanese description of the function name and the function name into the object list 61b (S408 and S409 in FIG. 6), and the functions 1 to 4 have no input and output. Enter the character string "None" in the input field and the output field (S411 to S417 in FIG. 6).

25 to 29 show the process specification 62 created based on the source code 60b and the object list 61b. Compared to the object list 61a, the object list 61b further includes functions 1 to 4 in the function column. Therefore, the second source code reverse unit 22 further generates the process specifications of the functions 1 to 4 in addition to the process specifications of the function xxxxxx (S602 in FIG. 9).

Further, the function xxxxxx of the source code 60b further includes "f2 ();" as compared with the function xxxxxx of the source code 60a. The second source code reverse unit 22 determines that "f2 ();" is a description of the operation, and inputs a symbol "·" indicating that it is a description of the operation. Further, "f2 ();" is converted to "function 2" based on the correspondence between the function column of the object list 61b and the label column of the function (S613 in FIG. 9). Therefore, the second source code reverse unit 22 outputs the process specification 62b1 of FIG. 25. Similarly, the second source code reverse unit 22 outputs the process specifications 62b2 to 62b5 of the functions 1 to 4 shown in FIGS. 26 to 29.

FIG. 30 is a diagram illustrating another functional specification 64b. The functional specification 64b is generated from the process specifications 62b1 to 62b5 and the function dependency information 63a of FIG. Compared with the process specification 62a6 of FIG. 11B, the process specification 62b1 further includes the character string “・ function 2” in the processing column. Therefore, the mapping unit 23 generates the functional specification 64b as shown in FIG.

FIG. 31 is a diagram illustrating another affected function information 65b. The affected function information 65b is generated from the source code 60b. Compared to the source code 60a, the source code 60b further includes functions 1 to 4 associated with the function to be modified xxxxxx. The function designation unit 24 classifies the functions 1 to 4 into four.

FIG. 33 is a diagram for explaining the relationship between the functions xxxxxx and the functions 1 to 4. In FIG. 33, the arrow points from the referencing function to the referenced function. Since the function 1 refers to the function xxxxxx, it is classified as "1" (S1115 in FIG. 18). Since the function 2 is referred to by the function xxxxxx, it is classified as "2" (S1116 in FIG. 18). Since the function 3 refers to the function 2 which has a reference relationship with the function xxxxxx, it is classified as "3" (S1117 in FIG. 18). Since the function 4 is referred to by the function 2 which has a reference relationship with the function xxxxxx, it is classified into "4" (S1118 in FIG. 18).

FIG. 32 is a diagram illustrating another change influence degree information 66b on the function. The change influence degree information 66b on the function is generated from the functional specification 64b and the affected function information 65b. The xxxxxx function is realized by the function xxxxxx to be changed, and there are four functions related to the function xxxxxx according to the affected function information 65b. Is entered as "4".

As described above, the change influence analysis device 10 of the present embodiment calculates and displays the degree of change influence on the function to be changed. In addition to "the number of times the function to be changed is referenced by other functions", "the number of times the function to be changed refers to other functions" and "the direct reference relationship with the function to be changed" It is calculated in consideration of "the number of times a function in the above refers to another function" and "the number of times a function having a direct reference relationship with the function to be changed is referred to by another function". By referring to the calculated change impact, the user can better understand the impact of a particular feature change on the software as a whole. As a result, the user can efficiently divert and develop the software in consideration of the influence.

4. Summary As described above, the change impact analyzer 10 according to the present embodiment analyzes the source code 60 and shows the influence of the function to be changed on the entire software based on the source code 60. It is a device that outputs the influence degree information 66. The change impact analyzer 10 includes a processor 20 that performs source code analysis processing. The processor 20 includes a first source code reverse unit 21, a second source code reverse unit 22, a mapping unit 23, a function designation unit 24, and a change effect analysis unit 25. The first source code reverse unit 21 generates an object list 61 in which each function included in the source code 60 is described from the source code 60. The second source code reverse unit 22 generates a process specification 62 in which the inputs, processes, and outputs of each process realized by each function are described from the object list 61. The mapping unit 23 describes the processing of the process to be changed that realizes the function to be changed from the process specification 62 and the dependency information 63 of the function that defines each function realized by each process. Generate 64. The function specification unit 24 generates the affected function information 65 in which other functions affected by the function to be changed are described from the source code 60. The change influence analysis unit 25 outputs the change influence degree information 66 for the function from the functional specification 64 and the affected function information 65.

The change impact degree information 66 on the function is information in which the function to be changed is associated with the change influence degree indicating the degree of influence on the entire software from the function to be changed.

The degree of change impact is "the number of times the function to be changed is referenced by another function", "the number of times the function to be changed refers to another function", and "the direct reference relationship with the function to be changed". It is a value calculated based on "the number of times a function refers to another function" and "the number of times a function having a direct reference relationship with the function to be changed is referred to by another function".

More specifically, the degree of influence of the change is "the number of times the function to be changed is referenced by another function", "the number of times the function to be changed refers to another function", and "the function to be changed". The sum of "the number of times a function in a direct reference relationship refers to another function" and "the number of times a function in a direct reference relationship with the function to be changed is referred to by another function". be.

Alternatively, the degree of impact of the change is "the number of times the function to be changed is referenced by another function", "the number of times the function to be changed refers to another function", and "the number of times the function to be changed refers to another function" and "direct reference to the function to be changed". It may be a value obtained by multiplying "the number of times the related function refers to another function" and "the number of times the function having a direct reference relationship with the function to be changed is referred to by another function". Other than that, it may be a value that increases by associating in combination.

By referring to the change impact information 66 on the function, the user can appropriately grasp the effect of the change of a specific function on the entire software. As a result, the user can efficiently divert and develop the software in consideration of the influence.

Embodiment 2.
Hereinafter, another embodiment of the change impact analysis device 10 will be described.

The change influence analysis device 10 of the first embodiment causes the user to recognize the difficulty level of the change by displaying the function to be changed and the change influence degree of the function on the display unit 40. On the other hand, the change influence analysis device 10 of the present embodiment displays the function to be changed and the process and function for realizing the function on the display unit 40. This makes the user aware of the difficulty of the change in more detail.

FIG. 34 is a diagram showing data input / output to the change impact analysis unit 25a according to the present embodiment. In the change influence analysis device 10 of the present embodiment, the function of the change influence analysis unit 25a is different from that of the first embodiment. The change influence analysis unit 25a inputs the process specification 62, the functional specification 64, and the affected function information 65, generates the correspondence information 67 of the function, the process, and the function based on the input, and stores it in the storage unit 30. The function, process, and function correspondence information 67 is an example of software impact information.

The correspondence information 67 of the function, the process, and the function is data in which the function to be changed and the process and the function that realize the function are described.

The operation of the change influence analysis unit 25a according to the present embodiment will be described.

FIG. 35 is a flowchart showing the operation of the change impact analysis unit 25a according to the present embodiment. FIG. 36 is a diagram showing an example of correspondence information 67 of a function, a process, and a function.

First, the change effect analysis unit 25a reads the process specification 62, the functional specification 64, and the affected function information 65 from the storage unit 30 (S1701). For example, the change effect analysis unit 25a reads the process specifications 62b1 to 62b5 of FIGS. 25 to 29, the functional specifications 64b of FIG. 30, and the affected function information 65b of FIG.

After that, the change effect analysis unit 25a determines the arrangement of the character string in the uppermost column of the functional specification document 64 in the correspondence information 67 of the function, process, and function (S1702). In the examples of FIGS. 25 to 29, 30, and 31, the change impact analysis unit 25a has the corresponding information 67b of the function, process, and function of the character string "xxxxxx function" in the uppermost column of the functional specification document 64b, as shown in FIG. Confirm the placement of in the function column.

After that, the change impact analysis unit 25a determines the function, process, and function of the process name of each function described in the function column of the affected function information 65 and the line number of the process specification in which the process is described. The arrangement of the corresponding information 67 in the process column is confirmed (S1703).

In the examples of FIGS. 25 to 29, 30, and 31, according to the affected function information 65b, the process function 1 calls the process of the xxxxxx function. The process name "function 1" and the line number "○" in the processing column of the process specification 62b2 of the function 1 are arranged. Similarly, since the process function 2 is called by the process of the xxxxxx function, the line number "3" of the process column of the process name "xxxxxx function" and the process specification 62b1 of the xxxxxx function is arranged. Since the process function 3 calls the process function 2, the process name "function 2" and the line number "Δ" in the processing column of the process specification 62b3 of the function 2 are arranged. Since the process function 4 calls the process function 2, the process name "function 4" and the line number "x" in the processing column of the process specification 62b5 of the function 4 are arranged.

After that, the change effect analysis unit 25a determines the arrangement of each character string in the function column of the affected function information 65 in the corresponding information 67 of the function, process, and function (S1704). In the examples of FIGS. 25 to 29, 30, and 31, as shown in FIG. 36, the functions of the character strings “function 1”, “function 2”, “function 3”, and “function 4” in the function column of the affected function information 65b, respectively. The arrangement of the process and function correspondence information 67b in the function column is confirmed.

After that, the change effect analysis unit 25a generates the correspondence information 67 of the function, the process, and the function and stores it in the storage unit 30 (S1705). In the examples of FIGS. 25 to 29, 30, and 31, the correspondence information 67b of the function, process, and function of FIG. 36 is generated. As described above, the function, process, and function correspondence information 67 is generated from the process specification 62, the functional specification 64, and the affected function information 65, and is stored in the storage unit 30. The processor 20 displays the correspondence information 67 of the function, the process, and the function on the display unit 40 based on the operation by the user via the operation unit 50.

As described above, the change impact analysis device 10 according to the present embodiment displays the correspondence information 67 of the function, the process, and the function on the display unit 40. The correspondence information 67 of a function, a process, and a function is data in which the function to be changed is associated with the process and the function that realizes the function. By referring to the correspondence information 67 of the function, the process, and the function, the user can grasp the function to be changed in association with the process and the function. This allows the user to divert and develop the software in consideration of the processes and functions affected by the change of a specific function.

As described above, the change impact analysis unit 25a according to the present embodiment further reads the process specification 62 and outputs the correspondence information 67 of the function, the process, and the function.

The correspondence information 67 of a function, a process, and a function is information in which the function to be changed is associated with the process and the function affected by the function to be changed.

By referring to the correspondence information 67 of the function, the process, and the function, the user can grasp the function to be changed in association with the process and the function. This allows the user to divert and develop the software in consideration of the processes and functions affected by the change of a specific function.

Other embodiments.
As described above, an embodiment has been described as an example of the technique in the present invention. However, the technique of the present invention is not limited to this, and can be applied to embodiments in which changes, replacements, additions, omissions, etc. are made as appropriate. Further, it is also possible to combine the components described in the above-described embodiment into a new embodiment.

In the above embodiment, the source code 60 is written in C language, but is not limited thereto. For example, it may be described in other languages such as C ++, Java®, Python, and Ruby.

In the above embodiment, the process specification 62 is described in Japanese, but is not limited thereto. For example, it may be written in other languages such as English, French, and Spanish.

The change impact analyzer 10 of the first embodiment outputs only the change impact degree information 66 for the function, and the change impact analyzer 10 of the second embodiment outputs only the correspondence information 67 of the function, the process, and the function. , Not limited to this. For example, the change impact analyzer 10 displays the selection screen of FIG. 37 before starting the analysis, and the user can use at least one of the change impact degree information 66 for the function and the correspondence information 67 of the function, process, and function. You may be able to select one.

10 Change impact analysis device 20 Processor 21 1st source code reverse unit 22 2nd source code reverse unit 23 Mapping unit 24 Function specification unit 25, 25a Change impact analysis unit 30 Storage unit 40 Display unit 50 Operation unit 60 Source code 61 Object list 62 Process specifications 63 Function dependency information 64 Functional specifications 65 Affected function information 66 Change impact information on functions 67 Function, process, and function correspondence information

Claims (5)

A device that analyzes source code and outputs software impact information that shows the impact of the function to be changed on the entire software based on the source code.
A control unit that performs analysis processing of the source code is provided.
The control unit
From the source code, a first source code reverse part that generates an object list in which each function included in the source code is described, and
From the object list, a second source code reverse unit that generates a process specification in which the inputs, processes, and outputs of each process realized by each function are described, and
Mapping that generates a functional specification that describes the processing of the process to be changed that realizes the function to be changed from the dependency information of the function that defines the process specification and each function realized by each process. Department and
From the source code, a function specification unit that generates affected function information, in which other functions affected by the function to be changed are described, and
A change impact analysis device including a change impact analysis unit that outputs the software impact information from the functional specifications and the affected function information. The software impact information is
This is information in which the function to be changed is associated with the degree of influence of the change, which indicates the degree of influence of the function to be changed on the entire software.
The change impact analyzer according to claim 1. The degree of influence of the change is
The number of times the function to be changed is referenced by other functions, and
The number of times the function to be changed refers to another function,
The number of times a function that has a direct reference relationship with the function to be changed refers to another function, and
The number of times a function that has a direct reference relationship with the function to be changed is referenced by another function, and
The change impact analyzer according to claim 2, which is a value calculated based on the above. The change impact analysis unit further reads the process specifications and outputs the software impact information.
The change impact analyzer according to claim 1. The software impact information is information in which the function to be changed is associated with a process and a function affected by the function to be changed.
The change impact analyzer according to claim 4.

Images