DOCSLIB.ORG

The IULS Approach to Software Wrapper Technology for Upgrading Legacy Systems Dr

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The IULS Approach to Software Wrapper Technology for Upgrading Legacy Systems Dr The IULS Approach to Software Wrapper Technology for Upgrading Legacy Systems Dr. David Corman The Boeing Company This article describes using software wrappers in Incremental Upgrade of Legacy Systems as a key technology for mod- ernizing legacy systems. It introduces three types of wrappers, describes a process for selecting which upgrade path to utilize, and discusses a tool-set developed by The Boeing Company for the Air Force that automatically generates wrap- pers. Lastly, it discusses real-world avionics upgrade examples where the tool-set has been applied and its effectiveness. vionics upgrades are frequent and environment (its context). The wrapped is to develop, demonstrate, and transition Aoccur for many reasons, including component becomes a software object. Its software wrapper technology that will warfighting enhancements, countering operational capability (functions and enable cost effective, incremental changing threats, hardware obsolescence, data) is encapsulated, and it can be inte- improvements to fielded weapon system and computer resource under-capacity. A grated through its standard interface with avionics. The products of IULS are: 1) typical production avionics upgrade cycle other software objects to form an opera- methodology for analyzing software for military aircraft frequently involves tional flight program (OFP) on a single or upgrade approach, 2) wrapper technology, embedded software changes. New ver- distributed processor host. The wrapper 3) tool-set for constructing wrappers for sions of mission processor software, the manages the timeliness of all shared and software upgrades, and 4) demonstrations most volatile class of avionics software, are external data, and provides any necessary of IULS wrapper technology applied to typically released annually and take two transformations. three significantly challenging problems: years to field from initial definition. For upgrades, the goal is to develop F-15E, C-17, and CV-22 avionics. Hardware obsolescence occurs collec- the new or reengineered applications IULS is funded by the Air Force tively over a longer term as vendors using the latest software engineering tech- Research Laboratory, Embedded change their business (military/commer- niques such as OO design and languages Information Systems Engineering Branch cial mix) and technology. Software tools (Ada and C++) with minimal concessions (AFRL)/(IFTA). Participants in the proj- and technology also evolve over a longer to the internal structure of the legacy sys- ect include The Boeing Company, period but may be driven by short-term tem. It is developed as if all other applica- Honeywell Technology Center, General events such as the introduction and impo- tions were resident in the new environ- Dynamics Information Systems, and sition of Ada. The change cycles are not ment. Because the new software is written TRW-Dayton. synchronized so the optimal hardware, within the paradigms of OO design and software and tool technology, and respec- languages, the wrapper can eventually be Software Wrapper Technologies tive program funding to support an removed once all of the application func- Figure 1 illustrates three hypothetical cases of implementing software changes using avionics upgrade at a given point in time tions have migrated to the new system. At wrappers. are often not available. this time, the legacy system can also be The problem of cost-effectively removed. upgrading legacy systems can be mitigat- The Incremental Upgrade of Legacy Re-Host In the case, the legacy processor is ed through reengineering with the latest Systems (IULS) program is a research and re-host obsolete and/or its resources are insuffi- generation hardware and architectural development effort, whose main objective concepts, including object-oriented (OO) software design, which inherently con- Figure 1: Wrapper Cases tains and isolates change. However, legacy Re-host Sync avionics software represents a large invest- Legacy Source Rehosted Executable Re-hosted Upgrade Executable ...1100110001110101 Processor ment in development tools, executable [Translate] In ...110011000111010 Out 010101010101010010 1010101010101010 code, and ground and flight qualification. 111010010011010001 0101110100100110 Compile 1100111001010010... 100010101001010... Should the upgrade require complete reengineering of this legacy software, Put Get much of this investment is lost; many air- craft programs simply cannot afford the Hybrid Sync up-front costs associated with reengineer- Legacy Executable Legacy Upgrade Processor ...110011000111010 Processor ...11001100011101 In ing and complete re-qualification. 0101010101010101 1010101010101010 Out 0101110100100110 0010111010010011 100010101001010... One solution to this dilemma is 01000101010010... implementing reengineering incremental- ly by inserting the latest technology in Put Get smaller, affordable steps, thereby reducing Emulate ISA Emulator Sync risk and deferring or reducing cost. Legacy Executable Fetch Legacy Upgrade Executable Software wrapper technologies hold par- Decode Processor ...11001100011101 ...110011000111010 In 0101010101010101 1010101010101010 Out I/O ? ticular promise in meeting this challenge. 0101110100100110 0010111010010011 100010101001010... 01000101010010... A wrapper is a software adapter or Emulate ISA Emulator ? Branch shell that isolates a software component Put Get from other components and its processing December 2001 www.stsc.hill.af.mil 9 Software Legacy Systems process and the data that flows between them. Wrapper Implementation Considerations Wrappers are generally applied at the application domain level. They act as clients and servers to the encapsulated component. Figure 3 illustrates a general wrapper structure for an OFP on a single processor. The legacy application inter- faces with other applications and other layers only through the wrapper. The wrapper architecture is tailored to the spe- cific legacy OFP environment. The method selected to implement the upgrade of a legacy system is to an extent an economic decision. The emulation option will tend to favor a context of a sta- ble application, infrequent OFP modifica- tion, and obsolete hardware. These cases Figure 2: Nominal Legacy Operational Flight Program Wrapper Process will generally be lower in performance, cient to support additional upgrades. The wrapper components. As components in being older systems. Therefore, the con- legacy software is re-hosted to a new the legacy OFP require changes, they can text analysis would focus on issues of processor by translating its source code be reengineered and moved to the new throughput, OFP stability, parts obsoles- (e.g., Ada 83 to C++) and/or recompiling processor. At some point in the migration, cence, OFP utility, etc. it for the new target (e.g., Ada 83 to Ada the remaining legacy components are re- Selecting a hybrid or re-host approach 95). Reengineering the OFP on the new hosted, the legacy processor is upgraded would generally be appropriate for a more processor could not be justified so wrap- or discarded, and the wrapper compo- dynamic and/or higher performance sys- per components are added to make it look nents in the new OFP, associated with the tem. Typical context would be OFPs that like an object in the OFP. New software legacy OFP interfaces, can be removed. are subject to periodic update and version features can be added incrementally to the release. In addition, the higher the wrapped component, or preferably, Emulate throughput needed, the more likely the designed as new objects in the OFP. Obsolete or underpowered hardware is upgrade path will not include emulation. also addressed in the emulate case. The The reason for this analysis factor is that Hybrid legacy software is judged to be very costly while software emulation provides a growth In the hybrid case, the legacy processor to reengineer and/or re-qualify. The path for the legacy upgrade, there is a and its OFP are retained for various rea- object code is executed on the new proces- penalty paid for using processing resource sons (high reengineering or logistics costs, sor by an emulation of the legacy proces- overhead. A hardware emulator approach etc.), but its resources are insufficient to sor’s instruction set architecture. will, with time, become a technology support additional upgrades. Also, there is Changes can still be made to the lega- dead-end (as would be the case for the an opportunity to satisfy upgrade require- cy executable using the legacy compiler legacy system) and require more near term ments with reuse library components that and software engineering environment. upgrade effort. are developed with more modern lan- The emulator and other wrapper compo- Any selected legacy upgrade technique guages (such as Ada 95 or C++) and tools. nents make the legacy executable compo- will, of course, be subject to obsolescence New features can be added incremen- nent (binary) look like an object. Other and eventual upgrading. Therefore, the tally to the upgrade OFP as objects on a feature upgrades could be added as new methods described for the upgrade process new processor. The objects will be bridged objects on the new processor. and wrapper generation emphasize as flexi- to the legacy OFP and processor with ble an approach as possible. Also, the Wrapping Process methods need to be portable between Figure 3: Wrapper Software Structure As with any other software development hardware platforms since these compo- activity, wrapper creation follows a nents will
Load more

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]