JP5422589B2 - Module analysis system, module analysis method, and module analysis program - Google Patents

Description

  The present invention relates to a module analysis system, a module analysis method, and a module analysis program for visualizing a system structure composed of a plurality of modules.

  For existing systems, the program may be partially changed to add new functions or modify functions. In this case, it is necessary to investigate how the change work affects other system configurations. In recent system development, there is a case in which a module in which each function is converted into a component is combined. Here, one module calls another module, so that the modules are related to each other. In such a case, if the number of modules used in the system is large, the interrelationship becomes complicated, and it takes time to investigate the influence range due to the module change. Furthermore, in the case of a large-scale system, design development may be performed by dividing the system into subsystems, and it may be difficult to specify the affected range due to differences in consistency and uniformity between subsystems.

  Therefore, a technique for grasping the range of influence associated with the change of the system has been studied (see, for example, Patent Document 1). In the system described in this document, documents and programs (modules) deliverables are managed. For this purpose, a function information table, a module information table, a function-module relation table, and an inter-module relation information table are provided. When registering a deliverable, selection of a module necessary for the function configuration is guided based on the function information table, and selection of a function related to the module is guided based on the module information table. Furthermore, selection of other modules related to the module is guided based on the inter-module relation information table. Then, when searching for the influence range associated with the system change, the function-module related table and the inter-module related information table are searched according to the information input as the search key.

  In addition, a software asset management system for outputting contents that affect each unit for reusing or remodeling software assets has been studied (see, for example, Patent Document 2). In the system described in this document, documents and program deliverables are managed in software development. For this reason, it comprises function information for holding information on the functions of the system and module information for holding information on the modules. When registering a deliverable, tag information that identifies design information and indicates the relationship of the design information is added to the deliverable. When searching for the scope of impact due to system changes, search for functions related to the system and the function-module related information that holds the related information between modules, and the inter-module related information that holds the relationships between modules. The tagged design information and related information are extracted, and it is possible to search for deliverables and design information that have an influence upon correction between systems.

Japanese Patent Laying-Open No. 2005-100078 (first page, FIG. 1) JP 2008-123432 A (first page, FIG. 1)

In the system described in the above-mentioned patent document, a screen displaying the relationship between each module is output. Thereby, the relevance of each module can be grasped visually. However, since many modules are used in a large system, it may be difficult to grasp the influence range simply by displaying the relationship between the modules.

  The present invention has been made to solve the above-described problems, and its purpose is to provide a module analysis system, a module analysis method, and a module analysis program for efficiently grasping the degree of influence of each module. It is to provide.

In order to solve the above-described problem, the invention according to claim 1 is directed to a module identifier.
Relevance information storage means for associating and storing module identifiers of lower-level modules called by this module, call count information storage means for storing the number of calls by which this module is called for the module identifier, and a client terminal. A module analyzing system comprising: a control unit that identifies a lower module for each module that constitutes the analysis target system, associates both module identifiers, and registers them in the association information storage unit Means for calculating the number of calls for each module, registering the number of calls for each module identifier in the number-of-calls information storage means, and obtaining the module identifier of the search target module from the client terminal. Associated with the module identifier of the target module Module identifiers of module modules are acquired from the association information storage means, module identifiers of other lower modules associated with the module identifiers of the acquired lower modules are acquired up to a predetermined hierarchy, and the acquired module identifiers are A module structure diagram including an expanded display that is displayed separately, and a call count for the module identifier displayed in the module structure diagram is acquired from the call count information storage unit, and in the module structure diagram, In the module structure diagram, when a plurality of the same module identifiers are included in the module structure diagram, the module identifier display method is changed from the display position of the module identifier displayed in advance. The distance to the display position of the displayed module identifier Flip to determine the necessity of deploying a display in accordance with the determination result, and means for aggregating expand the lower module, and summarized in that and means for outputting the module structure diagram on the client terminal.

  According to a second aspect of the present invention, in the module analysis system according to the first aspect, the lower module is specified by using any one of a program identifier, a screen identifier, and a database identifier included in the module source code. Is the gist.

According to a third aspect of the present invention, in the module analysis system according to the first or second aspect , the control means specifies a type of the lower module, and the type of the lower module in the module structure diagram. The gist is to change the display method of the module identifier of the lower module according to the above.

According to a fourth aspect of the present invention, in the module analysis system according to any one of the first to third aspects, the complexity of the lower module is evaluated by analyzing the contents of the lower module. The gist is to change the display method of the module identifier of the lower module according to the complexity.

A fifth aspect of the present invention is the module analysis system according to any one of the first to fourth aspects, further comprising exclusion information storage means for registering a module not to be searched, wherein the exclusion is stored in the module structure diagram. The gist is to delete the display of the module identifier of the non-search target module registered in the information storage means.

Invention of Claim 6 is a module analysis system as described in any one of Claims 1-5 , When the said control means starts each module, it acquires the call log of another module, The gist is to modify the information stored in the relevance information storage means using the call log.
A seventh aspect of the present invention is the module data analysis system according to any one of the first to sixth aspects, wherein a user management record including data relating to a user ID and a skill level is recorded. A dictionary data storage unit in which a word record including data relating to a section, a headword, a skill level, and a translation word is recorded, and the control unit further uses the user data storage unit to use the user. A skill level corresponding to the person ID is specified, and a word included in a source code of a module constituting the analysis target system is extracted as a translation target word from the dictionary data storage unit, and the translation target word is stored in the dictionary data storage If it is registered as a headword of a word record recorded in the department, a translated word corresponding to the specified skill level is extracted and displayed. It is the gist of.

