JP5929297B2 - Model diagram creation device, model diagram creation method, and model diagram creation program - Google Patents

Description

  The present invention relates to a model diagram creation device, a model diagram creation method, a model diagram creation program, and a data structure of a state event table for creating a model diagram, which create a model diagram necessary for generating an object-oriented model of software.

  Conventionally, in the development of an object-oriented model of software, reverse engineering is known in which various model diagrams are automatically created by analyzing a source code. According to this reverse engineering, it is possible to verify the discrepancy between the specifications and the actual product, and to find bugs, etc., improving software productivity and improving system maintenance and security. Can be useful.

  As an example of such a reverse engineering technique, for example, Patent Document 1 discloses a technique for automatically generating a state machine diagram by analyzing a source code. Patent Documents 2 and 3 disclose techniques for automatically generating a sequence diagram by analyzing a source code, respectively. According to these conventional techniques, it is possible to generate an object-oriented model reflecting one aspect of software to be developed.

JP 2008-198103 A JP 2004-94496 A JP 2009-295021 A

  However, with the above-mentioned conventional technology, it is possible to create behavior diagrams such as state machine diagrams and sequence diagrams individually, but it is not possible to create multiple types of behavior diagrams together with structure diagrams such as class diagrams. could not. For this reason, with the above-described conventional technology, behavior diagrams that cannot be automatically created must be created manually, and a consistent object-oriented model that reflects various aspects of the software to be developed is consistent. Generation was not realized.

  The present invention has been made in view of the above, and a model diagram creation apparatus and a model diagram creation method capable of realizing generation of a consistent object-oriented model while reflecting various aspects of software to be developed The object is to provide a model diagram creation program and a data structure of a model event creation state event table.

  In order to solve the above-described problems and achieve the object, the model diagram creation apparatus according to the present invention creates a model diagram for creating a model diagram necessary for generating an object-oriented model of software using a unified modeling language. In the device, a function defined according to a combination of a state and an event in a model diagram, a function defining a class diagram as a model diagram and a plurality of types of behavior diagrams, and a class type corresponding to the class diagram A storage unit that stores a state event table in which information to be defined is described, a structure diagram generation unit that generates a class diagram based on the state event table stored in the storage unit, and a state event table stored in the storage unit And a behavior diagram creation unit that creates a plurality of types of behavior diagrams based on the behavior diagram.

  Further, the model diagram creation apparatus according to the present invention is the above-described invention, wherein the state event table is a function for determining a state transition in the state machine diagram as a function for determining the configuration of the plurality of types of behavior diagrams, and a message in the sequence diagram. And a function for determining a message transmission destination in the sequence diagram.

  The model diagram creation apparatus according to the present invention is characterized in that, in the above invention, the class type includes a class representing a state transition machine and an existing software class.

  Further, in the above-described invention, the model diagram creation apparatus according to the present invention provides the name of the function as the function information included in the existing software in the state event table in which the class type is the class of the existing software. Only is described.

  The model diagram creating apparatus according to the present invention describes a function for calling a function of a class of the existing software in the state event table in which the type of the class is a class representing the state transition machine in the above invention. It is possible to do this.

  Further, in the above invention, the model diagram creating apparatus according to the present invention has information necessary for creating the class diagram and the plurality of types of behavior diagrams as elements, and the mutual relationship between the plurality of elements is expressed in a tree structure. The apparatus further includes an element configuration diagram creating unit that creates an element configuration diagram to be shown.

  The model diagram creation device according to the present invention is the display unit capable of displaying the element configuration diagram in the above invention, and the display every time the element configuration diagram creation unit adds an element to the element configuration diagram. And a display control unit for switching and displaying the display in the unit.

  Further, in the above-described invention, the model diagram creating apparatus according to the present invention is capable of displaying the class diagram and the plurality of types of behavior diagrams, and the display control unit includes the class diagram creating unit and the class diagram creating unit. The structure diagram and the behavior diagram respectively created by the behavior diagram creation unit are displayed on the display unit in the order of creation.

  In the model diagram creating apparatus according to the present invention as set forth in the invention described above, the display control unit displays the element configuration diagram, the class diagram, and the behavior diagram side by side on the display unit.

  The model diagram creation method according to the present invention is a model diagram creation method executed by a model diagram creation device that creates a model diagram necessary for creating an object-oriented model of software using a unified modeling language. Functions that are defined according to the combination of states and events in the class, and that define the structure of a class diagram as a model diagram and multiple types of behavior diagrams, and information that defines the class type corresponding to the class diagram A class diagram creating step for creating a class diagram by referring to the state event table from a storage unit for storing the state event table, and creating a plurality of types of behavior diagrams by referring to the state event table from the storage unit And a behavior diagram creating step.

  In addition, the model diagram creation program according to the present invention provides a model diagram creation device that creates a model diagram necessary for generating an object-oriented model of software using a unified modeling language, and a combination of states and events in the model diagram. Stores a function that is defined in accordance with the class event as a model diagram and functions that define the structure of multiple types of behavior diagrams, and a state event table that describes information that defines the type of class corresponding to the class diagram A class diagram creating step for creating a class diagram by referring to the state event table from the storage unit, and a behavior diagram creating step for creating a plurality of types of behavior diagrams by referring to the state event table from the storage unit. It is made to perform.

  In addition, the data structure of the state event table for creating a model diagram according to the present invention is defined according to the combination of the state and event in the model diagram necessary for generating an object-oriented model of software using the unified modeling language. And a function that defines the structure of a class diagram as a model diagram and a plurality of types of behavior diagrams, and information that defines the class type corresponding to the class diagram.

  Further, the data structure of the state event table for creating a model diagram according to the present invention, in the above invention, as the function, a function for determining state transition in a state machine diagram, a function for determining message transmission conditions in a sequence diagram, and It includes a function for determining a message transmission destination in the sequence diagram.

  Further, the data structure of the state event table for creating a model diagram according to the present invention is the above-described invention, wherein the structure diagram is a class diagram, and information defining a class type corresponding to the class diagram is described. The types of classes include a class representing a state transition machine and an existing software class.

  The data structure of the state event table for creating a model diagram according to the present invention is included in the existing software when the type of the class in the state event table is the class of the existing software in the above invention. Only the name of the function is described as function information.

  Further, the data structure of the state event table for creating a model diagram according to the present invention is such that, in the above invention, when the class type in the state event table is a class representing the state transition machine, the existing software class A function for calling the function is described.

  According to the present invention, a class diagram and a plurality of types of functions are defined on the basis of a state event table in which information defining a class type corresponding to the class diagram and functions defining the class diagram and a plurality of types of behavior diagrams are described. Since behavior diagrams are automatically created, it is possible to generate a consistent object-oriented model while reflecting various aspects of the software to be developed.

