Thesis (M.Sc.) -- University of Toronto, 2002.
|Series||Canadian theses = -- Th`eses canadiennes|
|The Physical Object|
|Pagination||3 microfiches : negative.|
The book does a good job of describing the different technologies the project used as well as others available for modernization efforts -- Java/J2EE, Web Services, wrapper code, and different packaged systems -- providing an overview of each technology as well as customized ways to write integrations from the legacy systems to modern by: In real industrial application scenery, a data reengineering based on common business-oriented language (COBOL) is designed for supporting the access the data from the relational database of. Because of the huge scope of legacy systems in the business world (it is estimated that there are billion lines of COBOL code alone for legacy business systems; Bianchi, ), data reengineering, along with its related step of program reengineering, of legacy systems and their data constitute a significant part of the software Author: Richard C. Millham. The legacy system in this case study consists of nearly 2 million lines of COBOL code developed over 30 years. The system is being replaced with a modern system based on the Java 2 Enterprise.
25,, articles and books. Periodicals Literature. Procedural code in legacy Cobol compilation units is typically composed of a collection of parameterless subroutines . the modularization tool as part of its broader investigation into the role that advanced technologies can play in reengineering Cobol legacy systems into. M.G.J. van den Brand, P. Klint, C. VerhoefRe-engineering needs generic programming language technology ACM SIGPLAN Notices, 32 (2) (), pp. Google Scholar. Software evolution is an inevitable process for software systems. Repeated changes alter the structure of a system, rapidly degrading it and making the system “legacy”. Reengineering seems to be a promising approach to upgrade these systems according to the latest technologies. Based on actual code of about COBOL programs, a mixture of OS/VS COBOL and COBOL programs, the SDF definition discussed in the previous section is adapted and reduced to a restricted grammar. The reason that we want a restricted grammar is to improve the performance of the parser generator, the generated parserm and the tools that use.
This book features an extensive case study involving a major modernization effort. The legacy system in this case study consists of nearly 2 million lines of COBOL code developed over 30 years. The system is being replaced with a modern system based on the Java 2 Enterprise Edition (J2EE) architecture. This research focuses on how to reengineer Cobol legacy systems into object oriented systems using Sward's Parameter Based Object Identification (PBOI) methodology. The method is based on relating categories of imperative subprograms to classes written in object oriented language based on how parameters are handled and shared among them. The reverse engineering project described in this paper is aimed at documenting a million lines of code COBOL/IMS/DB2 system for world-wide car leasing. The ultimate goal is to re-implement that system. The system was originally developed in the s with less than 3 million code lines and has since evolved to its current size. Legacy code. Originally, this describes an application ‘inherited’ from a previous generation of programmers, developed in a language of an earlier generation and running on a platform (hardware, OS, ) also old or unsupported. This did reference primarily to Mainframe Cobol code.