The invention described in claim 8 is related information storage means for storing a module identifier in association with a module identifier of a lower module called by the module, and the number of times the module is called for the module identifier. Is a module analysis system comprising a module analysis system comprising a call count information storage means for storing the information and a control means connected to the client terminal, wherein the control means constitutes a system to be analyzed. For each step, a lower module is specified, the module identifiers of both are associated and registered in the association information storage means, the number of calls is calculated for each module, and the number of calls for each module identifier is stored in the call number information storage means And the module of the search target module from the client terminal. When the module identifier is acquired, the module identifier of the lower module associated with the module identifier of the search target module is acquired from the relevance information storage unit, and the other lower module associated with the module identifier of the acquired lower module is acquired. Acquiring a module identifier of a module up to a predetermined hierarchy, generating a module structure diagram including an expanded display for displaying the acquired module identifier in a hierarchy, and from the call count information storage means to the module structure diagram Obtaining the number of calls for the displayed module identifier, and changing the display method of each module identifier according to the number of calls in the module structure diagram, and including a plurality of the same module identifiers in the module structure diagram If the From the display position of Lumpur identifier, the necessity of deploying display according to the distance to the display position of the module identifier to be displayed subsequent to
The gist is to execute the step of collecting and unfolding the expanded display of the lower modules and outputting the module structure diagram to the client terminal according to the determination result .

The invention described in claim 9 is related information storage means for storing a module identifier in association with a module identifier of a lower module that is called by the module, and the number of times the module is called for the module identifier. Is a program for analyzing a module analysis system using a module analysis system including a call count information storage means for storing the information and a control means connected to the client terminal, and the control means constitutes an analysis target system Means for identifying a lower module for each module, associating both module identifiers with each other and registering them in the relevance information storage means; calculating the number of calls for each module; and calling number information storage means for each module identifier Means for registering to the module of the search target module from the client terminal. The module identifier of the lower module associated with the module identifier of the search target module is acquired from the relevance information storage means, and the other lower module associated with the module identifier of the acquired lower module. Means for generating a module structure diagram including an expanded display for displaying the module identifiers up to a predetermined level and displaying the acquired module identifiers divided into layers, and displayed in the module structure diagram from the call count information storage unit Means for changing the display method of each module identifier according to the number of calls in the module structure diagram, and when the module identifier includes a plurality of the same module identifiers, Module displayed in advance From the display position of Besshi, and determines the necessity of deploying display according to the distance to the display position of the module identifier to be displayed subsequently, depending on the determination result, it means for aggregating expand the lower-level module, The gist is to cause the module structure diagram to function as means for outputting to the client terminal.

(Function)
According to the inventions described in claims 1, 8 , and 9 , the control unit specifies a lower module for each module constituting the analysis target system, associates both module identifiers, and registers them in the relevance information storage unit. . Further, the number of calls is calculated for each module, and the number of calls for each module identifier is registered in the call number information storage means. When the module identifier of the search target module is acquired from the client terminal, the module identifier of the lower module associated with the module identifier of the search target module is acquired from the relevance information storage unit. Next, module identifiers of other lower modules associated with the acquired module identifiers of the lower modules are acquired up to a predetermined hierarchy, and a module structure diagram including an expanded display that displays the acquired module identifiers divided into hierarchies is generated. . Further, the number of calls for the module identifier displayed in the module structure diagram is acquired from the call number information storage means, and the display method of each module identifier is changed in accordance with the number of calls in the module structure diagram. Then, the module structure diagram is output to the client terminal. Thereby, a related module can be specified according to the calling relationship, and the degree of influence of this module can be efficiently grasped.

  According to the second aspect of the present invention, the lower module is specified by using any one of the program identifier, the screen identifier, and the database identifier included in the module source code. Thereby, a related module can be specified by each element which comprises a system.

According to the present invention, in the module structure diagram, when a plurality of the same module identifiers are included in the module structure diagram, the module identifiers that are displayed subsequently are displayed from the display positions of the module identifiers that are displayed in advance. The necessity of unfolding display is determined according to the distance to the position. Accordingly, it is possible to suppress the repetition of the expansion display and provide the expansion status.

According to the invention described in claim 3 , the control means specifies the type of the lower module, and changes the display method of the module identifier of the lower module in the module structure diagram. Thereby, the influence degree according to the kind of module can be grasped | ascertained in a module structure drawing.

According to the fourth aspect of the invention, the content of the lower module is analyzed to evaluate the complexity, and the display method of the module identifier of the lower module is changed in the module structure diagram. Thereby, the influence degree according to the complexity of the module can be grasped in the module structure diagram.

According to the invention described in claim 5 , in the module structure diagram, the display of the module identifier of the non-search target module registered in the exclusion information storage means is deleted. Thereby, display of unnecessary modules can be deleted, and the module structure diagram can be simplified.

According to the sixth aspect of the present invention, when the module is activated, the control means acquires a call log of another module. And the information memorize | stored in the relevance information memory | storage means is corrected using a call log. Thereby, the relationship between modules can be reviewed according to an actual operation state.
According to the seventh aspect of the present invention, the control means further specifies the skill level corresponding to the user ID of the user using the user data storage unit, and analyzes from the dictionary data storage unit. When a word included in a source code of a module constituting the target system is extracted as a translation target word and the translation target word is registered as a headword of a word record recorded in the dictionary data storage unit, the identification The translated words corresponding to the skill level are extracted and displayed. This makes it possible to provide a translation that is easy to understand depending on the skill level.

  According to the present invention, it is possible to provide a module analysis system, a module analysis method, and a module analysis program for efficiently grasping the degree of influence of each module.

The system schematic of embodiment of this invention. It is explanatory drawing of the data recorded on each data storage part of this invention, (a) is a user data storage part, (b) is a dictionary data storage part, (c) is recorded in a relevance data storage part. FIG. Explanatory drawing of the process sequence in embodiment of this invention. Explanatory drawing of the process sequence in embodiment of this invention. Explanatory drawing of the process sequence in embodiment of this invention. Explanatory drawing of the process sequence in embodiment of this invention. Explanatory drawing of the screen expansion | deployment in embodiment of this invention. Explanatory drawing of relationship between design document, module, and database. Explanatory drawing of the relevance of each module. Explanatory drawing of the process sequence in other embodiment.

  Hereinafter, an embodiment embodying the present invention will be described with reference to FIGS. In this embodiment, a module analysis system for analyzing a module used in a system (analysis target system) designed based on a design document is assumed. In this analysis target system, various types of information processing are executed using data recorded in a database. In the module analysis system of this embodiment, as shown in FIG. 1, an analysis server 20 connected to a client terminal 10 and a program management server 30 is used.

  The client terminal 10 is a computer terminal used by a person in charge of module analysis. The client terminal 10 has a function of transmitting data via a network, a function of displaying received data, and the like. For this reason, the client terminal 10 includes a control unit (not shown), an input unit such as a keyboard and a mouse, an output unit such as a display, a communication unit, and the like.

  The program management server 30 stores design documents and program resources created in system development. Therefore, the program management server 30 includes a design document data storage unit 31 and a program resource storage unit 32.

  The design document data storage unit 31 stores files related to design documents created in basic design and detailed design during system development. As shown in FIG. 8, the design document file recorded in the design document data storage unit 31 is associated with system information (system ID) for specifying a system, and screen designs used in this system. Document data (screen design document file) and database design document data (DB design document file) are recorded. In the screen design document file, a screen name and a screen ID are recorded, and a program ID of a program used in this screen is recorded. In addition, the DB design document file includes data relating to the database name, database ID, table name, table ID, item name, item ID, and item definition.

