503:
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.
116:
65:
180:
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.
471:
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
418:
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. Once transformation is complete and functional equivalence has been
406:
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,
333:
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,
293:
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
198:
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. This approach pushed by Gartner puts the Application Portfolio Analysis
502:
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
493:
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
328:
Software
Composition â It is extremely rare that developers create 100% original code these days in anything built after 2010. 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
253:
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
309:
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
179:
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
42:
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
382:
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.<ration
752:
Menychtas, Andreas; Konstanteli, Kleopatra; Alonso, Juncal; Orue-Echevarria, Leire; Gorronogoitia, Jesus; Kousiouris, George; Santzaridou, Christina; Bruneliere, Hugo; Pellens, Bram; Stuer, Peter; Strauss, Oliver; Senkova, Tatiana; Varvarigou, Theodora (2014), "Software modernization and
232:
or
Service-Oriented Migration and Reuse Technique (SMART). 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.
342:
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.
298:
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
47:(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
283:
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
320:
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
431:. 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
696:
Menychtas, Andreas; Santzaridou, Christina; Kousiouris, George; Varvarigou, Theodora; Orue-Echevarria, Leire; Alonso, Juncal; Gorronogoitia, Jesus; Bruneliere, Hugo; Strauss, Oliver; Senkova, Tatiana; Pellens, Bram; Stuer, Peter (2013),
451:
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.
423:
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.
39:), 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.
324:
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
475:
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.
367:
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,
260:
Define modernization strategy: the strategy defines the transformation process. This strategy must accommodate changes happening during the modernization process (technologies changes, additional knowledge, requirement
419:
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
479:
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.
267:
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.
264:
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.
240:
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
176:â. 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.
443:
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
199:(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.
303:
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.
220:
Software modernization is a risky, difficult, long, and highly intellectual process involving multiple stakeholders. The software modernization tasks are supported by various tools related to
415:
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.
195:(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.
172:
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 â
360:
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
383:
Hub|language=en-US|access-date=2017-08-23}}</ref> This is often used as an intermediate step to eliminate legacy and expensive hardware. Most common examples include
351:
to understand software health, quality, composition, complexity, and cloud readiness to start segmenting and prioritizing applications for various modernization options.
211:
WMU (Warrants, Maintenance, Upgrade) is a model for choosing appropriate maintenance strategies based on aspired customer satisfaction level and their effects on it.
357:: Applications components are strongly interlaced implying requirement for understanding the complexity and resolving the interdependencies of software component.
334:
their best applicable implementations, suitability in a particular context, and the best practices to follow before selecting the right modernization approach.
539:
394:
Package implementation: Replacement of legacy applications, in whole or part, with off-the-shelf software (COTS) such as ERP, CRM, SCM, Billing software etc.
1138:
Koskinen, Jussi; Lintinen, Heikki; Sivula, Henna; Tilus, Tero. "Evaluation of
Software Modernization Estimation Methods Using NIMSAD Meta Framework".
1164:
236:
A general software modernization management approach taking risks (both technological and business objectives) explicitly into account consists of:
371:
Re-engineering: A technique to rebuild legacy applications in new technology or platform, with same or enhanced functionality â usually by adopting
257:
Understand and evaluate target technology: this allows compare and contrast technologies and capabilities against requirements and existing system.
1289:
Moltke, H. v. (Wednesday, January 22, 2003 9:55 PM). Risk-Managed
Modernization. Jawaharlal Nehru, Speech to Parliament New Delhi,: Seacord.book.
317:), resulting in a modernized application that carries more security, reliability performance and maintainability issues than the original system.
1083:
306:
Organizational change management â Users must be re-trained and equipped to use and understand the new applications and platforms effectively.
280:
EMEE (Early
Maintenance Effort Estimation) is a new approach for quick maintenance effort estimation before starting the actual maintenance.
250:
Create the
Business Case: the business case supports the decision process in considering different approaches when decision makers need it.
468:
can be small-scale, such as migrating a single system, or large-scale, involving many systems, new applications, or a redesigned network.
556:
Wolfart, Daniele; Assunção, Wesley; da Silva, Ivonei; Domingos, Diogo; Schmeing, Ederson; Villaca, Guilherme; Paza, Diogo (June 2021).
277:
Softcalc (Sneed, 1995a) is a model and tool for estimating costs of incoming maintenance requests, developed based on COCOMO and FPA.
1236:
Series, A. S. (ISO 9001:2008). Legacy
Modernization â Transformation into an Agile Enterprise. A whitepaper on Legacy Modernization
244:
Identify stakeholders: all persons involved in the software modernization: developers, testers, customers, end-users, architects, âŚ
310:
overlapping functionality, data duplication; throw-away systems to bridge legacy and new systems needed during the interim phases.
354:
1032:
1200:
829:
726:
713:, 15th International Symposium on Symbolic and Numeric Algorithms for Scientific Computing (SYNASC), IEEE, pp. 424â431,
435:
is necessary, then the existing business rules can be extracted to form part of the statement of requirements for a rewrite.
853:
Izzet Sahin; Fatemeh âMariamâ Zahedi (2001). "Policy analysis for warranty, maintenance, and upgrade of software systems".
705:
698:
208:
Renaissance Method for iteratively evaluating legacy systems, from technical, business, and organizational perspectives.
1055:
1114:
955:
622:
577:
375:(SOA). This is the most efficient and agile way of transforming legacy applications. This requires application-level
192:
159:
141:
247:
Understand the requirements: requirements are divided in 4 categories: user, system, constraints and nonfunctional.
930:
Lewis, G.; Morris, E.; Smith, D.; O'Brien, L. (2005). "Service-Oriented
Migration and Reuse Technique (SMART)".
990:
126:
1007:
980:
205:(MDE) is being investigated as an approach for reverse engineering and then forward engineering software code.
1304:
1040:
Proceedings of the 14th international conference on Software engineering and knowledge engineering - SEKE '02
372:
1079:
1245:
1097:
De Lucia, A.; Fasolino, A.R.; Pompelle, E. (2001). "A decisional framework for legacy system management".
408:
464:
operating system (or the reverse). Migration can involve moving to new hardware, new software, or both.
699:"ARTIST Methodology and Framework: A Novel Approach for the Migration of Legacy Software on the Cloud"
1259:"Creating Reusable Software Component from Object-Oriented Legacy System through Reverse Engineering"
221:
1148:
902:
812:
767:
679:
364:
systems for high efficiency. This is a quick and cost-effective way of transforming legacy systems.
202:
1181:
C. Ghezzi (2018). "Supporting Dependable Evolution". In Gruhn, Volker; Striemer, RĂźdiger (eds.).
300:
225:
137:
982:
Modernizing Legacy Systems: Software Technologies, Engineering Processes, and Business Practices
540:"Not just a nip and tuck, application modernization extends the lifecycle of legacy code assets"
133:
86:
1143:
807:
762:
420:
361:
802:
Ian Warren; Jane Ransom (2002). "Renaissance: A Method to Support Software System Evolution".
889:
707:
2013 15th International Symposium on Symbolic and Numeric Algorithms for Scientific Computing
666:
432:
376:
348:
48:
44:
917:"VB6 migration. Why compromise data security when you can migrate to more modern platforms?"
494:
component-based software development to enhance productivity and accelerate time to market.
403:
32:
932:
13th IEEE International Workshop on Software Technology and Engineering Practice (STEP'05)
601:
Bartoszuk, Cezary; DÄ
browski, Robert; Stencel, Krzysztof; Timoszuk, Grzegorz (June 2013).
8:
173:
427:
The goal of legacy transformation is to retain the value of the legacy asset on the new
1206:
1120:
1073:
1061:
961:
916:
835:
732:
628:
583:
399:
384:
1196:
1110:
1051:
986:
951:
881:
825:
722:
645:
618:
607:
Proceedings of the 14th International Conference on Computer Systems and Technologies
602:
587:
573:
557:
428:
1224:
1210:
1124:
1065:
965:
839:
632:
1270:
1188:
1102:
1043:
943:
935:
862:
817:
772:
736:
714:
610:
565:
512:
465:
314:
1182:
879:
1030:
821:
407:
more and more applications that were written in so called modern languages like
658:
517:
1192:
1298:
1106:
36:
28:
1275:
1258:
1099:
Proceedings IEEE International Conference on Software Maintenance. ICSM 2001
777:
614:
569:
347:
Application Assessment: Baselining the existing application portfolio using
718:
453:
448:
90:
1047:
229:
939:
880:
Jussi Koskinen; Jarmo Ahonen; Heikki Lintinen; Henna Sivula; Tero Tilus.
751:
695:
1031:
Andrea De Lucia; Eugenio Pompella & Silvio Stefanucci (July 2002).
804:
26th Annual International Computer Software and Applications Conference
457:
444:
188:
There are different drivers and strategies for software modernization:
947:
753:
cloudification using the ARTIST migration methodology and framework",
79:
16:
Updating or porting legacy software to modern practices and platforms
1239:
866:
144:. Statements consisting only of original research should be removed.
75:
1256:
852:
659:"Building a Multiplatform Application Modernization Business Case"
23:
or platform modernization, refers to the conversion, rewriting or
600:
24:
790:
1227:
Modernization in a Nutshell|last=|first=|date=|website=Moderniz
656:
646:
Simonâs Bounded Rationality. Origins and use in Economic Theory
555:
388:
329:
within the 3rd party code, and 2.) open source licensing risk.
1140:
Publications of the Information Technology Research Institute
979:
Lewis, Grace A.; Plakosh, Daniel; Seacord, Robert C. (2003).
882:"Estimation of the Business Value of Software Modernizations"
412:
1162:
1257:
S.K. Mishra; D.S. Kushwaha; A.K. Misra (JulyâAugust 2009).
929:
461:
558:"Modernizing Legacy Systems with Microservices: A Roadmap"
379:
with legacy systems that are not well known or documented.
411:
are becoming legacy. Whereas 'legacy' languages such as
1096:
1137:
1033:"Effort Estimation for Corrective Software Maintenance"
1008:"A Fast Track to Software Modernization | Mobilize.Net"
855:
Journal of Software Maintenance: Research and Practice
801:
288:
978:
603:"On quick comprehension and assessment of software"
1225:http://www.modernizationhub.com%7Ctitle=Mainframe
562:Evaluation and Assessment in Software Engineering
1296:
215:
985:. Addison-Wesley Professional. pp. 27â37.
691:
689:
747:
745:
497:
488:
483:
686:
1163:Santhosh G. Ramakrishna; V. V. (May 2007).
755:Scalable Computing: Practice and Experience
313:Poor management of structural quality (see
183:
742:
1274:
1180:
1147:
1082:) CS1 maint: location missing publisher (
811:
776:
766:
160:Learn how and when to remove this message
1005:
337:
1042:. SEKE '02 Ischia, Italy. p. 409.
657:Stefan Van Der Zijden; Thomas Klinect.
534:
532:
387:applications being rehosted on UNIX or
1297:
271:
438:
529:
109:
58:
19:Legacy modernization, also known as
1184:The Essence of Software Engineering
13:
289:Challenges in legacy modernization
14:
1316:
472:can process the migrating files.
193:Architecture Driven Modernization
1263:The Journal of Object Technology
1165:"Logistics Legacy Modernization"
114:
63:
1283:
1250:
1230:
1217:
1174:
1170:. Infosys Technologies Limited.
1156:
1131:
1090:
1024:
999:
972:
923:
909:
873:
846:
35:languages, architectures (e.g.
795:
784:
650:
639:
594:
549:
78:format but may read better as
1:
523:
373:Service Oriented Architecture
216:Modernization risk management
54:
456:could also mean moving from
294:is fraught with challenges:
7:
822:10.1109/CMPSAC.2002.1045037
791:The ARTIST research project
506:
140:the claims made and adding
10:
1321:
498:Risk-managed modernization
489:Creating reusable software
484:Articles, papers and books
1193:10.1007/978-3-319-73897-0
222:Model-driven architecture
1107:10.1109/ICSM.2001.972781
1078:: CS1 maint: location (
203:Model Driven Engineering
184:Modernization strategies
1276:10.5381/jot.2009.8.5.a3
778:10.12694/scpe.v15i2.980
615:10.1145/2516775.2516806
570:10.1145/3463274.3463334
226:Object Management Group
87:converting this section
897:Cite journal requires
719:10.1109/SYNASC.2013.62
674:Cite journal requires
421:program transformation
362:Program transformation
228:and processes such as
45:subject-matter experts
21:software modernization
1223:ef>{{Cite web|url=
1048:10.1145/568760.568831
377:Software intelligence
355:Application Discovery
349:Software intelligence
338:Modernization options
301:Enterprise Architects
49:Software intelligence
1305:Software maintenance
1101:. pp. 642â651.
940:10.1109/step.2005.24
934:. pp. 222â229.
806:. pp. 415â420.
609:. pp. 161â168.
564:. pp. 149â159.
33:computer programming
449:Windows 2000 Server
272:Modernization costs
174:bounded rationality
1187:. pp. 32â33.
546:, October 24, 2006
439:Software migration
230:ISO/IEC 14764:2006
125:possibly contains
89:, if appropriate.
43:developed. As the
1202:978-3-319-73897-0
831:978-0-7695-1727-8
728:978-1-4799-3036-4
445:Windows NT Server
254:about the system.
170:
169:
162:
127:original research
108:
107:
1312:
1290:
1287:
1281:
1280:
1278:
1254:
1248:
1243:
1237:
1234:
1228:
1221:
1215:
1214:
1178:
1172:
1171:
1169:
1160:
1154:
1153:
1151:
1135:
1129:
1128:
1094:
1088:
1087:
1077:
1069:
1037:
1028:
1022:
1021:
1019:
1018:
1012:www.mobilize.net
1003:
997:
996:
976:
970:
969:
927:
921:
920:
913:
907:
906:
900:
895:
893:
885:
877:
871:
870:
850:
844:
843:
815:
799:
793:
788:
782:
781:
780:
770:
749:
740:
739:
712:
703:
693:
684:
683:
677:
672:
670:
662:
654:
648:
643:
637:
636:
598:
592:
591:
553:
547:
536:
513:System migration
315:software quality
165:
158:
154:
151:
145:
142:inline citations
118:
117:
110:
103:
100:
94:
85:You can help by
67:
66:
59:
1320:
1319:
1315:
1314:
1313:
1311:
1310:
1309:
1295:
1294:
1293:
1288:
1284:
1255:
1251:
1244:
1240:
1235:
1231:
1222:
1218:
1203:
1179:
1175:
1167:
1161:
1157:
1149:10.1.1.106.2633
1136:
1132:
1117:
1095:
1091:
1071:
1070:
1058:
1035:
1029:
1025:
1016:
1014:
1004:
1000:
993:
977:
973:
958:
928:
924:
915:
914:
910:
898:
896:
887:
886:
878:
874:
867:10.1002/smr.242
851:
847:
832:
813:10.1.1.137.7362
800:
796:
789:
785:
768:10.1.1.675.6225
750:
743:
729:
710:
701:
694:
687:
675:
673:
664:
663:
655:
651:
644:
640:
625:
599:
595:
580:
554:
550:
537:
530:
526:
509:
500:
491:
486:
441:
340:
291:
274:
218:
186:
166:
155:
149:
146:
131:
119:
115:
104:
98:
95:
84:
68:
64:
57:
17:
12:
11:
5:
1318:
1308:
1307:
1292:
1291:
1282:
1269:(5): 133â152.
1249:
1238:
1229:
1216:
1201:
1173:
1155:
1130:
1115:
1089:
1057:978-1581135565
1056:
1023:
1006:Mobilize.Net.
998:
991:
971:
956:
922:
908:
899:|journal=
872:
861:(6): 469â493.
845:
830:
794:
783:
741:
727:
685:
676:|journal=
649:
638:
623:
593:
578:
548:
527:
525:
522:
521:
520:
518:Data migration
515:
508:
505:
499:
496:
490:
487:
485:
482:
440:
437:
396:
395:
392:
380:
369:
365:
358:
352:
339:
336:
331:
330:
326:
322:
318:
311:
307:
304:
290:
287:
286:
285:
281:
278:
273:
270:
269:
268:
265:
262:
258:
255:
251:
248:
245:
242:
217:
214:
213:
212:
209:
206:
200:
196:
185:
182:
168:
167:
122:
120:
113:
106:
105:
71:
69:
62:
56:
53:
15:
9:
6:
4:
3:
2:
1317:
1306:
1303:
1302:
1300:
1286:
1277:
1272:
1268:
1264:
1260:
1253:
1247:
1246:SearchCIO.com
1242:
1233:
1226:
1220:
1212:
1208:
1204:
1198:
1194:
1190:
1186:
1185:
1177:
1166:
1159:
1150:
1145:
1141:
1134:
1126:
1122:
1118:
1116:0-7695-1189-9
1112:
1108:
1104:
1100:
1093:
1085:
1081:
1075:
1067:
1063:
1059:
1053:
1049:
1045:
1041:
1034:
1027:
1013:
1009:
1002:
994:
988:
984:
983:
975:
967:
963:
959:
957:0-7695-2639-X
953:
949:
945:
941:
937:
933:
926:
918:
912:
904:
891:
883:
876:
868:
864:
860:
856:
849:
841:
837:
833:
827:
823:
819:
814:
809:
805:
798:
792:
787:
779:
774:
769:
764:
760:
756:
748:
746:
738:
734:
730:
724:
720:
716:
709:
708:
700:
692:
690:
681:
668:
660:
653:
647:
642:
634:
630:
626:
624:9781450320214
620:
616:
612:
608:
604:
597:
589:
585:
581:
579:9781450390538
575:
571:
567:
563:
559:
552:
545:
541:
535:
533:
528:
519:
516:
514:
511:
510:
504:
495:
481:
477:
473:
469:
467:
463:
459:
455:
450:
446:
436:
434:
430:
425:
422:
416:
414:
410:
405:
401:
393:
390:
386:
381:
378:
374:
370:
366:
363:
359:
356:
353:
350:
346:
345:
344:
335:
327:
323:
319:
316:
312:
308:
305:
302:
297:
296:
295:
282:
279:
276:
275:
266:
263:
259:
256:
252:
249:
246:
243:
239:
238:
237:
234:
231:
227:
223:
210:
207:
204:
201:
197:
194:
191:
190:
189:
181:
177:
175:
164:
161:
153:
143:
139:
135:
129:
128:
123:This section
121:
112:
111:
102:
93:is available.
92:
88:
82:
81:
77:
72:This section
70:
61:
60:
52:
50:
46:
40:
38:
37:microservices
34:
30:
29:legacy system
26:
22:
1285:
1266:
1262:
1252:
1241:
1232:
1219:
1183:
1176:
1158:
1139:
1133:
1098:
1092:
1039:
1026:
1015:. Retrieved
1011:
1001:
981:
974:
931:
925:
911:
890:cite journal
875:
858:
854:
848:
803:
797:
786:
758:
754:
706:
667:cite journal
652:
641:
606:
596:
561:
551:
543:
538:Gardner, D:
501:
492:
478:
474:
470:
442:
426:
417:
397:
341:
332:
292:
235:
219:
187:
178:
171:
156:
150:October 2018
147:
124:
99:October 2018
96:
91:Editing help
73:
41:
20:
18:
404:application
400:legacy code
261:evolution).
1017:2021-03-19
992:0321118847
948:10344/2208
524:References
462:UNIX-based
458:Windows NT
241:candidate.
134:improve it
55:Strategies
31:to modern
1144:CiteSeerX
1074:cite book
808:CiteSeerX
763:CiteSeerX
588:235474042
466:Migration
454:Migration
391:platform.
385:mainframe
368:Replace).
325:invested.
284:processes
224:from the
138:verifying
1299:Category
1211:49187426
1125:32184332
1066:10627249
966:18912663
840:16563177
633:17034416
507:See also
429:platform
321:process.
737:8150975
433:rewrite
402:is any
132:Please
25:porting
1209:
1199:
1146:
1123:
1113:
1064:
1054:
989:
964:
954:
838:
828:
810:
765:
735:
725:
631:
621:
586:
576:
389:Wintel
74:is in
1207:S2CID
1168:(PDF)
1121:S2CID
1062:S2CID
1036:(PDF)
962:S2CID
836:S2CID
761:(2),
733:S2CID
711:(PDF)
702:(PDF)
629:S2CID
584:S2CID
544:ZDNet
460:to a
413:COBOL
80:prose
27:of a
1197:ISBN
1111:ISBN
1084:link
1080:link
1052:ISBN
987:ISBN
952:ISBN
903:help
826:ISBN
723:ISBN
680:help
619:ISBN
574:ISBN
409:java
76:list
1271:doi
1189:doi
1103:doi
1044:doi
944:hdl
936:doi
863:doi
818:doi
773:doi
715:doi
611:doi
566:doi
447:to
136:by
1301::
1265:.
1261:.
1205:.
1195:.
1142:.
1119:.
1109:.
1076:}}
1072:{{
1060:.
1050:.
1038:.
1010:.
960:.
950:.
942:.
894::
892:}}
888:{{
859:13
857:.
834:.
824:.
816:.
771:,
759:15
757:,
744:^
731:,
721:,
704:,
688:^
671::
669:}}
665:{{
627:.
617:.
605:.
582:.
572:.
560:.
542:,
531:^
398:A
51:.
1279:.
1273::
1267:8
1213:.
1191::
1152:.
1127:.
1105::
1086:)
1068:.
1046::
1020:.
995:.
968:.
946::
938::
919:.
905:)
901:(
884:.
869:.
865::
842:.
820::
775::
717::
682:)
678:(
661:.
635:.
613::
590:.
568::
163:)
157:(
152:)
148:(
130:.
101:)
97:(
83:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.