JP5952716B2 - Class diagram conversion device and class diagram conversion program - Google Patents

Description

  The present invention relates to a class diagram conversion device and a class diagram conversion program for converting a class diagram created for object-oriented software development into another appropriate class diagram.

  In recent software development, an object-oriented development method has been widely adopted. In particular, in development using Java (registered trademark), a class diagram based on UML (Unified Modeling Language) (registered trademark) is often used. As a feature of current object-oriented development, it is possible to develop UML modeling language consistently from concept modeling process to logical modeling process, and to the physical modeling process if the implementation language is an object-oriented language such as Java language. As a result, the applicability of the specification itself from the upstream process to the downstream process is improved, and the time for creating the specification can be reduced. In addition, it is known that the design intention in the upstream process can be easily communicated to the downstream process by using the same modeling language.

  Similar to conventional modeling, in object-oriented software development, there can generally be multiple ways of grasping the structure for the modeled object, so the final decision on the structure to be adopted must be made by the designer. In this regard, unlike conventional development methods such as structuring methods, object-oriented development methods pattern combinations of classes as a way of understanding the structure (class and relationship between classes) for the modeled object. "Design patterns" (Note that what is presented (catalogized) together with multiple design patterns is referred to as "Design Pattern Catalog". Refer to Non-Patent Document 1) and "Refactoring Catalog" that catalogs methods for redesigning classes. Is proposed (see Non-Patent Document 2). This makes it easier to determine the structure to be modeled than in the past.

E. Gamma et al. (Shinichi Honda et al.), “Design Patterns for Reuse in Object Oriented”, Softbank Publishing, Tokyo, October 1999 M. Fowler, (Kodama Koshin, Tomono Akio, etc.), “Refactoring Programming Improvement Techniques”, Pearson Kirihara, Tokyo, 2000

However, in the software development based on object orientation, when a designer actually wants to use a design pattern or a refactoring catalog, there are the following problems at present.
・ In the first place, there are not enough tools to support design patterns and refactoring catalogs.
・ Furthermore, in order to use existing design patterns and refactoring catalogs, it is difficult to use because it requires advanced knowledge of individual design patterns and refactoring.

  As in the case of structured design, in object-oriented software development, structural design that takes into account the implementation of modeling performance etc. is performed in the downstream process, while in the upstream process modeling, the implementation method, language to be implemented, In order to design an abstract structure that does not depend on middleware or the like, the structure represented by the class diagram generally differs. However, there is no class diagram conversion tool that takes into account the difference in viewpoint in each process.

  Furthermore, when class design is actually performed, there are a plurality of model representation methods, and therefore, the designer often gets confused about which design pattern (structure) is best represented. In that case, the designer needs to reapply to each of the multiple design patterns and manually change each class in the class diagram to express it with the optimal design pattern, which is very labor intensive. .

  The present invention has been made in view of such a background, and the present invention provides a class diagram conversion device and a class diagram that support design of a class diagram based on an optimal design pattern when reviewing a class diagram once created. It is an object to provide a conversion program.

In order to solve the above-described problem, the invention according to claim 1 provides a pattern of a structure indicated by a combination of a class and a relation representing a connection relation between the classes in a class diagram used in object-oriented software development. A class diagram conversion device for converting to another pattern different from the current pattern and displaying it on a display device, the class constituting the class diagram, an object of the class, and an object indicating an example of the class, As an equivalent component when converting the class diagram, for each of the two components in the class diagram, the type of association between the components and the class, the attribute, or the object with the type of components, class diagram information representing the configuration of a pattern of the class diagram before conversion, the pattern constituting the class diagram, Pattern determining logic for determining whether corresponds to which pattern of the constant group of patterns by referring to the class diagram information, and, pattern after convertible conversion in the pre-conversion pattern and the pre-conversion pattern converting pattern indicating a combination of the stores the conversion pattern information that is more stored a storage unit, a class diagram before conversion is displayed on the display device acquires the class diagram information before the conversion, the conversion The application part to be converted in which at least one of the class, the attribute, and the object in the previous class diagram is selected is acquired via an input unit, and the pre-conversion indicated in the acquired application part of the pattern of the class diagram, with reference to the class diagram information specified on the basis of the pattern determination logic for the particular pattern The convertible conversion pattern is determined with reference to the conversion pattern information, and one or more convertible in the pre-conversion pattern and the pre-conversion pattern indicated in the determined convertible conversion pattern The converted pattern is displayed on the display device, selection information of the converted pattern selected from the one or more converted patterns is acquired via the input means, The class diagram conversion device is characterized by comprising display processing means for converting the obtained pattern of the class diagram before conversion into the acquired pattern after conversion and displaying the pattern on the display device.

By doing in this way, the class diagram conversion device identifies the pattern of the application location of the class diagram conversion selected by the designer or the like based on the pattern determination logic, and can convert one or more that can be converted for the identified pattern The converted pattern is displayed on the display device. Then, the class diagram conversion device can convert the class diagram before conversion indicated in the selection information of the application location into a pattern after conversion selected by the designer or the like and display it on the display device.
Therefore, since the designers can select an optimal pattern after conversion from one or more converted patterns displayed on the display device, advanced knowledge about each pattern (design pattern). Class diagram can be converted without the need for.

According to a second aspect of the present invention, the predetermined pattern group includes a pattern indicating a relationship between a class and an attribute, a pattern indicating a class aggregation relationship, and an abstract class in the class aggregation relationship in the class diagram. The class diagram conversion device according to claim 1, wherein the class includes a pattern including an object in a pattern and class aggregation relationship, a pattern that realizes an inheritance relationship by delegation, and a pattern that indicates an inheritance relationship .

In this way, in software development based on object-oriented, when the design class diagram is frequently used, and it is difficult to determine optimal whether the at expressing any pattern for which can be expressed by a plurality of patterns , A pattern indicating the relationship between a class and an attribute, a pattern indicating a class aggregation relationship, a pattern having an abstract class in the class aggregation relationship, a pattern in which the class has objects in the class aggregation relationship, and an inheritance relationship realized by delegation The pattern after conversion and the pattern indicating the inheritance relationship can be displayed and selected by a designer or the like.
The invention according to claim 3 includes a conversion pattern for converting the pattern indicating the relationship between the class and the attribute into a pattern indicating the aggregated relationship of the class as the conversion pattern stored in the conversion pattern information. The class diagram conversion device according to claim 2 is provided.
According to a fourth aspect of the present invention, as a conversion pattern stored in the conversion pattern information, a pattern indicating an aggregation relationship of the class is abstracted between a pattern indicating a relationship between the class and an attribute, and the aggregation relationship of the class. 3. The class diagram conversion device according to claim 2, comprising a conversion pattern for converting each of a pattern having a class and a pattern in which the class includes an object in the class aggregation relationship.
In the invention according to claim 5, as a conversion pattern stored in the conversion pattern information, a pattern having an abstract class in the aggregation relation of the class, a pattern indicating the aggregation relation of the class, and an aggregation relation of the class The class diagram conversion device according to claim 2, further comprising: a conversion pattern for converting each of the classes including a pattern including an object.
In the invention according to claim 6, as a conversion pattern stored in the conversion pattern information, a pattern in which the class includes an object in the aggregation relation of the class, a pattern indicating the aggregation relation of the class, and an aggregation relation of the class The class diagram conversion device according to claim 2, further comprising: a conversion pattern for converting each of the patterns having an abstract class in between.
The invention according to claim 7 includes, as the conversion pattern stored in the conversion pattern information, a conversion pattern that mutually converts a pattern that realizes an inheritance relationship by the delegation and a pattern that indicates the inheritance relationship. The class diagram conversion device according to claim 2 is characterized.

The invention according to claim 8, computer, and a class diagram conversion program to function as the respective means constituting the class diagram conversion device according to any one of claims 1 to 7.

By doing in this way, a computer can be functioned as each means which comprises the class diagram conversion apparatus of any one of Claim 1 thru | or 7 .

  According to the present invention, it is possible to provide a class diagram conversion device and a class diagram conversion program that support design of a class diagram with an optimal design pattern when reviewing a class diagram once created.