The program resource storage unit 32 stores program resources of modules used in the system. In this program resource, as shown in FIG. 8, a screen control module created by HTML, a program module created by Java (registered trademark), and a stored series of a series of processing procedures for a database are combined into one DB processing program. A procedure (SP) module and the like are included. The screen control module holds the program name of the program used on this screen and the screen IDs of other screens to be called together with the screen name and screen ID for specifying each module. The program module holds a stored procedure ID of a stored procedure used in this program, together with a program name and a program ID for specifying each module. The SP module holds a database name, a database ID, a table name, a table ID, an item name, and an item ID used in this module, together with a stored procedure name and stored procedure ID for specifying each module.

  In such a module, as shown in FIG. 9, another screen can be called from a specific screen, or a specific program can be executed by a specific operation on the screen. When operating the database, the stored procedure is called. Thus, each module (screen, program, stored procedure) has a relationship between the module to be called and the module to be called. Here, it is assumed that a module to be called is an upper hierarchy and a module to be called is a lower hierarchy. Specifically, the program module can be specified as a lower module of the screen control module by the program ID recorded in the screen control module. The SP module can be specified as a lower module of the program module by the stored procedure ID recorded in the program module. The database used by the SP module can be specified by the database ID, table ID, item ID, etc. recorded in the SP module. Thereby, the relevance of the modules related to the items from the screen to the database can be specified.

The analysis server 20 includes a control unit 21, a user data storage unit 22, a dictionary data storage unit 23, and a relevance data storage unit 25.
The control unit 21 includes control means such as a CPU (not shown) and memories such as RAM and ROM, and executes module analysis processing. Specifically, each process (relationship registration stage, search reception stage, design document search stage, influence range search stage, expanded display stage, code display stage, etc.) described later is executed. By executing the module analysis program for this purpose, the control unit 21 of the analysis server 20, as shown in FIG. 1, relevance registration means 211, search reception means 212, design document search means 213, influence range search means 214. , Functioning as unfolding display means 215 and code display means 216.

  The relevance registration unit 211 executes a process of acquiring from the program management server 30 a design document for the analysis target system and a program created based on this design document. Further, the relevance registration unit 211 evaluates the relevance of the modules constituting the analysis target system and executes a process of registering in the relevance data storage unit 25.

  The search reception unit 212 executes processing for receiving a search request from the client terminal 10. This search reception means 212 takes over the processing to a design document search means 213 and an influence range search means 214 described later.

  The design document search unit 213 executes a process of searching for a related module using a screen name or a database name included in the design document. Then, the design document search means 213 executes processing for outputting the search result on the display of the client terminal 10.

The influence range search unit 214 executes a process of specifying a module and searching for another module related to this module. Then, the influence range search unit 214 executes a process of displaying the search result on the display of the client terminal 10.

The expansion display unit 215 executes processing for displaying, in a tree structure, module identifiers of other modules related to the specified module in the client terminal 10. This expanded display means 215 holds a type color classification table in order to change the display method for each module type. In this type color classification table, display colors are recorded corresponding to module types. Further, the development display means 215 holds a statistical evaluation color coding table in order to change the display method according to the statistical value of each module. In this statistical evaluation color classification table, display colors are recorded with respect to statistical values (first and second reference values in the present embodiment) that serve as threshold values for color classification. Further, the expansion display unit 215 includes a non-target ID memory (exclusion information storage unit) for recording a module ID that is not a search target in the module structure diagram.
The code display means 216 executes processing for displaying the module source code and outputting the translated result of the source code in the client terminal 10.

  As shown in FIG. 2A, a user management record 220 for managing a person in charge who uses this system is recorded in the user data storage unit 22. This user management record 220 is recorded when a person in charge is registered. The user management record 220 includes data related to the user ID and skill level.

Data relating to an identifier for identifying each person in charge is recorded in the user ID data area.
In the skill level data area, data relating to the level at which the skill of the person in charge is evaluated is recorded.

  As shown in FIG. 2B, the dictionary data storage unit 23 records a word record 230 for translating the source code. The word record 230 is recorded when a word included in the source code is registered. The word record 230 includes data relating to a headword, a skill level, and a translated word.

In the headword data area, data relating to words (command name, variable name, etc.) used in the source code is recorded.
In the skill level data area, data relating to an identifier for specifying a level at which a user's skill is evaluated is recorded.
In the translated word data area, data relating to the content of the headword translated according to the skill level is recorded.

  The relevance data storage unit 25 functions as relevance information storage means and call count information storage means. In this relevance data storage unit 25, as shown in FIG. 2C, a relevance management record 250 indicating the relevance of each module is stored. This association management record 250 is recorded when an association registration process described later is executed. The relevancy management record 250 includes data on the system ID, the target module, the module type, the design document key, the resource storage destination, the lower module, the number of calls, and the call frequency.

In the system ID data area, data relating to an identifier for specifying the system in which the module is used is recorded.
In the target module data area, data relating to a module identifier for specifying each module used in this system is recorded. As these module IDs, a screen ID, a program ID, a stored procedure ID (SPID), or the like is used.