FIG. 1 is a block diagram showing a functional configuration of a model diagram creation apparatus according to Embodiment 1 of the present invention. FIG. 2 is a diagram illustrating a configuration example of the state event table. FIG. 3 is a diagram illustrating a configuration example (second example) of the state event table. FIG. 4 is a diagram showing a configuration of a class diagram created from the state event table shown in FIG. FIG. 5 is a diagram showing the configuration of a class diagram created from the state event table shown in FIG. FIG. 6 is a diagram showing the configuration of a state machine diagram created from the state event table shown in FIG. FIG. 7 is a diagram showing a configuration of a state machine diagram created from the state event table shown in FIG. FIG. 8 is a diagram showing a configuration of a sequence diagram created from the state event table shown in FIGS. 2 and 3. FIG. 9 is a flowchart showing an outline of processing of a model diagram creation method performed by the model diagram creation device according to Embodiment 1 of the present invention. FIG. 10 is a flowchart showing an overview of class diagram creation processing performed by the model diagram creation device according to Embodiment 1 of the present invention. FIG. 11A is a diagram illustrating a display example in the display unit of the element configuration diagram to which components are added. FIG. 11B is a diagram illustrating a display example on the display unit of the element configuration diagram in a state where a class diagram and class elements are added. FIG. 11C is a diagram illustrating a display example in the display unit of the element configuration diagram to which various functions are added. FIG. 11D is a diagram illustrating a display example in the display unit of the element configuration diagram to which the attribute is added. FIG. 11E is a diagram illustrating a display example in the display unit of the class diagram. FIG. 11F is a diagram illustrating a display example on the display unit of the element configuration diagram in which a series of class diagram creation processing is completed for the state event table illustrated in FIG. 3. FIG. 12 is a flowchart showing an overview of a state machine diagram creation process performed by the model diagram creation device according to Embodiment 1 of the present invention. FIG. 13A is a diagram illustrating a display example in the display unit of the element configuration diagram in which elements of the state machine diagram are added. FIG. 13B is a diagram illustrating a display example in the display unit of the element configuration diagram to which the state is added. FIG. 13C is a diagram illustrating a display example in the display unit of the element configuration diagram to which the event is added. FIG. 13D is a diagram illustrating a display example in the display unit of the element configuration diagram with the start element added. FIG. 13E is a diagram illustrating a display example on the display unit of the element configuration diagram in which a series of state machine diagram creation processing is completed for the state event table. FIG. 14 is a flowchart showing an overview of sequence diagram creation processing performed by the model diagram creation device according to Embodiment 1 of the present invention. FIG. 15A is a diagram illustrating a display example in the display unit of the element configuration diagram to which elements of the sequence diagram are added. FIG. 15B is a diagram illustrating a display example in the display unit of the element configuration diagram in which the element of the message end point is added. FIG. 16 is a diagram illustrating a configuration example of the state event table stored in the state event table storage unit included in the model diagram creating apparatus according to Embodiment 2 of the present invention. FIG. 17 is a diagram showing a configuration example of another state event table stored in the state event table storage unit of the model diagram creating apparatus according to Embodiment 2 of the present invention. FIG. 18 is a diagram showing a configuration example of still another state event table stored in the state event table storage unit of the model diagram creating apparatus according to Embodiment 2 of the present invention. FIG. 19 is a diagram showing the structure of a class diagram created by the model diagram creation device according to Embodiment 2 of the present invention based on the state event table shown in FIG. FIG. 20 is a diagram showing the configuration of a sequence diagram created by the model diagram creation device according to the second embodiment of the present invention based on the state event table shown in FIGS. 17 and 18. FIG. 21 is a diagram showing a display screen example when the display unit of the model diagram creating apparatus according to Embodiment 2 of the present invention displays an element configuration diagram with all components added.

  DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments for carrying out the present invention (hereinafter referred to as “embodiments”) will be described with reference to the accompanying drawings.

(Embodiment 1)
FIG. 1 is a block diagram showing a functional configuration of a model diagram creation apparatus according to Embodiment 1 of the present invention. A model diagram creation apparatus 1 shown in FIG. 1 is an apparatus that automatically creates a model diagram necessary for generating an object-oriented model of software using a unified modeling language (UML). A model diagram creating apparatus 1 shown in FIG. 1 includes an input unit 2 realized by using an interface such as a keyboard, a mouse, and a touch panel, and a display unit configured to display various kinds of information, such as a liquid crystal or an organic EL. 3, a storage unit 4 that stores various types of information including information for creating a UML model diagram, and a control unit 5 that controls the operation of the model diagram creation device 1.

  The storage unit 4 includes a state event notation unit 41 that stores a state event table that is referred to when the model diagram creating apparatus 1 creates a model diagram, and a creation information storage unit 42 that stores information such as the created model diagram. And have. The state event table is a table showing the relationship between states and events in the model diagram, and is a function defined according to the combination of the state and the event. The structure of the model diagram and multiple types of behavior diagrams It has a data structure in which a function to be defined is described. A plurality of state event tables can be described in one file (hereinafter referred to as a component). The detailed configuration of the state event table will be described later.

  The storage unit 4 is realized by using a ROM in which a model diagram creation program according to the first embodiment, a program for starting a predetermined OS, and the like are stored in advance, and a RAM in which calculation parameters and data of each process are stored. Is done.

  The control unit 5 includes a structure diagram creating unit 51 that creates a structure diagram of the model diagram based on the state event table stored in the state event table storage unit 41, a state event table stored in the state event table storage unit 41, and Based on the structure diagram created by the structure diagram creation unit 51, a behavior diagram creation unit 52 that creates a plurality of types of behavior diagrams, and a structure diagram and information necessary to create the plurality of types of behavior diagrams are provided as elements. And an element configuration diagram creating unit 53 that creates an element configuration diagram showing the mutual relationship of a plurality of elements in a tree structure, and a display control unit 54 that controls display on the display unit 3.

  In the first embodiment, a class diagram is taken as an example of a structure diagram, while a state machine diagram and a sequence diagram are taken as examples of behavior diagrams, but this is merely an example. For example, either a component diagram or an object diagram can be applied as a structure diagram. In addition, any one of a communication diagram (collaboration diagram), an activity diagram, a use case diagram, a timing diagram, and an interaction summary diagram can be applied as a behavior diagram.

  The control unit 5 is realized by using a CPU or the like, and is connected to each component of the model diagram creating apparatus 1 to be controlled via a bus line. The control unit 5 reads out various programs including information stored and stored in the storage unit 4 and the model diagram creation program according to the first embodiment from the storage unit 4, thereby creating a model diagram creation method according to the first embodiment. The calculation process related to is executed.

  The model drawing creation program according to the first embodiment can be recorded on a computer-readable recording medium such as a hard disk, a flash memory, a CD-ROM, a DVD-ROM, or a flexible disk and widely distributed. .

  The model diagram creating apparatus 1 having the above configuration may be realized by using one computer or may be realized by using a plurality of computers. In the latter case, it is possible to perform processing in cooperation with each other while transmitting and receiving data via a communication network such as the Internet.

  FIG. 2 is a diagram illustrating a configuration example of the state event table stored in the state event table storage unit 41. A state event table 100 shown in the figure is a table that provides a correspondence relationship between states and events in the model diagram. The state event table 100 includes a class name, a matrix, a function table, and an attribute table.

  The class name is indicated by an item [Class_Name] in the table. The class name of the state event table 100 is ComponentA described on the right side of the item. This class name is the name of the class diagram and state machine diagram. It is also the class name described in the class diagram.

  The matrix in the state event table represents the correspondence between states (rows) and events (columns). In the state event table 100, an item [State] indicates a state, and an item [Event] indicates an event. The state event table 100 includes two states “state 1 (STATE 1)” and “state 2 (STATE 2)”. “State 1” and “State 2” are Japanese state names, and “STATE 1” and “STATE 2” are displayed in the model diagram, respectively. The state event table 100 includes two events “event 11 (E11)” and “event 12 (E12)”. “Event 11” and “Event 12” are state names in Japanese, and “E11” and “E12” are displayed in the model diagram, respectively. Hereinafter, the elements of the matrix are referred to as cells.

  A specific relationship between the state and the event is described in the cell determined by the state and the event. In FIG. 2, the specific description inside each cell is described according to an XML (Extensible Markup Language) format.

