JP6917874B2 - System characterization system and system characterization device - Google Patents

Description

The present invention relates to a system characteristic evaluation system and a system characteristic evaluation device applicable to system design, development, maintenance, and the like.

Renewal of large-scale information systems such as production control systems may be required in response to customer requests. There is a large gap between the specifications and the source code of such information systems, and many of them have been developed for several decades. For this reason, it takes a huge amount of man-hours just to grasp the availability of the managed source code, and it is often difficult to grasp the entire software structure and design guidelines.

Further, since such an information system often has a plurality of functions having different properties, there are many requests for improvement of the functions. In such a situation, it is difficult to capture all the improvement requests for the functions, and it is necessary to deal with the improvement requests with high priority while operating the information system.

Under such circumstances, by analyzing the dependency relationships and dependency types between the components of the source code and specifying the importance for each dependency type, the range of influence when the source code is modified is extracted, and the impact level is determined. There is technology to support evaluation. (Patent Document 1)

Japanese Unexamined Patent Publication No. 2012-230538

However, in the technique disclosed in Patent Document 1, the repair target is selected based on the existing structure obtained from the analysis result of the source code, that is, static information. From the analysis results of such a structure alone, it is difficult to determine the repair priority in consideration of the current business usage status, maintainability, and time-series changes such as repair results.

For example, even if there is a problem in the structure as a result of source code analysis, if the program has no problem in business use, the priority of repair is likely to be low.
Also, regarding the improvement of non-functionality such as processing time and availability, the latter processing is better for batch processing that is executed at night and processing that is started and executed by the user during the day, even if the processing time is the same. The improvement priority is likely to be high.

On the other hand, in a system in which a large number of users use the system at individual timings according to individual purposes, the priority of each function is likely to be independent of the execution time zone. In this way, in order to determine the repair target, it is desirable to recognize the system usage method and development results as characteristics that indicate the characteristics of the system.

The present invention has been made in view of the above circumstances, and an object of the present invention is to provide a system characteristic evaluation system and a system characteristic evaluation device capable of evaluating the priority of improvement points of a system.

In order to achieve the above object, the system characteristic evaluation system according to the first aspect includes a system characteristic evaluation device and a display device. The system characteristic evaluation device includes a software structure analysis unit that analyzes the relationship between program calls and data in the source code and generates a graph structure with the program as a node and the program call relationship as a directional edge. Based on the analysis result of the source code and the system information of the system in which the program is executed, the characteristic analysis unit that calculates the characteristic value of the system for each node and the node are merged based on the characteristic value. It is provided with an improvement part analysis unit that reconstructs the graph structure based on the merged result of the nodes. The display device displays the graph structure reconstructed by the improvement point analysis unit.

According to the present invention, it is possible to evaluate the priority of the improvement points of the system.

FIG. 1 is a block diagram showing a schematic configuration of a system characteristic evaluation system according to an embodiment. FIG. 2 is a block diagram showing a schematic configuration of the system characteristic evaluation device of FIG. FIG. 3 is a block diagram showing a specific configuration of the system characteristic evaluation system of FIG. FIG. 4 is a block diagram showing a hardware configuration of the system characteristic evaluation device of FIG. FIG. 5 is a diagram showing an example of the contents of the node information table of FIG. FIG. 6 is a diagram showing an example of the contents of the edge information table of FIG. FIG. 7 is a diagram showing an example of the characteristic data of FIG. FIG. 8 is a flowchart showing the operation of the software structure analysis unit of FIG. FIG. 9 is a flowchart showing the operation of the characteristic analysis unit of FIG. FIG. 10 is a diagram showing an operation flow of the improvement point analysis unit of FIG. 3 when a characteristic item is specified. FIG. 11 is a flowchart showing the operation of the improved part analysis unit of FIG. FIG. 12 is a diagram showing an example of a display screen having a graph structure constructed based on the node information table of FIG. 5 and the edge information table of FIG. FIG. 13 is a diagram showing an example in which the characteristic value of the selected node is displayed on the display screen of FIG. FIG. 14 is a diagram showing an example of a display screen having a reconstructed graph structure displayed on the display device of FIG. FIG. 15 is a diagram showing an example of the contents of the node information table corresponding to the graph structure after the reconstruction of FIG. FIG. 16 is a diagram showing an example of the contents of the edge information table corresponding to the graph structure after the reconstruction of FIG.

The embodiment will be described with reference to the drawings. It should be noted that the embodiments described below do not limit the invention according to the claims, and all of the elements and combinations thereof described in the embodiments are indispensable for the means for solving the invention. Is not always.

FIG. 1 is a block diagram showing a schematic configuration of a system characteristic evaluation system according to an embodiment.
In FIG. 1, the system characteristic evaluation system is provided with a system characteristic evaluation device 10, a display device 20, a business system 30, a source code management device 40, and a failure management device 50. The system characteristic evaluation device 10, the display device 20, the business system 30, the source code management device 40, and the failure management device 50 are connected via the network 70. The network 70 may be a WAN (Wide Area Network) such as the Internet or a digital leased line, a LAN (Local Area Network) such as Ethernet (registered trademark) or WiFi, or a WAN and a LAN. It may be mixed. The network 70 may be wired, wireless, or a mixture of wired and wireless.

