JP2020038586A - Determination device, determination method, and determination program - Google Patents

Abstract

To determine whether a plurality of source codes created from a reference source code have been properly updated.SOLUTION: A determination device 1 includes an analysis unit 2 configured to generate relevant information indicating a relation between programs with respect to a reference source code, a first source code, and a second source code, a calculating unit 3 configured to calculate, on the basis of the relevant information of each source code, difference information for each of the first and second source codes with respect to difference from the reference source code and calculate an applied difference indicating a difference between the calculated difference information, and an evaluation unit 4 configured to determine whether the first source code and the second source code are the same on the basis of the applied difference, and when the first source code and the second source code are not the same, determine difference information of the second source code based on the first source code.SELECTED DRAWING: Figure 1

Description

  The present disclosure relates to a determination device, a determination method, and a determination program.

  When a company builds an IT system, it creates "common source code" that includes functions commonly used by multiple companies and reduces some company-specific functions to a common source code in order to reduce the construction cost. Perform the customization work to be added and create the "dedicated source code".

  On the other hand, when the common source code is updated while customizing the common source code at a certain point in time and creating the dedicated source code and continuing to operate the IT system, the same update is performed on the dedicated source code as well. Need to be implemented.

  The update content added by customization exists in the dedicated source code, and there is a risk that if the integration is performed mechanically, the update content will not be appropriately reflected and a part of the update content will be lost. Therefore, in order to prevent a part of the update content from being lost, the update (update content) for the common source code is not reflected in the source code, but is received in the form of a text or a design document. Then, by manually applying the contents of the text or design document received by the developer or the operator to the dedicated source code, it is possible to prevent a part of the updated contents from being lost.

  However, if the developer or the operator manually applies the updated content to the source code, the development cost or the operation cost increases. Further, even when the developer or the operator manually applies the updated content to the source code, it is not possible to sufficiently prevent a part of the updated content from being lost. Therefore, when a part of the reference source code is modified, there is a related technology that calculates the updated content as the difference content and applies the calculated difference content to the source code (for example, Patent Document 1 and Patent Document 1). 2).

  In Patent Document 1, a call graph indicating a call relationship of software before correction is compared with a call graph indicating a call relationship of software after correction, and it is determined that the call source of a subroutine has been changed. A technique applied to software is disclosed.

  Patent Document 2 discloses a target model in which a change in a target model obtained by an n-th change of a target model 0 and a change in a target model 1 are merged to appropriately apply updated contents. A technique for performing this is disclosed.

JP 2017-142712 A JP 2008-269136 A

  However, Patent Literatures 1 and 2 do not disclose determining that a plurality of source codes created by adding different update contents from a reference source code are the same. Further, Patent Literatures 1 and 2 do not disclose a technique for grasping an update content that becomes a difference when there is a difference between the plurality of source codes.

  The purpose of the present disclosure has been made in order to solve the above-described problem, and a determination device capable of determining whether a plurality of source codes created from a reference source code are appropriately updated, A determination method and a determination program are provided.

The determination device according to the present disclosure,
A reference source code, an analysis unit that generates relationship information indicating a relationship between programs included in each source code with respect to a first source code and a second source code created from the reference source code;
A difference information between the first source code and the second source code and the reference source code, based on the relationship information of each source code, and a difference between the relationship information and a relationship that is the difference. A calculation unit that calculates the difference information including a change type indicating a change content of the information, and calculates an applied difference indicating a difference between the difference information;
Based on the applied difference, it is determined whether the first source code and the second source code are the same, and if the first source code and the second source code are not the same, the first An evaluation unit that determines difference information of the second source code based on a source code.

The determination method according to the present disclosure,
Generating relationship information indicating a relationship between programs included in each of the reference source code and the first source code and the second source code created from the reference source code;
A difference information between the first source code and the second source code and the reference source code, based on the relationship information of each source code, and a difference between the relationship information and a relationship that is the difference. Calculating the difference information including a change type indicating a change content of the information, and calculating an applied difference indicating a difference between the difference information;
Based on the applied difference, it is determined whether the first source code and the second source code are the same, and if the first source code and the second source code are not the same, the first Determining difference information of the second source code based on the source code.

The determination program according to the present disclosure includes:
Generating relationship information indicating a relationship between programs included in each of the reference source code and the first source code and the second source code created from the reference source code;
A difference information between the first source code and the second source code and the reference source code, based on the relationship information of each source code, and a difference between the relationship information and a relationship that is the difference. Calculating the difference information including a change type indicating a change content of the information, and calculating an applied difference indicating a difference between the difference information;
Based on the applied difference, it is determined whether the first source code and the second source code are the same, and if the first source code and the second source code are not the same, the first Determining the difference information of the second source code based on the source code.

  According to the present disclosure, it is possible to determine whether a plurality of source codes created from a reference source code have been appropriately updated.

1 is a diagram illustrating a configuration example of a determination device according to an outline of an embodiment. FIG. 3 is a diagram illustrating a relationship between source codes related to the embodiment. FIG. 2 is a diagram illustrating a configuration example of a determination device according to the embodiment; FIG. 3 is a schematic diagram illustrating a relationship between each source code stored in a source code storage unit and a program. FIG. 3 is a conceptual diagram illustrating a relationship between programs included in each source code. FIG. 3 is a conceptual diagram illustrating a relationship between programs included in each source code. FIG. 3 is a conceptual diagram illustrating a relationship between programs included in each source code. FIG. 3 is a conceptual diagram illustrating a relationship between programs included in each source code. FIG. 4 is a diagram illustrating an example of relation information of each source code. FIG. 9 is a diagram for describing an outline of a process performed by a difference calculation unit. It is a figure showing an example of a relation information difference table. It is a figure explaining an example of a change difference table. It is a figure explaining processing of an application difference calculation part and an application difference evaluation part. It is a figure explaining processing of an application difference calculation part and an application difference evaluation part. FIG. 5 is a diagram illustrating an operation example of the determination device according to the embodiment. FIG. 5 is a diagram illustrating an operation example of the determination device according to the embodiment. FIG. 5 is a diagram illustrating an operation example of the determination device according to the embodiment. FIG. 5 is a diagram illustrating an operation example of the determination device according to the embodiment. FIG. 5 is a diagram illustrating an operation example of the determination device according to the embodiment. FIG. 5 is a diagram illustrating an operation example of the determination device according to the embodiment. FIG. 2 is a block diagram illustrating a hardware configuration of a determination device according to each embodiment of the present disclosure.

  Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. The following description and drawings are appropriately omitted and simplified for clarity of explanation. In the following drawings, the same elements are denoted by the same reference numerals, and a repeated description is omitted as necessary.

