JPH086791A - Universal class construction drawing generating method - Google Patents

Abstract

PURPOSE:To generate a class construction drawing with high universal applicability considering object-oriented succession and making into a capsule. CONSTITUTION:After plural class construction drawings are inputted and desired adaptability factors for them are inputted, a rate of coincidence is calculated by performing matching among the semantic data of plural inputted class construction drawings, and the class construction drawing can be generated and outputted based on the data which satisfies the adaptability factor.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a general-purpose class structure diagram generation method, and more particularly, in an object-oriented analysis / design support system that supports system development using object-oriented technology, a class structure of systems similar to the business field. The present invention relates to a general-purpose class structure diagram generation method suitable for extracting the same data from a diagram and generating a general-purpose class configuration diagram for the business field.

[0002]

2. Description of the Related Art In recent years, object-oriented technology has attracted attention as a new system development technology capable of improving system maintainability and reusability.

In the analysis / design of a system using the object-oriented technology, a "thing" existing in the world is used as an object, and a class structure diagram defining a relationship between the objects (classes or instances) is created. The class structure diagram is the most central diagram in object-oriented analysis / design.

The general-purpose class structure diagram is a class structure diagram in which the same data is extracted from a class structure diagram of a system similar to a business field in consideration of inheritance relation and encapsulation which are object-oriented features.

Therefore, in the case of newly constructing the same system as the business field in which the general-purpose class structure diagram was created, the analysis / design of the system can be performed early by modifying or changing the created general-purpose class structure diagram, and the development period Can be reduced and reliability can be improved.

Conventionally, this kind of general-purpose class structure diagram has been created by a method of simply comparing the semantic data of the class structure diagram and outputting the matched data as a general-purpose class structure diagram.

FIG. 14 is a flow chart for explaining a conventional general-purpose class structure diagram generation method. First, an operator is made to select a plurality of class structure diagrams to be objects of the general-purpose class structure diagram, and the selected classes are selected. The structure diagram is set as input data in the general class structure diagram generation process (step 201), and then the data comparison between the semantic data of the class structure diagram is performed. If the comparison result is the same data, the general class structure diagram Is generated (step 202), and the generated general-purpose class structure diagram is output to the display unit (step 203).

[0008]

However, the conventional class structure diagram generation method described above does not consider the object-oriented features of "inheritance" and "encapsulation". There is a problem that the structure diagram cannot be generated.

Further, since the completely matched semantic data is generated as a class structure diagram, there is a problem that the usage rate of the general-purpose class structure diagram is reduced when the number of matched semantic data is small.

An object of the present invention is to provide a general-purpose class structure diagram generation method capable of creating a highly versatile class structure diagram in consideration of object-oriented inheritance and encapsulation.

[0011]

In order to achieve the above-mentioned object, the present invention basically inputs a plurality of class structure diagrams and, after inputting an arbitrary matching rate for the class structure diagrams, Matching between semantic data of a plurality of input class structure diagrams is performed to calculate a matching rate, and semantic data satisfying the matching rate is extracted based on the matching rate to generate a class structure diagram between the semantic data. It is characterized by doing.

[0012]

According to the present invention, first, an operator is made to input a plurality of class structure diagrams for which general-purpose class structure diagrams are to be generated, and at the same time, an arbitrary matching rate for the class structure diagrams is inputted. Thereafter, matching is performed between the semantic data of the input plurality of class structure diagrams to calculate the matching rate, and the semantic data satisfying the matching rate is extracted based on the matching rate, and the class structure between the semantic data is extracted. Generate the diagram.

Thus, it is possible to generate a general-purpose class structure diagram that is appropriate and has high versatility regardless of the configuration of the inheritance relationship of each class structure diagram.

[0014]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail below with reference to the drawings.

FIG. 1 illustrates the present invention as an object-oriented analysis /
It is a system configuration block diagram which shows one Example at the time of applying to a design system.