The system characteristic evaluation device 10 can evaluate the characteristics of the business system 30 in which the program in the source code is executed based on the static information and the dynamic information of the source code. Static information about the source code is information that does not change with respect to the execution of the source code. As static information about the source code, a graph structure in which the program in the source code is a node and the call relationship of the program is a directional edge can be mentioned. Dynamic information about the source code is information that can be changed with respect to the execution of the source code. The dynamic information about the source code can include the system information of the business system 30. Examples of the system information of the business system 30 include operation information and failure information of the business system 30.

The display device 20 can display the evaluation result of the characteristics of the business system 30 based on the operation of the user 80. The business system 30 can execute various programs related to the business of the user 90. The source code management device 40 can manage the source code executed by the business system 30. The fault management device 50 can manage faults in the business system 30.

The system characteristic evaluation device 10 can acquire the source code from the source code management device 40. The system characteristic evaluation device 10 can generate static information of the source code based on the structural analysis of the source code. The system characteristic evaluation device 10 can acquire dynamic information about the source code from the business system 30, the source code management device 40, and the failure management device 50.

At this time, the application log of the business system 30 to be evaluated for system characteristics is acquired from the business system 30, the source code of the business system 30 and the change history of the source code are acquired from the source code management device 40, and the business system 30 is involved. The failure history can be acquired from the failure management device 50. Then, the system characteristic evaluation device 10 can generate a graph structure of the source code based on the structural analysis of the source code. Further, the system characteristic evaluation device 10 can manage characteristic values obtained by analyzing various information for each element of the source code. Source code elements are programs contained in the source code. This program may be a shell script. Various types of information are static information and dynamic information related to the source code. The characteristic value can be used for evaluating the characteristics of the business system 30 in which the program is executed. The characteristic value can be evaluated numerically for the characteristic items set from the viewpoint of program implementation and structure, the viewpoint of program modification history, and the viewpoint of program usage.

Then, the system characteristic evaluation device 10 can symbolize the graph structure of the source code and display it on the display device 20. By visually recognizing the display device 20, the user 80 can determine the priority of improving the source code.

Here, the system characteristic evaluation device 10 evaluates the characteristics of the business system 30 while referring not only to the static information related to the source code but also to the dynamic information related to the source code, thereby performing the current business use of the business system 30. It is possible to judge the priority of improvement of the source code that reflects the time-series changes such as the situation, maintainability, and the repair record of the source code.

For example, even if there is a problem in the structure as a result of structural analysis of the source code, if the program has no problem in business use in the business system 30, the priority of improving the source code can be lowered.
Also, regarding the improvement of non-functionality such as program processing time and availability, the latter processing is performed even if the processing time is the same between the batch processing performed at night and the processing started and executed by the user during the day. The priority of improvement of the program used for can be increased.

Further, in the business system 30 used by a large number of users 90 at individual timings according to individual purposes, it is possible to set the priority of improvement of each function so as not to be influenced by the execution time zone of the program.

In the example of FIG. 1, the system characteristic evaluation device 10 is connected to the business system 30 and the source code management device 40 via the network 70, but the system characteristic evaluation device 10 is a function of the business system 30. Or the system characteristic evaluation device 10 may be used as one function of the source code control device 40.

FIG. 2 is a block diagram showing a schematic configuration of the system characteristic evaluation device of FIG.
In FIG. 2, the system characteristic evaluation device 10 is provided with a structural analysis unit 1011 and a characteristic evaluation unit 102. The structure analysis unit 101 is provided with a software structure analysis unit 101 and software structure data 111. The characteristic evaluation unit 102 is provided with a characteristic analysis unit 1021, a characteristic value calculation unit 1022, an improvement location analysis unit 1023, characteristic data 112, and display software structure data 113.

The structural analysis unit 101 generates static information about the source code based on the structural analysis of the source code. The characteristic evaluation unit 102 evaluates the characteristics of the business system 30 in which the program in the source code is executed based on the static information and the dynamic information of the source code.

The software structure analysis unit 1011 analyzes the source code collected from the source code management device 40, identifies the program or data as a node, the call relationship between the programs as an edge, and the call relationship between the program and the data, and software structure data. Store in 111.

The characteristic analysis unit 1021 analyzes the characteristics of the business system 30 for each node stored in the software structure data 111. Specifically, regarding the characteristic items stored in the characteristic data 112, based on the application log collected from the business system 30, the change history collected from the source code management device 40, the failure history collected from the failure management device 50, and the like. The characteristic value is calculated and stored in the software structure data 111.

The characteristic value calculation unit 1022 calculates the characteristic value of each characteristic item for each node stored in the software structure data 111. The characteristic value calculation unit 1022 can be provided for each characteristic item. At this time, the ID that specifies the characteristic value calculation unit 1022 can be associated with the characteristic item and set in the characteristic data 112. The characteristic value calculation unit 1022 can be called and operated by the characteristic analysis unit 1021.

In the example of FIG. 2, the characteristic value calculation unit 1022 is provided separately from the characteristic analysis unit 1021, but the characteristic value calculation unit 1022 may be configured as one function of the characteristic analysis unit 1021. ..

The improvement location analysis unit 1023 determines whether the characteristic values of each program and data stored in the software structure data 111 exceed the threshold value stored in the characteristic data 112 for the characteristic items received by the display device 20. can do. Further, the improvement location analysis unit 1023 reconstructs the software structure data 111 based on the determination result and stores the software structure data 111 in the display software structure data 113.

Hereinafter, the operation of the system characteristic evaluation device 10 will be described with reference to FIGS. 1 and 2.
The software structure analysis unit 1011 acquires the source code of the target business system 30 from the source code management system 40, and analyzes the program (function) and the data, the call relationship between the programs, and the call relationship between the programs and the data. Then, the software structure analysis unit 1011 generates a graph structure in which the program and the data referred to by the program are nodes, the call relationship of the program, and the reference relationship between the program and the data are directional edges, and store the graph structure in the software structure data 111.

Next, the characteristic analysis unit 1021 analyzes the characteristic value of the node stored in the software structure data 111. The characteristic analysis unit 1021 calls the characteristic value calculation unit 1022 associated with each characteristic item, analyzes the data to be analyzed for each program, and stores the analysis result in the software structure data 111.

Further, the system characteristic evaluation device 10 arranges the nodes in the order of execution time series based on the software structure data 111 storing the characteristic values. Then, the type, color, thickness, size or display position can be set for each node and each edge according to the characteristic value, and each node and each edge can be symbolized based on the setting information. Then, the symbolized information is transmitted to the display device 20 via the network 70. The display device 20 sets the type, color, thickness, size, or display position of each node and each edge based on the symbolized information, and displays each node in the order of execution time.

Next, when the system characteristic evaluation device 10 receives the characteristic item specified by the user 80 from the display device 20, the system characteristic evaluation device 10 operates the improvement location analysis unit 1023. The improvement location analysis unit 1023 determines for each node whether or not the threshold value stored in the characteristic data 112 is exceeded for each characteristic value of the node. Then, the improvement location analysis unit 1023 sets the node exceeding the threshold value as an improvement candidate, and sets the node of the software structure data 111 as it is as the node of the display software structure data 113. The node that does not exceed the threshold value is merged with another node that does not exceed the threshold value, and the merged node is used as the node of the display software structure data 113. Further, an edge is set for the merged node, and the edge is set as the edge of the display software structure data 113.

Further, the improvement point analysis unit 1023 recalculates the characteristic value for the merged node. When calculating the characteristic value, the improvement location analysis unit 1023 can call the characteristic analysis unit 1021 and have the characteristic analysis unit 1021 recalculate the characteristic value. The characteristic value of the merged node can be calculated based on the characteristic value of the original node.

Then, the system characteristic evaluation device 10 sets the type, color, thickness, size, or display position for each node and each edge according to the recalculated characteristic value, and based on the setting information, each node and each edge. Edges can be symbolized. Then, the symbolized information is transmitted to the display device 20 via the network 70. The display device 20 sets the type, color, thickness, size, or display position of each node and each edge based on the symbolized information, and displays each node in the order of execution time.

As a result, the user 80 can easily confirm the node to be improved for the specified characteristic item while confirming the structure of the software, the execution order, and the relationship between the programs based on the arrangement of the graph structure. Therefore, the user 80 can easily specify the improvement target in the source code while considering the position in business and the like.

Further, the system characteristic evaluation device 10 displays the nodes with low priority without impairing the structure of the software, the execution order, and the relationship between the programs by merging the nodes whose characteristic values do not exceed the threshold value. The number can be reduced. Therefore, even in a large-scale information system having hundreds or more programs, the user 80 can easily specify the improvement target in the source code while considering the position in business and the like.

Furthermore, even when it is difficult to grasp the overall software structure, design guidelines, etc. due to a large gap between the specifications and the source code due to changes in the source code, the user 80 can position the user 80 in business. Taking this into consideration, it is possible to easily identify the improvement target in the source code.

Further, even when the business system 30 has a plurality of functions having different properties and there are many requests for improvement of functions, it is possible to easily specify the improvement target in the source code while incorporating all the requests for improvement of the functions.

FIG. 3 is a block diagram showing a specific configuration of the system characteristic evaluation system of FIG.
In FIG. 3, the software structure data 111 is provided with a node information table 1111 and an edge information table 1112. The display software structure data 113 is provided with a display node information table 1131 and a display edge information table 1132. The application log 3001 is held in the business system 30. The source code management device 40 holds the source code 4001 and the change history 4002 of the source code 4001. The fault management device 50 holds a fault history 5001 related to the business system 30.

The software structure analysis unit 1011 acquires the source code 4001 of the target business system 30 from the source code management device 40, and analyzes the program (function) and the data, the call relationship between the programs, and the call relationship between the program and the data. Based on the analysis result, the software structure analysis unit 1011 updates the node information table 1111 with the program and data as nodes, and sets the edge information table 1112 with the program call relationship and the program and data call relationship as directional edges. Update.

Next, the characteristic analysis unit 1021 acquires the software structure data 111 updated by the software structure analysis unit 1011. Further, the characteristic analysis unit 1021 acquires the change history 4001 from the source code management device 40, the application log 3001 from the business system 30, and the failure history 5001 from the failure management device 50 via the network 70. Then, the characteristic analysis unit 1021 operates the characteristic value calculation unit 1022 corresponding to the characteristic item stored in the characteristic table 1121, and calculates the characteristic value of the characteristic item for each node. Then, the characteristic analysis unit 1021 stores the characteristic values calculated for each characteristic item in the node information table 1111 for each node.

