JP2008123254A - INFLUENCE ANALYSIS TOOL FOR LARGE-SCALE BUSINESS SYSTEM USING Java (R) LANGUAGE PROGRAM - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a tool for extremely reducing a load on the maintenance work of a large-scale business system using a Java (R) language program. <P>SOLUTION: The tool for analyzing the Java (R) language program extracts class information, method information, and reference destination method information from the class file of the Java (R) language program. The tool generates, based on the extracted information, pair information of the combination of an association source concrete class method ID, composed of a concrete class ID and a concrete method ID, with an association destination concrete class method ID, which is the association destination of the association source concrete class method ID. The tool designates the desired class method, extracts the series of concrete class methods to be associated with the class method, and displays the methods on a screen. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to an analysis tool for a Java (registered trademark) language program, and particularly to an impact analysis tool for a large-scale business system using the Java language program. Java is a registered trademark of Sun Microsystems, Inc.

  For example, in a large-scale business system such as a securities business, a COBOL language program has been generally used. In order to increase maintenance efficiency, the program is generally classified for each processing purpose and has a hierarchical structure. In addition, there are a variety of structural analysis tools that presuppose that the program has a hierarchical structure. By using these tools, the system can be efficiently maintained.

  Recently, in order to reconstruct a large-scale business system, an example in which the language used is changed from COBOL to Java is increasing.

  Compared to the COBOL language, the Java language is superior in productivity, extensibility, and applicability, so it is widely used for open system development. However, there are various problems in maintenance work efficiency as described below. In fact, it is used only in very limited conditions.

  In the following, the outline of the Java language will be described first, and then problems when the Java language program is used for the development of a large-scale business system will be described.

  A Java language program is composed of a combination of a plurality of classes. A class is a collection of data and processing. In other words, in the Java language, a part called a class in which related data and processes are collected is created, and a complex program is created by freely combining and reusing them. Data constituting a class is called a field, processing is called a method, and a field or method is called a class member.

  A class is program code, and in order to actually execute it on a computer, an object must be created. An object is a name for a class when a class that is a program code exists in an executable state on a computer memory. Creating an object from a class is called instantiation or objectification.

  A field is a variable (data) in a class, and a method defines a data operation method (processing). The value to be processed is called an argument (parameter), and the value resulting from the processing is called a return value (return value).

  One reason why the extensibility and applicability of Java language programs is excellent is that there is a mechanism of class inheritance. Class inheritance is a function in which a class inherits members of another class. For example, class B can inherit class A members. The class that is inherited is called a superclass (parent class), and the class that is inherited is called a subclass (child class).

  In the Java language, what is called an interface that defines an access method for a class is used. An interface is similar to a class, but differs from a class in that only constants and the abstract methods described below can be members.

  Classes are classified into abstract classes, concrete classes, and interfaces. An abstract class is obtained by adding an interface function to a normal class, and a concrete class describes an actual program code and can be instantiated. Interfaces and abstract classes cannot be instantiated as they are. In other words, among the abstract class, concrete class, and interface, only the concrete class can generate object code.

  On the other hand, methods are also classified into abstract methods and concrete methods. An abstract method is a method that defines only the method name, return type, and arguments, but does not define logic (contents of processing). This abstract method is defined in the interface and the abstract class. A concrete method defines a method name, a return type, an argument, and logic, and is defined by an abstract class or a concrete class. The concrete method of the reference destination may be referred to as an implementation method, and a class having the implementation method may be referred to as an implementation class.

  Next, a program written using the Java language will be described with reference to FIG.

  In the figure, reference numerals 100, 300, and 400 denote concrete classes, and reference numeral 200 denotes an example of an interface. The concrete class 100 has the name Userclass. The class has a method called usrmdt. The method indicates that the reference destination is an interface called IStrategy.

  On the other hand, the interface 200 has a name IStrategy and includes an abstract method tc.

  The concrete class 300 has a name classA and a concrete method tc. The concrete class 300 is called an implementation class because it generates an object. Since the concrete class 100 is associated with another concrete class 300 via the interface 200, in this specification, 100 is referred to as an association source class, and 300 is referred to as an association destination class.

  FIG. 1-2 is a class diagram showing the relationship between classes of programs described as in FIG. 1-1. Class 100 refers to interface 200 and class 300 refers to class 400. Further, since the class 300 inherits the interface 200, it is displayed using a symbol 500.

  FIG. 1C is a sequence diagram illustrating the relationship between objects. As described above, only concrete classes can generate objects among concrete classes, abstract classes, and interfaces. This figure shows the relationship between objects 100 ′, 300 ′, and 400 ′ of classes 100, 300, and 400. Objects of class 100, 300, 400 are generally created by another class. A class that generates each object 100 ′, 300 ′, and 400 ′ is referred to as a generation class, and classes 100, 300, and 400 are referred to as generated classes.

  Next, information included in one class will be described.

  FIG. 1-4 is a diagram illustrating information included in one class and the relationship between the information. One class includes class information 10, method information 20, data information 60, and information 30 indicating a relationship between methods.

  The class information 10 includes a class ID 11, a class name 12, a super class name (parent class name) 13, and an interface name 14. The method information 20 includes information on a method ID 21, a method name 22, a method type (concrete type, abstract type) 23, an argument 24, and an argument type 25.

  The inter-method relation information 30 includes a method 31 referred to by the method 21, a method name 32 of the referred method, and an argument type 33 of the reference method. The reference method 31 is classified into four types: a method 34 with a static qualifier, an interface method 35, a special method 36 called a constructor, and another method 37. A constructor is a method that is automatically called when an object is created, and a static method is a special method that makes the operation the same for any object.

  The interface 35 includes information on the interface name 41 and the method type 42, and the other class 37 also includes information on the reference class 38 and the method type 39. The static method 34 includes information on the reference destination class 40.

  When an object is generated with the class 10, a class name 51 that is information of the class 50 that is a target for generating the object is included.

  On the other hand, information 60 such as a variable name 61, a reference class 62 when referring to a variable, a variable type 63, and the like is included as information 60 on the class 10 field.