(Outline of Embodiment)
Prior to description of an embodiment of the present disclosure, an outline of the embodiment will be described. FIG. 1 is a diagram illustrating a configuration example of a determination device according to an outline of an embodiment. The determination device 1 determines whether a plurality of source codes created from a reference source code match. The determination device 1 may be, for example, a server, a computer device, or the like.

The determination device 1 includes an analysis unit 2, a calculation unit 3, and an evaluation unit 4.
The analysis unit 2 generates relationship information indicating a relationship between a reference source code and a program included in each of the first source code and the second source code created from the reference source code.

  The source code may be, for example, software, a batch file, or the like. Alternatively, the source code may be a program file in which a program group indicating a set of programs to be executed is set in one file.

  The program may be, for example, one or more functions included in the source code. Alternatively, the program may be, for example, one or more processing contents to be executed by the determination device 1 or an instruction to be executed by the determination device 1.

  The relationship information may be, for example, information indicating a relationship between a calling program and a called program. Alternatively, the relationship information may be, for example, information indicating a relationship between the processing orders to be executed.

  The calculating unit 3 is a difference information between each of the first source code and the second source code and the reference source code based on the relation information of each source code, and a difference between the relation information and a relation that is the difference. Difference information including a change type indicating information change content is calculated. The calculation unit 3 calculates an applied difference indicating a difference between pieces of difference information.

  The evaluation unit 4 determines whether the first source code and the second source code are the same based on the application difference calculated by the calculation unit 3. When the first source code and the second source code are not the same, the evaluation unit 4 determines difference information of the second source code based on the first source code.

  As described above, the analysis unit 2 generates the relationship information indicating the relationship between the programs included in each source program. The calculating unit 3 calculates difference information with respect to the reference source code for each of the first source code and the second source code based on the relation information of each source code, and calculates an applied difference indicating a difference between the difference information. I do. The evaluation unit 4 determines whether the first source code and the second source code are the same based on the applied difference. When the first source code and the second source code are not the same, the evaluation unit 4 determines difference information of the second source code based on the first source code. Therefore, by using the determination device 1 according to the embodiment, it is possible to determine whether a plurality of source codes created from a reference source code have been appropriately updated. Further, by using the determination device 10 according to the embodiment, even when a plurality of source codes created from the reference source code are not appropriately updated, it is possible to grasp the details of the difference. .

(Embodiment)
First, before describing the details of the embodiments, the issues are re-arranged. FIG. 2 is a diagram illustrating a relationship between source codes related to the embodiment.

  In FIG. 2, white blocks that are not shaded indicate source codes. The blocks shaded by oblique lines indicate the updated contents from the source code described at the starting point of the arrow, and the source code created based on the updated contents is described at the ending point of the arrow. For example, the common source code 2 indicates that the common source code 1 is a source code created by adding the update content of the common update 1 to the common source code 1.

  Of the source code shown in FIG. 2, a source code including functions commonly used by a plurality of companies is called a common source code, and a source code including functions used by some companies is a dedicated source code. Call. Further, among the common source codes, for example, a source code including functions commonly used by all the companies, and a reference source code is referred to as a common source code 1. The common source code 1 corresponds to the reference source code in the outline of the embodiment.

  Generally, a plurality of source codes are created from the common source code 1. One of the plurality of source codes is a common source code 2 created based on the common source code 1 with updated functions of functions commonly used by all companies. The updated content is referred to as a common update 1. The common update 1 is an update content (update work) for editing the common source code 1 when a new function that is assumed to be used in common by all companies is added and a discovered problem is corrected. The source code created by the common update 1 is referred to as a common source code 2.

  The other is the dedicated source code 1 created with the functions used by some companies as updated contents based on the common source code 1. The updated content is referred to as customization 1. If there is a company that cannot satisfy the request with only the common source code 1 due to the fact that some company-specific requests exist, for example, the customization 1 requires the update contents (update work) to realize the company-specific request. ).

  Although FIG. 2 illustrates that two source codes are created from the common source code 1, three or more source codes may be created. FIG. 2 shows only one of the common source code 2 and the dedicated source code 1 between the common source code 1 and the dedicated source code 2, but a plurality of source codes exist. May be. The common source code 2 and the dedicated source code 1 are source codes existing between the common source code 1 and the dedicated source code 2, and may be referred to as intermediate source codes.

  Even if two source codes are created from the common source code 1 as described above, if the number of source codes to be managed increases, management becomes difficult and development costs increase. It is preferable to make them common. Therefore, the source code is shared at any timing of updating the source code.

  As shown in FIG. 2, the dedicated source code 2 is created from the common source code 2, and the dedicated source code 2 is created from the dedicated source code 1. A task of making a change corresponding to the common update 1 to the dedicated source code 1 is referred to as a dedicated update 1. The operation of making a change corresponding to customization 1 to the common source code 2 is referred to as customization 2. The dedicated source code 2 is a source code created by the dedicated update 1 or the customization 2 and obtained by adding a change corresponding to the common update 1 and the customization 1 to the common source code 1. In other words, the dedicated source code 2 created from the common source code 2 and the dedicated source code 2 created from the dedicated source code 1 are common source codes.

  Here, since the dedicated source code 2 created from the common source code 2 and the dedicated source code 2 created from the dedicated source code 1 are common source codes, they must be the same source code. There is. However, a case where the dedicated source code 2 is created from the common source code 1 via the common source code 2 and a case where the dedicated source code 2 is created from the common source code 1 via the dedicated source code 1 correspond to each case. Update content is different. Therefore, the dedicated source code 2 created from the common source code 1 via the common source code 2 and the dedicated source code 2 created from the common source code 1 via the dedicated source code 1 are the same source code. There is a possibility that it will not.

  If a different dedicated source code 2 is created, a source code that further includes updated contents is created based on the different dedicated source code 2, and there is a concern about the quality of the entire IT system. Also, since the update from the common source code 1 is usually performed a plurality of times, for example, it is visually checked whether the source code created is the same every time the update is performed. Then, the development or operation efficiency becomes low. Further, for example, if it is visually checked whether or not the source code created at each update corresponding to the update is the same, there is a concern about the quality of the entire IT system.

  Therefore, in the present embodiment, an object is to determine whether or not the dedicated source code 2 created based on different changes from the reference common source code 1 is the same. Furthermore, in the present embodiment, even if a different dedicated source code 2 is created, it is an object to grasp which update content has not been applied.

