Traditional Data Oriented versus Process Oriented Reengineering of Legacy Systems

Traditional Data Oriented versus Process Oriented Reengineering of Legacy Systems

Raul Valverde (Concordia University, Canada) and Malleswara Talla (Concordia University, Canada)
DOI: 10.4018/978-1-4666-0155-0.ch003
OnDemand PDF Download:
No Current Special Offers


The chapter presents data oriented and process oriented models of legacy systems. It discusses the details of systems development and evolution models mainly aiming at an ongoing reengineering of legacy systems. It proposes few strategies for reengineering of both data oriented model and process oriented models. The legacy systems often miss automatic interfaces to external systems, so the chapter presents a strategy focusing on automatic update of data of the system. Likewise, the chapter also presents a strategy for process reengineering in order to integrate external systems. Finally, a legacy system is envisioned as a comprehensive mix of both data and process oriented, while proposing a gradual ongoing reengineering of both data structures and process methods.
Chapter Preview

2. Traditional Data Models And Reengineering Techniques

The traditional methodologies include data models of organization’s data, a technique for organizing and documenting a system’s data (Whitten, J. L., Bentley D. L. and Dittman K.V., 2000). Data modeling is often called database modeling because a data model is often implemented as a database (Satzinger & Jackson & Burd 2002), which is depicted in an Entity Relationship Diagram (ERD) for presenting the data in terms of the entities and their relationships.

Figure 1.

Sample ERD diagram of a typical order processing system


An entity is a class of persons, places, objects, events, or concepts about which data is captured and stored.

Complete Chapter List

Search this Book: