REPLACEMENT TECHNOLOGY PRACTICE

Reuse and Extend ROI of your Legacy Enterprise Application

Today, many companies are looking for ways to reduce costs and improve the accessibility of legacy applications. As new technologies and applications arise, old ones become obsolete. As a result, valuable information assets become trapped. The challenge is to get the existing content into new environment in a fast, cost-effective and preferably without losing data quality and integrity.

Legacy modernization is a great opportunity to align business processes more closely with new IT capabilities. A legacy migration aims to retain the value of the legacy asset on the new platform. This practice can take several forms. For example, it might involve translation of the source code, re-architecting the existing platform or some level of re-use of existing code plus a web-to-host capability to provide the customer access.

“International Data Corp. estimates that 200 billion lines of legacy code are still in use today on more than 10,000 large mainframe sites. The difficulty in accessing legacy applications is reflected in a December 2001 study by the Hurwitz Group that found only 10% of enterprises have fully integrated their most mission-critical business processes”

When does an Application become a Legacy Application?

• Joe Celko, IT Writer

"People associate the term legacy with big iron and Big Blue, but the phrase is increasingly being used to include any and every application in existence before the birth of the web."

Replacement Technology

Replacement technology refers to the migrating or porting of a legacy system to a modern programming language or software. They are also referred to as software/database migration with the objective to retain and extend the value of the legacy investment through migration to new platforms .

ZSL’s PowerMigrator™ - A Tool & Process based Migration/Approach

We help global companies to become more agile and responsive through our legacy modernization and special migration solutions. We offer specialized solutions for migrating applications from old systems to the latest platforms and architectures. We provide end-to-end migration solutions that are backed by in-depth expertise with a proven track record with years of experience.

We provide specialized services in migrating applications from PowerBuilder, FoxPro etc., to Web (.NET/ J2EE) application. We pride ourselves in migrating different types of application to a common platform where all the business logic is extracted and deployed as components, which can be accessed using any standard front end. This approach makes code assets turn out to be the foundation to build new composite application developments.

Re-implementing applications on new platforms can reduce operational costs, and the additional capabilities of new technologies can provide access to valuable functions such as Web Access to the client. Once migration is complete, the applications can be aligned more closely to the current and future business needs through the addition of new functionality to the migrated application.

The Benefits of ZSL Migration Services :

• Reusability of legacy application assets

• Faster turnaround-time

• User friendliness

• Low cost solution

• Quality and Timely delivery

ZSL Migration - 7 Steps Approach

Our PowerMigrator™ tool executes the migration process by implementing the following easy steps:

Step 1 : Automatic Effort Estimation

Estimating the effort & time required to migrate the application to new platform, using PowerMigrator™ Object and Code analyzer.

Step 2 : Gathering requirements & assessing

Analyzing the source code, application mining to extract business rules and create a high-level document about the application functionalities and work flow.

Step 3 : Preparing / making it ready for migration

Upgrade the code to appropriate version and check for missing code / objects.

Step 4: Migration

Generating Forms

By using PowerMigrator™, we generate front-end forms (HTML/ DHTML/ ASP.NET/ JSP etc.), that produces the same look and feel of the original Client/Server application, it can also be extended for additional functionalities.

Mapping events and codes

With the help of PowerMigrator™ tool, user object events can be mapped to a business logic component (ASP.NET/ VB.NET/ C#.NET) and all codes can be sliced and restructured into presentation, persistent data and business logic.

Step 5: Adding New functionalities

We incorporate new functionalities to meet specific business needs, not met by the legacy applications.

Step 6: Testing

We create suitable test scripts for the migrated application, once the testing process is over; the application will be deployed in the respective environment for Customer Acceptance Testing.

Step 7: Post Migration Support

This includes Version control and tracking changes, implementing new enhancements etc.