KR100609240B1 - Method and apparatus for generating diagram modeling tools with user's customization requirements based on mof meta-models - Google Patents

Abstract

The present invention relates to an apparatus and method for supporting a new diagram modeling tool by using meta information defined based on a meta-object facility (MOF) metamodel, and to defining various metamodels based on the MOF. It allows you to dynamically generate visual diagram modeling tools based on the model. Therefore, it provides a meta computer case software tool that has extended notation and behavior mechanisms for frequently changeable domains and creates diagram modeling tools that can dynamically reflect tool user requirements. Has characteristics. The creation of various diagram modeling tools that reflect user requirements based on MOF-based metamodels enables the automatic generation of code that configures different diagram modeling tools for different domains and plug-ins. Can be reused by componentizing in the form of. Therefore, the present invention has the effect that it is possible to efficiently produce a variety of different diagram modeling tools that are highly reusable and portable.

MOF, meta-model, meta-CASE tool, diagram-modeling tool, user customization

Description

METHOD AND APPARATUS FOR GENERATING DIAGRAM MODELING TOOLS WITH USER'S CUSTOMIZATION REQUIREMENTS BASED ON MOF META-MODELS}

1 is a flowchart of a system operation according to the present invention;

2 is a diagram illustrating a tree structure of meta information representing a node that is a basic modeling element of a diagram;

3 is a diagram illustrating a tree structure of meta information representing link element information used to link node elements;

4 is a system configuration according to the present invention,

5 is a diagram illustrating a modeling tool user interface screen provided by the system of the present invention;

6 is a diagram illustrating a part of an example of modeling tool information generated by a user using a modeling tool definer;

7 illustrates an execution screen of an automatically generated diagram modeling tool.

The present invention relates to a technology for automatically generating implementation code constituting a modeling tool, and in particular, to define a metamodel to generate a modeling tool, and the element information constituting the modeling tool based on the metamodel MOF metamodel that can automatically generate different modeling tools needed by users with Meta CASE tools that support the functions specified above. And apparatus and method for generating diagram modeling tools based on user requirements.

Existing CASE tools consist of features and components that were determined at the time of tool development, so they cannot be extended to have new components or functions. For example, in the preceding paper of `` Application Development using a Meta-Repository based Framework '' published by ECOOP in 1997, when developing a user application, the model is visually edited to obtain a part of the implementation code, and the generated model information is meta-model based. It describes a framework that saves in the repository and extracts the stored model information when the user's requirements are changed or added to enable further editing.

In this paper, we need the ability to model, examine modeled information, and generate implementation code for the definition of the diagram model. When the user's chosen domain changes or the user's requirements change, the environment of the preceding paper cannot automatically provide the user with a new diagram modeling tool. Therefore, whenever a new tool is needed, a new model must be modeled and the tool must be coded by the developer to create the tool.

This is a huge burden on developers and inefficient production of new tools every time. Therefore, there is a need for a meta CASE tool that provides an effective and automated way to create new diagram modeling tools.

In general, existing meta-case tools that generate modeling tools for modeling diagrams define different meta-modeling languages and define meta-model information in a form that can only be recognized by each meta-case tool. define. The use of non-standardized metamodeling languages requires separate analysis engines for analyzing metamodel information defined using individually defined metamodeling languages. In addition, meta-model information defined using different meta-modeling languages is incompatible with each other, so it is not efficient to define expressive and compatible meta-model information.

In addition, in some cases, the defined metamodel information is only suitable for a specific field, which may increase the developer's effort in extending the metamodel components and the analysis engine to create a new diagram modeling tool. In this case, the work performed is not much different from the work of directly implementing individual diagram modeling tools, and there is a big difference from the output that can be produced through the environment in which various modeling tools are generated.

And most of the diagram modeling tools to date are mostly CASE tools that provide semi-automated implementation code through modeling. There is no device to generate.

In 1997, J. Ebert, R. Suttenbach, and I. Uhe's previous paper, Meta-CASE in Practice: a Case for KOGGE, describes KOGGE, a Meta-CASE tool that creates modeling tools that support visual modeling languages and methods. (KOblenz Generator for Graphical design Environments).