In FIG. 1, 101 is a display unit for displaying a class structure diagram and a general-purpose class structure diagram, 102 is an input unit for inputting a conformance ratio of the general-purpose class structure diagram, and 103 is a common part from the class structure diagrams of a plurality of systems. A processing unit for extracting and generating a general class structure diagram; 104 a class structure diagram storage unit for storing a plurality of class structure diagrams and a general class structure diagram;
Reference numeral 105 denotes a matching rate storage unit that stores the matching rate of the general-purpose class structure diagram.

FIG. 2 is a diagram showing an example of a class structure diagram which is input data of the embodiment. FIG. 2A is a class structure diagram A410 and FIG. 2B is a class structure diagram B430.

Class structure diagram A410 shows class "person" 4
11, "Employees" 414, "Banks" 417 and the relationships between those classes.

The class "person" 411 has an attribute "name" 4
12, has "address" 413. Class "Employee" 414
Has "Title" 415 as attribute and "Payroll" 4 as method
Have 16.

The class "bank" 417 has the attribute "name"
418, has "employment" 419 in the method. class"
The relationship between the person “411” and the “employee” 414 is a succession relationship “a type” 420.

Class "employee" 414 and "bank" 417
Is related to "hire" 421, which is a many-to-one relationship.

Similarly, the class structure diagram B430 has classes "person" 431, "employee" 433, "post office" 437.
And the relationships between those classes.

The class "person" 431 has an attribute "name" 4
Have 32. Class "employee" 433 has attributes "address" 434, "post" 435, and method "payroll"
Has 436.

The class "Post Office" 437 has "Name" 438 as an attribute and "Employment" 439 as a method. The relationship between the class “person” 431 and the “employee” 433 is a succession relationship “a type” 440.

The relationship between the class "employee" 433 and the "post office" 437 is a many-to-one relationship "hire" 441.

4 to 7 show the class structure diagram A4 of FIG.
01 and the class structure diagram B413 to the class structure diagram storage unit 1
It is a figure which shows the table format of the meaning data stored in 04. There are roughly two types of the table 510, a substantial type and a related type.

The table of the semantic data of the class structure diagram A410 includes the entity type class table 511, the entity type attribute table 512, the entity type method table 513, the entity type generalization table 514, the entity type many-to-one table 515, and the association type attribute. Table 516, related type method table 51
7, related type generalization table 518, and related type many-to-one table 519.

Of these, the entity type class table 511
Consists of "identifier", "class name", and "meaning" field of the class name.
It has a person “411”, an “employee” 414, and a “bank” 417.

The entity type attribute table 512 includes "identifier", "attribute name", "meaning" of attribute name, "size", and "size".
It is composed of fields of "type", and "name" 412 and 418, "address" 413, "of FIG.
Holds a post “415”.

The substantive method table 513 is composed of fields of "identifier", "method name", and "meaning" of the method name, and "salary calculation" 416 and "employment" 419 of FIG. 2 are set as the value of the method name. Have as a method name.

The entity type generalization table 514 is composed of fields of "identifier", "generalization name", and "meaning" of the generalization name, and the value of the generalization name is "one type" 42 in FIG.
Has 0.

The substantial type many-to-one table 515 is composed of fields of "identifier", "many-to-one name", and "meaning" of many-to-one name, and "hire" 421 in FIG. To have.

The related type attribute table 507 is composed of fields of "identifier", "class.identifier", and "attribute.identifier". As the value of class.identification and attribute.identifier, the entity type class table 511 and the entity type are stored. A set of record identifiers in the attribute table 512, "ec001, ea001", "ec
It has 002, ea002 ”,“ ec002, ea003 ”, and“ ec003, ea001 ”.

The related type method table 517 is composed of fields of "identifier", "class.identifier", and "method.identifier". The entity type class table 511 and the entity type are used as the values of the class.identifier and the method.identifier. A set of record identifiers in the method table 513, “ec002,
It has “em001” and “ec003, em002”.

