JPH11219287A - Software development supporting device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a software development supporting device provided with a class method mounting supporting part for automatically generating event calling logic for being the help of a developer performing complicated method mounting work. SOLUTION: A source code generation function 12 is provided with the class method mounting supporting part 30 provided with an event information obtaining part 17 for obtaining event information from the event information 11, an event-to-method relative information generation part 18 for obtaining a method corresponding to the event of the obtained event information from class information and relating them, an event processing code generation part 19 for generating a source code for calling the event based on the related event and method and a source code synthesis and output part for synthesizing the source code generated from a class diagram and the source code of an event processing.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for developing object-oriented software on a computer, and in particular, to automatically generate source code of an object-oriented language from a class diagram by OMT, or an event trace diagram and a class diagram. The present invention relates to a software development support device including a source code generation unit.

[0002]

2. Description of the Related Art Before describing conventional techniques, the meanings of terms used in the field of object-oriented software development will be described first.

In the object-oriented approach, the real world is composed of “things (= objects)” and relation definition information defining “relationships” between “things”, and the system is expressed as “things” and “relationships”. Build as things.

[0004] An object is composed of "attribute" data necessary to fulfill the role of the object and a procedure called a "method".

In the object orientation, properties common to individual objects are abstracted, a model called a class is considered, and a system is expressed using the model. A model created using a class is called a class diagram.

When a program is executed, a class generated as a type is called an instance.

Conventional Example 1. Next, a conventional example will be described. A well-known method for expressing a class diagram is an object-oriented methodology (OMT). In the OMT, a diagram called an event trace diagram that describes the order in which events occur between classes is used. As an example of a device that supports OMT on a computer, a tool Rose / C ++ manufactured by the US company Rational is well known. With this device, various diagrams such as a class diagram and an event trace diagram can be created / edited. Also,
This device uses one of the object-oriented programming languages
It has a C ++ source code generation function, and generates C ++ source code based on the definition of each class on the class diagram.

FIG. 4 is a block diagram showing the function of Rose / C ++. This device has, as main functions, a class diagram editor 1, an event trace diagram editor 6, and a C ++ source code generation function 12, which is a source code generation unit. This device has various other editors, but is omitted in this specification.

FIG. 5 shows an example of a class diagram, in which three rectangles connected by arrows are shown. These three rectangles indicate classes, 51 indicates a Driver class, 52 indicates an Automobile class, and 53 indicates an Engine class. Also,
Arrow lines connecting the classes indicate the mutual relationship, 54 is a class name display area, 55 is an attribute list display area, and 56 is a method list display area. Also,
A diamond-shaped mark 57a on the left side of the relationship 57, which is an arrow line between rectangles, indicates aggregation, and indicates that the Automobile class includes the Engine class. In Rose / C ++, a class diagram as shown in FIG. 5 can be created using the class diagram editor 1. R
Inose / C ++, a diagram is displayed on the class diagram display unit 2,
The user edits classes, attributes, methods, relationships, and the like, which are elements on the class diagram, by using the class diagram element editing unit 3. Further, the user uses the class diagram element specification editing unit 4 to input detailed information such as the name and definition of each element.
Further, the code generation property editing unit 5 inputs information necessary for generating the source code.

FIG. 6 shows an example of an event trace diagram. In FIG. 6, User indicated by 58 is Dri.
An instance of the ver class, MyCar denoted by 59 is an instance of the Automobile class, and TheEngine denoted by 60 is an instance of the Engine class. Arrow lines between each instance indicate events. The event indicated by 61 is from User to My
A StartEngine () event sent to Car. The event indicated by 62 is from MyCar to TheE
Start () event sent to ngine
Occurs after the StartEngine () event.
Thus, the event trace diagram represents the events dispatched between instances of several classes and the order of those events. In Rose / C ++,
Such an event trace diagram can be created. In Rose / C ++, a diagram is displayed on the event trace diagram display unit 7, and the user edits an instance or an event, which is an element on the event trace diagram, by the event trace diagram element editing unit 8. Further, the user uses the event trace diagram element specification editing unit 9 to input detailed information such as the name and definition of each element.