In the module type data area, data relating to an identifier for specifying the type of the module (for example, HTML, servlet, customer, table, etc.) is recorded.
In the design document key data area, data relating to key information (screen name, DB table name, etc.) described in the design document for this module is recorded.

  Information for specifying the location where the program resource of this module is stored is recorded in the resource storage destination data area. By using this resource storage destination data, the source code of this module can be acquired from the program resource storage unit 32.

  In the lower module data area, data relating to a module identifier for specifying another module (lower module) called by this module is recorded. When calling a plurality of lower modules, the module IDs of all lower modules are recorded.

  In the call count data area, data relating to the number of times this module is called by another upper module is recorded. A module with a large number of calls indicates that the module is frequently used.

  In the call frequency data area, data relating to a statistical value regarding the rate at which this module is called is recorded. In the present embodiment, the call frequency is used as the statistical value. This call frequency is calculated by [module call count] / [total call count of all modules].

  A processing procedure for analyzing a module used in an analysis target system using the module analysis system configured as described above will be described with reference to FIGS. Here, the relevance registration process (FIG. 3), the relevance display process (FIG. 4), the development control process (FIG. 5), and the code display process (FIG. 6) will be described in this order.

(Relevance registration process)
First, the relevance registration process will be described with reference to FIG. In this association registration process, the analysis server 20 periodically accesses the program management server 30 and is executed by batch processing.

  Here, the control part 21 of the analysis server 20 performs the acquisition process of relevance information (step S1-1). Specifically, the relevance registration unit 211 of the control unit 21 accesses the program management server 30 and acquires a design document file from the design document data storage unit 31. Then, the relevance registration unit 211 acquires system information and design document key information (screen name, DB table name, etc.) from the design document file.

  Next, the relevance registration unit 211 sequentially extracts modules (screen control module, program module, SP module) recorded in the program resource storage unit 32 as processing targets. Then, the relationship registration unit 211 acquires a screen name, a screen ID, a DB table name, a program ID, a stored procedure ID, and the like included in the extracted source code of the processing target module. The screen ID, program ID, and stored procedure ID acquired here are the module IDs of the related modules in the lower hierarchy called by the processing target module.

Next, the control unit 21 of the analysis server 20 executes relevance information registration processing (step S1-2). Specifically, the relevance registration unit 211 of the control unit 21 generates a relevance management record 250 in which a module ID is recorded for each acquired module, and records the relevance management record 250 in the relevance data storage unit 25. Here, the relevance registration unit 211 identifies the module type based on the extension of the module and records it in the relevance management record 250. Furthermore, the relevance registration unit 211 records the design document key information acquired from the design document data storage unit 31 in the relevance management record 250. These processes are repeated for all modules recorded in the program resource storage unit 32.

  Next, the control unit 21 of the analysis server 20 executes a call count calculation process (step S1-3). Specifically, the relevance registration unit 211 of the control unit 21 sequentially specifies the module ID of the relevance management record 250 recorded in the relevance data storage unit 25 as the processing target ID, and this processing target ID is The number of calls is calculated by counting the number of relevance management records 250 recorded in the lower module data area.

  Next, the control unit 21 of the analysis server 20 executes a call count registration process (step S1-4). Specifically, the relevance registration unit 211 of the control unit 21 records the number of calls calculated in step S1-3 in the call count data area of the relevancy management record 250 of the processing target ID. This process is repeated for all relationship management records 250.

  Next, the control unit 21 of the analysis server 20 executes a call evaluation statistical evaluation process (step S1-5). Specifically, the relevance registration unit 211 of the control unit 21 acquires the number of calls recorded in all the relevance management records 250 and calculates the total number of calls by summing up the number of calls. Then, the relevance registration unit 211 calculates the call frequency by dividing the number of calls recorded in each relevance management record 250 by the total number of calls.

  Next, the control unit 21 of the analysis server 20 executes a statistical evaluation result registration process (step S1-6). Specifically, the relevance registration unit 211 of the control unit 21 records the call frequency calculated in step S1-5 in each relevance management record 250.

(Relevance display processing)
Next, the relevance display process will be described with reference to FIG. When evaluating the relevance of each module, the person in charge accesses the analysis server 20 using the client terminal 10.

  First, the control unit 21 of the analysis server 20 executes a login process (step S2-1). Specifically, the search reception unit 212 of the control unit 21 outputs a login screen on the display of the client terminal 10. This login screen is provided with a user ID input field. When a user ID is input in this input field, the search reception unit 212 acquires the user ID from the client terminal 10 and performs user authentication using the user data storage unit 22. When the user authentication is completed, the search reception unit 212 outputs a search reception screen 500 on the display of the client terminal 10 as shown in FIG. On this search reception screen 500, design document search and influence range search can be performed. When specifying a module based on a design document, a design document search screen is used. On the other hand, when the evaluation target module can be identified, the influence range search screen is used.

  A search condition input field is provided on the design document search screen. In the search condition input field, the screen name and database table name used in the design document are entered. In this case, the control unit 21 of the analysis server 20 executes a design document search process (step S2-2). Specifically, the search reception unit 212 of the control unit 21 takes over the process to the design document search unit 213. In this case, the design document search means 213 extracts the relationship management record 250 in which the keyword input in the search condition input field is recorded in the design document key data area in the relationship data storage unit 25.

Then, the design document search means 213 outputs the design document search result screen 501 shown in FIG. 7 on the display of the client terminal 10. On the design document search result screen 501, a list of module information (module ID, module name) recorded in the extracted association management record 250 is displayed. Thereby, the person in charge can grasp | ascertain the module relevant to a design document.

  On the other hand, the influence range search screen is provided with input columns for search conditions for module type, search direction, and module name. In the module type input field, the type of module (screen, program, stored procedure, etc.) is entered. In the search direction input field, an upper direction and a lower direction are designated. In the module name input column, a keyword (module ID or the like) for specifying the analysis target module is input. In this case, the control unit 21 of the analysis server 20 executes an influence range search process (step S2-3). Specifically, the search reception unit 212 of the control unit 21 takes over the process to the influence range search unit 214. In this case, the module information grasped in the design document search (step S2-2) can be input here. Further, when the module information is grasped in advance, the design document search process (step S2-2) can be omitted. When a search condition is set on the influence range search screen, the influence range search unit 214 uses the relevance data storage unit 25 to extract a relevance management record 250 that matches the search condition (module type, module name). .

  Next, the control part 21 of the analysis server 20 performs a module specific process (step S2-4). Specifically, the influence range search unit 214 of the control unit 21 outputs the module search result screen 502 shown in FIG. 7 on the display of the client terminal 10. This module search result screen 502 includes a list display of module information (module ID, module name) recorded in the relationship management record 250 extracted in step S2-3. Here, on the module search result screen 502, a desired module (analysis target module) is selected. In this case, the influence range search unit 214 specifies the module ID of the analysis target module selected on the module search result screen 502.

