In EDS ansehen

Re-implementing a legacy system.

Gespeichert in:
Bibliographische Detailangaben
Titel: Re-implementing a legacy system.
Autoren: Sneed, Harry1 harry.sneed@t-online.de, Verhoef, Chris2 x@cs.vu.nl
Quelle: Journal of Systems & Software. Sep2019, Vol. 155, p162-184. 23p.
Schlagwörter: *LEGACY systems, *COMPUTER software, *COMPUTER programming, JAVA programming language, COBOL (Computer program language)
Abstract: • Re-implementation as an alternative to redevelopment and conversion. • Reverse-Engineering as a prerequisite to re-implementation. • 10 Steps of the legacy system re-implementation process. • Re-implementing a state payroll system on an IBM mainframe. • Re-implementing a car leasing system in COBOL/IMS with Java/DB2. Re-implementation is one of the alternatives to migrate a legacy software system next to conversion, wrapping and redevelopment. It is a compromise solution between automated conversion and complete redevelopment. The technical architecture can be revised and the code replaced, but the functional architecture – the use cases remains as it was. The challenge of this approach is to preserve the functionality while changing the technical implementation. This approach is taken when conversion is not feasible and redevelopment is too expensive or too great a risk. It entails more than a 1:1 transformation but less than a total rewrite. The same components remain with different contents. In this paper the case for reimplementation is presented and the process described. The tools required to support the process are identified and their use illustrated. Finally, two industrial case studies are presented, one with a VisualAge/ PL/I-DB2 system and one with a COBOL-IMS application. [ABSTRACT FROM AUTHOR]
Copyright of Journal of Systems & Software is the property of Elsevier B.V. and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)
Datenbank: Business Source Index
Beschreibung
Abstract:• Re-implementation as an alternative to redevelopment and conversion. • Reverse-Engineering as a prerequisite to re-implementation. • 10 Steps of the legacy system re-implementation process. • Re-implementing a state payroll system on an IBM mainframe. • Re-implementing a car leasing system in COBOL/IMS with Java/DB2. Re-implementation is one of the alternatives to migrate a legacy software system next to conversion, wrapping and redevelopment. It is a compromise solution between automated conversion and complete redevelopment. The technical architecture can be revised and the code replaced, but the functional architecture – the use cases remains as it was. The challenge of this approach is to preserve the functionality while changing the technical implementation. This approach is taken when conversion is not feasible and redevelopment is too expensive or too great a risk. It entails more than a 1:1 transformation but less than a total rewrite. The same components remain with different contents. In this paper the case for reimplementation is presented and the process described. The tools required to support the process are identified and their use illustrated. Finally, two industrial case studies are presented, one with a VisualAge/ PL/I-DB2 system and one with a COBOL-IMS application. [ABSTRACT FROM AUTHOR]
ISSN:01641212
DOI:10.1016/j.jss.2019.05.012