JP2008123343A - Software differential measurement device, software differential measurement program, and recording medium recording it - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a software differential measurement device capable of accurately summing up the number of lines of a newly created program source code in pieces of software being developed simultaneously. <P>SOLUTION: The software differential measurement device is provided with an effective code extraction part, a measurement target configuration specific code extraction part, and a comparison part. In the effective code extraction part, software configurations as pairs of a program source code and compilation setting information are input, and among program source codes contained in the software configurations, codes (effective codes), from each of which a portion to be ignored in compilation work is deleted, are output. In the measurement target configuration specific code extraction part, effective codes as measurement targets and an effective code as a comparison target are input, and among the codes included in the effective codes as measurement targets, codes, from each of which a portion matching a portion of the effective code as a comparison target is deleted, are generated for extracting effective code portions specific to the measurement targets. In the comparison part, two codes are input to be compared mutually, and a difference between the two codes is output. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a software difference measuring device, a software difference measuring program, and a recording medium on which the software difference measuring program is recorded, and in particular, a software difference measuring device, a software difference measuring program, and a software difference measuring program for measuring the development scale of software. The present invention relates to a recorded recording medium.

  In software development, a method of dividing the scale of a newly developed program source by the time required for development is generally used as a method of calculating software productivity. In many cases, the number of program source code lines is used as an indicator of development scale.

  However, in recent software development, due to the increase in scale, it is difficult to newly create all the program source codes. For this reason, a development method of adding / changing based on existing program source code is often selected. Therefore, if the number of lines of the entire program source code is used as an indicator of the development scale of a certain software, the development scale is often not correctly indicated.

  Using such a development method, in order to measure the number of lines in the newly created program source code, obtain the difference between the existing program source code that was the basis and the program source code after addition / change. However, a method of counting the number of lines of the difference is used.

  For example, as a method for acquiring a difference between two program source codes, Japanese Patent Laid-Open No. 5-158765 (hereinafter, Patent Document 1) proposes a C language program difference information acquisition method.

  This C language program difference information acquisition method can acquire difference information that does not include differences in parts that do not directly affect the processing contents of the program, such as annotations and indentation, and is a newly created program for the purpose of productivity calculation Suitable for measuring the number of source code lines.

  In recent years, with the shortening of the software commercialization cycle, a plurality of similar software has been changed and developed at the same time.

  In this case, in addition to the above-mentioned development method for adding / changing based on the existing program source code, it is not necessary to develop a plurality of similar software separately, but to develop the program source code of the previously developed software in parallel. Add parts specific to similar software being developed and extract only the program source code required for the software that was previously developed during compilation, or extract only the program source code required for the software being developed in parallel By doing so, a method of developing a plurality of software at the same time is taken.

  In the case where the program source code is written in C language, a method called conditional compilation using a preprocessing instruction may be used as shown in FIG. FIG. 19 is a diagram showing a specific example of a function for acquiring the desktop area width on the screen. In the example shown in FIG. 19, there is a menu area at the right or left edge of the screen, and the desktop area width is acquired by subtracting the width of the menu area from the width of the screen. In this example, lines written as “#ifdef X100”, “#else”, and “#endif” are pre-processing instructions.

  The size of the screen may differ depending on the device on which the software is installed. In this case, a program corresponding to the size of each screen must be created individually for each software. In the function shown in FIG. 19, if a macro named “X100” is defined, the program source code shown in FIG. 20 is extracted. If not defined, the program source code shown in FIG. 21 is extracted. As described above, in the function shown in FIG. 19, the program source code for obtaining different screen widths is extracted without defining the macro “X100”.

  Two software "X100" and "X200" are being developed at the same time, with "X100" being developed in advance and "X200" being developed in parallel with "X100" And In the software developed in advance, the “X100” macro is defined and the “X200” macro is not defined. In the software developed in parallel, the “X200” macro is defined and “X100” is defined. If the macro is not defined, the program source code shown in FIG. 20 is a program source code required for the software developed in advance, and the program source code shown in FIG. 21 is a program required for the software developed in parallel. Source code.

  By adopting such a development method, the same function extension was required for multiple similar software, or an error was found in a common part of multiple similar software, and correction was required. In some cases, it can be done with a single addition / modification. In addition, it is possible to prevent the addition / correction omission in some software.

  For example, in the example shown in FIG. 19, even if the calculation formula for the desktop area width is changed, the calculation formula in the return statement in FIG. 19 is changed to a correct value regardless of the number of similar software. It's okay.

  In the case of such a development method, in order to measure the number of lines of the program source code newly created in the software developed in advance for the purpose of calculating productivity, a program unique to the software developed in advance In both the source code and the program source code common to a plurality of similar softwares, it is necessary to obtain a difference from the existing program source code and total the number of lines of the program source code of the difference.

  Similarly, for the purpose of calculating productivity, to measure the number of lines of newly created program source code in software that is being developed in parallel, only the program source code that is unique to the software being developed in parallel is already present. It is necessary to acquire the difference from the program source code and to count the number of lines of the program source code of the difference.

