JP2015102878A - Program relation analysis method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To save the time for understanding the outline of a numerous number of programs constituting a program relation chart of a large-scale system when the program relation chart is created on the basis of a technique for creating and displaying a program relation chart for analyzing and grasping the programs of an enterprise information system.SOLUTION: A program relation analysis method is for analyzing program files and creating and displaying the relations of the programs. The program relation analysis method analyzes the syntax of the program files to acquire the inter-program call information and data item information, creating a program relation chart, performing grouping in terms of the relations of data item references and updates, extracting programs relating to business data items, sorting the programs on the basis of the relations with the business data items, creating a program relation chart on the basis of the results of program sorting, and displaying the program relation chart.

Description

  The present invention relates to analysis of a program of a computing system. In particular, the present invention relates to an analysis in a business system for performing a predetermined business and a technique for outputting the analysis result.

  In computing systems, it is necessary to analyze the programs used there. This is useful for grasping the contents of an existing system or a system under development, for example, when replacing the system or developing a new system, and for feedback on new development or problems of the existing system. As a background art of this technical field, there is JP 2008-293486 A (Patent Document 1). In this publication, “a plurality of programs are grouped in units of modules based on the structure of function calls, files, classes, libraries, etc., and the related diagram is displayed. Can be effectively displayed according to the purpose of the analysis "(see summary).

JP 2008-293486 A

  In recent years, with the increase in replacement projects, attention has been paid to existing application analysis and grasping techniques. One of the techniques is the generation and display of program related diagrams in which program call relationships are displayed in a graph structure. However, in a large-scale system, since there are a large number of programs constituting the program related diagram, it takes time to understand the outline of the program related diagram. In Patent Document 1, a program related diagram is effectively displayed by performing grouping focusing on a program structure such as a folder structure and a function calling method.

  However, since the above-mentioned Patent Document 1 is a grouping that focuses on the program structure such as the folder structure and how to call a function, it is difficult to effectively display a program related diagram from a business viewpoint. For example, if multiple business processes are implemented in one program related diagram, the part that is executed in common for the business and the part that is executed individually for the business are classified and displayed. For example, a part that implements system processing such as log output or error check is omitted.

  On the other hand, enterprise information systems for enterprises mainly refer to and update a database storing business-related data, and there are many cases in which the relationship between business and data items can be grasped.

  In order to solve the above-described problems, the present invention improves readability by grouping programs constituting a program-related diagram based on business data items related to business. As a more specific aspect thereof, for example, the configuration described in the claims is adopted. In other words, the present application includes a plurality of means for solving the above-mentioned problems. To give an example, a program-related analysis method for analyzing a program file and creating and displaying a program relationship, Analyzing the syntax, obtaining the call information between programs and data item information, providing means for creating a program-related diagram, means for grouping from the relationship between reference and update of data items, and business data items And a means for classifying the program based on the relationship with the business data item, and a means for creating and displaying a program related diagram based on the classification result of the program.

  According to the present invention, readability can be improved by grouping a large number of programs constituting a program-related diagram based on business data items. Thereby, for example, it is possible to shorten the work time for grasping the program relation from the business viewpoint.

  Problems, configurations, and effects other than those described above will be clarified by the following description of embodiments.

