Introduction

To
Zylog Systems Limited (ZSL)
&
Legacy Application Modernization

www.zsl.com
Core Competency / Services

www.zsl.com
 Zylog - Evolution

2008 - 2010
4 companies acquired
2009-10
2008-9
$219m
$151m Turnover
Turnover
2007-8
$153m Turnover

2006-7
$93m Turnover
2007
2004 Zylog IPO through
Zylog Europe BSE/NSE Zylog - Growing,
incorporated
Profitable,
1996
Opened ODC – Chennai well-managed medium
Opened USA office sized software
business.

www.zsl.com
 Corporate Information
Incorporated as Public Limited Company (June 1995).
Turnover $200m+ (2010), Operating profit 19% of total revenue

3000+ Developers (Java, C#, OpenSource)

www.zsl.com
Partial Customer List

www.zsl.com
Example Vertical Market - Telecoms

www.zsl.com
 Technology Stack Partners

Microsoft

Oracle

IBM

300+ Software Developer Certifications

www.zsl.com
Main Development Centre

75,000 sq ft, approx 750 Developers

www.zsl.com
 Main Development Centre
Floors 2 and 3, each with 250 – 275 Production staff + support staff & Facilities

www.zsl.com
Legacy Application Modernization Department

www.zsl.com
Meeting Rooms

www.zsl.com
Modernization Practice Data Centre

www.zsl.com
Core Competency / Services

www.zsl.com
Business Problems
Business agility is restricted by
software systems

Software progress reduced by

complexity

Business has to continue while

improvements are made

www.zsl.com
Modernization Drivers
Business Opportunity

Obsolescence

Skills Shortage

Cost Reduction

Wider Access

Architecture Alignment

Integration with other services

www.zsl.com
Application Options

www.zsl.com
The problems with COTS Packages
Highly Invasive to Av ERP system costs
business operation £0.5m to licence

Highly invasive to IT Av ERP system costs £0.5

procedures to implement

Causes organizations
Av ERP system costs £5m
to /bend’ to suit the to maintain over its lifetime
package

Benefits lower than Benefits lower than

expected expected

Costs higher than Future flexibility is limited

expected by the ERP vendor

www.zsl.com
Cornell University and Cutter Survey - 2006
98% of customers forced to change business
processes

COTS packages fully implemented only 28% of times

81% of companies reported using a great deal of effort

using COTS application with existing data

77% of companies reported using a great deal of effort

integrating a COTS application with other applications

61% of companies reported preferring the custom

legacy application to the new COTS application

Only 18% of respondents said it had been easy to

realize benefits from the COTS application

www.zsl.com
 Modernization Options
Option Category Characteristics Cost/Time
1. Manual Re-write • Expensive • High Cost
• Time-Consuming • Long Duration
• Risky
• Quality, Native Solution
2. Modernization • Protects investment in • Moderate Cost
(Semi-Automatic) business logic • Moderate Time
• 30%-40% of Manual • Low Maintenance cost
Cost & Duration
• Quality, Native Solution
• Moderate Risk
• Re-Architected
• Modernized
• Enhanced
• Future-Proof solution
3. Automated Code • No Re-Architecture (4GL • Low Migration cost
Conversion C/S to C/S Java/.NET) • High Maintenance cost
• Poor Scalability
• Poor Integration

www.zsl.com
Modernization Benefits
Business Opportunity

Protect existing investment

Mitigate Risk

Minimize Business Disruption

Minimize IT Dept Disruption

www.zsl.com
Manual v Automatic Migration Metrics
Developer Cost £400 per Developer Cost $400
day per day

160 LOC per day 400 LOC per day

500K LOC App requires 500K LOC App requires

156 man months min 62 man months

Developer Cost £400 per Developer cost £400

day, £8k per month per day, £8k per month

500K LOC costs 500K LOC costs

£1.25m £0.5m

(+ Re-Architecture and Modernization work)

www.zsl.com
Legacy Application Modernization

www.zsl.com
IT Portfolio Management
Create inventory of Applications

Map applications to the enterprise model

Drill down to detailed mappings

Identify areas for action

Manage IT portfolio via, planning,

evaluation and management

www.zsl.com
Replace/Rewrite Scenario
Management Decision taken to replace/re-write

Overall approach still to be determined

Rewrite? Migrate? Automated migration?

Evaluate Options

Identify preferred solution

Implement preferred approach

www.zsl.com
Architecture Consolidation Scenario
IT Architecture constantly evolves

Applications need to re-align

Applications need to integrate

Abstract and re-use common

functionality

Create efficient new platform

www.zsl.com
Model Driven Migration Scenario
Application architecture becomes
inefficient

Initiative to model the Application

Model enables improvements to me

identified

To-Be Architecture Defined

Re-Architecting / Re-Factoring occurs

www.zsl.com
Interface Modernization Scenario
Quick win scenario

Improve usability

Automate new business processes

Consolidate older ‘green’ screens

Replace shadow systems

www.zsl.com
SOA Transformation
Establish SOA policy

Establish target architecture

Implement SOA Technology & Standards

Re-factor selected applications using SOA

Develop new applications using SOA

www.zsl.com
Data Conversion Scenario
Data structures evolve

Data structure needs converting

Data is to be migrated

Data access code changes

App Architecture does not change

www.zsl.com
Language/Platform Migration Scenario

Driven by Technological
obsolescence

Driven by standardized applications

No functional improvement

No data redesign

www.zsl.com
Lift & Shift Migration Scenario

Convert one language or compiler to another

Eliminates a language, compiler or platform

No architectural change

Often driven by IT cost reduction

Can create an emulation environment

www.zsl.com
Aspects of Modernization

www.zsl.com
7 Stage Modernization Process

www.zsl.com
3 Architectural Domains

www.zsl.com
Zylog Transformation Framework

www.zsl.com
Model Based Transformation

www.zsl.com
 Modernization Tooling
Microsoft Team Language Specific Tool
System s

VSTS Architect
Language Parser
Edition

VSTS Developer
Output Templates
Edition

VSTS Test Edition Modelling Tool

Visual Studio Coding Standards Tool

www.zsl.com
Typical Legacy Application (e.g. Oracle Forms)

518 Tables / 228 Views Oracle Forms 4.5

125 DB Functions .

36 DB Packages .

305 DB triggers .

380 Oracle Forms .

66 Forms Libraries (Oracle
Designer) .

375 Oracle Reports .

www.zsl.com
Typical Architectural Decisions
N-tier, Scalable, Performant, Secure

MVC / MVVM Framework (C#/NET Java)

WPF, Silverlight, Ajax, Flex

Loose coupling between tiers (SOA)

Service Orientation (WCF / RIA)

Performance / Caching

Reliability

Availability

Portability

www.zsl.com
Oracle Forms to Java migration

www.zsl.com
Code Transformation

www.zsl.com
Source/Target Transformation

www.zsl.com
Modernization Team Deployment
Customer Site

London (Zylog)

Chennai (Zylog)

- Balance deployment locations and price

www.zsl.com
Engagement Model

www.zsl.com
Case Study – Government Legal dept

Source Application Target Application

Oracle Forms N-Tier Java App

Information IBM Execution
Management Environment
System

www.zsl.com
Government Benefits Application
Benefit Eligibility

Benefit Determination

Client correspondence, Mgt Reports

Workflow-based Application

1000 Screens in Application

Java EE, Oracle/ADF/Tuxedo

www.zsl.com
Electrical Retailer
PowerBuilder Legacy 4GL Solution

Distributed Databases

Reducing synchronization window

Limiting new shop opening schedule

Target: C# .NET Framework application

Aggressive shop openings

www.zsl.com
Case Study – Solothurn Switzerland
Workflow Doc Mgt System

Legacy 4GL Application

POC – Stage 1

Full migration to Java/Linux (36 depts, 400 users)

Integrated with Open Office

Built-in scripting engine

Dynamic Fields/Screens

Flexible Workflow driven application

www.zsl.com