CBDI Forum
CBDI Service Oriented Architecture Practice Portal
Independent Guidance for Service Architecture and Engineering
Search:

eLearning

Report Summary
Title: Patterns for Legacy
Author: Richard Veryard
Publication Date: 1 February 2001
Report Type:
Abstract: Many difficulties remain with legacy systems; but there is little willingness now to spend any more time and money improving them, unless there is a strong and immediate business reason for doing so. Understandably, most of the business attention is devoted to new business requirements, and the funding is going into development projects to satisfy these requirements. Of course, behind the scenes, most of these projects involve some kind of link with legacy systems. Without proper coordination, and without an overall view of the IT systems, each of these projects could further worsen the situation, making legacy systems more complicated, proliferating clones and variations, and increasing the tangle of interconnections. However, with good management, we might start to see legacy systems being progressively cleaned up and improved, as each project establishes robust and reusable interfaces into well-wrapped parts of the legacy, and new functionality is added to the legacy systems pragmatically, in accordance with CBD guidelines and patterns.
Report Access Type:
  Silver/Gold (Premium)
Available for separate purchase Single copies of recent CBDI Journals may be purchased
Login
Username: 
Password: 
 
   
Please note that by proceeding you are providing the CBDi Forum with approval to use cookies. Please also ensure that you have cookies enabled in your browser.
 

  © Everware-CBDI Inc 1999-2008