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