Next, when the system characteristic evaluation device 10 receives the characteristic item specified by the user 80, the improvement location analysis unit 1023 is operated. The improvement location analysis unit 1023 refers to the node information table 1111 and the characteristic table 1121 and determines whether or not each node of the node information table 1111 exceeds the threshold value set in the characteristic table 1121. Further, the improvement point analysis unit 1023 reconstructs the graph structure for display based on the determination result, stores the reconstructed graph structure program and data as nodes in the display node information table 1131, and stores the reconstructed graph structure program and data in the display node information table 1131. The call relationship of the reconstructed graph structure program and the call relationship between the program and data are stored in the display edge information table 1132 as directional edges.

FIG. 4 is a block diagram showing a hardware configuration of the system characteristic evaluation device of FIG.
In FIG. 4, the system characteristic evaluation device 10 is provided with a main control unit 103, a main storage unit 104, an input unit 105, an output unit 106, and a communication unit 107. The main control unit 103 is provided with a processor 1031 and a RAM 1032.

The main control unit 103 loads the program recorded in the main storage unit 104 into the RAM 1032, and the processor 1031 executes the program to control the information processing in the system characteristic evaluation device 10.
The main storage unit 104 non-volatilely stores information about the system characteristic evaluation device 10. The main storage unit 104 may be a magnetic disk device or an SSD (Solid State Drive).

The software structure analysis program 1011P, the characteristic analysis program 1021P, the characteristic value calculation program 1022P, the improvement location analysis program 1023P, the software structure data 111, the characteristic data 112, and the display software structure data 113 are stored in the main storage unit 104. The characteristic value calculation program 1022P can be provided for each characteristic item.

The software structure analysis unit 101 can be realized by the processor 1031 executing the software structure analysis program 1011P. The characteristic analysis unit 1021 can be realized by the processor 1031 executing the characteristic analysis program 1021P. The characteristic value calculation unit 1022 can be realized by the processor 1031 executing the characteristic value calculation program 1022P. The improvement location analysis unit 1023 can be realized by the processor 1031 executing the improvement location analysis program 1023P.

When it is necessary to manually input information about the system characteristic evaluation device 10, the input unit 105 inputs the information to the system characteristic evaluation device 10.
When the output unit 106 needs to output information about the system characteristic evaluation device 10, the system characteristic evaluation device 10 outputs the information to the user.
The communication unit 107 connects to the display device 20, the business system 30, the source code management device 40, and the fault management device 50 via the network 70, and connects the display device 20, the business system 30, the source code management device 40, and the fault management device. Communicate with 50.

FIG. 5 is a diagram showing an example of the contents of the node information table of FIG.
In FIG. 5, the node information table 1111 includes a node ID 501 assigned to each program or data, a processing name 502 that can identify the program name or data name for each node, and a program or data type 503. , Stores the characteristic 504 of the business system 30 related to program execution.

At least one set characteristic item is stored in the characteristic 504. As the characteristic 504, the real value 5041 of the characteristic 504 and the characteristic value 5042 that has been normalized or the like can be stored, respectively.

In the example of FIG. 5, a storage example of a node of a system in which a shell script calls a program implemented in COBOL or C language and the program calls data is shown. In addition, an example in which the processing time is set as a characteristic item is shown.

FIG. 6 is a diagram showing an example of the contents of the edge information table of FIG.
In FIG. 6, the edge information table 1112 includes an edge ID 511 that can be uniquely specified for each call relationship between programs or a reference relationship between a program and data shown in FIG. 5, an edge caller node ID 512, and an edge call destination. Stores node ID 513. As the caller node ID and the callee node ID, the node ID 501 stored in the node information table 1111 is used.

Since the edge is oriented, it can be divided and held so that the reference source node and the reference destination node can be identified. For example, when a plurality of programs are called from one program, edge IDs having the same caller program ID but different call destination program IDs are created.

In addition, the node information table 1111 can also store the relationship type 514 so that a call between programs or a call between a program and data can be identified. In the example of FIG. 6, the program call order is represented by "next", and the data reference relationship is represented by "in" or "out". Further, in a program group having a hierarchical structure such as when a shell script calls a program, it is expressed by "call" as a relationship in which a program in a higher hierarchy calls a program in a lower hierarchy. The type 514 of this relationship can be appropriately changed according to the software structure.

FIG. 7 is a diagram showing an example of the characteristic data of FIG.
In FIG. 7, the characteristic table 1121 stores the characteristic ID 601 and the characteristic name 602, the threshold value 603, and the characteristic value calculation unit ID 604 for each characteristic item managed by the node information table 1111. The characteristic ID 601 is an ID that can uniquely identify the characteristic item. The characteristic name 602 can indicate the name of the characteristic to be displayed on the node information table 1111 and the display device 20. The threshold value 603 is a standard of the characteristics of the node that can be improved when the characteristics of the characteristic item specified by the user 80 are expressed numerically.

The threshold value 603 can be preset with respect to the real value 5041 or the characteristic value 5042 of the characteristic 504. FIG. 7 shows an example in which the threshold value 603 is set for the real value 5041 of the characteristic 504. However, the standard used for setting the threshold value 603 can be changed. For example, the administrator may make changes, or the history of the characteristic value 5042 before and after the system modification may be acquired, and the threshold value 603 may be set based on the actual value at that time.

The characteristic value calculation unit ID 604 is an ID that can uniquely identify the program that analyzes the characteristic ID.

In the example of FIG. 7, the characteristic name managed as a characteristic item is the processing time, the number of programs, the number of special syntaxes, the importance of data, the number of special syntaxes of the implementation language, the execution time zone, the failure occurrence frequency, the repair frequency, and the like. Although the number of simultaneous repairs and the number of calling programs vary, other characteristic items may be set.

FIG. 8 is a flowchart showing the operation of the software structure analysis unit of FIG.
In FIG. 8, the software structure analysis unit 1011 can operate by using the detection that the source code has been added or changed to the repository of the source code management device 40 as a trigger.

At this time, the software structure analysis unit 1011 acquires the source code 4001 of the business system 30 from the source code management device 40 and analyzes the source code 4001 (S701). Specifically, the software structure analysis unit 1011 specifies the identification of the program and the data in the source code 4001, the relationship between the program and the data, the call relationship of the program, and the like.

Next, the software structure analysis unit 1011 assigns a node ID with the specified program and data as a node based on the analysis result of the source code 4001, and updates the node information table 1111 (S702).

Next, the processing-data call relationship and the reference relationship are analyzed, and the edge information table 1112 is updated based on the analysis result (S703).

The system characteristic evaluation device 10 can manage changes in the elements of the software structure to be displayed on the display device 20 by the process of FIG.

FIG. 9 is a flowchart showing the operation of the characteristic analysis unit of FIG.
In FIG. 9, the characteristic analysis unit 1021 can operate when the software structure data 111 is changed or periodically. At this time, the characteristic analysis unit 1021 acquires the node ID 501 from the node information table 1111 (S801).

Next, the characteristic analysis unit 1021 acquires the characteristic value calculation unit ID 604 for each characteristic item from the characteristic table 1121, acquires the software structure from the software structure data 111, and acquires the change history 4001 from the source code management device 40. The application log 3001 is acquired from the business system 30, and the failure history 5001 is acquired from the failure management device 50.
(S802).

Next, the characteristic analysis unit 1021 operates the characteristic value calculation unit 1022 for each characteristic item, and calculates the characteristic value 5042 for all the characteristic items (S803).

Next, the characteristic analysis unit 1021 determines whether or not the characteristic values 5042 of all the nodes have been calculated (S804). If the characteristic values 5042 of all the nodes have not been calculated, the process returns to S803 and the processes of S803 and S804 are repeated until the characteristic values 5042 of all the nodes are calculated. Then, when the characteristic analysis unit 1021 calculates the characteristic values 5042 of all the nodes, the characteristic value 5042 is stored in the node information table 1111 together with the real value 5041 of the characteristic 504 (S805).

The system characteristic evaluation device 10 can manage the change of the characteristic value 5042 of the node by the process of FIG.

Hereinafter, specific examples of the analysis method will be shown for each characteristic name 602 in the characteristic table 1211 shown in FIG. 7.

Regarding the processing time of the characteristic IDI1, the application log 3001 is analyzed and the processing time is calculated from the start time and the end time of the processing.
Regarding the number of programs of the characteristic IDI2, the source code 4001 is analyzed, and the number in which one program calls another program with respect to the program having a calling relationship is calculated.

For the number of special syntaxes of the characteristic IDI3, the source code 4001 is analyzed, and the number of times the syntax and the processing that are not common in the implementation language are used for the implementation method of the processing are calculated. In particular, in a program that uses a legacy language such as COBOL as an implementation language, the older the program is, the more frequently it is used, which may cause difficulty in repairing.

The data importance of the characteristic IDI4 is set based on the number of programs that refer to the data and the number of references between a plurality of functions by analyzing the source code 4001. If there is local data that is referenced only by a certain function and data that is referenced by various functions, set the latter to be more important.
For the execution time zone of the characteristic IDI5, the time information at which the program is executed is set by referring to the application log 3001 and the batch setting information.

Regarding the failure occurrence frequency of the characteristic IDI6, the failure information 5001 is analyzed and the number of failure occurrences in a preset period is calculated.
Regarding the repair frequency of the characteristic IDI7, the change history 4002 is analyzed and the number of repairs of the program is calculated.
Regarding the number of simultaneous repairs of the characteristic IDI8, the change history 4002 is analyzed, and the number of programs that are changed at the same time in each repair is calculated.

Regarding the variation in the number of calling programs of the characteristic IDI9, the source code 4001 is analyzed, the number of programs called from a certain program is analyzed, and the standard deviation and percentile values when the programs of the same layer are compared are set.

The characteristic value calculated for each characteristic item may be not only the calculated value itself, but also a percentile value or an N-level rank.

FIG. 10 is a diagram showing an operation flow of the improvement point analysis unit of FIG. 3 when a characteristic item is specified.
In FIG. 10, the display device 20 acquires software structure data 111 and characteristic data 112 from the system characteristic evaluation device 10 (S901), and displays the software structure 111 and the characteristic name 602 arranged according to the characteristic values (S902). ..

