JP2012194748A - Configuration report generation device, program and recording medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To automatically analyze a configuration item and facilitate software development.SOLUTION: A configuration report generation device 1, which analyzes the structure of software and generates a report about a configuration item, comprises: source code acquisition means for acquiring a source code 72 before erasing a configuration item of the software; configuration item analysis means 50 for analyzing the source code 72 before erasing the configuration item, which is acquired by the source code acquisition means, and for outputting data capable of at least recognizing a relationship among the configuration item, a function and other program elements; and report generation means 60 for generating a report that at least describes the relationship among the configuration item, the function and the other program elements, based on the output of the configuration item analysis means 50.

Description

  The present invention relates to a configuration report creation device that analyzes a structure of software and creates a report related to configuration items, and a computer-readable program and a storage medium for realizing the configuration report creation device.

  In the field of developing a program to be executed by a computer, the source file and header file described in a human readable language such as C language are preprocessed, compiled, linked and directly processed by the computer. Processing to convert into executable machine language is performed.

  Patent Document 1 describes a compile system that performs automatic optimization on a source program and generates an object program.

  By the way, in the source file and the header file, there are configuration items that can be substituted with numerical values, character strings, and other data structures. This configuration item is an important element for debugging and simulation, and it is highly necessary to recognize the relationship between configuration items and the relationship between configuration items and functions in the field of program development.

  Conventionally, in order to obtain information on such configuration items, a person has investigated the source code using an OS (operating system) command.

JP 2010-140344 A

  However, especially in a large-scale program, there are many configuration items, and the relationship between these and functions is complicated. When a person investigates this using an OS command, it often takes a long time and the possibility of misidentification is high.

  The present invention is to solve such problems, and a configuration report creation apparatus capable of automatically analyzing software configuration items and facilitating software development, and to realize this. The main purpose is to provide this program.

In order to achieve the above object, the first aspect of the present invention provides:
A configuration report creation device that analyzes a software structure and creates a report on a configuration item that appears in a source program of the software and can be substituted with a numerical value, a character string, and other data structures,
Source code acquisition means for acquiring source code before erasing configuration items of the software;
Configuration item analysis means for analyzing the source code before erasing the configuration item acquired by the source code acquisition means and outputting at least data capable of recognizing the relationship between the configuration item and a function or other program element When,
Based on the output of the configuration item analysis means, a report creation means for creating a report describing at least the relationship between the configuration items and functions and other program elements;
A configuration report creation device comprising:

  According to the first aspect of the present invention, the configuration item that analyzes the source code before erasing the configuration item and outputs data that can recognize at least the relationship between the configuration item and the function or other program elements. Since an analysis means is provided and a report is created based on the output, configuration items can be automatically analyzed to facilitate software development.

In the first aspect of the present invention,
The configuration item analysis means analyzes the source code before erasing the configuration item acquired by the source code acquisition means, and sets the program element including the configuration item as a plurality of nodes, and the plurality of nodes are connected. It may be a means for outputting the arranged tree-like data structure.

in this case,
The configuration item analysis means, based on the presence of “#ifdef”, “#endif”, “#else” in the source code before erasing the configuration item, branch points in the tree-like data structure, and merge It may be a means for determining a location.

In the first aspect of the present invention,
When the source file and the header file constituting the software are input, the source code acquisition means interprets only the include relation defined in the source file and the header file, and the source before the configuration item is deleted. It may be a means for acquiring a code.

