JPH07152544A - Diagram production support system and its method - Google Patents

Abstract

PURPOSE:To extremely improve the production efficiency of diagrams. CONSTITUTION:This system and method is provided with a diagram plotting means 3 which plots the component elements of a diagram by means of a graphic knowledge (A) 2 that defines the shapes of component elements of various diagrams and a diagram component element plotting library 1 which consists of software modules used for plotting the component elements of diagrams and then outputs the 1st diagram data where at least the meaning of each component element is described, a diagram converting means 6 which converts the 1st diagram data into the 2nd diagram data based on the inter- diagram relation knowledges (A) 2 and (B) 5, and a diagram verifying means 8 which verifies the repugnancy of diagrams in regard of the prescribed verifying items based on the 1st diagram date, the 3rd diagram date, i.e., a verifying subject, end the inter-diagram relation knowledges (A) 2 and (C) 7.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a diagram creation support system and a diagram creation support method used in analysis or design of a system or software.

[0002]

BACKGROUND OF THE INVENTION System or software analysis,
In designing, various methodologies have been conventionally proposed. In those methodologies, the target system structure is observed from various viewpoints, and a diagram is drawn as an observation result from each viewpoint. Data flow diagram as a diagram,
State transition diagrams and the like are known. The CASE (Computer
Aided Software Engineering) tools. CAS
The E-tool supports the construction of diagrams depending on various methods.

[0003]

However, the conventional CASE tool has the following problems. (1) Since the diagram that can be drawn is limited by each method, the diagram to be drawn cannot be changed according to the developer or the development target. (2) Many diagrams have been proposed for each method, but conversion between them is not easy. (3) There are various diagrams in each method, but the check for equivalence and consistency between diagrams is not sufficient. (4) Even if it is possible to convert the diagram and check the consistency between the methods, the conversion format and check items are limited, and it is difficult to customize according to the developer and the development target. (5) In developing a system, a conventional CASE tool cannot provide such support although it is necessary to grasp the relationship between a diagram for one viewpoint and a diagram for another viewpoint. (6) When developing a system, there is a demand to integrate diagrams for individual viewpoints created by dividing the target system structure into several parts and to create a new diagram. Conventional CASE tools support this. Can't do.

The diagram creation support system and the diagram creation support method of the present invention have been made in view of such a problem, and an object thereof is to overcome the above-mentioned problems of the conventional CASE tool. , It is to provide a diagram creation support system and a diagram creation support method capable of improving the efficiency of diagram creation.

[0005]

In order to achieve the above object, the diagram creation support system according to the first invention comprises a graphic knowledge database defining the shapes of its constituent elements for each type of diagram, Using the diagram component drawing library, which consists of software modules for drawing the components of various diagrams, draws the components of the diagram and at least the first diagram data describing the meaning of each component. The first diagram data from the diagram drawing means is used by using the first diagram relation knowledge database describing the relation knowledge between the diagram drawing means to be output and the diagram before conversion and the diagram after conversion. Diagram change to convert to the second diagram data Means and the diagrams and first diagram data from drawing means, and the third diagram data as verified, second describing the relationship knowledge between diagrams after validation and verification previous diagram
Based on the relational knowledge database
Diagram verification means for verifying consistency between diagrams with respect to predetermined verification items.

A diagram creation support system according to a second aspect of the present invention is the diagram creation support system according to the first aspect of the present invention, further comprising a diagram meaning knowledge database defining meanings regarding a certain diagram. , And means for verifying the consistency within the diagram regarding a predetermined verification item based on the diagram semantic knowledge database and the first diagram data from the diagram drawing means.

A diagram creation support system according to a third aspect of the present invention is the diagram creation support system according to the first aspect of the present invention, wherein the first diagram data from the diagram drawing means is based on a predetermined diagram composition rule. Further comprising a diagram synthesizing means for synthesizing the second diagram data from the diagram converting means to generate synthesized diagram data.

A diagram creation support system according to a fourth aspect of the present invention is the diagram creation support system according to the third aspect of the present invention, and a selecting means for selecting a specific element from the synthesized diagram data, and this selection. Conversion means for converting the specific element selected by the means into display data according to a predetermined diagram conversion rule.

The diagram creation support system according to the fifth aspect of the invention comprises a graphic knowledge database defining the shapes of the constituent elements for each type of diagram and a software module for drawing the constituent elements of various types of diagrams. When drawing a diagram component drawing library and a certain component of the diagram, select the software module corresponding to the shape of the selected component from the figure knowledge database, and use this software module to And a diagram drawing means for drawing components and outputting at least diagram data describing the meaning of each component.

A diagram creation support system according to a sixth aspect of the present invention is the diagram creation support system according to the fifth aspect of the present invention, which is an inter-diagram relationship describing relationship knowledge between a diagram before conversion and a diagram after conversion. It further comprises diagram conversion means for converting the diagram data from the diagram drawing means into predetermined diagram data using the knowledge database.