The contents described in the cell will be specifically described. The description contents of the cell are as shown below.
[f_function name]
<Action>
<Condition Func = "condition function name">
<Logic> Event response function name </ Logic>
<Message> Destination class name @ event function name </ Message>
<TransitionState> State name after transition </ TransitionState>
</ Condition>
</ Action>

The first item [f_function name] of the cell gives the response function name.
The Condition tag (<Condition>) defines the condition function of the class diagram. The attribute value (condition function) of the Condition tag gives a guard condition for transitions in the state machine diagram and a guard condition for messages from the class lifeline in the sequence diagram.
Logic tag (<Logic>) defines the action name of transition in the state machine diagram.
The Message tag (<Message>) is described in a format of “destination class name @ event function name”. Of these, the destination class name gives the destination of the message from the class lifeline in the sequence diagram. The event function name gives the message name from the class lifeline in the sequence diagram. If the event function has an argument, the event function name (argument 1, argument 2,...) Is described.
The TransitionState tag (<TransitionState>) defines a transition destination state in the state machine diagram.
A plurality of Condition tags and Message tags may be described in one cell. In one cell, the Condition tag, Logic tag, Message tag, and TransitionState tag can be omitted.

  In the state event table 100 shown in FIG. 2, a response function [f_Action11] is defined in the cell corresponding to the combination of the state 1 and the event 11. The contents of the response function [f_Action11] will be described. The condition function in the Condition tag is Conditon11. The action name of the transition defined by the Logic tag is Action11. The class name of the transmission destination defined by the Messege tag is ComponentB, and the event function name is event 21. The transition destination state defined by the TransitionState tag is state 2.

  A response function [f_Non] is defined in the cell corresponding to the combination of the state 1 and the event 12. This response function [f_Non] means that no processing is performed (no processing).

  A response function [f_Action13] is defined in the cell corresponding to the combination of the state 2 and the event 11. The contents of the response function [f_Action13] will be described. The action name of the transition defined by the Logic tag is Action13. The class name of the transmission destination defined by the Message tag is ComponentB, and the event function name is event 22.

  A response function [f_Action12] is defined in the cell corresponding to the combination of the state 2 and the event 12. The contents of the response function [f_Action12] will be described. The condition function in the Condition tag is Conditon12. The action name of the transition defined by the Logic tag is Action12. The class name of the transmission destination defined by the Message tag is ComponentB, and the event function name is event 22. The transition destination state defined by the TransitionState tag is state 1.

  In the state event table 100, three types of functions [Func_Logic], [Func_Condition], and [Func_Interface] are described as a function table. Each function has a function name ([Func_Name]), source code ([Func_Code]) that is the contents of the function, an Include file name ([Func_Include]), and a comment ([Func_Comment]) that describes the function. (In FIG. 2, other than function names are omitted). The source code is described using a programming language such as C, C ++, Java (registered trademark), for example.