The second aspect of the present invention is:
Analyzing the software structure and causing the computer to function as a configuration report creation device that creates reports on configuration items that appear in the software source program and that can be substituted with numerical data, character strings, and other data structures A computer readable program for
The computer
Source code acquisition means for acquiring source code before erasing configuration items of the software;
Configuration item analysis means for analyzing the source code before erasing the configuration item acquired by the source code acquisition means and outputting at least data capable of recognizing the relationship between the configuration item and a function or other program element When,
Based on the output of the configuration item analysis means, a report creation means for creating a report describing at least the relationship between the configuration items and functions and other program elements;
It is a computer readable program for making it function as.

  According to the second aspect of the present invention, the configuration item that analyzes the source code before erasing the configuration item and outputs at least data that can recognize the relationship between the configuration item and the function or other program elements. Since the computer is functioned as an apparatus for generating a report based on the output of the analysis means, it is possible to automatically analyze the configuration items and facilitate software development.

In a second aspect of the invention,
The configuration item analysis means analyzes the source code before erasing the configuration item acquired by the source code acquisition means, and sets the program element including the configuration item as a plurality of nodes, and the plurality of nodes are connected. It may be a means for outputting the arranged tree-like data structure.

in this case,
The configuration item analysis means, based on the presence of “#ifdef”, “#endif”, “#else” in the source code before erasing the configuration item, branch points in the tree-like data structure, and merge It may be a means for determining a location.

In the second aspect of the present invention,
When the source file and the header file constituting the software are input, the source code acquisition means interprets only the include relation defined in the source file and the header file, and the source before the configuration item is deleted. It may be a means for acquiring a code.

The third aspect of the present invention is:
A computer-readable storage medium storing a program according to the second aspect of the present invention.

  According to the present invention, it is possible to provide a configuration report creation apparatus capable of automatically analyzing configuration items and facilitating software development, and a program for realizing the configuration report creation apparatus.

1 is a system configuration example of a configuration report creation apparatus 1 according to an embodiment of the present invention. It is a flowchart which shows the flow of the analysis process by the configuration item analysis part 50, and the process before and behind that. 4 is a flowchart showing a flow of analysis processing by a configuration item analysis unit 50. It is the output image of the preprocessor part 40 which concerns on a present Example. It is an image figure which shows a mode that the configuration item analysis part 50 adds a node etc. typically. It is an image figure which shows a mode that the configuration item analysis part 50 adds a node etc. typically. It is an image figure which shows a mode that the configuration item analysis part 50 adds a node etc. typically. It is an image figure which shows a mode that the configuration item analysis part 50 adds a node etc. typically. FIG. 5 is an image diagram schematically showing a tree-like data structure obtained as a result of the configuration item analysis unit 50 performing analysis processing on the output image of the preprocessor unit 40 shown in FIG. 4.

  DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments for carrying out the present invention will be described with reference to the accompanying drawings.

  Hereinafter, a configuration report creating apparatus 1 according to an embodiment of the present invention will be described with reference to the drawings.

[Constitution]
FIG. 1 is a system configuration example of a configuration report creation apparatus 1 according to an embodiment of the present invention. The configuration report creation device 1 is configured around a CPU (not shown) and includes various storage devices including a RAM 10 and a program memory 20, an input port 30, a timer, and other components.

  The RAM 10 functions as a working memory. The program memory 20 is, for example, a ROM (Read Only Memory) or an EEPROM (Electrically Erasable and Programmable Read Only Memory), and stores a program 22 executed by the CPU.

  The configuration report creating apparatus 1 according to the present embodiment includes a preprocessor unit 40 and configuration items as functional blocks realized by fetching, decoding, and executing each instruction included in the program 22 from the program memory 20. An analysis unit 50 and a report creation unit 60 are provided.

  A source file 72 and a header file 74 of software 70 that is a report creation target are input to the input port 30 from an external storage device or the like. The input source file 72 and header file 74 are output to the preprocessor unit 40.

  The source file 72 is a file describing various commands and functions in, for example, the C language or the C ++ language. The header file 74 describes function prototypes, global variable declarations, symbolic constants, and the like. The source file 72 includes necessary contents among the contents described in the header file 74 by the “#include” instruction (the contents are expanded on the spot).

  When the source file 72 and the header file 74 are input, the preprocessor 40 interprets only the include relationship defined in the source file 72 and the header file 74, and obtains the source code before erasing the configuration item of the software 70. Acquire and output to the configuration item analysis unit 50 (Note that “output” is a convenient expression, and the source code before erasing the configuration item is stored in the RAM 10, and this is stored in the configuration item analysis unit 50. May be used).

  Here, in a general preprocess, not only the contents of the header file 74 are expanded by inclusion, but also processing such as erasing conditional expressions based on the presence or absence of definition of configuration items is performed. The preprocessor 40 in the example executes a part of the preprocess (or outputs the dependency obtained as a result of the preprocess).

  The configuration item analysis unit 50 analyzes the relationship between configuration items, the relationship between configuration items and functions, the relationship between configuration items and files, etc. in the source code input from the preprocessor 40 before erasing the configuration items. Then, the analysis result is stored in the configuration database 12 constructed on the RAM 10. Details will be described later.

  The report creation unit 60 creates and outputs a configuration report in a desired format based on the data stored in the configuration database 12. The configuration report may be displayed on a display device or may be output on a medium such as paper or a storage device.