A diagram creation support system according to a seventh aspect of the present invention is the diagram creation support system according to the fifth aspect of the invention, wherein the diagram data from the diagram drawing means, the diagram data to be verified, and the pre-verification It further comprises a diagram verification means for verifying the consistency between the diagrams with respect to a predetermined verification item based on the inter-diagram relationship knowledge database describing the relationship knowledge between the diagram and the diagram after verification.

A diagram creation support system according to an eighth aspect of the present invention is the diagram creation support system according to the seventh aspect of the present invention, further comprising a diagram meaning knowledge database defining meanings regarding a certain diagram. , And means for verifying consistency within the diagram with respect to predetermined verification items based on the diagram semantic knowledge database and the diagram data from the diagram drawing means.

A diagram creation support system according to a ninth aspect of the present invention is the diagram creation support system according to the sixth aspect of the invention, in which the meaning of each component from the diagram drawing means is based on a predetermined diagram composition rule. It further comprises a diagram synthesizing means for synthesizing the described diagram data and the diagram data from the diagram converting means to generate synthesized diagram data.

A diagram creation support system according to a tenth aspect of the present invention is the diagram creation support system according to the ninth aspect of the present invention, and a selection means for selecting a specific element from the synthesized diagram data, and this selection. Conversion means for converting the specific element selected by the means into display data according to a predetermined diagram conversion rule.

The diagram creation support method according to the eleventh aspect of the invention comprises a graphic knowledge database defining the shapes of the constituent elements for each type of diagram and a software module for drawing the constituent elements of various types of diagrams. Use the Diagram Component Plot Library to draw diagram components,
At least a diagram drawing process for outputting the first diagram data describing the meaning of each component and a first inter-diagram relation knowledge database describing relation knowledge between a diagram before conversion and a diagram after conversion are used. Then, a diagram conversion step of converting the first diagram data into second diagram data, the first diagram data, the third diagram data as a verification target, the diagram before verification and the diagram after verification. A diagram verification step of verifying consistency between the diagrams with respect to a predetermined verification item based on a second inter-diagram relationship knowledge database describing the relationship knowledge with the diagram.

The diagram creation support method according to the twelfth invention is the diagram creation support method according to the eleventh invention, wherein the diagram verification step includes a diagram meaning knowledge database defining meanings related to a certain diagram, The step of verifying the consistency within the diagram with respect to a predetermined verification item based on the diagram data of 1.

The diagram creation support method according to a thirteenth invention is the diagram creation support method according to the eleventh invention, wherein the first diagram data and the second diagram data are created based on a predetermined diagram composition rule. The method further comprises a diagram synthesizing step of synthesizing the diagram data and the synthesized diagram data.

A diagram creation support method according to a fourteenth aspect of the present invention is the diagram creation support method according to the thirteenth aspect of the present invention, further comprising a selection step of selecting a specific element from the synthesized diagram data. And a conversion step of converting the specific element into display data according to a predetermined diagram conversion rule.

The diagram creation support method according to the fifteenth aspect of the present invention includes a step of creating a graphic knowledge database defining the shapes of the constituent elements for each of the various diagrams, and a method of drawing the constituent elements of the various diagrams. In the process of creating a diagram component drawing library consisting of software modules and in drawing a component with a diagram, a software module corresponding to the shape of the component selected from the graphic knowledge database is selected, and the software is selected. A diagram drawing step of drawing a component of the diagram using a module and outputting diagram data describing at least the meaning of each component.

A diagram creation support method according to a sixteenth aspect of the present invention is the diagram creation support method according to the fifteenth aspect of the present invention, which is an inter-diagram relationship describing the relationship knowledge between a diagram before conversion and a diagram after conversion. The method further comprises a diagram conversion step of converting the diagram data into predetermined diagram data using a knowledge database.

The diagram creation support method according to the seventeenth invention is the diagram creation support method according to the fifteenth invention, wherein the diagram data created in the diagram drawing step, the diagram data to be verified, and the verification The method further comprises a diagram verification step of verifying the consistency between the diagrams with respect to a predetermined verification item based on the inter-diagram relationship knowledge database describing the relationship knowledge between the previous diagram and the verified diagram.

A diagram creation support method according to an eighteenth invention is the diagram creation support method according to the seventeenth invention, wherein the diagram verification step includes a diagram meaning knowledge database defining meanings related to a certain diagram, and the diagram. It includes a step of verifying the consistency within the diagram regarding a predetermined verification item based on the diagram data created in the drawing step.

The diagram creation support method according to the nineteenth invention is the diagram creation support method according to the sixteenth invention, wherein the diagram data created in the diagram drawing step based on a predetermined diagram composition rule, The method further comprises a diagram synthesizing step of synthesizing the diagram data created in the converting step to generate synthesized diagram data.

