Cloud and Infrastructure the Legacy of Legacy—The Ultimate Drag

Total Page:16

File Type:pdf, Size:1020Kb

Cloud and Infrastructure the Legacy of Legacy—The Ultimate Drag Cloud and infrastructure The legacy of legacy—the ultimate drag on condensing into a cloud About the series services, managing this broad range requires a view Contents on how much can change by when, an appropriate Overview operating model, and a balanced perspective on In order to enable new business and preserve existing what should be developed and controlled, and what About the series value, global Information Technology (IT) executives needs to be monitored and governed. should address the growing dichotomy between the Background agility companies want, and the stability they need. To help equip the IT executive in forming those views This dichotomy is becoming exacerbated as legacy and making those judgements we present points of Some existential threats 2 data centers becomes farther and farther removed view on key trends and topics. from the cloud and from mobile end users. Meanwhile, Determining a new landing platform 3 delivering data to devices and taking advantage of platforms often means giving up some control over Innovating the way 3 Background operating systems, hardware, and data centers. It’s 9 a.m. on Monday. Do you know where your data is? There are aging back office behemoths with little Refresh, transform, or replace 4 source code, no original developers, and growing Introduction operational risks. They are not cloud ready, or even Don’t forget the plumbing 5 As IT executives look to provide value from their IT refresh ready. We consider the legacy of legacy—a portfolios, they are balancing a mix of emerging, material part of the corporate landscape. Not Testing 5 current, and legacy technologies. With the world of confronting it is likely an existential threat. Mission technology ever evolving at pace, the gulf between critical transaction processing engines and back office Conclusion 5 emerging and legacy continues to widen. The systems may be on mainframes, or on large stand- consumer market drives advances in end user devices alone midrange systems with proprietary operating and end user expectations. Many service vendors systems. The hardware, operating, and database invest in cloud, virtualization, and orchestration, while systems may be outdated and unsupported. The manufacturers attempt to deliver more compute application interfaces and data transfer will likely be horsepower at lower cost. Behind the tablets, clouds, built in a way that binds them closely to the technology. and chips, there still sits a data center and a room full of legacy infrastructure waiting for refresh. The code, if available and documented correctly, has programming interfaces that need to be used and This widening gap between end user devices, data are not straightforward to change. The knowledge mobility, cloud services, and back office legacy of the application and interfaces may be in a small systems challenges the IT executive to manage and set of people. Data processing is likely started maintain technology in a complex array of delivery through overnight batch processing, perhaps using capabilities. From mobile apps to mainframe MIPS, customized job, event, and interface handling. and from in-house servers to sourced vendor 1 More than one IT executive has looked at his ageing Staff skills Data damage legacy systems, thought about how to get them Access to skills and institutional memory and Legacy infrastructure and data centres were to x86 virtualized platforms and concluded—“too knowledge fade and reduce as time passes. often built without considering some modern difficult to think about, on to the next problem.” Education, training, and practice largely maintain threats. Electronics and magnetic media are currency with technology trends. So as technology susceptible to electromagnetic phenomena. In this article we discuss how not confronting this ages, so do the skills and resources available to Over time electromagnetic events from solar now can be an existential threat to the enterprise. support it. Skills and knowledge shortages limit the activity are a certainty. Less certain, but no less We also offer some practical approaches for taking ability to get enough of the best people, lowering the threatening, are other sources, natural or manmade, on the legacy of legacy. probability that systems are properly maintained and of electromagnetic pulses. From any source, that incidents and problems are effectively managed. these events threaten electronics, including all Some existential threats This drives up the risk of more serious and sustained IT Infrastructure and magnetic storage media. service disruptions. Sufficiently strong events destroy data. Mitigation techniques are available. Data centers without some The possibility of a digital dark age looms ahead. levels of protection leave open the possibility of Technology advances at pace, and the gap between NASA in shortage of people with sudden and dramatic losses. legacy and emergent technologies grows. Data over time FORTRAN skills becomes unreadable, and then indecipherable as storage NASA requires engineers to communicate and archive media change or become unstable, software with the two Voyager crafts launched in White House preparing for catastrophic and operating systems evolve, and skills become extinct. the 1970’s and are unable to find people solar flares Aging hardware and software ultimately become over- with a skill set that includes command over John P. Holdren, asst. to the president for challenged with the size and performance needs of Fortran and the ability to control a 64KB Science and Technology, and director, Office modern data and interfaces, can no longer be compiled, memory machine. 2 of Science and Technology Policy, admitted patched or supported, and/or eventually hit the set of that solar flares pose a “significant conditions from which they are unable to handle or challenge” to technology. Studies estimate recover, and they fail. For some that archived data and Opportunity costs that such an incident would cause a loss of information is for all intents and purposes lost, as there is Ageing systems can become management and $2.6 trillion in the US alone. 3 no ability to restore it, nor to run software that can use it. money distractions. As support and maintenance increase in complexity, and as costs potentially rise to keep things running safely and securely with the right The passage of time and the evolution of technology The digital dark age skills, focus is distracted from other opportunities. are threats to the ability of ageing information Vint Cerf, one of the fathers of the Internet, When IT Executives and their teams are spending technology to do its job. And in today’s economy that stated that one might soon enter the “digital too much time and money on legacy, they likely job can be no less than the ability of a business to dark age” as old formats of data and documents are not spending enough on other opportunities function. It can be an expensive and difficult path to may not be readable due to unsupported to add value to the business. Lack of business ditch the legacy and maintain technology currency. backward compatibility of devices. 1 enhancements may also drive business lines and Lengthy outages, security failures, or irrecoverable employees to form their own shadow IT. system and data losses will likely cost even more. 2 Information security Determining a new landing But before we look at some aspects of what to look Information security can be an issue for legacy as platform for in refresh, transform, or replace scenarios, we much as for emerging technology. There is likely will consider first ways an organization can build very little that does not interface and exchange momentum behind a legacy program, and strategic Confronting the legacy of legacy will not be easy, data in some way with a more modern system approaches to mitigating legacy risk. nor quick. IT executives should be considering how or end user capability. Perhaps operating on its to confront the estate and what the target landing own, an ageing mainframe system appears more platform or platforms should look like. secure. But as long as there is some manner for it to Innovating the way communicate with and share data or access to other One first step is to develop a target portfolio mix of systems and users, it is a potential vulnerability. Collaborate with the business technologies and platforms. Some business models may Those people that do harm—intentionally or not— Innovating your way out of legacy is about leveraging be suited to high levels of standardization such that there can exploit the most straightforward path, which the entire firm to think creatively about business could be very few, or even one type of target platform is often ageing mid-range systems or desktop processes and needs. It can be tempting to start or service. Others may require a mix of technologies applications no longer capable of being patched or a traditional legacy refresh program by trying to and platforms each optimally suited to their business supported in ways to prevent vulnerabilities being recreate the current system. Stakeholders may be value and competitive advantage. It may be the case that exploited. Legacy technology may not be in front of beholden to the way they do things and the manner certain workloads are best suited to a highly customized mind on this issue, but can be the most vulnerable in which the system in question serves them. So the solution, are optimal on mainframe, or are not best underbelly of your estate. starting position can often be a design exercise that suited to virtualization. In any case determine across the tries to move the existing legacy functionality to an portfolio the best suited target platform(s) and the target upgraded platform, or to replace it with something ratios of how much you want and where you want it. On an average, 4 percent of all the software that does the same thing in a similar way.
Recommended publications
  • Software Evolution Objectives
    Software evolution Objectives To explain why change is inevitable if software systems are to remain useful To discuss software maintenance and maintenance cost factors To describe the processes involved in software evolution To discuss an approach to assessing evolution strategies for legacy systems Topics covered Program evolution dynamics Software maintenance Evolution processes Legacy system evolution Software change Software change is inevitable New requirements emerge when the software is used The business environment changes Errors must be repaired New computers and equipment is added to the system The performance or reliability of the system may have to be improved A key problem for organisations is implementing and managing change to their existing software systems Importance of evolution Organisations have huge investments in their software systems - they are critical business assets To maintain the value of these assets to the business, they must be changed and updated The majority of the software budget in large companies is devoted to evolving existing software rather than developing new software Spiral model of evolution Program evolution dynamics Program evolution dynamics is the study of the processes of system change After major empirical studies, Lehman and Belady proposed that there were a number of ‘laws’ which applied to all systems as they evolved There are sensible observations rather than laws. They are applicable to large systems developed by large organisations. Perhaps less applicable in other cases Lehman’s laws Law Description Continuing change A program that is used in a real-world environment necessarily must change or become progressively less useful in that environment. Increasing complexity As an evolving program changes, its structure tends to become more complex.
    [Show full text]
  • Software Evolution of Legacy Systems a Case Study of Soft-Migration
    Software Evolution of Legacy Systems A Case Study of Soft-migration Andreas Furnweger,¨ Martin Auer and Stefan Biffl Vienna University of Technology, Inst. of Software Technology and Interactive Systems, Vienna, Austria Keywords: Software Evolution, Migration, Legacy Systems. Abstract: Software ages. It does so in relation to surrounding software components: as those are updated and modern- ized, static software becomes evermore outdated relative to them. Such legacy systems are either tried to be kept alive, or they are updated themselves, e.g., by re-factoring or porting—they evolve. Both approaches carry risks as well as maintenance cost profiles. In this paper, we give an overview of software evolution types and drivers; we outline costs and benefits of various evolution approaches; and we present tools and frameworks to facilitate so-called “soft” migration approaches. Finally, we describe a case study of an actual platform migration, along with pitfalls and lessons learned. This paper thus aims to give software practitioners—both resource-allocating managers and choice-weighing engineers—a general framework with which to tackle soft- ware evolution and a specific evolution case study in a frequently-encountered Java-based setup. 1 INTRODUCTION tainability. We look into different aspects of software maintenance and show that the classic meaning of Software development is still a fast-changing environ- maintenance as some final development phase after ment, driven by new and evolving hardware, oper- software delivery is outdated—instead, it is best seen ating systems, frameworks, programming languages, as an ongoing effort. We also discuss program porta- and user interfaces. While this seemingly constant bility with a specific focus on porting source code.
    [Show full text]
  • A Technique for Legacy System Re-Engineering
    International Journal of Management and Applied Science, ISSN: 2394-7926 Volume-2, Issue-12, Special Issue-1, Dec.-2016 INFORMATION SYSTEM INTEGRATION: A TECHNIQUE FOR LEGACY SYSTEM RE-ENGINEERING EMOKPAE OSATOHANMWEN Dept of Computer Engineering, Institute of Opencast Mining and Technology. Agbor Road Benin City, Nigeria. E-mail:[email protected] Abstract - Many organizations are still faced with the problems of converting applications written in legacy compilers such as COBOL, PASCAL ANS FORTRAN etc. into internet compliant applications. This has become necessary because most internet-based applications are written in C++, Java and Ms.Net. The objective of this paper is to show how information system integration can aid in the forward engineering of legacy system. Software re-engineering covers the examination and alteration of legacy system in order to rebuild it according to modem software engineering methods and technologies in a forward engineering process. Information system integration provides a means for both understanding and capturing about the application and its domain and re-developing the system based on change requirement. Information system integration helps to rebuild any legacy by adopting modern software engineering principles, methods and technologies, which allows systems to architecture engineers over the years have devises many modernization techniques. This paper evaluates the use of information system integration as a veritable technique for transformation of legacy system. Keywords - COBOL, PASCAL, FORTRANS, C++,Java Ms.Net etc I. INTRODUCTION streamlining business processes to the software used. There are five levels of integrating information Many organizations are still faced with the problem system, which include data, data management, of converting applications written in Legacy middleware, application and user interface (Bizer, compilers such as COBOL, Pascal and FORTRAN 2003).
    [Show full text]
  • The 2020 Guide to Legacy System Innovation
    The 2020 Guide to Legacy System Innovation Legacy Systems The Keys A New Freedom for 2 APIs 4 6 8 Meet the to Freedom Approach to the Future 21st Century Modernization. The 2020 Guide to Legacy System Innovation Legacy Systems Meet the 21st Century egacy systems running on mainframe computers are at the heart of our economy – and our society. L They are an essential part of our tax systems, our social services, and our public safety. They also run the stock market, our financial institutions, ATMs, transportation systems and utility grids. In fact, we use them all the time and likely don’t even know it. For state and local governments, these legacy systems are a mixed blessing. On the one hand, they have provided extraordinary reliability. They’ve proved themselves with successful track records of 20, 30, or APIs even 40 years. On the other hand, they are rigid, and some would even say fragile, closed and expensive to maintain. Making changes to a legacy system is costly, risky, and prone to failure. Also, legacy systems are by nature siloed systems that keep their data locked inside where it’s safe, but inaccessible. As one senior public sector IT executive put it, “I feel like my data is in jail.” For decades, agencies have been looking for freedom include day-to-day operations, staffing, responding to from legacy systems—a way off of their existing systems. pressure for innovation from elected officials, application Software AG offers a better, stronger alternative: the users and citizens themselves, and complying with Freedom for Legacy solution.
    [Show full text]
  • Impact Analysis of Legacy System Migration to the Cloud Environment: a Focused Study
    ISSN 2278-3091 Volume 9, No.1, January – February 2020 H. SeetharamaTantry et al., International Journal of Advanced Trends in Computer Science and Engineering, 9(1), January – February 2020, 134 – 141 International Journal of Advanced Trends in Computer Science and Engineering Available Online at http://www.warse.org/IJATCSE/static/pdf/file/ijatcse21912020.pdf https://doi.org/10.30534/ijatcse/2020/21912020 Impact Analysis of Legacy System Migration to the Cloud Environment: A Focused Study H. SeetharamaTantry1, Murulidhar N.N2., K. Chandrasekaran3 1 Department of Mathematics & Computational Sciences, National Institute of Technology Karnataka, Surathkal, India, e-mail: [email protected] 2 Department of Mathematics & Computational Sciences, National Institute of Technology Karnataka, Surathkal, India, e-mail: [email protected] 3 Department of Computer Science and Engineering, National Institute of Technology Karnataka, Surathkal, India, e-mail: [email protected] ABSTRACT creating, and recycling the software modules and platforms when expected maintenance follow-ups can never again Although “Legacy System” frameworks are frequently accomplish the ideal framework properties. The essential worked over numerous years by a blend of IT and business point of software modernization [1] is to decrease support specialists. They stay inflexible inside the authoritative cost and increase adaptability. The majority of these setting and business speculation made by practical frameworks were created years back and have kept on applications. Semantic Design provides highly automated advancing. New necessities have repeated changes on these tools and services to migrate legacy system to a new legacy system bringing about unstructured source code that platform. The proposed migration of the legacy software life is hard to keep up.
    [Show full text]
  • Enterprise Application Integration Using Service Oriented Architecture with Generic Pattern
    International Journal of Current Engineering and Technology E-ISSN 2277 – 4106, P-ISSN 2347 - 5161 ® ©2014 INPRESSCO , All Rights Reserved Available at http://inpressco.com/category/ijcet Research Article Enterprise Application Integration using Service Oriented Architecture with Generic Pattern Nilesh Vishwasrao PatilȦ*, M. C. KshirsagarȦ and P. C. JaypalȦ ȦVishwbharati Academy College of Engineering, Ahmednagar, Pune University Accepted 01 Oct 2014, Available online 10 Oct 2014, Vol.4, No.5 (Oct 2014) Abstract Nowadays the computer world is almost migrating from the tightly coupled architecture to loosely coupled architecture directly or indirectly. There are many intentions of Enterprise Application Integration in the organizations to achieved desired functions. The main objective of the Enterprise Application Integration is to implement integration layer between heterogeneous and/or homogeneous systems using Service Oriented Architecture in the direction of achieving the loosely coupled architecture. The integration architecture we have today is very limited and need to improve it as agile as possible. The reusability is not the new thing for software industry; it has been playing the crucial part in the software life cycle development process from last decade. Software industry has achieved the powerful accomplishment in throughput and preeminence because of reusability in software development process instead of creating same thing again and again. In this paper, we will discuss about Enterprise Application Integration using Service Oriented Architecture for achieving loosely coupled architecture directly or indirectly with the help of Web Services or Messaging Queue services. Keywords: SOA: Service Oriented Architecture, WS: Web services, WSDL: Web Service Description/Definition Language, W-SOA: Web Service Oriented Architecture, ESB: Enterprise Service Bus.
    [Show full text]
  • Addressing Software Related Issues on Legacy Systems – a Review
    INTERNATIONAL JOURNAL OF SCIENTIFIC & TECHNOLOGY RESEARCH VOLUME 9, ISSUE 03, MARCH 2020 ISSN 2277-8616 Addressing Software Related Issues On Legacy Systems – A Review Mubashir Ali, Shahzad Hussain, Mahmood Ashraf, Mahnoor Khalid Paracha Abstract: In current technological era, organizations and systems are moving towards automation. Software development always played a sensitive role and software maintenance continually bring challenges for developers. The problem of legacy systems is continuously travels with time. Technologically outdated software or computer systems are known as legacy systems. While software or system development, whatever technique or technology adopted by developers, current developed systems will be the legacy of future. Due to constant advancement in computing, legacy systems are not supporting the technologically updated software. Replacing or updating legacy systems and development of requirement oriented new systems as substitute brings many challenges like budget, time, data movement, training etc. Most of the small level and middle level companies are not able to face these challenges. This paper will conduct an extensive review to highlight the software related issues and their respective solution on legacy systems. The old legacy systems will be used with technologically updated software to fulfill the current requirements. This solution made the scope wider by reusing the available system, refining it with latest features, providing architecture of updated software installation and maintenance that reduce
    [Show full text]
  • Mitigating Cyber Security Risks in Legacy Process Control Systems
    Process Solutions White Paper Mitigating Cyber Security Risks in Legacy Process Control Systems Executive Summary The term “legacy process control system” has different connotations for different people. To many, it refers to proprietary systems from a past era. To others, the term may imply the new generation DCS that have been founded on open technology, or systems using no-longer-supported Microsoft operating systems. These systems have fundamentally different architectures and present different risks. The continuous evolution of the DCS enabled organizations to protect the investment in equipment and control strategies over long periods of time. However, interfacing decades- old controllers with current technology also makes this equipment indirectly vulnerable to attack. All these systems have one common denominator: they experience gaps in support. This makes them more vulnerable than contemporary systems. This white paper will discuss various techniques for protecting legacy systems, the problems surrounding these techniques, and new methods for analyzing security. Mitigating Cyber Security Risks in Legacy Process Control 2 Systems Table of Contents Introduction ..................................................................................................................................................................................................... 3 How to Prevent or Delay a System from Becoming a Legacy System ................................................................................................... 4 Prevention
    [Show full text]
  • Administering Evergreen Through the Command Line Documentation Interest Group Administering Evergreen Through the Command Line Documentation Interest Group
    Administering Evergreen through the Command Line Documentation Interest Group Administering Evergreen through the Command Line Documentation Interest Group Report errors in this documentation using Launchpad. Table of Contents I. Introduction ............................................................................................................................................................. 7 1. About This Documentation ............................................................................................................................... 9 2. About Evergreen ............................................................................................................................................ 10 II. Installing Evergreen ............................................................................................................................................... 11 3. System Requirements ..................................................................................................................................... 14 Server Minimum Requirements .................................................................................................................... 14 Web Client Requirements ........................................................................................................................... 14 Staff Client Requirements ........................................................................................................................... 14 4. Installing the Evergreen server ........................................................................................................................
    [Show full text]
  • Legacy Systems Management Needs Improvement
    TREASUR Y INSPECTOR GENERAL FOR TAX ADMINISTRATION Legacy Systems Management Needs Improvement August 19, 2020 Reference Number: 2020-20-044 [email protected] | www.treasury.gov/tigta | 202-622-6500 This report has cleared the Treasury Inspector General for Tax Administration disclosure review process and information determined to be restricted from public release has been redacted from this document. 1 To report fraud, waste, or abuse, please call us at 1-800-366-4484 HIGHLIGHTS: Legacy Systems Management Needs Improvement Final Audit Report issued on August 19, 2020 Reference Number 2020-20-044 Why TIGTA Did This Audit What TIGTA Found This audit was initiated to assess The IRS has not developed specific or long-term plans to address the IRS’s efforts to identify and updating, replacing, or retiring most of its legacy systems. Through replace its legacy systems. various initiatives, the IRS identified 45 systems for modernization or candidates for modernization and 34 systems for retirement. Impact on Taxpayers While various business units and functions have differing definitions Legacy systems are critical for of a legacy system, the IRS does not have an enterprise-wide many organizations because definition or a complete and accurate inventory of legacy systems. By they support key mission applying the Information Technology organization’s definition of a functionalities. However, they legacy system to the As-Built Architecture (ABA) as of April 29, 2020, can also carry significant risks, TIGTA determined that 288 (43 percent) of the 669 systems in the including increased cybersecurity IRS’s production environment had missing information that prevented threats and maintenance costs.
    [Show full text]
  • Microsoft Windows "Chicago"
    Microsoft Windows ‘‘Chicago’’ Reviewer’s Guide Beta-1 The information discussed in this guide is based on features and functionality present either in the Beta-1 release of Chicago, or planned for a future release. The discussion of Chicago herein, does not represent a commitment on the part of Microsoft for providing or shipping the features and functionality discussed in the final retail product offerings of Chicago. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. Table of Contents INTRODUCTION ....................................................1 Welcome ..................................................................................1 Chicago Mission......................................................................1 Where We’ve Been.................................................................................................1 Where We Are Today.............................................................................................1 Where We’re Headed .............................................................................................2 How We Get There.................................................................................................3 A Quick Preview of Chicago’s Top Features ........................4 Even Easier.............................................................................................................4 Faster and More Powerful ......................................................................................5
    [Show full text]
  • Challenges and Success Factors in the Migration of Legacy Systems to Service Oriented Architecture (SOA)
    School of Technology Department of Computer Science Master Thesis Project 30p, Spring 2014 Challenges and success factors in the migration of legacy systems to Service Oriented Architecture (SOA) By Nataliya Vlizko Supervisor: Annabella Loconsole Examiner: Paul Davidsson Abstract Service-Oriented Architecture (SOA) provides a standards-based conceptual framework for flexible and adaptive systems and has become widely used in the recent years because of it. The number of legacy systems has already been migrated to this platform. As there are still many systems under consideration of such migration, we found it relevant to share the existing experience of SOA migration and highlight challenges that companies meet while adopting SOA. As not all of these migrations were successful, we also look into factors that have influence on the success of SOA projects. The research is based on two methods: a literature review and a survey. The results of the thesis include identification and quantitative analysis of the challenges and success factors of SOA projects. We also compare the survey results for different samples (based on the company industry, work area, size, and respondents experience with SOA and respondents job positions). In total, 13 SOA challenges and 18 SOA success factors were identified, analyzed and discussed in this thesis. Based on the survey results, there are three SOA challenges received the highest importance scores: “Communicating SOA Vision”, “Focus on business perspective, and not only IT perspective” and “SOA Governance”. The highest scored SOA success factor is “Business Process of Company”. While comparing different samples of the survey results, the most obvious differences are identified between the results received from people with development related job positions and people with business related job positions, and the results from companies of different sizes.
    [Show full text]