Over the years various organizations have spent huge amount of funds and have invested a lot of knowledge in building applications.
These legacy applications have evolved over many years with day-to-day business processes tightly intigrated with in them containing a lot of knowledge and data.
But with the advent of internet and collapsing of boundaries, these legacy systems have become huge bottle necks for companies looking to expand over the internet and take their business processes to a higher level.
Several companies want to leverage the power of the internet but do not wish scrapt the legacy and start from scratch as the legacy application as it is reliable, built as per organizational processes and needs.
If it has to be built from scratch then it would require a huge timeframe and cost.
The best way to tackle this bottleneck is to web enable the legacy application, as it would be "fast to market" since the new system is based on existing legacy business logic.
Shorter "time to market" and "reuse" of existing logic means lower costs to the company where reliability and processes remain intact.
The Web-Enabling Process
Legacy Software Assessment
This step consists of identifying the individual processes and components that will be web enabled. Assessment of each process and component is essential in development of the protal.
GAP Analysis and Architecture
After the processes and components have been identified for web enabling; the next step is to identify gaps between what is available in legacy application versus what needs to be achieved in the web enabled portal.
The GAP Analysis will provide the base for what needs to be built a fresh along with reusing old business logic.
Developing Bridging Components
Bridging Components are peices of code which enable communication between the web components and the existing legacy components.
Introduction of Web Portal
Web Portal is built which accesses its own business logic along with the Bridging components to seamlessly web enable the legacy application.