The relational generalization table 518 includes "identifier", "generalization.identifier", "class [upper] .identifier", "
"Class [lower] .Identifier" field, and a set of the entity type generalization table 514 and the entity type class table 511 is used as the value of the generalization.identifier, class [upper] .identifier and class [lower]. It has “eg001, ec001, ec002”.

The association type many-to-one table 519 has "identifier", "many-to-one identifier", "class [many] .identifier", "
Class [1] .Identifier ”field, and the values of the many-to-one identifier, class [many] .identification and class [1] .identifier are stored in the entity type many-to-one table 515 and the entity type class table 511. It has a pair, "ep001, ec002, ec003".

Similarly, as shown in FIGS. 6 and 7, the table 520 of the class structure diagram B430 semantic data includes the entity type class table 521 and the entity type attribute table 52.
2, from entity type method table 523, entity type generalization table 524, entity type many-to-one table 525, relation type attribute table 526, relation type method table 527, relation type generalization table 528, relation type many-to-one table 529 Composed.

Of these, the entity type class table 521
Consists of "identifier", "class name", and "meaning" field of the class name.
It has a person "431", an "employee" 433, and a "post office" 437.

The entity-type attribute table 522 has "identifier", "attribute name", "meaning" of attribute name, "size", and "size".
2 is composed of fields of "type" and "name" 432 and 438 and "address" 434, "of FIG.
Holds a post “435”.

The substantive method table 523 is composed of fields of "identifier", "method name", and "meaning" of the method name, and "payroll calculation" 436 and "employment" 439 of FIG. 2 are set as the value of the method name. To have.

The entity type generalization table 524 is composed of fields of "identifier", "generalization name", and "meaning" of the generalization name, and the value of the generalization name is "one type" 44 in FIG.
Has 0.

The substantial type many-to-one table 525 is composed of fields of "identifier", "many-to-one name", and "meaning" of many-to-one name, and "hire" 441 in FIG. To have.

The related type attribute table 526 is composed of fields of "identifier", "class.identifier", and "attribute.identifier". As the value of class.identification and attribute.identifier, the entity type class table 521 and the entity type are stored. A set of record identifiers in the attribute table 522, "ec001, ea001", "ec
It has 001, ea002 ”,“ ec002, ea003 ”, and“ ec003, ea001 ”.

The related type method table 527 is composed of fields of "identifier", "class.identifier", and "method.identifier". The entity type class table 521 and the entity type are used as the values of the class.identifier and the method.identifier. A set of record identifiers in the method table 523, “ec002,
It has “em001” and “ec003, em002”.

The relational generalization table 528 includes "identifier", "generalization.identifier", "class [upper] .identifier", "
"Class [lower] .Identifier" field, and a set of the entity type generalization table 524 and the entity type class table 521 is used as the value of the generalization.identifier, class [upper] .identifier and class [lower]. It has “eg001, ec001, ec002”.

The relational many-to-one table 529 has "identifier", "many-to-one identifier", "class [many] .identifier", "
Class [1] .Identifier ”field, and the values of the many-to-one identifier, class [many] .identification and class [1] .identifier are stored in the entity type many-to-one table 525 and the entity type class table 521. It has a pair, "ep001, ec002, ec003".

8 to 11 are diagrams showing an intermediate table generated in the processing steps of the present invention.

FIG. 8 is a diagram showing the relation type tables of the class structure diagram A meaning data and the class structure diagram B meaning data of FIGS. The structure of the related name table 610 of the class structure diagram meaning data is shown in FIG.
1, related type method table 612, related type generalization table 613, and related type many-to-one table 614.

Of these, the related type attribute table 611
Consists of "class name" and "attribute name" fields, and "person, name" and "as the value of class name and attribute name"
Person, address ”,“ employee, name ”,“ employee, address ”,“
Has "Employee, Title", "Bank, Name".