[Analysis processing]
Hereinafter, the analysis process by the configuration item analysis unit 50 and the processes before and after that will be described. 2 and 3 are flowcharts showing the flow of analysis processing by the configuration item analysis unit 50 and the processing before and after that.

  First, the configuration item analysis unit 50 performs initialization processing such as deleting the contents stored in the necessary area of the RAM 10 and creating a start node (S100).

  Next, an instruction for one line is read from the RAM 10 (S102), and analysis processing is performed (S200 to S218).

  When the analysis process of the instruction is performed, it is determined whether or not the analyzed instruction is the instruction on the last line (S104). If the instruction is on the last line, the termination process is performed (S106). If not, the target instruction is advanced by one line (S108), and the processing from S102 onward is executed again.

  Hereinafter, the analysis process will be described.

  First, the configuration item analysis unit 50 determines whether “#else” exists in the read instruction (S200). If “#else” exists, the position of the node to be added next is moved below the configuration start node set immediately before the configuration end node is not linked (S202). Note that the movement of the node addition position is applied only once for the node to be added in the next routine, and for subsequent node additions and node additions until “#else” first appears, It shall be added directly under the node added in the previous routine.

  In this embodiment, “node” refers to a branch point or other reference point in the tree-like data structure generated by the configuration item analysis unit 50. As will be described later, the configuration item analysis unit 50 generates a plurality of pieces of node information in which labels, attributes (subroutines, functions, etc.), upper nodes, lower nodes, etc. are specified, so that the nodes are connected in a tree shape. Create a data structure.

  When “#else” does not exist in the read instruction, the configuration item analysis unit 50 determines whether or not a function definition exists in the read instruction (S204). If a function definition exists, a function node (a node to which a function is assigned as an attribute; hereinafter, the same is interpreted) is added (S206).

  When the function definition does not exist in the read instruction, the configuration item analysis unit 50 determines whether or not a subroutine exists in the read instruction (S208). If a subroutine exists, a subroutine node is added (S210).

  When there is no subroutine in the read instruction, the configuration item analysis unit 50 determines whether “#ifdef” exists in the read instruction (S212). If “#ifdef” exists, a configuration start node is added (S214).

  When “#ifdef” does not exist in the read instruction, the configuration item analysis unit 50 determines whether “#endif” exists in the read instruction (S216). If “#endif” exists, a configuration end node is added below the node added most recently, and links with all related nodes are set (S218).

  If “#endif” does not exist, the configuration item analysis unit 50 ends the flow of FIG. 3 without performing any processing.

