The IRMA Community
Newsletters
Research IRM
Click a keyword to search titles using our InfoSci-OnDemand powered search:
|
Data Reengineering of Legacy Systems
Abstract
Legacy systems, from a data-centric view, could be defined as old, business-critical, and standalone systems that have been built around legacy databases, such as IMS or CODASYL, or legacy database management systems, such as ISAM (Brodie & Stonebraker, 1995). Because of the huge scope of legacy systems in the business world (it is estimated that there are 100 billion lines of COBOL code alone for legacy business systems; Bianchi, 2000), data reengineering, along with its related step of program reengineering, of legacy systems and their data constitute a significant part of the software reengineering market. Data reengineering of legacy systems focuses on two parts. The first step involves recognizing the data structures and semantics followed by the second step where the data are converted to the new or converted system. Usually, the second step involves substantial changes not only to the data structures but to the data values of the legacy data themselves (Aebi & Largo, 1994).
Related Content
|
Margee Hume, Paul Johnston.
© 2017.
19 pages.
|
|
Jessy Nair, D. Bhanu Sree Reddy.
© 2017.
27 pages.
|
|
Joseph R. Muscatello, Diane H. Parente, Matthew Swinarski.
© 2017.
19 pages.
|
|
Klaus Wölfel.
© 2017.
33 pages.
|
|
Rui Pedro Marques.
© 2017.
21 pages.
|
|
Ebru E. Saygili, Arikan Tarik Saygili.
© 2017.
17 pages.
|
|
Aparna Raman, D. P. Goyal.
© 2017.
41 pages.
|
|
|