[0011] These class diagrams and event trace diagrams, which are the products of analysis and design by the object-oriented approach, are important design diagrams when implementing programs using an object-oriented programming language such as C ++. In the case of Rose / C ++, the skeleton of the C ++ source code can be generated by the source code generation function 12. In the source code generation function 12, the class definition obtaining unit 13 stores the class information 10 in which the class information of the class diagram created by the class diagram editor 1 is stored.
Then, the definition information for each class is extracted from, and the definition information is replaced with the C ++ source code by the class definition conversion unit. Then, the source code output unit 15 generates a source code, and stores the generated source code in the source code 16.

The event trace diagram is a scenario showing the operation at the time of execution, and shows the order of occurrence of events between the instances. The event shown in the event trace diagram is equal to the method of the class that is the source of the receiving instance. For example, in the event trace diagram of FIG. 6, the StartEngine () event is the class Automob of MyCar, which is an instance on the receiving side.
It is equal to the method StartEngine () of ile. This is also the case in the event trace diagram in FIG.
This information is important in the implementation of the program.
However, the source code generated by Rose / C ++ is based only on the information in the class diagram, and the information in the event trace diagram is not reflected in the source code at all.

[0013] In Rose / C ++, simple methods such as instance creation and deletion of classes, reference and setting of attribute values are implemented up to the processing body. However, for other non-simple methods defined by the user, only a skeleton without a processing body is generated. The processing body of such a user-defined method needs to be manually described by a developer on an editor. Hereinafter, these points will be described.

In the event trace diagram of FIG.
River, Automobile, and Engine instances User, MyCar, and TheE, respectively.
nine. Then, the event Star transmitted from the instance User to the instance MyCar
tEngine (), an event St transmitted from the instance MyCar to the instance TheEngine
There are two events, art (). Then, after the event StartEngine () is transmitted, the event Start () is transmitted. Event Start
Engine () is a method of instance MyCar, event Start () is an instance of TheEn
If it is a method of Gine, in the implementation in the C ++ source code, it is necessary to manually describe the process of calling the method Start () of the class Engine in the processing body of the method StartEngine () of the class Mobile.

Conventional example 2. Another conventional example is disclosed in
There is an invention of No. 22358. A first object of the invention of Japanese Patent Application Laid-Open No. 9-22358 is that, at an initial stage of designing a class for realizing a certain business, even if a person who is not familiar with the object-oriented approach can find a method that the class should have. An object of the present invention is to provide a method for automatically generating a method for each class that can be automatically generated with a small number of steps. A second object is to provide a method for automatically generating a method for each class, which can automatically generate a method to be possessed by a class so that the class has high reusability and high quality. Further, a third object is to provide a method for automatically generating a method for each class, which can automatically generate code of a method to be possessed by a class and can reduce a simple mounting work.

In order to achieve the first object, a plurality of method generation pattern information respectively corresponding to a plurality of class attributes are previously stored in pattern information storage means,
When generating a method of a class required to realize the target processing function, class definition information consisting of information such as class names and attributes, and inter-class relationship information that defines the relationship between classes are defined. Thereafter, comparing the class definition information and the inter-class relationship information, determine whether the attribute of the class defined in the class definition information is a simple attribute not related to another class or a related attribute related to another class, The method generation pattern information corresponding to the attribute of the determination result is read from the pattern information storage unit, and the method generation pattern information is expanded to generate a method of each class defined by the class definition information and the interclass relation information. It is characterized by the following. Also, in order to achieve the second object, after generating a method of a class having a relation attribute,
It is characterized in that it is determined whether or not the type of the related class is defined in the class definition information, and if not, the method corresponding to the attribute of the type is deleted. Further, in order to achieve the third object, a method is characterized in that after a method of each class is generated, the method is coded.

[0017]