The function [Func_Logic] is an event response function in the state machine diagram, and is a function that gives a transition action in the state machine diagram. In the state event table 100, Action11 (), Action12 (), and Action13 () are defined as specific functions. Here, () described next to each function means no argument.
The function [Func_Condition] is a function that gives a transition condition in the state machine diagram and a message condition in the sequence diagram. In the state event table 100, Condition11 () and Condition12 () are defined as specific condition functions.
The function [Func_Interface] is a function used from another class. In the state event table 100, Get () whose return value is an int type and Set (int) whose return value is a boolean type are defined as specific functions. Here, the argument of Set is an integer (denoted as int).
Note that the functions defined in the state event table are not limited to those described above.

  Attributes in the class diagram are defined in the attribute table. In the attribute table, an attribute name ([Attr_Name]), an attribute type ([Attr_Type]), an initial value ([Attr_Ini]), and a comment explaining the attribute ([Attr_Comment]) are described (in FIG. 2, the attribute (Excluding names and attribute types) In the state event table 100, an attribute name attr is described as a specific attribute.

  FIG. 3 is a diagram illustrating a configuration example of another state event table stored in the state event table storage unit 41. In the state event table 200 shown in the figure, the class name ([Class_Name]) is ComponentB. The state event table 200 includes three states “state 3 (STATE 3)”, “state 4 (STATE 4)”, and “state 5 (STATE 5)”. The state event table 200 includes two events “event 21 (E21)” and “event 22 (E22)”.

  A response function [f_Action21] is defined in the cell corresponding to the combination of the state 3 and the event 21. In this response function [f_Action21], the action name of the transition defined by the Logic tag is Action21, and the state of the transition destination defined by the TransitionState tag is state 4.

  A response function [f_Action24] is defined in the cell corresponding to the combination of the state 3 and the event 22. In this response function [f_Action24], the transition action name defined by the Logic tag is Action24, and the transition destination state defined by the TransitionState tag is state 5.

  A response function [f_Action22] is defined in the cell corresponding to the combination of the state 4 and the event 21. In this response function [f_Action22], the action name of the transition defined by the Logic tag is Action22, and the state of the transition destination defined by the TransitionState tag is state 5.

  A response function [f_Action26] is defined in the cell corresponding to the combination of the state 4 and the event 22. In this response function [f_Action26], the action name of the transition defined by the Logic tag is Action26, and the state of the transition destination defined by the TransitionState tag is state 3.

  A response function [f_Action23] is defined in the cell corresponding to the combination of the state 5 and the event 21. In this response function [f_Action23], the action name of the transition defined by the Logic tag is Action23, and the state of the transition destination defined by the TransitionState tag is state 3.

  A response function [f_Action25] is defined in the cell corresponding to the combination of the state 5 and the event 22. In this response function [f_Action25], the action name of the transition defined by the Logic tag is Action25, and the state of the transition destination defined by the TransitionState tag is state 4.

  In the response functions [f_Action21] to [f_Action26] described above, there is no Condition tag or Message tag.

  Next, the configuration of the class diagram, state machine diagram, and sequence diagram created by the model diagram creation apparatus 1 based on the state event tables 100 and 200 will be described.

  FIG. 4 is a diagram showing a configuration of a class diagram created by the model diagram creation device 1 from the state event table 100. In the class diagram 300 shown in the figure, the class name ComponentA is described at the top. Information related to the attribute having the attribute name attr is added below the class name.

  Below the attribute, functions used by other classes (function names Get and Set) are added. Here, int described on the right side of the function Get () means that the return value is an int type. The boolean described on the right side of the function Set (int) means that the return value is a true value (true or false). These arguments and return values are also defined in the functions shown below.

Below the functions used from other classes, an event function (E11, E12), a condition function (Condition11, Condition12), and an event response function (Action11, Action12, Action13) are added.
Stereotype << Event >> is set in the event function. The event function scope is public, accessible from all locations. The event function has no arguments and its return value is void.
A stereotype << Guard >> is set in the condition function. The scope of a conditional function is private, accessible only from within its own class. A conditional function has no arguments and its return value is a boolean.
Stereotype << Action >> is set in the event response function. The scope of the event response function is private. The event response function has no arguments and the return value is void.

  FIG. 5 is a diagram showing a configuration of a class diagram created by the model diagram creation device 1 from the state event table 200. In the class diagram 400 shown in the figure, the class name ComponentB is described at the top. An attribute is added below the class name, but nothing is described because this class has no attribute. Below the attribute, two event functions (function names E21, E22) are described in the item << Event >>. In the item << Action >>, six event response functions (function names Action21, Action22, Action23, Action24, Action25, Action26) are described.

  FIG. 6 is a diagram showing a state machine diagram created from the state event table 100 by the model diagram creation device 1. The state machine diagram 500 shown in the figure is a diagram showing a transition between the state 1 (STATE 1) and the state 2 (STATE 2).

  The transition from the state 1 to the state 2 is triggered by the event E11 and transitions with the action name Action11 under the condition Condition11. This transition is described in the Condition tag and Logic tag of the cell corresponding to the combination of state 1 and event 11 in the state event table 100.

  The transition from the state 2 to the state 1 is triggered by the event E12 and transitions with the action name Action12 under the condition Condition12. This transition is described in the Condition tag and Logic tag of the cell corresponding to the combination of state 2 and event 12 in the state event table 100.

  The transition from the state 2 to the state 2 is triggered by the event E11 and unconditionally changes with the action name Action13. This transition is described in the logic tag of the cell corresponding to the combination of state 2 and event 11 in the state event table 100.

  The initial state of the state machine diagram 500 is state 1 located at the top of the states included in the matrix of the state event table 100.

  FIG. 7 is a diagram showing a configuration of a state machine diagram created from the state event table 200 by the model diagram creation device 1. A state machine diagram 600 shown in the figure is a diagram showing a mutual transition between the state 3 (STATE 3), the state 4 (STATE 4), and the state 5 (STATE 5).

  The transition from the state 3 to the state 4 is triggered by the event E21 and the action name Action21. This transition is described in the logic tag of the cell corresponding to the combination of state 3 and event 21 in the state event table 200.

  The transition from the state 4 to the state 5 is triggered by the event E21 and the action name Action22. This transition is described in the logic tag of the cell corresponding to the combination of state 4 and event 21 in the state event table 200.

  The transition from the state 5 to the state 3 is triggered by the event E21 and the action name Action23. This transition is described in the logic tag of the cell corresponding to the combination of the state 5 and the event 21 in the state event table 200.

  Transition from the state 3 to the state 5 is triggered by the event E22 and the action name Action24. This transition is described in the logic tag of the cell corresponding to the combination of state 3 and event 22 in the state event table 200.

  The transition from the state 5 to the state 4 is triggered by the event E22 and the action name Action25. This transition is described in the logic tag of the cell corresponding to the combination of the state 5 and the event 22 in the state event table 200.

  The transition from the state 4 to the state 3 is triggered by the event E22 and the action name Action26. This transition is described in the logic tag of the cell corresponding to the combination of the state 4 and the event 22 in the state event table 200.

  The initial state of the state machine diagram 600 is state 3 located at the top of the states included in the matrix of the state event table 200.

  FIG. 8 is a diagram showing the configuration of a sequence diagram created by the model diagram creating apparatus 1 from the state event tables 100 and 200. A sequence diagram 700 shown in the figure is a diagram for giving a message flow from the class name ComponentA to the class name ComponentB.

  As a message related to the combination of the state 1 and the event 11, the event 21 is transmitted to the class name ComponentB under the condition Condition11. This message transmission is described in the Message tag of the cell corresponding to the combination of state 1 and event 11 in the state event table 100.

  As a message related to the combination of the state 2 and the event 11, the event 22 is unconditionally transmitted to the class name ComponentB. This message transmission is described in the Message tag of the cell corresponding to the combination of state 2 and event 11 in the state event table 100.

  As a message related to the combination of the state 2 and the event 12, the event 22 is transmitted to the class name ComponentB under the condition Condition12. This message transmission is described in the Message tag of the cell corresponding to the combination of state 2 and event 12 in the state event table 100.

  FIG. 9 is a flowchart showing an outline of the process of the model diagram creation method performed by the model diagram creation device 1. When the model diagram creation apparatus 1 receives a model diagram creation instruction signal from the input unit 2 (step S1: Yes), the class diagram (step S2), the state machine diagram (step S3), and the sequence diagram (step S4) Are created sequentially. When the model diagram creation instruction signal is not input (step S1: No), the model diagram creation device 1 repeats step S1. The order of creating the state machine diagram and the sequence diagram may be reversed. Hereinafter, the processing of steps S2 to S4 will be described in detail.

  FIG. 10 is a flowchart showing an overview of class diagram creation processing (step S2) performed by the model diagram creation device 1. It is assumed that a folder for model diagrams is generated in advance in the storage unit 4 of the model diagram creating apparatus 1 by input from the input unit 2. Hereinafter, the folder name of this folder is “Architecture”.

  First, the element configuration diagram creation unit 53 adds all components in which the state event table is described to the element configuration diagram (step S11). As an example, a case will be described in which the state event table 100 shown in FIG. 2 and the state event table 200 shown in FIG. FIG. 11A is a diagram illustrating a display example when the display unit 3 displays an element configuration diagram in which components are added under the control of the display control unit 54. In the element configuration diagram 801 shown in FIG. 11A, components (ComponentA and ComponentB) corresponding to two state event tables are described as a lower layer structure of Component, as shown in an area surrounded by a broken line (hereinafter referred to as a broken line area). ing. It should be noted that the broken line area is merely provided for convenience in order to clearly indicate the added portion, and is not actually displayed on the display unit 3.

  The model diagram creating apparatus 1 performs the processes of steps S12 to S16 described below for all the state event tables. First, in step S12, the structural diagram creation unit 51 and the element configuration diagram creation unit 53 add a class diagram and class elements (step S12). At this time, the structure diagram creating unit 51 performs a process of adding a class element to the class diagram. In addition, the element configuration diagram creating unit 53 adds a class diagram and class elements to the element configuration diagram. For example, when processing is performed on the state event table 100, a class diagram and class elements called ComponentA are added. FIG. 11B is a diagram illustrating a display example on the display unit 3 of the element configuration diagram to which the element configuration diagram creation unit 53 has added a class diagram and class elements. In the element configuration diagram 802 shown in FIG. 11B, a class diagram and class elements having different icons are added to the element configuration diagram 801 shown in FIG. 11A (see the broken line area).

  Thereafter, the structural diagram creation unit 51 and the element configuration diagram creation unit 53 add various functions to the class diagram and the element configuration diagram (step S13). For example, when processing is performed on the state event table 100, various functions include event functions E11 and E12, condition functions Condition11 and Condition12, event response functions Action11, Action12 and Action13, and functions Get from other classes. Set is added. FIG. 11C is a diagram illustrating a display example on the display unit 3 of the element configuration diagram to which various functions are added. In the element configuration diagram 803 illustrated in FIG. 11C, the above-described various functions are added to the element configuration diagram 802 illustrated in FIG. 11B (see the broken line area).

  Subsequently, the structural diagram creation unit 51 and the element configuration diagram creation unit 53 add attributes (step S14). For example, in the case of the state event table 100, an attribute attr is added. FIG. 11D is a diagram illustrating a display example on the display unit 3 of the element configuration diagram to which the attribute is added. In the element configuration diagram 804 illustrated in FIG. 11D, an attribute attr is added to the element configuration diagram 803 illustrated in FIG. 11C (see the broken line area).

  Thereafter, the display control unit 54 causes the display unit 3 to display the class diagram created by the structural diagram creation unit 51 (step S15). FIG. 11E is a diagram showing a display example of the class diagram on the display unit 3. The display screen 805 shown in the figure includes a class diagram display area 806 for displaying a class diagram 300 created by the structure diagram creation unit 51 based on the state event table 100, and an element configuration diagram 804 created by the element configuration diagram creation unit 53. Are displayed side by side. A class diagram name (Component A) is displayed at the top of the class diagram display area 806.

  The structural diagram creation unit 51 stores the created class diagram in the creation information storage unit 42 (step S16). Note that the model diagram creating apparatus 1 may perform the process of step S16 before step S15 or in parallel with step S15.

  The model diagram creating apparatus 1 performs the processes of steps S12 to S16 described above for all the state event tables. FIG. 11F is a diagram illustrating a display example on the display unit 3 of the element configuration diagram in which the element configuration diagram creation unit 53 has completed the processing up to step S14 for the state event table 200. In the element configuration diagram 807 illustrated in FIG. 11F, a tree structure of a class diagram related to ComponentB is added to the element configuration diagram 804 illustrated in FIG. 11D (see the broken line area). Also in this case, the element configuration diagram 807 and the class diagram 400 are displayed in parallel on the display unit 3 in step S15.

  The model diagram creation apparatus 1 returns to the main routine shown in FIG. 9 when class diagram creation processing is completed for all the state event tables.

  Next, a state machine diagram creation process (step S3) will be described. FIG. 12 is a flowchart for explaining an overview of a state machine diagram creation process performed by the model diagram creation device 1. This state machine diagram creation process is also repeated for all state event tables.

  First, the behavior diagram creation unit 52 and the element configuration diagram creation unit 53 add a state machine diagram (step S21). Specifically, the behavior diagram creation unit 52 starts creating a state machine diagram having the same name as the class diagram. On the other hand, the element configuration diagram creation unit 53 adds an element of the state machine diagram to a layer below the element of the class diagram of the element configuration diagram. FIG. 13A is a diagram illustrating a display example on the display unit 3 of the element configuration diagram to which elements of the state machine diagram are added. In the element configuration diagram 811 illustrated in FIG. 13A, the element of the state machine diagram of Component A is added to the lower layer of the element of the class diagram with respect to the element configuration diagram 807 illustrated in FIG. 11F (see the broken line area).

  Subsequently, the behavior diagram creation unit 52 and the element configuration diagram creation unit 53 add all necessary states to the state machine diagram (step S22). For example, when processing is performed on the state event table 100, state 1 (STATE1) and state 2 (STATE2) are added. FIG. 13B is a diagram illustrating a display example on the display unit 3 of the element configuration diagram in which a state is added to the state event table 100. In the element configuration diagram 812 shown in FIG. 13B, two state elements STATE1 and STATE2 are added to the element configuration diagram 811 shown in FIG. 13A (see the broken line area).

  Thereafter, the behavior diagram creation unit 52 and the element configuration diagram creation unit 53 add all the events necessary for the state machine diagram as trigger elements under the class from the event names in the state event table (step S23). For example, in the case of the state event table 100, events E11 and E12 are added. FIG. 13C is a diagram illustrating a display example on the display unit 3 of the element configuration diagram to which the event is added. In the element configuration diagram 813 illustrated in FIG. 13C, two events are added to the element configuration diagram 812 illustrated in FIG. 13B (see the broken line area).

  Subsequently, the behavior diagram creation unit 52 adds all necessary transitions to the state machine diagram (step S24). For example, when processing is performed on the state event table 100, a transition from state 1 to state 2 and a transition from state 2 to state 1 are added. This process corresponds to adding a transition with the state corresponding to the cell in which the TransitionState tag is described in the state event table as the transition source state (source) and the content of the TransitionState tag as the transition destination state (target). This process is not reflected in the element configuration diagram.

  Thereafter, the behavior diagram creation unit 52 adds an event name, a condition, and an action to the transition added in Step S24 (Step S25). For example, when processing is performed on the state event table 100, an event name E11, a condition name Condition11, and an action Action11 are first added to the transition from state 1 to state 2. In this process, a transition trigger whose name is an event name corresponding to a cell in which a TransitionState tag is described in the state event table is added. If there is a cell in which a Condition tag is described in the state event table, a transition guard is added with the value of the attribute name Func of the Condition tag as the guard function name. In addition, the content of Logic tag is made into an action. This process is also not reflected in the element configuration diagram.

  Subsequently, the behavior diagram creation unit 52 and the element configuration diagram creation unit 53 add a start element (step S26). Specifically, the model diagram creating apparatus 1 uses the top state of the state event table as an initial state and adds a transition from the start element to the initial state. For example, when processing is performed on the state event table 100, the initial state is STATE1. FIG. 13D is a diagram illustrating a display example on the display unit 3 of the element configuration diagram to which the start element is added. In the element configuration diagram 814 illustrated in FIG. 13D, a start element is added to the element configuration diagram 813 illustrated in FIG. 13C (see the broken line area).

  Thereafter, the display control unit 54 causes the display unit 3 to display the state machine diagram created by the behavior diagram creation unit 52 (step S27). For example, for the state event table 100, the display control unit 54 causes the display unit 3 to display the state machine diagram 500 shown in FIG.

  The behavior diagram creation unit 52 stores the created state machine diagram in the creation information storage unit 42 (step S28). Note that the model diagram creating apparatus 1 may perform the process of step S28 before step S27 or in parallel with step S27.

  The model diagram creating apparatus 1 performs the processes of steps S21 to S28 described above for all the state event tables. FIG. 13E is a diagram showing a display example on the display unit 3 of the element configuration diagram that has completed a series of state machine diagram creation processing (processing in steps S21 to S28) for the state event table 200. In the element configuration diagram 815 shown in the figure, a tree structure of a state machine diagram related to Component B is added to the element configuration diagram 814 shown in FIG. 13D (see the broken line area). Also in this case, the display control unit 54 causes the display unit 3 to display the element configuration diagram 815 and the state machine diagram 600 in parallel.

  The model diagram creation apparatus 1 returns to the main routine shown in FIG. 9 when the state machine diagram creation processing has been completed for all the state event tables.

  Next, a sequence diagram creation process (step S4) will be described. FIG. 14 is a flowchart showing an outline of sequence diagram creation processing performed by the model diagram creation device 1. Also for the sequence diagram creation process, the process is repeated for all state event tables.

  First, the control unit 5 confirms whether or not a Message tag is described in the state event table (step S31). When the message tag is described in the state event table (step S31: Yes), the control unit 5 proceeds to step S32. On the other hand, when the message tag is not described in the state event table (step S31: No), the control unit 5 proceeds to processing for another state event table. For example, the state event table 100 corresponds to a case where a Message tag is described, and the state event table 200 corresponds to a case where a Message tag is not described.

  In step S32, the behavior diagram creation unit 52 and the element configuration diagram creation unit 53 add a sequence diagram (step S32). Here, the behavior diagram creation unit 52 starts creating a sequence diagram having a predetermined name, and the element configuration diagram creation unit 53 uses the above-described name as the element name in the lower layer of the component of the component configuration diagram. Add diagram elements. FIG. 15A is a diagram illustrating a display example on the display unit 3 of the element configuration diagram to which elements of the sequence diagram are added. In the element configuration diagram 821 shown in FIG. 15A, elements of the sequence diagram are added to the element configuration diagram 815 shown in FIG. 13E (see the broken line area). In the first embodiment, the name of the sequence diagram is newly generated as ComponentC, but the method of setting the name is arbitrary.

  Subsequently, the behavior diagram creation unit 52 adds the transmission source class in the state event table to the sequence diagram (step S33). For example, when processing is performed on the state event table 100, a class with the class name ComponentA is added. This process is not reflected in the description of the element configuration diagram.

  Thereafter, the behavior diagram creation unit 52 and the element configuration diagram creation unit 53 add an element of the message end point (step S34). FIG. 15B is a diagram illustrating a display example on the display unit 3 of the element configuration diagram in which the element of the message end point is added. In the element configuration diagram 822 shown in FIG. 15B, three message end points (indicated by black circles) are added to the element configuration diagram 821 shown in FIG. 15A (see the broken line area).

  Subsequently, the behavior diagram creation unit 52 adds a message from the message end point to the transmission source class added in step S33 (step S35). The message name here is described in the format of “state name / event name (argument)”. For example, when processing is performed on the state event table 100, Message tags are described in three cells. For this reason, the behavior diagram creation unit 52 adds three messages. The message names of each message are “STATE1 / E11 ()”, “STATE2 / E11 ()”, and “STATE2 / E12 ()”. This process is not reflected in the description of the element configuration diagram.

  Thereafter, the behavior diagram creation unit 52 adds a class corresponding to the class name of the transmission destination to the sequence diagram (step S36). For example, in the case of the state event table 100, the class name of the transmission destination is ComponentB. This process is not reflected in the description of the element configuration diagram. If the destination class is not specified in the status event table, the destination class name can be an existing asset (legacy).

  Subsequently, the behavior diagram creation unit 52 adds a message to the transmission destination class (step S37). The message name here is described in the format of “[condition]: event name (argument)”. If there are no conditions, describe only "event name (argument)". For example, when processing is performed on the state event table 100, Message tags are described in three cells. For this reason, the behavior diagram creation unit 52 corresponds to three messages “[Condition11]: E21 ()”, “E22 ()”, and “[Condition12]: E22 ()”. Add to This process is not reflected in the description of the element configuration diagram.

  Thereafter, the display control unit 54 causes the display unit 3 to display the sequence diagram created by the behavior diagram creation unit 52 (step S38). For example, for the state event table 100, the sequence diagram 700 shown in FIG. 8 is displayed together with the element configuration diagram 822 shown in FIG. 15B.

  The behavior diagram creation unit 52 stores the created sequence diagram in the creation information storage unit 42 (step S39). Note that the model diagram creating apparatus 1 may perform the process of step S39 before step S38 or in parallel with step S38.

  When the model diagram creation device 1 finishes the sequence diagram creation processing for all the state event tables, the element configuration diagram creation unit 53 stores the element configuration diagram in the creation information storage unit 42 (step S40). Thereafter, the model diagram creating apparatus 1 returns to the main routine shown in FIG.

  According to the first embodiment of the present invention described above, a function that defines the structure of a structure diagram as a model diagram and a plurality of types of behavior diagrams is structured based on a state event table in which the combinations of states and events are described. Since a diagram and a plurality of types of behavior diagrams are automatically created, it is possible to generate a consistent object-oriented model while reflecting various aspects of the software to be developed.

  Further, according to the first embodiment, in the state event table, the function for determining the state transition in the state machine diagram, the function for determining the message transmission condition in the sequence diagram, and the function for determining the message destination in the sequence diagram Since it can be described, at least two behavior diagrams can be automatically created.

  In addition, according to the first embodiment, an element configuration diagram having information necessary for creating a structure diagram and a plurality of types of behavior diagrams as elements and showing the mutual relationship of the plurality of elements in a tree structure is created. Therefore, the user can easily recognize information for creating various model diagrams from the state event table.

  In addition, according to the first embodiment, every time an element is added to the element configuration diagram, the display on the display unit is switched and displayed, so the user can accurately grasp the progress of the model diagram creation process in real time. can do.

  Further, according to the first embodiment, since the element configuration diagram and the model diagram are displayed in parallel, the user can obtain various information by viewing one screen.

  Note that the procedure for creating the class diagram, the state machine diagram, and the sequence diagram described in the first embodiment is merely an example, and the procedure can be appropriately changed within a range where no contradiction occurs.

(Embodiment 2)
The second embodiment of the present invention is characterized by creating a model diagram that provides a mechanism for automatically incorporating existing software (legacy code) at the time of model generation. In the second embodiment, information indicating the class type is described in the state event table. The configuration of the model diagram creating apparatus according to the second embodiment is the same as the configuration of the model diagram creating apparatus 1 described in the first embodiment.

  In the second embodiment, a class diagram is taken as an example of a structure diagram, while a state machine diagram and a sequence diagram are taken as examples of behavior diagrams, but this is only an example.

  In the second embodiment, two types of state event tables are applied. The first type is a state event table that generates a class diagram of the state transition machine as in the first embodiment. The second type is a state event table that defines a function to be called by an existing software class. In the second embodiment, an item called class type is provided as information defining the type of state event table. The class type is described as [Class_Type] in the state event table. The name of the class type is “STM” for the first status event table and “Legacy” for the second status event table. Note that the name of this class type is merely an example.

In the cells constituting the matrix of the state event table and determined by the state and the event, a specific relationship between the state and the event is described according to the XML format. The specific description contents of the cell are as shown below.
[f_function name]
<Action>
<Condition Func = "condition function name">
<Logic> Event response function name </ Logic>
<Message> Class type STM destination class name @ event function name </ Message>
<Call> Class type Legacy class name @ function name </ Call>
<TransitionState> State name after transition </ TransitionState>
</ Condition>
</ Action>

Here, STM (State Transition Machine) is a software component represented by a state transition machine model. The STM class changes its state while calling an object method (function) in response to a trigger event from itself or from the outside.
Legacy is a software component of existing code that is not STM. Legacy classes do not change state when methods are called.

In the second embodiment, as compared with the first embodiment, a Call tag (<Call>) is added inside the cell. This Call tag is a tag for calling a function included in the class of the class type Legacy from the state transition machine class. If the function being called is a function with arguments,
<Call> Class type Legacy class name @ function name (argument 1, argument 2, ...) </ Call>
Is described. It is possible to describe multiple Call tags in one cell. When the Call tag is described in the cell, the behavior diagram creation unit 52 adds the element of the class corresponding to the class name as a link destination to the sequence diagram. Unlike the Messege tag, the Call tag is a destination software class.

  16 to 18 are diagrams illustrating configuration examples of the state event table stored in the state event table storage unit 41. In the following description, the names of specific states, events, response functions, etc. described in the state event table are, for example, “state 1”, “event 11”, “response function Action11”. The description will be made using the same name as 1, but this is a measure for facilitating comparison with the first embodiment, and a measure for avoiding redundant description of the same contents.

  First, the configuration of the status event table 910 shown in FIG. 16 will be described. The status event table 910 describes class types in addition to class names, matrices, function tables, and attribute tables. The class type of the state event table 910 is STM. The description contents of the state event table 910 excluding the class type are the same as the description contents of the state event table 100 described in the first embodiment.

  Next, the configuration of the status event table 920 shown in FIG. 17 will be described. The class type of the state event table 920 is STM. The description contents of the state event table 920 are almost the same as those of the state event table 200 described above, but the contents of the response functions [f_Action21] and [f_Action24] are slightly different. The response function [f_Action21] describes that a function Method1, which is a function having no argument of a class whose class name is LegacyComponent, is called. On the other hand, the response function [f_Action24] describes that a function Method2 (p1, p2) which is a function of a class whose class name is LegacyComponent and has arguments p1 and p2 is called.

  Next, the configuration of the status event table 930 shown in FIG. 18 will be described. The state event table 930 defines the classes described in the response functions [f_Action21] and [f_Action24] of the state event table 920, the class name is LegacyComponent, and the class type is Legacy. Unlike the state event table of the class type STM, the state event table 930 does not describe a matrix that defines state transition, and defines only a function [Func_Interface] that interfaces with existing software.

  In the state event table 930, as a specific function, a function Method1 having no argument, and a function Method2 having an int type argument p1 and a char [] type argument p2 are defined. Since the source codes of these functions Method1 and Method2 exist in the existing software, it is not necessary to specify only the function name in the state event table 930 and describe the contents (source code). Therefore, in the function table of the function [Func_Interface], the “content (source code)” column in the function tables of the state event tables 910 and 920 is not provided.

  Next, the configuration of the class diagram, state machine diagram, and sequence diagram created by the model diagram creation device 1 based on the state event tables 910, 920, and 930 will be described.

  The class diagram and state machine diagram created by the model diagram creating apparatus 1 from the state event table 910 are the same as the class diagram 300 (FIG. 4) and the state machine diagram 500 (FIG. 6) described in the first embodiment. The class diagram and state machine diagram created by the model diagram creation apparatus 1 from the state event table 920 are the same as the class diagram 400 (FIG. 5) and the state machine diagram 600 (FIG. 7) described in the first embodiment. is there. The sequence diagram created by the model diagram creation device 1 from the state event tables 910 and 920 is the same as the sequence diagram 700 (FIG. 8) described in the first embodiment.

  FIG. 19 is a diagram showing a configuration of a class diagram created by the model diagram creation device 1 based on the state event table 930. In the class diagram 940 shown in the figure, the class stereotype << Legacy >> and the class name LegacyComponent are described at the top. Below the class name, functions (function names Method1 and Method2) are described. Here, the function Method1 is a function having no argument, and its return value is void. The function Method2 is a function having two arguments of int type and char [] type, and its return value is void.

  FIG. 20 is a diagram illustrating a configuration of a sequence diagram created by the model diagram creating apparatus 1 based on the state event tables 930 and 940. The sequence diagram 950 shown in the figure is a diagram for giving a message flow from the class name ComponentB (class type STM) to the class name LegacyComponent (class type Legacy).

  The message associated with the combination of state 3 and event 21 is a call to function Method1. The message related to the combination of the state 3 and the event 22 is a call to the function Method2. By defining these calls in the sequence diagram, the existing software is automatically read when the model is generated.

  In the second embodiment, the outline of the process of the model diagram creation method performed by the model diagram creation device 1 is the same as that of the first embodiment (see FIGS. 9, 10, 12, and 14).

  FIG. 21 is a diagram illustrating a display example when the display control unit 54 causes the display unit 3 to display an element configuration diagram to which all components have been added. In the element configuration diagram 960 shown in the same figure, five components (component names: ComponentA, ComponentB, LegacyComponent, ComponentC, and ComponentD) are added. In the element configuration diagram 960, the lower layer structure of Component A, Component B, and Component C is in a non-display state. The lower layer structure of Component A, Component B, and Component C is the same as that described in FIG. 15B.

  In the broken line area LC, a class diagram of LegacyComponent and functions Method1 and Method2 are described as elements of the component having the component name LegacyComponent.

  In the broken line area D, as a component element having the component name ComponentD, a sequence diagram whose name is ComponentD and two message end points are described.

  According to the second embodiment of the present invention described above, the same effect as in the first embodiment described above can be obtained.

  Further, according to the second embodiment, since the existing software class is provided as the class type corresponding to the class diagram in addition to the class representing the state transition machine, it is conventionally buried in the source code. The part that has been used can be extracted as an object and can be easily reused.

  Further, according to the second embodiment, since the function having the function of calling the existing software class is described in the state event table, when the model is generated, the apparatus for generating the model Source code can be automatically imported into the model without human intervention. Therefore, the user does not need to analyze whether the source code of the existing software is reusable, and the model can be generated more quickly.

  Up to this point, the mode for carrying out the present invention has been described. However, the present invention should not be limited only by the two embodiments described above. For example, in the present invention, the structure diagram creation unit and the behavior diagram creation unit may be provided with a function of checking the consistency of the created model diagram. In this case, it is more preferable to display the check results of the structure diagram creation unit and the behavior diagram creation unit on the display unit.

  Further, the present invention provides a product line type software development including domain engineering that develops a domain that is a reusable software component and application engineering that develops software that is a product by using the domain. It is also useful when creating model diagrams necessary for designing line architecture (component diagrams).

  Note that the names of various model diagrams, states, events, functions, components, classes, class types, and the like used in this specification are merely set for illustrative purposes.

DESCRIPTION OF SYMBOLS 1 Model diagram creation apparatus 2 Input part 3 Display part 4 Storage part 5 Control part 41 State event table storage part 42 Creation information storage part 51 Structure drawing creation part 52 Behavior figure creation part 53 Element structure figure creation part 54 Display control part 100, 200, 910, 920, 930 State event table 300, 400, 940 Class diagram 500, 600 State machine diagram 700, 950 Sequence diagram 801, 802, 803, 804, 807, 811, 812, 813, 814, 815, 821, 822, 960 Element configuration diagram 805 Display screen 806 Class diagram display area

Claims (11)

In a model diagram creation device that creates a model diagram necessary for generating an object-oriented model of software using a unified modeling language,
Functions that are defined according to combinations of states and events in the model diagram, functions that define the structure of the class diagram and multiple types of behavior diagrams as model diagrams, and information that defines the class types corresponding to the class diagram A storage unit for storing a state event table in which is described,
A structure diagram creating unit that creates a class diagram based on the state event table stored in the storage unit;
A behavior diagram creation unit that creates a plurality of types of behavior diagrams based on a state event table stored in the storage unit;
A model drawing creation device characterized by comprising: The state event table is:
The functions for determining the configuration of the plurality of types of behavior diagrams include a function for determining state transitions in a state machine diagram, a function for determining message transmission conditions in a sequence diagram, and a function for determining message destinations in a sequence diagram. The model diagram creation device according to claim 1, wherein   3. The model diagram creation apparatus according to claim 1, wherein the class types include a class representing a state transition machine and an existing software class. In the state event table where the class type is the class of the existing software,
4. The model diagram creating apparatus according to claim 3, wherein only the name of the function is described as information on the function included in the existing software. In the state event table in which the type of the class is a class representing the state transition machine,
5. The model diagram creation apparatus according to claim 3, wherein a function for calling a function of the existing software class can be described.   It further includes an element configuration diagram creating unit that creates an element configuration diagram having information necessary for creating the class diagram and the plurality of types of behavior diagrams as elements, and showing a mutual structure of the plurality of elements in a tree structure. The model diagram creation device according to any one of claims 1 to 5. A display unit capable of displaying the element configuration diagram;
A display control unit that switches and displays the display in the display unit each time the element configuration diagram creation unit adds an element to the element configuration diagram;
The model diagram creation device according to claim 6, further comprising: The display unit
The class diagram and the plural types of behavior diagrams can be displayed,
The display control unit
8. The model diagram creating apparatus according to claim 7, wherein the class diagram and the behavior diagram created by the structure diagram creating unit and the behavior diagram creating unit are displayed on the display unit in the order of creation. The display control unit
9. The model diagram creation apparatus according to claim 8, wherein the element configuration diagram, the class diagram, and the behavior diagram are displayed side by side on the display unit. In the model diagram creation method executed by the model diagram creation device that creates the model diagram necessary for generating an object-oriented model of software using a unified modeling language,
Functions that are defined according to combinations of states and events in the model diagram, functions that define the structure of the class diagram and multiple types of behavior diagrams as model diagrams, and information that defines the class types corresponding to the class diagram A class diagram creating step for creating a class diagram with reference to the state event table from the storage unit storing the state event table in which is described,
A behavior diagram creating step of creating a plurality of types of behavior diagrams with reference to the state event table from the storage unit;
A model drawing creation method characterized by comprising: In the model diagram creation device that creates the model diagram necessary for generating an object-oriented model of software using a unified modeling language,
Functions that are defined according to combinations of states and events in the model diagram, functions that define the structure of the class diagram and multiple types of behavior diagrams as model diagrams, and information that defines the class types corresponding to the class diagram A class diagram creating step for creating a class diagram with reference to the state event table from the storage unit storing the state event table in which is described,
A behavior diagram creating step of creating a plurality of types of behavior diagrams with reference to the state event table from the storage unit;
A model diagram creation program characterized by having

Images