This preceding paper is based on its own tool description, Extended Entity Relationship (ERE) and GRAL (GRAph specification language), to create a tool.

These descriptions are created by the supporting tools that support each and create modeling tools using the information created by the tools. This feature requires the expansion of EER and GRAL to extend the metamodel, and the tools that support it also need to be changed to extend it. Also, because it is based on a nonstandard metamodel, the metamodel cannot be used in other Meta-CASE tools.

Another prior patent published in April 2001, Apparatus and Method for Producing Modeling Tools, uses Meta Meta Definition Language to construct meta information and analyze defined meta model information to generate new modeling tools. Describes the tool.

However, in this patent, the domain to be configured is limited to the field of database system, and the generated modeling tool is a modeling tool that can model only the objects that make up object-oriented database or relational database through UMA (Universal Modeling Architecture). The disadvantage is that it produces.

In addition, since the meta-model language used is a user-defined non-standard meta-modeling language, it is difficult to extend the analysis engine for analyzing the defined metamodel information and the semantics for semantic analysis.

In addition, it cannot be applied to various domains, and thus it is impossible to derive meta-model-based diagram modeling tools and results generated using techniques for constructing a standardized meta-model language and meta-case tools.

Meta CASE tool configuration method that automatically generates a diagram modeling tool that can model the model in the form of diagrams, and the device is characterized by the refined modeling elements and attributes based on the user's needs as the expression power required by the CASE tool to assist modeling increases It cannot be expanded to reflect them.

The metamodeling language and metamodel information, once defined, must be reusable and extensible as needed, so the need to be defined through standardized methods and standardized modeling languages is a prerequisite. In addition, it is possible to express various diagram models based on information defined by metamodels such as architecture diagrams representing various fields of models, class diagrams related to implementation, activity diagrams, etc. The ability to automatically generate modeling tools enables these meta-case tools to create and provide extended diagram modeling tools for editing new models without the need for developers to write code.

The present invention has been implemented to solve the above-described problems of the prior art, MOF that can automatically generate a diagram modeling tool without having to directly write code for a diagram modeling tool that supports modeling a new diagram The purpose is to provide an apparatus and method for generating diagram modeling tools based on metamodels and user requirements.

In order to achieve the above object, the present invention is characterized in that it supports to define a MOF-based metamodel suitable for an area so as to develop a system of various areas.

In order to achieve the above object, the present invention is characterized by automatically generating a diagram modeling tool that supports visual modeling using a user's requirements defined based on a metamodel.

In order to achieve the above object, the present invention is characterized in that the implementation code of the generated diagram modeling tool is componentized in the form of a plug-in and can be integrated and used in an existing integrated development environment.

To this end, according to an embodiment of the present invention, as an apparatus for generating a diagram modeling tool based on a MOF metamodel and user requirements, a metamodel that enables a user to define a MOF metamodel using a MOF class modeling construct It consists of an editor and a metamodel validator that verifies that the metamodel defined in the metamodel editor conforms to the MOF definition rules, and defines and edits a metamodel based on the MOF when the information required to generate the modeling tool is input and selected by the user. Intermediate mediation between the meta model definer, a meta model analyzer that analyzes user-defined MOF meta model information, a model management API generator that automatically generates a model management API using meta model analysis information through the meta model analyzer, and a modeling tool. The module that generates the model management wrapper API that acts. It consists of the Dell Management Wrapper API Generator, which is a model manager that analyzes the MOF-based metamodel and generates code to access model management structure and model definition information in a consistent form, and defines node information, which is the basic modeling element of the diagram. It consists of a node information builder and a link information builder that defines link information that serves to connect the nodes of the diagram defined by the node information builder according to the relationship of the nodes, modeling to define the configuration information of the modeling tool to create Analyze the tool definer and the modeling tool information defined in the modeling tool definer to generate implementation code constituting the diagram modeling tool, and generate the modeling tool as a plug-in component to connect with the integrated development environment. Generator and the meta mod Provides a modeling tool generating device based on MOF metamodel and user requirements including a product repository for storing outputs generated from Dell definer, model manager, modeling tool definer, and diagram modeling tool generator.

