KR100309670B1 - System for converting schema of case model information - Google Patents

Abstract

PURPOSE: A system for converting a schema of CASE(computer Aided software Engineering) model information is provided to store the CASE model in a relational database after converting the CASE model into a relational database schema by using a mapping rule between a model of tool having different paradigm and a relational database schema. CONSTITUTION: The method comprises the steps of reconfiguring each CASE model into an integrated meta-model based on the class and relationship between classes after converting each CASE tool into an object model consisting of object and relationship, converting the class of each model into a schema according to the conversion rule by obtaining the class table generating information from the meta-model information(65) in case that the meta-model information is about the object(64) and generating a class table for CASE model information(68), and converting the table generating information into a schema according to the relationship conversion rule by obtaining the table generating information from the meta-model information(71) in case of a meta-relation(70) and generating a relationship table for CASE model information(72).

Description

CS Model Information Schema Transformation System

The present invention relates to a relational schema conversion system of computer-aided software engineering (CASE) tool model information. For this purpose, the model information used in the CASE tool is converted into a database schema having a relational paradigm to increase the operability and interoperability of the model information system.

The data used in the CASE tool is a model. A CASE tool is a computer that supports the entire process of software development, analysis, design, and implementation. The user can make software development more convenient by using the model used for analysis and the model used for design. Information about the model is called metadata. That is, metadata is data for describing and defining data as data about data. Information repositories have the ability to store and manage this metadata.

Therefore, the information store stores the information about the model in the physical information store and supports the CASE tool to retrieve the desired information while having the information about the model.

The object-oriented reengineering software development support tool (RESORT) analyzes the source code of the previously developed system (Legacy System) and displays it as design information, and reconstructs the design information into objects supporting the object-oriented paradigm to construct a new system. It is an object-oriented reengineering software to create, and the information repository (RESORT / D) is to reconstruct and store the design information of different paradigms such as the design information of the existing system and the reorganized object-oriented design information into an integrated model, and the tool desired It serves to process and provide form.

However, CASE tools use different models depending on the methodology and notation they support. In addition, since the paradigm of CASE model information and database is different, information repository should convert information about CASE models into schema suitable for database paradigm. In order to map models and database schemas with different paradigms, there is a problem that requires a lot of effort and time, such as understanding different paradigms and understanding model information.

As described above, the CASE tools supporting the software development process have different methodologies and paradigms supporting the methodologies, and provide different models according to the methodologies. Information repositories create an Integrated Meta Model from these models and store it in a database. To be stored in the database, the model and metamodels provided by the CASE tools must be converted into a schema that matches the structure of the database. In this regard, a CASE model information schema transformation system for meta-model relational database schema transformation with different paradigms is required.

In addition, in order to effectively operate the CASE model information schema transformation system, various elements must be provided. First, CASE model information should be converted into a form that can be mapped into a schema suitable for a database having a relational paradigm. To this end, a schema converter for CASE model information is required. You also need a rule for schema mapping for this converter. In order to satisfy this problem, the CASE model information schema transformation system requires a CASE model information schema converter using rules for schema mapping.

Accordingly, the present invention converts a CASE model into a relational database schema by using rules for mapping between a model of a tool having a different paradigm and a relational database schema to improve the problems of the conventional CASE information repository as described above. Its purpose is to provide a CASE model information schema transformation system that can be stored in a relational database.

1 is an overall configuration diagram of an information repository (RESORT / D) including a CASE model information schema transformation system according to the present invention.

2 is a block diagram of CASE model information that is schema transformed in an information repository to which the present invention is applied.

3 is a block diagram illustrating schema conversion of CASE model information according to a class conversion rule and a relationship conversion rule proposed in the present invention.

4 is a flowchart illustrating a relational database schema transformation of CASE model information according to the present invention.

<Description of the symbols for the main parts of the drawings>

10: tool interface 11: information store interface

