Legacy system program transformation by Lyee methodology

  • Authors:
  • Yozo Takeda;Hamido Fujita

  • Affiliations:
  • Iwate Prefectural University, Iwate 020-0193, Japan;Iwate Prefectural University, Iwate 020-0193, Japan

  • Venue:
  • Knowledge-Based Systems
  • Year:
  • 2004

Quantified Score

Hi-index 0.00

Visualization

Abstract

Based on the comparative review of several approaches to legacy system conversion and revitalization, the Lyee methodology application for the issue is presented to clarify its idea, the associated procedure, and the implemented tools. It could be said that with the tools and manual developed by ICBSM&T, the mechanical transformation of the conventional program to a Lyee-structured one becomes possible as long as the programs are made in a procedure-oriented language. In addition to the program structure conversion, the Lyee methodology permits people to choose any application language in the transformed program. At the same time, quite a new approach related to the system conversion is introduced, in which the chunk of data extracted from an old program is edited to make a new conventional structure program that has a logical sequence instead of a Lyee type of declarative program. These features can be realized through the concept of LyeeBELT, which is a set of word-information about the attributes, formulae, and conditions for an independent data item. The overall workflow of the legacy program transformation is shown in the following. A critical part in its implementation is the feasibility study (pre-analysis) stage where necessary information is supposed to be secured, and an appropriate plan and policy about the system to be revitalized in the new system environment should be clarified so as to customize the tools accordingly. If the initial process is completed, the mechanical legacy system conversion will be realized by registering the parameters in the tool, and the reestablishment of business knowledge in the LyeeBELT will be enabled. With the regulated business logic on the LyeeBELT, the program maintenance afterwards becomes drastically simplified and stable without the 'spaghetti' problem, so that software evolution can be possible.