In addition, according to another embodiment of the present invention, as a method for generating a diagram modeling tool based on a MOF metamodel and user requirements, when a user inputs and selects information necessary for generating a modeling tool, the diagram modeling tool based on the input information is used. Analyzing the modeling tool information that can be generated and the meta model information reflected in the modeling tool information, generating code of the diagram modeling tool based on the analyzed modeling tool information and the meta model information; Generating model management API code for managing a model created by a diagram modeling tool based on the meta model information, and generating a model management wrapper API serving as an intermediate between the modeling tool code and the model management API code. And the generated diamond Provides a method of generating a diagram modeling tool based on the MOF metamodel and user requirements including generating a plug-in for the RAM modeling tool and model management API code, and storing the generated plug-in of the modeling tool in a repository. .

Hereinafter, with reference to the accompanying drawings will be described in detail a preferred embodiment of the present invention.

Prior to the description, the present invention defines a diagram modeling tool desired by a developer by defining user requirements related to the notation, constraints, rules, functions, menus, and icons required to generate various diagram modeling tools as meta information based on the MOF metamodel. With that in mind, developers don't have to implement any code to create new diagram modeling tools.

In addition, the present invention is portable and scalable even if the domain to be modeled based on the MOF, which is an industry standard and a standardized means of expressing the metamodel, for information for generating a diagram modeling tool defined based on the MOF metamodel. You can define metamodels. In the present invention, scalable metamodel information is a basic data for generating a tool for editing a diagram model. In this regard, a metamodel defined based on MOF can generate a diagram modeling tool with excellent modeling ability. Imply that there is.

In the present invention, meta-model information for generating a diagram modeling tool is a representational tool that can be used to model various diagrams using meta-model information defined and defined based on the industry standard MOF worldwide, without any code implementation. Create it and provide it to the tool user. Defining metamodel information based on MOF provides extensibility to expand information when metamodel information needs to be expanded, and provides the analysis power and ease of analysis of the analysis engine that analyzes metamodels defined based on MOF. In addition, various diagram modeling tools having new functions and features can be obtained by componentizing them in the form of plug-ins through external meta model information defined based on MOF.

The automatic generation apparatus and method of the diagram modeling tool based on the MOF metamodel and the user requirements presented in the present invention minimize and automate the restrictions that may exist in creating and extending a new diagram modeling tool. Differentiate from the CASE tool. It also facilitates the extension of metamodels needed to create diagram modeling tools, maintains compatibility in importing and using externally defined metamodel information, and Unified Modeling Language (UML) and XML (eXtended Markup Language) other than MOF. ), Which makes it interoperable with standards such as XML Metadata Interchange (XMI) and Java Metadata Interface (JMI).

Hereinafter, with reference to the accompanying drawings will be described an embodiment of the present invention;

1 is a flowchart illustrating a system operation process of the present invention.

First, as shown in step S101, a request is made to create a diagram modeling tool so that a diagram modeling tool required by a user of the present system can be generated.

In step S102, to define the components of the diagram modeling tool, input diagram modeling tool definition information stored in the output repository or select basic metamodel information.

In step S103, a user supports editing of node information, which is a basic modeling element supported by a modeling tool, and in step S104, editing information about a link, which is an element for connection between nodes, is supported. That is, in step S103 and step S104, the user may define modeling tool information for generating a diagram modeling tool using meta-model information desired by the user.

The modeling tool information is analyzed in step S105 with respect to the generated modeling tool information and the metamodel information reflected in the modeling tool information. In step S106, the metamodel information applied to the modeling tool information is analyzed.

In step S107, the code of the diagram modeling tool is generated based on the analyzed modeling tool information and the metamodel information.

In step S108, a model management API (Application Programming Interface), which is code for managing a model created in the diagram modeling tool, is automatically generated based on the analyzed metamodel information.

In step S109, a model management wrapper API is automatically generated that serves as an intermediate between the code of the modeling tool and the model management API.

In step S110, a plug-in is automatically generated for the generated diagram modeling tool and model management API code.

In step S111, the plug-in of the generated modeling tool is stored in the modeling tool plug-in repository of the output repository, so that the user can use the generated diagram modeling tool when modeling the system.

Environments that create diagram modeling tools based on meta information must meet the following requirements to create new diagram modeling tools tailored to the user's requirements.