As described above, according to the object-oriented analysis / design support apparatus having the source code generation function described in the first conventional example, the generation and deletion of class instances and the values of class attributes are provided. There was a problem that most methods had to be written by hand except for a simple method such as reference / setting. Further, there is a problem that the information of the created event trace diagram is not reflected at all in the source code generated by the source code generation function.

Further, Japanese Patent Application Laid-Open No.
The invention of US Pat. No. 22,358 is an invention in which a method of a basic pattern is automatically generated. Although there are differences in methodologies and means, a product close to the gist of Rose / C ++, a product of the US-Ratio, Inc. Has been released.

The present invention has been made in view of the above problems, and includes a method development support unit in a software development support device, thereby assisting a developer who performs a complicated method mounting operation. The purpose is to provide.

[0020]

According to the present invention, there is provided a software development support apparatus including an OMT (OMT is an objectm).
An abbreviation of modeling technique, which is one of the object-oriented analysis / design development methodologies for promoting system analysis and design using object-oriented). At least classes, methods, and relationships between classes are input as class information and a class diagram is created and illustrated. A class diagram editor for supporting the editing / editing operation, an event trace diagram editor for inputting at least an instance of the OMT class and the order of occurrence of the event as event information, and supporting the creation / editing of an event trace diagram to be illustrated; A source code generation unit that automatically generates a source code of a processing main body based on class information of a class diagram created by a diagram editor, wherein the source code generation unit is configured to be input by the class diagram editor. Class information And a source code for a process of associating an event with a method based on the event information input by the event trace diagram editor and invoking a method corresponding to the event. It has a class method implementation support unit to be implemented in the source code of the main body.

The class method implementation support unit associates an event with a method based on the class information input by the class diagram editor and the event information input by the event trace diagram editor to generate event-to-method relative information. An event-to-method relative information generating unit to generate, and an event processing code generating unit to generate a source code of a process of calling a method corresponding to the event from the event-to-method relative information generated by the event-to-method relative information generating unit; A source code synthesizing output unit for synthesizing a source code created by the event processing code generation into a source code of the processing body.

The software development support device according to the present invention is an OMT (OMT is an object modeling).
abbreviation of "technique", which is one of the object-oriented analysis / design development methodologies for promoting system analysis and design using object-orientation). A class diagram editor that supports editing work,
An event trace diagram editor for inputting at least an instance of the OMT class and an event occurrence order as event information and supporting creation / editing of an event trace diagram to be illustrated, and information of the class diagram created by the class diagram editor. And a source code generation unit for automatically generating the source code of the processing body, the source code generation unit,
Class information input by the class diagram editor,
An event-to-method relative information generating unit that generates event-to-method relative information by associating an event with a method based on the event information input by the event trace diagram editor; An event processing code generation unit that generates a source code of a process for calling a method corresponding to the event from the event-to-method relative information, and combining the source code generated by the event processing code generation unit with the source code of the processing body And a source code synthesizing output unit.

In the event trace diagram editor, a method corresponding to an event of the input event information includes:
A search is made as to whether or not it exists in the class information input by the class diagram editor, and if not, a class is determined from the event information, and the event is added as a method to the determined class. An event trace diagram element specification editing unit to be defined is provided.

The software development support apparatus further includes a processing component storage for storing processing patterns generally used in a program routine as processing components. A processing component allocating unit that specifies a processing component stored in the processing component storage is provided.

The event processing code generation unit generates a source code of a process for calling a method for an event based on the event-to-method relative information, and generates a process code specified for the event information by the processing component allocation unit. The method is characterized in that a part is acquired from the processing parts storage and a source code is generated.

[0026]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiment 1 Hereinafter, a first embodiment of the present invention will be described with reference to FIGS. FIG. 1 is a block diagram showing the overall configuration of the system according to the present embodiment. The same elements as those in FIG. 4 described in the first conventional example are denoted by the same reference numerals, and description thereof will be omitted. In FIG. 1, reference numeral 17 denotes an event information acquisition unit that extracts information on the event and instances on both sides of transmission and reception from the event information 11, and 18 corresponds to the event obtained from the event information acquisition unit 17 and the event retrieved from the class definition acquisition unit 13. An event-to-method relative information generation unit 19 for associating with a method and generating event-to-method relative information. A processing body 19 of a method of a class corresponding to an instance on the event receiving side based on the event-to-method relative information. Is an event processing code generation unit that generates source code of a method of another instance called from the processing body of the method. Reference numeral 30 denotes a class method implementation support unit, which includes an event information acquisition unit 17, an event-to-method relative information generation unit 18, an event processing code generation unit 19, and a source code synthesis output unit 20.
It is composed of Reference numeral 20 denotes a source code synthesis output unit that appropriately synthesizes source codes generated by the class definition conversion unit 14 and the event processing code generation unit 19 and outputs a source code 16.

Next, as an example of implementing a class method based on the class diagram of FIG. 5 and the event trace diagram of FIG. 6, an operation of generating an event processing component in the present embodiment will be described with reference to a flowchart of FIG. Will be described.

First, in the class diagram of FIG.
Class, Automobile Class and Engine
Classes are defined, and associations are defined between each class. The developer uses the class diagram element specification editing unit 4 to define that the Engine class is aggregated into the Automobile class. Also, in the event trace diagram of FIG. 6, each instance corresponding to the three classes defined in the class diagram of FIG. 5 is defined, and an event is defined between each of them. The developer uses the event trace diagram element specification editing unit 9 to convert the Mobile class instance User into an Automobile.
The event sent to the instance MyCar of the class includes the method Start of the Automobile class.
Specify Engine (). In addition, Automob
From the instance MyCar of the ile class to Engin
The event sent to the instance TheEngine of the e class includes the method Star of the
Specify t ().

When the developer instructs the source code generation function 12 to execute, the class definition obtaining unit 13 obtains the class definition information from the class information 10, and the event information obtaining unit 17 reads the event information from the event information 11. And information on the instances on the transmitting and receiving sides (step 10).
1).

Next, the event-to-method relative information generation unit 18 searches for the corresponding class from the class information based on the receiver instance information of the event acquired by the event information acquisition unit 17 and defines the class as an event. It is confirmed that the provided method belongs to the corresponding class (step 102).

Specifically, the event information acquisition unit 17
An event called "start ()" is acquired, and the receiving instance "TheEngine" of the event is "Engine".
Know that it is a class. Then, the event-to-method relative information generation unit 18 determines from the class information
Find the e class and make sure that the method Start () in the Engine class is the same as the event start ().

Further, the event-to-method relative information generation unit 18 obtains information on the event received immediately before by the event transmitting side instance, and checks the method corresponding to the event (step 103).

Specifically, the transmitting instance MyCa
In r, the event StartEngine () immediately before the event Start () is called is acquired, and it is confirmed that the event is a method of the Automobile class.

Event-to-method relative information generator 18
Is the target event (here, the event Star
t ()) and the method of the class indicated by the receiving instance are combined, and the event received immediately before the target event (here, the event StartEngine
e ()) and the method of the class indicated by the instance receiving it are combined to generate information that associates these two combinations (step 10).
4).

Specifically, an instance TheEngine which is one of the event information, a method Start () which is one of the class information thereof, and an event Start () which is one of the event information are combined.
Instance MyCar and its method StartEn
Gine () and the event StartEngine () are combined to generate information that associates these two pieces of information.

The event processing code generation unit 19 generates a C ++ source code based on the information generated by the event-to-method relative information generation unit 18 and stores information specifying which method to embed the generated source code in. It is added (step 106).

Specifically, the instance TheEngi
Calling the method Start () of ne is C ++
Generated in source code, this process is an instance My
Information specifying that the operation is performed in the method StartEngine () of Car is added.

Step 10 from acquisition of information on the corresponding method to generation of C ++ source code for each event
Steps 2 to 106 are repeated (step 10
7).

The class definition conversion unit 14 receives the class definition information from the class definition acquisition unit 13 and converts it into C ++ source code (step 108).