It is a functional block diagram which shows the structural example of the class diagram conversion apparatus which concerns on this embodiment. It is a figure for demonstrating the pattern of the same type expression which the class diagram conversion apparatus concerning this embodiment handles. It is a figure which shows an example of the class diagram information of pattern [1] stored in the class diagram information database which concerns on this embodiment. It is a figure which shows an example of the class diagram information of pattern [2] stored in the class diagram information database which concerns on this embodiment. It is a figure which shows an example of the class diagram information of the pattern [3] stored in the class diagram information database concerning this embodiment. It is a figure which shows an example of the class diagram information of pattern [4] stored in the class diagram information database which concerns on this embodiment. It is a figure which shows an example of the class diagram information of the pattern [5] stored in the class diagram information database concerning this embodiment. It is a figure which shows an example of the class diagram information of the pattern [6] stored in the class diagram information database concerning this embodiment. It is a figure which shows the other example of the same type expression which the class diagram conversion apparatus concerning this embodiment handles. It is a figure which shows the other example of the class diagram information of the pattern [5] stored in the class diagram information database which concerns on this embodiment. It is a flowchart which shows the flow of the class diagram conversion process which the class diagram conversion apparatus concerning this embodiment performs. (A) is a conceptual diagram showing the selected class and other components having “relation” when one class is selected as an application location to be converted. (B) is the figure which showed the conceptual diagram of (a) with the class diagram. It is a figure which shows an example of the pre-conversion pattern selection screen which concerns on this embodiment. It is a figure which shows the example of the conversion pattern list screen which concerns on this embodiment. It is a figure which shows the example of the conversion pattern list screen which concerns on this embodiment. It is a figure for demonstrating the class diagram conversion process of the 1st conversion pattern by the class diagram conversion apparatus concerning this embodiment. It is a figure for demonstrating the class diagram conversion process of the 2nd conversion pattern by the class diagram conversion apparatus concerning this embodiment. It is a figure for demonstrating the class diagram conversion process of the 3rd conversion pattern by the class diagram conversion apparatus concerning this embodiment. It is a figure for demonstrating the class diagram conversion process of the 4th conversion pattern by the class diagram conversion apparatus concerning this embodiment. It is a figure for demonstrating the class diagram conversion process of the 5th conversion pattern by the class diagram conversion apparatus concerning this embodiment. It is a figure for demonstrating the class diagram conversion process of the 6th conversion pattern by the class diagram conversion apparatus concerning this embodiment. It is a figure for demonstrating the class diagram conversion process of the 7th conversion pattern by the class diagram conversion apparatus concerning this embodiment. It is a figure for demonstrating the class diagram conversion process of the 8th conversion pattern by the class diagram conversion apparatus concerning this embodiment. It is a figure for demonstrating the class diagram conversion process of the 9th conversion pattern by the class diagram conversion apparatus concerning this embodiment. It is a figure for demonstrating the class diagram conversion process of the 10th conversion pattern by the class diagram conversion apparatus concerning this embodiment. It is a figure for demonstrating the example of application of the conventional design pattern.

  Next, a mode for carrying out the present invention (hereinafter referred to as “the present embodiment”) will be described in detail with reference to the drawings as appropriate.

<Prerequisite technology>
First, a technique that is a premise of the present invention will be described.

(Application of design pattern)
The application of design patterns in software development based on object orientation is generally composed of the following five stages.

(1) Situation understanding stage This is the stage where the designer understands the modeling object. At this stage, the designer visualizes the model using a modeling tool or the like, and deepens the understanding of the modeling object.
(2) Design pattern selection stage The designer selects a design pattern written in UML from the design pattern catalog.
(3) Application Location Determination Stage on Model / Code The designer determines an applicable location for the selected design pattern using the design model / implementation code. At present, a function that automatically specifies the application location by a tool has not been developed, and the designer manually determines using a modeling tool.
(4) Deployment stage The components (classes, attributes, etc.) determined in the application location determination stage in (3) above and the roles that make up the design pattern (instead of specific classes, their roles and behavior are abstracted) Are associated with each other), and the associated constituent elements are converted and arranged so as to match the design pattern. Currently, there exists a modeling tool having a function of automatically converting and arranging after a designer associates components (see Non-Patent Document 1).
(5) Peripheral adjustment stage The periphery of the part where the design pattern is developed in the development stage (4) is checked for any defects compared to before development. At present, it is necessary for the designer to determine whether or not there is a final defect. Therefore, even when the components are automatically converted / arranged in the expansion stage (4), the designer determines whether there is a defect and corrects it manually.

An application example of the above design pattern will be described with reference to FIG.
First, the designer extracts the components of the classes “A”, “B”, “C”, “D”, and “E” shown in FIG. 26A in the situation understanding stage of (1). To do.
In the design pattern selection stage (2), the designer selects the “Observer pattern” shown in FIG. 26B as a design pattern from the design pattern catalog. The “Observer pattern” is composed of four roles (“Subject”, “Observer”, “ConcreteSubject”, “ConcreteObserver”) as shown in FIG. It is tied by the “relation” shown in. In the following, “relation” indicating a connection relationship between classes defined as a UML notation is described as a relationship with key brackets (“relation”).

  Next, in the application location determination stage of (3), the designer determines the application location of the design pattern from the components shown in FIG. Here, it is assumed that all components of classes “A”, “B”, “C”, “D”, and “E” have been determined by the designer.

Subsequently, in the development stage of (4), each component is associated with a role constituting the design pattern.
Here, as shown in FIG. 26C, the designer associates the class “A” with “Subject”, the class “C” with “Observer”, and the class “B” with “ConcreteSubject”. , And class “D” and class “E” are associated with “ConcreteObserver”.
Then, after associating each component with the role constituting the design pattern by the designer, the modeling tool automatically converts and arranges and designs a class diagram as shown in FIG. That is, the class diagram shown in FIG. 26D is a result of applying the components shown in FIG. 26A to the “Observer pattern” design pattern shown in FIG.

  Next, in the surrounding adjustment stage of (5), the designer determines whether there is a defect in the class diagram shown in FIG. 26D, and if there is a defect, manually corrects it.

  As described above, the function of the current modeling tool using the design pattern is to display the design pattern described in UML, and manually associate the displayed design pattern role with each component to be applied. The conversion and placement of each component is automatically performed so as to match the design pattern.

(Refactoring)
As a function similar to the application of a design pattern, “refactoring” of a program is known. This refactoring is a program improvement technique for organizing the internal structure of source code without changing the operation seen from the outside of the program. However, tools using a refactoring catalog for supporting this refactoring are usually limited to work support at the program level.

As described above, in the refactoring support tool for the software product of the downstream process such as the source code program and the implementation model, and the conventional design pattern application support tool described above, the upstream process (conceptual modeling process and logical modeling process) It was not possible to support pattern application and class diagram conversion in editing class diagrams.
In particular, conventional modeling tools that support design patterns simply display a design pattern catalog written in UML. To determine which pattern should be selected from many patterns, the design pattern catalog is used. It required advanced knowledge of the individual design patterns described. In other words, since there are multiple ways to represent a model for a model to be designed, the designer may be confused as to which design pattern (structure) should be represented when attempting class design. In many cases, once a class diagram is designed with a certain design pattern, trial and error is required to determine the optimum design pattern by applying it to another design pattern, which has a great deal of labor.

In particular, management system modeling using SID (Shared Information and Data Model), which is an information model provided by TMForum (TMF: TeleManagement Forum) that defines standard technologies for management systems for telecommunication (TeleManagement Forum GB922, “ Information Framework (SID): Concepts and Principles, “Version 7.15, March 2011.” has the following features and further problems.
Since the SID is a conceptual model, it is necessary to convert the structure that does not depend on the implementation appearing in the SID class diagram into a structure that takes into consideration the implementation method, the language to be implemented, middleware, and the like as the development process proceeds.
In SID modeling, a unique SID pattern (design pattern) that is not found in the pattern catalog is applied. In particular, “Entity Characteristic Pattern” (Pattern [4] TMF SID Spec.Char. Pattern in FIG. 2 to be described later) can be added by adding an instance without changing the existing class even if it is desired to add an attribute for a certain class. It is a design pattern with extensibility that can be done. This unique SID pattern is not included in the conventional design pattern catalog, and the designer cannot use it for class diagram design.

  Based on these characteristics, in order to support object-oriented software development including management system modeling using SID, the class diagram conversion device and class diagram conversion program according to the present embodiment are based on existing design patterns and refactoring. It was not limited, and the pattern which was likely to be in doubt about which design pattern the designer selects at the time of class design was targeted. In addition, advanced knowledge about existing design patterns and refactoring is not required, and it is possible to support review and correction of class diagrams.

<Overview>
Next, an outline of processing executed by the class diagram conversion apparatus 1 according to the present embodiment will be described. The class diagram conversion apparatus 1 according to the present embodiment presents a pattern (design pattern) different from the created class diagram when examining the created class diagram (that is, reviewing the class diagram). Select the optimal pattern from the presented patterns and convert the class diagram.

  In this embodiment, a pattern change judgment (conversion pattern) that frequently appears when a class diagram once created with a pattern is changed to a class diagram of another pattern is classified as “conversion pattern information”. It is stored in the class diagram conversion device 1. Then, other convertible patterns for the class diagram once created with a certain pattern are displayed based on the conversion pattern information stored in the class diagram conversion device 1, and the designer can select another pattern after conversion. To convert the class diagram display to the selected pattern.

The class diagram conversion apparatus 1 of the present embodiment targets the following six types as target classes and their “related” patterns (design patterns). Details will be described later with reference to FIGS.
Pattern [1]: Relationship between class and attribute Pattern [2]: Aggregation relationship of class Pattern [3]: Aggregation relationship of class + abstract class between Patterns [4]: TMF SID Spec. Char. pattern
(Entity Specification Characteristic pattern)
Pattern [5]: Realization of inheritance relationship by delegation Pattern [6]: Inheritance relationship

Among the patterns [1] to [6], the class diagram conversion apparatus 1 handles the following 10 conversion patterns that can be converted to each other. Further, the present embodiment is characterized in that classes, attributes, and objects, which are usually different concepts when describing the structure of a class diagram, are handled as equivalent components in the process of converting the class diagram. Details will be described later with reference to FIGS. 2, 16 to 25, and the like.
(First conversion pattern): Pattern [1] → [2]
(Second conversion pattern): Pattern [2] → [1]
(Third conversion pattern): Pattern [2] → [3]
(Fourth conversion pattern): Pattern [3] → [2]
(Fifth conversion pattern): Pattern [3] → [4]
(Sixth conversion pattern): Pattern [4] → [3]
(Seventh conversion pattern): Pattern [2] → [4]
(Eighth conversion pattern): Pattern “4” → “2”
(9th conversion pattern): Pattern [5] → [6]
(10th conversion pattern): Pattern [6] → [5]

In the present embodiment, the class diagram conversion apparatus 1 identifies a pattern of a class diagram before conversion, and a conversion pattern that can be converted into a pattern of a different expression from a class in the pattern, a combination of the classes, “relation”, or the like. The converted pattern) is presented to the designer and selected. Then, the class diagram conversion device 1 converts the class diagram pattern based on the selected conversion pattern and displays it.
Hereinafter, the configuration of the class diagram conversion apparatus 1 will be described in detail.