Next, problems when the Java language program is used for a large-scale business system will be described.
Since the Java language is composed of a combination of a large number of classes, it is excellent in productivity and is also a language suitable for extending the system. However, when maintaining the system, there are a number of problems as described below.

  If the Java language is used for a large-scale administrative program such as a securities business system, the number of classes ranges from tens of thousands to hundreds of thousands, and the number of methods ranges from hundreds of thousands to millions. Become.

  In such a system, if any trouble occurs, the class or method that caused the trouble must be identified. It is also necessary to know the set of classes and methods that will be affected when the identified class or method is modified.

  Similarly, when adding or modifying a class to add a new function to the system, it is necessary to grasp a series of classes and methods that are affected by the added or modified class or method.

  In order to improve the efficiency of such maintenance work, as in the case of using the COBOL language, the program using the Java language is classified into tens of thousands to hundreds of thousands of classes according to the processing purpose of the work. It is common to have a structured structure. In the maintenance of the Java program, the class diagram illustrated in FIG. 1-2 and the sequence diagram illustrated in FIG. 1-3 are used. You know the set of classes and methods that are associated with a class or method.

  However, the Java language program has a structure in which it is difficult to identify a class or method in which a problem has occurred, or to identify a series of classes or methods related to the identified class or method. The burden on the person is very large.

  One reason is that the conventional tool cannot grasp the detailed flow of each method.

  Further, as illustrated in FIG. 1C, a sequence diagram showing the flow of the objects 100 ′, 300 ′, and 400 ′ is also used. In the Java language program, the concrete classes 100, 300, and 400 and the objects 100 ′ and 300 are used. 'And 400' are not synchronized. That is, a concrete class and a class that generates an object of that class are generally separate, such as an object 100 ′ is generated by a concrete class 300 and an object 300 ′ is generated by a concrete class 400. Even if it is used, the burden on the program developer is not reduced so much.

  Furthermore, although the conventional analysis tools can display class diagrams and sequence diagrams, the number of classes and objects that can be displayed on a single screen is limited to about 10 or so, and a huge number of classes and methods are grasped. This is another reason why it is difficult to maintain the program.

  An object of the present invention is to provide a tool that can solve the conventional problems as described above and can remarkably reduce the burden of maintenance work in a large-scale business system using a Java language program.

  Specifically, an object of the present invention is to provide a tool capable of displaying a relation between concrete classes and methods, including concrete methods belonging to a class hidden in a source code program due to class inheritance.

  Another object of the present invention is to provide a tool capable of displaying concrete class methods hidden by an interface or abstract class and their relations.

  Another object of the present invention is to provide a tool capable of displaying all concrete class methods belonging to a certain class and their relations in a program having a hierarchical structure in which classes are functionally classified. There is.

  Another object of the present invention is that when a desired concrete class method is specified in a program in which the classes are functionally classified and hierarchized, a series of related class methods are specified. The purpose is to provide a tool that can display concrete classes and methods.

  Another object of the present invention is to generate a design document by reverse engineering based on the implemented resources, greatly reducing the cost of maintaining the design document, and at the same time, avoiding a discrepancy between the design document and the implementation. To provide tools.

  In order to achieve the above object, an analysis tool according to the present invention includes a first means for extracting class information, method information, and reference destination method information from a class file of a Java language program, and extracted class information, method information, and Based on the reference destination method information, it consists of a combination of a related source concrete class / method ID consisting of a concrete class ID and a concrete method ID, and a related destination concrete class / method ID which is a related destination of the related source concrete class / method ID. The second means for generating pair information and the third means for specifying a desired class method, extracting a series of concrete class methods related to the class method, and displaying them on the screen. It has one feature.

  Another feature of the present invention is that the class information of the first means is class ID information, class type information indicating whether the class belongs to a concrete class, an interface, or an abstract class, and the class Including the class information in the parent-child relationship.

  In another feature of the present invention, the method information of the first means includes method ID information and method type information indicating whether the method belongs to a concrete method, an abstract method, or another method. There is.

  Another feature of the present invention is that the reference method information of the first means includes ID information of a reference source class method, name information of a class method that is a reference destination of the reference source class method, and a reference That is, it includes information on the type of reference destination class indicating whether the destination class belongs to a concrete class, an interface, or an abstract class.

  According to the present invention, the following effects can be obtained.

  (1) A Java language program can be grasped on the screen as a more detailed relationship between classes and methods than a relationship between classes. Relationships between class methods can be grasped as relationships between concrete class methods excluding interfaces and abstract classes that do not generate objects.

  (2) Since the relationship can be grasped by using a concrete class / method ID as a unit, a class / method for accessing a data item of a certain class or a series of class / methods in which the data item is used is identified. It becomes possible to do.

  (3) Since it is possible to grasp the relationship of a class method for a concrete class method as a unit, in a hierarchical Java language program, the range that a certain class method has on other class methods can be specified. All classes and methods used for one transaction can be specified and displayed on the screen.

  (4) Although the conventional tool for creating a sequence diagram showing the relationship between objects cannot analyze the relationship to a concrete method prior to the relationship to the concealment method, in the tool of the present invention, The relationship to the concrete method can also be analyzed and displayed on the screen.

  With the above (1) to (4), it is possible to remarkably reduce the burden of maintenance work on a large-scale business Java language program.

  (5) By generating the design document by reverse engineering, the number of man-hours for maintaining the design document manually can be greatly reduced.

  (6) If the design document is manually maintained, a divergence between the design document and the implementation is likely to occur, but by generating by reverse engineering, there is no divergence from the implementation.

  In the present invention, a Java language program is regarded as a unit of a class method, and in particular, a relation between concrete class and method IDs involved in substantial processing in the Java language program constituting the system is expressed.

  FIG. 1-5 exemplifies the flow of processing when a Java language program is regarded as a class method.

  In this figure, the method M2 of the class C11 of the highest hierarchy refers to the method M4 of the class C21 of the next hierarchy, the method M4 of the class C21 refers to the method M5 of the class C31 of the next hierarchy, and is indicated by a dotted line below. An example having a reference relationship is shown. Similarly, an example is shown in which the method M4 of the class C11 refers to the method M1 of the class C22, and the method M1 of the class C22 refers to the method M5 of the class C31.

  The above class diagram (FIGS. 1-2) merely shows the relationship between the classes C11, C21, C22... Developers have to analyze and understand the source code.

  Here, the ID of each class is represented by C11, C21, C22..., A code that can be uniquely (uniquely) specified in the system is assigned, and each method is M1, M2, M3. Thus, a code that can be uniquely specified in each class is assigned. Therefore, all methods in the system can be uniquely specified by class ID + method ID (hereinafter referred to as class / method ID).

  Therefore, if it is possible to express the relationship between all the class method IDs that are involved in substantial processing (that is, the object is generated) in the Java language program constituting the system, the desired method is specified. Or a set of class methods related to the method.

  Hereinafter, a procedure for generating an analysis tool according to the present invention will be described.