Next, the control unit 21 of the analysis server 20 executes a related module search process (step S2-5). Here, the search method differs depending on the search direction.
When “lower direction” is selected as the search direction, the influence range search unit 214 of the control unit 21 uses the relevance management record 250 in which the module ID of the analysis target module is recorded in the target module data area. Obtained from the data storage unit 25. Then, the influence range search unit 214 acquires the module ID (lower module ID) recorded in the lower module data area of the relationship management record 250. Further, the influence range search unit 214 searches the relevance data storage unit 25 for the relevance management record 250 in which the acquired lower module ID is recorded in the target module data area. Then, the module IDs of all lower modules related to the module ID to be analyzed are specified based on the mutual relationship between the modules.

  On the other hand, when “upper direction” is selected as the search direction, the influence range search unit 214 of the control unit 21 uses the relevance management record 250 in which the module ID of the analysis target module is recorded in the lower module data area. Obtained from the relevance data storage unit 25. Then, the influence range search unit 214 acquires the module ID (upper module ID) recorded in the target module data area of the relationship management record 250. Further, the influence range search unit 214 searches the relevance data storage unit 25 for the relevance management record 250 in which the higher module ID is recorded in the lower module data area. And it specifies based on the module ID of all the high-order modules relevant to module ID of analysis object, and the mutual relationship of a module.

Then, the influence range search unit 214 outputs the influence range display screen 503 shown in FIG. 7 on the display of the client terminal 10. This influence range display screen 503 includes a list display of module information (module type, module ID, module name) recorded in the relationship management records 250 of all the identified modules. Further, the influence range display screen 503 includes a module structure diagram display button. Further, the influence range display screen 503 includes a link icon for acquiring the program resource of the module for each module. In this link icon, data relating to the resource storage destination is recorded.

  When the module structure diagram display button is selected on the influence range display screen 503, the control unit 21 of the analysis server 20 executes a module structure diagram display process (step S2-6). Specifically, the expansion display means 215 of the control unit 21 outputs the module structure diagram display screen 504 shown in FIG. 7 on the display of the client terminal 10. On the module structure diagram display screen 504, the module ID of the module to be analyzed is displayed as a root node, and the module IDs of other modules directly related to this module are displayed as child nodes of the tree structure. Here, when “lower direction” is selected as the search direction, the module IDs of other modules called by the analysis target module are linked and displayed. On the other hand, when “upward direction” is selected as the search direction, other modules that call the analysis target module are linked and displayed.

This module structure diagram display screen 504 includes a “development display” button, a “type color classification” button, a “calling frequency” button, and a “non-search target setting” button.
When the “deployment display” button is selected on the module structure diagram display screen 504, the control unit 21 of the analysis server 20 executes a development control process (step S2-7). Here, the related modules associated with the module of the child node linked to the analysis target module are expanded and displayed in the tree structure. Specific processing will be described later with reference to FIG. Note that the following display change processing (step S2-8) to non-search target removal processing (step S2-10) according to the module type can also be used in expanded display in a tree structure.

  When the “type color classification” button is selected on the module structure diagram display screen 504, the control unit 21 of the analysis server 20 executes a display change process according to the module type (step S2-8). Specifically, the expansion display unit 215 of the control unit 21 acquires the module type of each module displayed on the module structure diagram display screen 504 from the association management record 250. Then, the expansion display unit 215 displays the module ID included in the module structure diagram display screen 504 by color classification for each module type using the type color classification table.

  When the “call frequency” button is selected on the module structure diagram display screen 504, the control unit 21 of the analysis server 20 executes display change processing according to the statistical evaluation result (step S2-9). Specifically, the expansion display unit 215 of the control unit 21 acquires the calling frequency of each module displayed on the module structure diagram display screen 504 from the relevance management record 250. Then, the development display unit 215 displays the module ID included in the module structure diagram display screen 504 in a color-coded manner according to the call frequency, using the statistical evaluation color-coding table. Here, the module having a higher calling frequency than the first reference value has a first color (for example, red), and the module having a higher calling frequency than the second reference value has a second color (for example, yellow). However, the module with a low calling frequency is changed to a third color (for example, black).

When the “non-search target setting” button is selected on the module structure diagram display screen 504, the control unit 21 of the analysis server 20 executes the process of removing the non-search target (step S2-1).
0). Specifically, the expansion display unit 215 of the control unit 21 outputs an exclusion target registration screen on the display of the client terminal 10. In this exclusion target registration screen, a check box and an input completion button are provided for the module ID of the related module. Here, the check box of the module not to be searched is selected. When the expansion display unit 215 detects selection of the input completion button, the module ID of the module not to be displayed is recorded in the non-target ID memory. Then, the expansion display unit 215 deletes the display of the module ID recorded in the non-target ID memory on the module structure diagram display screen 504, and expands it into a tree structure using the remaining module ID.

  On the other hand, when the link icon is selected on the influence range display screen 503, the control unit 21 of the analysis server 20 executes code display processing (step S2-11). This process will be described later with reference to FIG.