A diagram creation support method according to a twentieth aspect of the invention is the diagram creation support method according to the nineteenth aspect of the invention, including a selecting step of selecting a specific element from the combined diagram data, and a selecting step. And a conversion step of converting the specific element into display data according to a predetermined diagram conversion rule.

[0025]

Embodiments of the present invention will be described in detail below with reference to the drawings. FIG. 1 is a block diagram of the first embodiment of the present invention. In the figure, the diagram creation support system is
A diagram graphic knowledge A (2) as a graphic knowledge database that defines the shapes of the constituent elements for each type of diagram, and a diagram constituent drawing library 1 consisting of software modules for drawing the constituent elements of various diagrams. Have The diagram drawing means 3 extracts a software module corresponding to the shape of the selected component of the diagram from the diagram figure knowledge A (2) when drawing a certain component of the diagram, and uses this software module. Then, the constituent elements of the diagram are drawn, and the diagram data A (4) describing the meaning of each constituent element is output separately from the data relating to the figure.

The diagram converting means 6 is an inter-diagram relation knowledge database A, B as an inter-diagram relation knowledge database which describes relation knowledge between different diagrams.
Using (5), the diagram data A (4) from the diagram drawing means 3 is converted into another type of diagram data B (12).

Further, the diagram verifying means 8 is a diagram data A from the diagram drawing means 3.
Based on (4), the diagram data C (6), and the inter-diagram relationship knowledge A, C (7), the consistency between the diagrams is verified with respect to the predetermined verification item 10.
Further, the diagram verification means 8 determines a predetermined verification item based on the diagram meaning knowledge A (9) as a diagram meaning knowledge database defining meanings related to the diagram and the diagram data A (4) from the diagram drawing means 3. For 10, verify the consistency inside the diagram.

FIG. 2 is a class structure diagram as an object diagram diagram according to the OMT method, and is used to create the diagram component drawing library 1 of FIG. 1 described above.

In FIG. 2, a quadrangle represents a class, a connecting line between classes with a triangle represents an inheritance relationship, an upper part is a parent class, and a lower part is a child class. Also,
The connecting lines with diamonds show the aggregation relationship, and the ones marked with black circles are the constituent elements. Therefore, the diagram (Di
agram) 20 is a diagram item (Diagram Ite
m) It consists of a group of 21 diagram items, 20
It can be seen that is composed of a node (Node) 22 and an arc (Arc) 23. This node 22 is a rectangle (Rectangle)
24 and a cloud 25, the arc 23 has a triangle relation (TriangleRelation) 26, and a rhombus relation (R).
homb Relation) 27 and Double Line 28
And an arrow (Arrow) 29.

The diagram item 21 is composed of a collection of graphical items 30 representing a shape. The graphical item 30 is composed of a text 31, a shape 32, and a group 33 of them,
The shape 32 includes a line 34 and a polygon 3.
There are 5 and Circle 36.

By utilizing the concept of inheritance in the object-oriented design method based on such a class structure, each software module of the diagram component drawing library 1 can be efficiently created.

Further, FIG. 2 also includes class information necessary for describing a diagram as shown in the figure, and the classes for describing each class shown in FIG.
Rectangle (Rect) inherited from the class of Node 22
angle) is created based on 24 classes. Also, the relation line with a triangle that indicates inheritance is the arc 23.
Relation inherited from the class (Triangle Relation)
It is created based on 26 classes. Similarly, the aggregate relation is created based on the class of Rhomb Relation 27. In addition, Cloud 25, double line (Do
uble Line) 28 and Arrow (Arrow) 29 are classes used when creating a Booth class diagram as shown in FIG.

In the above-mentioned creation of the new class, the diagram item (Diagram Item) 21, which is a higher-level class, has the information about the basic operation, movement, enlargement, reduction, deletion, insertion, etc. for the figure, and newly defines it. No need.

Next, the diagram figure knowledge A (2) of FIG.
Will be described. Diagram figure knowledge A (2)
The components of the diagram and the class structure of Figure 2 above,
That is, it defines the correspondence with the software modules of the diagram component drawing library 1.

The diagram knowledge of the diagram figure knowledge A (2) is expressed by a set of three relation names (component name, drawing module) as follows. shape (Class, Rectangle) shape (Inheritance, Triangle Relation) shape (Aggregation, Rhomb Relation) Here, the shape knowledge of the first line indicates that the shape of the class is a rectangle, and the second line is The inherited shape is a triangle ", and the third line indicates that the aggregate shape is a diamond."

The diagram graphic knowledge A (2) has been described above, but the diagram drawing means 3 corresponds to this component when a specific component is selected from the diagram graphic knowledge A (2). A software module is selected from the diagram component drawing library 1 and the module is activated to perform drawing.

For example, it is assumed that the user has created the diagram as shown in FIG. 2 by the diagram drawing means 3 based on the above-mentioned figure knowledge. In this case, as can be seen in Figure 2, the graphical item (Graphica
l Item 30 and Group 33 are rectangles (re
ctangle), and from the diagram figure knowledge A (2), a rectangle (rectangle) represents a class. Therefore, the diagram drawing means 3 separates each of the diagrams from the figure information as a result of drawing. The following semantic information about the components (diagram data A
(4)) can be output.

Class (Graphical Item) // Graphical It
em is a class class (Group) class (Text) class (Shape) class (Line) class (Polygon) class (Circle) class (Diagram) class (Diagram Item) class (Node) class (Arc) class (Cloud) class (Double Line) inherit (Group, Graphical Item) // Group is Graphic
inherit (Text, Graphical Item) inherit (Shape, Graphical Item) inherit (Line, Shape) inherit (Polygon, Shape) inherit (Circle, Shape) inherit (Node, Diagram Item) inherit (Arc, Diagram Item) ) inherit (Cloud, Node) inherit (Double Line, Arc) aggregate (Group, Graphical Item) // Group is Grahi
aggregate (Diagram, Diagram Item) which is an aggregation of cal Items The procedure of the above-described diagram drawing processing will be described below with reference to the flowchart of FIG. Here, S represents a step. First, the user selects a particular diagram from several display menus not shown. As a result, for example, the diagram graphic knowledge A (2) in FIG. 1 is selected (S1). Next, the system associates all the components of the diagram with the software modules of the diagram component drawing library 1 (S2). Next, the user selects a specific component from all the displayed components (S3). In response to this, the system activates the corresponding software module from the diagram component drawing library 1 (S
4). Next, edit the component (S5),
If not finished, the same processing is executed for the next selected diagram component. When it is finished, for example, the diagram data A as described above
(4) is generated (S6, S7).

The processing operation of the diagram converting means 6 will be described below. The diagram conversion means 6 converts the diagram data A (4) using the inter-diagram relationship knowledge A, B (5) and outputs the diagram data B (12).

Here, the inter-diagram relationship knowledge A, B
(5) can be considered to indicate the relationship between the class diagram by the OMT method shown in FIG. 2 and the class diagram by the Booth method as shown in FIG. 3, and can be described as follows. .

Equivalent (class, class) equivalent (inherit, inherit) equivalent (aggregate, use) In the above example, the second term is the component name in the OMT method, and the third term is the component name in the Booth method. Shows.

Further, when the diagram converting means 6 performs the conversion, the above-mentioned inter-diagram relationship knowledge A, B is used.
For (5), for example, the unification and backtracking mechanism used in the processing of the Prolog language is applied,
The conversion instruction at this time can be described by the following formula. ? -equivalent (X, Y), X (S), output (Y (S)).? -equivalent (X, Y), X (S, T), output (Y (S, T)). where , Output (X) serves to register X as new knowledge.

After execution of the above conversion instruction, only the last two lines of the diagram data A (4) by the OMT method, aggregate (Group, Graphical Item) aggregate (Diagram, Diagram Item) are used (Group, Graphical Item). It is converted to use (Diagram, Diagram Item) and there is no other change. Diagram data B (1
2) is generated.

The figure knowledge of the class diagram according to the Booth method can be defined as follows. By combining this figure knowledge and the above diagram data B (12), a class diagram as shown in FIG. 3 is generated.

Shape (Class, Cloud) shape (Inheritance, Arrow) shape (Aggregation, Double Line) As described above, the semantic information is common between the two methods,
Although only the shapes are different, according to the present embodiment, it is possible to create diagrams of various methods only by changing the information on the shapes.

The procedure of the above diagram conversion processing will be described with reference to the flowchart of FIG. First, the diagram data A (4) is read, and the inter-diagram relationship knowledge A, B (5) is read (S10, S1).
1). Next, the conversion instruction as described above is read and conversion is executed (execution by unifying and returning), and the converted diagram data B (12) is output (S12, S1).
3).

Next, the diagram verification means 8 in FIG. 1 will be described. The diagram verification means 8 uses the diagram drawing means 3 separately from the inter-diagram relationship knowledge A, C (7) created separately from the inter-diagram relationship knowledge A, B (5) and the diagram data B (12). Receiving the created diagram data C (6) and the diagram data A (4) from the diagram drawing means 3, the diagram data A (4) and the diagram data C regarding the specific verification item 10 selected by the user. Verify whether (6) matches, that is, the consistency between the two diagrams. Here, the inter-diagram relationship knowledge A, C (7) is determined by the type of the inputted diagram data, but may be the same as the inter-diagram relationship knowledge A, B used for the diagram conversion.

Further, by inputting the diagram meaning knowledge defining the meaning of one kind of diagram data and the diagram data to the diagram verifying means 8, it is possible to detect the inconsistency in the diagram. In FIG. 1, the diagram verifying means 8 verifies the internal consistency of the diagram A (4) using the diagram semantic knowledge A (9) with respect to the specific verification item 10 selected by the user, and obtains the verification result 11. An example is shown.