(1) Class file generation First, a class file is generated from a Java program.

  A class file is a file generated by compiling each class constituting a Java source code program. For example, each class of the Java source code program is described as illustrated in FIG. 2A. When this class is compiled, it is described with numbers as illustrated in FIG. 2-2. In a large-scale business system, the number of classes reaches several hundred thousand, so that many class files are created.

  The class file includes a concrete file, an abstract class, and an interface file.

(2) File analysis Next, this class file is analyzed to extract four types of information. The class information shown in FIG. 3A, the method information shown in FIG. 3B, the super class information shown in FIG. 3C, and the method related information shown in FIG.

  Conventionally, there has been an attempt to extract class information and method information from a source code program, but the present invention has one feature in that method related information is further extracted.

  The class information includes concrete class, abstract class and interface class ID, class name, package name, super class name, super class package name, and class type information.

  A package is a collection of multiple classes and interfaces. A superclass is a class that is inherited, that is, a parent class, and a class that is inherited is called a subclass (child class). The class type is information that the class classifies into three types: a concrete class, an abstract class, and an interface.

  As shown in FIG. 3B, the method information includes information such as class ID, method ID, method name, argument and return value information, constructor, and method type. The method ID is an ID uniquely determined in each class ID. A constructor is a special method that is automatically called when an object is created.

  As shown in FIG. 3C, the super class information includes information indicating the relationship between the child class ID and the parent class name and the relationship between the class ID and the interface name.

  In the method related information, as shown in FIG. 3-4, in addition to the class ID and method ID, a unique key ID (an ID that uniquely identifies the record in FIG. 3-4), a reference class Name and the name of the referenced method. Reference destination class information indicating whether the reference destination class belongs to a concrete class, an interface, or an abstract class is also included.

  FIG. 3-5 shows a flow for extracting the class information, method information, super class information, and method related information from the class file.

  In step S401, one class file illustrated in FIG. Subsequently, class name information is extracted from the class item description (S402), and class type information is further extracted (S403).

