J-L. Hainaut, C. Tonneau, M. Joris, and M. Chandelon. Transformation-based Database Reverse Engineering. In Proceedings of the 12th International Conference on the EntityRelationship Approach, Lecture Notes in Computer Science, Dallas, Texas, December 1993. Springer-Verlag.  Home/Search   Document Details and Download   Summary   Related Articles   Check

.... data model that subsumes conceptual constructs as well as logical (and physical) constructs [18,15] Based on this common data model, Hainaut et al. have defined a catalog of schema transformations which are used to gradually replace low level implementation constructs by more abstract concepts [19]. However, the execution of in place transformations (suggested by Hainaut) impede iterative DBRE processes because the original (logical) schema implementation is lost during the migration process. Jeusfeld and Johnen propose an approach to schema migration that employs a generic meta model as ....

J.-L. Hainaut, C. Tonneau, M. Joris, and M. Chandelon. Transformation-based database reverse engineering. Lecture Notes in Computer Science, 823:364, 1994.

....of the transformations in 4 and 5 also receives a lot of attention in the database and information systems research community. This reversed process is referred to as reverse engineering. For this fairly new area also a wide range of strategies and algorithms exists ( Kal91, FG92, SS93, HCTJ93, HTJC93b, HTJC93a, CBS94] These algorithms all operate on the base of a set of possible schema transformations and heuristics to best apply them. The above discussed five classes either operate on a conceptual data schema or an internal schema of a given implementation platform. The modelling process up ....

J-L. Hainaut, C. Tonneau, M. Joris, and M. Chandelon. Transformation-based Database Reverse Engineering. In Proceedings of the 12th International Conference on the EntityRelationship Approach, Lecture Notes in Computer Science, Dallas, Texas, December 1993. Springer-Verlag.

....based on embedded foreign keys. Its description is outside the scope of this paper and is not herein included. 4 Future Work Having in mind a more complete classification of DBRE methods, the one herein presented should be extended in its two dimensions. First, to include more methods like [Hainaut93] supported by the DBMAIN CASE environment [Henrard98a] or MeRCI [C Wattiau96] And the second one, to include more characteristics relevant for the classification, such as the impact of incompleteness of information or the quality of the conceptual schemas produced. We envisage an ideal DBRE ....

J-L Hainaut, C. Tonneau, M Joris, M. Chandelon, "Transformation Based Database Reverse Engineering", in Proc. of the 12 th International Conference on EntityRelationship Approach, R. Elmasri and V. Kouramajian (Eds.), Arlington, Texas, USA, pp 353-372, Dec 1993.

....with the mapping of a conceptual model into a logical one. The design of a federated database implements the reverse operation because the databases to integrate already exist. There are various another reasons for applying reverse engineering to existing relational databases, they are outlined in [10]. The Extended Entity Relationship (EER) models for defining canonical data model in a federated environment are not easily exploitable because the EER schema is not carried out automaticaly in views in a target model. Nevertheless for using an EER model for canonical model, 13] proposes ....

Hainaut J.L., Tonneau C., Joris M., Chandelon M., "Transformation-based Database Reverse Engineering", Proceedings of the 12th Int. Conference on Entity-Relationship Approach, Springer Verlag, Vol 823, pp 364-375, 1994.

....which contain detailed information about the application domain. The relational schema is extensively classified into different kinds of relations, attributes, and inclusion dependencies. Based on this information, the entity and relationship types can be identified. Hainaut et al. HCTJ93, HTJC93, HEH 95] present an extensive methodology for database reverse engineering. Few approaches regard also queries in the relational schema to extract additional semantic of the relational schema [VA95a, JSZ97] Reverse engineering in [PTBK96] starts with analyzing the equi join queries embedded in ....

J. Hainaut, C. Tonneau, M. Joris, and M. Chandelon. Transformation-based database reverse engineering. Technical report, Institut d'Informatique, University of Namur, 1993.

.... of various types, inclusion dependencies, and others) relational schemas are supposed to be in third normal form ; the key attributes are consistent named ; the relations are given without instances ; Moreover up to now methods do not clearly show how to extract n ary relationships (n 2) [7] proposes generic transformation operations that could be used on n ary relationships in practical design activities including database reverse engineering. 5] maps relations with two or more primary key fields to N:N relationships. We believe this statement is ambiguous because a relation having ....

J.L. Hainaut, C. Tonneau, M. Joris, M. Chandelon, "Transformation-based Database Reverse Engineering", Proceedings of the 12th Int. Conference on Entity-Relationship Approach, Springer Verlag, Vol 823, 364-375, 1993.

....application programs. Algorithms for converting a relational schema into the original Entity Relationship (ER) model [4] can be found in [7] 15] proposes a more powerful approach that considers inheritance and provide a very detailed classification of relations and attributes. Other approaches [1,10,11,12] provide to define an Extended ER diagram from a relational schema. Other approaches for reverse engineering of relational database consider binary relationship [18] or object oriented as target semantic data models [3,9,14,17,27] Some tools exist [6,8,17,18] Recent relational database reverse ....

....[13] The fundamental differences of these two approaches is the interpretation of cardinality constraints particularly for n ary relationships. The approach of Chen and its extensions [5,17,22,26] consider cardinality constraints based on the identifiers of relationships. The second approach [10,15,24] consider cardinality constraints which are based on participation constraints between entities and relationships. This approach is used by the majority of commercial tools and methodologies [2,25] These two different approaches are neither complementary nor opposite [23] We can note that the ....

Hainaut, J.L., Tonneau, C., Joris, M., Chandelon, M. Transformation-based Database Reverse Engineering, in Proceedings of the 12th Int. Conference on Entity-Relationship Approach, Springer Verlag, 823, (1993) 364-375.

....dependencies which must be identified by the user. Fonkam and Gray [13] have analyzed three previous methods ( 7] 11] and [12] and tried to overcome their limitations. In their work candidate keys play a major role. A general framework to database reverse engineering is introduced by Hainaut [14]. This framework cannot only be used for relational database schemas but for all different logical models as it is based on schema independent transformations. The problem with all the approaches above is that they concentrate on recovering the database structure only. In this paper we go one step ....

Hainout J.-L., Tonneau C., Joris M., Chandelon M. Transformation-based database reverse engineering. Proc. of the Intern. Converence on ER-Approach 1993.

....database structure (Fahrner and Vossen 1995a) The conceptual design representation can be any of the semantic data models like ER, EER, object oriented, and so on. On the other hand, the existing database structure can be represented in the relational model, hierarchical model, and so on. Hainaut et al. 1993) propose a two step process for database reverse engineering. The first step is data structure extraction. During this step, the existing database structure is analyzed (e.g. schema, database contents, queries) to produce a complete description of the existing source schema. During the second ....

Hainaut, J., C. Tonneau, M. Joris, and M. Chandelon. 1993. Transformationbased database reverse engineering. In Proceedings of the 12th international conference on entity relationship approach held in Texas, USA, December, 1993, edited by R. Elmasri, V. Kouramajian, and B. Thalheim, 364--75, Springer.

No context found.

J-L. Hainaut, C. Tonneau, M. Joris, and M. Chandelon. Transformation-based Database Reverse Engineering. In Proceedings of the 12th International Conference on the EntityRelationship Approach, Lecture Notes in Computer Science, Dallas, Texas, December 1993. Springer-Verlag.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC