Arkin Software offers complete migration solution to retire Power Builder Applications. It is a tools based migration framework- comprising of a automated tools; migration methodology; and experienced consultants that facilitate factory-like precision.
There are three Converter tools.
(a) GUI converter converts legacy GUI into web-structure, RIA technologies or thin-client GUI, with similar look & feel.
(b) Code converter converts business logic of the legacy code into equivalent java.
(c) DAO converter converts SQL calls into a chosen persistent framework like SPRING JDBC or JDBC.
Besides these, there are two extremely important tools.
(d) Analyzer: It is this tool that helps us even if there is limited or non-existent documentation and application knowledge. This tool dives through legacy code, builds metrics and relationships to help our team to size and understand the legacy complexity and accurately estimate the migration effort.
(e) Traceability Generator: It maps legacy code to converted java code in a spreadsheet format. This traceability matrix serves two purposes: One is to ensure that no legacy code is missed out during conversion; and the other is to facilitate client’s internal teams to catch up with migrated Java code.
Arkin Software’s unique approach to migration is architecture-centric. That means, we start with the target architecture and migrate the legacy to that target. Never one-to-one migration. Because, migrated applications must live in production for another 20-25 years, which is possible only if they are built on right architecture. Nobody likes applications that may look like Java, but stink like legacy.
Arkin Software offers tools based approach to convert 2-tier client/server applications to 3-tier or multi-tier Java based web architecture. The legacy client/server is a 2-tier application. Business logic and data access is partly coded on the UI side, and partly in the form of stored procedures running on database server. During migration, the code is segregated into different layers like - UI, Business logic, Communication, and DAO layers. The database system can remain the same, or that can also be migrated to a different one. If you prefer to have similar GUI after migration, it is possible, as it minimizes end-user re-training. If you prefer to have adaptive RIA UI to work on multiple form-factor devices, that is possible too.
4. ARKIN SOFTWARE
TECHNOLOGIES
ARKIN SOFTWARE
TECHNOLOGIES
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
info@arkinsoftware.com
8. ARKIN SOFTWARE
TECHNOLOGIES
ARKIN SOFTWARE
TECHNOLOGIES
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
info@arkinsoftware.com
9. ARKIN SOFTWARE
TECHNOLOGIES
ARKIN SOFTWARE
TECHNOLOGIES
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 Migration
Schema / 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
info@arkinsoftware.com
13. ARKIN SOFTWARE
TECHNOLOGIES
ARKIN SOFTWARE
TECHNOLOGIES
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
info@arkinsoftware.com
14. ARKIN SOFTWARE
TECHNOLOGIES
ARKIN SOFTWARE
TECHNOLOGIES
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 _/
info@arkinsoftware.com