Hereinafter, with reference to the drawings, details of an embodiment of the present disclosure will be described.
<Configuration example of determination device>
A configuration example of the determination device 10 will be described with reference to FIG. FIG. 3 is a diagram illustrating a configuration example of a determination device according to the embodiment. The determination device 10 corresponds to the determination device 1 in the outline of the embodiment. The determination device 10 is a device that determines whether or not a dedicated source code 2 created based on a different update content from a reference common source code 1 is the same. The determination device 10 may be, for example, a computer device or a server.

  The determination device 10 includes a relation information analysis unit 11, a difference calculation unit 12, an applied difference evaluation unit 13, a storage unit 14, and an output unit 15.

  The relation information analysis unit 11 corresponds to the analysis unit 2 in the outline of the embodiment. The relation information analysis unit 11 generates relation information between programs included in each source code for each source code stored in the source code storage unit 141 of the storage unit 14. The relationship information analysis unit 11 analyzes the relationship to itself and other resources described in the source code, and obtains information on the source code to be analyzed, the relationship source, and the relationship destination. This analysis can be performed by a general program analysis technique such as a static analysis.

  When generating the relation information, the relation information analysis unit 11 registers the generated relation information in the relation information table T1. The relation information table T1 is stored in the relation information storage unit 142 of the storage unit 14. Description of the relation information table T1 will be described later.

  The source code storage unit 141 stores a common source code 1, a common source code 2, a dedicated source code 1, a dedicated source code 2_1 created from the common source code 2, and a dedicated source code 2_2 created from the dedicated source code 1. Is stored. That is, the relational information analysis unit 11 generates the common source code 1, the common source code 2, the dedicated source code 1, the dedicated source code 2_1 created from the common source code 2, and the dedicated source code 2_2 created from the dedicated source code 1. Generate relation information for each of the.

  The exclusive source code 2_1 can be said to be a source code created based on the first modified content from the common source code 1 serving as a reference. The exclusive source code 2_2 can be said to be a source code created based on the second modified content from the common source code 1 serving as a reference. The common source code 2 can be said to be a source code created based on some of the first changes from the common source code 1 to the dedicated source code 2_1. The dedicated source code 1 can be said to be a source code created based on some of the second changes from the common source code 1 to the dedicated source code 2_2. In other words, the common source code 2 and the dedicated source code 1 can be said to be intermediate source codes.

  In the present embodiment, each source code described above is described as being stored in the source code storage unit 141 in advance, but each source code may be input from an input unit (not shown).

  The source code may be, for example, software, a batch file, or the like. Alternatively, the source code may be a program file in which a program group indicating a set of programs to be executed is set as one file.

  The program may be, for example, one or more functions included in the source code. Alternatively, the program may be, for example, one or more processing contents to be executed by the determination device 1 or an instruction to be executed by the determination device 1.

  The relationship information may be, for example, information indicating a relationship between a calling program and a called program. Alternatively, the relationship information may be, for example, information indicating a relationship between the processing orders to be executed.

  Here, the relationship between each source code stored in the source code storage unit 141 and the program will be described with reference to FIG. FIG. 4 is a schematic diagram showing the relationship between each source code stored in the source code storage unit and a program. The source code storage unit 141 holds one or more programs and information on source codes to which the programs belong.

  As shown in FIG. 4, the source code storage unit 141 stores each source code required to determine whether the dedicated source codes 2_1 and 2_2 match. Specifically, the source code storage unit 141 stores a common source code 1 S1, a common source code 2 S2, a dedicated source code 1 S3, a dedicated source code 2_1 S4, and a dedicated source code 2_2 S5, respectively. In each source code, a program included in the source code is collectively stored. For example, if the common source code 1 S1 includes programs A to E, the common source code 1 S1 is set as one folder, and the programs A to E are stored in the folder.

  Next, the relationship between programs included in each source code and each program will be described with reference to FIGS. 5 to 8, and the relationship information generated for each source code will be described with reference to FIG. FIGS. 5 to 8 are conceptual diagrams showing the relationship between programs included in each source code. FIG. 9 is a diagram illustrating an example of related information of each source code.

  FIG. 5 shows the relationship between the programs included in the common source code 1. As shown in FIG. 5, the common source code 1 includes programs A to E, and the program A, the program B, and the program C are related with the program A as a starting point.

  The relationship between the program A and the programs B and C is, for example, the relationship when the program A is a program that calls the programs B and C. Alternatively, the relationship between the program A, the program B, and the program C is, for example, a relationship in a processing order in which the program B and the program C are executed after the program A is executed. Program C is related to program D and program E.

  FIG. 6 shows a relationship between programs included in the common source code 2. As shown in FIG. 6, the common source code 2 includes programs A to E and a program H. Starting from the program A, the program A, the program B, and the program C are related. The relationship between program A, program B and program C is the same as in FIG. The program B is related to the program H. Program C is related to program D and program E.

  Here, in FIG. 6, the blocks shaded by vertical lines indicate that the program has been added to the common source code 1, and the blocks shaded by hatched lines indicate the program added to the common source code 1. Indicates that the program has been deleted. That is, the common source code 2 is a source code obtained by adding the program H from the common source code 1 and deleting the program E from the common source code 1.

  FIG. 7 shows a relationship between programs included in the dedicated source code 1. As shown in FIG. 7, the dedicated source code 1 includes programs A to E and a program X. Starting from the program A, the program A, the program B, and the program C are related. Program B is related to program X. The dedicated source code 1 is obtained by adding a program X from the common source code 1. Program C is related to program D and program E.

  FIG. 8 shows a relationship between programs included in the dedicated source code 2_2. That is, FIG. 8 shows a relationship diagram of the program of the dedicated source code 2_2 based on the dedicated source code 1. As shown in FIG. 8, the dedicated source code 2_2 includes programs A to E, a program H, and a program X. Starting from the program A, the program A, the program B, and the program C are related. Program B is related to program H and program X. Program C is related to program D and program E. However, the program E is a program deleted from the dedicated source code 1. Note that when the updated contents are appropriately applied to the dedicated source code 2_1 and the dedicated source code 2_2, the programs A to D, the program H, and the program X included in the dedicated source code 2_2 are also included in the dedicated source code 2_1. Will be included.

  Next, with reference to FIG. 9, the related information of each source code will be described. FIG. 9 is a diagram illustrating an example of a relation information table T1 in which relation information of each source code is registered. The relation information table T1 is a table in which relation information of a program included in each source code is registered. In the relation information table T1, a source code name, a relation source, and a relation destination are set in order from the left of the table.