[Specific processing example]
Here, a specific processing example when the analysis processing is performed using the flows shown in FIGS.

  FIG. 4 is an output image of the preprocessor unit 40 according to the present embodiment. Hereinafter, results when the flows of FIGS. 2 and 3 are applied to the source code before the configuration item deletion shown in FIG. 4 will be sequentially described. 5 to 8 are image diagrams schematically showing how the configuration item analysis unit 50 adds nodes and the like.

  FIG. 5A is an image diagram schematically illustrating a state in which the configuration item analysis unit 50 has created a start node.

  FIG. 5B is an image diagram schematically showing how a node is created after the configuration item analysis unit 50 reads the line number 100. As shown in the figure, since the function Func1 is defined at the line number 100, the function node Func1 is added under the start node.

  Information such as [file name as a label (Func1), line number (100), attribute (function), upper node (start node), lower node (unknown at this time)] is given to the node.

  FIG. 5C is an image diagram schematically showing how a node is created after the configuration item analysis unit 50 reads the line number 102. As shown in the figure, since subroutine fsub1 is called at line number 102, subroutine node fsub1 is added below function node Func1.

  Information such as [file name as label (fsub1), line number (102), attribute (subroutine), upper node (function node Func1), lower node (unknown at this time)] is assigned to the node. Further, with the addition of the subroutine node fsub1, the subroutine node fsub1 is added to the “lower node” of the function node Func1.

  FIG. 5D is an image diagram schematically illustrating how the configuration item analysis unit 50 creates a node after reading the line number 103. As shown in the figure, since “#ifdef” exists in the line number 103, a configuration start node TypeA is added under the subroutine node fsub1.

  Information such as [file name as a label (TypeA), line number (103), attribute (configuration start), upper node (subroutine node fsub1), lower node (unknown at this time)] is given to the node. The Further, with the addition of the configuration start node TypeA, the configuration start node TypeA is added to the “subordinate node” of the subroutine node fsub1.

  FIG. 6A is an image diagram schematically showing how a node is created after the configuration item analysis unit 50 reads the line number 104. As shown in the figure, since the subroutine fsub2 is defined in the line number 104, the subroutine node fsub2 is added under the configuration start node TypeA.

  Information such as [file name as label (fsub2), line number (104), attribute (subroutine), upper node (configuration start node TypeA), lower node (unknown at this time)] is given to the node. The Further, with the addition of the subroutine node fsub2, the subroutine node fsub2 is added to the “lower node” of the configuration start node TypeA.

  FIG. 6B is an image diagram schematically showing how the configuration item analysis unit 50 creates a node after reading the line number 105. As shown in the figure, since “#ifdef” exists in the line number 105, a configuration start node TypeB is added under the subroutine node fsub2.

  Information such as [file name as a label (TypeB), line number (105), attribute (configuration start), upper node (subroutine node fsub2), lower node (unknown at this time)] is assigned to the node. The Further, with the addition of the configuration start node TypeB, the configuration start node TypeB is added to the “subordinate node” of the subroutine node fsub2.

  FIG. 6C is an image diagram schematically showing a state in which a node is created after the configuration item analysis unit 50 reads the line number 106. As shown in the drawing, since the subroutine gsub1 is called at the line number 106, the subroutine node gsub1 is added under the configuration start node TypeB.

  Information such as [file name as label (gsub1), line number (106), attribute (subroutine), upper node (configuration start node TypeB), lower node (unknown at this time)] is given to the node. The Further, with the addition of the subroutine node gsub1, the subroutine node gsub1 is added to the “lower node” of the configuration start node TypeB.

  FIG. 6D is an image diagram schematically showing how the configuration item analysis unit 50 moves to the next node addition position after reading the line number 108. As illustrated, since “#else” exists in the line number 108, the next node addition position is moved under the configuration start node TypeB.

  FIG. 7A is an image diagram schematically showing how a node is created after the configuration item analysis unit 50 reads the line number 109. As illustrated, since the subroutine gsub2 is called at the line number 109, the subroutine node gsub2 is added under the configuration start node TypeB.

  Information such as [file name as label (gsub2), line number (109), attribute (subroutine), upper node (configuration start node TypeB), lower node (unknown at this time)] is given to the node. The Further, with the addition of the subroutine node gsub2, the subroutine node gsub2 is added to the “lower node” of the configuration start node TypeB.

  FIG. 7B is an image diagram schematically showing a state in which a node is created after the configuration item analysis unit 50 reads the line number 110. As shown in the figure, since “#endif” exists in the line number 110, the configuration end node TypeB * is added. Note that a link is set in the configuration termination node TypeB * so that all of the termination points of the nodes connected with the configuration start node TypeB as the starting point are the upper nodes.

  The node includes [file name as a label (TypeB *), line number (110), attribute (end of configuration), upper node (subroutine node gsub1, subroutine node gsub2), lower node (currently unknown)], etc. Is given. In addition, with the addition of the configuration termination node TypeB *, the configuration termination node TypeB * is added to the “lower nodes” of the subroutine node gsub1 and the subroutine node gsub2.

  FIG. 7C is an image diagram schematically showing how the configuration item analysis unit 50 moves to the next node addition position after reading the line number 112. As shown in the figure, since “#else” exists in the line number 112, the next node addition position is moved under the configuration start node TypeA.

  FIG. 8A is an image diagram schematically showing how a node is created after the configuration item analysis unit 50 reads the line number 113. As shown in the drawing, since the subroutine fsub3 is called at the line number 113, the subroutine node fsub3 is added under the configuration end node TypeB *.

  Information such as [file name as label (fsub3), line number (113), attribute (subroutine), upper node (configuration end node TypeB *), lower node (unknown at this time)] is assigned to the node. Is done. Further, with the addition of the subroutine node fsub3, the subroutine node fsub3 is added to the “lower node” of the configuration end node TypeB *.

  FIG. 8B is an image diagram schematically showing how a node is created after the configuration item analysis unit 50 reads the line number 114. As shown in the figure, since “#endif” exists in the line number 114, the configuration end node TypeA * is added. Note that a link is set in the configuration end node TypeA * so that all of the end points of the nodes connected with the configuration start node TypeA as the start point are the upper nodes.

  Information such as [file name as label (TypeA *), line number (114), attribute (configuration end), upper node (subroutine node fsub3), lower node (unknown at the moment)] is given to the node. Is done. Further, with the addition of the configuration termination node TypeA *, the configuration termination node TypeA * is added to the “lower node” of the subroutine node fsub3.

  By executing the above processing up to the last line, generated data as shown in FIG. 9 is obtained. FIG. 9 is an image diagram schematically showing a tree-like data structure obtained as a result of the configuration item analysis unit 50 performing analysis processing on the output image of the preprocessor unit 40 shown in FIG. Actually, the graphic data as shown in FIG. 9 is not generated, but as described above, aggregate data of nodes to which various kinds of information are assigned is generated, and the report creation unit 60 refers to the aggregate data to generate the graphic data. 9 can recognize a tree-like data structure. Note that graphic data as shown in FIG. 9 may be output as a report.

  The tree-like data structure output from the configuration item analysis unit 50 is stored in the configuration database 12.