It is an example of the block diagram of the program analyzer in one Embodiment of this invention. It is an example of the flowchart explaining the process of the program analyzer in one Embodiment of this invention. It is an example of the program file for demonstrating the process of the syntax analysis of the program analyzer in one Embodiment of this invention. It is an example of the flowchart explaining the process of the grouping of the data item in one Embodiment of this invention. It is an example of the program file for demonstrating the process of the grouping of the data item in one Embodiment of this invention. It is an example of the table explaining the grouping result by argument at the time of operation start in one embodiment of the present invention. It is an example of the program file for demonstrating the process of the grouping of the data item in one Embodiment of this invention. It is an example of the table explaining the grouping result 115 by CALL argument in one Embodiment of this invention. It is an example of the table explaining the correspondence list 116 between programs in one Embodiment of this invention. It is an example of the flowchart explaining the process of extraction of the program relevant to the business data item in one Embodiment of this invention. It is an example of the table explaining the business data item list 112 in one Embodiment of this invention. It is an example of the table explaining the business data item / program relation 117 in one embodiment of the present invention. It is an example of the flowchart which extracts the call origin program relevant to the business data item in one Embodiment of this invention. It is an example of the flowchart which extracts the call destination program relevant to the business data item in one Embodiment of this invention. It is an example of the table explaining the program classification result 118 in one Embodiment of this invention. It is an example of the image figure of the screen which displays a result for the operator in one Embodiment of this invention. It is an example of the image figure of the screen which displays a result for the operator in one Embodiment of this invention.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
In the present embodiment, an example of a so-called business system program related analysis apparatus will be described.
FIG. 1 is an example of a configuration diagram of the program-related analysis apparatus of this embodiment.
The program analysis device 1 is a computer including a CPU 10, a main memory 11, a storage device 12, an input device 13, an output device 14, and a communication interface 15, which are connected by an internal bus or the like. The CPU 10 performs various processes by reading the unit stored in the storage device 12 into the main memory 11 and executing it. The storage device 12 includes a program syntax analysis unit 101 that analyzes the syntax of a program file, a data item grouping unit 102 that performs grouping from the relationship between reference and update of data items, and business data that extracts programs related to business data items Item-related program extraction unit 103, program classification unit 104 that classifies programs based on relevance to business data items, program-related display unit 105 that creates and displays program-related diagrams based on program classification results, and programs to be analyzed File 111, business data item list 112 that stores business data items related to the business, program syntax analysis result 113 that stores the result of analyzing the syntax of each program file, and data items that are acquired as arguments during program operation (Hereafter, operation starts Grouping by focusing on the grouping result by argument 114 at the start of operation for storing information on data items grouped by focusing on the argument), and on the data item used as an argument at the time of calling the program (hereinafter referred to as CALL statement argument) CALL argument grouping result 115 for storing the information of the converted data item, the inter-program argument correspondence list 116 for storing the result of associating the CALL statement argument and the operation start argument, and the information of the program related to the business data item The business data item / program relation 117 and the program classification result 118 for storing the result of classifying the program based on the relation with the business data item are stored.

  FIG. 2 is an example of a flowchart for explaining processing of the program-related analysis apparatus of the present embodiment. Hereinafter, the operation of each unit in FIG. 1 will be described based on the flowchart in FIG. 2.

  In S11 program syntax analysis, the program syntax analysis unit 101 analyzes the syntax of the program file 111. The program name, data item information, operation start argument information, and program call information are extracted by syntax analysis and stored in the program syntax analysis result 113. Data item information is the data item name, type, size used in the program, the data item usage location indicating the location where each data item is used, and whether the data item is referenced or updated at the usage location. The usage method of the indicated data item is stored. The operation start argument information stores information such as the size and type of the operation start argument of each program. For example, the argument at the start of COBOL operation is a data item declared by LINKAGE SECTION. The program call information includes the name of the other program called from the program being parsed, the location where the CALL statement is used to indicate the location where the other program is called, and the CALL statement argument name indicating which data item is the argument to the calling program. Is stored. In the case of COBOL as an example of a program call argument, an argument assigned in the USING phrase of the CALL statement is given.