12: reverse engineering tool interface 13: object restructuring tool interface

14: domain modeling tool interface 20: CASE model information management system

30: information storage management system 40: database management system

50: Database 100: CASE model information schema conversion system

110, 120: CASE tool model 130: Integrated metamodel

140: model information schema conversion rule 150: relational database table

200: CASE tool 300: model information

310: structure chart 320: reference graph

330: call graph 340: control flow graph

350: UML object model 351: domain model

352 refinement model 353 initial object model

400: model information management 411: model information schema converter

412: Model information extractor 420: Diagram

430: object 440: relationship

The relational schema conversion system of CASE tool model information according to the present invention for achieving the above object is to convert the model information provided from each CASE (Computer Aided Software Engineering) tool having a different paradigm into a schema suitable for the database paradigm of the information repository. In the relational schema transformation system of CASE tool model information to be transformed, each CASE model is converted from each CASE tool into an object model consisting of objects and relationships, and then reconstructed into a unified metamodel based on the class and the relationship between the classes. Perform the steps, and read the metamodel information to obtain table generation information from the metamodel information, convert the class of each model into a schema by class conversion rules, and Creating the class tables In the case of MetaRelation by reading the metamodel information, the table generation information is obtained from the metamodel information, converted into a schema according to a relationship conversion rule of each model, and the relation table for the CASE model information. By performing the step of generating them characterized in that the tool model information having a different paradigm is converted into a schema suitable for the paradigm of the database and stored.

1 shows an overall configuration diagram of an information repository (RESORT / D) including a CASE model information schema transformation system according to the present invention.

As shown, the information store (RESORT / D) is a tool interface 10 for receiving data from various CASE tools (not shown) or outputting data to the CASE tool, and information about the model itself. A CASE model information management system 20 which manages, an information repository management system 30 which obtains information of a model required by a tool from the CASE model information management system 20 and maps the CASE model information to a relational database schema; The database management system 40 processes data by accessing a physical disk from the database 50 through a query word.

The tool interface 10 includes an information storage interface 11 and a reverse engineering tool interface 12 connected to a reverse engineering CASE tool, an object restructuring tool interface 13 connected to an object restructuring CASE tool, and an area modeling CASE tool. It consists of an area modeling tool interface 14 connected to it.

The reverse engineering tool interface 12, the object restructuring tool interface 13, and the region modeling tool interface 14 may be used as inputs to the CASE model information schema transformation system 100. Each model is transformed into an object model consisting of objects and relationships.

The CASE model information schema conversion system 100 proposed in the present invention operates in the information storage management system 30.

2 shows the relationship between the CASE model information and the CASE model information schema transformation system according to the present invention.

As shown in the figure, the model information, which is defined by a certain rule, for a certain tool and its modeling information, and management of an information repository for managing the model information is shown. The model information is information in which modeling information for each tool handled in an information store (RESORT / D) is defined by a predetermined rule. The CASE model information schema conversion system is a system for converting CASE model information into a relational database schema using modeling information and schema conversion rules obtained from such model information.

In general, the model information 300 includes a structure chart 310, a variable reference graph 320, and a call graph as shown as modeling information for each tool 100. Graph) 330, control flow graph 340 and UML object model 350, wherein the UML object model 350 is a domain model 351, a refining model 352 and the initial object model (Initial Model) (353).

The management of model information of the information repository 300 is performed by managing the diagram 420 of the model information, the object 430 and the relationship 440. In addition, the information store performs the operations of the model information schema converter 411 and the model information extractor 412, but the present invention intends to limit the model information schema transformation.

3 illustrates a conversion flow diagram of model information in the CASE model information schema transformation system 100. Each CASE tool has a different methodology and a paradigm that supports it, and provide different models according to the methodology.