In step S404, all the item values of “extends” are extracted. “extends” is a symbol that defines inheritance, for example, class A “extends B”.
The description indicates that the subclass (child class) A has inherited the superclass (parent class) B. Further, when the “extends” symbol is used for an interface, it indicates that the extended interface (child interface) inherits the interface (parent interface).

In step S405, all the implementations item values are extracted. Implementations is a symbol that defines the implementation, for example, class C components D
Describes that the class C implements the interface D, for example.

  In step S406, it is determined whether the class type of the read class file is an interface or a class. In the case of a class, the class described in the “extends” item (above D) is used as the superclass name (S407), and the item value of “implements” (above D) is used as the interface name (S408).

  On the other hand, if it is determined in step S406 that the interface is an interface, the extended item value is set as the extended interface name (S409).

  Next, in steps S410 to S419, information regarding the method is extracted. First, the method name is extracted from the class file (S412), and the type name (for example, integer type) of the return value (processing result value) and the type name of the argument (variable and parameter to be processed) are sequentially extracted (sequentially). S413, S414).

  In step S415, it is determined whether the method name is equal to the class name. If the method name is equal, it is determined that the method is a method called a constructor called when an object is generated (S416).

  If the determination in step S415 is no, it is determined whether processing logic exists in the method (S417). If processing logic exists, it is determined as a concrete method (S418), and a method that defines only the calling method without describing the processing is determined as an abstract method (S419). In this way, the method information shown in FIG. 3-2 is extracted.

  Next, method-related information is extracted in steps S420 to S427. In step S420, the method information of the reference destination described in the processing logic of the method body is searched. In step S421, it is determined whether there is an unprocessed method. If there is, the process proceeds to step S422, and the method name of the reference destination method is extracted. In step S423, the class name of the class to which the reference method belongs is extracted.

  Next, it is determined whether or not the argument of the processing logic is a register variable (S424). If the argument is a register variable, the type name of the argument (for example, an integer type) is traced back to the logic and assigned to the register variable. ) Is taken out (S425). If the determination in step S424 is no, the type names of the arguments of the reference method are sequentially extracted (S426). Further, it is determined from the operand that calls the reference destination method whether the reference destination is an interface or a class (S427).

  As described above, the present invention extracts not only class information and method information but also reference class and method information. The obtained information is organized as an XML file exemplified in FIGS. 3-6.