In the source code name, the name of the source code related to the registered related information is set.
In the relation source and the relation destination, the relation source and the relation destination between the programs are set. For example, in the relationship between the program A and the program B included in the common source code 1, as shown in FIG. Therefore, the program A is set as the relation source, and the program B is set as the relation destination. Therefore, as shown in FIG. 9, “common source code 1” is set as the source code name, “program A” is set as the relation source, and “program B” is set as the relation destination. The relation information analysis unit 11 similarly analyzes the relation source and relation destination programs for each program included in each source code, and registers the relation information in the relation information table T1.

  Returning to FIG. 3, the difference calculation unit 12 will be described. The difference calculator 12 corresponds to the calculator 3 in the outline of the embodiment. The difference calculation unit 12 calculates, based on the relation information of each source code, a difference in relation information between a common source code 1 serving as a reference and a dedicated source code 2_1 created through the common source code 2, and Difference information including a change type of the related information that is a difference is calculated. Further, the difference calculation unit 12 is configured to calculate a difference in relation information between the common source code 1 serving as a reference and the dedicated source code 2_2 created through the dedicated source code 1, and a change type of the relation information serving as the difference. Is calculated. Further, the difference calculator 12 calculates a difference between the calculated difference information.

  First, an outline of processing performed by the difference calculation unit 12 will be described with reference to FIG. FIG. 10 is a diagram illustrating an outline of a process performed by the difference calculation unit. In FIG. 10, white blocks correspond to the respective source codes in FIG. 2 and indicate relation information of the respective source codes.

  The difference calculation unit 12 calculates a difference (relation information difference) of the relation information between the source codes using the relation information of each source code. The calculated relationship information difference is indicated by a block shaded by a horizontal line. This calculation process is performed by the relation information difference calculation unit 121.

  Next, the difference calculating unit 12 calculates a change difference between the common update 1 relation information difference and the customization 1 relation information difference by using the relation information difference indicated by the blocks shaded by horizontal lines. This calculation process is performed by the change difference calculation unit 122. In the following description, this change difference will be described as an existing change difference.

  Further, the difference calculation unit 12 calculates a change difference between the customization 2 relation information difference and the dedicated update 1 relation information difference by using the relation information difference indicated by blocks shaded by horizontal lines. This calculation process is performed by the change difference calculation unit 122. In the following description, this change difference will be described as a new change difference.

  That is, the difference calculator 12 calculates difference information between the common source code 1 as the reference source code and each of the intermediate source codes (the common source code 2 and the dedicated source code 1) based on the relation information of each source code. calculate. The difference calculation unit 12 calculates difference information between each intermediate source code (common source code 2 and dedicated source code 1) and each source code (dedicated source code 2_1 and dedicated source code 2_2).

  Further, the difference calculator 12 calculates a difference between the existing change difference and the new change difference. This difference may be described as an applied difference.

Returning to FIG. 3, the details of the difference calculator 12 will be described.
The difference calculator 12 includes a relation information difference calculator 121, a change difference calculator 122, and an applied difference calculator 123.

  The relationship information difference calculation unit 121 calculates difference information of the relationship information between the common source code 1 and the common source code 2 based on the relationship information of each source code generated by the relationship information analysis unit 11. Further, the relationship information difference calculation unit 121 calculates difference information of relationship information between the common source code 2 and the dedicated source code 2_1 based on the relationship information of each source code generated by the relationship information analysis unit 11.

  Further, the relationship information difference calculation unit 121 calculates difference information of the relationship information between the common source code 1 and the dedicated source code 1 based on the relationship information of each source code generated by the relationship information analysis unit 11. . Further, the relation information difference calculation unit 121 calculates difference information of relation information between the dedicated source code 1 and the dedicated source code 2_2 based on the relation information of each source code generated by the relation information analysis unit 11.

  The relationship information difference calculation unit 121 determines, based on one of the relationship information of the two source codes for which the difference is to be calculated, that the relationship information (the relationship source and the relationship destination) of the two source codes all match. Exclude information. The relationship information difference calculation unit 121 calculates the difference between the relationship information of two source codes based on one of the relationship information of the two source codes for which the difference is to be calculated. The relation information difference calculation unit 121 includes a change flag indicating the change content (change type) of the relation information in the relation information serving as the difference based on whether or not the relation information serving as the difference is included in the reference source code. To determine.

  Specifically, the relation information difference calculation unit 121 adds “delete” indicating the change content of the relation information to the relation information that exists only in the reference source code among the two source codes for which the difference is to be calculated. Is added. In addition, the relation information difference calculation unit 121 adds “addition” indicating the change content of the relation information to the relation information that exists only in the other source code that is not the reference among the two source codes for which the difference is calculated. Give. In this embodiment, one of the common source code 2 and the dedicated source code 2 is used as a reference.

  Then, the relation information difference calculation unit 121 registers the name of the relation information difference and the change flag in the relation information difference table T2. The relation information difference table T2 is stored in the relation information difference storage unit 143.

  The relation information difference table T2 and the relation information difference processing of the relation information difference calculation unit 121 will be described with reference to FIGS. FIG. 11 is a diagram illustrating an example of the relation information difference table.

  First, the relationship information difference table T2 will be described with reference to FIG. The relation information difference table T2 is a table in which the difference of the relation information calculated by the relation information difference calculation unit 121 is registered. The relationship information difference, the relationship source, the relationship destination, and the change flag are set in the relationship information difference information table T2.

  In the relation information difference, information indicating which relation information is different is set. As the relation information difference, one of the relation information differences indicated by the hatched blocks of the vertical lines in FIG. 10 is set. For example, in the case of a difference between the relation information of the common source code 1 and the relation information of the common source code 2, the relation information difference is set to the common update 1 relation information difference.

In the relationship source and the relationship destination, the relationship source and the relationship destination of the relationship information calculated as the relationship information difference are set.
In the change flag, a change type of the relation information calculated as the relation information difference is set, and specifically, “add” or “delete” is set. As described above, “delete” is set to the relationship information that exists only in the reference source code among the two source codes for which the difference is to be calculated. On the other hand, “added” is set to relation information that exists only in the other source code that is not a reference.

  The standard for calculating the common update 1 relation information difference and the customization 1 relation information difference is assumed to be the common source code 1. It is also assumed that the reference for calculating the customization 2 relation information difference and the dedicated update 1 relation information difference is the common source code 2 and the dedicated source code 1, respectively.

  Next, the relationship information difference processing of the relationship information difference calculation unit 121 will be described with reference to FIG. As shown in FIG. 9, a line in which “common source code 1” is set as the source code name indicates a line in which relation information of common source code 1 is set. A line in which the source code name is set to “common source code 2” indicates a line in which the related information of the common source code 2 is set.

  When calculating the difference between the relationship information between the common source code 1 and the common source code 2, the relationship information difference calculation unit 121 calculates the relationship information difference with reference to the common source code 1. First, the relation information difference calculation unit 121 excludes relation information in which the relation information (the relation source and the relation destination) all match. The remaining information includes a line whose source code name is “common source code 1”, whose relation source is “program C” and whose relation destination is “program E”, and whose source code name is “common source code 2” and whose relation source is “ This is a row in which the relation destination is “program H” in “program B”.

  Since the relationship between the programs whose relation source is “program C” and whose relation destination is “program E” is information deleted by the common source code 2, the relation information difference calculation unit 121 sets the change flag to “delete”. Is given. The relation information difference calculation unit 121 registers the information as a relation information difference in the relation information difference table T2.

  Further, since the relationship between the programs whose relation source is “program B” and whose relation destination is “program H” is information added in the common source code 2, the relation information difference calculation unit 121 sets “ Add ”. The relation information difference calculation unit 121 registers the information as a relation information difference in the relation information difference table T2.

  The relationship information difference calculation unit 121 performs the same process on each piece of relationship information, calculates the relationship information difference shaded with a vertical line in FIG. 10, and registers the difference in the relationship information difference table T2.

  Returning to FIG. 3, the change difference calculator 122 will be described. The change difference calculator 122 calculates a difference between the relationship information differences calculated by the relationship information difference calculator 121. The change difference calculation unit 122 excludes the relationship information in which the relationship source, the relationship destination, and the change flag all match in the relationship information difference table T2. The change difference calculation unit 122 inverts the change flag of the information remaining as the relation information difference of the customization 1 or the customization 2 among the information remaining as the relation information difference in the relation information difference table T2, and changes the information along with the name of the change difference. Register it in the change difference table T3. Inverting the change flag means that the change flag is changed to “delete” when the change flag is “add”, and is changed to “add” when the change flag is “delete”. The change difference table T3 is stored in the change difference storage unit 144.

  The change difference table T3 will be described with reference to FIGS. 10, 11, and 12. FIG. 12 is a diagram illustrating an example of the change difference table. The change difference table T3 is a table in which an existing change difference and a new change difference that are shaded in FIG. 10 are set.

As shown in FIG. 12, a change information difference, a relation source, a relation destination, and a change flag are set in the change difference table T3.
In the change information difference, information indicating which change information is the difference is set. Any of the change information differences indicated by the hatched blocks in FIG. 10 is set as the change information difference. For example, in the case of a difference between the customization 1 relation information difference and the common update 1 relation information difference, the existing change difference is set as the change information difference.

In the relationship source and the relationship destination, the relationship source and the relationship destination of the relationship information calculated as the difference between the two pieces of change information to be compared are set.
In the change flag, a change type of the related information calculated as a difference of the change information is set, and specifically, “add” or “delete” is set. As described above, the change flag of the relation information included in the customization 1 relation information difference or the customization 2 relation information difference among the two relation information differences for which the difference is calculated is inverted. This is because, for example, when comparing the common update 1 relation information difference and the customization 1 relation information difference, the customization 1 relation information difference is subtracted from the common update 1 relation information difference. In other words, it is performed to determine what difference is included in the customization 1 relation information difference based on the common update 1 relation information difference.

  A specific example will be described with reference to FIG. 11. When calculating the difference information between the common update 1 relation information difference and the customization 1 relation information difference, the change difference calculation unit 122 determines that the relation source, the relation destination, and the change flag all match. Exclude related information. In FIG. 11, since there is no related information corresponding to this condition, the change difference calculation unit 122 does nothing.

  Next, the change difference calculation unit 122 inverts the change flag of the relationship information of the customization 1 relationship information difference. Since the change flag of the customization 1 relation information difference is “addition”, the change difference calculation unit 122 sets the change flag to “delete” and subtracts the customization 1 relation information difference from the common update 1 relation information difference. Then, the change difference calculation unit 122 sets the calculated result in the change difference table T3 as an existing change difference. Similarly, the change difference calculation unit 122 calculates a new change difference and registers it in the change difference table T3.

  Returning to FIG. 3, the applied difference calculation unit 123 will be described. The application difference calculation unit 123 calculates a difference between the existing change difference and the new change difference. The applied difference calculation unit 123 excludes relation information in which the relation source, the relation destination, and the change flag included in the existing change difference and the new change difference are all the same. Further, the applied difference calculation unit 123 stores the information remaining in the existing change difference and the information obtained by inverting the change flag of the information remaining in the new change difference in the applied difference storage unit 145.

  Next, the applied difference evaluation unit 13 will be described. The applied difference evaluation unit 13 corresponds to the evaluation unit 4 in the outline of the embodiment. The applied difference evaluation unit 13 determines whether the dedicated source code 2_1 and the dedicated source code 2_2 are the same based on the applied difference calculated by the applied difference calculation unit 123. When the dedicated source code 2_1 and the dedicated source code 2_2 are not the same, the applied difference evaluation unit 13 determines difference information between the dedicated source code 2_1 and the dedicated source code 2_2 based on the applied difference.

  The applied difference evaluation unit 13 determines the state of the dedicated source code 2_1 and the state of the dedicated source code 2_2 from the state of the applied difference, and outputs the state to the output unit 15. If there is no applied difference, the applied difference evaluator 13 determines that there is no inconsistency in the states of the four pieces of related information, and that the related state between the dedicated source code 2_1 and the dedicated source code 2_2 is correct.

  If there is an applied difference, the applied difference evaluation unit 13 determines that there is an inconsistency in the state of the four pieces of related information, and that the related state between the dedicated source code 2_1 and the dedicated source code 2_2 is incorrect. The applied difference evaluation unit 13 outputs to the output unit 15 a determination as to whether the dedicated source code 2_1 and the dedicated source code 2_2 are the same, and outputs the applied difference to the output unit 15 if they are not the same.

  Here, a specific example of the processing performed by the applied difference calculating unit 123 and the applied difference evaluating unit 13 will be described with reference to FIGS. FIG. 13 and FIG. 14 are diagrams illustrating the processing of the applied difference calculation unit and the applied difference evaluation unit.

  FIGS. 12 and 13 show a change difference table T3 in which the existing change difference and the new change difference calculated by the change difference calculation unit 122 are registered. FIG. 12 shows a case where the existing change difference and the new change difference match in the change difference table T3. FIG. 13 shows a case where the existing change difference and the new change difference do not match in the change difference table T3.

  When the change difference table T3 is as shown in FIG. 12, the applied difference calculation unit 123 does not calculate anything as the applied difference because the existing change difference and the new change difference match. Since no applied difference has been calculated, the applied difference evaluation unit 13 determines that the dedicated source code 2_1 and the dedicated source code 2_2 are the same. Then, the applied difference evaluation unit 13 outputs to the output unit 15 that the dedicated source code 2_1 and the dedicated source code 2_2 are the same.

  For example, assuming that some information is missing in the dedicated update 1 relation information and the change difference table T3 is as shown in FIG. 13, the applied difference calculation unit 123 determines the existing change difference and the new change difference. Is calculated. The application difference calculation unit 123 calculates information of a line where the relation source is “program B”, the relation destination is “program H”, and the change flag is “add” as the application difference. FIG. 14 illustrates the application difference calculated by the application difference calculation unit 123.

  When the information that is the application difference is calculated, the application difference evaluation unit 13 determines that the dedicated source code 2_1 and the dedicated source code 2_2 are not the same because the application difference has been calculated. Then, the applied difference evaluation unit 13 outputs to the output unit 15 that the dedicated source code 2_1 and the dedicated source code 2_2 are not the same, and the calculated applied difference.

  Returning to FIG. 3, the description will be continued. The storage unit 14 stores various information. The storage unit 14 includes a source code storage unit 141, a relation information storage unit 142, a relation information difference storage unit 143, a changed difference storage unit 144, and an applied difference storage unit 145.

  The source code storage unit 141 stores a common source code 1, a common source code 2, a dedicated source code 1, a dedicated source code 2_1 created from the common source code 2, and a dedicated source code 2_2 created from the dedicated source code 1. I do. The source code storage section 141 also stores programs included in each source code.