(Deployment control processing)
Next, the expansion control process will be described with reference to FIG. This process is executed when the “development display” button is selected in the module structure diagram. In this process, in the expanded module ID, the expanded display to the other hierarchy is performed only for the first appearance, and in the case of reposting, the expanded display to the other hierarchy is omitted.

  Here, first, the control unit 21 of the analysis server 20 executes the first module specifying process in the module structure diagram (step S3-1). Specifically, the expansion display unit 215 of the control unit 21 specifies the module ID of the module displayed at the top as the related module in the tree structure displayed on the module structure diagram display screen 504.

  Next, the control part 21 of the analysis server 20 performs the determination process about whether there exists expansion | deployment to another hierarchy (step S3-2). Specifically, the expansion display unit 215 of the control unit 21 makes a determination based on the relevance with other modules identified in step S2-5. If the module ID of the upper module or the lower module is specified, it is determined that there is expansion to another hierarchy.

  When there is an expansion to another hierarchy (in the case of “YES” in step S3-2), the control unit 21 of the analysis server 20 executes a determination process as to whether or not the module ID of the related module is the first appearance in the tree structure. (Step S3-3). Specifically, the expansion display unit 215 of the control unit 21 determines whether or not the identified module IDs of the upper module and the lower module are included in the upper part of the tree structure displayed on the module structure diagram display screen 504. . This is the first time the module ID is not included in the upper part of the tree structure.

  In the case of the first appearance (in the case of “YES” in step S3-3), the control unit 21 of the analysis server 20 executes the process of adding the development information to another hierarchy (step S3-4). Specifically, the expansion display means 215 of the control unit 21 executes the expansion control process for this related module. In the present embodiment, the expansion control process is repeated until the leaf node is reached.

  And the control part 21 of the analysis server 20 performs the determination process about whether it is complete | finished (step S3-5). Specifically, the expansion display means 215 of the control unit 21 determines whether or not expansion of all related modules displayed in the module structure diagram has been completed. This process (step S3-5) is executed also when there is no expansion to another hierarchy (in the case of “NO” in step S3-2), and when it is not the first appearance (in the case of “NO” in step S3-3). .

When the expansion for all the related modules is completed (in the case of “YES” in step S3-5), the expansion control process is ended.
On the other hand, if there remains a related module that has not been expanded (in the case of “NO” in step S3-5), the control unit 21 of the analysis server 20 executes a process for specifying the next module (step S3- 6). Specifically, the expansion display means 215 of the control unit 21 identifies the next module in the module expansion diagram. Then, the processing from step S3-2 is repeated.

(Code display process)
Next, the code display process will be described with reference to FIG. This process is executed when a link icon is selected on the influence range display screen 503.

  Here, first, the control unit 21 of the analysis server 20 executes a first frame display process (step S4-1). Specifically, the code display means 216 of the control unit 21 outputs the code translation screen 505 shown in FIG. 7 on the display of the client terminal 10. The code translation screen 505 includes a left frame (first frame) for displaying codes and a right frame (second frame) for displaying translated words of the source code. Here, the code display unit 216 acquires the resource storage destination recorded in the association management record 250 of the module ID of the selected link icon. Then, the code display unit 216 acquires the source code of the target module from the program resource storage unit 32 using this resource storage destination, and outputs it to the left frame of the code translation screen.

  Next, the control unit 21 of the analysis server 20 executes display change processing for each nested structure (step S4-2). Specifically, the code display means 216 of the control unit 21 specifies a nested structure in the source code displayed in the left frame. Then, the code display unit 216 changes the display color of the source code for each nested structure.

  Moreover, the control part 21 of the analysis server 20 performs a 2nd frame display process (step S4-3). Specifically, the code display means 216 of the control unit 21 displays the module source code acquired from the program resource storage unit 32 in the second frame so as to match the source code display line of the first frame. .

  Next, the control unit 21 of the analysis server 20 executes a skill level specifying process (step S4-4). Specifically, the code display unit 216 of the control unit 21 acquires the skill level recorded in the user management record 220 specified in the login process (step S2-1).

  Next, the control part 21 of the analysis server 20 performs the specific process of a translation object word (step S4-5). Specifically, the code display means 216 of the control unit 21 sequentially extracts words included in the source code displayed in the second frame as translation target words.

  Next, the control part 21 of the analysis server 20 performs a translation process (step S4-6). Specifically, the code display means 216 of the control unit 21 compares the extracted translation target word with the headword recorded in the word record 230 recorded in the dictionary data storage unit 23. When the translation target word is registered as a headword, the code display unit 216 extracts a translation word corresponding to the skill level specified in step S4-4 from the word record 230. When the translation target word is not registered as a headword or when the translation word corresponding to the skill level is not registered, the source code is left as it is.

According to this embodiment, the following effects can be obtained.
(1) In the present embodiment, the relevance data storage unit 25 stores a relevance management record 250 that indicates the relevance of each module. Then, the control unit 21 of the analysis server 20 executes related module search processing (step S2-5) and module structure diagram display processing (step S2-6). Thereby, about a specific module, the other module relevant to this module can be grasped | ascertained. Therefore, when a specific module is corrected, the influence range of other modules due to the correction can be grasped.

  (2) In the present embodiment, in the relevance display process, “upper direction” or “lower direction” is selected as the search direction. The control unit 21 of the analysis server 20 executes related module search processing according to the search direction (step S2-5). Thereby, it is possible to grasp the influence on the module that is not called and the module that is called.

  (3) In the relevance display process of this embodiment, the control unit 21 of the analysis server 20 executes a display change process according to the module type (step S2-8). This makes it possible to efficiently grasp the types of related modules that are affected.

  (4) In the relevance display process of this embodiment, the control unit 21 of the analysis server 20 executes a display change process according to the statistical evaluation result (step S2-9). Thereby, it is possible to grasp the magnitude of the influence in the related module that is affected.

  (5) In the relevance display process of the present embodiment, the control unit 21 of the analysis server 20 executes a removal process that is not a search target (step S2-10). Thereby, the module structure diagram can be simplified by excluding modules that do not need to be displayed.

  (6) In the present embodiment, in the expansion control process, when the module ID of the related module appears for the first time (in the case of “YES” in step S3-3), the control unit 21 of the analysis server 20 expands to another hierarchy. Information addition processing is executed (step S3-4). As a result, it is possible to grasp not only related modules that are directly affected but also indirectly affected modules.

  On the other hand, when the module ID of the related module is not first displayed (in the case of “NO” in step S3-3), the process of adding development information to another layer (step S3-4) is not executed. As a result, it is possible to generate an easy-to-view module structure diagram by collecting the expanded display and suppressing the repetition of the same display.

  (7) In the present embodiment, in the code display process, the control unit 21 of the analysis server 20 executes a display change process for each nested structure (step S4-2). Moreover, the control part 21 of the analysis server 20 performs a translation process (step S4-6). Thereby, the relationship between a source code and a translated sentence can be easily grasped.

  Further, the control unit 21 of the analysis server 20 executes skill level acquisition processing (step S4-4). This makes it possible to provide a translation that is easy to understand depending on the skill level.