Next, the information to be extracted described here will be shown by taking FIG. 3 as an example. The program of FIG. 3 is a program that uses data item A1 as an argument at the start of operation, adds 1 to A1 at line number 00101, sets a value in data item A2, and calls PGM002 at line number 00102. The program syntax analysis unit 101 extracts PGM001 as the program name. As data item information, it is extracted that A1 is referred to by line number 00101, and A2 is updated by line number 00101 and is referenced by line number 00102. A1 is extracted as argument information at the start of operation. It is extracted that PGM002 is called with the line number 00102 as the program call information and A2 is used as the argument.
Means for acquiring such information can be realized by using Patent Document 1 or existing compiler technology.

  In S12 data item grouping, the data item grouping unit 102 performs grouping based on the relationship between the reference and update of the data item, starting from the data item specified as the argument at the start of operation and the argument in the CALL statement. FIG. 4 is an example of a detailed flowchart of S12. In S121, the argument name at the start of the operation is used as a starting point, grouping is performed by tracking the data item referring to it, and the result is stored in the grouping result 114 by argument at the start of operation. FIG. 5 will be described as an example. FIG. 5 shows a program PGM001 that updates the value of A1 with reference to the operation start argument Arg1 at line number 00201 and updates the value of A2 with reference to A1 at line number 00202. In addition, the value of A3 is updated with reference to the operation start argument Arg1 at line number 00301. The data item grouping unit 102 searches the data item information and extracts A1 and A3 which are data items whose values are updated with reference to Arg1 which is an argument at the start of operation. Next, the data item A2 whose value is updated is extracted with reference to the extracted data item A1 or A3. When this operation is repeated and there are no more data items to be extracted, the extracted data items are combined into one group. In this example, Arg1, A1, A2, and A3 form one group. The data item grouping unit 102 stores the result in the argument grouping result 114 at the start of operation. FIG. 6 shows an example of the argument grouping result 114 at the start of operation. The program name 1141 stores PGM001, the operation start argument 1142 stores Arg1, the argument-specific data item group 1143 stores Arg1, A1, A2, A3, and the argument-specific group ID stores an identifier number GH001 that makes each record unique.

  In S122, the CALL statement argument is used as a key, the data item being updated is tracked, grouped, and the result is stored in the CALL statement argument grouping result 115. FIG. 7 will be described as an example. 7 updates the value of B1 by referring to the operation start argument ARG2 at the line number 00401, updates the value of B2 by referring to the data item B1 at the line number 00402, and updates the program PGM003 at the line number 00403 to B2. Is a program PGM002 that is called as an argument. The data item grouping unit 102 searches the data item information, and extracts B1, which is a data item referred to when updating the value of the data item B2 as an argument of the program call. Next, the data item Arg2 referred to when the value of the extracted data item B1 is updated is extracted. When this operation is repeated and there are no more data items to be extracted, the extracted data items are combined into one group. In this example, B2, B1, and Arg2 form one group. The data item grouping unit 102 stores the result in the CALL sentence argument grouping result 115. FIG. 8 is an example of the CALL sentence argument grouping result 115. PGM002 for the call source program name 1151, 00403 for the CALL statement line number 1152, PGM003 for the call destination program name 1153, B2 for the CALL statement argument 1154, B2, B1, Arg2 for the CALL data item group 1155, and the group ID for each CALL Stores the identifier number that identifies the record.

  In the examples of S121 and S122, it is described that there is only one group in each program, but actually there are a plurality of groups in one program.

  In S123, the CALL statement argument name is associated with the operation time argument of the program to be called based on the CALL statement use location stored in the program call information by the data item grouping unit 102, and the result is displayed as an inter-program argument correspondence list 116. To store. FIG. 9 shows an example of the inter-program argument correspondence list 116. In FIG. 7, when the operation start argument of PGM003 is C1, PGM002 is the call source program name 1161 of the inter-program argument correspondence list 116, 00403 is the CALL statement line number 1162, B2 is the call statement argument 1163, and the call destination program name 1164 PGM003, and C1 is stored in the operation start argument 1165.

  In S13 business data item related program extraction, the business data item related program extraction unit 103 extracts a data item belonging to the same group as the business data item, thereby extracting a related program. FIG. 10 is an example of a detailed flowchart of S13. In S131, the name of the business data item related to each business is acquired by referring to the business data item list 112, the group to which each acquired business data item belongs is extracted, and the result is stored in the business data item / Stored in the program relation 117. FIG. 11 shows an example of the business data item list 112. The business name is stored in the business name 1121, and the data item related to the business is stored in the business data item 1122. FIG. 12 shows an example of the business data item / program relation 117. A business data item name 1171, a related program 1172 that is a program related to the business data item name, and a group ID 1173 that is an ID of a group to which the related data item belongs.