Next, when the user 90 specifies the characteristic name 602 (S903), the display device 20 transmits the characteristic ID 601 corresponding to the characteristic item of the characteristic name 602 to the characteristic evaluation unit 102 of the system characteristic evaluation device 10 (S904). ..

The improvement part analysis unit 1023 of the characteristic evaluation unit 102 determines whether or not the characteristic value of each node stored in the software structure data 1111 exceeds the threshold value based on the threshold value 603 set in the received characteristic ID 601. S905). By determining whether or not the characteristic value of each node exceeds the threshold value, it is possible to determine the improvement portion of the source code 4001. As shown in FIG. 7, when the threshold value 603 is set for the real value 5041 of the characteristic 504, it is determined whether or not the real value 504 of the characteristic 504 of each node exceeds the threshold value 603. May be good.

Next, the improvement location analysis unit 1023 merges the nodes that were not candidates for improvement in the analysis of the improvement location to generate the display node and the display edge, and creates the display software structure data 113 (S906). ..

Next, when the display software structure data 113 is created, the characteristic evaluation unit 102 instructs the display device 20 to display the display software structure data 113 (S907). Then, the display device 20 acquires the display software structure data 113 from the characteristic evaluation unit 102 (S908), arranges the reconstructed nodes and edges according to the characteristic values, and displays them (S909).

FIG. 11 is a flowchart showing the operation of the improved part analysis unit of FIG.
In FIG. 11, the improvement location analysis unit 1023 operates when the user specifies a characteristic item. At this time, the improvement location analysis unit 1023 reads the node information table 1111 and the characteristic table 1121 and acquires the threshold value for each characteristic item from the characteristic table 1121 (S1001).

Next, the improvement location analysis unit 1023 determines for each node in the node information table 1111 whether the real value 5041 of the characteristic 504 exceeds the threshold value 603 for each characteristic item (S1002). In the characteristic table 1121 of FIG. 7, a threshold value for the characteristic value 5042 may be set instead of the threshold value 603 for the real value 5041 of the characteristic 504. At this time, it is possible to determine whether the characteristic value 5042 exceeds the threshold value for each characteristic item.

Next, the improvement location analysis unit 1023 sorts all the nodes into execution time zones (S1003).

Next, the improvement location analysis unit 1023 treats the node exceeding the threshold value 603 as it is as an improvement candidate. On the other hand, the nodes that do not exceed the threshold value 603 are regarded as non-improvement candidates. Then, the improvement location analysis unit 1023 merges the nodes that are candidates for non-improvement, and recalculates the characteristic value of the merged node (S1004). The characteristic value of the merged node can be calculated based on the characteristic value of each node before the merge.

In the merging method, a plurality of non-improvement candidate nodes among the improvement candidate nodes are specified and merged with respect to the nodes sorted in the execution time zone order in S1003. For example, when the non-improvement candidate nodes are arranged consecutively in the order of execution time zone, the non-improvement candidate nodes can be merged with each other. On the other hand, when there are improvement candidate nodes between the non-improvement candidate nodes, it is possible to prevent the non-improvement candidate nodes from being merged with each other. As a result, the number of nodes with low priority for improvement can be reduced without impairing the execution order of the nodes and the relationship between programs in the software structure, and the visibility of the node to be improved can be improved. can.

Moreover, the characteristic value of the merged node can be set according to the characteristic item. At this time, the characteristic value of the merged node may be the sum of the characteristic values of the nodes before the merge, or may be the maximum value of the characteristic values of the node before the merge. For example, for nodes that do not have an inclusive relationship, such as processing time and the number of special syntaxes, the characteristic values of the merged nodes can be calculated by summing the nodes before merging. Regarding the importance of data and the execution time zone, the maximum value of the node before merging can be used as the characteristic value of the merged node. The nodes to be merged may be merged so as not to exceed the characteristic value specified by the user, and may be a plurality of nodes.

Next, the improvement point analysis unit 1023 sorts the nodes in the execution time series order and sets the edge based on the execution time of the node (S1005).

Next, the improvement location analysis unit 1023 stores the generated node information and edge information in the display node information table 1131 and the display edge information table 1132 of the display software structure data 113 (S1006).

FIG. 12 is a diagram showing an example of a display screen having a graph structure constructed based on the node information table of FIG. 5 and the edge information table of FIG.
In FIG. 12, the display screen 1101 can display a software structure including a node 1103 and an edge 1105, and a characteristic item 1102 that can be specified by the user 80. In the example of FIG. 12, the processing performance, the operating time zone, the number of programs, and the number of special syntaxes are displayed.

When displaying the software structure on the display screen 1101, display symbols can be set on the node 1103 and the edge 1105. As this symbol, a figure, a symbol, a character, or the like can be used. In the example of FIG. 12, the node 1103 indicating the program and data is indicated by a circle, and the edge 1105 indicating the calling relationship is indicated by an arrow.

Note that the node 1103 can be displayed in the execution time series order 1104 of the first node in the call relationship. In the example of FIG. 12, it is shown that the nodes S1 to S5 are executed first, and then the nodes S6 to S14 are executed.

The node showing the program or data may change the display method such as color, shading, and shape size according to the type of the node and the size of the characteristic value obtained from the characteristic value calculation unit 1022 data. For example, the node 1103 displays the size of the processing time by the size of the node. By changing the representation of the node in this way, it becomes easy to grasp the node having a high value among all the nodes.