The related method table 612 is composed of fields of "class name" and "method name", and has "employee, payroll", "bank, employment" as values of the class name and method name.

The relational generalization table 613 is composed of fields of "generalization name", "class [upper] name", and "class [lower] name", and the generalization name, class [upper] name and class [lower]. It has "a kind of person, employee" as the name value.

The relational many-to-one table 614 is "many-to-one".
It consists of fields of "Name", "Class [many] name", "Class [1] name", and many-to-one name, class [many] name and class
[1] Has the value of first name as "hire, employee, bank".

Similarly, the related name table 620 of the class structure diagram B semantic data shown in FIG.
21, an associated type method table 622, an associated type generalization table 623, and an associated type many-to-one table 624.

The related type attribute table 621 is composed of fields of "class name" and "attribute name", and "person, name", "person, address", "as the values of the class name and the attribute name.
It has "employee, name", "employee, address", "employee, job title", and "post office, name".

The related method table 622 is composed of fields of "class name" and "method name", and has "employee, payroll", "post office, employment" as values of the class name and method name.

The relational generalization table 623 is composed of fields of "generalization name", "class [upper] name", and "class [lower] name", and generalization name, class [upper] name and class [lower]. It has "a kind of person, employee" as the name value.

The relational many-to-one table 624 is "many-to-one".
It consists of "Name", "Class [many] name", "Class [1] name" fields, and many-to-one name, class [many] name and class
[1] Has "Hire, Employee, Post Office" as the value of the name.

FIG. 10 shows a relation name comparison result table 700 in which the relation type tables of the class structure diagram A and the class structure diagram B are compared to determine whether or not the same relation name is present.

The record items become a class structure diagram for comparison. The fields of this table are the union of the related name tables of the class structure diagram A and the class structure diagram B of FIGS. 8 and 9, and the attribute table part is “person, name”, “
Person, address ”,“ employee, name ”,“ employee, address ”,“
It consists of “Employee, Position”, “Bank, Name”, “Post Office, Name”.

Further, the method table portion is "employee,
It consists of "Payroll", "Bank, Employment", "Post Office, Employment", the generalization table part is "a kind, person, employee", many-to-one table part is "hire, employee, bank" Consists of "," Hire, Employee, Post Office ".

Further, "1" in the table means that the related name of the field exists in the class structure diagram, and "0" means that the related name does not exist.

FIG. 11 shows a related name matching rate calculation result table 80 in which the related name matching rate, which is the ratio of existence of the same related name, is calculated from the related name comparison result table 700 of FIG.
It shows 0.

The fields of this table 800 are shown in FIG.
It is the same as the 0 field, and each number, "100", "50", etc. of the related name matching rate record indicates the matching rate for each related name.

FIG. 12 shows a generic class structure diagram meaning data table 900, which is a substantial class table 90.
1, a substance type attribute table 902, a substance type method table 903, a substance type generalization table 904, a substance type many-to-one table 905, a relation type attribute table 906, and a relation type method table 907.

Of these, the entity type class table 901
Is composed of fields of "identifier", "class name", and "meaning" of the class name.
Has "people" and "employees".

The entity type attribute table 902 includes "identifier", "attribute name", "meaning" of attribute name, "size" and "
It is composed of "type" fields, and has "name", "address", and "post" of FIG. 11 as the value of the attribute name.

The substantive method table 903 is composed of fields of "identifier", "method name", and "meaning" of the method name, and "payroll calculation" and "employment" of FIG. 11 are used as method name values. Have as.

The entity type generalization table 904 is composed of fields of "identifier", "generalization name", and "meaning" of the generalization name, and has "one type" of FIG. 11 as the value of the generalization name.

The related type attribute table 905 is composed of fields of "identifier", "class.identifier", and "attribute.identifier". As the value of class.identification and attribute.identifier, the entity type class table 901 and the entity type are stored. A set of record identifiers in the attribute table 902, "ec001, ea001", "ec
It has 002, ea002 ”,“ ec002, ea003 ”, and“ ec003, ea001 ”.

The related type method table 906 is composed of fields of "identifier", "class.identifier", and "method.identifier". As the values of the class.identifier and the method.identifier, the entity type class table 901 and the entity type are stored. A set of record identifiers in the method table 903, “ec002,
It has “em001” and “ec003, em002”.

The relational generalization table 907 includes "identifier", "generalization.identifier", and "class [upper] .identifier".
, “Class [lower]. Identifier” field, and the values of generalization.identifier, class [upper]. Identifier and class [lower]. Identifier are stored in the entity type generalization table 904 and the entity type class table 901. Pair, “eg001, ec001, ec00
With 2 ”.

FIG. 13 shows a general class structure diagram 1000 created using the general class structure diagram meaning data table 900 of FIG.

This general-purpose class structure diagram 1000 is composed of classes "person" 1001, "employee" 1003 and the relationship between these classes.

The class "person" 1001 has an attribute "name"
Have 1002. Also, the class "Employee" 1003
The attribute has “post” 1004 and “address” 1005, and the method has “payroll” 1006.

Class “person” 1001 and “employee” 100
The relationship with 3 is the inheritance relationship “one type” 1007.

FIG. 3 is a flow chart showing the procedure for generating the general class structure diagram 1000.

The generation procedure will be described below with reference to this flowchart.

Here, the matching rate “80” with the class structure diagram A410 and the class structure diagram B430 is set as input data, the general class structure diagram is generated, and the general class structure diagram is displayed on the display unit 101. The case of outputting will be described as an example.

Operation of Step 301 In step 301, the name list of the class structure diagrams A to Z already stored in the class structure diagram storage unit 104 is displayed on the display unit 101.
, And request the operator to select the class structure diagram. Next, the class structure diagram A410 and the class structure diagram B430 selected by the operator from the name list are set as input data in the generation process of the general class structure diagram.

Operation of Step 302 In step 302, the input screen of the matching rate is displayed on the display unit 101.
, And the operator is requested to input the precision rate. Next, the matching rate “80” input by the operator is stored in the matching rate storage unit 105.

Operation of Step 303 In step 303, conversion processing is performed on each of the semantic data of the class structure diagram A410 and the class structure diagram B430 set in step 301.

Taking the processing on the semantic data of the class structure diagram A410 as an example, the relational generalization table 518 indicates EOF.
In the meantime, the class [upper] .identification “ec001” and the class [lower] .identifier “ec002” are searched, and the class [upper] .identifier “ec001” is used as a key to attribute from the related type attribute table 516. Search for "," ea002 ", class [lower] .Identifier" ec002 "and attribute.Identifiers" ea001 "," e
Related type attribute record "ec002, ea00" which consists of a002 "
1 ”,“ ec002, ea002 ”are created, the identifier“ re005 ”is added to the record, and the related type attribute table 516
Register with.

Next, the method.identifier is searched from the related type method table 517 using the class [upper] .identifier “ec001” as a key. Method. Because the identifier does not exist
Return to the search process for the relational generalization table. If method.identifier exists, class [lower] .identifier ”ec00
A related type method record having a class [lower level] .identifier and attribute.identifier as a set is created from 2 ”and its method.identifier, and the identifier is added to the record and registered in the related type method table 517.

Operation of Step 304 In step 304, comparison processing of the relational type tables in the semantic data of the class structure diagram A410 and the class structure diagram B430 is performed.

Taking the processing on the semantic data of the class structure diagram A410 as an example, each of the related type tables 516 to 519.
Is used to create the related name table 610.

Taking the processing for the related type attribute table 516 as an example, while the related type attribute table 516 is not EOF, the records "person, name", "person, address" are repeated by the processing of repeating the conversion processing of the related type attribute table 516. ,
"Employee, name", "employee, address", "employee,
The related type attribute table 611 of FIG. 8 composed of "post", "bank, name" is created.

