JP4180099B2 - Recording medium recording sequence analysis program, sequence analysis apparatus, and sequence analysis method - Google Patents

Description

The present invention relates to a recording medium recording a sequence analysis program, a sequence analysis apparatus, and a sequence analysis method , and in particular, a recording medium recording a sequence analysis program for analyzing a sequence of a program described in an object-oriented language, a sequence analysis apparatus, and a sequence It relates to the analysis method .

  When system development is performed using an object-oriented language, a sequence diagram in UML (Unified Modeling Language) standardized by OMG (Object Management Group) is regarded as a document for implementation.

  This sequence diagram shows a calling relationship of methods (corresponding to functions in a procedural language) of a class group related to a predetermined function, and is usually created for each function.

  By the way, since the sequence diagram for the entire system is often in the order of hundreds or thousands, for example, there is a problem that it is difficult to check the consistency between the sequence diagrams of the methods.

  Therefore, it is possible to consolidate these sequence diagrams into a single drawing to simplify the check, but in an object-oriented language, the class is an atomic operation unit, so it is simply aggregated into one drawing. However, if class members are allowed to be edited, class-by-class editing becomes difficult.

The present invention has been made in view of the above points, and provides a recording medium, a sequence analysis apparatus, and a sequence analysis method that record a sequence analysis program capable of enhancing the listability of the entire system using an object-oriented language. The purpose is to provide.

In the present invention, in order to solve the above-mentioned problem, a sequence diagram in which a call relationship included in an instance derived from a class for each function of a program is represented as an arrow for a program described in an object-oriented language, and The computer that can access the database that stores the class diagram that shows the correspondence between the class and the methods included in the class, acquires the sequence diagram from the database, and the connection source of each arrow shown in the acquired sequence diagram The class and instance, the identifier of the sequence that includes the connection source class, and the method name are acquired, and the identifier and method name of the sequence diagram that includes the connection destination class and instance of the arrow and the connection destination class are acquired. , Consists of a column corresponding to each acquired class and a row corresponding to each arrow. For each row corresponding to each arrow, the name, identifier, and method name of the acquired connection source instance are described in the column corresponding to the connection source class of the arrow, and the column corresponding to the class to which the arrow is connected The conversion means for generating a matrix-format sequence list in which the name, identifier, and method name of the connection destination instance obtained in the above are generated, the display processing means for displaying the sequence list generated by the conversion means, and the class diagram from the database. Whether the method included in the class shown in the acquired class diagram is compared with the method whose name is listed in the column corresponding to the class in the sequence list generated by the conversion means or it determines, when there is no match, to function as a check means for performing an error display on the sequence list by the display processing means and displayed Recording medium for recording a sequence analysis program, characterized in that there is provided.

Here, the conversion means acquires the sequence diagram from the database, and acquires the class and instance of the connection source of each arrow shown in the acquired sequence diagram, the identifier of the sequence including the class of the connection source, and the method name. In addition, the class and instance of the connection destination of the arrow, the identifier of the sequence diagram including the class of the connection destination, and the method name are acquired, and it is composed of a column corresponding to each acquired class and a row corresponding to each arrow. For the line corresponding to each arrow, enter the name, identifier, and method name of the acquired connection source instance in the field corresponding to the arrow connection source class, and obtain it in the field corresponding to the arrow connection destination class. A matrix-type sequence list describing the name, identifier, and method name of the connected instance is generated. The display processing means displays the sequence list generated by the conversion means. The check means obtains a class diagram from the database, and the methods included in the class shown in the obtained class diagram and the methods whose names are listed in the columns corresponding to the classes in the sequence list generated by the transformation means Are compared to determine whether or not they match, and if they do not match, an error is displayed on the sequence list displayed by the display processing means.

In the present invention, for a program written in an object-oriented language, a sequence diagram representing an invocation relationship included in an instance derived from a class for each function of the program as an arrow, and included in a class and a class The computer that can access the database that stores the class diagram that shows the correspondence with the existing method, obtains the sequence diagram from the database, the class and instance of the connection source of each arrow shown in the acquired sequence diagram, the connection source Acquires the identifier and method name of the sequence that includes the class, and also acquires the identifier and method name of the sequence diagram that includes the connection destination class and instance, and the connection destination class, and corresponds to each acquired class. Column and a row corresponding to each arrow, corresponding to each arrow In the column corresponding to the connection source class of the arrow, the name, identifier, and method name of the acquired connection source instance are described, and the acquired connection destination instance is displayed in the column corresponding to the connection destination class of the arrow. Conversion means for generating a sequence list in a matrix format describing names, identifiers, and method names, display processing means for displaying the sequence list generated by the conversion means, a class diagram from the database, and the acquired class diagram If the method included in the indicated class is compared with the method whose name is listed in the column corresponding to the class in the sequence list generated by the conversion means to determine whether they match, and if they do not match in, since the function as the check means for performing an error display on the sequence list by the display processing means and displayed, Obuji It is possible to improve the list of sequences with the system described in transfected oriented language.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
FIG. 1 is a principle diagram illustrating the operating principle of the present invention. In this figure, a sequence analysis apparatus 2 that realizes a sequence analysis method according to the present invention reads and analyzes a plurality of sequence diagrams 1a to 1d and outputs a sequence list 3.

  The sequence analysis apparatus 2 includes a class name acquisition unit 2a, an instance name acquisition unit 2b, a method name acquisition unit 2c, a call relationship acquisition unit 2d, and a sequence list display unit 2e.