First, it must be able to edit or receive the MOF metamodel for generating diagram modeling tools.

Second, in addition to the meta model information, the definition information of the diagram modeling tool should be able to define additional attribute and notation information to be used in the diagram modeling tool.

Third, the diagram modeling tool generator should be able to define the information to create the diagram modeling tool based on the MOF metamodel.

Fourth, the diagram modeling tool generator should be available as information for creating modeling tools as definition information of modeling tools.

Fifth, there must be a model management mechanism that can manage the relationship between the model elements of the MOF metamodel and the instances of each model element.

Sixth, the interface to access the model should be created with consistent naming rules that can be expected in the diagram modeling tool generator.

Seventh, the diagram modeling tool generator should be able to automatically generate the implementation code constituting the modeling tool using the MOF metamodel information and the definition information for generating the modeling tool.

2 and 3 illustrate meta information input by a user for automatically generating a diagram modeling tool.

User-defined meta information is information defined to express abstract grammar of diagram elements to be modeled in diagram modeling tool. The basic information that the user must enter to automatically generate the diagram modeling tool includes behavior information such as notation for each model element, user-defined attributes, relationship between notation and model elements, and menu action for each model element.

Notation information represents graphical symbol and icon information of the modeling element.

The user-defined attribute information includes attribute information selected by the user among the attributes defined in the MOF metamodel and semantic information additionally defined by the user for each attribute.

The relationship information between the notation and the model element expresses how the model elements and the notation are mapped.

Behavior information is represented by user-defined menu actions and model management wrapper API information that are mapped to be performed on each modeling element.

2 illustrates meta information used to represent a node, which is a basic modeling element of a diagram. This is represented using tags to specify the functionality of the diagram modeling tool associated with the node in each node, diagram. The user can define node information by assigning a desired value to a tag corresponding to each node.

The '<node>' tag consists of four attributes: 'node type', 'paletteicon', 'metamodelname', and 'description'. 'node type' represents node type information and 'paletteicon' represents the name of the icon file. 'metamodelname' represents the package name of the model element corresponding to the node in the metamodel, and 'description' describes the node description.

The '<node>' tag includes three tags, '<notation>', '<property>' and '<actions>' as dependent tags. '<notation>' tag indicates information about the notation, 'type' indicating the type of the notation, 'isResizable' indicating whether the notation is resizable, 'color' indicating the color information of the notation, and each notation can overlap. 'IsOverlay' information indicating whether there is an additional attribute is described. In addition, the '<notation>' tag includes tags such as '<label model>', '<attribute model>', and '<operation model>' that map model information of the detailed area of each notation as a dependent tag.

The '<property>' tag represents the attribute of each element, 'name' represents the mapping element name with the model element, 'type' represents the type of the attribute, and 'setter / getter' is required to set and get attribute model information. 'Describe the method name as an attribute.

The '<action>' tag represents the menu action and model management action of the modeling element and describes each action name and method name, which is the action information.

3 shows meta information used to represent link element information used to link node elements. The '<link>' tag represents a diagram element used to link the '<node>' element and has attribute information of 'type', 'paletteicon', 'metamodelname' and 'description' like the node type attribute.

The '<link>' tag includes dependent tags such as '<notation>', '<connecting elements>', and '<action>' tags.

'<notation>' tag expresses link type information like node notation information and describes 'type' and 'color' information. Include the '<label model>' and '<attribute model>' tags as dependent tags to map detailed model information for the link. The '<connecting elements>' tag includes a '<element model>' tag as a dependent tag to represent the kind of element to be connected to the link.

4 is a system configuration diagram of the present invention, which is a meta CASE tool for generating a diagram modeling tool based on a MOF metamodel, and includes four accessory devices and one output repository to have the above-described differences.

That is, the system 400 generates a metamodel definer 410 for defining and editing a MOF metamodel, a code for analyzing a metamodel based on the MOF, and accessing model management structure and model definition information in a consistent form. Model manager 450 to automatically create, modeling tool definer 470 that defines the components, properties, functions of the modeling tool to create, the implementation code constituting the diagram modeling tool automatically generates a plug-in component The diagram modeling tool generator 490 is characterized in that it is composed of a product storage 430 for storing the various products generated from the above four accessories.

The metamodel definer 410 is comprised of a metamodel editor 412 that allows a user to define a MOF metamodel and a metamodel verifier 414 that verifies a metamodel defined according to MOF definition rules.

The output repository 430 includes a metamodel repository 432 for storing metamodels created by the metamodel definer 410, a modeling tool information repository 434 for storing information defined by the modeling tool definer 470, and diagram modeling. The model generator includes a modeling tool plug-in repository 436 for storing plug-ins of the modeling tool generated by the tool generator 490 and a model repository 438 for storing diagram models created by a user using the modeling tool.

The model manager 450 may include a meta model analyzer 452 that analyzes user-defined meta model information, a model management API generator 454 that automatically generates a model management API using meta model analysis information, a model management API, and a modeling tool. It consists of a model management wrapper API generator 456 that generates a model management wrapper API that acts as an intermediate intermediary.

The modeling tool definer 470 defines a node information builder 472 that defines node information that is a main modeling element of the diagram, and a link information builder 474 that defines link information that serves to connect the nodes of the diagram according to the relationship between the nodes. It is composed of

The diagram modeling tool generator 490 is a modeling tool generator that automatically generates modeling tool code based on the modeling tool information analyzer 492 and the analyzed modeling tool information. And a plug-in generator 496 that automatically generates the generated modeling tool as a plug-in type component and works with the integrated development environment.

The metamodel definer 410 defines a UML metamodel using the MOF to define various metamodels. The meta model can be defined using the UML class modeling construct supported by MOF.

The model manager 450 generates a model management API for accessing model information through JMI, which is a MOF-Java mapping. The model management API is required to access the model in the model code of the diagram modeling tool, so the code for calling the model management API must be generated in the diagram modeling tool. To actually call these model management APIs, you need to understand the metamodel information. Therefore, the model management wrapper API is created so that the model information can be easily utilized without the meta model information for the automatic generation of the diagram modeling tool. The model management wrapper API is defined and generated in a form with consistent rules independent of the metamodel. In the diagram editor, model information can be accessed by calling the corresponding wrapper API according to the model management wrapper API definition rules.

The modeling tool definer 470 supports defining additional information necessary for generating a diagram modeling tool so that the desired diagram can be edited in addition to the meta model information. After defining the modeling elements to compose the diagram, defining mapping with the elements defined in the metamodel, and defining the attribute information of each modeling element. Model information included in the metamodel may be used as the attribute information, and information not included in the metamodel may be additionally defined as an attribute. After setting the model-related information of each element, define the notation shape how modeling elements will be represented on the diagram. Defines mapping of detailed model information according to defined notation type and defines menu action and model management action information which each modeling element has.

The modeling tool generator 494 receives analysis information about the modeling tool as an input, and applies code of a model-view-control (MVC) pattern to divide the model, view, and controller to generate code of the diagram modeling tool. The information constituting the modeling information generated by the diagram modeling tool is classified into two models for storing model information of the metamodel and views and attribute information of the diagram that do not appear in the metamodel. Access to the model instance of the metamodel is through the model management API generated by the model management API generator. If the model management API is to be used directly, the modeling tool requires information about the structure of the metamodel. However, because the modeling tool generator is difficult to understand the structural information of the metamodel, for this purpose, instead of directly using the interface accessed through the model management API, diagram modeling to manage the model through the model management wrapper API generated by the model management wrapper API generator. The model code of the tool is generated. The view information of the diagram modeling tool is modeled by using the type information and notation information of the notation inputted by the user for each modeling element to be defined in the modeling tool definer, and mapping information about the metamodel and connection according to the type of notation. Generated by the view code of the element. Controller information of the diagram modeling tool generates code of the basic control action and basic editing action of the diagram modeling tool, and additional action information of each modeling element entered by the user in the modeling tool definer is generated as action code. The environment in which the generated diagram modeling tool is integrated and used is the integrated development environment. The integrated development environment consists of a set of plug-ins, and the integrated tool is composed of one or more plug-ins. Each plug-in consists of a plug-in XML file that specifies Java binary code and integration-related information. Therefore, the plug-in generator 496 performs a function of automatically generating the generated diagram modeling tool as a plug-in to support executing the diagram modeling tool as a plug-in.

