Le marché Legacy
La maintenance et l'évolution des systèmes existants sont devenus un enjeu majeur pour les entreprises. Refinetm permet de moderniser les patrimoines.Dès qu’une organisation dispose d’un patrimoine logiciel important en production, elle doit s’interroger sur la manière de lutter contre le « vieillissement » de ce patrimoine sous peine de devenir coûteux à maintenir, inflexible et obsolète.
Ces systèmes sont souvent « irremplaçables » car il n’existe pas de progiciel sur étagère qui couvre correctement les fonctionnalités spécifiques au métier de l’entreprise - développées et testées en production sur des dizaines d’années- et les risques de réécriture sont trop élevés. Dès lors l’approche la moins coûteuse, la moins risquée pour ne pas « dilapider » ce précieux héritage reste la modernisation logiciel, c'est-à-dire les techniques d’analyse et de transformation d’un existant. Parce que les patrimoines sont complexes, volumineux, hétérogènes, les moderniser requiert une approche industrielle et adaptable aux environnements, et aux besoins de performance et d’évolution, spécifiques à chaque entreprise.
A Trillion Lines of Code
The mission-critical applications on which major financial, telecommunications, retail, and government agencies depend today have been written over the past 50 years in hundreds of languages with multiple dialects running on multiple platforms. Corporations worldwide have deployed nearly a trillion lines of code into production. Conservative estimates put the number of lines of COBOL in production at over 200 billion.
RefineTM
Languages such as C, Basic, Pascal, Ada, Fortran, PL/I, RPG, and Jovial account for another 200 billion lines. Even “small” programming languages such as NATURAL account for more than 10 billion lines of code supporting enterprise computing. All of this legacy software runs on a variety of platforms including those from IBM, Digital, Unisys, Tandem, NCR, HP, and Sun, as well as on almost-forgotten platforms of such vendors as Burroughs, Control Data, Sperry, Data General, Wang, Datapoint, and Prime.
Definition of Legacy Applications
Legacy systems are a core asset at many organizations. These legacy systems have been around for decades and have a very critical impact on day to day business processes. However, owing to a variety of reasons, these legacy systems have high TCO and represent a bottleneck towards the emergence of an agile IT portfolio.
A legacy system can be defined as "a computer platform or application program that continues to be used because of the prohibitive cost of replacing or redesigning it, despite its poor competitiveness and compatibility with modern equivalents."
These are typically invaluable assets with embedded business logic representing many years of coding, developments, enhancements, and modifications.
Pain Points of Legacy Systems
Legacy Applications are often undocumented, tightly coupled, and relatively closed and inflexible. In most cases they were developed independently without a consistent underlying architecture, resulting in overlapping and redundant functionality and data.
 |
 |
|
The main pain points presented by legacy assets can be summarized as follows:
|
||
 |
 |
The important point to note is that legacy systems satisfy mission-critical operations and have been doing so for most large organizations for a long time. In addition, legacy systems have enjoyed significant investment from the IT organizations.
Existing systems cost too much, leaving too little money for new business projects.
The total cost of keeping existing applications enhanced, up to date, and running consumes a disproportionate share of the budget. Forrester’s research shows that:
- North American and European enterprises spend 75% of their software budgets on ongoing operations and maintenance, leaving just 25% for new investments.
- That is not enough funding for projects that can increase revenue and leverage new business opportunities.
The burden of maintaining and extending legacy systems that are increasingly cut off from current technology and best practices compels the need for a planned and phased modernization of legacy systems associated with the industrialization of the maintenance and test activities.
The Legacy alternatives
The legacy alternatives:
- Do nothing and leaves it as is which means that the technology obsolescence and code entropy of recurring maintenance increase the cost of maintenance, operation and ownership.
- Rewrite all of the legacy applications and migrating data involves high cost and enormous complications as demonstrated by numerous failures of such projects.
- Replace the legacy apps with software package when available. For example, large groups of internally written financial, manufacturing, and human resources applications have been replaced with packaged application solutions from vendors like Cullinet Software, McCormack & Dodge, and other vendors that no longer exist — in part, a testament to the failure of rip and replace.
- Modernize the legacy application.
The modernization imperative
Today the business practices of corporations are locked in the software that runs both the online transaction processing systems and decision support systems. The software or code base represents the intellectual property of these corporations. People come and go, but the business practices of the corporation are codified in its software. These business rules are the lifeblood of the corporation, and transformation of the corporation hinges on the ability to modernize the software that codifies these business rules to more modern environments.
