Power Builder to Java Migration - Tools based - Arkin Software

ARKIN SOFTWARE TECHNOLOGIESARKIN SOFTWARE TECHNOLOGIES

Timely | Reliable | ResponsiveUSA India Peru Colombia

Arkin Software TechnologiesLegacy Modernization Enterprise Mobility Automated Testing

[email protected]

Power Builder-> Java Migration


Mission-critical Custom Solutions

Delivering enterprise IT solutions for over a decade.

Frameworks & Automated Tools

Operating from US, Peru, and India

Clients in 11 countries

CMMi Level 3 Appraised & ISO 9001:2008 certified

Legacy ModernizationMatureQuality Standards

Product Engineering Solutions

Services for entire Product life cycle

Web, mobile, SaaS architecture

Pre-sales and Post-sales support

Capital Markets Solutions Depository & Settlement platform

Securities trading platform

Covers all securities and FOREX

Power Builder

Oracle Forms

Visual Basic

ProC

Informix 4GL

Unibasic/Unidata

Legacy Java

All 4GL systems

Mobile Enablement; Mobility Employee/client/partner facing apps.

ERP / Legacy / Web apps integration

Advanced Security & Single Code Base

Cloud Enablement IaaS – Amazon, Rackspace, Azure

PaaS – Amazon, Salesforce

Testing Automation Services Test automation

Flexible deployment model

Full range portfolio for testing servicesPartnership Approach

Outcome Based

Pricing

Experienced Team

Arkin @ a glance

Robust Frameworks &Tool based Process

Automation

[email protected]


More than50 Million Lines

of Java code

in Production

Proven Results

Rich Experience. Proven Credentials.

[email protected]


Legacy Systems Migration – A Business Imperative

• Technology obsolescence / End of support announcements– In reality, its end of technology, with/with-out official EoS

• Dwindling availability of skilled resources, for continued changes to the application– Present availability ratio is less than 1:100; – projected to get even worse - No new inflow; Retiring workforce

• Very high cost of legacy application maintenance / High TCO– Vintage cars is an expensive hobby.

• Incompatibility for the evolving landscape– Cloud– Mobile

• Adoption of Open Source Software– Low TCO– Large development/support community and efficient frameworks

[email protected]


Arkin’s Legacy Migration Framework

[email protected]


Client Server Technologies - Arkin’s Conversion Approach

100% retirement of legacy

Legacy codebase as SRS

Quick time-to-market

Accelerators for manual work

100% Test automation

Same or new GUI, as needed

Better Performance

Improved Scalability

Easy Maintainability

All Java

No proprietary code

IS09126 Code Quality

Fits into new landscape reg/:

Reports : Jasper/iText/

Pentaho/Any Other

Identity management

SOA backbone


Arkin’s Database Migration Framework

[email protected]


More to it than Automation Tools

Almost Never a 1:1 Migration Architectural differences between Legacy and Java CUI Differences – Function keys Restructuring of Code Performance bottlenecks

Inefficient Code in Legacy SQL code in the client side Pure business validations in procedures Not following OOAD principles Bottlenecks in code Dead Code/ Unused Code

Implementation of New Features Security features (coding security: Spring IOC) New or modified functionalities

Legacy Concepts Do Not Always Map Linear Programming Character User Interface Implicit Functionalities

Legacy Issues Tight coupling between UI & Business Logic Poor coding practices Little or no documentation

Legacy Migration is:

About retaining and extending the value of your mission critical application(s) Enable business processes to gain significantly from new technologies

[email protected]


Tools Driven. Factory Approach.

Phase Name of Arkin Tool

Assessment & Planning

Analyzer

Code Migration GUI Converter

Code Converter

DAO Converter

Traceability Generator

Database Migration Database MigrationSchema / Data

Views / SP’s/Functions

Reports

Process related Name of other Tools

Architecture Validation Selenium, JMeter

Load Testing Oracle Load Tester / Selenium

Performance analysis JProfiler

Functionality Testing Oracle Tester, Selenium

Code Coverage Clover

Code Quality Sonar

Unit Testing JUnit

Continuous Integration Jenkins, Maven, RunDeck

Regression testing Selenium

Source Code Control SVN

Defect Tracking [web] Mantis

Audio-Video Communications

Skype / GoTo Meeting

[email protected]


Migration Approach

The three-phased approach clearly separates the three elements of the migration – Planning, Migration and Testing & Deployment. The tool migration

[email protected]


Project Artifacts

Activity (Phase) Deliverables

Analysis & Planning Statement of Work (SOW)Detailed Project Plan

Architecture Validation Arch Validation Document

All deliverables, given below

For Each Migration Release Test Cases

Test Automation Scripts

Test Report

Tested Source Code

Code quality report

Performance profile report

Test coverage report

Code documentation

Build Release Notes

Installation and Deployment Document

[email protected]


Thank You

[email protected]


How to go about?• Perform Application Portfolio Analysis - bi-furcated by each application

– Establish complete

• inventory of legacy applications of both online & batch programs

• Application flow including of dependencies

– Identify all external integrations

• Database based / Flat file based / Message Brokers etc

– Perform Application Assessment• Generate code metrics

• Perform run-time analysis

• Establish usage metrics

– Discuss migration objectives and Technology Choices

• Establish the dependency flow

– From lowest / independent application to highest dependent application

– Pickup the least dependent application as pilot

• Migration Choice[s]

– Independent applications Migrate code and DB and deploy into production

– Dependent applications • Migrate code first, keep DB as is and deploy into production

• After all applications are moved into production then migrate the DB to Oracle

[email protected]


Summary & Next Steps

Activities Prospect Arkin

1 Non Disclosure Agreement _/

2 Provide access to running legacy application source code, Datastore

metadata

_/

3 Provide demo of the legacy application showing different complexities ,

mainly related to User Interface, Transaction processing, any special

requirements

_/

4 Address any queries related to the legacy application ; i.e. related to

access to source code, datastore, sample test data etc for static analysis

/ dynamic analysis of code

_/

5 Provide the Migration expectations & technologies choices _/

6 Perform static & dynamic analysis of code _/

7 Address any queries related to code, migration expectations /

technology choices

_/

8 Perform walk-thru of Statement Of Work and Address any clarifications _/

9 Submit SOW both Technical & Commercial and address any clarifications _/

10 SOW Approval / sign off to move forward with migration _/

[email protected]

Power Builder to Java Migration - Tools based - Arkin Software

Software

Transcript of Power Builder to Java Migration - Tools based - Arkin Software