5 illustrates a user interface screen of the modeling tool definer 470 that provides a user to define information of the modeling tool. Reference numerals 500 and 520 denote screens for editing the basic information of the node / link. If you click the Add button (reference number 502) to add node or link information at reference number 500, a reference number 520 screen appears. For each node / link on the screen 520, each node name or link name is input in an input field of reference number 522, and a metamodel element mapped to a node or link is input in an input field of reference number 524. In the input field at 526, specify the UMLnotation shape used to visually represent the node or link in the diagram, and specify the node or link's icon file path in the input field at 528.

Reference numerals 540 and 560 are screens provided for editing the attribute information for each node / link. Clicking the Add button (reference number 542) to add attribute information for the node or link at reference number 540 displays a reference number 560 screen. On the screen 560, for each attribute of each node / link, enter each attribute name in the input field of reference number 562, and enter the node or link name to which the attribute is to be assigned in the input field of reference number 564. Specifies the metamodel access API for accessing the corresponding model element of the attribute in the input field of reference number 566.

6 illustrates an example of modeling tool information generated by a user by using the modeling tool definer 470. In FIG. 6, information of a diagram modeling tool is defined based on a metamodel of a Component Collaboration Architecture (CCA) specification and an entity specification of a UML profile for EDOC. The CCA specification consists of elements of process components, protocols and ports. Process components are components that perform functions and interact with other process components through ports, and the interactions are represented by protocols. Ports represent different types of interfaces. The main component of an entity specification is an entity, which is used to model the data information in the system. The example modeling tool you want to create takes process components, protocols, ports, and entities as modeling elements and allows you to model system architectures that describe the interactions between components such as process components and entities. To this end, reference numeral 602 includes meta-model element information corresponding to icon path information for an icon to be displayed in the modeling tool palette for each node or link.

Reference numeral 604 includes mapping information of the shape of the notation and metamodel elements for the detail region of the notation. Reference numeral 606 includes model management wrapper API information for getting and setting attribute names, attribute types, and attribute information.

Reference numeral 608 includes model management wrapper API information and additional user-defined action information for model management actions such as model instance creation and deletion of each modeling element.

7 illustrates an execution screen of a diagram modeling tool that is automatically generated by using user-defined modeling tool information. Reference numeral 702 denotes a screen displaying the generated diagram modeling tool and reference numeral 704 denotes a palette of the generated diagram modeling tool. Reference numeral 706 denotes a screen in which the diagram modeling tool generated in the plug-in structure of the integrated development environment is included as a plug-in.

As described above, the present invention automatically generates a diagram modeling tool required by a user without complicated implementation process using modeling tool information input by the user based on the MOF metamodel.

As described above, the "automatic generation apparatus and method of diagram modeling tool based on MOF metamodel and user requirements" according to the present invention defines meta information necessary for automatically generating diagram modeling tool based on MOF metamodel. You can create different diagram models for different disciplines. Whenever the user's requirements for the modeling tool change, the apparatus and method generates a highly expressive diagram modeling tool based on standardized metamodel information, and imports metamodel information according to the MOF standard defined externally. Provides interoperability to create modeling tools. The generated diagram modeling tool is componentized in the form of a plug-in to provide convenience of reuse.

As mentioned above, although this invention was demonstrated concretely based on the Example, this invention is not limited to this Example, Of course, various changes are possible within the range which does not deviate from the summary.

Claims (13)