<Configuration of class diagram conversion device>
FIG. 1 is a functional block diagram illustrating a configuration example of the class diagram conversion apparatus 1 according to the present embodiment.
The class diagram conversion device 1 expresses the same contents as the class diagram based on the class diagram once created in a certain pattern (hereinafter, sometimes referred to as “same type expression”). The class of another pattern (design pattern) This is a device that displays a diagram and converts it into a class diagram of another pattern selected by the designer.
As shown in FIG. 1, the class diagram conversion device 1 is connected to an input device 3 and a display device 2. For example, the input device 3 includes a mouse, a keyboard, a touch panel, and the like. Further, the display device 2 includes a liquid crystal display or the like.
The class diagram conversion apparatus 1 includes a control unit 10, an input / output unit 20 (input unit), a memory unit 30, and a storage unit 40 (storage unit).

  The control unit 10 is responsible for the overall control of converting a class diagram once created with a pattern into a class diagram of another pattern and displaying it. The display processing unit 11 (display processing means) and the input / output information processing unit 12 With.

  The display processing unit 11 (display processing means) is responsible for overall processing for converting a class diagram, and includes a class diagram display unit 111, a conversion pattern display unit 112, and a class diagram conversion processing unit 113. .

  The class diagram display unit 111 displays the class diagram on the display device 2 based on the class diagram information 100 (details will be described later), which is information indicating the class, attribute, “relation”, etc., and among the components of the class diagram, The designer is allowed to select a class, a combination of classes, and the like, which will be applied to class diagram conversion.

  The conversion pattern display unit 112 corresponds to which pattern among the predetermined patterns (six types of patterns) indicated by the class and its “relation” for the application part of the class diagram conversion selected by the designer. Identify what to do. Then, the conversion pattern display unit 112 extracts a conversion pattern that can be converted as a homomorphic expression with respect to the identified pattern with reference to conversion pattern information stored in the conversion pattern database 42 to be described later. ”List screen (conversion pattern list screen 300)” (see FIG. 14 and FIG. 15), and displays it on the display device 2. The conversion pattern display unit 112 receives conversion pattern selection information based on the “applicable conversion pattern list screen (conversion pattern list screen 300)”.

  Based on the acquired conversion pattern selection information, the class diagram conversion processing unit 113 converts the constituent elements of the class diagram to be applied based on the selected conversion pattern, generates a converted class diagram, and displays it. Displayed on the device 2.

  The input / output information processing unit 12 delivers input information acquired from the input device 3 via the input / output unit 20 to the display processing unit 11, and displays output information from the display processing unit 11 via the input / output unit 20. Transmit to device 2.

  The input / output unit 20 (input unit) receives information (selection information and the like) related to processing of the control unit 10 from a mouse, a keyboard, a touch panel, or the like that is the input device 3. In addition, information related to the class diagram generated by the control unit 10 is output to the display device 2. The input / output unit 20 includes an input interface and an output interface.

  The memory unit 30 includes storage means such as a RAM (Random Access Memory), and temporarily stores information necessary for the processing of the control unit 10.

  The storage unit 40 (storage means) includes a class diagram information database 41 that stores class diagram information 100 (see FIGS. 3 to 8 to be described later) that is information necessary for generating a class diagram, a conversion pattern database 42, Is memorized.

In this class diagram information 100, as information for displaying the class diagram on the display device 2, as shown in FIG. 3 to FIG. 8 etc., a relation type 101, a relation ID 102, a From element type 103, a From element ID 104, To Data items of an element type 105, a To element ID 106, a From element name 107, a To element name 108, and display related information 109 are included.
The association type 101 stores the type of “association” between the components of the class diagram. For example, “attribute (CLASS-ATTRIBUTE)” indicating the relationship between the class and the attribute of the class, -“AGGREGATION” that indicates a partial relationship, “INHERITANCE” that indicates that another class inherits the characteristics (attributes and operations) of a class, and an example of a class and its class Stores an “instance (CLASS-INSTANCE)” indicating a relationship with an object.
The association ID 102 is an identifier unique to the “association” between the components in the class diagram (class diagram information 100).

The From element type 103 stores the type of the higher-order constituent element among the two constituent elements of interest in a class diagram, for example, a class, an attribute, and an object.
The From element ID 104 stores a unique identifier in the class diagram (class diagram information 100) for the component of the From element type 103.
Note that the component (class) indicated by the From element type 103 and the From element ID 104 in the class diagram information 100 may be referred to as “upper class” below.

The To element type 105 stores the type of the lower-level component among the two components of interest in a certain class diagram, and stores, for example, a class, an attribute, and an object.
The To element ID 106 stores an identifier unique to the component of the To element type 105 in the class diagram (class diagram information 100).
The component (class) indicated by the To element type 105 and the To element ID 106 in the class diagram information 100 may be hereinafter referred to as “lower class”.

The From element name 107 stores a specific name of the component indicated by the From element type 103 and the From element ID 104.
The To element name 108 stores a specific name of the component indicated by the To element type 105 and the To element ID 106.

  The display related information 109 stores the shape and position information for displaying the class diagram on the screen. For example, the shape of the class on the screen (rectangle, etc.), the position information on the screen (for example, coordinate information of four points in the case of a rectangle), and the like are stored. In addition, as the shape of the “relation” indicated by the line connecting the constituent elements, if it is “inherit”, a white triangle (△) arrow, and if it is “aggregation”, a white diamond on the class side indicating the whole (◇) and the like are stored, and when there is a direction between the components, information on the direction of the arrow is stored.

  In this embodiment, the class diagram structure is described in the From element type 103 and the To element type 105 in order to treat each of the class, attribute, and object as a constituent element that is a target of the process of converting the class diagram. In this case, classes, attributes, and objects that are usually different concepts are stored as equal information.

  Returning to FIG. 1, in the conversion pattern database 42, pattern determination logic for specifying which of the predetermined patterns (six types of patterns) the application portion to be converted selected from the class diagram corresponds to The conversion pattern information indicating the 10 types of conversion patterns that can be converted to each other as the same type expression is stored (details will be described later). In this pattern determination logic, specifically, for a certain class selected as an application location to be converted from the class diagram, the record storing the class is in a predetermined pattern (six types of patterns). When a combination of a plurality of classes is selected as an application location to be converted from the logic for determining whether or not there is a possibility of being included from the class diagram, the combination of the plurality of classes is changed to a predetermined pattern (6 Type pattern) and logic for specifying the type are stored.

The storage unit 40 includes storage means such as a hard disk and a flash memory, and stores a program (class diagram conversion program) for performing the processing of the control unit 10 and the like.
The function of the control unit 10 is realized, for example, by a CPU (Central Processing Unit) developing and executing a program (class diagram conversion program) stored in the storage unit 40 of the class diagram conversion device 1 in the memory unit 30. Is done.

  Here, the six types of patterns (design patterns) indicated by the “association” with the class and the above-described ten types of conversion patterns that can be mutually converted as the same type expression will be specifically described.

(Details of 6 patterns)
FIG. 2 is a diagram for explaining patterns of isomorphic expressions handled by the class diagram conversion apparatus 1 according to the present embodiment. FIG. 2 shows combinations of six types of patterns indicated by “association” between classes and patterns having the same type expression, that is, convertible patterns (conversion patterns).

≪Pattern [1] ≫
As shown in FIG. 2, the pattern [1] indicates “relationship between class and attribute”. Based on the UML description method, a class is represented by a rectangle as a shape on the screen, and the class name of the class (“Class A” in [1] in FIG. 2) and the attribute name of the class (in FIG. 2). In [1], “attribute a”, “attribute b”, “attribute c”) are displayed.

FIG. 3 shows class diagram information 100 (100a) for generating the “relationship between class and attribute” of the pattern [1] on the screen. FIG. 3 is a diagram showing an example of the class diagram information 100 (100a) of the pattern [1] stored in the class diagram information database 41. As shown in FIG.
In the class diagram information 100 (100a) of the pattern [1], for example, as shown in the first row, “attribute (CLASS-ATTRIBUTE)” is stored as the relation type 101, and “1 (1- 1) ”,“ Class ”is stored in the From element type 103,“ A ”is stored in the From element ID 104,“ Attribute ”is stored in the To element type 105, and“ a ”is stored in the To element ID 106. That is, information indicating that the relationship between the class “A” and the attribute “a” is “attribute (CLASS-ATTRIBUTE)” is stored. The same applies to the attribute “b” and the attribute “c”.
Note that the pattern determination logic stored in the conversion pattern database 42 may include, in the pattern [1], a record in which the class is stored for a certain class selected as an application location to be converted from the class diagram. As a logic for determining whether or not there is a property, the relation type 101 of the record of the class diagram information 100 is information of “attribute (CLASS-ATTRIBUTE)”, and the From element type 103 of the record is “ "Class" and the To element type 105 is "attribute" (logic 1-1) are stored. In addition, when a combination of a plurality of classes is selected as an application location to be converted from the class diagram, each of the plurality of classes is stored as logic for specifying the combination of the plurality of classes as the pattern [1]. In the record, it is stored that each of the conditions satisfies the condition (logic 1-1) described above and the From element ID 104 of each record is the same (logic 1-2).

≪Pattern [2] ≫
Pattern [2] shown in FIG. 2 indicates “class aggregation relationship”. In aggregation (AGGREGATION), classes are connected by a line with a white diamond (◇) on the class side indicating the whole. The class “a”, the class “b”, and the class “c” indicate a relationship that is a part of the class “A” (entire).

FIG. 4 shows class diagram information 100 (100b) for generating the “class aggregation relationship” of this pattern [2] on the screen. FIG. 4 is a diagram illustrating an example of the class diagram information 100 (100b) of the pattern [2] stored in the class diagram information database 41.
In the class diagram information 100 (100b) of the pattern [2], for example, “AGGREGATION” is stored as the relation type 101 as shown in the first line, and “2 (2-1)” is stored in the relation ID 102. "," Class "is stored in the From element type 103," A "is stored in the From element ID 104," Class "is stored in the To element type 105, and" a "is stored in the To element ID 106. That is, information indicating that the class “A” and the class “a” are in an aggregated (whole-part) relationship is stored. The same applies to the class “b” and the class “c”. Therefore, the class “A” indicates that the classes “a”, “b”, and “c” are in a relation to be aggregated.
Note that the pattern determination logic stored in the conversion pattern database 42 may include a record in which the class is stored in the pattern [2] for one class selected as an application location to be converted from the class diagram. As a logic for determining whether or not there is a property, the relation type 101 of the record in the class diagram information 100 is “AGGREGATION” information, and the From element type 103 of the record is “class”. And that the To element type 105 is “class” (logic 2-1). In addition, when a combination of a plurality of classes is selected as an application location to be converted from the class diagram, each of the plurality of classes is stored as logic for specifying the combination of the plurality of classes as the pattern [2]. In the record, it is stored that each of the conditions satisfies the condition (logic 2-1) described above and the From element ID 104 of each record is the same (logic 2-2).

≪Pattern [3] ≫
The pattern [3] illustrated in FIG. 2 indicates “abstract class between classes + abstract class”. This abstract class (“Class R” in [3] in FIG. 2) is common to its lower classes (“Class a”, “Class b”, and “Class c” in [3] in FIG. 2). Attributes, operations, roles, and the like are collected as one class, and a lower class is expressed as inheriting an abstract class that is a higher class. The abstract class (class “R”) indicates a relationship that is aggregated into a higher class (class “A” in [3] in FIG. 2).

FIG. 5 shows class diagram information 100 (100c) for generating “class aggregation relationship + abstract class between” of the pattern [3] on the screen. FIG. 5 is a diagram illustrating an example of the class diagram information 100 (100c) of the pattern [3] stored in the class diagram information database 41.
In the class diagram information 100 (100c) of the pattern [3], for example, “AGGREGATION” is stored as the related type 101 in the first row, “2” is stored in the related ID 102, and “From” is stored in the From element type 103. “Class”, “A” is stored in the From element ID 104, “Class” is stored in the To element type 105, and “R” is stored in the To element ID 106.
In the second row, “INHERITANCE” is stored as the relationship type 101, “3 (3-1)” is stored in the relationship ID 102, “class” is stored in the From element type 103, and “R” is stored in the From element ID 104. , “Class” is stored in the To element type 105, and “a” is stored in the To element ID 106. The third row and the fourth row are stored in the same manner, and “b” and “c” are stored in the To element ID 106, respectively.
Therefore, the class “A” aggregates the class “R”, and the classes “a”, “b”, and “c” have a relationship of inheriting the class “R”.
Note that the pattern determination logic stored in the conversion pattern database 42 may include a record in which the class is stored in the pattern [3] for a certain class selected as an application location to be converted from the class diagram. For determining whether or not there is a property, and when a combination of a plurality of classes is selected as an application location to be converted from the class diagram, the combination of the plurality of classes is specified as a pattern [3] As logic, at least one record of “AGGREGATION” and “INHERITANCE” is associated with each of the plurality of records including the selected class of the class diagram information 100. The To element ID 106 of the aggregated record and the From element ID 104 of the inherited record are the same. Paid.

≪Pattern [4] ≫
The pattern [4] shown in FIG. 2 indicates a “TMF SID Spec.Char. Pattern”. This “TMF SID Spec.Char. Pattern” is a unique SID pattern, and a class specific to this pattern is associated with a specific object of the class as information included in the class.
In the example shown in [4] of FIG. 2, the class “SA” includes the object “A” as data, and the class “SA” has a relationship of aggregating the class “SAC”, and the class “SAC”. "Includes objects" a "," b ", and" c "as data.

FIG. 6 shows class diagram information 100 (100d) for generating the “TMF SID Spec.Char. Pattern” of this pattern [4] on the screen. FIG. 6 is a diagram illustrating an example of the class diagram information 100 (100d) of the pattern [4] stored in the class diagram information database 41.
In the class diagram information 100 (100d) of the pattern [4], for example, “Instance (CLASS-INSTANCE)” is stored as the relationship type 101 in the first row, and “4 (4-1)” is stored in the relationship ID 102. , “From” is stored in the From element type 103, “SA” is stored in the From element ID 104, “Object” is stored in the To element type 105, and “A” is stored in the To element ID 106.
In the second row, “AGGREGATION” is stored as the relationship type 101, “2” is stored in the relationship ID 102, “class” is stored in the From element type 103, “SA” is stored in the From element ID 104, and the To element type 105 is stored. “Class” is stored in “To”, and “SAC” is stored in To element ID 106.
In the third row, “Instance (CLASS-INSTANCE)” is stored as the relationship type 101, “4 (4-2)” is stored in the relationship ID 102, “Class” is stored in the From element type 103, and “SAC” is stored in the From element ID 104. "," Object "is stored in the To element type 105, and" a "is stored in the To element ID 106. The fourth row and the fifth row are also stored in the same manner, and “b” and “c” are stored in the To element ID 106, respectively.
In the pattern determination logic stored in the conversion pattern database 42, when a combination of a plurality of classes is selected as an application location to be converted from the class diagram, the combination of the plurality of classes is identified as a pattern [4]. As a logic for this, at least one record of “AGGREGATION” and “Instance (CLASS-INSTANCE)” exists in each of the plurality of records of the class diagram information 100. That the same class as the class indicated in the From element type 103 and From element ID 104 of the record of the record exists in the From element type 103 and From element ID 104 of the record of the instance, and the To element type 105 and To element of the aggregated record Other than the class shown in ID106 Is stored in the From element type 103 and the From element ID 104 of the instance record.

≪Pattern [5] ≫
Pattern [5] shown in FIG. 2 indicates “realization of inheritance relationship by delegation”. Here, “delegation” refers to entrusting processing of a message requested to its own class (object) to another class (object). In the example shown in [5] of FIG. 2, the class “B” and the class “A” have a delegation relationship, and the class “B” entrusts processing to the class “A”. In the class diagram, for example, as shown in [5] of FIG. 2, this delegation relationship is a class in which a white rhombus (◇) indicating aggregation is attached to the class side indicating the delegation source and the delegation destination is indicated. It is expressed by being connected by a line with an arrow (→) on the side.

FIG. 7 shows class diagram information 100 (100e) for generating the “realization of inheritance relationship by delegation” of this pattern [5] on the screen. FIG. 7 is a diagram showing an example of the class diagram information 100 (100e) of the pattern [5] stored in the class diagram information database 41.
In the class diagram information 100 (100e) of pattern [5], “AGGREGATION” is stored as the relation type 101 in the fourth line, “2” is stored in the related ID 102, and “class” is stored in the From element type 103. , “B” is stored in the From element ID 104, “Class” is stored in the To element type 105, and “A” is stored in the To element ID 106. The display related information 109 stores that there is an arrow (→) from the class “B” to the class “A” (indicated as “B” → “A” (delegation) in FIG. 7). The
Note that the pattern determination logic stored in the conversion pattern database 42 includes, for a certain class selected as an application location to be converted from the class diagram, whether the record storing the class is included in the pattern [5]. As the logic for determining whether or not the relationship type 101 of the record of the class diagram information 100 is information of “AGGREGATION”, the From element type 103 and the To element type 105 of the record of the aggregation are Further, it is stored that the information of the arrow indicating the delegation destination exists in the display related information 109 of the aggregated record (logic 5-1). In addition, when a combination of a plurality of classes is selected as an application location to be converted from the class diagram, each of the plurality of classes is stored as logic for specifying the combination of the plurality of classes as the pattern [5]. In the record, it is stored that each of the conditions satisfies the above-mentioned (logic 5-1) and the From element ID 104 of each record is the same (logic 5-2).

