ACM Home Page
Please provide us with feedback. Feedback
Wrapper-based evolution of legacy information systems
Full text PdfPdf (873 KB)
Source ACM Transactions on Software Engineering and Methodology (TOSEM) archive
Volume 15 ,  Issue 4  (October 2006) table of contents
Pages: 329 - 359  
Year of Publication: 2006
ISSN:1049-331X
Authors
Philippe Thiran  Facultés Universitaires Notre-Dame de la Paix, Namur, Belgium
Jean-Luc Hainaut  Facultés Universitaires Notre-Dame de la Paix, Namur, Belgium
Geert-Jan Houben  Vrije Universiteit Brussel, Brussels, Belgium
Djamal Benslimane  Université Claude Bernard, Lyon 1, Villeurbanne cedex, France
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 96,   Downloads (12 Months): 423,   Citation Count: 1
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1178625.1178626
What is a DOI?

ABSTRACT

System evolution most often implies the integration of legacy components, such as databases, with newly developed ones, leading to mixed architectures that suffer from severe heterogeneity problems. For instance, incorporating a new program in a legacy database application can create an integrity mismatch, since the database model and the program data view can be quite different (e.g. standard file model versus OO model). In addition, neither the legacy DBMS (too weak to address integrity issues correctly) nor the new program (that relies on data server responsibility) correctly cope with data integrity management. The component that can reconciliate these mismatched subsystems is the R/W wrapper, which allows any client program to read, but also to update the legacy data, while controlling the integrity constraints that are ignored by the legacy DBMS.This article describes a generic, technology-independent, R/W wrapper architecture, a methodology for specifying them in a disciplined way, and a CASE tool for generating most of the corresponding code.The key concept is that of implicit construct, which is a structure or a constraint that has not been declared in the database, but which is controlled by the legacy application code. The implicit constructs are elicited through reverse engineering techniques, and then translated into validation code in the wrapper. For instance, a wrapper can be generated for a collection of COBOL files in order to allow external programs to access them through a relational, object-oriented or XML interface, while offering referential integrity control. The methodology is based on a transformational approach that provides a formal way to build the wrapper schema and to specify inter-schema mappings.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Aiken, P., 1996. Data Reverse Engineering. McGraw-Hill.
 
2
Balzer, R. 1981. Transformational implementation : An example. IEEE TSE 7, 1, 3--14.
 
3
 
4
 
5
 
6
Brodie, M. and Stonebraker, M. 1995. Migrating Legacy Systems, Morgan Kaufmann.
 
7
Carey, M. J., Florescu, D., Zachary, G. I., and Ying, L. 2000. XPERANTO: Publishing Object-Relational Data as XML. In Proceedings of WebDB (Informal Proceedings), 105--110.
 
8
 
9
 
10
 
11
 
12
13
 
14
 
15
 
16
Hainaut, J.-L. 2002. Introduction to Database Reverse Engineering. LIBD Lecture Notes, University of Namur. http://www.info.fundp.ac.be/~dbm/publication/2002/DBRE-2002.pdf; October 2005.
 
17
Hainaut, J.-L. 2005. Transformation-Based Database Engineering. In Transformation of Knowledge, Information and Data: Theory and Applications. P. van Bommel, Ed. IDEA Group, 1--28.
 
18
 
19
 
20
Hick, J.-M., Englebert, V., Henrard, J., Roland, D., and Hainaut, J.-L. 2004. The DB-MAIN Database Engineering CASE Tool (version 7.1)---Functions Overview, DB-MAIN Technical Manual, Institut d'Informatique, University of Namur. http://www.rever-sa.com/DISTRIBUTION/VERSION.7/DB-MAIN-Reference-Manual.pdf; October 2005
 
21
Lawrence, R., Barker, K., and Adil, A. 1998. Simulating MDBS Transaction Management Protocols. In Proceedings of the CAINE Conference.
 
22
 
23
Lim, E. P. and Lee, H. K. 1999. Export Database Derivation in Object-Oriented Wrappers. Inform. Softw. Tech. 41, Elsevier, 183--196.
 
24
 
25
 
26
 
27
 
28
 
29
 
30
 
31
Ritsch, H. and Sneed, H. 1993. Reverse Engineering Programs via Dynamic Analysis. In Proceedings of the 1st IEEE Working Conf. on Reverse Engineering. Baltimore, IEEE Computer Society Press, 192--201.
 
32
 
33
 
34
 
35
 
36
 
37
 
38
 
39
 
40
Thiran, Ph., Estievenart, F., Hainaut, J.-L. and Houben, G. J. 2005b. A Generic Framework for Extracting XML Data from Legacy Databases. Journal of Web Engineering, 4, 3, Rinton Press, 205--223.
 
41
Weiser, M. 1984. Program Slicing, IEEE TSE 10, 352--357.
 
42
Wu, B., Lawless, D., Bisbal, J., Grimson, J., Wad, V., O'sullivan, D., and Richardson, R. 1997. Legacy System Migration: A Legacy Data Migration Engine, In Proceedings of the 17th International Database Conference (DATASEM '97), Ed. Czechoslovak Computer Experts, 129--138.
 
43


Collaborative Colleagues:
Philippe Thiran: colleagues
Jean-Luc Hainaut: colleagues
Geert-Jan Houben: colleagues
Djamal Benslimane: colleagues