Taking the process of creating the record “person, name” as an example, the class.identifier “ec001” and the attribute.identifier “ea001” are searched from the related type attribute table 516, and the class.identifier “ec001” and the attribute .Identifier "ea001"
Each of the keys is used as a key to search the class name “person” from the entity type class table 511 and the attribute name “name” from the entity type attribute table 512, and the retrieved class name “person”
And record "person, name" is created from attribute name "name".

Next, the related type attribute table 5 of the semantic data
Record of the related name table 611 created from 16 "
Person, name ”,“ person, address ”,“ employee, name ”,
"Employee, Address", "Employee, Title", "Bank,
Name ”and the related name table 621 created from the related type attribute table 526 of the semantic data of the class structure diagram B430.
Records for "People, Names", "Employees, Names", "
Employee, address ”,“ employee, title ”,“ post office, name ”are merged and records“ person, name ”,“ person, ”
Address ”,“ Employee, Name ”,“ Employee, Address ”,
"Employee, Position", "Bank, Name", "Post Office,"
Create a related name table consisting of "name".

A related name comparison result table 700 of FIG. 10 in which the records of the table are used as field names and the class structure diagram A410 and the class structure diagram B430 are used as records.
To create.

Class structure diagram A410 and class structure diagram B
A flag is set for the record 430.

That is, taking the processing for the record of the class structure diagram A410 as an example, the record of each related name table created from the semantic data of the class structure diagram A410 is compared with the field name of the related name comparison result table 700.

Taking the processing for the attribute field of the related name comparison result table 700 as an example, by matching, "person,
Name "," Person, Address "," Employee, Name "," Employee, Address "," Employee, Title "," Bank, Name "
Since they match, the flag is set to "1".

In the collation of "post office, name", since they do not coincide, the flag is set to "0". As a result, the related name tables 610 and 620 of the class structure diagrams A and B of FIGS. 8 and 9 are created, and the related name comparison result table 700 of FIG. 10 is also created.

Operation of Step 305 In step 305, the related name matching rate for each field is calculated for the related name comparison result table 700 created in step 304, and the related name matching rate calculation result table 800 as shown in FIG. To create. In this example, the following calculation formula is used as the calculation processing of the related name matching rate.

[0095]

[Equation 1] Entity type related name match rate [%] = Number of entity type related names present (flag "1") / Number of class structure diagrams x 100 Field "Person, Name" related name match rate calculation processing For example,

[0096]

## EQU2 ## (Number of flags "1" = 2) / (Number of class structure diagrams = 2) × 100 = 10.0 [%].

Operation of Step 306 In step 306, general class structure diagram meaning data is generated from the related name matching rate calculation result table 800 created in step 305.

Taking the field "person, name" as an example,
The related type match “100.0” of the field “person, name” is compared with the matching rate “80” stored in the matching rate storage unit 105 in step 302.

Related name matching rate “100.0” is matching rate “80”
As described above, the processing unit 103 uses the class name “person” and the attribute name “name” as the generic class structure diagram meaning data.
To the entity type class table 901 and the entity type attribute table 902, respectively.

Further, the related type attribute record "re00" in which the identifier "re001" is added to the identifier "ec001" of the class name "person" in the entity type class table and the identifier "ea001" of the attribute name "name" in the entity type attribute table
5, ea001, ec001 ”and create related type attribute table 90
Add to 5.

Operation of Step 307 In step 307, the related type generalization table 907 in the general class structure diagram meaning data table 900 created in step 306 is searched.

While the relational generalization table 907 is not EOF, table conversion processing is performed. Class [upper]. Identifier "ec
001 ”, class [lower] .Identifier“ ec002 ”is searched, and attribute.Identifier“ ea001 ”is searched from the related type attribute table 905 with class [upper] .Identifier“ ec001 ”as a key, and related type generalization Retrieval of class [lower] .Identifier “ec002” from table 907. Attribute.identifier “ea” from related type attribute table 905 with the identifier “ec002” as a key
Search for "001".