Further, as an example of the extraction method, there is a character string search of data item information stored in the program syntax analysis result 113.
In S132, it is determined whether the program calling the program extracted in S131 is related in terms of business data items. FIG. 13 is an example of a detailed flowchart of S132.

  In S1321, the grouping result 114 by argument at the start of operation is searched, and the group including the business data item is extracted from the program extracted in S131. In S1322, it is confirmed whether or not there is an operation start argument in the extracted group. If it exists, the process proceeds to S1323. In S1323, the inter-program argument correspondence list 116 is searched with the operation start argument extracted in S1322, and the calling source program and the CALL statement argument are acquired. In S1324, the caller program and the group name to which the CALL statement argument belongs are registered in the business data item / program relation 117. In step S1325, it is confirmed whether or not an operation start argument exists in the registered group. If it exists, the process returns to S1323. In S1326, if there is an uninvestigated group, the process returns to S1322, and the same processing is performed for the uninvestigated group.

  In S133, it is determined whether the program called from the program extracted in S131 is related in terms of business data items. FIG. 14 is an example of a detailed flowchart of S133. In S1331, the CALL grouping result 115 is searched, and the group including the business data item is extracted from the program extracted in S131. In S1332, it is confirmed whether the CALL sentence argument exists in the extracted group. If it exists, the process proceeds to S1333. In S1333, the inter-program argument correspondence list 116 is searched with the CALL statement argument extracted in S1332, and the call destination program and the operation start argument are acquired. In S 1334, the call destination program and the group name to which the operation start argument belongs are registered in the business data item / program relation 117. In S1335, it is confirmed whether the CALL statement argument exists in the registered group. If it exists, the process returns to S1333. In S1336, if there is an uninvestigated group, the process returns to S1332, and the same processing is performed for the uninvestigated group.

  In S14 program classification, the program classification unit 104 classifies the processing into processing other than business such as business-specific processing, multi-business usage processing, and error processing based on the relationship between the program and the business. The program classification unit 104 searches the business data item / program relation 117 and extracts business data items related to each program. Next, based on the business data item list 112, the program is classified from the business viewpoint, and the classification result is stored in the program classification result 118. FIG. 15 shows an example of the program classification result 118. A program name 1181, a related business name 1182 and a classification pattern 1183 are stored. As an example of the classification pattern 1183, when all the extracted business data items belong to the same business, the program is regarded as business-specific processing, and the classification pattern is business-specific. Further, when belonging to a plurality of tasks, it is regarded as a process common to a plurality of tasks, and the classification pattern is made common to the tasks. If there is no related business data item, it is regarded as processing other than business, and the classification pattern is set to other than business.

  In S15, the program related display unit classifies the program into individual business, common business, and non-business based on the program classification result 118, and displays a program related diagram. 16 and 17 are display examples. FIG. 16 shows an example in which a user designates a business name and only a program related to the business is highlighted. PGM001, 002, 003, 011 and 012 which are programs related to the business are displayed. Other programs are hidden. FIG. 17 shows an example in which programs commonly used for business and programs used for individual business are highlighted.

101 program structure analysis unit 102 data item grouping unit 103 business data item related program extraction unit 104 program classification unit 105 program related display unit 111 program file 112 business data item list 113 program syntax analysis result 114 grouping result by argument at start of operation CALL Argument grouping result 116 Inter-program argument correspondence list 117 Business data item / program related 118 Program classification result

Claims (5)

A program-related analysis device that analyzes a program file and creates and displays program relevance,
Means for receiving the program file;
Means for analyzing the syntax of the received program file, obtaining call information between programs and data item information, and creating a program related diagram;
Means for grouping the data items into business data items for each business from the relationship between reference and update of the data items;
Means for extracting the business data item and a program related to the business data item;
Means for classifying the programs included in the program file based on the relationship with the business data item;
And a means for creating and displaying a program relation diagram based on the classification result of the program. The program-related analysis device according to claim 1,
The means for realizing the grouping performs grouping of the data items starting from a data item acquired as an argument during a program operation. The program-related analysis device according to claim 1,
The means for realizing the grouping includes means for grouping the data items starting from a data item used as an argument when calling the program. The program-related analysis device according to claim 1,
The program-related analysis device is characterized in that the means for extracting the program extracts a related program by extracting another group related to the group to which the business data item belongs. The program-related analysis device according to claim 1,
The program-related analysis apparatus characterized in that the display means classifies the program based on the relationship between the program and the business, and creates and displays a program-related diagram.

Images