The relation information storage unit 142 stores a relation information table T1 in which relation information of each source code generated by the relation information analysis unit 11 is set.
The relation information difference storage unit 143 stores the relation information difference table T2 in which the relation information difference calculated by the relation information difference calculation unit 121 is set.

The change difference storage unit 144 stores a change difference table T3 in which the change differences calculated by the change difference calculation unit 122 are set.
The applied difference storage unit 145 stores the applied difference calculated by the applied difference calculation unit 123.

  The output unit 15 displays the information output by the applied difference evaluation unit 13 to the user. Specifically, the output unit 15 outputs a determination result as to whether the dedicated source code 2_1 and the dedicated source code 2_2 are the same. When the dedicated source code 2_1 and the dedicated source code 2_2 are not the same, the output unit 15 further outputs the applied difference output by the applied difference evaluation unit 13.

<Operation example of determination device>
Subsequently, an operation example of the determination device 10 according to the embodiment will be described with reference to FIGS. 15 to 20 are diagrams illustrating an operation example of the determination device according to the embodiment.

First, the overall operation of the determination device 10 will be described with reference to FIG.
The relation information analysis unit 11 generates relation information of the source code stored in the source code storage unit 141 (Step S1).

Next, the relationship information difference calculation unit 121 calculates a difference between the relationship information of a specific pair from the relationship information stored in the relationship information storage unit 142 (Step S2).
Next, the change difference calculation unit 122 calculates a difference between the relationship information differences of a specific pair from the relationship information differences stored in the relationship information difference storage unit 143 (Step S3).

Next, the applied difference calculation unit 123 calculates a difference between the change differences stored in the change difference storage unit 144 (Step S4).
Finally, based on the applied difference stored in the applied difference storage unit 145, the applied difference evaluation unit 13 determines the application state of the update (update content) applied to the dedicated source code 2_1 and the dedicated source code 2_2. Evaluation is performed (step S5).

  Next, FIG. 16 will be described. FIG. 16 is a diagram illustrating details of the operation performed in step S1 of FIG.

  The relation information analysis unit 11 selects one of the source codes stored in the source code storage unit 141, analyzes the relation information of the source code, and generates the relation information (step S11). Note that the relation information analysis unit 11 performs the process of step S11 on all the source codes stored in the source code storage unit 141.

  For example, when an instruction to call another program B is described in the content of the program A described in the source code, the related information from the program A to the program B is created. The related information is similarly analyzed for other source codes.

  When the processing of step S11 is performed on all the source codes, the relation information analysis unit 11 registers the generated relation information (analysis result) in the relation information table T1 (step S12).

  Next, FIG. 17 will be described. FIG. 17 is a diagram illustrating details of the operation performed in step S2 of FIG.

  The relation information difference calculation unit 121 acquires the relation information of the common source code 1 and the relation information of the common source code 2 from the relation information table T1, and calculates the relation information difference of the common update 1 based on the common source code 1. It is calculated (step S21).

  The relation information difference calculation unit 121 acquires the relation information of the special source code 1 and the relation information of the special source code 2_2 from the relation information table T1, and calculates the relation information difference of the special update 1 based on the special source code 1. It is calculated (step S22).

  The relation information difference calculation unit 121 acquires the relation information of the common source code 1 and the relation information of the dedicated source code 1 from the relation information table T1, and calculates the relation information difference of the customization 1 based on the common source code 1. (Step S23).

  The relation information difference calculation unit 121 acquires the relation information of the common source code 2 and the relation information of the dedicated source code 2_1 from the relation information table T1, and calculates the relation information difference of the customization 2 based on the common source code 2. (Step S24).

  The relation information difference calculation unit 121 registers the calculated relation information differences in the relation information difference table T2 (Step S25).

  Next, FIG. 18 will be described. FIG. 18 is a diagram illustrating details of the operation performed in step S3 of FIG.

  The change difference calculation unit 122 acquires the common update 1 relation information difference and the customization 1 relation information difference from the relation information difference table T2, and uses the difference between the common update 1 relation information difference and the customization 1 relation information difference as an existing change difference. It is calculated (step S31).

  Specifically, the change difference calculation unit 122 excludes information in which the relation source, the relation destination, and the change flag all match in the common update 1 relation information difference and the customization 1 relation information difference. Next, the change difference calculation unit 122 inverts the change flag of the customization 1 related information difference among the remaining information. Then, the change difference calculation unit 122 calculates the existing change difference by integrating the relation information difference of the common update 1 relation information and the customization 1 relation information difference.

  The change difference calculation unit 122 acquires the dedicated update 1 related information difference and the customized 2 related information difference from the related information difference table T2, and sets the difference between the dedicated update 1 related information difference and the customized 2 related information difference as a new changed difference. It is calculated (step S32).

  Specifically, the change difference calculation unit 122 excludes information in which the relation source, the relation destination, and the change flag all match in the dedicated update 1 relation information difference and the customization 2 relation information difference. Next, the change difference calculation unit 122 inverts the change flag of the customization 2 relation information difference among the remaining information. Then, the change difference calculation unit 122 integrates the relationship information difference of the dedicated update 1 relationship information and the customization 2 relationship information difference to calculate an existing change difference.

  The change difference calculation unit 122 registers the existing change difference and the new change difference calculated in steps S31 and S32 in the change difference table T3 (step S33).

  Next, FIG. 19 will be described. FIG. 19 is a diagram illustrating details of the operation performed in step S4 of FIG.

  The application difference calculation unit 123 acquires the existing change difference and the new change difference from the change difference table T3, and calculates the difference between the existing change difference and the new change difference as an application difference (Step S41).