(3) DB input of extracted information The information extracted as described above is input to the DB. FIG. 4-5 shows a DB input flow. In step S501, the record for each class is read by the above-described XML file. In step S502, information on the class is class information illustrated in FIG. Registered in the table T100. In step S503, information about the method is registered in the method information table T200 illustrated in FIG. In step S504, the super class information and interface information of the class are registered in the super class information table T300 illustrated in FIG. In step S505, the method related information is registered in the method related information table T400 illustrated in FIG. 4-4. In this way, all the information of all tens of thousands to hundreds of thousands of classes is input to the DB (S506).

(4) Generation of inter-method related information Next, inter-method related information is created based on various information input to the DB. In the case of FIG. 1-5, the inter-method related information refers to pair information of C11m2 of the concrete class / method ID and C21m4 of the concrete class / method ID of the reference destination, and C11m2 is the reference source class. The method ID C21m4 is referred to as a referenced class method ID. Note that a concrete class / method may refer to another concrete class via an abstract class or an interface, and thus may be referred to as an associated class / method ID or an associated class / method ID.

  The pair information indicating the relationship between the methods is generated by creating an inter-method relationship information table.

  FIG. 5A shows an inter-method relation information table T900. A processing flag 901 is used in the process of creating the table T900. 0 is set when the analysis is completed, 1 is set when the object ID cannot be specified, and 2 is set when the object ID and the class method of the reference destination cannot be specified. 903 is a class ID of a concrete class (implementation class) of a reference source (relationship source), 904 is a method ID of a concrete method (implementation method) of the reference source (relationship source), and 903 and 904 refer to the reference source (relationship source) A concrete class / method ID is formed. The information 903 is the same as the class ID of the method related information table T400 (FIG. 3-4), and 904 is the same as the method ID of the table T400. Reference numeral 906 denotes a class ID of a concrete class (implementation class) of a reference destination (related destination), and reference numeral 907 denotes a method ID of a concrete method of the reference destination (related destination).

  Next, with reference to FIG. 5B, a flow for creating inter-method related information will be described.

  In step S1001, concrete methods are extracted from the method information table T200 (FIG. 3-2) one by one. In step S1002, it is determined whether or not a concrete method exists. If there is, a reference destination class name, a reference destination method name, and a reference destination package name are referenced with reference to the method related information table T400 (FIG. 3-4). Is extracted (S1003).

  In the following description, the terms “reference destination” and “relationship destination” are used as representatives, and “reference source” and “relationship source” are used as representative terms.

  In step S1004, it is determined whether or not related destination information exists. If YES, the process proceeds to step S1005.

  In step S1005, the class information table T100 is referenced, and the class ID and class type information of the related class are extracted using the extracted class name and package name as key information. In step S1006, the method information table T200 is referred to, and the method ID and method type information are extracted using the method name extracted earlier and the class ID extracted in step S1005 as key information.

  If the class type extracted in step S1005 is a concrete class, the class ID is registered as the related destination ID 906 in the table T900. If the method type extracted in step S1006 is a concrete method, the method ID is registered as the related destination method ID 907. (S1007).

  Further, the concrete method ID extracted in step S1001 is registered as the association source method ID 904 of the table T900, and the class ID of the concrete class to which the association source concrete method belongs is registered as the association source class ID 903 of the table T900 (S1007).

  Through the above processing, pair information of the concrete class / method ID of the relation source and the concrete class / method ID of the relation destination is generated.