Here, the class name obtaining unit 2a obtains class names of classes constituting the program.
The instance name acquisition unit 2b acquires an instance name of an instance derived from each class.

The method name acquisition unit 2c acquires the method name of the method included in each instance.
The call relationship acquisition unit 2d acquires the call relationship of each method.

  The sequence list display means 2e displays a list of information acquired by the class name acquisition means 2a, instance name acquisition means 2b, and method name acquisition means 2c in a table format, and is based on the information acquired by the call relationship acquisition means 2d. Display the sequence list that shows the call relationship of each method.

Next, the operation of the above principle diagram will be described.
As a sequence diagram to be processed, a sequence diagram comprising a class A, a class B, and a class C has a structure in which the class A calls the method A of the class B and the class B calls the method B and the method C of the class C Assume that 1a and the other sequence diagrams 1b-1d are selected.

The class name acquisition unit 2a acquires class names (for example, class A to class C) included in these sequence diagrams 1a to 1d.
The instance name acquisition unit 2b acquires the instance names (for example, instance A to instance B (not shown)) included in the sequence diagrams 1a to 1d.

The method name acquisition means 2c acquires the method name (for example, method A to method C) included in the sequence diagrams 1a to 1d.
The call relationship acquisition means 2d acquires the call relationship of methods included in the sequence diagrams 1a to 1d (such as “class A calls method A of class B”).

  The sequence list display means 2e is obtained by the class name acquisition means 2a, the instance name acquisition means 2b, and the class name, instance name, and method name acquired by the method name acquisition means 2c, and the call relationship acquisition means 2d. The sequence list 3 is generated on the basis of the called relationship and displayed.

  Here, in the sequence list 3, all classes included in the sequence diagrams 1a to 1d are listed, and an instance and a method of each class are shown as attributes. In addition, calling relationships between methods are indicated by arrows.

  For example, class B has method A (mA), and this method A is called from class A. The class C has a method B (mB) and a method C (mC), and these methods are called from an instance A (iA) of the class B. In this figure, only the portion corresponding to the sequence diagram 1a is shown, but the contents related to the classes corresponding to the sequence diagrams 1b to 1d are also actually displayed.

  By the way, the display contents of the sequence list 3 displayed as described above are only allowed to be edited in units of classes (for example, moving, copying, and deleting classes). However, it is prohibited to move only method A of class B. Therefore, it is possible to change the display mode according to the purpose and eliminate the complexity of operations (such as moving instances and methods individually) by allowing only changes in units of classes. It becomes possible to do.

As described above, according to the present invention, since one sequence list is generated from a plurality of sequence diagrams, the listability of the entire system can be improved.
In addition, regarding the change of the display content, only the change in the class unit is permitted, so that it is possible to eliminate the complexity of the operation as described above.

Next, a configuration example of the embodiment of the present invention will be described.
FIG. 2 is a block diagram showing a configuration example of a sequence analysis apparatus that implements the sequence analysis method according to the present invention.

  As shown in this figure, a sequence analysis apparatus 10 includes a CPU (Central Processing Unit) 10a, a ROM (Read Only Memory) 10b, a RAM (Random Access Memory) 10c, an HDD (Hard Disk Drive) 10d, and a GB (Graphics Board). 10e, I / F (Interface) 10f, and a bus 10g, and a display device 11 and an input device 12 are connected to the outside.

Here, the CPU 10a controls each part of the apparatus according to a program stored in the HDD 10d and executes various arithmetic processes.
The ROM 10b stores basic programs and data executed by the CPU 10a.

The RAM 10c temporarily stores programs to be executed by the CPU 10a and data being calculated.
The HDD 10d stores various programs executed by the CPU 10a, sequence diagrams to be analyzed, and sequence list data as analysis results.

The GB 10e converts image data drawn in accordance with a drawing command supplied from the CPU 10a into a video signal and outputs it.
The I / F 10 f converts the representation format of the data supplied from the input device 12 so as to conform to the internal format of the sequence analysis device 10.

