Academia.eduAcademia.edu

Outline

Title
Abstract
Key Takeaways
Planning Overview
Portfolio Analysis
Reengineering Definitions and Objectives
Cost-Benefit Analysis
References
All Topics
Computer Science
Software Engineering

Planning the reengineering of legacy systems

Profile image of Harry SneedHarry Sneed

1995, IEEE Software

https://doi.org/10.1109/52.363168
visibility

…

description

11 pages

link

1 file

Abstract

Planning the Reengineering of Legacy n Systems HARRY M . SNEED , Software Engineering Services e How canyou know i f reengineering is cost-effective? If it is preferable to new development? OY to maintaining the status quo? The author proposes a way to quantzjj the costs and prove the benefits of Yeengineering over other alternatives and offers some advice on contracting a reengineering project.

Key takeaways
sparkles

AI

  1. Reengineering projects must demonstrate cost-effectiveness through detailed analysis of quality and productivity metrics.
  2. Implement a five-step planning process for reengineering: justification, portfolio analysis, cost estimation, cost-benefit analysis, and contracting.
  3. Maintenance metrics are crucial for justifying reengineering by assessing existing software quality and costs.
  4. Technical quality must precede functional reengineering to ensure functional equivalence is demonstrable post-project.
  5. Legacy systems should only be reengineered without functional adaptations, maintaining the same functionality throughout the process.

Related papers

Refactoring as a Technique for the Reengineering of Legacy Systems
Anders Hessellund

2004

View PDFchevron_right
Reengineering Framework to Enhance the Performance of Existing Software
Kanwalvir Singh, Kanwalvir Singh Dhindsa

International Journal of Advanced Computer Science and Applications

Term reengineering refers to improve the quality of the system. Continues maintenance and aging degrade the performance of the software system. Right approach and methodology must be adapted to perform reengineering. With lack of right approach and methodology, reengineering itself will be costly and time-consuming. For the process of reengineering main concerns include when to reengineer, how to estimate cost, the right approach for reengineering, and how to validate software enhancement. This research paper proposed a framework to identify the need for reengineering, to estimate the cost of reengineering, and to validate software quality improvement. Research work used the agile methodology to perform tasks of reengineering. Reengineering needs are identified using prediction based decision tree approach. Reengineering is applied using the agile Scrum methodology. Cost estimation is done using story point estimation. Performance analyses are done using complexity measures analysis of the internal design metrics and mean time to execute metric. The research used various automated tools like CKJM ver1.9, Rapid Miner studio ver7.1, and Net beans7.3 framework.

View PDFchevron_right
Reengineering Legacy Systems Towards New Technologies
Djelloul Bouchiha

A book chapter in Encyclopedia of Information Science and Technology, Fifth Edition, edited by Mehdi Khosrow-Pour D.B.A., IGI Global, 2021, pp. 1214-1230., 2021

Software reengineering is an important area of the software engineering. The quest to maintain and understand operational legacy systems has always been a challenge for software practitioners. This chapter presents a compilation of notions and techniques covering major areas namely, reverse engineering, program understanding, software maintenance, migration and evolving. Our objective is not to create new terms, but to introduce the terms already in use with different perspectives.

View PDFchevron_right
A dual-spiral reengineering model for legacy system
Xinyu Wang

Computer Technology has been in existence for many years; as time goes on there is an increasing number of outdated systems. Legacy System Reengineering has become a critical effort in many technology organizations. Several reengineering models have been developed, such as the Byrne Model and the Evolutional Model. These models have addressed some of the issues in the reengineering process, but other issues remain. This paper presents a dual-spiral reengineering model, which performs as a cyclic approach, and addresses issues that those models do not, making the reengineering process more successful. This model has been successfully applied to a legacy financial software system reengineering effort.

View PDFchevron_right
Selection and Implementation of Technologies for the Re-Engineering of an Existing Software System
Stan Naspinski

2011

View PDFchevron_right
Investigation of Quality and Functional Risk Issues in Reengineering Process of Legacy Software System
Vrinda Tokekar

International Journal of Programming Languages and Applications, 2014

The modern business environment requires organizations to be flexible and open to change if they are to gain and retain their competitive age. Competitive business environment needs to modernize existing legacy system in to self-adaptive ones. Reengineering presents an approach to transfer a legacy system towards an evolvable system. Software reengineering is a leading system evolution technique which helps in effective cost control, quality improvements and time and risk reduction. However successful improvement of legacy system through reengineering requires portfolio analysis of legacy application around various quality and functional parameters some of which includes reliability and modularity of the functions, level of usability and maintainability as well as policy and standards of software architecture and availability of required documents. Portfolio analysis around these parameters will help to examine the legacy application on quality and functional gaps within the application [1]. In this paper we identify and measure risk factors related to quality and functional aspect of legacy system. Paper analyzes a variety of risk components related to quality and functional dimensions of legacy application. Identification and development of various metrics and important measures to compute impact value of individual risk component is also addressed. Existing quality and functional level of legacy system are considered to identify and categories risk components. The impact of various technical issues such as inconsistency between architecture of legacy and target system, unmodularised legacy system architecture, unavailability of required design documents, high degree of coupling between modules of legacy system has been covered in the paper..

View PDFchevron_right
Enterprise Application System Reengineering
David Yen

Journal of Database Management, 2006

Due to the rapid changes in information technology (IT), the life cycle to develop an information system has become significantly shorter. Furthermore, companies worldwide have invested much time and effort in developing their existing enterprise application systems in order to maintain their own competitive advantages. Specifically, they are facing a similar problem of preserving the investment. Information system reengineering technology (ISRT) is one way to solve this problem. However, most of the systems reengineered by using traditional ISRT may lack flexibility and reusability and also have some quality concerns. The component-based software engineering can provide some remedy by providing a flexible and reusable enterprise application system. Many companies could benefit from thinking more in terms of building their own business components for their information system areas. This article considers a reengineering approach in order to migrate legacy systems to component-based ...

View PDFchevron_right
Techrisk - A Decisional Framework to Measure Technical Dimensions of Legacy Application for Rejuvenation Through Reengineering
Vrinda Tokekar

International Journal of Software Engineering & Applications, 2011

Competitive business environment wants to modernize existing legacy system in to self-adaptive ones. A variety of options are available to renovate legacy system in to more contemporary system. Recently the phenomenon of "software reengineering ", a methodology to allow old ways of thinking to be replaced with new, fresh approaches to increase productivity and quality of system, has been reported. However evolving legacy system through reengineering is a risky and error-prone task due to extensive changes it requires in the majority of cases. Therefore cost effective reengineering requires identifying and measuring impact of system, managerial and technical risk. We present a technical domain framework TechRisk to identify and measure quality and functional dimensions of legacy system. The objective is to identify those risk factors of technical domain which are critical to the success of reengineering. Proposed decision driven framework TechRisk provide support to identify and eliminate the highest impact risks in the software reengineering process and help to create a successful reengineering solution.

View PDFchevron_right
MngRisk — A decisional framework to measure managerial dimensions of legacy application for rejuvenation through reengineering
Vrinda Tokekar

2011 3rd International Conference on Electronics Computer Technology, 2011

Nowadays legacy system reengineering has emerged as a well-known system evolution technique. The goal of reengineering is to increase productivity and quality of legacy system through fundamental rethinking and radical redesigning of system. A broad range of risk issues and concerns must be addressed to understand and model reengineering process. Overall success of reengineering effort requires to considering three distinctive but connected areas of interest i.e. system domain, managerial domain and technical domain.. We present a hierarchical managerial domain risk framework MngRisk to analyze managerial dimensions of legacy system. The fundamental premise of framework is to observe, extract and categories the contextual perspective models and risk clusters of managerial domain. This work contributes for a decision driven framework to identify and assess risk components of managerial domain. Proposed framework provides guidance on interpreting the results obtained from assessment to take decision about when evolution of a legacy system through reengineering is successful.

View PDFchevron_right
Evolving software reengineering technology for the emerging innovative-competitive era
Phillip Hwang

1994

This paper reports on a multi-tool commercial/military environment combining software Domain Analysis techniques with Reusable Software and Reengineering of Legacy Software. It is based on the development of a military version for the Department of Defense (DOD). The integrated tools in the military version are: Software Specification Assistant (SSA) and Software Reengineering Environment (SRE), developed by Computer Command and Control Company (CCCC) for Naval Surface Warfare Center (NSWC) and Joint Logistics Commanders (JLC), and the Advanced Research Project Agency (ARPA) STARS Software Engineering Environment (SEE) developed by Boeing for NAVAIR PMA 205. The paper describes transitioning these integrated tools to commercial use. There is a critical need for the transition for the following reasons: First, to date, 70 percent of programmers' time is applied to software maintenance. The work of these users has not been facilitated by existing tools. The addition of Software Re...

View PDFchevron_right