As shown there is one model 110 provided by CASE tool A and another model 120 provided by CASE tool B. As such, different models (110, 120 ...) are provided depending on how each tool supports them. These models 110 and 120 are converted into object models formed in relation to objects through the interface 10 of FIG. 1. In the CASE model information schema conversion system 100, schema conversion is performed based on the information of these objects and relationships.

The information repository extracts the integrated metamodel (130) from these models (110, 120 ...) and stores it in the database.

To be stored in the database, the models and metamodels provided by the CASE tools must be converted into a schema that matches the structure of the database. The CASE model information schema transformation system 100 performs a relational database schema transformation of metamodels having a different paradigm.

In order to operate CASE model information schema conversion system effectively, various elements should be provided. First, CASE model information should be converted into a form that can be mapped into a schema suitable for a database having a relational paradigm. To this end, a schema converter for CASE model information is required. There is also a need for rules for schema mapping for this converter. In order to satisfy this problem, the CASE model information schema transformation system has developed a CASE model information schema converter 140 using schema transformation rules.

The CASE model information schema converter 140 according to the present invention is designed to have a schema conversion rule according to the present invention. The rule is a rule for mapping the metamodel to be converted into a schema that matches the storage structure of the database in which the metamodel is actually stored.

Since the present invention maps CASE model information having a different paradigm into a relational database schema, it refers to the definition of a class, which is the data constituting the metamodel, and the relational database transformation rules for the relationship between classes and classes.

The model shown in FIG. 3 is based on a UML (Unified Modeling Language) notation among object-oriented models. Among the symbols used in the meta-model, the rectangular block 131 refers to a class, and the line 132 represents a relationship. The rhombus block 133 is meant to be included in the relationship, and the inverted triangle block 134 represents inheritance.

That is, the meta model 130 of the CASE model information is composed of a class 131 and a relationship 132. The meta model is converted into a database schema according to the following process.

First, create a table for each model extracted from the metamodel. These tables have attributes as model names and metamodel names, and there is no relation between each model.

Second, the conversion rule for a class is that each class defined in the metamodel is stored as a tuple in the class table, and the attributes of this table are the representative key and the class. It has an annotation and an attribute and operations.

Third, the conversion rule for relation is that each relation is created as one table according to the relation of aggregation, inheritance, and association. It is stored as a tuple of a relation table according to the form of. Attributes of these tables include the representative key, the source class ID and destination class ID from which the relationship begins, the start point X (Start_X), the start point Y (Start_Y), and the end point X of the location information of the relationship. (End_X), end point Y (End_Y), and annotations.

As described above, the conversion rule for the class and the conversion rule for the relationship are summarized as follows.

In other words, converting a class to a relational database schema creates one table with a class table name. Attributes that the table has include a primary key, a class name, and a class. Class attribute 1, class attribute 2, ..., class attribute n (n is the number of attributes of the class with the most attributes of the class in the metamodel), class operation Class operation 1, class operation 2, ..., class operation n (n is the number of operations of the class with the most operations of the class that the metamodel has) and annotation.

In addition, when a relationship is converted to a relational database schema, tables are created for each type of relationship as shown below. Attributes of the table include a primary key, It has a relation name, a source class ID, a destination class ID, a start point X (Start_X), a start point Y (Start_Y), an end point X (End_X), an end point Y (End_Y), and an annotation.

As described above, when a class is converted to a relational database schema, the classes can be defined as shown in the following table.

When a relationship is converted to a relational database schema, the relationship can be defined as shown in the following table.

The CASE model information schema converter 140 converts the model information of the metamodel 130 to have the schema conversion rule as described above, so that the metamodel matches the storage structure of the database where the metamodel is substantially stored. It is mapped to a schema that is composed of a relational database table 150.

The data stored in the database according to the tools are stored in the relational database table 150 so that the CASE model information having different paradigms, that is, the model 110 of the CASE tool A and the CASE tool as shown in FIG. The data stored in each database of the model 120 of B can be mutually utilized.

Since the present invention maps CASE model information having a different paradigm into a relational database schema, it refers to the definition of a class, which is the data constituting the metamodel, and the relational database transformation rules for the relationship between classes and classes.

FIG. 4 is a flowchart illustrating a relational database schema conversion of CASE model information based on the schema conversion rule according to the present invention. In the case of a meta-object during conversion, the CASE model information is read and a table generation rule for each model ( In the case of information about an object by referring to a model extracted from a metamodel, the attributes and operations of the object are found, and the primary key as an attribute by the class conversion rule. ), Create a class table for the CASE model information by adding a class name and an annotation. In the case of MetaRelation, relation tables are generated by the relation conversion rule by referring to the table generation rule provided by the CASE model information.

That is, as shown, the model information is read (61) to determine whether it is new model information. (62) If it is not new model information, if there is an existing DB, there is an existing DB without creating a new DB. In this case, a message informing of the error is output (64), and if not, a new DB is created (63). When model information read with reference to a table generation rule (model extracted as a class in a metamodel) for each model is determined as information on an object (64), table generation information is obtained from the model information (65). Find the attributes and operations of the object from the model information (66), add the representative key, class name and remarks as attributes according to the class conversion rule (67), convert them to the database schema with the above information, and add them to the CASE model information. Create class tables for (68).

On the other hand, if the read model information is a meta-relation (70), the table generation information is obtained from the model information (71), and by referring to the obtained table generation rule is converted into a database schema by the relationship conversion rule and generates relation tables. (72).

If the read model information is neither an object nor a relationship, an error message is output (73).

Since the CASE model information data having the different paradigm are stored in the tables generated in this way, it is possible to overcome the fact that the databases for the models supported by the respective CASE tools cannot be used in the conventional case and to utilize each other's databases.

According to the present invention, all the models to be supported by the CASE tool can be converted into a relational database schema, and through the idea of the CASE model information and the relational database schema having different paradigms, the information storage management system is managed by the database management system. It can improve the consistency of model information management system and interoperability of model information, and can automatically convert model information provided by CASE tool to relational database schema.

Therefore, efficiency and productivity can be improved by avoiding duplication of database schema for CASE model information, reducing effort and cost for schema generation, and reducing schema change management cost according to model information change.

Claims (3)

CASE tool that converts model information provided from each computer-assisted software engineering (CASE) tool having a different paradigm into a schema suitable for the database paradigm of the information store. In the relational schema conversion system of model information, an object is generated from each CASE tool. Reconstructing each of the provided CASE models into a unified metamodel based on a class and a relationship between the classes, after being converted into an object model having a relation with and; Read the metamodel information to obtain the table generation information from the metamodel information to convert the class of each model into a schema according to the class conversion rules, and generates class tables for the CASE model information Steps; In the case of MetaRelation, the meta model information is read and the table generation information is obtained from the meta model information. The meta model information is converted into a schema according to the relationship conversion rule of each model, and the relation tables for the CASE model information are generated. By performing the steps; A relational schema conversion system of CASE tool model information, characterized by converting and storing tool model information having a different paradigm into a schema suitable for a database paradigm. The method of claim 1, wherein the generating of the class tables comprises, for each model extracted from the metamodel, a name of each tool model and a name of the metamodel as attributes, and a relationship between each model. create a table without relations; Each class defined in the metamodel is stored as a tuple in the class table, and the attributes of this table include the representative key, attributes and operations of the class, and remarks. Schema Conversion System. The relationship transformation rule of claim 1, wherein the relationship conversion rule of the relationship table generation step causes each relationship to be generated in one table according to the relationship of aggregation, inheritance, and association. According to each type, these are stored as a table of relations, and the attributes of these tables are the representative key, the source class ID and destination class ID from which the relationship begins, the starting point of the relationship, the starting point X starting point Y ending point X ending point A CASE model information schema transformation system characterized by having _Y and Annotation.

Images