Software modernization

Short description: Updating or porting legacy software to modern practices and platforms

Software modernization, also known as legacy modernization or platform modernization, refers to the conversion, rewriting or porting of a legacy system to modern computer programming languages, architectures (e.g. microservices), software libraries, protocols or hardware platforms. Legacy transformation aims to retain and extend the value of the legacy investment through migration to new platforms to benefit from the advantage of the new technologies.[1]

As a basis and first step of software modernization initiatives, the strategy, the risk management, the estimation of costs, and its implementation, lies the knowledge of the system being modernized. The knowledge of what all functionalities are made for, and the knowledge of how it has been developed.[2] As the subject-matter experts (SMEs) who worked at the inception and during all evolutions of the application are no-longer available or have a partial knowledge, and the lack of proper and up-to-date documentation, modernization initiatives start with assessing and discovering the application using Software intelligence.[3]

## Contents

* 1 Strategies
* 1.1 Modernization strategies
* 1.2 Modernization risk management
* 1.3 Modernization costs
* 1.4 Challenges in legacy modernization
* 1.5 Modernization options
* 2 Software migration
* 3 Articles, papers and books
* 3.1 Creating reusable software
* 3.2 Risk-managed modernization
* 4 See also
* 5 References

## Strategies

This section is in list format, but may read better as prose. You can help by converting this section, if appropriate. Editing help is available. (October 2018)

|

This section possibly contains original research. Please improve it by verifying the claims made and adding inline citations. Statements consisting only of original research should be removed. (October 2018) (Learn how and when to remove this template message)

|

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”.[4] 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.

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.

### Modernization strategies

There are different drivers and strategies for software modernization:

* 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.
* Business-Focus Approach: The modernization strategy is tied to the business value added by the modernization. It implies defining the intersection of the criticality to the business of an applications with its technical quality.[1] This approach pushed by Gartner puts the Application Portfolio Analysis (APA) as a prerequisite of modernization decisions for an application portfolio to measures software health, risks, complexity and cost providing insight into application strengths and weaknesses.[5]
* Model Driven Engineering (MDE) is being investigated as an approach for reverse engineering and then forward engineering software code.[6][7][8]
* Renaissance[9] Method for iteratively evaluating legacy systems, from technical, business, and organizational perspectives.
* WMU (Warrants, Maintenance, Upgrade) is a model for choosing appropriate maintenance strategies based on aspired customer satisfaction level and their effects on it.[10][11]

### Modernization risk management

Software modernization[12] is a risky, difficult, long, and highly intellectual process involving multiple stakeholders. The software modernization tasks are supported by various tools related to Model-driven architecture from the Object Management Group and processes such as ISO/IEC 14764:2006 or Service-Oriented Migration and Reuse Technique (SMART).[13] Software modernization implies various manual and automated tasks performed by specialized knowledge workers. Tools are supporting project participants' tasks and help organize the collaboration and sequencing of the work.

A general software modernization management approach [14] taking risks (both technological and business objectives) explicitly into account consists of:

* Analysis the existing portfolio: measuring the technical quality and business value. Confronting the technical quality with business goals to define the right strategy: replace, no go, low priority, good candidate.
* Identify stakeholders: all persons involved in the software modernization: developers, testers, customers, end-users, architects, …
* Understand the requirements: requirements are divided in 4 categories: user, system, constraints and nonfunctional.
* Create the Business Case: the business case supports the decision process in considering different approaches when decision makers need it.
* Understand the system to be modernized: this is a critical step as software documentation is rarely up-to-date and projects are made by numerous teams, both internal or external and usually out of sight for long time. Extracting the content of the application and its architecture design help reason about the system.
* Understand and evaluate target technology: this allows compare and contrast technologies and capabilities against requirements and existing system.
* Define modernization strategy:[15] the strategy defines the transformation process. This strategy must accommodate changes happening during the modernization process (technologies changes, additional knowledge, requirement evolution).
* Reconcile strategy with stakeholder needs: implied stakeholders may have varying opinions on what is important and what is the best way to proceed. It is important to have a consensus between stakeholders.
* Estimate resources: when previous steps are defined, costs can be evaluated. It enables the management determining whether the modernization strategy is feasible given the available resources and constraints.

### Modernization costs

* 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)[16][17] 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[18]

### Challenges in legacy modernization

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.[19] Typical legacy systems have been in existence for more than two decades. Migrating is fraught with challenges:

* Lack of visibility across large application portfolios – Large IT organizations have hundreds, if not thousands, of software systems. Technology and functional knowledge are by nature distributed, diluted, and opaque. No central point of visibility for senior management and Enterprise Architects is a top issue – it is challenging to make modernization decisions about software systems without having the necessary quantitative and qualitative data about these systems across the enterprise.
* 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.[20]
* Poor management of structural quality (see software quality), resulting in a modernized application that carries more security, reliability performance and maintainability issues than the original system.
* 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.
* Software Composition – It is extremely rare that developers create 100% original code these days in anything built after 2010.[21] They are often using 3rd party and open source frameworks and software components to gain efficiency, speed, and reusability. This introduces two risks: 1.) vulnerabilities within the 3rd party code, and 2.) open source licensing risk.

Last but not 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

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.

* Application Assessment: Baselining the existing application portfolio using Software intelligence to understand software health, quality, composition, complexity, and cloud readiness to start segmenting and prioritizing applications for various modernization options.
* Application Discovery: Applications components are strongly interlaced implying requirement for understanding the complexity and resolving the interdependencies of software component.
* 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 converters or Program transformation systems for high efficiency. This is a quick and cost-effective way of transforming legacy systems.
* Cloud Migration: Migration of legacy applications to cloud platforms often using a methodology such as Gartner’s 5 Rs methodology to segment and prioritize apps into different models (Rehost, Refactor, Revise, Rebuild, Replace).
* Re-engineering: A technique to rebuild legacy applications in 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.[6] This requires application-level Software intelligence with legacy systems that are not well known or documented.
* 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.[22] 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.[23]

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.[7] 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

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.[24]

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

### Creating reusable software

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.[25]

### Risk-managed modernization

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.[26]

## See also

* System migration
* Data migration
* Green computing

## References