Here, in the case of verifying the inconsistency in the diagram, as the diagram semantic knowledge A (9), for example, the following semantic knowledge, for example, inheritance and ancestor (ance).
stor) is defined.

Ancestor (X, Y):-inherit (Y, X). Ancestor (X, Z):-ancestor (X, Y), ancestor (Y, Z). For such semantic knowledge, You can check the existence of inheritance loop for all classes by entering the verification item? -Class (X), ancestor (X, X). At this time, similarly to the diagram conversion, by using the processing mechanism by unification and backtracking, when there is a contradiction in the diagram, the name of the class that constitutes the inheritance loop is obtained as the solution of X.

The procedure of the above-mentioned diagram verification process will be described below with reference to the flowchart of FIG. First, the diagram data A (4) and the diagram data C (6) are read, and the inter-diagram relationship knowledge A, C (7) is read (S20, S21). next,
The specific verification item 10 is read and verification is performed (execution by unification and backtracking), and the verification result 11 is output (S2).
2, S23). In this way, at the time of verification, the user can input an item to be verified, so that flexible verification can be performed.

The following effects can be obtained from the first embodiment described above. (1) By combining a diagram component drawing library using an object-oriented class hierarchy and diagram figure knowledge, that is, a database of semantic information that a diagram is a class, and a shape that a class is a rectangle Since an information database is prepared separately and they are associated with each other, it is possible to create an editor that can describe diagrams of various methods by changing only the shape information, and it is flexible according to the developer or development target. Can be customized.

(2) Since the diagram figure knowledge as the knowledge about the shape of the diagram, the diagram data as the logical meaning data of the diagram, and the inter-diagram relation knowledge defining the relation between the diagrams are separately held, By combining these, flexible conversion between various diagrams is possible.

(3) Since the consistency between the diagram data and various kinds of semantic knowledge is examined, it is possible to verify the consistency between the diagrams or within the diagrams. (4) In verification and conversion, verification rules and conversion rules can be flexibly defined, and customization by the developer and development target becomes easy.

(5) Since the unification and backtracking mechanism used in the Prolog language are used, conversion and verification can be realized by one engine. The second embodiment of the present invention will be described below. In the second embodiment, a diagram composition support function having a diagram composition function and a view setting function described below is added to the configuration of the first embodiment.
The diagram composition function realizes composition (merging) of two diagrams of different types (viewpoints) and composition (merging) of two diagrams of the same type. The view setting function is used when it is desired to select and display a specific item from the information described in the diagram. For example, when a new synthetic diagram is obtained from two diagrams, it is often the case that only a part of the information of the diagrams is actually displayed. Therefore, this view setting function allows you to select and specify the items you want to display from the information that the diagram has, and display only the necessary information in an easy-to-see manner.

FIG. 7 is a block diagram of a diagram synthesis support system for realizing the above-mentioned diagram synthesis support function. In the figure, the diagram synthesizing means 44 stores definition data of a plurality of diagrams, here two diagrams, that is, diagram data A (41) and B (42) which are data defining components and a relation between components. In response, the diagram data A × B (45) synthesized based on the diagram synthesis rule 43 describing the rule for synthesizing (merging) these definition data is generated. Here, in the following, the above diagram data A
(41) and B (42) are the data output from the diagram drawing means 3 shown in FIG. 1, that is, the diagram data A (4) and the data output from the diagram converting means 6, that is, the diagram data B, respectively.
The description will be made assuming that it is the same as (12).

Further, the diagram view converting means 48
Receives the diagram data, which is the definition data of a certain diagram, here the diagram data A × B (45), and sets the view data 46 for setting the item to be displayed in the information of the diagram and the diagram data. Based on the diagram conversion rule 47 in which a rule for displaying based on the view data 46 is described, it is converted into display diagram data 49.

The above will be described in more detail with reference to FIGS. 8 to 13. 8 and 9 show the Boot
Class diagram created by h method (Fig. 8)
And the object diagram (Fig. 9). In the following, the present embodiment will be described by taking the synthesis (merging) of these two diagrams as an example. However, in order to avoid making the explanation complicated, the class diagrams and object diagrams handled below are simplified from the original.

8 and 9 show analysis / design results regarding the "toggle switch" in the home heating system (Source: G. Booch, Object-Oriented Design with App)
lications).

First, the toggle switch class diagram of FIG. 8 will be described. This class diagram consists of "classes" and "relationships between classes".
The dotted cloud shape is a symbol that expresses a "class", and each label inside the cloud shape, namely HeatSwitch (50), Togg.
leSwitch (52) and BooleanView (51) are class names. Arrows and double lines are symbols that express the "relationship between classes". The arrows indicate the inheritance relationship, with the starting class as the child class and the ending class as the parent class. The double line indicates the usage relationship, which means that the class with the black circle uses the resource of the other class. Boc
In the h method, the structure of the class (attributes and operations) is defined in the class template and is not displayed as a class diagram.