(5) Displaying Concrete Class / Method Related Information Next, a flow for displaying the concrete class / method related information generated as described above will be described with reference to FIG.

  When a class method of a Java language program is specified and, for example, when analyzing the range of classes when the class method is modified, first, in step S1301, the class method ID is specified. . Next, related destination class / method information is sequentially extracted from the inter-method related information table T900, such as the related destination class / method of the class / method and the related destination class / method of the related destination class / method. .

  For example, in the case where the relationship between the extracted class and method is expressed as shown in FIG. 6B, for example, in step S1303, the class name, method name, and argument character string shown in FIG. Generate text data.

  Further, in step S1304, the generated text data is transferred to existing software that is displayed on the web, and is displayed on the web browser software of the user's PC, for example, in a format as shown in FIG. 6-4 (S1305).

  As described above, software for displaying text data on the web as shown in FIG. 6-4 is already known.

  FIG. 6-5 is an explanatory diagram of a large-scale business system to which the tool of the present invention is applied, in which 70 is a terminal device, 71 is a server, 72 is a DB, and 73 is a maintenance personal computer.

  Taking securities business as an example, a terminal 70 composed of hundreds to thousands of personal computers installed in each branch is connected to a server 71 of the head office through a network 74. Data such as securities and bond transactions is input from each terminal 70, processed by the server 71 at the head office, and stored in the database 72.

  On the other hand, in order to maintain the Java language program used in this securities business system, the data shown in the tables T100 to T900 are stored in the DB 72, and the program shown in each flowchart is stored in the maintenance personal computer 73. Stored. When information specifying a specific class / method is input from the maintenance personal computer 73, the relationship diagram illustrated in FIG. 6-4 is displayed on the screen.

  According to the above-described tool of the present invention, all of the large-scale business Java language programs in which the number of classes and methods reaches several hundred thousand to several million, all used for specific business processing (transactions). The concrete class / method can be extracted and displayed on the screen.

  Furthermore, by designating a predetermined concrete class method and extracting and displaying a concrete class method related thereto, it is also possible to specify a range in which the predetermined concrete class method affects.

  Therefore, it is possible to specify a class / method to access a data item and specify the transaction, database, business logic, etc. in which the data item is used. The burden of maintenance work can be significantly reduced as compared with the conventional case.

Explanatory drawing of a Java language program. Explanatory drawing which shows an example of the class diagram of a Java language program. Explanatory drawing which shows an example of the sequence diagram of a Java language program. Explanatory drawing which shows the information contained in the class in a Java language program, and its relationship. Explanatory drawing which shows the flow of a process at the time of catching a Java language program as a class method. Explanatory drawing which shows an example of a Java source code program. The figure for demonstrating compilation of a Java source code program. Explanatory drawing which shows the content of the class information of a class file. Explanatory drawing which shows the content of the method information of a class file. Explanatory drawing which shows the content of the super class information of a class file. Explanatory drawing which shows the content of the class file method related information. The flowchart which shows the flow which extracts each information from a class file. Explanatory drawing which shows the XML file obtained as a result of analyzing a class file. Explanatory drawing of a class information table. Explanatory drawing of a method information table. Explanatory drawing of a super class information table. Explanatory drawing of a method related information table. The flowchart which shows the flow which throws into the DB the information extracted from the class file. Explanatory drawing of the related information table between methods. The flowchart which shows the flow which produces the related information table between methods. The flowchart which shows the flow which displays the relationship between class methods. Explanatory drawing that displays the relationship between classes and methods. Explanatory drawing of the text data produced | generated in order to display the relationship between a class method. Explanatory drawing of the screen that displays the relationship between classes and methods. The block diagram which shows an example of the system applied from this invention tool.

Explanation of symbols

100, 300, 400: Concrete class 200: Interface 100 ', 300', 400 ': Object 10: Class information 20: Method information 30: Inter-method related information C11, C21, C22, C31, C41, C42, C43: Concrete Class M1, M2, M3, M4, M5: Concrete method T100: Class information table T200: Method information table T300: Super class information table T400: Method related information table T900: Intermethod related information table 70: Terminal 71: Server 72: Database (DB)
73: PC
74: Network

Claims (4)

First means for extracting class information, method information and reference method information from a class file of a Java language program;
Based on the class information, method information and reference method information extracted from the class file, the related source concrete class / method ID composed of the concrete class ID and the concrete method ID, and the related destination of the related source concrete class / method ID A second means for generating pair information consisting of a combination of a certain related concrete class and method ID;
A Java language program analysis tool comprising third means for designating a desired class method, extracting a series of concrete class methods related to the class method, and displaying them on a screen.   2. The class information according to claim 1, wherein the class information of the first means includes class ID information, class type information indicating whether the class belongs to a concrete class, an interface, or an abstract class, and parent and child of the class. An analysis tool characterized by containing related class information.   2. The method information according to claim 1, wherein the method information of the first means includes method ID information and method type information indicating whether the method belongs to a concrete method, an abstract method, or another method. Analysis tool.   The reference method information of the first means includes ID information of a reference source class method, name information of a class method serving as a reference destination of the reference source class method, and a reference destination class. An analysis tool characterized by including information on a class of a reference destination indicating whether it belongs to a concrete class, an interface, or an abstract class.

Images