1. ↑ 1.0 1.1 Gardner, D: "Not just a nip and tuck, application modernization extends the lifecycle of legacy code assets", ZDNet, October 24, 2006
2. ↑ Wolfart, Daniele; Assunção, Wesley; da Silva, Ivonei; Domingos, Diogo; Schmeing, Ederson; Villaca, Guilherme; Paza, Diogo (June 2021). "Modernizing Legacy Systems with Microservices: A Roadmap". Evaluation and Assessment in Software Engineering. pp. 149–159. doi:10.1145/3463274.3463334. ISBN 9781450390538. https://dl.acm.org/doi/pdf/10.1145/3463274.3463334.
3. ↑ Bartoszuk, Cezary; Dąbrowski, Robert; Stencel, Krzysztof; Timoszuk, Grzegorz (June 2013). "On quick comprehension and assessment of software". Proceedings of the 14th International Conference on Computer Systems and Technologies. pp. 161–168. doi:10.1145/2516775.2516806. ISBN 9781450320214. https://dl.acm.org/doi/pdf/10.1145/2516775.2516806.
4. ↑ Simon’s Bounded Rationality. Origins and use in Economic Theory
5. ↑ Stefan Van Der Zijden; Thomas Klinect. Building a Multiplatform Application Modernization Business Case. https://www.gartner.com/en/documents/3881472.
6. ↑ 6.0 6.1 Menychtas, Andreas; Santzaridou, Christina; Kousiouris, George; Varvarigou, Theodora; Orue-Echevarria, Leire; Alonso, Juncal; Gorronogoitia, Jesus; Bruneliere, Hugo et al. (2013), "ARTIST Methodology and Framework: A Novel Approach for the Migration of Legacy Software on the Cloud", 2013 15th International Symposium on Symbolic and Numeric Algorithms for Scientific Computing, 15th International Symposium on Symbolic and Numeric Algorithms for Scientific Computing (SYNASC), IEEE, pp. 424–431, doi:10.1109/SYNASC.2013.62, ISBN 978-1-4799-3036-4, https://hal.inria.fr/hal-00869276/file/ARTISTMethodologyFramework_SYNACS-MICAS2013.pdf
7. ↑ 7.0 7.1 Menychtas, Andreas; Konstanteli, Kleopatra; Alonso, Juncal; Orue-Echevarria, Leire; Gorronogoitia, Jesus; Kousiouris, George; Santzaridou, Christina; Bruneliere, Hugo et al. (2014), "Software modernization and cloudification using the ARTIST migration methodology and framework", Scalable Computing: Practice and Experience 15 (2), doi:10.12694/scpe.v15i2.980
8. ↑ The ARTIST research project
9. ↑ Ian Warren; Jane Ransom (2002). "Renaissance: A Method to Support Software System Evolution". 26th Annual International Computer Software and Applications Conference. pp. 415–420. doi:10.1109/CMPSAC.2002.1045037. ISBN 978-0-7695-1727-8.
10. ↑ Izzet Sahin; Fatemeh ‘Mariam’ Zahedi (2001). "Policy analysis for warranty, maintenance, and upgrade of software systems". Journal of Software Maintenance: Research and Practice 13 (6): 469–493. doi:10.1002/smr.242.
11. ↑ Jussi Koskinen; Jarmo Ahonen; Heikki Lintinen; Henna Sivula; Tero Tilus. Estimation of the Business Value of Software Modernizations. https://www.researchgate.net/publication/228951819.
12. ↑ "VB6 migration. Why compromise data security when you can migrate to more modern platforms?". https://www.abtosoftware.com/expertise/vb6-migration.
13. ↑ Lewis, G.; Morris, E.; Smith, D.; O'Brien, L. (2005). "Service-Oriented Migration and Reuse Technique (SMART)". 13th IEEE International Workshop on Software Technology and Engineering Practice (STEP'05). pp. 222–229. doi:10.1109/step.2005.24. ISBN 0-7695-2639-X.
14. ↑ Lewis, Grace A.; Plakosh, Daniel; Seacord, Robert C. (2003). Modernizing Legacy Systems: Software Technologies, Engineering Processes, and Business Practices. Addison-Wesley Professional. pp. 27–37. ISBN 0321118847. https://www.oreilly.com/library/view/modernizing-legacy-systems/0321118847/.
15. ↑ Mobilize.Net. "A Fast Track to Software Modernization | Mobilize.Net" (in en). https://www.mobilize.net/resources/guides/fast-track-software-modernization.
16. ↑ Andrea De Lucia; Eugenio Pompella; Silvio Stefanucci (July 2002). "Effort Estimation for Corrective Software Maintenance". Proceedings of the 14th international conference on Software engineering and knowledge engineering - SEKE '02. SEKE '02 Ischia, Italy. pp. 409. doi:10.1145/568760.568831. ISBN 978-1581135565. http://staff.unak.is/not/andy/MScMaintenance0809/Lectures/Add/EffortEstimationCorrective.pdf.
17. ↑ De Lucia, A.; Fasolino, A.R.; Pompelle, E. (2001). "A decisional framework for legacy system management". Proceedings IEEE International Conference on Software Maintenance. ICSM 2001. pp. 642–651. doi:10.1109/ICSM.2001.972781. ISBN 0-7695-1189-9.
18. ↑ Koskinen, Jussi; Lintinen, Heikki; Sivula, Henna; Tilus, Tero. "Evaluation of Software Modernization Estimation Methods Using NIMSAD Meta Framework". Publications of the Information Technology Research Institute.
19. ↑ "Legacy Modernization Challenges". 2 December 2025. https://dev.to/abhijith_rs_04018cf67d112/top-challenges-in-legacy-modernization-that-most-businesses-overlook-5c7g.
20. ↑ "Logistics Legacy Modernization". Infosys Technologies Limited. May 2007. http://www.infosys.com/industries/logistics-distribution/white-papers/Documents/logistics-legacy-modernization.pdf.
21. ↑ C. Ghezzi (2018). "Supporting Dependable Evolution". in Gruhn, Volker; Striemer, Rüdiger. The Essence of Software Engineering. pp. 32–33. doi:10.1007/978-3-319-73897-0. ISBN 978-3-319-73897-0. http://www.oapen.org/search?identifier=1002191.
22. ↑ "Mainframe Modernization in a Nutshell" (in en-US). http://www.modernizationhub.com.
23. ↑ Series, A. S. (ISO 9001:2008). Legacy Modernization – Transformation into an Agile Enterprise. A whitepaper on Legacy Modernization
24. ↑ SearchCIO.com
25. ↑ 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 8 (5): 133–152. doi:10.5381/jot.2009.8.5.a3.
26. ↑ Moltke, H. v. (Wednesday, January 22, 2003 9:55 PM). Risk-Managed Modernization. Jawaharlal Nehru, Speech to Parliament New Delhi,: Seacord.book.

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Software modernization. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Software_modernization&oldid=4296357"