Specifically, the applied difference calculating unit 123 compares the information registered as the existing change difference and the information registered as the new change difference, and determines the information in which the relationship source, the relationship destination, and the change flag all match. exclude. The applied difference calculation unit 123 calculates the remaining information as an applied difference.
The applied difference calculation unit 123 stores the calculated applied difference in the applied difference storage unit 145 (Step S42).

  Next, FIG. 20 will be described. FIG. 20 is a diagram illustrating details of the operation performed in step S5 of FIG.

  The applied difference evaluation unit 13 checks whether there is an applied difference stored in the applied difference storage unit 145 (Step S51). In other words, the applied difference evaluation unit 13 checks whether there is a difference between the existing change difference and the new change difference.

  When there is no applied difference (NO in step S51), the applied difference evaluation unit 13 determines that the dedicated source code 2_1 and the dedicated source code 2_2 are the same. Therefore, the applied difference calculation unit 123 outputs to the output unit 15 that the dedicated source code 2_1 and the dedicated source code 2_2 are the same, and the output unit 15 notifies the user that the dedicated source code 2_1 and the dedicated source code 2_2 are the same. Is output (step S52).

  On the other hand, when there is an applied difference (YES in step S51), the applied difference evaluating unit 13 determines that the dedicated source code 2_1 and the dedicated source code 2_2 are not the same. Therefore, the applied difference evaluation unit 13 outputs to the output unit 15 that the dedicated source code 2_1 and the dedicated source code 2_2 are not the same, and the output unit 15 notifies the user that the dedicated source code 2_1 and the dedicated source code 2_2 are not the same. Is output (step S53).

  Further, the applied difference evaluation unit 13 determines the applied difference as difference information of the dedicated source code 2_2 based on the dedicated source code 2_1, outputs the content of the applied difference to the output unit 15, and the output unit 15 The content of the difference is output to the user (step S54).

  As described above, the relation information analysis unit 11 generates the relation information indicating the relation between the programs included in each source program. The relationship information difference calculation unit 121 calculates various differences based on the relationship information of each source code, and calculates an applied difference. The applied difference evaluation unit 13 determines whether the dedicated source code 2_1 and the dedicated source code 2_2 are the same based on the applied difference. Therefore, by using the determination device 10 according to the embodiment, it is possible to determine whether a plurality of source codes created from a reference source code are appropriately updated.

  When the dedicated source code 2_1 and the dedicated source code 2_2 are not the same, the applied difference evaluation unit 13 determines difference information of the dedicated source code 2_2 based on the dedicated source code 2_1. Therefore, by using the determination device 10 according to the embodiment, even if a plurality of source codes created from a reference source code are not appropriately updated, the difference contents of the plurality of source codes can be grasped. It is possible to do.

  Further, the determination device 10 according to the present embodiment has a table for registering various differences. Therefore, if the dedicated source code 2_1 and the dedicated source code 2_2 are not the same, the user traces the difference information calculated as the applied difference through each table, and a part of the update content is lost in any source code. Can be determined.

  Specifically, when the dedicated source code 2_1 and the dedicated source code 2_2 are not the same, the user can find the missing part by following the change difference table T3, the relation information difference table T2, and the relation information table T1. It becomes possible. Therefore, according to the present embodiment, it is possible to suppress a decrease in the quality of the IT system.

  Furthermore, the determination device 10 according to the present embodiment has an output unit 15, and the output unit 15 outputs the determination result of the applied difference evaluation unit 13 and the applied difference to the user. By confirming the output content of the output unit 15, the user can determine whether the update content of the dedicated source code 2_1 or the dedicated source code 2_2 has been applied without omission, without relying on visual observation. Therefore, according to the present embodiment, it is possible to improve the development efficiency or the operation efficiency while suppressing the quality deterioration of the IT system.