In addition, you may change each said embodiment as follows.
In the above embodiment, the control unit 21 of the analysis server 20 executes module structure diagram display processing (step S2-6). On the module structure diagram display screen 504, the module ID of the module to be analyzed is displayed as a root node, and the module IDs of other modules directly related to this module are displayed as child nodes of the tree structure. Here, the root node may be changed and displayed. For example, when a child node displayed on the module structure diagram display screen 504 is selected, the selected child node is set as a root node, and module IDs of other modules directly related to this module are displayed as child nodes of the tree structure. Display as. Thereby, other modules related to an arbitrary module can be displayed in a tree structure.

  In the above embodiment, the control unit 21 of the analysis server 20 performs a translation process (step S4-6). Specifically, the code display means 216 of the control unit 21 compares the extracted translation target word with the headword recorded in the word record 230 recorded in the dictionary data storage unit 23. Here, the dictionary used for translation may be changed according to the application field of the analysis target system. In this case, the field of use is recorded in the word record 230 of the dictionary data storage unit 23. Then, the code display unit 216 acquires information related to the field of use of the system from the comment sentence recorded in the analysis target system, and executes a translation process using the word record 230 of the field of use. Thus, accurate translation can be performed according to the field of use of the analysis target system.

  In the above embodiment, the call frequency is recorded as the module evaluation result (statistical evaluation result) in the relevance data storage unit 25. Then, in the relevance display process, a display change process is executed according to the statistical process result (step S2-9). The display changing method is not limited to this. For example, it is possible to change the display method according to the evaluation results such as the number of codes in each module, the complexity, and the type of use variable. For the number of codes, the relevance registration unit 211 counts the number of lines of the source code of the related module. Regarding the complexity, the relevance registration unit 211 counts the number of repetitions, the number of determination branches, the number of nestings, and the like in the source code of the related module. Then, an evaluation result is calculated by comparing the count value with a reference value. As for the type of the use variable, the relevance registration unit 211 changes the display method according to the access modifier (public, private, protected) assigned to the variable.

  In the above embodiment, in the association display process, the display change process is executed according to the statistical process result (step S2-9). Here, the display color is changed. The change of the display method is not limited to this. For example, the font or character size representing the module ID may be changed.

  In the above embodiment, in the expansion control process, if it is the first appearance (in the case of “YES” in step S3-3), the control unit 21 of the analysis server 20 executes the process of adding expansion information to another hierarchy (step S3-3). S3-4). The method for integrating the expanded display is not limited to this. If the developed module ID is not the first appearance, a link for jumping to the display position of the first appearance of the module ID may be set. As a result, the expanded display (expanded information to other layers) can be confirmed at the first display position of the module ID.

  In the above embodiment, in the expansion control process, if it is the first appearance (in the case of “YES” in step S3-3), the control unit 21 of the analysis server 20 executes the process of adding expansion information to another hierarchy (step S3-3). S3-4). The method for integrating the expanded display is not limited to this. When module IDs of the same related module are detected at a location that is more than the reference number of steps from the previous display position, the module IDs may be expanded and displayed again. This process will be described with reference to FIG. In this case, the development display means 215 holds a reference value for determining whether or not development display is necessary.

First, similarly to steps S3-1 to S3-3, the control unit 21 of the analysis server 20 identifies the first module (step S5-1), and determines whether there is an expansion to another layer ( In step S5-2), a determination process (step S5-3) as to whether or not this is the first time is executed.

  In the case of the first appearance (in the case of “YES” in step S5-3), similarly to step S3-4, the control unit 21 of the analysis server 20 executes an expansion information addition process to another hierarchy (step S5-4). ).

  On the other hand, if it is not the first appearance (in the case of “NO” in step S5-3), the control unit 21 of the analysis server 20 performs a calculation process of the distance from the display position of the expanded display of the same module (step S5-5). . Specifically, the expansion display means 215 of the control unit 21 calculates the distance (number of steps) from the position of the previously expanded display to the current module display position with the module ID of the same related module in the tree structure. To do.

  Next, the control part 21 of the analysis server 20 performs the determination process about whether distance is more than a reference value (step S5-6). Specifically, the expansion display means 215 of the control unit 21 compares the calculated distance (number of steps) with a reference value.

If the distance is greater than or equal to the reference value (“YES” in step S5-6), the control unit 21 of the analysis server 20 executes a process of adding development information to another layer (step S5-4).
On the other hand, when the distance does not reach the reference value or more (in the case of “NO” in step S5-6), similarly to step S3-5, the control unit 21 of the analysis server 20 determines whether or not to end. Execute (Step S5-7).
When the development for all the related modules is finished (in the case of “YES” in step S5-7), the development control process is finished.

If there is a module that has not been expanded (“NO” in step S5-7), the control unit 21 of the analysis server 20 determines the next module as in step S3-6. Is executed (step S5-8).
As a result, when it is far from the position where it has been expanded and displayed, it is possible to easily confirm the expanded content by performing expanded display on another layer again.

  In the above embodiment, the control unit 21 of the analysis server 20 executes relevance information acquisition processing (step S1-1). Here, the relevance of each module is specified by analyzing the source code. The method for specifying the relationship is not limited to this. For example, it is possible to record an operation log and re-evaluate the relevance based on the operation log. In this case, each module is actually operated, and an operation log (call log) for other modules called by each module is recorded in the operation log storage unit based on all operation states. Then, the module relevance recorded in the call log is compared with the relevance recorded in the relevance data storage unit 25. If the call between the modules cannot be confirmed in the call log, the relevance of these modules is corrected in the relevancy management record 250 of the relevance data storage unit 25. As a result, even if there is a relationship between modules in the source code, the relationship can be corrected if it is not actually used.