In a system having a hierarchical structure in which a shell script calls a program, only the relationships between the nodes of the shell script in the upper hierarchy are displayed, and the calling relationships are expanded according to the specification of the user 80. You may. For example, it is assumed that the node S11 is selected on the display screen 1101 when the nodes S1 to S14 in the upper layer are displayed on the display screen 1101. At this time, the hierarchical structure 1107 of the node S11 can be displayed on the display screen 1101.

In the hierarchical structure 1107 of the node S11, it is assumed that the nodes P11 and P12 in the middle layer and the nodes D11 to D13 in the lower layer are provided. At this time, the symbols of the nodes S1 to S14, the symbols of the nodes P11 and P12, and the symbols of the nodes D11 to D13 may be made different from each other. In the example of FIG. 12, nodes P11 and P12 are shown as squares, and nodes D11 to D13 are shown as diamonds.

As a result, the entire software configuration of the business system 30 is first confirmed by the nodes S1 to S14 in the upper hierarchy, and then the target is expanded to the nodes of interest to the user and expanded into a hierarchical structure, and the relationship between the detailed program and the data. It becomes possible to advance the grasp of sex.

FIG. 13 is a diagram showing an example in which the characteristic value of the selected node is displayed on the display screen of FIG.
In FIG. 13, for example, when node 1103 is pressed on the display screen 1101, the characteristic table 1106 relating to node 1103 is displayed. In the characteristic table 1106, the characteristic value of the pressed node 1103 is displayed for each characteristic item. The characteristic table 1106 can be created from the characteristic 504 of the node information table 1111. As a result, the user 80 can confirm the characteristic value of the node 1103 that he / she is interested in among the large number of nodes 1103 displayed on the display screen 1101.

When the user 80 presses the item name of the characteristic item 1102, the characteristic value of the node 1103 and the threshold value are compared based on the threshold value of the designated characteristic item. At this time, the nodes that do not exceed the threshold value are regarded as non-improvement candidates, and the nodes that are non-improvement candidates are merged with each other. Then, the graph structure is reconstructed based on the merged node, and the reconstructed graph structure is displayed. This display method is particularly effective when applied to a batch system in which the fluctuation of the program execution time is small.

FIG. 14 is a diagram showing an example of a display screen having a reconstructed graph structure displayed on the display device of FIG.
The display screen 1201 of FIG. 14 shows a case where the processing performance, the operating time zone, and the number of programs are specified as the characteristic items.

Here, assuming that the processing performance is the processing time, it can be seen from FIG. 5 that the processing time of the node S1 is 7 sec and the processing time of the node S2 is 5 sec. It can be seen from FIG. 7 that the threshold value of the processing time is 10 sec. Therefore, regarding the processing time, it is determined that the processing time of each node S1 and S2 is below the threshold value. Therefore, the nodes S1 and S2 are non-improvement candidate nodes. Further, the nodes S1 and S2 are continuous in the execution time sequence order 1104. As a result, the nodes S1 and S2 are merged, and a new node S1 + 2 is generated. At this time, the real value of the characteristics of the nodes S1 + 2 can be the sum of the real values of the characteristics of the original nodes S1 and S2. Further, a characteristic value is given to the real value of the characteristic of the node S1 + 2. Then, by pressing the node S1 + 2, the characteristic table 1206 of the node S1 + 2 can be displayed.

On the other hand, it can be seen from FIG. 5 that the processing time of the node S3 is 250 sec. It can be seen from FIG. 7 that the threshold value of the processing time is 10 sec. Therefore, regarding the processing time, it is determined that the processing time of each node S3 is equal to or greater than the threshold value. Therefore, the node S3 is regarded as an improvement candidate node and is treated as it is.

FIG. 15 is a diagram showing an example of the contents of the node information table corresponding to the graph structure after the reconstruction of FIG. The node information table 1131 shows a case where the nodes S1 + 2 are generated by merging the nodes S1 and S2.

In FIG. 15, the node information table 1131 includes a node ID 1301 assigned to each program or data, a processing name 1302 capable of identifying the program name or data name for each node, and a program or data type 1303. , Stores the characteristic 1304 of the business system 30 related to program execution.

At least one set characteristic item is stored in the characteristic 1304. As the characteristic 1304, the real value 13041 of the characteristic 1304 and the characteristic value 13042 that has been normalized or the like can be stored, respectively.

Here, the node information table 1131 stores the information of the merged node and the information of the unmerged node among the nodes of FIG. 5 as a result of the operation of the improvement location analysis unit 1023. For the merged node, the characteristic value stores the value recalculated after the merge. FIG. 15 shows an example in which the shell script nodes S1 and S2 are stored as merged nodes S1 + 2. As for the processing time of the nodes S1 + 2, the total value of the processing times of the nodes S1 and S2 of the original shell script is stored.

FIG. 16 is a diagram showing an example of the contents of the edge information table corresponding to the graph structure after the reconstruction of FIG.
In FIG. 16, by merging the nodes S1 and S2, the edges attached to the nodes S1 and S2 also change. Therefore, the edge information table 1112 in FIG. 6 is updated to the edge information table 1132 in FIG. 16 according to the merge result of the nodes S1 and S2.