When measuring the number of lines of newly created program source code in software that is being developed in parallel, obtain the difference from the existing program source code of the program source code common to multiple similar software should not be done. This is because if the difference in the program source code common to a plurality of similar software is included in the number of lines of the newly created program source code, the number of lines of the program source code newly created in the plurality of similar software is measured. This is because duplication occurs and the overall development scale and productivity are calculated higher than the actual ones.
JP-A-5-158765

  However, when the number of lines of a program source code newly created by software developed in parallel using the C language program difference information acquisition method disclosed in Patent Document 1 is measured, the input program Whether the source code is program source code common to a plurality of similar software is not identified. Therefore, the total number of lines of newly created program source code for both the program source code unique to the software being developed in parallel and the program source code common to multiple similar software is obtained. There has been a problem that the number of lines of the newly created program source code cannot be obtained only by the program source code unique to the software being developed.

  The present invention has been made in view of such problems, and a software difference measuring device capable of accurately totaling the number of lines of a newly created program source code in software developed in parallel, It is an object of the present invention to provide a software difference measurement program and a recording medium on which the software difference measurement program is recorded.

  In order to achieve the above object, according to one aspect of the present invention, a software difference measurement device includes an effective code extraction unit that extracts an effective code from a software configuration, and a first effective code extracted from the first software configuration. And a unique code extracting means for extracting an effective code unique to the first software configuration from the second effective code extracted from the second software configuration. A first unique code that is an effective code unique to the first software configuration from the first effective code extracted from the software configuration and the second effective code extracted from the second software configuration; and a third software From the third effective code extracted from the configuration and the fourth effective code extracted from the fourth software configuration, the second Extracts the unique code, further comprising a comparing means for outputting a difference between the first unique code and the second unique code.

  Preferably, the unique code extracting unit extracts the first unique code by generating a code in which a portion of the code included in the first effective code is deleted from a portion that matches a certain part of the second effective code. To do.

  Preferably, the software configuration includes a pair of program source code and compile setting information, and the effective code extracting means includes code input means for acquiring the program source code from the software configuration, and compile for acquiring the compile setting information from the software configuration. A setting information input means, a compile setting information analyzing means for analyzing the compile setting information to extract a macro definition, a macro storage means for storing the macro, and whether the program source code is analyzed to determine whether it is an effective code. Code analysis means for determining, and preprocessing condition determination means for determining a preprocessing condition for the preprocessing command extracted by the code analysis means.

  More preferably, the preprocessing condition determining unit determines that the preprocessing condition is satisfied when the macro is included in the preprocessing command extracted by the code analyzing unit.

  Preferably, the first software configuration is a configuration of the first software in the measurement target environment, the second software configuration is a configuration of the second software in the comparison target environment, and the third software configuration is the measurement target. The fourth software configuration is the configuration of the fourth software in the comparison target environment, the software configuration includes the program source code, and the difference output by the comparing means is the first software configuration. This is a difference specific to the measurement target environment between the software program source code and the third software program source code.

  According to another aspect of the present invention, the software difference measurement program is a process for measuring a difference specific to the measurement target environment of the first software program source code and the third software program source code in the measurement target environment. The first effective code from the first software configuration that is the first software configuration, the third effective code from the third software configuration that is the third software configuration, and the third effective code in the environment to be compared An effective code extraction step of extracting a first effective code from a second software configuration that is a configuration of two software and a first effective code from a fourth software configuration that is a configuration of the fourth software in the environment to be compared; First soft from effective code and second effective code Unique code extraction step means for extracting a first unique code which is an effective code unique to the hardware configuration and extracting a second unique code which is an effective code unique to the third software configuration from the third effective code and the fourth effective code And a comparison step for outputting a difference between the first unique code and the second unique code.

  According to still another aspect of the present invention, the recording medium is a computer-readable recording medium and records the above-described software difference measurement program.

  According to the present invention, when a plurality of similar software is changed / developed at the same time, a source code program newly developed in a portion common to a plurality of similar softwares when obtaining the development scale of the software to be measured The development scale of the software to be measured can be obtained more accurately without including the development scale. As a result, software productivity can be calculated more accurately, leading to improvements in accuracy such as estimation of development period and resource allocation.

  Embodiments of the present invention will be described below with reference to the drawings. In the following description, the same parts and components are denoted by the same reference numerals. Their names and functions are also the same.

  FIG. 1 is a block diagram showing a specific example of the hardware configuration of the software difference measuring apparatus 100 according to the present embodiment. The hardware configuration of the software difference measuring apparatus 100 according to the present embodiment is the same as the hardware configuration of a general personal computer. Specifically, referring to FIG. 1, a software difference measurement apparatus 100 includes a calculation unit 101 including a CPU (Central Processing Unit) that controls the whole, a ROM (Read Only Memory), a RAM (Random Access Memory), and the like. ) And HD (Hard Disk) storage device 102, CD-ROM (Compact Disk-Read Only Memory) and other recording media such as a reading device, and a keyboard, mouse, communication device, etc. , And an output device 104 that outputs a calculation result such as a communication device or a display device. These are connected by a bus 105. Alternatively, the software difference measuring device 100 may be configured by a plurality of independent devices and connected by a dedicated line or a wireless communication line.

  Furthermore, the storage device 102 includes, as predetermined storage areas, a software configuration storage unit 1021 that stores a software configuration input from the input device, and a program storage unit 1022 that stores a software difference measurement program executed by the CPU. included. The software configuration here is assumed to be a combination of program source code and compile setting information.

  FIG. 2 is a block diagram illustrating a specific example of a functional configuration of the software difference measurement apparatus 100 for performing the software difference measurement process. Each unit shown in FIG. 2 is a function mainly formed in the CPU by executing the software difference measurement program stored in the program storage unit 1022 by the CPU, but at least a part of the software difference measurement device 100 is not shown. Other hardware configurations may be formed.

  With reference to FIG. 2, the calculation unit 101 of the software difference measurement device 100 includes an effective code extraction unit 1, a measurement target configuration specific code extraction unit 2, and a comparison unit 3.

  The effective code extraction unit 1 is a software configuration stored in the software configuration storage unit 1021 and reads the software configurations 4 and 6 to be compared and the software configurations 5 and 7 to be measured, From the program source code included in the software configuration, each code (this code is hereinafter referred to as an effective code) from which the portion ignored in the compilation operation is deleted is extracted and output to the measurement target configuration specific code extraction unit 2 .

  Here, “effective code” refers to program code that is actually used to generate a program corresponding to the environment. For example, if the program code is written in C language, it indicates a part including a character string that is deleted by preprocessing by a preprocessor or passed to a compiler without being replaced with a blank.

  The measurement target configuration unique code extraction unit 2 deletes a portion that matches a part of the effective code to be compared from the code included in the effective code to be measured input from the effective code extraction unit 1 and performs measurement. An effective code included in the target software configuration and a unique effective code portion (hereinafter also referred to as a unique code) is extracted. The extracted unique code is input to the comparison unit 3.

  The comparison unit 3 compares the two unique codes input from the measurement target configuration unique code extraction unit 2 and outputs the difference.

FIG. 3 is a block diagram illustrating a specific example of a detailed configuration of the effective code extraction unit 1.
Referring to FIG. 3, effective code extraction unit 1 includes a code input unit 8 that reads source code included in a software configuration, a compile option input unit 9 that reads a compile option included in the software configuration, and a compile option input. Analysis of the compile option read by the section 9 and extraction of the macro definition contents, an option analysis section 10, a macro storage section 11 for storing the macro definition contents, and analysis of the source code read from the code input section 8 A code analysis unit 12 for determining whether the code is an effective code, a counter storage unit 13 for storing numerical information used for the determination of the code analysis unit 12, and preprocessing of the source code input by the code input unit 8 The preprocessing condition determination unit 14 for determining the condition and the code analysis unit 12 determine that the code is an effective code. Configured to include a code output section 15 for outputting the code.

  In the present embodiment, the following description will be given assuming that the software difference measuring apparatus 100 according to the present embodiment is used for developing similar software that operates in two different environments, the X100 environment and the X200 environment. Do. Further, in this assumption, it is assumed that each software has two versions, version 1.0 and the next version, version 2.0. Then, using the software difference measuring device 100, a difference specific to the X200 environment is obtained from the differences between the software version 1.0 and version 2.0 of the X200 environment. In this assumption, the X200 environment is a measurement target environment and is referred to as a “measurement target environment”. The X100 environment is a comparison target for obtaining a difference specific to the measurement target environment, and is referred to as a “comparison target environment”.

In this case, the software configurations 4 and 6 to be compared and the software configurations 5 and 7 to be measured respectively represent the following software configurations:
Software configuration 4: X100 environment software configuration in version 1.0,
Software configuration 5: Software configuration of X200 environment in version 1.0,
Software configuration 6: Software configuration of X100 environment in version 2.0,
Software configuration 7: Software configuration of the X200 environment in version 2.0.