In the above embodiment, the control unit 21 of the analysis server 20 executes a process for adding development information to another layer (step S3-4). Specifically, the expansion display unit 215 of the control unit 21 repeats the expansion control process until the leaf node is reached. Instead of this, the expansion control process in the other hierarchy may be executed up to a predetermined hierarchy. In this case, the expansion display unit 215 holds data relating to the number of reference hierarchies to be expanded. Then, the expansion display unit 215 counts the expanded hierarchies, and ends the expansion to other hierarchies when the number of reference hierarchies is reached.

  In the above embodiment, the control unit 21 of the analysis server 20 performs a translation process (step S4-6). Here, the translation target word is translated using the dictionary data storage unit 23. In this case, you may make it interpret according to the structure of a source code. In this case, the dictionary data storage unit 23 records the translation pattern to be translated according to the syntax including the headword. For example, the part of speech of the translated word is specified and rearranged in an order that is easy to read as Japanese.

  DESCRIPTION OF SYMBOLS 10 ... Client terminal, 20 ... Analysis server, 21 ... Control part, 211 ... Relevance registration means, 212 ... Search reception means, 213 ... Design document search means, 214 ... Influence range search means, 215 ... Deployment display means, 216 ... Code display means, 22 ... user data storage section, 23 ... dictionary data storage section, 25 ... relevance data storage section, 30 ... program management server, 31 ... design document data storage section, 32 ... program resource storage section.

Claims (9)

Relevance information storage means for storing a module identifier in association with a module identifier of a lower module called by the module;
Call number information storage means for storing the number of calls for which this module has been called for the module identifier;
A module analysis system comprising control means connected to a client terminal,
The control means is
For each module constituting the analysis target system, a lower module is specified, and a module identifier of both is associated and registered in the association information storage unit;
Means for calculating the number of calls for each module, and registering the number of calls for each module identifier in the call number information storage means;
When the module identifier of the search target module is acquired from the client terminal, the module identifier of the lower module associated with the module identifier of the search target module is acquired from the relevance information storage unit,
Acquiring the module identifier of another lower module associated with the module identifier of the acquired lower module up to a predetermined hierarchy;
Means for generating a module structure diagram including an expanded display for displaying the acquired module identifier in a hierarchy;
Obtaining the number of calls for the module identifier displayed in the module structure diagram from the call number information storage means,
In the module structure diagram, means for changing a display method of each module identifier according to the number of calls,
In the module structure diagram, when a plurality of the same module identifiers are included, an expansion display is required depending on the distance from the display position of the module identifier displayed in advance to the display position of the module identifier displayed subsequently. Means for determining whether or not, and in accordance with the determination result, the expanded display of the lower module,
A module analysis system comprising: means for outputting the module structure diagram to the client terminal. 2. The module analysis system according to claim 1, wherein the lower module is specified by using any one of a program identifier, a screen identifier, and a database identifier included in a module source code. The control means identifies the type of the lower module,
3. The module analysis system according to claim 1, wherein in the module structure diagram, a display method of a module identifier of the lower module is changed according to a type of the lower module. Analyze the contents of lower modules to evaluate the complexity,
In the module structure diagram, depending on the complexity of the lower module, the module analysis system according to any one of claims 1-3, characterized in that to change the appearance of the module identifier of the lower-level module. It further includes an exclusion information storage means that registers modules not to be searched,
The module analysis system according to any one of claims 1 to 4 , wherein in the module structure diagram, the display of the module identifier of the module not to be searched registered in the exclusion information storage unit is deleted. When the control unit starts each module, it acquires a call log of another module,
The call log using a module analysis system according to any one of claims 1-5, characterized in that modifying the relevant information information stored in the storage means.   A user data storage unit in which a user management record including data relating to a user ID and skill level is recorded;
  A dictionary data storage unit in which word records including data on headwords, skill levels, and translated words are recorded;
  The control means further comprises:
  Using the user data storage unit, the skill level corresponding to the user ID of the user is specified,
  From the dictionary data storage unit, the word included in the source code of the module constituting the analysis target system is extracted as a translation target word,
  The translation word according to the specified skill level is extracted and displayed when the translation target word is registered as an entry word of a word record recorded in the dictionary data storage unit. The module analysis system of 1-6. Relevance information storage means for storing a module identifier in association with a module identifier of a lower module called by the module;
Call number information storage means for storing the number of calls for which this module has been called for the module identifier;
A method for analyzing a module using a module analysis system including a control unit connected to a client terminal,
The control means is
For each module constituting the analysis target system, identifying a lower module, associating both module identifiers and registering them in the association information storage means,
Calculating the number of calls for each module, and registering the number of calls for each module identifier in the call number information storage means;
When the module identifier of the search target module is acquired from the client terminal, the module identifier of the lower module associated with the module identifier of the search target module is acquired from the relevance information storage unit,
Acquiring the module identifier of another lower module associated with the module identifier of the acquired lower module up to a predetermined hierarchy;
Generating a module structure diagram including an expanded display for displaying the acquired module identifier in a hierarchy;
Obtaining the number of calls for the module identifier displayed in the module structure diagram from the call number information storage means,
In the module structure diagram, changing the display method of each module identifier according to the number of calls,
In the module structure diagram, when a plurality of the same module identifiers are included, an expansion display is required depending on the distance from the display position of the module identifier displayed in advance to the display position of the module identifier displayed subsequently. Determining whether or not, and aggregating the expanded display of the lower modules according to the determination result;
And outputting the module structure diagram to the client terminal. Relevance information storage means for storing a module identifier in association with a module identifier of a lower module called by the module;
Call number information storage means for storing the number of calls for which this module has been called for the module identifier;
A program for analyzing a module using a module analysis system comprising a control means connected to a client terminal,
The control means;
Means for identifying lower modules for each module constituting the analysis target system, associating both module identifiers and registering them in the relevance information storage means;
Means for calculating the number of calls for each module and registering the number of calls for each module identifier in the call number information storage means;
When the module identifier of the search target module is acquired from the client terminal, the module identifier of the lower module associated with the module identifier of the search target module is acquired from the relevance information storage unit,
Acquiring the module identifier of another lower module associated with the module identifier of the acquired lower module up to a predetermined hierarchy;
Means for generating a module structure diagram including an expanded display for displaying the acquired module identifier in a hierarchy;
Obtaining the number of calls for the module identifier displayed in the module structure diagram from the call number information storage means,
In the module structure diagram, means for changing the display method of each module identifier according to the number of calls,
In the module structure diagram, when a plurality of the same module identifiers are included, an expansion display is required depending on the distance from the display position of the module identifier displayed in advance to the display position of the module identifier displayed subsequently. Means for determining whether or not, and in accordance with the determination result, the expanded display of the lower-level modules,
A module analysis program that functions as means for outputting the module structure diagram to the client terminal.

Images