Value-Based Migration of Legacy Data Structures

2014 ◽  
pp. 115-134 ◽  
Author(s):  
Matthias Book ◽  
Simon Grapenthin ◽  
Volker Gruhn
Keyword(s):  
Data Structures ◽  
Legacy Data

Migrating legacy data structures based on variable overlay to Java

2009 ◽  
pp. n/a-n/a ◽  
Author(s):  
Mariano Ceccato ◽  
Thomas Roy Dean ◽  
Paolo Tonella ◽  
Davide Marchignoli
Keyword(s):  
Data Structures ◽  
Legacy Data

Data Reengineering of Legacy Systems

2009 ◽  
pp. 37-44
Author(s):  
Richard C. Millham
Keyword(s):  
Data Structures ◽  
Database Management ◽  
Significant Part ◽  
Management Systems ◽  
Second Step ◽  
Legacy Systems ◽  
Business Systems ◽  
Business World ◽  
Software Reengineering ◽  
Legacy Data

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).

Data Reengineering of Legacy Systems

2011 ◽  
pp. 181-188
Author(s):  
Richard C. Millham
Keyword(s):  
Data Structures ◽  
Database Management ◽  
Significant Part ◽  
Management Systems ◽  
Second Step ◽  
Legacy Systems ◽  
Business Systems ◽  
Business World ◽  
Software Reengineering ◽  
Legacy Data

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).

Specification scheme for the visualisation of data structures

1994 ◽  
Vol 9 (3) ◽  
pp. 127
Author(s):  
X.-B. Lu ◽  
F. Stetter
Keyword(s):  
Data Structures

The Social Furniture of Virtual Worlds

Disputatio ◽  
2019 ◽  
Vol 11 (55) ◽  
pp. 345-369
Author(s):  
Peter Ludlow
Keyword(s):  
Large Class ◽  
Data Structures ◽  
Virtual Worlds ◽  
Causal Powers ◽  
Virtual Objects ◽  
David Chalmers ◽  
The Social

AbstractDavid Chalmers argues that virtual objects exist in the form of data structures that have causal powers. I argue that there is a large class of virtual objects that are social objects and that do not depend upon data structures for their existence. I also argue that data structures are themselves fundamentally social objects. Thus, virtual objects are fundamentally social objects.

Sign in / Sign up

Export Citation Format

Share Document