Specifically, Dri in the class diagram of FIG.
ver class, Automobile class, Engi
Generate skeleton of ne class definition and method definition in C ++ source code.

Finally, in the source code synthesis output unit 20, the C ++ source code generated by the event processing code generation unit 19 is inserted into a designated position of the C ++ source code generated by the class definition conversion unit 14 (step 10).
9).

More specifically, in the skeleton of the definition of the method StartEngine () of the Automobile class, the method S of the instance TheEngine is included.
Insert the C ++ source code of the process that calls start ().

As described above, since the class diagram and the event trace diagram shown in FIGS. 5 and 6 can be implemented in a form supplementing the processing body of the class method, the manual work in the implementation work of the developer can be performed. Burden can be reduced.

Embodiment 2 Next, a second embodiment of the present invention will be described. The overall configuration of the system in the present embodiment is the same as FIG.

In the event trace diagram editor 6,
Define a new event. At this time, if the method corresponding to the event is not set in the class information 10, the event trace diagram element specification editing unit, if a new method is defined here, sets the event trace A method newly defined on the diagram editor is automatically added and stored in the class information 10.

In this way, in the process of creating the event trace diagram, the class diagram is automatically corrected by reflecting the additional work on the event trace diagram editor. Can be reduced.

Embodiment 3 Next, a third embodiment of the present invention will be described with reference to FIG. FIG. 3 is a block diagram showing the overall configuration of the system according to the present embodiment. The same elements as those in the first embodiment are denoted by the same reference numerals, and description thereof will be omitted. In FIG. 3, reference numeral 21 denotes a processing component allocating unit that allocates a processing component to each event;
A processing component storage 2 stores and manages various general-purpose processing components. The processing component is assumed to be a processing component of various patterns such as a component obtained by combining basic processes such as conditional branch control and iterative control used in a program routine, and a component obtained by combining the components.

The event processing component in the present embodiment is the C ++ source code generated by the event processing code generator 19 described in the first embodiment. Therefore, the description of the operation of generating the event processing component will be omitted, and the added operation will be described.

On the event trace diagram editor 6, a processing component is designated for each event by the processing component allocation unit 21 as necessary. At this time, the processing order with the separately specified method is also specified. Event information 11
The processing component information and the processing order information are also stored in the.

At the time of source code generation, the event processing code generator 19 generates C ++ source code based on the information generated by the event-to-method relative information generator 18 and embeds the generated source code in any method. Is added. At this time, the calling code of the processing component specified by the processing component allocating unit 21 is also added to the generated source code, and the information is supplemented by obtaining the information from the processing component storage 22.

In this way, the processing body of the class method can be implemented not only by calling an event, but also by complementing the calling of an existing processing component.
It is possible to reduce the burden of manual work in the implementation work of the developer.

[0052]

According to the present invention, the provision of the class method implementation support unit, particularly, the event processing code generation unit enables automatic generation of the method call processing code based on the event trace diagram. It is possible to supplement the implementation of the class method in the processing body. Thereby, there is an effect that the information of the event trace diagram can be effectively used.

Further, according to the present invention, by linking the class information and the event trace diagram element specification editing unit, a unified management in which the class diagram and the event trace diagram correspond to each other can be realized, and the design work with few errors can be realized. There are effects that can be performed.

Further, according to the present invention, by introducing the processing component storage, it becomes possible to allocate the processing body of the class method to each event on the event trace diagram. As a result, the processing body of the class method can be further added and automatically generated, and the process of the mounting operation can be shortened.

[Brief description of the drawings]

FIG. 1 is a block diagram showing an overall configuration of a software development support device according to a first embodiment of the present invention.

FIG. 2 is a flowchart of a source code generation function according to the first embodiment.

FIG. 3 is a block diagram showing an overall configuration of a software development support device according to a third embodiment of the present invention.

FIG. 4 is a block diagram showing the overall configuration of a conventional device.

FIG. 5 is a diagram showing a part of a class diagram.

FIG. 6 is an event trace diagram showing events between instances of a class defined in the class diagram.

[Explanation of symbols]

1 Class diagram editor, 2 Class diagram display unit, 3 Class diagram element editing unit, 4 Class diagram element specification editing unit, 5 Code generation property editing unit, 6 Event trace diagram editor, 7 Event trace diagram display unit, 8 Event trace diagram Element editing unit, 9 Event trace diagram element specification editing unit, 10 class information, 11 event information, 12
Source code generation function, 13 Class definition acquisition unit, 1
4 class definition converter, 15 source code output unit, 1
6 Source code, 17 Event information acquisition unit, 18
Event-to-method relative information generation section, 19 event processing code generation section, 20 source code synthesis output section, 21
Processing component allocation unit, 22 processing component storage, 30 class method implementation support unit, 51 Driver class, 52 A
umobile class, 53 Engine class, 54 class name display area, 55 attribute list display area, 56 method list display area, 57 relation,
57a Diamond-shaped mark, 58 User instance of Driver class, 59 MyCar instance of Automobile class, 60Engine instance of TheEngine class, 61 Start
An Engine () event, a 62 Start () event.

Claims (6)

[Claims] An OMT (OMT is an object mod)
An abbreviation for "eling technique", which is one of the object-oriented analysis / design development methodologies that promote system analysis and design using object-oriented design). A class diagram editor for supporting the editing / editing operation, an event trace diagram editor for inputting at least an instance of the OMT class and the order of occurrence of the event as event information, and supporting the creation / editing of an illustrated event trace diagram; A source code generation unit that automatically generates source code of a processing body based on class information of a class diagram created by a diagram editor, wherein the source code generation unit is input by the class diagram editor. Class information and Based on the event information input by the event trace diagram editor, a source code for a process of associating an event with a method and calling a method corresponding to the event is created, and the generated source code is processed by the processing body. A software development support device, comprising: a class method implementation support unit for implementing the method in a source code. 2. The method according to claim 1, wherein the class method implementation support unit associates the event with the method based on the class information input by the class diagram editor and the event information input by the event trace diagram editor. An event-to-method relative information generation unit that generates information; and an event processing code generation unit that generates a source code of a process for calling a method corresponding to the event from the event-to-method relative information generated by the event-to-method relative information generation unit. And a source code synthesizing output unit for synthesizing a source code created by generating the event processing code into a source code of the processing body.
Software development support device as described. 3. An OMT (OMT is an object mod)
An abbreviation for "eling technique", which is one of the object-oriented analysis / design development methodologies that promote system analysis and design using object-oriented design). A class diagram editor for supporting the editing / editing operation, an event trace diagram editor for inputting at least an instance of the OMT class and the order of occurrence of the event as event information, and supporting the creation / editing of an illustrated event trace diagram; A software development support device having a source code generation unit for automatically generating a source code of a processing body based on information of a class diagram created by a diagram editor, wherein the source code generation unit is input by the class diagram editor. Class information and the An event-to-method relative information generating unit that generates event-to-method relative information by associating an event with a method based on the event information input by the event trace diagram editor; and an event-to-method relative information generating unit. An event processing code generation unit that generates a source code of a process for calling a method corresponding to the event from the event-to-method relative information; and combining the source code generated by the event processing code generation unit with a source code of the processing body. A software development support device comprising a source code synthesis output unit. 4. The event trace diagram editor searches whether or not a method corresponding to an event of the input event information exists in the class information input by the class diagram editor, and does not exist. In case,
4. The software development support device according to claim 2, further comprising an event trace diagram element specification editing unit that determines a class from the event information and additionally defines the event as a method for the determined class. . 5. The software development support device further includes a processing component storage for storing processing patterns generally used in a program routine as processing components. 4. The software development support device according to claim 2, further comprising a processing component allocating unit that specifies a processing component stored in the processing component storage. 6. The event processing code generation unit generates a source code of a process for calling a method for an event based on the event-to-method relative information, and is specified for the event information by the processing component allocation unit. 6. The software development support device according to claim 5, wherein the processing component obtained from the processing component storage and generates a source code.