Next, the toggle switch object diagram of FIG. 9 will be described. This object diagram is composed of "objects" and "relationships between objects". The solid cloud shape is "object"
, The solid line is a symbol expressing the “relationship between objects”. Each label in the cloud, ie aController
(53), aToggleSwitch (55), aBooleanViewTrue
(56) and aBooleanViewFalse (54) are object names. Also, arrows on solid lines represent message exchanges between objects, and labels represent message names. The symbols F and P attached to the ends of the solid lines represent the visibility between objects.

Here, the above two diagrams, that is, the class diagram and the object diagram, have the following relationships. That is, an object is an instance of a class. For example, the object aToggleSwitch (55) is an instance of the class ToggleSwitch 52 and can perform the operations defined in this class. Also, the object aBooleanViewTrue (5
6) and aBooleanViewFalse (54) are both instances of the class BooleanView (51).

The synthesis (merging) of the toggle switch class diagram and the toggle switch object diagram reflecting such a relationship will be described below. In this example, the description method of the programming language Prolog is used as the data format.

First, the diagram data as the semantic information of both diagrams will be shown. The diagram data A (41) of the class diagram of FIG. 8 is as follows.
However, in the Booth method, the list of attribute names and the list of operation names of “class definition” are stored in the class template, and thus are not displayed as a class diagram. <Diagram data: Toggle switch class diagram> / * set of defined classes class set (diagram name, list of class names) * / class set (ToggleSwitchClassDiagram, [HeatSwitch, ToggleSwitch, BooleanView]) / * class definition class (Class name, list of attribute names, list of operation names) * / class (HeatSwitch, [heat switch on / off], []) class (ToggleSwitch, [switch on / off], [switch on, switch off] class (BooleanView, [boolean view], [update, state]) / * Set of class relations that are defined class relation (relation type, class name, class name) * / class relation (Inherit, HeatSwitch, ToggleSwitch) class relation (Use, ToggleSwitch, BooleanView) In addition, the diagram data B (42) of the object diagram of Fig. 9 is as follows: <Diagram data: Toggle switch Object diagram> / * set of defined objects object set (list of diagram name, object name) * / object set (ToggleSwitchObjectDiagram, [aContoroller aToggleSwitch, aBooleanViewTrue aBooleanViewFalse]) / * object definition object (object name, Class name) * / object (aContoroller, Contolroller) object (aToggleSwitch, ToggleSwitch) object (aBooleanViewTrue, BooleanView) object (aBooleanViewFalse, BooleanView) / * set of object relations defined object relation (object name, visibility, synchronization, Message name Object name, visibility, synchronization, message name) * / object relation (aContoroller, Null, Simple, State, aToggleSwitch, Field, Null, Null) object relation (aToggleSwitch, Filed, Simple, update, aBooleanViewTrue, Parameter, Simple , State) object relation (aToggleSwitch, Filed, Sim ple, update, aBooleanViewFalse, Parameter, Simple, state) Now, the relationship between the class diagram and the object diagram is "correspondence between the class of the object defined on the object diagram and the class defined on the class diagram (here Then, it is called an instance relationship). " Therefore, the above two diagram data A (41) and diagram data B (4
In the diagram synthesis rule 43 for synthesizing 2), an instruction for extracting an instance relationship from two diagram data is described in Prolog language.

The diagram synthesizing means 44 synthesizes the two diagram data according to the diagram synthesizing rule 43. In this embodiment, the union of the two diagram data sets the following "class and object instance". New diagram data is generated with the addition of data on "relationship".

/ * Relationship between class and object * / class object relation (instance, object name, class name) * / class object relation (instance, aToggleSwitch, ToggleSwitch) class object relation (instance, aBooleanViewTrue, BooleanView) class object relation ( instance, aBooleanViewFalse, BooleanView) FIG. 10 is a display example of diagram data A × B (45) obtained by combining two diagram data. This allows the user to simultaneously view the relationships between objects and the classes, for example.

The above diagram synthesis processing is summarized as follows. That is, in the flowchart of FIG. 12, first, the diagram data A (41) and the diagram data B (42) are the diagram synthesizing means 4
4 is input (step S30). Next, the diagram composition rule 43 is read (step S31). Next, the diagram synthesizing means 44 synthesizes the two diagrams based on the read diagram synthesizing rule 43, and the synthesized diagram data A × B (45)
Is output (steps S32 and S33).

Next, the user wants to display information relating to the operation of each object (operation defined by the corresponding class) in the composite diagram data A × B (45), and this is displayed as the view data 46. Suppose you set it by In this case, (1) of the diagram conversion rule 47 regarding the class diagram and the object diagram as defined below is referred to, the information related to the operation of each object is extracted, converted by the diagram view conversion means 48, and, for example, , Figure 1
The display diagram data 49 as shown in 1 is displayed. <Diagram conversion rule> Rule example (1) / * object has an operation defined by a class * / object operation (OBJECT NAME, LIST OF OPERATION):-object (OBJECT NAME, CLASS NAME), class (CLASS NAME, LIST OF FIELD, LIST OF OPERATION). Rule example (2) / * In the inheritance relationship, the object of the child class has the functions of the child class and the parent class * / object operation (OBJECT NAME, LIST OF OPERATION):-object (OBJECT NAME, CHILD CLASS NAME), class relation (inherit, CHILD CLASS NAME, PARENT CLASS NAME), class (CHILD CLASS NAME ,, LIST OF OPERATION CHILD), class (PARENT CLASS NAME,, LIST OF OPERATION PARENT), append (LIST OF OPERATION CHILD, LIST OF OPERATION PARENT , LIST OF OPERATION). The diagram view conversion process described above is summarized as follows. That is, in the flowchart of FIG. 13, first, the synthesized diagram data A × B (4
5) is input to the diagram view conversion means 48 (step S40). Next, items to be displayed are set based on the view data 46 (step S41). Next, the diagram conversion rule 47 is read (step S42). Next, the diagram view conversion means 48 reads the view data 46 and the read diagram conversion rule 4
The display diagram data 49 is created based on No. 7 and output (steps S43 and S44).

According to the combining function of the second embodiment described above,
When different types of diagrams are combined, it is possible to check the consistency between the two diagrams on the combined diagram or check the consistency with another diagram while describing one diagram. . In addition, when the same type of diagrams are combined, it becomes easy to divide the system analysis / design (diagram creation work).

Further, by the view setting function, it is possible to select and set the information to be displayed from the information that the diagram has, and display only the necessary information in an easy-to-see manner. further,
With the above two functions, it is possible to support the creation of a diagram in the analysis / design of the system and software, and to develop a higher quality system and software.

[0071]

According to the present invention, the efficiency of creating a diagram can be greatly improved.

[Brief description of drawings]

FIG. 1 is a configuration diagram of a diagram creation support system according to a first embodiment of the present invention.

FIG. 2 is a diagram showing an object diagram according to the OMT method.

FIG. 3 is a diagram showing an object diagram according to the Booth method.

FIG. 4 is a flowchart showing a procedure of a diagram drawing process.

FIG. 5 is a flowchart showing a procedure of diagram conversion processing.

FIG. 6 is a flowchart showing a procedure of a diagram verification process.

FIG. 7 is a configuration diagram of a diagram synthesis support system according to a second embodiment of the present invention.

FIG. 8 is a diagram showing a class diagram according to the Booth method.

FIG. 9 is a diagram showing an object diagram according to the Booth method.

FIG. 10 is a diagram showing a diagram in which two diagrams are combined.

FIG. 11 is a diagram showing an example in which specific display items are displayed near the object diagram.

FIG. 12 is a flowchart showing a procedure of a diagram combining process.

FIG. 13 is a flowchart showing a procedure of diagram view conversion processing.

[Explanation of symbols]

1 ... Diagram component drawing library, 2 ... Diagram figure knowledge A, 3 ... Diagram drawing means, 4 ... Diagram data A, 5 ... Inter-diagram relationship knowledge A,
B, 6 ... Diagram data C, 7 ... Inter-diagram relationship knowledge A, C, 8 ... Diagram verification means, 9 ... Diagram semantic knowledge A, 10 ... Verification item, 11 ... Verification result,
12 ... Diagram data B.

Claims (20)

[Claims] 1. A diagram is created by using a graphic knowledge database that defines the shape of each constituent element for each type of diagram and a diagram constituent element drawing library including a software module for drawing the constituent elements of each type of diagram. Drawing the components of
A diagram drawing means for outputting at least first diagram data describing the meaning of each constituent element, and a first inter-diagram relation knowledge database describing relation knowledge between a diagram before conversion and a diagram after conversion are used. And a diagram converting means for converting the first diagram data from the diagram drawing means into second diagram data, the first diagram data from the diagram drawing means, and the third diagram data as a verification target. And a diagram verification means for verifying consistency between the diagrams with respect to a predetermined verification item, based on a second inter-diagram relationship knowledge database describing relationship knowledge between the diagram before verification and the diagram after verification. , Which is characterized by including: Lamb creation support system. 2. The database further comprises a diagram semantic knowledge database that defines the meaning of a diagram,
The diagram verifying means includes means for verifying consistency within the diagram regarding a predetermined verification item based on the diagram semantic knowledge database and the first diagram data from the diagram drawing means. The diagram creation support system according to claim 1. 3. The combined diagram data is generated by combining the first diagram data from the diagram drawing means and the second diagram data from the diagram converting means based on a predetermined diagram combining rule. The diagram creation support system according to claim 1, further comprising: 4. Selection means for selecting a specific element from the combined diagram data, and conversion means for converting the specific element selected by the selection means into display data according to a predetermined diagram conversion rule. The diagram creation support system according to claim 3, further comprising: 5. A graphic knowledge database defining the shapes of the constituent elements for each type of diagram, a diagram constituent drawing library comprising software modules for drawing the constituent elements of various diagrams, and a constituent element having a diagram. In drawing, a software module corresponding to the shape of the component selected from the graphic knowledge database is selected, the component of the diagram is drawn using this software module, and at least each component is drawn. A diagram creation support system comprising: a diagram drawing means for outputting diagram data describing meaning. 6. A diagram for converting diagram data from the diagram drawing means into predetermined diagram data by using an inter-diagram relation knowledge database describing relation knowledge between a diagram before conversion and a diagram after conversion. The diagram creation support system according to claim 5, further comprising conversion means. 7. Based on the diagram data from the diagram drawing means, the diagram data as a verification target, and the inter-diagram relation knowledge database describing the relation knowledge between the diagram before verification and the diagram after verification. The diagram creation support system according to claim 5, further comprising a diagram verification means for verifying consistency between the diagrams with respect to a predetermined verification item. 8. The database further comprises a diagram semantic knowledge database that defines the meaning of a diagram,
8. The diagram verifying means includes means for verifying consistency within a diagram regarding a predetermined verification item based on the diagram semantic knowledge database and the diagram data from the diagram drawing means. A diagram creation support system. 9. Diagram data synthesized by synthesizing diagram data describing the meaning of each component from the diagram drawing means and diagram data from the diagram converting means on the basis of a predetermined diagram synthesizing rule. 7. The diagram creation support system according to claim 6, further comprising a diagram synthesizing means for generating 10. Selection means for selecting a specific element from the synthesized diagram data, and conversion means for converting the specific element selected by the selection means into display data according to a predetermined diagram conversion rule. The diagram creation support system according to claim 9, further comprising: 11. A diagram is created by using a graphic knowledge database that defines the shape of each constituent element for each type of diagram and a diagram constituent element drawing library including a software module for drawing the constituent elements of various types of diagrams. The first step is to describe the relational knowledge between the diagram before conversion and the diagram after the diagram drawing step of drawing the first diagram data describing at least the meaning of each component by drawing the components A diagram conversion step of converting the first diagram data into second diagram data by using the inter-diagram relationship knowledge database, the first diagram data, and the third diagram data as a verification target, Diagram before verification and diagram after verification A diagram verification step of verifying a consistency between the diagrams with respect to a predetermined verification item based on a second inter-diagram relationship knowledge database describing the relationship knowledge with the ram, and a diagram characterized by the following: Creation support method. 12. The diagram verifying step comprises a step of verifying a consistency inside a diagram for a predetermined verification item based on a diagram meaning knowledge database defining a meaning related to a certain diagram and the first diagram data. 12. The diagram creation support method according to claim 11, further comprising: 13. A diagram synthesizing step of synthesizing the first diagram data and the second diagram data based on a predetermined diagram synthesizing rule to generate synthesized diagram data. 12. The diagram creation support method according to claim 11, which is characterized in that. 14. The method further comprises a selecting step of selecting a specific element from the combined diagram data and a converting step of converting the selected specific element into display data according to a predetermined diagram conversion rule. 14. The diagram creation support method according to claim 13, wherein: 15. A process for creating a graphic knowledge database defining the shapes of the constituent elements for each type of diagram, and a diagram constituent drawing library composed of software modules for drawing the constituent elements of various types of diagrams. When drawing a process and a certain component of a diagram, select the software module corresponding to the shape of the selected component from the figure knowledge database, and use this software module to draw the component of the diagram. And a diagram drawing step of outputting diagram data in which at least the meaning of each constituent element is described, and a diagram creation supporting method. 16. A diagram conversion step of converting the diagram data into predetermined diagram data using an inter-diagram relation knowledge database describing relationship knowledge between a diagram before conversion and a diagram after conversion. 16. The method according to claim 15, wherein
The method to support diagram creation in the description. 17. The diagram data created in the diagram drawing step, the diagram data as a verification target, and the inter-diagram relation knowledge database describing the relation knowledge between the diagram before verification and the diagram after verification. 16. The diagram creation support method according to claim 15, further comprising a diagram verification step of verifying a consistency between the diagrams with respect to a predetermined verification item. 18. The diagram verifying step, based on the diagram meaning knowledge database defining the meaning of a certain diagram, and the diagram data created in the diagram drawing step, confirms the consistency within the diagram regarding predetermined verification items. 18. The diagram creation support method according to claim 17, further comprising a step of verifying. 19. A diagram composition that composes the diagram data created in the diagram drawing step and the diagram data created in the converting step to generate combined diagram data based on a predetermined diagram combining rule. 17. The diagram creation support method according to claim 16, further comprising a step. 20. A selection step of selecting a specific element from the combined diagram data, and a conversion step of converting the selected specific element into display data according to a predetermined diagram conversion rule. 20. The diagram creation support method according to claim 19.