More specifically, specific examples of software configurations 4 to 7 are shown in FIGS.
Referring to FIG. 4, software configuration 4 is configured by a pair of program source code 16 and compile setting information 17. In the present embodiment, it is assumed that the program source code 16 is written in C language. The compile setting information 17 is a compiler option passed to the compiler. In this specific example, one software configuration includes one program source code and one compiler option that is compile setting information, but a plurality of these may be included. When a plurality of program source codes exist in one software configuration, the processing described later may be repeatedly executed for each program source code.

  Referring to FIGS. 5 to 7, software configurations 5 to 7 also include a program source code and a compiler option that is compile setting information in the same software configuration 4 as shown in FIG. 4. Are each included in the configuration.

  FIG. 8 is a flowchart showing a specific example of the software difference measurement process in the software difference measurement apparatus 100 according to the present embodiment. The processing shown in the flowchart of FIG. 8 is realized by the CPU executing a software difference measurement program stored in the software configuration storage unit 1021 and controlling each unit shown in FIGS. In the following description of the processing, specifically, it is assumed that the software difference measurement processing is performed on the software configurations 4 to 7 shown in FIGS.

  Referring to FIG. 8, first, effective code extraction unit 1 acquires software configuration 4 to be compared from software configuration storage unit 1021 as an input, and extracts effective code from program source code 16 ( Step S100). When the software configuration 4 is the configuration shown in FIG. 4, the effective code shown in FIG. 9 is extracted and output to the measurement target configuration specific code extraction unit 2 in step S100.

  Similarly, the effective code extraction unit 1 acquires the software configuration 5 to be measured from the software configuration storage unit 1021 as an input, and extracts the effective code from the program source code of the software configuration 5 (step S110). If the software configuration 5 is the configuration shown in FIG. 5, the effective code shown in FIG. 10 is extracted and output to the measurement target configuration specific code extraction unit 2 in step S <b> 110.

  Similarly, the effective code extraction unit 1 acquires the software configuration 6 to be compared from the software configuration storage unit 1021 as an input, and extracts the effective code from the program source code of the software configuration 6 (step S120). . When the software configuration 6 is the configuration shown in FIG. 6, the effective code shown in FIG. 11 is extracted and output to the measurement target configuration specific code extraction unit 2 in step S120.

  Similarly, the effective code extraction unit 1 acquires the software configuration 7 to be measured from the software configuration storage unit 1021 as an input, and extracts the effective code from the program source code of the software configuration 7 (step S130). . If the software configuration 7 has the configuration shown in FIG. 7, the effective code shown in FIG. 12 is extracted and output to the measurement target configuration specific code extraction unit 2 in step S130.

  Subsequently, the measurement target configuration unique code extraction unit 2 extracts the effective code extracted from the software configuration 4 of the X100 environment in version 1.0 which is the comparison target by the effective code extraction unit 1 in step S100, and the effective code extraction in step S110. The code that is specific to the X200 environment in version 1.0 is extracted using the effective code extracted from the software configuration 5 of the X200 environment in version 1.0 to be measured by the unit 1 (step S140). When the effective code extracted in step S110 is the effective code shown in FIG. 9 and the effective code extracted in step S110 is the effective code shown in FIG. 10, in step S140, the measurement target shown in FIG. The effective code (hereinafter referred to as “measurement target unique code”) unique to each is extracted and output to the comparison unit 3.

  Similarly, the measurement target configuration unique code extraction unit 2 extracts the effective code extracted from the software configuration 6 of the X100 environment in version 2.0, which is the measurement target by the effective code extraction unit 1 in step S120, and the effective code extraction in step S130. The code that is specific to the X200 environment in version 2.0 is extracted using the effective code extracted from the software configuration 7 of the X200 environment in version 2.0, which is the measurement target, by the unit 1 (step S150). When the effective code extracted in step S120 is the effective code shown in FIG. 11 and the effective code extracted in step S130 is the effective code shown in FIG. 12, in step S150, the measurement shown in FIG. A target unique code is extracted and output to the comparison unit 3.

  Finally, the comparison unit 3 uses the measurement target environment specific code in version 1.0 extracted by the measurement target configuration specific code extraction unit 2 in step S140 and the version 2 extracted by the measurement target configuration specific code extraction unit 2 in step S150. 0.0, the environment-specific partial difference in the comparison target environment X200 is output even between version 1.0 and version 2.0 by comparing the measurement target environment-specific code at the input and comparing them (step S160). . When the measurement target environment specific code extracted in step S140 is the effective code shown in FIG. 13 and the measurement target environment specific code extracted in step S150 is the effective code shown in FIG. 14, in step S160, The difference shown in FIG. 15 is output.

  FIG. 16 is a flowchart showing an effective code extraction process by the effective code extraction unit 1 in steps S100 to S130.

  Referring to FIG. 16, first, compile option input unit 9 reads a compile option included in the software configuration, option analysis unit 10 analyzes the compile option, and if the compile option includes a macro definition option. The macro is defined in the macro storage unit 11 (step S200). Various options are included in the options read from the compile option input unit 9, but in step S200, the option analysis unit 10 analyzes the compile option and affects whether or not a certain part of the source code is an effective code. The part to be detected is detected from the compile options, and the value is stored in the macro storage unit 11. For example, when the compile option is the compile option 17 shown in FIG. 4, a macro definition option such as “-DX100” corresponds to the part that affects the determination of whether a certain part of the source code is effective code. .

  In step S200, as one specific example, the macro storage unit 11 defines the extracted macro by storing the macro name and the macro definition character string in pairs in a table format as shown in FIG. . For example, if the macro definition option is “-DMAX_SIZE = 10”, the option analysis unit 10 analyzes that the macro name is “MAX_SIZE” and the macro definition character string is “10”. Are stored in the macro storage unit 11. If the macro definition option is “-DX100” as described above, the option analysis unit 10 analyzes that the macro name is “X100” and the macro definition character string is unknown. In the column, “1” is set as a specific example of a character string representing that fact, and the macro name and macro definition pair is stored in the macro storage unit 11.

  By storing in the macro storage unit 11 in this way, when a macro name is given, the table is searched with the macro name of each stored macro, and if there is a match with the macro name, the character string that is the definition content thereof Can be obtained.

  Subsequently, the code analysis unit 12 sets the counter value stored in the counter storage unit 13 to 0 (step S205). Subsequently, the code input unit 8 reads one line of data from the source code included in the software configuration (step S210). In step S <b> 210, the code input unit 8 reads lines that have not been read in order from the top of the source code, and the read source code for one line is passed to the code analysis unit 12.

  Subsequently, the code analysis unit 12 checks the counter value stored in the counter storage unit 13 (step S220). If the counter value is a positive value (YES in step S220), the processing after step S340 described later is performed. If not (NO in step S220), the processes after step S230 are performed. When the process is started and the source code on the first line is analyzed, the counter value is 0 in step S205, and the process proceeds to step S230 and subsequent steps.

  In step S230, the code analysis unit 12 checks whether the source code of the line read by the code input unit 8 is a #if statement or a #ifdef statement. If it is neither an #ifdef statement nor a #if statement (NO in step S230), the processing after step S270 described later is performed. If it is either an #ifdef statement or a #if statement (YES in step S230), the processing after step S240 is performed.

  In step S240, the code analysis unit 12 uses the preprocessing condition determination unit 14 to determine the conditions described in the #ifdef statement or #if statement. If the source code in the above line is an #ifdef statement, in step S240, the preprocessing condition determination unit 14 searches whether or not the macro name following “#ifdef” is stored in the macro storage unit 11, and the searched macro Is present, it is determined that the condition is satisfied.

  If the source code in the above line is an #if statement, the preprocessing condition determination unit 14 determines whether the conditional expression following “#if” is satisfied. In step S240, the preprocessing condition determination unit 14 divides the conditional expression into tokens, and checks whether a macro name that is the same character string as the token exists in the macro storage unit 11. If it exists, replace the character string of the matching token with the character string of the matching macro definition, interpret the conditional expression, and check whether the conditional expression is satisfied.

  Then, the code analysis unit 12 confirms the determination of the condition establishment by the preprocessing condition determination unit 14 (step S250). If the condition is satisfied (YES in step S250), the code analysis unit 12 adds 1 to the counter value stored in the counter storage unit 13 (step S260), and extracts the measurement target configuration specific code from the code output unit 15 The unit 2 is caused to output a blank line (a line in which nothing is described) (step S320). If the condition is not satisfied (NO in step S250), the code analysis unit 12 skips the process of step S260, that is, does not add the counter value, and the measurement target configuration unique code extraction unit 2 from the code output unit 15 does not add. To output a blank line (step S320).

  If the source code of the line read by the code input unit 8 is neither an #ifdef statement nor a #if statement (NO in step S230), the code analysis unit 12 further processes the line read by the code input unit 8. It is confirmed whether the source code is an #else statement (step S270). If it is an #else statement (YES in step S270), the code analysis unit 12 adds 1 to the counter value stored in the counter storage unit 13 (step S280), and the measurement target configuration unique code extraction unit from the code output unit 15 2 is made to output a blank line (step S320).

  If the source code of the line read by the code input unit 8 is not any of the #ifdef statement, #if statement, and #else statement (NO in step S270), the code analysis unit 12 further includes the code input unit. It is checked whether the source code of the line read by 8 is a #define statement (step S300). If the source code of the line read by the code input unit 8 is a #define statement that is a macro-defined code (YES in step S300), the code analysis unit 12 analyzes the #define statement and obtains the result of the analysis. The contents of the macro definition are stored in the macro storage unit 11 (step S310), and a blank line is output from the code output unit 15 (step S320). If not, that is, if the source code of the line read by the code input unit 8 is not any of the #ifdef statement, #if statement, #else statement, and #define statement (NO in step S300), code analysis The unit 12 outputs the line input from the code input unit 8 to the measurement target configuration specific code extraction unit 2 using the code output unit 15 (step S330).

  If it is confirmed in step S220 that the counter value is not a positive value (NO in step S220), the code analysis unit 12 uses the #ifdef or #if statement as the source code of the line read by the code input unit 8. It is confirmed whether or not there is (step S340). If it is either an #ifdef statement or a #if statement (YES in step S340), the code analysis unit 12 adds 1 to the counter value stored in the counter storage unit 13 (step S350), and the code output unit 15 The measurement target configuration unique code extraction unit 2 is caused to output a blank line (step S320).

  If the source code of the line read by the code input unit 8 is neither an #ifdef statement nor a #if statement (NO in step S340), the code analysis unit 12 further performs the source code of the line read by the code input unit 8 Is a #endif statement (step S360). If it is an #endif statement (YES in step S360), the code analysis unit 12 subtracts 1 from the counter value stored in the counter storage unit 13 (step S370), and the measurement target configuration unique code extraction unit from the code output unit 15 2 is made to output a blank line (step S320).

  When the source code of the line read by the code input unit 8 is not any of the #ifdef statement, #if statement, and #endif statement (NO in step S360), the code analysis unit 12 further includes the code input unit. It is checked whether the source code of the line read 8 is an #else statement and the counter value stored in the counter storage unit 13 is 1 (step S380).

  If the source code of the line read by the code input unit 8 is an #else statement and the counter value stored in the counter storage unit 13 is 1 (YES in step S380), the code analysis unit 12 stores the counter The counter value stored in the unit 13 is decremented by 1 (step S390), and a blank line is output from the code output unit 15 to the measurement target configuration specific code extraction unit 2 (step S320). When the source code of the line read by the code input unit 8 is not any of the #ifdef statement, #if statement, endif statement, and #else statement, or the counter value stored in the counter storage unit 13 is 1. If not (NO in step S380), the processing in step S390 is skipped, that is, the blank line is output from the code output unit 15 to the measurement target configuration specific code extraction unit 2 without subtracting the counter value ( Step S320).

  The code analysis unit 12 processes one line of source code read from the code input unit 8 and defines a macro in the line by executing the processes in steps S210 to S390 described above. That is, the portion that is the effective code is output from the code output unit 15 to the measurement target configuration specific code extraction unit 2 (step S310). If no effective code is included, a blank line is output from the code output unit 15 to the measurement target configuration specific code extraction unit 2 for that line (step S320).

  When the processing of steps S210 to S390 is completed, the code analysis unit 12 confirms whether the code input unit 8 has read all lines (step S400). If all lines have been read (YES in step S400), the effective code extraction process is completed. In this case, what is output by the code output unit 15 to the measurement target configuration specific code extraction unit 2 in the process so far is an effective code. If a line that has not been read remains (NO in step S400), the processes from step S210 are repeatedly executed until the processes for all the lines are completed.

  Specifically, when the effective code is extracted from the program source code 16 of the software configuration 4 shown in FIG. 4, the counter values for the first line “void GetImageExt (ImgType type)” to the sixth line “{” are shown. Is 0, the above steps S220 to S330 are executed, and as shown in FIG. 9, these lines are output as they are as the effective code. In the processing so far, the counter value remains 0.

  Next, the seventh line “#ifdef X100” is determined to be an #ifdef statement by the code analysis unit 12 in step S230, and further determined to be already defined in step S200 in step S240. Therefore, the condition is satisfied in step S250, and the counter value is kept at 0. Further, as shown in FIG. 9, the seventh line is output as a blank line as an effective code in step S320.

  Next, for the eighth line “case IMAGE_JPEG:” to the tenth line “break;”, since the counter value is 0, the above steps S220 to S330 are executed, and as shown in FIG. As for the 8th line to the 10th line, these lines are output as they are. In the processing so far, the counter value remains 0.

  Next, the eleventh line “# endif / * X100 * /” is determined to be an #endif statement by the code analysis unit 12 in step S290, and therefore, in step S320 as shown in FIG. As the effective code, the eleventh line is output as a blank line. In the processing so far, the counter value remains 0.

  Next, although the line 12 “#ifdef X200” is determined to be an #ifdef statement by the code analysis unit 12 in step S230, the macro is defined in step S200 in step S240. Therefore, the condition is not satisfied in step S250, and the counter value is set to 1 in step S260. Also, as shown in FIG. 9, the twelfth line is output as a blank line as an effective code in step S320.

  Next, for the 13th line “case IMAGE_SVG:” to the 15th line “break;”, since the counter value is 1, the above steps S340 to S380 are executed, and as shown in FIG. In step S320, the 13th to 15th lines are output as blank lines as effective codes. In addition, the counter value remains 1 in the processing so far.

  Next, with respect to the 16th line “# endif / * X200 * /”, the code analysis unit 12 determines that it is an #endif statement in step S360, so that the counter value returns to 0 in step S370. Also, as shown in FIG. 9, the 16th line is output as a blank line as an effective code in step S320.

  Finally, for the 17th line “case IMAGE_PNG:” to the 22nd line “}”, since the counter value is 0, the above steps S220 to S330 are executed, and as shown in FIG. Lines 17 to 22 are output as they are.

  9 is extracted from the program source code 16 of the software configuration 4 of FIG. Similarly, the effective codes shown in FIGS. 10 to 12 are extracted for the other software configurations 5 to 7.

  FIG. 18 is a flowchart showing the unique code extraction process performed by the measurement target configuration unique code extraction unit 2 in steps S140 and S150.

  Referring to FIG. 18, first, the measurement target configuration specific code extraction unit 2 reads one line from the effective code of the measurement target environment (step S500). In step S500, the measurement target configuration unique code extraction unit 2 reads one line that has not yet been read in the order of description of the effective code of the measurement target environment.

  Subsequently, the measurement target configuration unique code extraction unit 2 confirms that the line read in Step S500 is not a blank line (Step S510). When the line read in step S500 is a blank line (NO in step S510), the measurement target configuration specific code extraction unit 2 outputs a blank line to the comparison unit 3 (step S550).

  If the line read in step S500 is not a blank line (YES in step S510), the measurement target configuration specific code extraction unit 2 reads one line from the effective code of the comparison target environment (step S520). In step S520, the measurement target configuration unique code extraction unit 2 reads one line that has not yet been read in the description order of the effective code of the comparison target environment.

  Next, the measurement target configuration unique code extraction unit 2 confirms that the line read in Step S520 is a blank line (Step S530). When the effective code line of the measurement target environment read in step S500 is not a blank line and the effective code line of the comparison target environment read in step S520 is a blank line (YES in step S530), the measurement target The configuration specific code extraction unit 2 outputs the line of the effective code of the measurement target environment read in step S500 to the comparison unit 3 (step S540).

  When neither the effective code line of the measurement target environment read in step S500 nor the line read in step S520 is a blank line (NO in step S530), the measurement target configuration specific code extraction unit 2 sends a blank line to the comparison unit 3. Is output (step S550).

  Subsequently, the measurement target configuration unique code extraction unit 2 confirms whether or not all effective codes of the measurement target environment have been read (step S560). If all lines have been read (YES in step S560), the process is completed. If there are still unread lines (NO in step S560), the processes from step S5000 are repeatedly executed until the processes for all the lines are completed.

  Through the above processing, the measurement target configuration unique code extraction unit 2 outputs the portion that is not the unique code as a blank line and the portion that becomes the unique code to the comparison unit 3 as the content of the input source code as it is.

  Specifically, when the unique code is extracted from the effective code of the measurement target environment shown in FIG. 10 using the effective code of the comparison target environment shown in FIG. 9, the measurement target environment of FIG. When the fourth line, the seventh line to the thirteenth line, the seventeenth line, and the twenty-second line of the effective code are read, these lines are empty in the measurement target configuration specific code extraction unit 2 in step S510. As shown in FIG. 13, the fourth, seventh to thirteenth lines, the seventeenth line, and the twenty-second line are output as blank lines as unique codes in step S550 as shown in FIG.

  In step S500, the first to third lines, the fifth to sixth lines, the 18th to 21st lines, and the 23rd to 24th lines of the effective code of the measurement target environment in FIG. 10 are read. In this case, in the above-described step S510 and step S530, the measurement target configuration unique code extraction unit 2 determines that these lines are not blank lines and the corresponding lines of the effective code of the comparison environment code in FIG. 9 are not blank lines. As shown in FIG. 13, the first to third lines, the fifth to sixth lines, the 18th to 21st lines, and the 23rd to 24th lines are empty as unique codes in step S550. Output in line.

  When the 14th to 16th lines of the effective code of the measurement target environment in FIG. 10 are read in step S500, these lines are empty in the measurement target configuration specific code extraction unit 2 in steps S510 and S530. It is determined that the corresponding line of the effective code of the comparison environment code in FIG. 9 is not a line, and the line read in step S500 as the unique code is output as it is in step S500.

  Through the above processing, the measurement target environment specific code of FIG. 13 is extracted from the effective code of the measurement target environment of FIG. 10 using the effective code of the comparison target environment of FIG. Similarly, for the effective code of the measurement target environment of FIG. 12, the measurement target environment specific code of FIG. 14 is extracted using the effective code of the comparison target environment of FIG.

  In step S260, the comparison unit 3 compares the unique code shown in FIG. 13 with the unique code shown in FIG. 14, and the difference is changed from the 13th line “case IMAGE_SVG:” of the unique code in FIG. 15 lines “break;” are extracted, and the difference shown in FIG. 15 is output.

  The measurement target environment specific code of FIG. 13 is the version 1.0 software configuration 4 of the comparison target X100 environment of the effective code of the software configuration 5 of the version 200 of the X200 environment that is the measurement target environment (FIG. 10). This is an effective code unique to the effective code (FIG. 9), and is an effective code unique in the X200 environment. Further, the measurement target environment specific code in FIG. 14 is the software of version 2.0 of the X100 environment that is the comparison target of the effective code (FIG. 12) of the software configuration 7 of version 2.0 of the X200 environment that is the measurement target environment. This is an effective code unique to configuration 6 (FIG. 11), and is an effective code unique in the X200 environment. Therefore, the difference shown in FIG. 15 as these differences is a difference specific to the X200 environment between version 1.0 and version 2.0.

  By obtaining the difference in this way in the software difference measuring apparatus 100 according to the present embodiment, a newly created program source code is extracted from the software being developed in parallel, and the number of lines is accurately determined. Can be tabulated.

  Furthermore, a program for causing a computer to execute the above-described software difference measurement process can be provided. Such a program can be recorded on a computer-readable recording medium such as a flexible disk attached to the computer, a CD-ROM, a ROM, a RAM, and a memory card, and provided as a program product. Alternatively, the program can be provided by being recorded on a recording medium such as a hard disk built in the computer. A program can also be provided by downloading via a network.

  The program according to the present invention is a program module that is provided as a part of a computer operating system (OS) and calls necessary modules in a predetermined arrangement at a predetermined timing to execute processing. Also good. In that case, the program itself does not include the module, and the process is executed in cooperation with the OS. A program that does not include such a module can also be included in the program according to the present invention.

  The program according to the present invention may be provided by being incorporated in a part of another program. Even in this case, the program itself does not include the module included in the other program, and the process is executed in cooperation with the other program. Such a program incorporated in another program can also be included in the program according to the present invention.

  The provided program product is installed in a program storage unit such as a hard disk and executed. The program product includes the program itself and a recording medium on which the program is recorded.

  The embodiment disclosed this time should be considered as illustrative in all points and not restrictive. The scope of the present invention is defined by the terms of the claims, rather than the description above, and is intended to include any modifications within the scope and meaning equivalent to the terms of the claims.

3 is a block diagram illustrating a specific example of a hardware configuration of a software difference measurement apparatus 100. FIG. It is a block diagram which shows the specific example of a function structure of the software difference measurement apparatus 100 for performing a software difference measurement process. 3 is a block diagram illustrating a specific example of a detailed configuration of an effective code extraction unit 1. FIG. FIG. 10 is a diagram showing a specific example of software configuration 4. It is a figure which shows the specific example of the software structure. It is a figure which shows the specific example of the software structure. FIG. 10 is a diagram illustrating a specific example of software configuration 7; It is a flowchart which shows the specific example of a software difference measurement process. It is a figure which shows the specific example of the effective code extracted from the software structure. It is a figure which shows the specific example of the effective code extracted from the software structure. It is a figure which shows the specific example of the effective code extracted from the software structure. It is a figure which shows the specific example of the effective code extracted from the software structure. It is a figure which shows the specific example of the measuring object intrinsic | native code obtained from the effective code extracted from the software structure 4, and the effective code extracted from the software structure 5. It is a figure which shows the specific example of the measurement object specific code obtained from the effective code extracted from the software configuration 6 and the effective code extracted from the software configuration. The measurement object specific code obtained from the effective code extracted from the software configuration 4 and the effective code extracted from the software configuration 5, the effective code extracted from the software configuration 6, and the effective code extracted from the software configuration 7 It is a figure which shows the specific example of the difference with the measurement object specific code | cord | chord obtained. It is a flowchart which shows the effective code extraction process in step S100-S130. It is a figure which shows the specific example of a macro definition. It is a flowchart which shows the extraction process of the specific code | cord | chord in step S140, S150. It is a figure which shows the specific example of the function which acquires the desktop area | region width on a screen. It is a figure which shows the specific example of a program source code. It is a figure which shows the specific example of a program source code.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 Effective code extraction part, 2 Measurement object structure specific code extraction part, 3 Comparison part, 4-7 Software structure, 8 Code input part, 9 Compile option input part, 10 Option analysis part, 11 Macro storage part, 12 Code analysis part , 13 Counter storage unit, 14 Preprocessing condition determination unit, 15 Code output unit, 16 Program source code, 17 Compile setting information, 100 Software difference measuring device, 101 Arithmetic unit, 102 Storage device, 103 Input device, 104 Output device, 105 bus, 1021 software configuration storage unit, 1022 program storage unit.

Claims (7)

An effective code extraction means for extracting an effective code from the software configuration;
Unique code extraction for extracting an effective code unique to the first software configuration from the first effective code extracted from the first software configuration and the second effective code extracted from the second software configuration Means and
In the unique code extracting means, the unique code is unique to the first software configuration from the first effective code extracted from the first software configuration and the second effective code extracted from the second software configuration. The first unique code that is the effective code, the third effective code extracted from the third software configuration, and the second unique code from the fourth effective code extracted from the fourth software configuration are extracted. ,
A software difference measurement device further comprising a comparison unit that outputs a difference between the first unique code and the second unique code.   The unique code extraction means generates the first unique code by generating a code by deleting a part of the code included in the first effective code that matches a certain part of the second effective code. The software difference measuring device according to claim 1, wherein the software difference measuring device is extracted. The software configuration includes a pair of program source code and compile setting information,
The effective code extraction means includes
Code input means for obtaining the program source code from the software configuration;
Compile setting information input means for acquiring the compile setting information from the software configuration;
Compile setting information analyzing means for analyzing the compile setting information and extracting a macro definition;
Macro storage means for storing the macro;
Code analysis means for analyzing the program source code to determine whether it is an effective code;
The software difference measuring device according to claim 1, further comprising: a preprocessing condition determining unit that determines a preprocessing condition for the preprocessing command extracted by the code analyzing unit.   4. The software difference according to claim 3, wherein the preprocessing condition determination unit determines that the preprocessing condition is satisfied when the macro is included in the preprocessing instruction extracted by the code analysis unit. 5. measuring device. The first software configuration is a configuration of the first software in the measurement target environment;
The second software configuration is a configuration of the second software in the comparison target environment,
The third software configuration is a configuration of third software in the measurement target environment,
The fourth software configuration is a configuration of the fourth software in the comparison target environment,
The software configuration includes program source code,
2. The software according to claim 1, wherein the difference output by the comparison unit is a difference unique to the measurement target environment between the program source code of the first software and the program source code of the third software. Differential measurement device. A program for causing a computer to execute a process for measuring a difference between the program source code of the first software and the program source code of the third software in the measurement target environment unique to the measurement target environment,
A first effective code from the first software configuration that is the configuration of the first software, a third effective code from the third software configuration that is the configuration of the third software, and a second software configuration that is the second software in the comparison target environment An effective code extracting step of extracting the first effective code from the software configuration and the first effective code from the fourth software configuration which is the configuration of the fourth software in the environment to be compared;
A first unique code which is an effective code unique to the first software configuration is extracted from the first effective code and the second effective code, and the third software configuration is extracted from the third effective code and the fourth effective code. A unique code extracting step means for extracting a second unique code that is an effective code unique to
A software difference measurement program for executing a comparison step of outputting a difference between the first unique code and the second unique code.   A computer-readable recording medium on which the software difference measurement program according to claim 6 is recorded.

Images