When it is determined that the attribute.identifier values are the same data, the records “re001, ec001, ea001” including the retrieved class [upper] .identifier “ec001” are deleted from the related type attribute table 905.

Further, the processing unit 103 uses the class [upper] .identifier "ec001" as a key, and the related type method table 9
Search method. Identifier from 03.

As a result of the search, if the method.identifier does not exist, the process returns to the search of the relational generalization table 907.

The processing unit 103 uses the EO of the relational generalization table.
F is determined, and step 307 ends.

Operation of Step 308 In Step 308, the display unit 101 is displayed on the basis of the generic class structure diagram meaning data converted in Step 307.
A general class structure diagram 1000 such as is displayed.

[0108]

As described above, according to the present invention, in consideration of inheritance relations and encapsulation, which are object-oriented features, a plurality of class structure diagrams of a similar system are input, and the class structure diagrams are input. After inputting an arbitrary matching rate, matching is performed between the meaning data of the input plurality of class structure diagrams to calculate a matching rate, and semantic data satisfying the matching rate is extracted based on the matching rate. Since the class structure diagram between the semantic data is generated, it is possible to generate a highly versatile class structure diagram.

Therefore, when a similar system is newly constructed, the general-purpose class structure diagram can be modified or changed to reduce the development period of the system and improve the reliability.

[Brief description of drawings]

FIG. 1 is a system configuration block diagram showing an embodiment when the present invention is applied to an object-oriented system.

FIG. 2 is a diagram showing an example of a class structure diagram used as input information in the embodiment.

FIG. 3 is a flowchart showing a processing procedure of an embodiment.

FIG. 4 is a diagram showing a configuration and an example of contents of a semantic data table of a class structure diagram A used in an embodiment.

FIG. 5 is a view showing a sequel to FIG. 4;

FIG. 6 is a diagram showing a configuration and an example of contents of a semantic data table of a class structure diagram B used in an embodiment.

FIG. 7 is a view showing a sequel to FIG. 6;

8 is a diagram showing a configuration and an example of contents of a relation name table of the semantic data of the class structure diagram A. FIG.

FIG. 9 is a diagram showing a configuration and an example of contents of a relation name table of the semantic data in the class structure diagram A.

FIG. 10 is a diagram showing a configuration and an example of contents of a related name comparison result table.

FIG. 11 is a diagram showing a configuration and an example of contents of a related name matching rate calculation result table.

FIG. 12 is a diagram showing a configuration and an example of contents of a generic class structure diagram meaning data table.

FIG. 13 is a diagram showing an example of a general class structure diagram output in the embodiment.

FIG. 14 is a flowchart showing a conventional procedure for generating a class structure diagram.

[Explanation of symbols]

101 ... Display unit, 102 ... Input unit, 103 ... Processing unit, 1
04 ... Class structure diagram storage unit, 105 ... Relevance ratio storage unit, 5
10, 520 ... Class structure diagram meaning data table, 61
0, 620 ... Class structure diagram Related name table of semantic data, 700 ... Related name comparison result table, 800 ... Related name matching rate calculation result table, 1000 ... General class structure diagram.

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Hiroyuki Chiba 12 Hitachi, Ltd. Information Systems Division, 890 Kashimada, Sachi-ku, Kawasaki-shi, Kanagawa

Claims (1)

[Claims] 1. A general-purpose class structure diagram generation method for extracting a general-purpose part from a plurality of class structure diagrams to generate a general-purpose class structure diagram. After inputting the matching rate, the matching rate is calculated by matching the meaning data of the input plurality of class structure diagrams, and the meaning data satisfying the matching rate is extracted based on the matching rate, A general-purpose class structure diagram generation method characterized by generating a class structure diagram between data.