The edge information table 1132 stores an edge ID 1311 that can be uniquely specified for each call relationship between programs or a reference relationship between programs and data shown in FIG. 5, a caller node ID 1312 for the edge, and a call destination node ID 1313 for the edge. do. As the caller node ID and the callee node ID, the node ID 1301 stored in the node information table 1131 is used. In addition, the node information table 1132 can also store the relationship type 1314 so that it can be identified whether it is a call between programs or a call between a program and data.

By performing the above processing, it is possible to grasp not only the software structure but also the improvement target candidates based on the development status and the operation status, and it is possible to reduce the man-hours for examining the renewal target at the time of system renewal.

The present invention is not limited to the above-described embodiment as it is, and at the implementation stage, the components can be modified and embodied within a range that does not deviate from the gist thereof. In addition, various inventions can be formed by an appropriate combination of the plurality of components disclosed in the above-described embodiment. For example, some components may be removed from all the components shown in the embodiments. In addition, components across different embodiments may be combined as appropriate.
In this embodiment, production control has been described as an example, but it can be applied to other fields.

10 system characteristic evaluation device, 20 display device, 30 business system, 40 source code management device, 50 failure management device, 101 software structure analysis unit, 102 characteristic evaluation unit, 1011 software structure analysis unit, 1021 characteristic analysis unit, 1022 characteristic value Calculation unit, 1023 Improvement point analysis unit, 111 software structure data, 112 characteristic data, 113 display software structure data

Claims (13)

System characterization device and
Equipped with a display device
The system characteristic evaluation device is
A software structure analysis unit that analyzes the relationship between program calls and data in the source code and generates a graph structure with the program as a node and the program call relationship as a directional edge.
A characteristic analysis unit that calculates the characteristic value of the system for each node based on the analysis result of the source code and the system information of the system in which the program is executed.
It is provided with an improvement point analysis unit that merges the nodes based on the characteristic values and reconstructs the graph structure based on the merge result of the nodes.
The display device is a system characteristic evaluation system that symbolizes and displays nodes and edges of a graph structure reconstructed by the improvement point analysis unit. The system characteristic evaluation system according to claim 1, wherein the system information is operation information or failure information of the system. The characteristic analysis unit assigns characteristic values to each of the operation information, the failure information, the structure information of the program, and the change history of the program.
The system characteristic evaluation system according to claim 2, wherein the improvement location analysis unit merges the nodes based on the characteristic values. The operation information is the processing time or execution time zone of the program, the failure information is the failure frequency of the system, the structural information is the number of programs, the number of special syntaxes or the data importance, and the change history. Is the system characteristic evaluation system according to claim 3, which is the frequency of repairs or the number of simultaneous repairs of the program. The characteristic analysis unit calculates the characteristic value for each characteristic item and calculates the characteristic value for each characteristic item.
The improvement part analysis unit
Whether or not the characteristic value satisfies the condition given for each characteristic item is determined for each node, and the condition is determined for each node.
Merge the selected nodes based on the above judgment result,
The system characteristic evaluation system according to claim 1, wherein the edge of the node is set based on the execution time series information of the node. The improvement point analysis unit arranges the nodes in the execution time series order of the nodes in a graph structure composed of edges and nodes of the source code.
The system characteristic evaluation system according to claim 1, wherein the display device displays symbols of the nodes in the order of the execution time series. The improvement part analysis unit
Symbols for displaying the node and the edge on the display device are set on the node and the edge, respectively.
The type, color, thickness, size or display position of the symbol is changed according to the characteristic value.
The system characteristic evaluation system according to claim 6, wherein the display device displays a symbol whose type, color, thickness, size, or display position has been changed. The improved position analyzing unit changes the nodes and edges of the graph structure on the basis of the specified characteristics items,
The system characteristic evaluation system according to claim 4, wherein the display device displays a symbol reflecting the change of the node and the edge. A source code management device that holds the source code and the change history of the source code,
A business system that holds an application log that includes the operation information of the system,
The system characteristic evaluation system according to claim 2, further comprising a failure management device that holds a failure history report of the system. A structural analysis unit that generates static information about the source code based on the structural analysis of the source code.
It is provided with a characteristic evaluation unit that acquires dynamic information about the source code and evaluates the characteristics of the system in which the program in the source code is executed based on the static information and the dynamic information of the source code .
The static information of the source code is a graph structure in which the program in the source code is a node and the calling relationship of the program is a directional edge.
The characteristic evaluation unit
A characteristic analysis unit that calculates the characteristic values of the system in which the program included in the source code is executed based on the static information and dynamic information of the source code for each node.
A system characteristic evaluation device including an improvement point analysis unit that merges the nodes based on the characteristic values and reconstructs the graph structure based on the merged result of the nodes. The system characteristic evaluation device according to claim 10, wherein the dynamic information of the source code is operation information or failure information of the system, or change history of the source code. The operation information is the processing time or execution time zone of the program, the failure information is the failure occurrence frequency of the system, and the change history is the repair frequency or the number of simultaneous repairs of the program. System characteristic evaluation device. A threshold value is set for each characteristic item of the characteristic of the source code.
The system characteristic evaluation device according to claim 10 , wherein the improvement location analysis unit compares the characteristic value with the threshold value for each characteristic item, and selects a node to be merged based on the comparison result.

Images