References (18)

  1. M. Hammer and J. Champy, Re- engineering the Colporation: A Manifcstoofor Business Revolution, Harper Business, New York, 1993.
  2. Richards, "DOD Legacy Sys- tems-Reverse-Engineering Data Requirements," Comm. ACM, May 1994. "Reverse Engineering and De- sign Recovery -A Taxonomy," IEEE Sojiwave, Jan. 1990, p. 13.
  3. P. Aiken, A. Muntz, and R.
  4. E. Chikofsky and J. Cross, I
  5. ~ ~~ ~ J A N U A R Y 1995 REFERENCES
  6. D. Coleman et al., "Using Metrics to Evaluate Software System Maintainability," Computer, Aug.
  7. D. Rombach and V. Basili, "Quantitative Software," Qualitdtrsicherung Znfomzatik-Spektrum, No. 10,
  8. N. Fenton, Software Metrics -A Rigorow Approach, Chapman & Hall, London, 1991.
  9. G. Berns, "Assessing Software Maintainability," Comm. ACM, Jan. 1984, pp. 32-49.
  10. J. Hartman and D.J. Robson, "Revalidation During the Software Maintenance Phase," Proc. Conf:
  11. T. Gilb, Prinnples of Software Engmeering Management, Addison-Wesley, Reading, Mass., 1988.
  12. M. Lehman and L. Belady, Program Euolution -Process of Software Change, Academic Press, London,
  13. G. Verdugo, "Portfolio Analysis -Managing Software as an Asset," Proc. Int'l Conj Software
  14. J.R. Horgan, S. London, and M. Lyu, "Achieving Software Quality with Testing Coverage Mea- 10.
  15. H. Sneed, "Regression Testing of Reengineered Software," Proc. Conf on Program Comprehension, 11. B. Boehm, Sofrware Engineering Economics, Prentice-Hall, Englewood Cliffs, N.J., 1983.
  16. R. Figlio, "Benefits of Reengineering," Proc. Sofrware Mazntenance Assoc. Con$, Software Maintenance 13. H. Sneed, Software-Wartung, Rudolf Mueller Verlag, Cologne, Germany, 1990. 1994, pp. 4449. 1987, pp. 145-156 (in German).
  17. Sofrware Maintenance, IEEE CS Press, Los Alamitos, Calif., 1989, pp. 70-79. 1985. Maintenance Management, Software Maintenance Assoc., New York, 1988, pp. 17-24. sures,'' Computer, Sept. 1994, pp. 60-69.
  18. IEEE CS Press, Los Alamitos, Calif., 1993, pp. 149.155. Assoc., New York, 1989.

Related papers

Iterative Reengineering of Legacy Systems
Alessandro Bianchi

IEEE Transactions on Software Engineering, 2003

During its life a legacy system is subjected to many maintenance activities, which cause degradation of the quality of the system: when this degradation exceeds a critical threshold the legacy system needs to be reengineered. In order to preserve the asset represented by the legacy system, the familiarity with it gained by the system's maintainers and users, and the continuity of execution of current operations during the reengineering process, the system needs to be reengineered gradually. Moreover, each program needs to be reengineered within a short period of time. The paper proposes a reengineering process model, which is applied to an in-use legacy system to confirm that the process satisfies previous requirements and to measure its effectiveness. The reengineered system replaced the legacy one to the satisfaction of all the stakeholders; the reengineering process also had a satisfactory impact on the quality of the system. Finally, this paper contributes to validate the cause-effect relationship between the reengineering process and overcoming the aging symptoms of a software system.

View PDFchevron_right
Software Reengineering -A Frame Of Reference
Journal of Computer Science IJCSIS

Now day development of software is describe by immediate process. Old systems have to take on the recent technologies; It can be achieved by changing or finding the features, I.e, Reengineering. Our proposed paper clarifies about the reengineering process of software. It also explains the efficient and better process in reengineering. There are two type common reengineering objectives. Improved feature: the existing software system will be of minimum quality, because of more changing during the time course. The main objective of reengineering is to increase software quality and to provide present working documentation. A higher quality degree is needed to enhance reliability, to minimize the maintenance cost, to develop maintainability, and to make for functional improvement.

View PDFchevron_right
20 Years of Software-Reengineering: A Résumé
Harry Sneed

This paper is an attempt to define what software reengineering is and what it has accomplished in the light of 20 years of practical application. The paper points out that reengineering is one of the many software maintenance activities, i.e. everything done with software once it has been put to use. Reengineering actions are devoted to improving the technical quality of existing software. By accepting this definition, it is possible to distinguish reengineering from other related activities performed on a software product after its first release such as reverse engineering, redocumentation, evolution and migration.

View PDFchevron_right
Estimating the Costs of a Reengineering Project
Harry Sneed

2005

Accurate estimation of project costs is an essential prerequisite to making a reengineering project. Existing systems are usually reengineered because it is cheaper to reengineer them than to redevelop or to replace them. However, to make this decision, management must know what the reengineering will cost. This contribution describes an eight step tool supported process for calculating the time and the costs required to reengineer an existing system. The process is derived from the author's 20 year experience in estimating reengineering projects and has been validated by several real life field experiments in which it has been refined and calibrated.

View PDFchevron_right
Research Summary of A Study for the Estimation of Legacy Programs for Effective Reengineering
Shahanawaj Ahamad

ORIENTAL JOURNAL OF COMPUTER SCIENCE & TECHNOLOGY ISSN: 0974-6471, 2017

The present research estimates the efficacy of a legacy program and the areas of its development. The research also intends to put forward as to what extent reengineering of a legacy program has to be done on the basis of the estimation approach. The study has tried to outline the current issues and trends in reengineering of a legacy program from various perspectives. An allinclusive literature review reveals that a lot of work has already been piled up with legacy system estimation and the reengineering domain, yet the basic assumptions of Complexity, Quality and Effort have not been worked out collectively. Hence the present research underlines this very maxim and studies the reengineering of a legacy program on the paradigms of Quality, Complexity, and Effort Estimation collectively. The findings put forward an equation and reengineering scale which would be highly compatible with present technology for the feasibility of an effective reengineering.

View PDFchevron_right

Related topics

  • Information Systems
  • Software Engineering
  • Software Quality

    • Cited by

    A Collaborative Method for Reuse Potential Assessment in Reengineering-Based Product Line Adoption
    Muhammad Riski

    2007

    Software product lines are rarely developed from scratch. Instead the development of a product line by reengineering existing systems is a more common scenario, which relies on the collaboration of diverse stakeholders to lay its foundations. The paper describes a collaborative scoping approach for organizations migrating existing products to a product line. The approach uses established practices from the field of reengineering and architectural recovery and synthesizes them in a collaborative process. The proposed approach employs best practices and tools from the area of collaboration engineering to achieve effective collaboration. The paper presents a case study as initial validation of the proposed approach.

    View PDFchevron_right
    Optimal Enhancement and Lifetime of Software Systems: A Control Theoretic Analysis
    Suresh Sethi

    Production and Operations Management, 2011

    We develop an optimal control model to maximize the net value provided by a software system over its useful life. The model determines the initial number of features in the system, the level of dynamic enhancement effort, and the lifetime of the system. The various factors affecting these optimal choices are systems characteristics (e.g., complexity, age, quality), user learning, and process maturity. We also consider that there is a time lag between the addition of a feature and the realization of its benefit to users.

    View PDFchevron_right
    Developing legacy system migration methods and tools for technology transfer
    Rita Francese

    Software: Practice and Experience, 2008

    This paper presents the research results of an ongoing technology transfer project carried out in cooperation between the University of Salerno and a small software company. The project is aimed at developing and transferring migration technology to the industrial partner. The partner should be enabled to migrate monolithic multi-user COBOL legacy systems to a multi-tier Web-based architecture. The assessment of the legacy systems of the partner company revealed that these systems had a very low level of decomposability with spaghetti-like code and embedded control flow and database accesses within the user interface descriptions. For this reason, it was decided to adopt an incremental migration strategy based on the reengineering of the user interface using Web technology, on the transformation of interactive legacy programs into batch programs, and the wrapping of the legacy programs. A middleware framework links the new Web-based user interface with the Wrapped Legacy System. An Eclipse plug-in, named MELIS (migration environment for legacy information systems), was also developed to support the migration process. Both the migration strategy and the tool have been applied to two essential subsystems of the most business critical legacy system of the partner company.

    View PDFchevron_right
    Legacy object modeling speeds software integration
    Niall Emmart

    Communications of the ACM, 1998

    handed down from a previous generation of developers, often with a long history of adaptation to the enterprise. In many cases the large, critical production systems referred to as 'legacy' are well-planned, well-managed, growing systems. In other cases, the 'legacy' now exists in an almost exclusively physical form (that is, a large corpus of program code and application data) frequently with inadequate or absent user and technical documentation. In the worst case, only run-time components may remain after the loss of source code. In addition, as organizations mature, diminishing numbers of technical personnel with direct knowledge of the application's internals remain on staff.

    View PDFchevron_right
    A generic cloud migration process model
    Dr. Mahdi Fahmideh

    European Journal of Information Systems, 2018

    Cloud computing literature provides a variety of perspectives towards the migration process, each with a different focus and mostly adopting heterogeneous technical-centric terminologies. Little, if any, studies have focused on developing an integrated and abstract process models which captures core domain constructs relevant to the cloud migration. By applying the metamodeling theoretical foundation, this article develops a generic process metamodel, as a domain language, for cloud migration. The metamodel is evaluated and refined through a three step approach including three case studies, domain expert review, and prototype system test. This research benefits academics and practitioners alike by underpinning a substrate for constructing, standardising, maintaining, and sharing bespoke cloud migration processes that suit given migration scenarios.

    View PDFchevron_right
    580 California St., Suite 400
    San Francisco, CA, 94104
    © 2025 Academia. All rights reserved