The display device 11 is composed of, for example, a CRT (Cathode Ray Tube) monitor, and displays a video signal output from the GB 10e.
The input device 12 is configured by an input device such as a mouse or a keyboard, for example.

  FIG. 3 is a diagram for explaining functional blocks realized when an application program stored in the HDD 10d of the sequence analysis apparatus 10 shown in FIG. 2 is started.

In this figure, the database 20 is constituted by the HDD 10d, and stores a sequence diagram and a class diagram (details will be described later) to be processed.
The conversion unit 21 is realized by the CPU 10a and the like, and executes processing for acquiring necessary items from the sequence diagram stored in the database 20 and converting it into a sequence list.

The database 22 is configured by the HDD 10d and stores a sequence list generated by the conversion unit 21.
The display processing unit 23 is realized by the CPU 10 a and other functions, performs a predetermined process on the sequence list stored in the database 22, and then supplies the sequence list to the display unit 26.

The inverse conversion unit 24 converts the designated portion of the sequence list stored in the database 22 into a sequence diagram and supplies the sequence diagram to the display processing unit 23.
The check unit 25 checks whether or not the contents of the sequence list stored in the database 22 are free from defects, and supplies the check result to the display processing unit 23.

The display unit 26 includes the GB 10 e and the display device 11, and displays and outputs information output from the display processing unit 23.
The input unit 27 includes an I / F 10f and the input device 12, and supplies information corresponding to a user operation to the display processing unit 23.

Next, the operation of the above embodiment will be described.
Assume that the sequence diagrams 40 to 43 shown in FIG. 4 and the class diagrams 50 to 53 shown in FIG. Here, the sequence diagram is a diagram illustrating a calling relationship of methods included in an instance derived from a class, and is a diagram generated for each function. In the example of the sequence diagram 40 shown in FIG. 4, the controller class 40a, the pencil instance 40b of the product class, and the A warehouse instance 40c of the inventory class are displayed. As indicated by the arrow, the controller class 40a calls the order receiving method of the pencil instance 40b. The pencil instance 40b calls the get quantity method and the get inventory method of the A warehouse instance 40c. Further, the pencil instance 40b calls a calc quantity method possessed by the pencil instance 40b itself. The numerical value displayed on the left side of each method indicates the hierarchy of method invocation relationships, and details thereof will be described later.

  FIG. 5 is a class diagram showing the relationship between classes and methods included in the classes. This example includes class diagrams 50 to 53, and the contents of the class diagram 50 to be processed are illustrated. In this example, a controller class 50a, a product class 50b, and an inventory class 50c are displayed, and the product class 50b has an order receiving method and a calc quantity method. The inventory class 50c has a get quantity method and a get inventory method. In this example, an example in which the class diagram is divided into a plurality of parts has been described, but they may be displayed together.

  In order to perform analysis processing on such target data, when the application program for analysis is activated by operating the input device 12, the CPU 10a reads and executes the corresponding program from the HDD 10d. As a result, a screen 60 of the analysis program as shown in FIG.

  In this display example, buttons 61 to 66 are displayed under the title “sequence analysis”, and a display area 67 in which analysis target data and analysis result data are arranged is displayed below the buttons 61 to 66.

  FIG. 7 is a diagram illustrating an example of a pull-down menu displayed when the buttons 61 to 66 illustrated in FIG. 6 are operated. The button 66 is not displayed in FIG. 7 because the command is directly executed without displaying the pull-down menu.

  As shown in FIG. 7, when the button 61 is operated, the reading 61a selected when reading the file to be analyzed and the printing selected when printing the contents displayed in the display area 67 are performed. 61b are displayed as menu items.

  When the button 62 is operated, a move 62a selected when moving a predetermined class in the sequence list displayed in the display area 67, a delete 62b selected when deleting a specified class, and a specified Display / non-display 62c selected when displaying or non-displaying the selected class is displayed as a menu item.

  When the button 63 is operated, a conversion 63a selected when converting the read sequence diagram into the sequence list and an inverse conversion 63b selected when converting a part of the sequence list back into the sequence diagram are displayed. Displayed as a menu item.

  When the button 64 is operated, the arrow line 64a selected when the arrow line indicating the method call relation is additionally displayed on the sequence list displayed in the display area 67, and similar or identical methods are aggregated. The method aggregation 64b selected at the time of display and the details / omission 64c selected at the time of omitting or adding the display item of the class are displayed as menu items.

  When the button 65 is operated, the mutual check 65a selected when the mutual contents of the sequence list and the class diagram are checked, and the suitability of the sequence numbers assigned to the methods of the sequence list are checked. The selected sequence number 65b, the entrance 65c selected when checking the method of the entrance, and the parameter 65d selected when checking the parameter of the method are displayed as menu items.

  Next, on the screen 60 shown in FIG. 6, when the button 61 is operated and the reading 61a which is a menu item is selected, and the sequence diagrams 40 to 43 shown in FIG. 21 reads the sequence diagrams 40 to 43 from the database 20. As a result, sequence diagrams 40 to 43 are displayed in the display area 67 of the screen 60 as shown in FIG.

  Next, when the button 63 is operated and the conversion 63a is selected, the conversion unit 21 executes processing for converting the sequence diagram into a sequence list. An example of this process will be described with reference to FIG. When the flowchart shown in FIG. 8 is started, the following steps are executed.

Step S10:
The conversion unit 21 reads from the database 20 the sequence diagram designated by selecting the reading 61a.

Step S11:
The conversion unit 21 proceeds to step S12 when the button 63 is operated and the conversion 63a is selected, and the same process is repeated otherwise.

Step S12:
The conversion unit 21 acquires one arrow line data from the sequence diagram. That is, the data of the class of the connection source and connection destination of the arrow line is acquired from the database 20.

Step S13:
The conversion unit 21 proceeds to step S14 when the arrow line data has been successfully acquired, that is, when unprocessed arrow line data exists, and otherwise processes all the arrow lines to be processed. The process ends when it is finished.

Step S14:
The conversion unit 21 analyzes the connection source information of the arrow line. That is, the conversion unit 21 analyzes the information of the connection source indicated by the arrow, and connects the connection source class, the connection source instance, the sequence diagram ID, the instance name, the generated instance, and the sequence number. , Method name, parameter, return value, connection destination class, connection destination instance.

  Here, the connection source class and the connection source instance indicate a connection source class and an instance indicated by an arrow. The sequence diagram ID indicates the ID (Identification) of the sequence diagram including the connection source and connection destination classes of the arrow. The instance name indicates the name of the connection source instance, and the generated instance is an identification code automatically assigned by the conversion unit 21. Sequence No. Is a serial number assigned to each method reflecting the class hierarchy. The method name indicates the name of the method, and the parameter and return value indicate the parameter (argument) and return value of the method. The connection destination class and the connection destination instance indicate a connection destination class and its instance.

Step S15:
The conversion unit 21 analyzes the information of the connection destination of the arrow line. That is, the conversion unit 21 analyzes the connection destination information indicated by the arrow, and connects the connection source class, the connection source instance, the sequence diagram ID, the instance name, the generated instance, and the sequence number. , Method name, parameter, return value, connection destination class, connection destination instance. Each information is the same as described above.

Step S16:
Write the connection source and connection destination information of the acquired arrow in the sequence list. And it returns to step S12 and repeats the same process.

  The sequence list generated as a result of the processing described above is displayed in the display area 67 of the screen 60 as shown in FIG. In this display example, only the portion related to the controller class 50a in the sequence list is displayed. When the slider 70 or the buttons 68 and 69 are operated, the product class 50 b and the inventory class 50 c can be displayed in the display area 67.

  Since the sequence list for all classes cannot be displayed at the same time due to space limitations, the details of the portions for each class in the sequence list will be described individually.

  FIG. 10 is an example of a sequence list regarding the controller class 50a. In this example, the connection source class, connection source instance, sequence diagram ID, instance name, generation instance, sequence number, etc. , Method name, parameter, return value, connection destination class, and connection destination instance are displayed. Each row stores data corresponding to each arrow in the sequence diagram shown in FIG. For example, in the example of FIG. 10, data corresponding to the order receiving method in the sequence diagram shown in FIG. 4 is stored. Specifically, the sequence diagram ID of the order receiving method is “Patten”, the generated instance is “Patten01”, the sequence number is “1”, the method name is “order received”, and the connection destination class is It is shown that it is a “product”.

  FIG. 11 is an example of a sequence list regarding the product class 50b. In this example, the item on the first line is information corresponding to the order receiving method shown on the first line in FIG. 10, and “controller” is selected as the connection source class, and the sequence diagram ID, instance name, and generated instance. , Sequence No. In addition, “Pattern”, “Pencil”, “Pattern02”, “1”, and “Order” are stored as method names.

Therefore, by referring to the item in the first row of FIGS. 10 and 11, information regarding the connection source and connection destination of the arrow line in the original sequence diagram can be acquired.
FIG. 12 is an example of a sequence list regarding the inventory class 50c. In this example, information on the method get quantity and the connection destination of the get stock shown in FIG. 11 is stored. Specifically, the information corresponding to the method get stock includes a connection source class, a connection source instance, a sequence diagram ID, an instance name, a generation instance, a sequence number, For each of the method names, “product”, “pencil”, “patten”, “A warehouse”, “patten03”, “1.1”, and “get quantity” are stored.

  As described above, according to the present embodiment, since one sequence list is generated and displayed from a plurality of sequence diagrams, the structure of the entire system can be referred to at a glance. It becomes possible.

  In addition, by converting the sequence diagram into a sequence list, it becomes possible to store it in the relational database. As described below, the functions of the relational database are used to easily search and edit items. It becomes possible.

  FIG. 13 is a diagram illustrating a procedure for searching for a predetermined character string included in the sequence list. When searching for a character string, first, the user operates the button 66, inputs a character string to be searched from a character string input screen (not shown) displayed as a result, and starts the search. If it does, the display process part 23 will acquire the character string input from the input part 27, and will search the applicable character string contained in the sequence list. When a corresponding character string is detected, the corresponding part of the sequence list is highlighted. FIG. 13 shows a search result when “order” is input as a character string to be searched. In this example, the method name “order received” is highlighted, and an item corresponding to the input character string can be found immediately.

Next, processing executed when the method aggregation 64b is selected after the button 64 is operated will be described with reference to FIG.
When the method aggregation 64b is selected, the display processing unit 23 rearranges the methods displayed in the sequence list so that the methods having the same or similar names are close to each other, and then displays the display unit 26. To update the display.

  As a result, the sequence list regarding the product class 50b is rearranged so that the method get quantity and the method get inventory are continuous as shown in FIG. By arranging the same or similar methods close to each other in this way, it is easy to check the consistency and consistency of how to call the same method and how to use it, which was conventionally scattered in multiple sequence diagrams. It becomes possible to do. In addition to arranging the same or similar methods close to each other, for example, by rearranging them in alphabetical order or in alphabetical order, similar methods are displayed close together, so you can easily find errors in method names, etc. It becomes possible.

Next, with reference to FIG. 15, processing when the button 64 details / omission 64c is selected will be described.
When the detail / omission 64c is selected, the display processing unit 23 displays a screen (not shown) for selecting a display item on the display unit 26 and receives a selection of the display item. Specifically, the connection source class, connection source instance, sequence diagram ID, instance name, generated instance, sequence No. , Display a screen for inputting the presence / absence of display for each of the method name, parameter, return value, connection destination class, and connection destination instance, and receive input of necessary items.

  Subsequently, the display processing unit 23 selects only the necessary items previously specified from the sequence list and displays them on the display unit 26. For example, when only the instance name and the method name are selected as necessary display items, the information shown in the display area 67 of FIG. 15 is displayed.

  In this example, only the instance name and method name of each class are displayed. For example, it can be seen that the pencil instance is calling the get quantity method of the instance A warehouse of the inventory class. The calc quantity method calls the calc quantity itself of the product class pencil instance.

In this way, by excluding necessary items from the screen, it is possible to improve the overall listability of the sequence list and improve the search speed.
Next, an operation when the button 64 is operated and the arrow line 64a is selected on the screen 60 shown in FIG. 15 will be described.

  When the button 64 is operated and the arrow line 64a is selected, the display processing unit 23 displays an arrow line corresponding to the calling relationship of each method when the arrow line is not currently displayed on the sequence list. To do. When the arrow line is in the display state, it is erased from the screen to be in a non-display state. In the present example, as shown in FIG. 15, since the arrow is in a non-display state, the display processing unit 23 puts the arrow in the display state. As a result, an arrow line is displayed as shown in FIG.

  In this way, by displaying or hiding the arrow line as necessary, it is possible to increase the visibility of other information or to improve the visibility of the method call relationship by the arrow line. It becomes possible to select arbitrarily.

Next, in FIG. 16, the operation when the movement 62a is selected after the button 62 is operated will be described.
When the movement 62a is selected, an arbitrary class can be moved to an arbitrary position. Movement is permitted only in class units. For example, in FIG. 16, if a controller class is selected as an object to be moved (for example, clicked with the mouse) and then an operation is performed to move the controller class to the right side of the inventory class, the display processing unit 23 displays the sequence list. The rearrangement process is performed so that the controller class on the table is arranged on the right side of the inventory class, and the rearranged data is supplied to the display unit 26 and displayed.

As a result, as shown in the display area 67 of FIG. 17, the controller class is displayed after the inventory class, and the direction of the arrow is appropriately corrected and displayed.
As described above, since the position of the class can be freely changed, it is possible to know the reference relationship of the method more easily by rearranging the class according to the purpose.

  In the above example, the case of moving a class has been described, but it is also possible to delete a class, display or hide a class, or perform a process of copying. For example, when deleting a class, the relationship with the other class having the calling relationship disappears, so that the point is deleted. The same applies to the non-display state. Thus, by permitting editing of the displayed contents in units of classes, it is possible to change the display mode according to the purpose and improve workability.

  Next, processing executed when an arbitrary class is selected and then the button 63 is operated to select the inverse transformation 63b will be described with reference to FIG. When this flowchart is started, the following steps are executed.