A device for generating diagram modeling tools based on MOF metamodels and user requirements. It consists of a metamodel editor that allows the user to define the MOF metamodel using the MOF class modeling construct, and a metamodel verifier that verifies that the metamodel defined in the metamodel editor conforms to the MOF definition rules. A metamodel definer for defining and editing a MOF-based metamodel once input and selection of A meta-model analyzer that analyzes user-defined MOF meta-model information, a model management API generator that automatically generates a model management API using the meta-model analysis information through the meta-model analyzer, and a model management wrapper that acts as an intermediate between modeling tools. It consists of a model management wrapper API generator that generates an API, a model manager that analyzes the MOF-based metamodel and generates a consistent form of code for accessing model management structure and model definition information. It consists of a node information builder that defines node information, which is a basic modeling element of the diagram, and a link information builder that defines link information that serves to connect nodes of the diagram defined by the node information builder according to the relationship of the nodes. A modeling tool definer defining configuration information of a modeling tool to be designed; A diagram modeling tool generator for generating an implementation code constituting a diagram modeling tool by analyzing the modeling tool information defined in the modeling tool definer, and generating the generated modeling tool as a plug-in component and interworking with an integrated development environment; Output storage for storing outputs generated from the meta model definer, model manager, modeling tool definer, diagram modeling tool generator MOF metamodel including and diagramming tool generation device based on user requirements. delete delete delete The method of claim 1, The diagram modeling tool generator, A modeling tool information analyzer for analyzing modeling tool information defined by the modeling tool definer; A modeling tool generator for automatically generating code of a modeling tool based on the modeling tool information analyzed by the modeling tool information analyzer; Plug-in generator that automatically generates the modeling tool generated by the modeling tool generator as a plug-in to be used in combination with the integrated development environment. MOF metamodel including and diagramming tool generation device based on user requirements. The method of claim 1, The output store, A metamodel repository for storing the MOF metamodel created by the metamodel definer; A modeling tool information store for storing modeling tool information defined in the modeling tool definer; A modeling tool plug-in repository for storing modeling tool plug-ins generated by the diagram modeling tool generator; Model repository for storing diagram models created by the user using the modeling tool MOF metamodel including and diagramming tool generation device based on user requirements. The method of claim 1, The model management wrapper API generator, Creates a model management wrapper API that is defined in a form with consistent rules independently for the metamodel, and calls the corresponding wrapper API according to the model management wrapper API definition rules in the generated diagram editor to provide access to model information. Apparatus for generating diagram modeling tools based on MOF metamodels and user requirements. The method of claim 1, The node information builder, It supports to define basic information of node, notation information, property information and action information, which are basic modeling elements for constructing diagram. The basic information includes a node type, an icon file name, a mapping with an element defined in a metamodel, and description information about the node. The notation information includes a UML (Unified Modeling Language) notation type, information on whether the notation can be adjusted, color information of the notation, information on whether the notation can be overlapped, and model element mapping information on detailed regions of each notation. The attribute information includes attribute type, mapping information with elements defined in the metamodel, and method information for accessing attribute model information. The action information includes an action name and method information for a menu action and a model management action of each node, so that the information can be defined so that the diagram modeling tool generation device based on the MOF metamodel and user requirements is provided. . The method of claim 1, The link information creator, The basic information, notation information, attribute information, and action information of the link necessary for the connection between the nodes can be defined as in the case of the node information, and the node information that can be connected to the link can be defined. Device for generating diagram modeling tools based on MOF metamodels and user requirements. The method of claim 5, The modeling tool information analyzer, An apparatus for generating a diagram modeling tool based on a MOF metamodel and a user requirement characterized by analyzing modeling tool information XML (eXtended Markup Language) document defined in the modeling tool definer to configure modeling tool information required by the modeling tool generator. . The method of claim 5, The modeling tool generator uses the editor analysis information generated by the modeling tool information analyzer to automatically generate models, views, and controller codes constituting the modeling tool without user intervention. Diagram modeling tool generation device. The method of claim 5, The plug-in generator extracts the plug-in information based on the modeling tool information created in the modeling tool definer so that the code of the modeling tool generated by the modeling tool generator can be used as a plug-in in the integrated development environment. A device for generating diagram modeling tools based on MOF metamodels and user requirements, which can be used as an independent modeling tool. How to create a diagram modeling tool based on the MOF metamodel and user requirements. Analyzing modeling tool information for generating a diagram modeling tool based on the input information and metamodel information reflected in the modeling tool information when information necessary for generating a modeling tool is input and selected by a user; Generating code of a diagram modeling tool based on the analyzed modeling tool information and metamodel information; Generating model management API code for managing a model created by a diagram modeling tool based on the analyzed metamodel information; Generating a model management wrapper API that serves as an intermediate between the code of the modeling tool and the model management API code; Generating a plug-in for the generated diagram modeling tool and model management API code; Storing the plug-in of the generated modeling tool in a repository; How to create a diagram modeling tool based on the MOF metamodel and user requirements.

Images