Integration for Legacy Data Systems Term Paper

  • Length: 8 pages
  • Subject: Business
  • Type: Term Paper
  • Paper: #39784527

Excerpt from Term Paper :

(E-Legacy: Legacy EAI for B2B Integration)

To present an idea of the significance of legacy software, it has been projected that in excess of 200 billion lines of COBOL code are present and this software application processes 70% of the global business data with 30 billion COBOL-based business dealings are carried out every day. Evidently these are extremely worthy assets to leverage. (Legacy Integration: Something Old, Something New: Integrating Legacy Systems) Think as a company business executive, looking at your product-line placing orders for backlog, your production schedules as against the product categories, your stock of goods as against your production schedules, and your inventory refill with the deficiency which was shown conspicuously. This is the objective of a totally integrated e-Legacy business. (E-Legacy: Legacy EAI for B2B Integration)

Legacy systems store a huge amount of important business information, together with details of the customer; hence it is indispensable in case of companies to be capable of opening this data rapidly and without difficulty. Employing the correct strategy and software, this information can be integrated with recent applications, facilitating an enterprise to create its business for the future making the expenses on new it infrastructure needless. A research undertaken presently realizes the continued significance of legacy systems intended for UK organizations, particularly in drawing and preventing customers from shifting loyalty in favor of other companies. The survey in its findings stated that 86% of the UK companies hold legacy systems as significant to customer service delivery, whereas more than two-thirds hold the importance of integrating legacy systems with customer service applications. Any business strategy which entails evasion of legacy systems is possibly detrimental to the relationship of a company with its customers and its all-round standing. (86% of UK Companies Regard to Legacy Systems as critical to customer service delivery: Survey Highlights Ongoing Importance of Legacy Systems for UK Industry)

Limitations of Legacy-system:

With the motivation for Business-to-Business -- B2B Internet suitability, legacy applications are frequently made responsible for roadblock in attaining a genuine 24/7 international web-enabled enterprise. (E-Legacy: Legacy EAI for B2B Integration) the expenses of managing a legacy information system can go up to millions of pound annually. Brodie and Stonebraker assert that the upkeep of a legacy system can make 80% of the total it budget, and can frequently be more than 90%. Expenses of this sort can stall the enterprise from building applications that take the benefit of recent technology. Bisbal et al. apply this facet of cost to outline a legacy system portraying it as a software system that cannot be sustained by adequate resources. Bisbal et al. portray legacy system as 'fragile, rigid, inaccessible and possess lack of scalability and absence of ingenuousness'. (Legacy information systems) the difficulties connected with the age of a system can be explained more proximally and have broader connotation compared to what we have witnessed till date. The period of a legacy system frequently ascertains the framework of the code and the intricacy of creating what is performs. (Legacy information systems)

Due to the absence of documentation, the maintenance programmers are left with just the code to help in the understanding the system, and this is the same code the developers must look forward so as to set up what the current system performs. Reverse engineering, the process by which the present system is once again documented from the code is opportune and expensive. Besides, suitably experienced personnel are difficult to locate. Software programmers skilled in the earlier assembly, second and third generation codes, might have moved up to latest software systems. Those who possess the required proficiencies are frequently unwilling to leave their hands from the projects that are employing latest technology. The supply and demand scenario of adequately skilled programmers generally implies such programmers are hard to hire and very costly to engage them. Slee and Slovin debate that perceiving the program can consume up to 50% of the maintenance time. The explanation for modification becomes simpler when the share of maintenance attains a whopping 95% of the it budget, and 50% of the maintenance time is devoted to just to gather knowledge about the system. (Legacy information systems)

Legacy data systems in Business:

In a huge organization, legacy systems are constituted of tens of millions lines of programming code which possesses a replacement worth in the region of billions of dollars. These application systems are indispensable to the long-term functioning of multifaceted businesses throughout the globe. Majority of these companies are even aggressively developing new, Web-based systems to support e-business projects. These projects are strategic, but yet need access to legacy data and transaction-based systems. These new systems require to access legacy settings to leverage the intelligence entrenched in these past systems. Nearly every company tackles the e-business and legacy systems integration by the use of some application integration instruments to access legacy data in a selective manner or activate back-end business dealings. These instruments tackle integration through the application of after-the-fact solutions which successfully differentiate recent systems from legacy settings for the long-term. This procedure presents restricted flexibility and impedes long-term, extensive up gradation alternatives to recent e-business systems and back-end settings. (Aligning Strategic Systems with Legacy Environments) greater efficient procedure for integrating strategic and legacy settings is to deal with this confrontation at the time of design and development chain. Recent systems leverage reclaimed constituents to restructure development and potential upgrade responsibilities. Reusable component libraries are conventionally supplied by the sellers or built by Java programmers. Legacy systems, on the contrary, are a valuable unexploited repository of business codes which can be subdivided into components and used again as a part of the development procedure. Componentization of legacy systems needs breaking down systems into important operations and sub-operations and deriving and unification of chosen business policies from those systems. The subsequent move involves classification of those derived components for reusing and composing them to enable them for availability to the development and maintenance groups. Whereas this process is not an easy task, software tools and systems have developed to a stage where legacy componentization is practicable and with the help of commercially accessible technology. The advantages of this are important. Rebuilding the business policies comprised within the legacy systems will cost some companies greater than their net reasonable market valuation.

Many debate that legacy business policies are not applicable to recent e-business needs. As against this, back-end systems have majority of the business logic required to facilitate increased volume, e-business dealings which are scalable. Legacy designs strictly are not compatible with cross-functional access to stovepipe data and transaction-based settings. Componentization will help in revolutionizing this dynamic through reassembling legacy astuteness such that new systems will be capable of reusing legacy logic to fulfill strategic e-business needs. Development endeavors can fulfill fresh development needs more rapidly and more efficiently by adding legacy components. This is better than trying to repeat years of entrenched legacy business logic from the very beginning. It managers must facilitate developers to deal with new development and legacy systems integration under an exclusive strategy that completely blends integration into the systems design and development life cycle. Any shortfall in this accord shelves the future of e-business solutions in leading enterprises. (Aligning Strategic Systems with Legacy Environments)

Guidelines for legacy-system integration:

After understanding the limitations, we have to be careful in adopting correct techniques for legal system integration. As understood earlier, since expenses are a major issue- it is costly to integrate and keep legacy systems functioning. In case a legacy system is inadequately made from the initial stages, at times it is risking good money to follow bad to keep them functional. You must realize the expenses of creating a new system from the very beginning, retooling the complete operation as well, in case you prefer not to maintain the legacy settings. Chief Information Officers - CIOs must think about the continuing feasibility of a legacy system prior to expending funds to integrate the same. Several types of integration are present, and these are available at different price segments. Real-time integration, for instance, which modifies and upgrades the information right through integrated systems the moment the modification is done, is the most intricate and thus the most costly. However, there are other points of integration which are not so expensive, even though they are not so exhaustive.

The intensities of integration must be propelled by the requirements of the business. The key is to match the integration category to the specific business requirement, which highlights the project. 'Prepare a business argument before anything else,' stated Andrew Efststhiou, program manager with the technology management strategy group of Yankee Group, a research company headquartered in Boston. "The moment you accomplish that, you can begin originating a solution that makes clear the various components and what nature of integration the business argument…

Cite This Term Paper:

"Integration For Legacy Data Systems" (2005, April 17) Retrieved February 10, 2017, from

"Integration For Legacy Data Systems" 17 April 2005. Web.10 February. 2017. <>

"Integration For Legacy Data Systems", 17 April 2005, Accessed.10 February. 2017,