[Create Report]
The report creation unit 60 creates a report related to configuration items based on the tree-like data structure output by the configuration item analysis unit 50. The contents of the report include, for example, (1) a list of configuration items (obtained by searching for a configuration start node), and (2) a reference position in the source code for each configuration item (link from start node) (3) Relationship between configuration items (whether there are links, distance (number of links), number of configuration items between them, etc.), (4) Relationship between configuration items and functions And so on.

  More specifically, when a configuration item appears in a conditional expression, it is preferable to be able to list functions and subroutines that are referenced when the condition is satisfied, functions and subroutines that are referenced when the condition is not satisfied, and the like.

  For example, in the case of the data structure of FIG. 9, for the configuration item TypeA, (A) Appears at the third link from the start node, (B) Other configuration item TypeB appears in the period from the start to the end of the item, (C) It is possible to provide information such as fsub2, gsub1, and gsub2 being referred to when the condition is satisfied, and fsub3 being referred to when the condition is not satisfied. Since such information is very useful in software development, the software development can be facilitated by automatically acquiring such information.

  According to the configuration report creating apparatus 1 of the present embodiment described above and a program for realizing the configuration report, configuration items can be automatically analyzed to facilitate software development.

  The best mode for carrying out the present invention has been described above with reference to the embodiments. However, the present invention is not limited to these embodiments, and various modifications can be made without departing from the scope of the present invention. And substitutions can be added.

  For example, the source file 72 and the header file 74 are input, and the source code before the configuration item to be analyzed is acquired by interpreting only the include relation to this, but before the configuration item is deleted. Source code may be directly input to the configuration report creating apparatus 1. In this case, the preprocessor unit 40 is not an essential configuration.

1 Configuration report creation device 10 RAM
12 Configuration Database 20 Program Memory 22 Program 30 Input Port 40 Preprocessor Unit 50 Configuration Item Analysis Unit 60 Report Creation Unit 70 Software 72 Source File 74 Header File

Claims (9)

A configuration report creation device that analyzes a software structure and creates a report on a configuration item that appears in a source program of the software and can be substituted with a numerical value, a character string, and other data structures,
Source code acquisition means for acquiring source code before erasing configuration items of the software;
Configuration item analysis means for analyzing the source code before erasing the configuration item acquired by the source code acquisition means and outputting at least data capable of recognizing the relationship between the configuration item and a function or other program element When,
Based on the output of the configuration item analysis means, a report creation means for creating a report describing at least the relationship between the configuration items and functions and other program elements;
A configuration report creation device comprising: A configuration report creation device according to claim 1,
The configuration item analysis means analyzes the source code before erasing the configuration item acquired by the source code acquisition means, and sets the program element including the configuration item as a plurality of nodes, and the plurality of nodes are connected. Means for outputting a structured tree-like data structure,
Configuration report creation device. A configuration report creation device according to claim 2,
The configuration item analysis means, based on the presence of “#ifdef”, “#endif”, “#else” in the source code before erasing the configuration item, branch points in the tree-like data structure, and merge A means of determining the location,
Configuration report creation device. A configuration report creation device according to any one of claims 1 to 3,
When the source file and the header file constituting the software are input, the source code acquisition means interprets only the include relation defined in the source file and the header file, and the source before the configuration item is deleted. A means of obtaining the code,
Configuration report creation device. Analyzing the software structure and causing the computer to function as a configuration report creation device that creates reports on configuration items that appear in the software source program and that can be substituted with numerical data, character strings, and other data structures A computer readable program for
The computer
Source code acquisition means for acquiring source code before erasing configuration items of the software;
Configuration item analysis means for analyzing the source code before erasing the configuration item acquired by the source code acquisition means and outputting at least data capable of recognizing the relationship between the configuration item and a function or other program element When,
Based on the output of the configuration item analysis means, a report creation means for creating a report describing at least the relationship between the configuration items and functions and other program elements;
A computer readable program to function as a computer. The program according to claim 5,
The configuration item analysis means analyzes the source code before erasing the configuration item acquired by the source code acquisition means, and sets the program element including the configuration item as a plurality of nodes, and the plurality of nodes are connected. Means for outputting a structured tree-like data structure,
program. The program according to claim 6,
The configuration item analysis means, based on the presence of “#ifdef”, “#endif”, “#else” in the source code before erasing the configuration item, branch points in the tree-like data structure, and merge A means of determining the location,
program. A program according to any one of claims 5 to 7,
When the source file and the header file constituting the software are input, the source code acquisition means interprets only the include relation defined in the source file and the header file, and the source before the configuration item is deleted. A means of obtaining the code,
program.   A computer-readable storage medium storing the program according to any one of claims 5 to 8.

Images