Step S30:
The inverse conversion unit 24 identifies the specified class according to the information acquired from the input unit 27 via the display processing unit 23. For example, when information specifying a plurality of classes is input from the input unit 27, the inverse conversion unit 24 identifies the specified classes.

Step S31:
The inverse conversion unit 24 acquires data corresponding to one arrow line in the sequence diagram that is included in the specified class. Specifically, the class, instance, and method name of the connection source and connection destination of the arrow line are acquired.

Step S32:
The inverse conversion unit 24 determines whether or not the data corresponding to the arrow line has been successfully acquired. If the acquisition has succeeded, the process proceeds to step S33. Otherwise, the process ends.

Step S33:
The inverse conversion unit 24 arranges the arrow line data of the sequence diagram (the data acquired in step S31 for each class) from the data corresponding to one arrow line acquired in step S31 (connection source and connection destination data). Data).

Step S34:
The inverse conversion unit 24 writes the arrow line data generated in step S33 to the corresponding part of the sequence diagram, returns to step S31, and repeats the same processing as described above.

  According to the above processing, it is possible to specify a desired class group on the sequence list and create a sequence diagram corresponding to the specified class group. It can be created easily.

Next, a process executed when the button 65 is operated and the mutual check 65a is selected will be described.
When the button 65 is operated and the mutual check 65a is selected, the check unit 25 executes the flowchart shown in FIG.

Step S50:
The check unit 25 reads the class diagram shown in FIG.
Step S51:
The check unit 25 creates a method list that is a list of methods included in the corresponding class in the sequence list (the class corresponding to the class diagram read in step S50).

Step S52:
The check unit 25 determines whether or not the acquired class is the last line of the sequence list. If it is the last line, the check unit 25 ends the process, and otherwise proceeds to step S53.

Step S53:
The check unit 25 compares the methods included in the class diagram with the methods included in the method list.

Step S54:
The check unit 25 determines whether or not the two match by comparing in step S53. If both match, the check unit 25 returns to step S50 as normal and repeats the same processing, otherwise. Proceed to step S55.

Step S55:
The check unit 25 highlights the entire corresponding line on the sequence list.
Step S56:
The check unit 25 displays an error message indicating that a method that does not match the class diagram exists.

  By the way, the method on the sequence diagram needs to be defined as a method of the class on the class diagram, but according to the above processing, is the method on the sequence diagram defined as a method on the class diagram? It is possible to automatically determine whether or not.

  In this example, it is checked whether the method called from the class included in the class diagram matches the method on the sequence diagram, but the present invention aims to check the mismatch between the class diagram and the sequence diagram. Therefore, although not shown in the drawings, the present invention includes a method for checking a mismatch between a class on a class diagram and a class on a sequence diagram.

  Next, processing executed when the button 65 is operated and the sequence number 65b is selected will be described with reference to FIG. When this flowchart is started, the following steps are executed.

Step S70:
The check unit 25 reads a predetermined one line of the sequence list.
Step S71:
The check unit 25 proceeds to step S72 if the reading is successful, that is, if there is an unprocessed line, and ends the process assuming that there is no processing target otherwise.

Step S72:
The check unit 25 indicates that the sequence number of the read line is 1. Whether the hierarchy is the top (entrance) method or not. 1. If so, the process proceeds to step S73. Otherwise, the process proceeds to step S76.

Step S73:
The check unit 25 acquires the information stored in the “connection source class” and “connection source instance” columns of the connection source indicated by the arrow.

Step S74:
The check unit 25 determines whether or not both of these columns are empty. If they are empty, the check unit 25 returns to step S70 as normal and repeats the same processing. Otherwise, the process returns to step S75. move on.

Step S75:
The check unit 25 has a sequence number of 1. The class is usually an entry class, and if the connection source class and connection source instance of the class are empty, if some information is stored, the line is reversed as an error, and the error Displays a message indicating that has occurred.

Step S76:
The check unit 25 acquires the relationship with the sequence number on one line.
Step S77:
The check unit 25 determines whether or not the sequence number on the first row belongs to a class on one layer. If the sequence number belongs to a class on one layer, the process proceeds to step S79. Advances to step S78. Here, whether or not it is one layer higher is determined by referring to the number of dots “.” Included in the sequence number. That is, the greater the number of dots, the deeper the sequence.

Step S78:
The check unit 25 determines whether or not the connection source class and connection source instance on the first row match the connection source class and connection source instance of the row, and if they match, it is normal as a sequence in the same hierarchy. Therefore, the process returns to step S70 and the same process is repeated, otherwise the process proceeds to step S81.

Step S79:
The check unit 25 determines whether or not the connection destination class and the connection destination instance on the first row match the connection source class and the connection source instance of the row.

Step S80:
The check unit 25 determines whether or not both of the steps S79 match, and if both match, the sequence on the first row is a sequence on the first layer, and the sequence on the first row is one sequence lower. If this is the case, the process returns to step S70 and the same process is repeated, assuming that it is in a normal state. Otherwise, the process proceeds to step S81.

Step S81:
The check unit 25 reverses the line and displays a message indicating that the line is not normal, assuming that the one line and the sequence of the line are not normal, and returns to step S70 to repeat the same processing.

According to the above processing, it is possible to automatically check whether the sequence number assignment method is normal.
Next, processing executed when the button 65 is operated and the entrance 65c is selected will be described with reference to FIG. When this flowchart is started, the following processing is executed.

Step S100:
The check unit 25 reads a predetermined one line of the sequence list.
Step S101:
The check unit 25 proceeds to step S102 if it has been successfully read, that is, if an unprocessed line remains, and otherwise ends the process assuming that there is no processing target.

Step S102:
The check unit 25 indicates that the sequence number of the read line is 1. It is determined whether or not If YES, the process proceeds to step S103. Otherwise, the process returns to step S100 and the same process is repeated.

Step S103:
The check unit 25 acquires the information stored in the “connection source class” and “connection source instance” columns of the connection source indicated by the arrow.

Step S104:
The check unit 25 determines whether or not both of these columns are empty. If they are empty, the process proceeds to step S105. Otherwise, the process ends.

Step S105:
The check unit 25 has a sequence number of 1. The class is usually an entry class, and if the connection source class and connection source instance of the class are empty, if some information is stored, the line is reversed as an error, and the error After displaying a message indicating that the error occurred, the process is terminated.

According to the above processing, it is possible to check whether or not the entrance method is normal.
Next, processing executed when the button 65 is operated and the parameter 65d is selected will be described with reference to FIG. This process is a process for determining whether or not the method parameters and return values described in the sequence list are normal. When this flowchart is started, the following steps are executed.

Step S120:
The check unit 25 reads a predetermined one line of the sequence list.
Step S121:
The check unit 25 determines whether reading is successful. That is, if there is no unprocessed line in the sequence list, the process is terminated, and otherwise, the process proceeds to step S122.

Step S122:
The check unit 25 acquires a connection source parameter and a return value of the predetermined line read in step S120.

Step S123:
The check unit 25 acquires the connection destination parameter and return value of the predetermined line read in step S120.

Step S124:
The check unit 25 compares the connection source and connection destination parameters and the return value type and number.

Step S125:
As a result of the comparison in step S124, the check unit 25 determines whether or not they match. If they match, the check unit 25 returns to step S120 as normal, and repeats the same processing. The process proceeds to S126.

Step S126:
The check unit 25 reverses the current line, displays a message indicating that the parameter and the return value are not normal, returns to step S120, and repeats the same processing.

According to the above processing, it is possible to automatically detect a row having an error in which the connection source and connection destination parameters included in the sequence list do not match.
In the above embodiment, the sequence list is generated from the sequence diagram. However, for example, it is also possible to generate the sequence list from the source file. In that case, the source file is decomposed for each class, the instances derived from each class and the methods included in each instance are identified, and the method call relationship is obtained by analyzing the text by text analysis. Can do. Then, based on the information thus obtained, a method list can be generated by performing the same processing as described above.

Moreover, the display of the sequence list shown above is an example, and the present invention is not limited only to such a case.
Finally, the above processing functions can be realized by a computer. In this case, the processing contents of the functions that the sequence analysis apparatus should have are described in a program recorded on a computer-readable recording medium, and the above processing is realized by the computer by executing this program on the computer. Is done. Examples of the computer-readable recording medium include a magnetic recording device and a semiconductor memory. In the case of distribution to the market, a program is stored and distributed on a portable recording medium such as a CD-ROM (Compact Disk Read Only Memory) or a floppy disk (registered trademark), or a computer connected via a network. It can also be stored in a storage device and transferred to another computer via a network. When executed by a computer, the program is stored in a hard disk device or the like in the computer, loaded into the main memory and executed.

It is a principle figure explaining the principle of operation of the present invention. It is a block diagram which shows the structural example of embodiment of this invention. It is a figure explaining the functional block mounted when the application program stored in HDD of the sequence analyzer shown in FIG. 2 is started. It is an example of the sequence diagram used as a process target. It is an example of the class diagram used as a process target. It is an example of the screen displayed when the application program for analysis concerning this invention is started. It is a figure which shows an example of the pull-down menu displayed when the button shown in FIG. 6 is operated. It is a flowchart explaining an example of the process which converts a sequence diagram into a sequence list performed when the button 63 is operated and the conversion 63a is selected. It is a display example of the sequence list generated by the conversion process. It is an example of the sequence list regarding a controller class. It is an example of the sequence list regarding a product class. It is an example of the sequence table regarding an inventory class. It is a screen showing a result of a search performed by operating a button 66 and inputting a character string. It is a display example which shows the result of a method aggregation process. It is a display example which shows the result of a method omission process. It is a display example which shows the result of a class movement process. It is a display example which shows the result of an arrow line non-display process. It is a flowchart explaining an example of the process which reversely converts a sequence table into a sequence diagram. It is a flowchart explaining an example of a comparison process with a class diagram and a sequence list. It is a flowchart explaining an example of a sequence number check process. It is a flowchart explaining an example of an entrance method check process. It is a flowchart explaining an example of a parameter check process.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1a-1d Sequence diagram 2 Sequence analyzer 2a Class name acquisition means 2b Instance name acquisition means 2c Method name acquisition means 2d Call relation acquisition means 2e Sequence list display means 3 Sequence list 10 Sequence analysis apparatus 10a CPU
10b ROM
10c RAM
10d HDD
10e GB
10f I / F
10 g Bus 11 Display device 12 Input device 20 Database 21 Conversion unit 22 Database 23 Display processing unit 24 Inverse conversion unit 25 Check unit 26 Display unit 27 Input unit

Claims (3)

For a program written in an object-oriented language, a sequence diagram showing the calling relationship included in an instance derived from the class for each function of the program as an arrow, and a method included in the class and the class A computer that can access a database that stores a class diagram showing the correspondence between
The sequence diagram is acquired from the database, and the connection source class and instance of each arrow represented in the acquired sequence diagram, the identifier of the sequence including the connection source class, and the method name are acquired, and the arrow The connection destination class and instance, the identifier of the sequence diagram that includes the connection destination class, and the method name are acquired, and it consists of a column corresponding to each acquired class and a row corresponding to each arrow. For the corresponding line, write the name, identifier, and method name of the connection source instance acquired in the column corresponding to the class of the connection source of the arrow, and acquire it in the column corresponding to the class of the connection destination of the arrow A conversion means for generating a matrix-type sequence list in which the name, identifier, and method name of a connection destination instance are described;
Display processing means for displaying the sequence list generated by the conversion means;
The class diagram is acquired from the database, and a name is described in a column corresponding to the class in the sequence list generated by the method included in the class shown in the acquired class diagram and the conversion unit. A check means for displaying an error on the sequence list displayed by the display processing means if they do not match,
A recording medium on which is recorded a sequence analysis program characterized by functioning as For a program written in an object-oriented language, a sequence diagram showing the calling relationship included in an instance derived from the class for each function of the program as an arrow, and a method included in the class and the class A database that stores a class diagram showing the correspondence between
The sequence diagram is acquired from the database, and the connection source class and instance of each arrow represented in the acquired sequence diagram, the identifier of the sequence including the connection source class, and the method name are acquired, and the arrow The connection destination class and instance, the identifier of the sequence diagram that includes the connection destination class, and the method name are acquired, and it consists of a column corresponding to each acquired class and a row corresponding to each arrow. For the corresponding line, write the name, identifier, and method name of the connection source instance acquired in the column corresponding to the class of the connection source of the arrow, and acquire it in the column corresponding to the class of the connection destination of the arrow A conversion means for generating a matrix-type sequence list in which the name, identifier, and method name of a connection destination instance are described;
Display processing means for displaying the sequence list generated by the conversion means;
The class diagram is acquired from the database, and a name is described in a column corresponding to the class in the sequence list generated by the method included in the class shown in the acquired class diagram and the conversion unit. A check means for displaying an error on the sequence list displayed by the display processing means if they do not match,
A sequence analysis apparatus comprising: For a program written in an object-oriented language, a sequence diagram showing the calling relationship included in an instance derived from the class for each function of the program as an arrow, and a method included in the class and the class A computer that can access a database that stores a class diagram showing the correspondence between
The sequence diagram is acquired from the database, and the connection source class and instance of each arrow represented in the acquired sequence diagram, the identifier of the sequence including the connection source class, and the method name are acquired, and the arrow The connection destination class and instance, the identifier of the sequence diagram that includes the connection destination class, and the method name are acquired, and it consists of a column corresponding to each acquired class and a row corresponding to each arrow. For the corresponding line, write the name, identifier, and method name of the connection source instance acquired in the column corresponding to the class of the connection source of the arrow, and acquire it in the column corresponding to the class of the connection destination of the arrow A conversion step for generating a matrix-type sequence list that describes the name, identifier, and method name of the instance to connect to
A display processing step for displaying the sequence list generated by the conversion means;
The class diagram is acquired from the database, and a name is described in a column corresponding to the class in the sequence list generated by the method included in the class shown in the acquired class diagram and the conversion unit. A check step of displaying an error on the sequence list displayed by the display processing means when the method is compared to determine whether the method matches,
The sequence analysis method characterized by performing this.

Images