(Other embodiments)
<1> In the embodiment described above, the following modifications may be made.
In the storage unit 14, each storage unit may further prepare another storage unit for each set of information stored therein. For example, instead of the change difference storage unit 144, a configuration may be provided that has an existing change difference storage unit and a new change difference storage unit.

  In the above-described embodiment, the storage unit 14 is described as having a configuration including the source code storage unit 141, the related information storage unit 142, the related information difference storage unit 143, the changed difference storage unit 144, and the applied difference storage unit 145. However, one storage unit may hold all information.

  In the above-described embodiment, the difference calculation unit 12 has been described as including the relation information difference calculation unit 121, the change difference calculation unit 122, and the applied difference calculation unit 123, but one calculation unit performs all calculations. May go. In this case, the operation may be suppressed only for the process related to the change flag, or the dummy information may be calculated and the result may be discarded.

  Further, as long as the information stored in all the storage units includes information required by the present apparatus, information calculated by an apparatus other than the present apparatus may be input. Further, in the configuration of the present apparatus, the processing up to the step of calculating the information input by the above-described method may be skipped, or the processing unit for performing the processing may be omitted.

  Furthermore, the processing target of the determination device 10 according to the above-described embodiment is not limited to a source code or a program. If a particular description can be associated with a specific description and the related information represented by the description, the information asset may be included in the target. At that time, the source code storage unit 141 may be expanded to store various information assets, or a storage unit corresponding to a new information asset may be added. Further, the relational information analysis unit 11 may be extended to analyze a new information asset, or a relational information analysis unit corresponding to the new information asset may be added.

  <2> In FIG. 21, the determination devices 1 and 10 (hereinafter, referred to as the determination device 1 and the like) described in the above-described embodiment may have the following hardware configuration. FIG. 21 is a block diagram illustrating a hardware configuration of a determination device and the like according to each embodiment of the present disclosure.

Referring to FIG. 21, the determination device 1 and the like include a processor 1202 and a memory 1203.
The processor 1202 reads the software (computer program) from the memory 1203 and executes the software, thereby performing the processing of the determination device 1 and the like described using the flowchart in the above embodiment. The processor 1202 may be, for example, a microprocessor, an MPU (Micro Processing Unit), or a CPU (Central Processing Unit). Processor 1202 may include multiple processors.

  The memory 1203 is configured by a combination of a volatile memory and a nonvolatile memory. The memory 1203 may include storage located away from the processor 1202. In this case, the processor 1202 may access the memory 1203 via an I / O interface (not shown).

  In the example of FIG. 21, the memory 1203 is used to store a software module group. The processor 1202 can perform the processing of the determination device 1 and the like described in the above-described embodiment by reading these software modules from the memory 1203 and executing them.

  As described with reference to FIG. 21, each of the processors included in the determination device 1 or the like executes one or a plurality of programs including a group of instructions for causing a computer to execute the algorithm described with reference to the drawings.

  In the above example, the program can be stored and supplied to a computer using various types of non-transitory computer readable media. Non-transitory computer readable media include various types of tangible storage media. Examples of non-transitory computer readable media include magnetic recording media (eg, flexible disks, magnetic tapes, hard disk drives), and magneto-optical recording media (eg, magneto-optical disks). Further, examples of the non-transitory computer-readable medium include a CD-ROM (Read Only Memory), a CD-R, and a CD-R / W. Further, examples of the non-transitory computer-readable medium include a semiconductor memory. The semiconductor memory includes, for example, a mask ROM, a PROM (Programmable ROM), an EPROM (Erasable PROM), a flash ROM, and a RAM (Random Access Memory). Also, the program may be supplied to the computer by various types of transitory computer readable media. Examples of transitory computer readable media include electrical signals, optical signals, and electromagnetic waves. Transitory computer readable media can provide the program to a computer via a wired communication line such as an electric wire and an optical fiber, or a wireless communication line.

  The present disclosure is not limited to the above embodiment, and can be appropriately modified without departing from the gist. In addition, the present disclosure may be implemented by appropriately combining the embodiments.

Reference Signs List 1, 10 determination device 2 analysis unit 3 calculation unit 4 evaluation unit 11 relation information analysis unit 12 difference calculation unit 13 applied difference evaluation unit 14 storage unit 15 output unit 121 relation information difference calculation unit 122 change difference calculation unit 123 applied difference calculation unit 141 Source code storage unit 142 Relation information storage unit 143 Relation information difference storage unit 144 Changed difference storage unit 145 Applied difference storage unit

Claims (7)

A reference source code, an analysis unit that generates relationship information indicating a relationship between programs included in each source code with respect to a first source code and a second source code created from the reference source code;
A difference information between the first source code and the second source code and the reference source code, based on the relationship information of each source code, and a difference between the relationship information and a relationship that is the difference. A calculation unit that calculates the difference information including a change type indicating a change content of the information, and calculates an applied difference indicating a difference between the difference information;
Based on the applied difference, it is determined whether the first source code and the second source code are the same, and if the first source code and the second source code are not the same, the first An evaluation unit that determines difference information of the second source code based on a source code. The analysis unit generates the relationship information of the intermediate source code generated between the reference source code and each source code,
The calculation unit is configured to determine, based on the relation information of each source code, second difference information between the reference source code and each intermediate source code, each of the intermediate source codes, the first source code, and the second source code. The determination device according to claim 1, further comprising calculating third difference information from the second difference information and calculating the applied difference based on the second difference information and the third difference information.   The calculation unit calculates a first change difference indicating a difference between the second difference information and a second change difference indicating a difference between the third difference information, and calculates the first change difference and the second change difference. The determination device according to claim 2, wherein a difference from the difference is calculated as the applied difference.   The calculation unit selects one of the two source codes from which each difference information is calculated as a reference source code, calculates a difference between the relationship information of the two source codes, and becomes the difference. The determination device according to any one of claims 1 to 3, wherein the change type of the relationship information serving as the difference is determined based on whether or not the relationship information is included in the selected source code.   Outputting the determination result of the evaluation unit, and further outputting difference information of the second source code based on the first source code when the first source code and the second source code are not the same. The determination device according to claim 1, further comprising a unit. Generating relationship information indicating a relationship between programs included in each of the reference source code and the first source code and the second source code created from the reference source code;
A difference information between the first source code and the second source code and the reference source code, based on the relationship information of each source code, and a difference between the relationship information and a relationship that is the difference. Calculating the difference information including a change type indicating a change content of the information, and calculating an applied difference indicating a difference between the difference information;
Based on the applied difference, it is determined whether the first source code and the second source code are the same, and if the first source code and the second source code are not the same, the first Determining difference information of the second source code based on a source code. Generating relationship information indicating a relationship between programs included in each of the reference source code and the first source code and the second source code created from the reference source code;
A difference information between the first source code and the second source code and the reference source code, based on the relationship information of each source code, and a difference between the relationship information and a relationship that is the difference. Calculating the difference information including a change type indicating a change content of the information, and calculating an applied difference indicating a difference between the difference information;
Based on the applied difference, it is determined whether the first source code and the second source code are the same, and if the first source code and the second source code are not the same, the first Calculating difference information of the second source code based on the source code.

Images