Software modernization

From Wikipedia, the free encyclopedia
  (Redirected from Automated software modernization)
Jump to navigation Jump to search

Legacy modernization, or software modernization, refers to the conversion, rewriting or porting of a legacy system to a modern computer programming language, software libraries, protocols, or hardware platform. Legacy transformation aims to retain and extend the value of the legacy investment through migration to new platforms.[1]


Legacy system modernization is often a large, multi-year project. Because these legacy systems are often critical in the operations of most enterprises, deploying the modernized system all at once introduces an unacceptable level of operational risk. As a result, legacy systems are typically modernized incrementally. Initially, the system consists completely of legacy code. As each increment is completed, the percentage of legacy code decreases. Eventually, the system is completely modernized. A migration strategy must ensure that the system remains fully functional during the modernization effort.

Making of software modernization decisions is a process within some organizational context. “Real world” decision making in business organizations often has to be made based on “bounded rationality”.[2] Besides that, there exist multiple (and possibly conflicting) decision criteria; the certainty, completeness, and availability of useful information (as a basis for the decision) is often limited.

Modernization strategies and benefits[3][edit]

  • Architecture Driven Modernization (ADM) is the initiative to standardize views of the existing systems in order to enable common modernization activities like code analysis and comprehension, and software transformation.
  • WMU (Warrants, Maintenance, Upgrade) is a model for choosing appropriate maintenance strategies based on aspired customer satisfaction level and their effects on it.[4]
  • SABA (Bennett et al., 1999) is a high-level framework for planning the evolution and migration of legacy systems, taking into account both organizational and technical issues.
  • Model Driven Engineering (MDE) is being investigated as an approach for reverse engineering and then forward engineering software code.[5][6][7]
  • Renaissance[8] Method for iteratively evaluating legacy systems, from technical, business, and organizational perspectives.
  • - Aversano at al. (2004) Measurement framework based on GQM (Goal-Question-Metrics) paradigm.
  • VDM (Visaggio's Decision Model)[9] Method and decision model for determining suitable software renewal processes at component-level based on the technical and economic qualities of those components.
  • SRRT (Economic Model to Software Rewriting and Replacement Times), Chan et al. (1996), Formal model for determining optimal software rewrite and replacement timings based on versatile metrics data.
  • Reengineering Planning Process (RPP), Sneed (1995), is a process model for estimating costs and benefits of reengineering.

Modernization risk management[edit]

  • Reengineering Project Failure Analysis, Bergey et al., 1999 (RPFA) is a check-list of potential problems related to reengineering projects, and of the corresponding appropriate technical and other means to react to the situation.
  • Risk-Managed Modernization, Seacord et al., 2003 (RMM) is a general software modernization management approach taking risks (and both technological and business objectives) explicitly into account.

Modernization costs[edit]

  • Softcalc (Sneed, 1995a) is a model and tool for estimating costs of incoming maintenance requests, developed based on COCOMO and FPA.
  • EMEE (Early Maintenance Effort Estimation)[10][11] is a new approach for quick maintenance effort estimation before starting the actual maintenance.
  • RENAISSANCE is a method to support system evolution by first recovering a stable basis using reengineering, and subsequently continuously improving the system by a stream of incremental changes. The approach integrates successfully with different project management processes[12]

Challenges in legacy modernization[edit]

Primary issues with a legacy system include very old systems with lack of documentation, lack of SMEs/ knowledge on the legacy systems and dearth of technology skills in which the legacy systems have been implemented. Typical legacy systems have been in existence for more than two decades. Migrating is fraught with challenges:

  • Organizational change management – Users must be re-trained and equipped to use and understand the new applications and platforms effectively.
  • Coexistence of legacy and new systems – Organizations with a large footprint of legacy systems cannot migrate at once. A phased modernization approach needs to be adopted. However, this brings its own set of challenges like providing complete business coverage with well understood and implemented overlapping functionality, data duplication; throw away systems to bridge legacy and new systems needed during the interim phases.[13]
  • Significant modernization costs and duration - Modernization of a complex mission critical legacy system may need large investments and the duration of having a fully running modernized system could run into years, not to mention unforeseen uncertainties in the process.
  • Stakeholders commitment - Main organization stakeholders must be convinced of the investment being made for modernization, since the benefits, and an immediate ROI may not be visible as compared to the modernization costs being invested.

Last but not the least, there is no one stop solution-fits all kind of option in modernization. With a multitude of commercial and bespoke options available for modernization, it’s critical for the customers, the sellers and the executors to understand the intricacies of various modernization techniques, their best applicable implementations, suitability in a particular context, and the best practices to follow before selecting the right modernization approach.

Modernization options[edit]

Over the years, several different options have come into being for legacy modernization – each of them met with varying success and adoption. Even now, there is a range of possibilities, as explained below, and there is no “the option” for all legacy transformation initiatives.

  • Migration: Migration of languages (3GL or 4GL), databases (legacy to RDBMS, and one RDBMS to another), platform (from one OS to another OS), often using automated parsers and converters for high efficiency. This is quick and cost-effective way of transforming legacy systems.
  • Re-engineering: A technique to rebuild legacy applications in a new technology or platform, with same or enhanced functionality – usually by adopting Service Oriented Architecture (SOA). This is the most efficient and agile way of transforming legacy applications.[5]
  • Re-hosting: Running the legacy applications, with no major changes, on a different platform. Business logic is preserved as application and data are migrated into the open environment. This option only needs the replacement of middleware, hardware, operating system, and database. [14]This is often used as an intermediate step to eliminate legacy and expensive hardware. Most common examples include mainframe applications being rehosted on UNIX or Wintel platform.
  • Package implementation: Replacement of legacy applications, in whole or part, with off-the-shelf software (COTS) such as ERP, CRM, SCM, Billing software etc.[15]

A legacy code is any application based on older technologies and hardware, such as mainframes, that continues to provide core services to an organization. Legacy applications are frequently large and difficult to modify, and scrapping or replacing them often means re-engineering an organization’s business processes as well. However, more and more applications that were written in so called modern languages like java are becoming legacy. Whereas 'legacy' languages such as COBOL are top on the list for what would be considered legacy, software written in newer languages can be just as monolithic, hard to modify, and thus, be candidates of modernization projects.

Re-implementing applications on new platforms in this way can reduce operational costs, and the additional capabilities of new technologies can provide access to functions such as web services and integrated development environments.[6] Once transformation is complete and functional equivalence has been reached the applications can be aligned more closely to current and future business needs through the addition of new functionality to the transformed application. The recent development of new technologies such as program transformation by software modernization enterprises have made the legacy transformation process a cost-effective and accurate way to preserve legacy investments and thereby avoid the costs and business impact of migration to entirely new software.

The goal of legacy transformation is to retain the value of the legacy asset on the new platform. In practice this transformation can take several forms. For example, it might involve translation of the source code, or some level of re-use of existing code plus a Web-to-host capability to provide the customer access required by the business. If a rewrite is necessary, then the existing business rules can be extracted to form part of the statement of requirements for a rewrite.

Software migration[edit]

Software migration is the process of moving from the use of one operating environment to another operating environment that is, in most cases, is thought to be a better one. For example, moving from Windows NT Server to Windows 2000 Server would usually be considered a migration because it involves making sure that new features are exploited, old settings do not require changing, and taking steps to ensure that current applications continue to work in the new environment. Migration could also mean moving from Windows NT to a UNIX-based operating system (or the reverse). Migration can involve moving to new hardware, new software, or both. Migration can be small-scale, such as migrating a single system, or large-scale, involving many systems, new applications, or a redesigned network.[16]

One can migrate data from one kind of database to another kind of database. This usually requires the data into some common format that can be output from the old database and input into the new database. Since the new database may be organized differently, it may be necessary to write a program that can process the migrating files.

When a software migration reaches functional equivalence, the migrated application can be aligned more closely to current and future business needs through the addition of new functionality to the transformed application.

The migration of installed software from an old PC to a new PC can be done with a software migration tool. Migration is also used to refer simply to the process of moving data from one storage device to another.

Articles, papers and books[edit]

Creating reusable software[edit]

Due to the evolution of technology today some companies or groups of people don’t know the importance of legacy systems. Some of their functions are too important to be left unused, and too expensive to reproduce again. The software industry and researchers have recently paid more attention towards component-based software development to enhance productivity and accelerate time to market.[17]

Risk-managed modernization[edit]

In general, three classes of information system technology are of interest in legacy system modernization: Technologies used to construct the legacy systems, including the languages and database systems. Modern technologies, which often represent nirvana to those mired in decades-old technology and which hold (the often unfulfilled) promise of powerful, effective, easily maintained enterprise information systems. Technologies offered by the legacy system vendors – These technologies provide an upgrade path for those too timid or wise to jump head-first into the latest wave of IT offerings. Legacy system vendors offer these technologies for one simple reason: to provide an upgrade path for system modernization that does not necessitate leaving the comfort of the “mainframe womb.” Although these technologies can provide a smoother road toward a modern system, they often result in an acceptable solution that falls short of the ideal.[18]

See also[edit]

Available Tools[edit]

  • apiwave - Most migrated APIs in top GitHub Java projects.


  1. ^ Gardner, D: "Not just a nip and tuck, application modernization extends the lifecycle of legacy code assets", ZDNet, October 24, 2006
  2. ^ Simon’s Bounded Rationality. Origins and use in Economic Theory
  3. ^ Jussi Koskinen; Jarmo Ahonen; Heikki Lintinen; Henna Sivula; Tero Tilus. "Estimation of the Business Value of Software Modernizations".
  4. ^ Izzet Sahin; Fatemeh ‘Mariam’ Zahedi (2001). "Policy analysis for warranty, maintenance, and upgrade of software systems". Journal of Software Maintenance: Research and Practice. 13: 469–493. doi:10.1002/smr.242.
  5. ^ a b ARTIST Methodology and Framework: A Novel Approach for the Migration of Legacy Software on the Cloud, 15th International Symposium on Symbolic and Numeric Algorithms for Scientific Computing (SYNASC), IEEE, 2013, pp. 424–431, doi:10.1109/SYNASC.2013.62
  6. ^ a b Software modernization and cloudification using the ARTIST migration methodology and framework, 15, Scalable Computing: Practice and Experience (SCPE), 2014, doi:10.12694/scpe.v15i2.980
  7. ^ The ARTIST research project
  8. ^ Ian Warren; Jane Ransom (2002). "Renaissance: A Method to Support Software System Evolution". 26th Annual International Computer Software and Applications Conference. p. 415. doi:10.1109/CMPSAC.2002.1045037.
  9. ^ G. Visaggio (2000). "Value-Based Decision Model for Renewal Processes in Software Maintenance". Annals of Software Engineering. 9: 215–233. doi:10.1023/A:1018980809600.
  10. ^ Andrea De Lucia; Eugenio Pompella & Silvio Stefanucci (July 2002). "Effort Estimation for Corrective Software Maintenance" (PDF). SEKE '02 Ischia, Italy. doi:10.1145/568760.568831.
  11. ^ De Lucia, A., Fasolino, A., and Pompella, E. A (2001). "Decisional Framework for Legacy System Management". IEEE CS Press. Florence, Italy: 642–651.
  12. ^ Koskinen, Jussi; Lintinen, Heikki; Sivula, Henna; Tilus, Tero. "Evaluation of Software Modernization Estimation Methods Using NIMSAD Meta Framework" (PDF). Publications of the Information Technology Research Institute. CiteSeerX
  13. ^ Santhosh G. Ramakrishna; V. V. (May 2007). "Logistics Legacy Modernization" (PDF). Infosys Technologies Limited.
  14. ^ "Mainframe Modernization in a Nutshell". Modernization Hub. Retrieved 2017-08-23.
  15. ^ Series, A. S. (ISO 9001:2008). Legacy Modernization – Transformation into an Agile Enterprise. A whitepaper on Legacy Modernization
  16. ^
  17. ^ S.K. Mishra; D.S. Kushwaha; A.K. Misra (July–August 2009). "Creating Reusable Software Component from Object-Oriented Legacy System through Reverse Engineering". The Journal of Object Technology. ETH Zurich. 8 (5): 133–152. doi:10.5381/jot.2009.8.5.a3.
  18. ^ Moltke, H. v. (Wednesday, January 22, 2003 9:55 PM). Risk-Managed Modernization. Jawaharlal Nehru, Speech to Parliament New Delhi,: