1 / 13

Wrapper-Based Evolution of Legacy Information Systems: Strategies for Migration and Integration

This paper explores the wrapper-based evolution of legacy information systems, focusing on their role in data migration and integration. It delves into various strategies for implementing wrappers that facilitate the transition from traditional data-intensive applications to modern architectures. Key components include techniques for ensuring data integrity, consistency, and validation logic while interfacing legacy components with new database systems. The study emphasizes the importance of wrapper architecture, transparency, and effective mapping definitions in streamlining information systems evolution.

july
Télécharger la présentation

Wrapper-Based Evolution of Legacy Information Systems: Strategies for Migration and Integration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Wrapper-based evolution of legacy information systems Philippe Thiran Jean-Luc Hainaut Djamal Benslimane By:- Kiran Yayavaram

  2. Introduction • Legacy data-Intensive Applications • Data management Systems • Wrappers • Data Integrity • Data Consistency

  3. Wrapper Based Strategies for Information Systems Evolution & Migration • Role of Wrappers in Systems Evolution & Migration • Translate Data & Queries from the legacy data model and interface to those expected by the new component. • Take Charge of Validation logic that ensures data integrity. • Database is migrated first. New Components are developed on this new database, while the legacy components are interfaced through wrappers

  4. Types of Wrappers • Forward Wrappers • Validation logic that ensures data Integrity. These emulate the new technology based on the legacy one. • Backward Wrappers • Model Conversion is the only responsibility. These emulate the legacy technology on top of the new one

  5. Approaches for wrapper Implementation • Wrapper Transparency • Update Facilities

  6. Wrappers…. • Building Wrappers • Wrapper Schema Definition • Mapping Definition

  7. Wrapper Architecture • Wrapper Architecture

  8. …[Wrapper Architecture] • Wrapper Query/Update Analysis • Error Reporting • Query/Update and Data Translation

  9. Abstract specification of a Wrapper • Model and Schema Specification • Transformational Mapping Specification • Implicit Constraints and Schema Interpretation

  10. Wrapper Development • Generic Methodology • Database Reverse Engineering for Schema Definition [DBRE] • Wrapper Generation • Tool Support

  11. Metrics of wrapper development cost Factors • Underlying DBMS to which the wrapper is dedicated • Size of the database and wrapper schemas • Number and the type of schema transformation of the sequence

  12. Conclusion Wrappers….. • Proves to be the core technology that allows a smooth transition to modern architectures. • Easier integration of a legacy database into current large applications • They relieve modern client components from the responsibility of controlling data integrity • Error Recovery & Transaction management

  13. ??????...Questions...??????

More Related