≪Pattern [6] ≫
Pattern [6] shown in FIG. 2 indicates “inheritance relationship”. The example shown in [6] of FIG. 2 indicates that the class “B” has a relationship of inheriting the class “A”.

FIG. 8 shows class diagram information 100 (100f) for generating the “inheritance relationship” of this pattern [6] on the screen. FIG. 8 is a diagram illustrating an example of the class diagram information 100 (100f) of the pattern [6] stored in the class diagram information database 41.
In the class diagram information 100 (100f) of the pattern [6], “INHERITANCE” is stored as the relation type 101 in the fourth line, “3” is stored in the related ID 102, and “class” is stored in the From element type 103. , “A” is stored in the From element ID 104, “Class” is stored in the To element type 105, and “B” is stored in the To element ID 106. This indicates that the class “B” inherits the class “A”.
Note that the pattern determination logic stored in the conversion pattern database 42 includes, for a certain class selected as an application location to be converted from the class diagram, whether the record storing the class is included in the pattern [6]. As the logic for determining whether or not the relationship type 101 of the record in the class diagram information 100 is “INHRITANCE” information, the From element type 103 and the To element type 105 of the inherited record are “Class” (logic 6-1) is stored. In addition, when a combination of a plurality of classes is selected as an application location to be converted from the class diagram, each of the plurality of classes stored as logic for specifying the combination of the plurality of classes as the pattern [6] In the record, it is stored that each of the records satisfies the condition (logic 6-1) described above and the From element ID 104 of each record is the same (logic 6-2).

  When determining the pattern of the application location to be converted, the relation type 101 is “attribute” as in the class diagram information 100 (100a) of “relationship between class and attribute” of the pattern [1] shown in FIG. In the case of only the “CLASS-ATTRIBUTE” record, the determination regarding the pattern [1] is performed based on (logic 1-1) or (logic 1-2). On the other hand, when the record of the target class diagram information 100 includes a record of “attribute (CLASS-ATTRIBUTE)” and other “related” records (for example, see FIG. 8), the record of the attribute Performs a determination on the pattern [2] to the pattern [6] with respect to a record of “related” other than the attribute without considering the record of the attribute as a determination target, as a unit with the class including the attribute.

(Conversion pattern of isomorphic expression)
Next, a conversion pattern which is a combination that can be mutually converted as the same type expression among the above-described six types of patterns will be described with reference to FIG. In FIG. 2, double arrows (⇔) are shown between patterns that are of the same type and can be converted to each other.

  As described above, there are 10 combinations of conversion patterns of the same type expression. This will be specifically described below.

As shown in FIG. 2, the “class and attribute relationship” of pattern [1] and the “class aggregation relationship” of pattern [2] can be converted into each other.
This is equivalent to the element of each attribute included in the class “A” of the pattern [1] being reconstituted with the class concept and aggregated in the class A as in the pattern [2]. (First conversion pattern: pattern [1] → [2]). Conversely, the lower class indicated by the aggregation relation of pattern [2] may be reconsidered as an attribute of the upper class as in pattern [1] (second conversion pattern: pattern [ 2] → [1]).

As shown in FIG. 2, the “class aggregation relationship” of pattern [2] and the “class aggregation relationship + abstract class” of pattern [3] can be converted into each other.
This is because the lower class in the “Class Aggregation Relationship” of pattern [2] is extracted and the attributes, operations, roles, etc. common to the lower class are extracted and a new abstract class is provided as in pattern [3]. This is because the abstract class may be regarded as equivalent to inheriting a lower class (third conversion pattern: pattern [2] → [3]). Conversely, the attributes, operations, roles, etc. common to the lower classes as in pattern [3] are not collected as an abstract class using inheritance relationships, and individual lower classes and patterns as in pattern [2]. In some cases, higher classes can be regarded as an aggregated relationship (fourth conversion pattern: pattern [3] → [2]).

As shown in FIG. 2, the “class aggregation relationship + abstract class” of pattern [3] and the “TMF SID Spec.Char. Pattern” of pattern [4] can be converted into each other.
This is because each class other than the abstract class shown in the pattern [3] may be instantiated into an object, and may be included as higher class data as shown in the pattern [4] ( Fifth conversion pattern: pattern [3] → [4]). Conversely, an object instantiated as in pattern [4] may be deinstantiated and expressed as a class as in pattern [3] (sixth conversion pattern: pattern [4]). → [3]).

As shown in FIG. 2, the “class aggregation relationship” of pattern [2] and the “TMF SID Spec.Char. Pattern” of pattern [4] can be converted into each other.
This is because there are cases where each class shown in pattern [2] is instantiated into an object, and as shown in pattern [4], attributes common to the object can be included as a new higher class. This is due to the fact (seventh conversion pattern: pattern [2] → [4]). Conversely, an object instantiated as in pattern [4] is de-instantiated as in pattern [2], and attributes and the like common to the objects are expressed as individual classes without being a higher class. (8th conversion pattern: pattern [4] → [2]).

As shown in FIG. 2, “realization of inheritance relationship by delegation” of pattern [5] and “inheritance relationship” of pattern [6] can be converted into each other.
This is because, for example, when class “B” delegates processing to class “A”, that is, in a delegation relationship, class “A” and class “B” are in an inheritance relationship, that is, class “A”. (9th conversion pattern: pattern [5] → [6]). On the other hand, as shown in pattern [6], when class “B” inherits the characteristics (attributes, operations) of class “A”, class “B” entrusts processing to class “A”. That is, there are cases where it can be expressed as a delegation relationship (tenth conversion pattern: pattern [6] → [5]).

  In addition to the first conversion pattern to the tenth conversion pattern, which is the class diagram conversion process based on the six types of patterns shown in the present embodiment, other patterns (design patterns) may be processed. These conversion patterns may be executed.

As another specific example of the conversion pattern, as shown in FIG. 9, the “class aggregation relationship” of the pattern [2] can be mutually converted with the “realization of the inheritance relationship by delegation” of the pattern [5]. A conversion pattern can be considered. This has a relationship between the upper class (“class A” in FIG. 9) and the lower class (“class a, b, c” in FIG. 9) indicated by the aggregation (whole-part) of pattern [2]. In some cases, the upper class may be expressed as a relationship that delegates processing to the lower class, that is, a delegation relationship (hereinafter referred to as “11th conversion pattern: pattern [2] → [5]”). . Conversely, as shown in pattern [5], when the upper class ("class A") is in a relationship of delegating processing to the lower class ("class a, b, c"), the upper class This is because there is a case where these classes are considered to be equivalent to the relationship in which lower classes are aggregated (hereinafter referred to as “twelfth conversion pattern: pattern [5] → [2]”).
Note that the class diagram information 100 (100g) for generating “realization of inheritance relationship by delegation” of the pattern [5] after the pattern [2] has been converted by the eleventh conversion pattern is displayed on the screen. 10 shows. As shown in FIG. 10, the class diagram information 100 (100g) of “realization of inheritance relationship by delegation” of pattern [5] is the class diagram of “class aggregation relationship” of pattern [2] shown in FIG. An arrow (→) indicating delegation from the higher class to the lower class is stored in the item of the display related information 109 of the aggregated record of the information 100 (100b).
The class diagram conversion apparatus 1 according to the present embodiment uses the eleventh conversion pattern (pattern [2] → [5]) and the twelfth conversion pattern (pattern [5] → [2]) as the conversion pattern information described above. It can also be included.

  When attention is paid to each of the six types of patterns in the first conversion pattern to the tenth conversion pattern described above, it can be understood as “conversion pattern information” that can be converted from the pattern before conversion to the pattern after conversion as shown below. it can.

Pattern [1] → [2]
Pattern [2] → [1], [3], [4]
Pattern [3] → [2], [4]
Pattern [4] → [2], [3]
Pattern [5] → [6]
Pattern [6] → [5]

For example, when attention is paid to the pattern [2], the conversion pattern information indicates that the class diagram expressed in the pattern [2] can be converted into the patterns [1], [3], and [4]. .
This conversion pattern information is stored in the conversion pattern database 42 (see FIG. 1).

  When the class diagram conversion device 1 according to the present embodiment determines that the pattern of the class diagram before conversion is any one of the patterns [1] to [6], the class diagram conversion device 1 stores the pattern in the conversion pattern database 42. The above conversion pattern information is referred to, the above conversion pattern that can be converted for the determined pattern is displayed, and the designer is made to select it. Then, the class diagram conversion device 1 converts the class diagram into the selected pattern and displays it.

<Class diagram conversion process>
Next, a class diagram conversion process executed by the class diagram conversion device 1 according to the present embodiment will be described.

  FIG. 11 is a flowchart showing the flow of class diagram conversion processing executed by the class diagram conversion device 1 according to this embodiment. The class diagram information database 41 of the storage unit 40 of the class diagram conversion apparatus 1 stores in advance class diagram information 100 (class diagram information 100 before conversion) that is information for configuring a class diagram before conversion. It is assumed that

  First, the class diagram display unit 111 (see FIG. 1) of the class diagram conversion device 1 acquires the class diagram information 100 before conversion from the class diagram information database 41 (step S10) and displays it on the display device 2.

Then, the class diagram display unit 111 causes the designer to select an application location to be converted based on the displayed class diagram. Then, the class diagram display unit 111 determines whether or not selection information on the application location of the class diagram has been received from the input device 3 via the input / output unit 20 (step S11). Here, the class diagram display unit 111 waits until the selection information of the application location is input when the selection information of the application location is not received (step S11 → No).
The selection of the application location is specified, for example, by clicking one class (predetermined operation with a mouse or the like) in the class diagram displayed on the screen by the input device 3 by the designer, A combination of classes is simultaneously selected (range designation) by a predetermined operation using a mouse or the like, and a part or all of the configuration of the class diagram is selected as an application location of class diagram conversion.
When the class diagram display unit 111 receives selection information on the application location (step S11 → Yes), the class diagram display unit 111 passes the selection information on the application location to the conversion pattern display unit 112 (see FIG. 1).

  The conversion pattern display unit 112 is based on the configuration specified by the application location selection information in the class diagram information 100 before conversion (hereinafter referred to as “applicable location class diagram information”) (see FIG. 4). Refer to the pattern determination logic stored in (1)), and which pattern corresponds to the application location to be converted among the predetermined patterns (six types of patterns) indicated by the class and its “relation” Is specified (step S12). That is, it identifies which pattern the pattern before conversion corresponds to.

Here, regarding the pattern specifying process before conversion in step S12, the designer selects one class as an application location to be converted, and selects a combination of a plurality of classes as an application location to be converted (range). It will be described in detail separately for the case where it is designated.
When one class is selected by the designer as an application location to be converted, the conversion pattern display unit 112 displays a “related” pattern including the selected class (described later, FIG. 13). The pattern before conversion is specified by allowing the designer to selectively input the pattern before conversion. On the other hand, when a combination of a plurality of classes is selected (range designation) as an application location to be converted, the conversion pattern display unit 112 is based on the pattern determination logic stored in the conversion pattern database 42 (see FIG. 1). Identify the pattern before conversion.

When one class is selected as an application location to be converted, the conversion pattern display unit 112 has other components (classes, attributes, etc.) having an “association” directly connected to the selected class. Object). Specifically, the conversion pattern display unit 112 extracts a record including the selected class from the class diagram information 100 before conversion. In other words, the conversion pattern display unit 112 determines whether the relation type 101 of the extracted record and the selected class are a higher-order component or a lower-order component (hereinafter referred to as “relation” direction). Is determined).
In FIG. 12A, when the class diagram shown in FIG. 12B is displayed on the screen in step S11, the designer selects “class A” as one class, and the “class A”. The conversion pattern display unit 112 displays “attribute X”, “class a”, “class b”, “class c”, and “class B”, which are other components having “relation” directly connected to It is a conceptual diagram when the relation type 101 and the direction of “relation” are determined by extraction. That is, FIG. 12A shows that, in the class diagram information 100 before conversion, one attribute record and three aggregation records are present as records in which class A exists in either the upper class or the lower class. , There are five “related” records, one inheritance record, and the direction of the “related”.

  Next, the conversion pattern display unit 112 displays each component of the extracted other constituent elements (here, “attribute X”, “class a”, “class b”, “class c”, “class B”). Then, the “related” pattern including the selected class is determined based on the pattern determination logic stored in the conversion pattern database 42 (see FIG. 1). Then, the conversion pattern display unit 112 displays the pattern determined for each record as the pre-conversion pattern selection screen 200 (see FIG. 13), and selects the pattern before conversion, that is, the pattern to be converted, to the designer. Let

FIG. 13 is a diagram illustrating an example of the pre-conversion pattern selection screen 200. The pre-conversion pattern selection screen 200 displays a pattern determined based on the pattern determination logic for each record storing the selected class and other extracted components in the class diagram information 100 before conversion. Is done. For example, as shown in FIG. 13, with respect to an attribute record in which “class A” and “attribute X” are stored, the “relationship between class and attribute” of pattern [1] is a pattern determined from that record. Is displayed (reference numeral 210). For the aggregated record in which “class A” and “class a” are stored, the “class aggregation relationship” of pattern [2] is displayed as a pattern determined from the record (reference numeral 220). Similarly, for the aggregated record in which “class A” and “class b” are stored, the “class aggregation relationship” of pattern [2] is displayed as a pattern determined from the record (reference numeral 230). . For the aggregated record in which “class A” and “class c” are stored, the “class aggregation relationship” of pattern [2] is displayed as a pattern determined from the record (reference numeral 240). For the inheritance record in which “class A” and “class B” are stored, the “inheritance relationship” of pattern [6] is displayed as a pattern determined from the record (reference numeral 250).
And the conversion pattern display part 112 specifies the pattern (pattern before conversion) used as conversion object, when the selection button (code | symbol 201) of the pattern selection screen 200 before conversion is selected and input by the designer.

  Further, the conversion pattern display unit 112 may convert the conversion pattern database 42 (see FIG. 1) if the class diagram information of the application location selected by the designer is information in which a combination of a plurality of classes is simultaneously selected (range designation). ) Stored in the pattern determination logic, it is determined in order from pattern [1] to pattern [6] whether or not each pattern (six patterns) corresponds to which pattern corresponds to which pattern. judge.

  Returning to FIG. 11, when one class is selected as an application location to be converted by the designer as a result of step S <b> 12, the conversion pattern display unit 112 displays the pre-conversion pattern selection screen 200 (FIG. 13). When no pattern is selected (when an end button (not shown) is pressed) or when a combination of a plurality of classes is selected as an application location to be converted (range specification), a predetermined pattern ( If none of the six types of patterns) is satisfied, the process is terminated (step S13 → No). On the other hand, in the conversion pattern display unit 112, when any pattern is specified as a pattern before conversion by the designer, or a combination of a plurality of classes corresponds to one of predetermined patterns (six types of patterns). In this case (step S13 → Yes), the process proceeds to the next step S14.

  In step S14, the conversion pattern display unit 112 extracts a conversion pattern that can be converted from the class diagram pattern of the application location with reference to the conversion pattern information stored in the conversion pattern database 42 (see FIG. 1). A conversion pattern list screen 300 (see FIGS. 14 and 15) is generated and displayed on the display device 2.

  FIG. 14 shows an example of a case where one class is selected as an application location to be converted by the designer in an aggregated record storing “class A” and “class a” indicated by reference numeral 220 in FIG. The conversion pattern list screen 300 (300a) when the “class aggregation relationship” of pattern [2] is selected by the designer is shown.

As illustrated in FIG. 14, the conversion pattern list screen 300 (300 a) includes a pattern display area 310 and a conversion pattern display area 320 of application locations. In the pattern display area 310 of the application location, the class diagram pattern (pattern before conversion) of the application location specified in step S12 is displayed. In the conversion pattern display area 320, the converted class diagram pattern is displayed as a conversion pattern that can be converted in the class diagram pattern at the application location. Then, the designer determines a pattern to be converted for the class diagram of the application location by selecting and inputting a selection button (reference numeral 301 (301a, 301b, 301c)) provided for each conversion pattern.
In FIG. 14, “Relationship between class and attribute” of Pattern [1], which is a conversion pattern that can be converted to “Class Aggregation Relationship” of Pattern [2] as an application location in the conversion pattern display area 320. Pattern [3] “Class aggregation relationship + abstract class between” and Pattern [4] “TMF SID Spec.Char. Pattern” are displayed and selected by the designer.

  Also, FIG. 15 shows that when a combination of a plurality of classes is selected (range designation) as an application location to be converted, the conversion pattern display unit 112 changes the class diagram pattern of the application location to “[2] class aggregation. The conversion pattern list screen 300 (300b) when it is determined as “relation” is shown.

  As with the conversion pattern list screen 300 (300a) shown in FIG. 14, in the conversion pattern list screen 300 (300b) shown in FIG. 15, the class diagram of the application location determined in step S12 is displayed in the pattern display area 310 of the application location. Pattern (a pattern before conversion including a plurality of components) is displayed. Also, in the conversion pattern display area 320, a converted class diagram pattern (a pattern composed of a plurality of components) is displayed as a conversion pattern that can be converted in the class diagram pattern of the application location. Then, the designer determines a pattern to be converted for the class diagram of the application location by selecting and inputting a selection button (reference numeral 303 (303a, 303b, 303c)) provided for each conversion pattern.

  Returning to FIG. 11, in step S <b> 15, the conversion pattern display unit 112 selects the conversion pattern by the designer on the conversion pattern list screen 300 displayed on the display device 2. It is determined whether or not conversion pattern selection information has been received. Here, when the conversion pattern display unit 112 has not received the selection information of the conversion pattern (step S15 → No), it waits until it is received. On the other hand, when the conversion pattern display unit 112 receives the conversion pattern selection information (step S15 → Yes), the conversion pattern display unit 112 passes the conversion pattern selection information to the class diagram conversion processing unit 113, and proceeds to the next step S16.

  In step S16, the class diagram conversion processing unit 113 converts the class diagram of the application location based on the conversion pattern selection information received in step S15. Then, the class diagram conversion processing unit 113 displays the converted class diagram on the display device 2. Details of the conversion processing based on each conversion pattern by the class diagram conversion processing unit 113 will be described later.

  By doing in this way, according to the class diagram conversion apparatus 1 according to the present embodiment, in the class diagram pattern of the application location selected by the designer, a conversion pattern that can be converted is presented, and the conversion selected by the designer The class diagram of the application location can be converted by the pattern.

(Class diagram conversion process)
Next, class diagram conversion processing by the class diagram conversion processing unit 113 of the class diagram conversion device 1 according to the present embodiment will be described.
The class diagram conversion processing unit 113 executes class diagram conversion processing based on the above-described (first conversion pattern) to (tenth conversion pattern). Hereinafter, the conversion process of the data of the class diagram information 100 performed when the class diagram conversion processing unit 113 executes the conversion process of each conversion pattern will be specifically described.

<< First conversion pattern: Pattern [1] → [2] >>
FIG. 16 shows the conversion process of the class diagram information 100 when the class diagram conversion apparatus 1 according to the present embodiment executes the first conversion pattern ([1] class and attribute relationship → [2] class aggregation relationship). It is a figure for demonstrating.
FIG. 16 shows class diagram information (reference numeral 1010) before conversion and class diagram information (reference numeral 2010) after conversion by the class diagram conversion processing. In the case of the first conversion pattern, the class diagram conversion processing unit 113 rewrites the association type 101 from “attribute” to “aggregation” and rewrites the To element type 105 from “attribute” to “class” as shown in FIG. .
By executing such data processing, the class diagram conversion processing unit 113 converts the class diagram information 100 from pattern [1] → [2].

  In FIG. 16, only the first line of the class diagram information 100 (100a) in FIG. 3 is shown as the class diagram information (reference numeral 1010) before conversion, and descriptions of the attributes “b” and “c” are omitted. doing. In addition, with regard to the class information after conversion (reference numeral 2010), the descriptions of the classes “b” and “c” are omitted. Hereinafter, in FIG. 17 to FIG. 25 as well, the description of the constituent elements that differ only in the ID (From element ID 104 or To element ID 106) is omitted in the class diagram information 100 before and after conversion.

<< Second conversion pattern: Pattern [2] → [1] >>
FIG. 17 shows the conversion process of the class diagram information 100 when the class diagram conversion device 1 according to the present embodiment executes the second conversion pattern ([2] class aggregation relationship → [1] class and attribute relationship). It is a figure for demonstrating.
FIG. 17 shows class diagram information (reference numeral 1020) before conversion and class diagram information (reference numeral 2020) after conversion by the class diagram conversion processing. In the case of the second conversion pattern, the class diagram conversion processing unit 113 rewrites the association type 101 from “aggregation” to “attribute” and rewrites the To element type 105 from “class” to “attribute” as shown in FIG. .
By executing such data processing, the class diagram conversion processing unit 113 converts the class diagram information 100 from pattern [2] to [1].

<< Third conversion pattern: Pattern [2] → [3] >>
FIG. 18 shows class diagram information 100 when the class diagram conversion device 1 according to the present embodiment executes the third conversion pattern ([2] class aggregation relationship → [3] class aggregation relationship + abstract class). It is a figure for demonstrating this conversion process.
FIG. 18 shows class diagram information (reference numeral 1030) before conversion and class diagram information (reference numeral 2030) after conversion by the class diagram conversion processing. In the case of the third conversion pattern, the class diagram conversion processing unit 113 newly inserts an abstract class (class R) for the To element type 105 and the To element ID 106 whose relation type 101 is “aggregation” as shown in FIG. To do. Then, the class diagram conversion processing unit 113 newly adds a record, sets “inherit” as the relation type 101, and sets the newly inserted abstract class (class R) as the From element type 103 and the From element ID 104. Then, the “class” of the To element type 105 before conversion and “a” of the To element ID 106 before conversion are transferred to the To element type 105 and To element ID 106.
By executing such data processing, the class diagram conversion processing unit 113 converts the class diagram information 100 from the pattern [2] to [3].

<< 4th conversion pattern: Pattern [3] → [2] >>
FIG. 19 shows class diagram information 100 when the class diagram conversion device 1 according to the present embodiment executes the fourth conversion pattern ([3] class aggregation relationship + abstract class → [2] class aggregation relationship). It is a figure for demonstrating this conversion process.
FIG. 19 shows class diagram information (reference numeral 1040) before conversion and class diagram information (reference numeral 2040) after conversion by the class diagram conversion processing. In the case of the fourth conversion pattern, the class diagram conversion processing unit 113 deletes the “inheritance” record from the class information before conversion (reference numeral 1040) as shown in FIG. The “class” of the To element type 105 and the “a” of the To element ID 106 are transferred to the To element type 105 and the To element ID 106 of the converted “aggregation” record.
By executing such data processing, the class diagram conversion processing unit 113 converts the class diagram information 100 from pattern [3] to [2].

<< Fifth Conversion Pattern: Pattern [3] → [4] >>
20 shows a class when the class diagram conversion apparatus 1 according to the present embodiment executes the fifth conversion pattern ([3] class aggregation relation + abstract class → [4] TMF SID Spec.Char. Pattern). It is a figure for demonstrating the conversion process of the figure information.
FIG. 20 shows class diagram information (reference numeral 1050) before conversion and class diagram information (reference numeral 2050) after conversion by the class diagram conversion processing. In the case of the fifth conversion pattern, the class diagram conversion processing unit 113 converts “Class A” indicated by the From element type 103 and the From element ID 104 of the “Aggregation” record before conversion, after conversion, as shown in FIG. It is instantiated as “object A” indicated by the To element type 105 and To element ID 106 of the newly added record of “instance”. Further, the class diagram conversion processing unit 113 adds the “class a” indicated by the To element type 105 and the To element ID 106 of the “inheritance” record before the conversion to the To element of the “instance” record newly added after the conversion. Instantiated as “object a” indicated by type 105 and To element ID 106.
The class diagram conversion processing unit 113 displays “class A” indicated by the From element type 103 and From element ID 104 of the “aggregated” record before conversion, and “class R” indicated by the To element type 105 and To element ID 106. Each is rewritten to a new class (“class SA” “class SAC”) that accommodates each object after conversion. Then, the class diagram conversion processing unit 113 deletes the “inheritance” record before the conversion.
By executing such data processing, the class diagram conversion processing unit 113 converts the class diagram information 100 from the pattern [3] to [4].

<< Sixth Conversion Pattern: Pattern [4] → [3] >>
FIG. 21 shows a class when the class diagram conversion apparatus 1 according to the present embodiment executes the sixth conversion pattern ([4] TMF SID Spec.Char. Pattern → [3] class aggregation relationship + abstract class between classes). It is a figure for demonstrating the conversion process of the figure information.
FIG. 21 shows class diagram information (reference numeral 1060) before conversion and class diagram information (reference numeral 2060) after conversion by the class diagram conversion processing. In the case of the sixth conversion pattern, the class diagram conversion processing unit 113 is an object of “class SA” that is a class indicated by the “element” 103 element type 103 and the “from” element ID 104 before conversion as shown in FIG. Yes, the “object A” indicated by the To element type 105 and the To element ID 106 of the “instance” record is set as the “class A” indicated by the From element type 103 and the From element ID 104 of the “aggregated” record after conversion. Deinstantiate. The class diagram conversion processing unit 113 is an object of “class SAC” that is a class indicated by the “elementary” To element type 105 and the To element ID 106 before conversion, and the To element type 105 of the record of “instance”. And the “object a” indicated by the To element ID 106 are de-instantiated as the “class a” indicated by the To element type 105 and the To element ID 106 of the newly added “inherited” record after conversion.
Also, the class diagram conversion processing unit 113 sets a new class (class R) inherited by the converted “class a” and stores it in the To element type 105 and the To element ID 106 of the converted “aggregation” record. Further, it is stored in the From element type 103 and From element ID 104 of the “inherited” record after conversion.
By executing such data processing, the class diagram conversion processing unit 113 converts the class diagram information 100 from the pattern [4] to [3].

<< Seventh conversion pattern: Pattern [2] → [4] >>
FIG. 22 shows the conversion of the class diagram information 100 when the class diagram conversion device 1 according to the present embodiment executes the seventh conversion pattern ([2] class aggregation relationship → [4] TMF SID Spec.Char. Pattern). It is a figure for demonstrating a process.
FIG. 22 shows class diagram information (reference numeral 1070) before conversion and class diagram information (reference numeral 2070) after conversion by the class diagram conversion processing. In the case of the seventh conversion pattern, the class diagram conversion processing unit 113 converts “Class A” indicated by the From element type 103 and the From element ID 104 of the “Aggregation” record before the conversion, as shown in FIG. It is instantiated as “object A” indicated by the To element type 105 and To element ID 106 of the newly added record of “instance”. Further, the class diagram conversion processing unit 113 adds the “element a” indicated by the “element” 105 of “aggregation” and the To element ID 106 before conversion to the To element type 105 of the record of “instance” newly added after conversion. And instantiated as “object a” indicated by the To element ID 106.
The class diagram conversion processing unit 113 includes a new class (“class SA”) that accommodates the converted “object A” and a new class (“class SAC”) that accommodates the converted “object a”. Set. Then, the class diagram conversion processing unit 113 generates a record in which the class SA aggregates the class SAC.
By executing such data processing, the class diagram conversion processing unit 113 converts the class diagram information 100 from the pattern [2] to [4].

<< Eighth conversion pattern: Pattern [4] → [2] >>
FIG. 23 shows the conversion of the class diagram information 100 when the class diagram conversion apparatus 1 according to the present embodiment executes the eighth conversion pattern ([4] TMF SID Spec.Char. Pattern → [2] class aggregation relationship). It is a figure for demonstrating a process.
FIG. 23 shows class diagram information (reference numeral 1080) before conversion and class diagram information (reference numeral 2080) after conversion by the class diagram conversion processing. In the case of the eighth conversion pattern, the class diagram conversion processing unit 113 is an object of “class SA” that is a class indicated by the “element” 103 element type 103 and the “from” element ID 104 before conversion as shown in FIG. Yes, the “object A” indicated by the To element type 105 and the To element ID 106 of the “instance” record is set as the “class A” indicated by the From element type 103 and the From element ID 104 of the “aggregated” record after conversion. Deinstantiate. The class diagram conversion processing unit 113 is an object of “class SAC” that is a class indicated by the “elementary” To element type 105 and the To element ID 106 before conversion, and the To element type 105 of the record of “instance”. And the “object a” indicated by the To element ID 106 are de-instantiated as the “class a” indicated by the To element type 105 and the To element ID 106 of the converted “aggregation” record.
By executing such data processing, the class diagram conversion processing unit 113 converts the class diagram information 100 from the pattern [4] to [2].

<< 9th conversion pattern: Pattern [5] → [6] >>
FIG. 24 illustrates the conversion process of the class diagram information 100 when the class diagram conversion apparatus 1 according to the present embodiment executes the ninth conversion pattern ([5] Realization of inheritance relationship by delegation → [6] Inheritance relationship). It is a figure for doing.
FIG. 24 shows class diagram information (reference numeral 1090) before conversion and class diagram information (reference numeral 2090) after conversion by the class diagram conversion processing. In the case of the ninth conversion pattern, the class diagram conversion processing unit 113 sets the value “B” of the From element ID 104 of the “aggregation” record before conversion to “inherit” newly set after conversion, as shown in FIG. To the To element ID 106 of the record. Also, the class diagram conversion processing unit 113 sets the value “A” of the To element ID 106 of the “aggregation” record before conversion to the From element ID 104 of the newly set “inheritance” record after conversion. Then, the class diagram conversion processing unit 113 deletes the “aggregation” record before conversion.
By executing such data processing, the class diagram conversion processing unit 113 converts the class diagram information 100 from the pattern [5] to [6].

<< 10th conversion pattern: Pattern [6] → [5] >>
FIG. 25 illustrates the conversion process of the class diagram information 100 when the class diagram conversion device 1 according to the present embodiment executes the tenth conversion pattern ([6] inheritance relationship → [5] realization of inheritance relationship by delegation). It is a figure for doing.
FIG. 25 illustrates class diagram information (reference numeral 1100) before conversion and class diagram information (reference numeral 2100) after conversion by the class diagram conversion processing. In the case of the tenth conversion pattern, the class diagram conversion processing unit 113, as shown in FIG. 25, “aggregation” in which the value “A” of the From element ID 104 of the “inheritance” record before conversion is newly set after conversion. To the To element ID 106 of the record. Also, the class diagram conversion processing unit 113 sets the value “B” of the To element ID 106 of the “inheritance” record before conversion to the From element ID 104 of the newly set “aggregation” record after conversion. Then, the class diagram conversion processing unit 113 stores, in the display related information 109 of the newly set “aggregation” record after conversion, the information of the arrow (→) from the class B to the class A that is the delegation destination. To do. Subsequently, the class diagram conversion processing unit 113 deletes the “inheritance” record before the conversion.
By executing such data processing, the class diagram conversion processing unit 113 converts the class diagram information 100 from the pattern [6] to [5].

  As described above, according to the class diagram conversion device 1 and the class diagram conversion program according to the present embodiment, the conversion pattern is displayed for patterns that are not limited to existing design patterns and are likely to be unclear to the designer. And let the designer choose. Therefore, the designer does not need advanced knowledge about the pattern that needs to be changed, and can review the class diagram once created and convert it to the optimum class diagram pattern.

1 class diagram conversion device 2 display device 3 input device 10 control unit 11 display processing unit (display processing means)
12 Input / output information processing section 20 Input / output section (input means)
30 memory section 40 storage section (storage means)
41 Class diagram information database 42 Conversion pattern database 100 Class diagram information 111 Class diagram display unit 112 Conversion pattern display unit 113 Class diagram conversion processing unit 200 Pre-conversion pattern selection screen 300 Conversion pattern list screen

Claims (8)

In the class diagram used in object-oriented software development, the pattern of the structure indicated by the combination of the classes and the relations representing the connection relationship between the classes is converted into another pattern different from the current pattern and displayed on the display device. A class diagram conversion device for causing
The class, the class attribute, and the object indicating the instance of the class are configured as equivalent components when converting the class diagram.
For each of the two components in the class diagram, the class before conversion using the type of association between the components and the type of the component indicating any one of the class, the attribute, and the object Class diagram information indicating a pattern of the configuration of the figure, pattern determination logic for specifying which pattern of the predetermined pattern group corresponds to the pattern constituting the class diagram with reference to the class diagram information , and, storage means for storing the conversion pattern information conversion pattern indicating a combination of the pattern after convertible conversion in the pre-conversion pattern and the pre-conversion of the pattern is more stored,
The class diagram information before the conversion is acquired and the class diagram before the conversion is displayed on the display device, and at least one of the class, the attribute, and the object of the class diagram before the conversion is selected. Obtain the application location to be converted via the input means,
The pattern of the class diagram before conversion indicated in the acquired application location is specified based on the pattern determination logic with reference to the class diagram information, and the conversion pattern that can be converted for the specified pattern is converted to the conversion Determine by referring to the pattern information,
The display device displays the pre-conversion pattern and one or more post-conversion patterns that can be converted in the pre-conversion pattern indicated by the determined conversion pattern that can be converted, and the one or more conversions The selection information of the converted pattern selected from the later patterns is acquired via the input means,
Display processing means for converting the pattern of the class diagram before conversion shown in the application location into the acquired pattern after conversion and displaying the pattern on the display device;
A class diagram conversion device comprising: The predetermined pattern group includes, in the class diagram, a pattern indicating a relationship between a class and an attribute, a pattern indicating a class aggregation relationship, a pattern having an abstract class in the class aggregation relationship, and a class in the class aggregation relationship. The class diagram conversion device according to claim 1, further comprising: a pattern including an object, a pattern realizing an inheritance relationship by delegation, and a pattern indicating the inheritance relationship . As a conversion pattern stored in the conversion pattern information,
Including a conversion pattern for converting a pattern indicating the relationship between the class and the attribute into a pattern indicating an aggregate relationship of the class.
The class diagram conversion device according to claim 2. As a conversion pattern stored in the conversion pattern information,
A pattern indicating an aggregation relationship of the class, a pattern indicating a relationship between the class and an attribute, a pattern having an abstract class in the aggregation relationship of the class, and a pattern in which the class includes an object in the aggregation relationship of the class Include a conversion pattern to convert to
The class diagram conversion device according to claim 2. As a conversion pattern stored in the conversion pattern information,
Including a conversion pattern for converting a pattern having an abstract class in the aggregation relation of the class into a pattern indicating the aggregation relation of the class and a pattern in which the class includes an object in the aggregation relation of the class.
The class diagram conversion device according to claim 2. As a conversion pattern stored in the conversion pattern information,
Including a conversion pattern for converting a pattern including the object in the class aggregation relationship into a pattern indicating the class aggregation relationship and a pattern having an abstract class in the class aggregation relationship.
The class diagram conversion device according to claim 2. As a conversion pattern stored in the conversion pattern information,
Including a conversion pattern for mutually converting a pattern realizing the inheritance relationship by the delegation and a pattern indicating the inheritance relationship
The class diagram conversion device according to claim 2. Class diagram conversion program for a computer to function as each means constituting the class diagram conversion device according to any one of claims 1 to 7.

Images