Philip Newcomb, CEO, TSRI - Legacy to Cloud modernization

The Software Revolution, Inc. (TSRI) © 2015 All rights reserved
sales@tsri.com 425 284 2770
A
Workshop Agenda
09:00 am to 09:15 am Welcome Tea/Coffee
09:15 am to 10:00 am Cloud Best Practices Workshop Introduction Neil McEvoy
10:00 am to 11:00 am Cloud Computing Architectures and Principles – Part 1 Philp Newcomb TSRI
11:15 am to 12:30 pm Legacy Migration Automation Patterns for Cloud Computing – Part 2 Philip Newcomb TSRI
11:00 am to 11:15am Morning Break
12:30 pm to 13:30 pm Sandwich Buffet Lunch
13:30 pm to 14:30 pm ROI of Modernization for Technical Debt Remediation Dan Sturtevant Silverthread
14:30 pm to 15:30pm UL Cyber Security Inspection Services for Cloud Computing Arjan Geluk Underwriters Lab
15:15 pm to 15:30 pm Afternoon Tea/Coffee
15:30 pm to 16:30 pm Achitecture Driven Modernization Case Studies for Cloud Migration Philip Newcomb
16:30 pm to 17:00 Panel Session with Newcomb, Sturtevant, Geluk as panelists moderated by McEvoy
17:00 pm to 18:30 pm Open Bar for Workshop Attendees Hosted by TSRI
Cloud Best Practices Network Workshop
for Bringing Legacy Applications to the Cloud
Kingsway Hall Hotel, 66 Great Queens Street, London WC2B 5BX
9am to 18:30pm, Wednesday October 14, 2015
Co-hosted by CBPN and TSRI
WithUnderwriters Laboratory and Silverthread

Part1
Legacy Migration To the Cloud
Best Practices Workshop
Modernization Motivations
and Challenges

A
Overcoming Obstacles To The Cloud Migration: The
Legacy Migration Conundrum
Taken to extremes, the Cloud
eliminates the need for privately
owned computers altogether.
All computing resources becomes
shared services operating in a
shared environment.
Look Before You
Leap
Have you ever
felt like a
lemming?
eager
adopter
Legacy
SystemLegacy
SystemLegacy
System

Studies of Commercial and Government IT concerning
Modernization projects have found some disturbing statistics
• Only 16% of IT projects are completed on time and on budget.
• 31% are cancelled before completion.
• The remaining 53% are late and over budget, with the typical cost growth exceeding the
original budget more than 89%.
• Of the IT projects that are completed, the final product contains only 61% of the originally
specified features.
• Root Cause Analysis:
− Traditional defense acquisition process is “ill-suited for information technology systems
− Weapon system acquisition processes are often misapplied to IT systems acquisition
− Weapon systems acquisition process is optimized to manage production risk
− Does not fit information technology acquisition that does not lead to significant production quantities.”
Defense Acquisition Panel, House Armed Services Committee

Yet Modernization To the Cloud Achieves Huge IT Cost Reductions
TCO reduced by 66% per Annum Average Single Year Total Cost according to Standish Group*
Achieved by Replacing Mainframe with Commodity Hardware and Software
− 81% Reduction in Total Basic Costs
− 66% Reduction in Total Operating Costs
− 66% Reduction in Application Maintenance Costs
MAINFRAME VS. COMMODITY – AVG. SINGLE YEAR COST REDUCTIONS
Statistics from 100 Make, Buy, Modernize Projects*
BASIC COST ($000) MAINFRAME COMMODITY DIFFERENCE$ DIFFERENCE%
Hardware Cost $321 $73 ($248) -77%
Software Cost $192 $26 ($166) -86%
Manpower Cost $645 $85 ($560) -87%
Maintenance Cost $132 $56 ($76) -58%
Other Costs $53 $53 ($229) -81%
Total Basic Costs $1,572 $293 ($1,279) -81%
APPLICATION COST ($000)
BASIC COST $1,572 $293 ($1,279) -81%
Software Infrastructure $400 $201 ($199) -50%
Database and System Admin $554 $332 ($222) -40%
Application Maintenance $926 $314 ($612) -66%
Other Costs $218 $90 ($128) -59%
Total Operating Costs $3670 $1,230 ($2,440) -66%
Standish Group
Modernization
White Paper
2010
* Independent Source:

Can Legacy Software Migration to the Cloud Be Accelerated?
“Legacy applications built some time ago on legacy or proprietary hardware and software platforms would
take an inordinate amount of effort to convert onto a cloud platform. Instead of conversion, if the systems
are near end-of-life and are good candidates for the cloud, you should redesign and rewrite the
applications from scratch”
o From: The Cloud at Your Service, Jothe Rosenberg, Arthur Mateos, Manning Press, 2011
“While some might disagree, I define legacy applications as those not written to support a standards-
based, Internet-based, and Web-based architecture. …. Sooner or later, enterprises will want to rewrite or
replace their legacy applications with those written using a modern architecture, migrate them to the cloud,
and manage and control them remotely.
o From: Implementing and Developing Cloud Computing Applications, David E. Y. Sarna, CRC Press,
2011
There is nothing written about legacy and the cloud in one of the best books on the cloud…
o Distributed and Cloud Computing: From Parallel Processing to the Intenet of Things, Hwang, Fox,
Dongarra, Morgan-Kauffman, 2012
• Legacy Systems consume 70% of O&M budgets and would benefit the enterprise the most
from their cloud enablement.
• But, manual modernization costs $13 to $43 per line, and many experts believe legacy systems
cannot be migrated to the cloud...

A
Clearly Legacy Migration is Biggest Impediment to Cloud Adoption
The dependency and cost burden of the legacy systems consumes
54% of the total US government IT budget (per OMB).

C
Cloud Migration, the 3rd Wave of IT Innovation
Information Technology Evolution
InformationDrivenCapability
• Central computer center, slow turn around
• One size fits all
• Limited reuse of application modules
1950 1960 1970 1980 1990 2000 2010 2020
Wave 1 Centralized - Mainframe
Wave 2 Client/Server - Decentralized
Wave 3 Internet - Cloud
• Virtualized compute; global network enabled, plug & play
• IT Infrastructure decoupled from Applications
• COTS & OSS Integration, Software as a Service
• Legacy Application Migration to the Cloud
 We are in early stages of Wave 3 information
technology
 Mainframe and Client-Server waves remain in place
 Waves represent many co-dependent technologies,
matured over time
 Adding functional capability has become easier with
each new wave
 But enterprise infrastructure gaps & vulnerabilities have
become more critical • PC enabled and network
• Software distributed in both server and client computers
• Heavy focus on software development and point to point integration
We must stop delivering yesterday’s technology tomorrow and we must migrate legacy systems to the cloud

What Is Cloud Computing In Theory?
Definition: Cloud computing is the delivery of computing as a service rather than a product,
whereby shared resources, software, and information are provided to computers and other
devices as a utility (like the electricity grid) over a network (typically the Internet). – Wikipedia
In the Cloud Everything is a Service
− SaaS – Application / Software as a Service
− PaaS - Platform as a Service
− IaaS - Infrastructure as a Service
− XaaS – Your Pick as a Service
Taken to extremes the Cloud eliminates the
need for privately owned computers altogether.
All computing resources becomes shared
services operating in a shared environment.
Source:https://en.wikipedia.org/wiki/Cloud_computing

A
What Enables/Limits Cloud Computing?
Cloud Computing Enabling Factors - Benefits
- Increased storage, computation capacity, flexibility
and cost reduction
- Pay as you go computation without massive up front
cost for consumers
Cloud Computing Limiting Factors - Obstacles
- Security of corporate data in the cloud.
- Data privacy, network performance and economics
- Complexity, Diversity, Cost Transition
The Cloud is a Hotbed Of Diversity, Innovation and
Competition
- A vast array of cloud computing architectures is
arising both within and outside of company firewalls.
- Cloud computing is taking form as Public clouds,
Private clouds, Inter-clouds, or Hybrid Clouds bed on
security requirements.
The Absence of Standardization and Competing Reference
Models Creates Adopter Confusion.

A
What Factors Inhibit Cloud Adoption for Legacy Enterprise Computing?
The leading cloud platform architectures are
oriented towards new application
development only
Relatively few legacy applications have been
migrated to the cloud.
• Yet O&M for legacy enterprise
applications accounts for 70 to 80% of
IT expenditures.
Cloud reference models are very different
from legacy application architectures.
• E.g. Vmware (80% of virtualization
market) supports x86 applications
only. i.e. Vmware is incompatible with
most legacy applications.
Source: http://www.zdnet.com/article/comparing-amazons-and-googles-platform-as-a-service-paas-offerings/

For ROI a good place to start is to look at
the three market leaders:
• Amazon Web Services
• Microsoft Azure
• Google Web ToolKit
Build a matrix of what your organization
considers its
• Key Performance Factors
Map KPF matrix that against vendor then
current capabilities as well as expected
(assured non-risk) probable future
capabilities.
Gartner Magic Quadrant May 2015
Source: https://aws.amazon.com/resources/gartner-2015-mq-learn-more/

Key Feature Cross Comparison from August 2014
Source: https://www.quora.com/How-do-AWS-Microsoft-Azure-and-Google-Cloud-compare-to-one-another

Gartner Rankings of Cloud Providers
Source: http://techcrunch.com/2013/11/19/centurylink-buys-tier3-the-infrasructure-platform-and-advanced-cloud-management-provider/ Corporate Site Nov 19,2013/current Alex Williams

Source: https://www.pinterest.com/pin/551268810607422504/ taken from a Gartner Chart of Cloud Vendor Emphasis 2013
Gartner’s Summary of Major Cloud Vendor’s Emphasis

Legacy Modernization ROI
for Cloud
Computing (LMROI)
– What key ROI drivers govern
transformation of legacy enterprise
applications to the Cloud.

TSRI Advantage: TSRI Impacts the Biggest Hurdle: The One-
Time Legacy Migration Cost and Risk
Cloud ROI is composed of 3 major
benefit areas:
• Cost Reduction,
• Productivity Enhancement,
• Revenue Transformation.
The cost piece is comprised of mainly
3 different areas:
• Ongoing Direct Costs,
• One-time Migration Costs,
• and Migration Risk.
Companies developing and
implementing custom applications on
Force.com realized a total benefit of
$8.21 for every $1 invested,
• a 1 to 3-year ROI of 721%.
Source: http://www.persistent.com/sites/default/files/Whitepaper-%20Assessing%20the%20ROI%20of%20Cloud.pdf
Benefits of Cloud
Cost Reduction
Productivity
Enhancement
Revenue
Transformation
-
+
+
Benefits of Cloud
Ongoing Direct
One-Time
Migration
Risk
+
+
= ROI of Cloud
Adoption
From IDC, “Force.com Cloud Platform Drives Huge Time to
Market and Cost Savings,” September 2009. W H I T E P A P E R
©

Microsoft Azure Cloud Adoption ROI Calculator
Source:http://blogs.msdn.com/b/davedev/archive/2009/08/07/how-much-will-i-really-save-on-cloud-computing.aspx

B
Analysis of Alternative 3 top Modernization Approaches
Approach
Manual Rewrite or
Redevelopment
COTS Standardization
Automated Code
Modernization
Cultural Acceptance
Cycle time reduces stake
holder confidence,
lowers buy-in
Disruption due to
changes in business
process
Excellent, retained UI.
Short time line reduces
resistance
Retention of Agency
Processes & Rules
Positive Potential for
retention of business
processes, but highly
risky
Requires adopt business
process already
integrated in COTS
product
Excellent, business logic
is retained. Technical
logic is replaced. Refresh
extends life of
applications.
Ability to leverage
existing investments
New Development often
leads to “rip and replace”
Most COTS require
infrastructure upgrade
Retains investment in
people, process and
technology
Risk and Cost
Most costly, and risky per
OMB, 70% to 83.9%
failure rate
Excellent ROI if COTS
process are perfect fit.
High costs and risks occur
with package adaptation.
Lowest risk and cost
option thanks to
innovations
Side-By-Side Comparison of Alternatives

B
What Is Cloud Transition Cost / Value Proposition?
Low Risk High-
Quality
Automated
Modernization
Failure-Prone
Manual
Rewrite

Cloud Reference
Architecture Patterns
NIST
Cloud Architecture Model

NIST Cloud Architecture Reference Architecture
The National Institute of
Standards and Technology
(NIST) describes cloud
computing models as:
• enables convenient, on-
demand network access to a
shared pool of configurable
computing resources
• rapidly provisioned and
released of resources with
minimal management effort
or service provider
interaction.
• promotes availability and is
composed of five essential
characteristics, three service
models, and four deployment
models.
Source: NIST Special Publication 500-292, NIST Cloud Computing Reference Architecture

NIST Cloud Architecture Reference Architecture
In other words, NIST puts forth
specific “essential
characteristics“:
• On-demand self-service.
• Broad network access.
• Resource pooling.
• Rapid elasticity.
• Measured Service.
• Cloud Software as a Service
(SaaS).
• Cloud Platform as a Service
(PaaS).
• Cloud Infrastructure as a Service
(IaaS)
• Community cloud.
• Public cloud
• Private cloud
• Hybrid cloud
Source: NIST Special Publication 500-292, NIST Cloud Computing Reference Architecture

Some of the more accepted terms for the layers
Most Common Terms:
• DaaS – Data as a service
• SaaS - Software as a
service
• PaaS – Platform as a
service
• IaaS – Integration as a
service
• iPaaS – Integration
Platform as a Service
There is some overloading
at times with these terms as
PaaS – can also be
interpreted as Payment as a
service.
http://www.survik.com/technology-practices/cloud-computing
Source: http://www.cmswire.com/cms/information-management/cloud-service-models-iaas-saas-paas-how-microsoft-office-365-azure-fit-in-021672.php

Benefits
• More secure, efficient enterprise-level application
connectivity.
• Increased availability of critical services. ,
• Faster time-to-productivity for Microsoft Azure projects.
• Higher bandwidth capacity.
• Improved predictability of performance. Improved security
for outgoing corporate network
requests.
• Reduced on-premises data center footprint and associated
investments. .
Best Practices
• Analyze network traffic patterns for optimal cloud-based
performance. .
• Consider the distributed cloud and Internet edge. traffic is
application migration planning process.
• Understand application flow details before migration
Microsoft Azure
Source: https://msdn.microsoft.com/en-us/library/mt619199.aspx
Enable hybrid applications. run all its applications in the cloud, this
cloud is a mixture of both private cloud (on-premises) resources and
public cloud technologies, such as Microsoft
• Provide robust access to Microsoft public cloud services. created
a reliable network path with a defined end-to-end service level.
• Use software-defined networking. performs the required
configuration changes on the routers, both at the Microsoft IT data
center and Microsoft Azure locations.

Microsoft Azure Cloud Reference Architecture
The Microsoft Azure Stack provides
• Perception of Infinite Capacity
• Perception of Continuous Availability
• Resiliency over Redundancy Mindset
• Service Provider's Approach in Delivering
Infrastructure
• Drive Predictability
• Minimize Human Involvement
• Optimization of Resource Usage
• Encourage Desired Consumer Behavior
Software, Platform, Infrastructure Layers represent the
technology stack, where each provides services to the layer
above.
The Service Operations and Management Layers represent the
process perspective and includes the management tooling
required to implement aspects of the process.
The Service Delivery Layer represents the alignment between
business and Information Technology (IT).
http
Source: http://social.technet.microsoft.com/wiki/contents/articles/4399.private-cloud-reference-model.aspx Microsoft TechNet Bill Loeffler with Revision by Santhosh Sivarahab

B
Microsoft Cloud Implementation Architecture
The Microsoft Azure Stack provides
• Perception of Infinite Capacity
• Perception of Continuous Availability
• Resiliency over Redundancy Mindset
• Service Provider's Approach in Delivering
Infrastructure
• Drive Predictability
• Minimize Human Involvement
• Optimization of Resource Usage
• Encourage Desired Consumer Behavior
Software, Platform, Infrastructure Layers represent the
technology stack, where each provides services to the
layer above.
The Service Operations and Management Layers
represent the process perspective and includes the
management tooling required to implement aspects of
the process.
The Service Delivery Layer represents the alignment
between business and Information Technology (IT).
Source: http://social.technet.microsoft.com/wiki/contents/articles/4399.private-cloud-reference-model.aspx Microsoft TechNet Bill Loeffler with Revision by Santhosh Sivarahab

Elastic infrastructure - The Redhat
Open Hybrid Cloud Architecture
• provides consistent management
across a broad range of
infrastructure
• including physical systems,
datacenter virtualization, and
IaaS public clouds.
Redhat single pane of glass view of
resources
• Establishes comprehensive view
of all computing resources
• provides the information IT
organizations need to optimize
workload placement.
Redhat approach – Mitigates silo’d
management of IT resources for IT
organizations.
Source: http://allthingsopen.com/2013/07/11/red-hats-open-hybrid-cloud-architecture/
Red Hat’s Open Hybrid Cloud Reference Architecture

LinxCloud (IaaS) provides - efficient, always-
on infrastructure with elastic scalability
• integrated data protection;
• advanced automation; and
• the ability to transparently migrate both
applications and data across the
infrastructure
• end-to-end, validated design
architecture that isolates IT resources for
enhanced security in shared virtual and
enterprise cloud environments..
LinxCloud Flexpod provides a Secure Multi-
Tenancy architecture certified platform for
Cisco, VMware and Netapp virtualization
and cloud infrastructure . Key features
include:
LinxCloud (IaaS) Cloud Implementation Architecture - networking,
processing and storage.
Source: http://linxdatacenter.com/Iaas Corporate Web Site

CORA’s Capability As A Service Cloud Architecture Model
Connect to networks outside the Enterprise
The focus of the CORA model is on the internal
enterprise IT landscape and its relationship with the
outside world by consuming services from other
parties and providing services to other external
consumers.
Summarizing, the CORA mode divides an IT landscape
into different (blue) layers and (green) elements and:
• provides insight in the way an IT landscape can
support both business flexibility and compliancy
boundaries by using several distributed
‘architecture styles’ (N-Tier, Service Oriented,
Resource Oriented) simultaneously;
• Can be used at different levels (Enterprise level,
project implementation level) and to design and
implement functions with a mixture of
‘architecture styles’ on the best fitted platform
available (or planned);
• Establishes relationships with vendor specific
reference architectures so that different
technologies can be fitted in and vendor-
specific functions can be properly allocated
across a hybrid IT-landscape
Source: Source: http://www.coramodel.com/

Rackspace Hosted Hybrid Cloud Security
Architectures When security and
compliance are of the utmost importance
for your data, here are some additional
points to consider with a hybrid
architecture:
• Ensure your ingress/egress points
within your cloud environment only
permit desirable traffic.
• Leverage intrusion detection systems,
web application firewalls and log
managers to continuously monitor the
health of your environment.
• Tier your most critical or sensitive data
assets into a single-tenant dedicated
environment and leverage multi-tenant
public cloud for product catalogs and
less sensitive data.
Rackspace Cloud Security Architecture for the Hybrid Cloud
Source: http://www.rackspace.com/knowledge_center/whitepaper/cloud-security-in-an-agile-world Article ID: 4021 Last updated on August 26, 2014 Authored by: Rackspace Support

Cisco IaaS Cloud Offering for Cloud Service Providers
Source: http://virtualization.info/en/news/2010/01/cisco-announces-iaas-cloud-offering-for.html Web Article by the virtualization.info Staff 27 January 2011
Cisco’s interest in virtualization roots in mid-
2007, when it invested $150M in VMware, but
the ambition to play a major role in this
industry became evident with the launch of
Unified Computing System (UCS) and the
announcement of a coalition with EMC and
VMware.
• Cisco provides Infrastructure-as-a-Service
(IaaS) cloud offering for service providers.
• The recommended design implies the use of
many Cisco gears (from the MDS to the
Nexus 700), of any storage backend of choice
(EMC is the first suggestion) and, guess what
• VMware vSphere 4.0 is the foundation
virtualization platform for private cloud
architecture called Secure Multi-Tenancy
powered by VMware virtualization.

High Level Architecture of G-Cloud
As the UK Government iteratively develops
its G-Cloud multi-source procurement
frameworks,
• G-Cloud Public Services Network (PSN);
• CloudStore or Government Application
Store (G-AS).
• As such, the G-Cloud is a private cloud
which is available only to the UK Public
Sector community
• Any SaaS applications that sit outside in
the Public Cloud, such
as Salesforce.com or Microsoft’s Office
365, are accessed via a secure gateway
service if architectural integrity is to be
maintained.
• This is where Integration and
Management Services come into play!
• CloudStore is an online procurement
portal through which buyers call-off
services from the frameworks but these
and the architecture are still evolving.
Source: https://mikewilliamsblog.wordpress.com/2013/01/18/is-the-governments-cloudstore-confusing-the-market/ Mike Williams’ Blog

CAML Cloud Application Modeling Language
The Cloud Application Modeling Language (CAML) enables
expressing cloud-based deployments directly in UML.
CAML provides a dedicated model library for expressing
high-level deployment topologies and a set of UML profiles
for wiring such deployment topologies with concrete cloud
provider offerings.
The Cloud Library and the set of Cloud Provider Profiles are
available at:
• CAML Eclipse Plugins
• Deployment models for a reference application (it's
based on the Java Petstore) can be found here.
• Google App Engine also applies profiles provided by
the UML-Profile-Store. Therefore, the respective UML-
Profile-Store plugins two Papyrus modeling tool to
create the models.
• A set of application deployment blueprints based on
• Amazon AWS best practices are available at: Blueprints
Source: https://code.google.com/a/eclipselabs.org/p/caml/ form Eclipse Labs

Cloud Security for Enterprise
Systems (CSES)
How are enterprise legacy systems can
be securely migrated to the Cloud.

Cloud Migration Top 9 Threats and Damages
Cyber threat is a Big Obstacle to
Cloud Adoption
• 56%of organizations have been
the target of a cyber attack to the
Extended supply chain
• 44% of all data breach involved
third-party mistakes
• Financial loss $8.6M average cost
associated with data breach
• Cost of protection 8% of total IT
budget spent on security
• Reputation damage 30% market
cap reduction due to recent
events Source: HP internal data,

Web Application Security Testing and Threat Mitigation as
a Systematic Repeatable Practice
Source: http://defencely.com/blog/estimating-web-application-security-testing/
Navy Continuous Threat Mitigation Process Model
(1) Generate Application Blueprint (AB) for the legacy system and legacy system of
systems to derive the design and architecture for the system as a whole.
(2) Analyze legacy system code for vulnerabilities using state-of-the-art Cyber
Security assessment tools, and augment the AB with vulnerability annotations
allowing the vulnerabilities to be identified in the legacy code using OMG threat
assessment models.
(3) Transform the code of the legacy system to a type-safe modern language using
JanusStudio® code conversion services. Verify the transformed target code has not
distorted functional fidelity (using instrumentation to rapidly detect functional
deviation between the legacy and the transformed system)
(4) Generate the Transformation Blueprint for the derived target system with
derived design and architecture for the modernized system.
(5) Analyze transformed system code (in Java, C++ or other languages) for
vulnerabilities using state-of-the-art Cyber Security assessment tools, and augment
the TB with vulnerability annotations allowing these vulnerabilities to be identified
in the target code using OMG threat assessment models.
(6) Verify the transformed target code has not distorted functional fidelity (using
instrumentation to rapidly detect functional deviation),
(7) Develop attack patterns to compromise the legacy and target versions of the
system, and
(8) Compare robustness of the legacy and target systems version of the system
when subjected to attacks from the attack library.
(9) Develop and apply refactoring rules as counter measures against Cyberattacks,
(10) Compare the legacy and refactored target versions to assess the robustness of
the counter measures.
(11) Iterate 5 through 10, measuring incremental improvement of robustness with
each successive refinement cycle.
(12) Generate a refreshed Transformation Blueprint augmented with indices that
allow comparative measurement of successive generation of robustness
enhancements.

Less Sensitive Information to Cloud verse Critical Systems
Automated code hardening techniques
• To establish a highly-disciplined process for
automated systematic analysis and hardening
of software of all kinds.
• To demonstrate a generalized process for
CWE, CVE and CAPEC detection and
remediation for large scale software systems.
A highly formal approach to software analysis
and remediation is needed
• provide means by which systems that are
widely utilized within mission critical software
infrastructure can be systematically analyzed
and corrected for weakness
• vulnerabilities and attack pattern
classifications and abstraction occurring
within their code, designs and architectures.
Source: http://softwarestrategiesblog.com/category/public-cloud-computing/

Part 2
Automated vs Conventional
Cloud Adoption Patterns
…Or How 100% Automated Conversion to
Cloud MicroServices Changes the Game
for Legacy Modernization and
Cloud Migration/Adoption

Five-Level Cloud Computing Adoption/Maturity Model
There are many variants on cloud adoption
themes.
The common terms used to describe cloud
adoption.
− Agility
− Speed
− Intelligence
− Increased Margins
− Flexibility
The Maturity of Adoption Cycle is depicted in the
adjacent Cloud Adoption Pyramid Model
The Pinacle is Highly Adaptive Service Oriented
Microsystems
Source: http://www.eweek.com/c/a/Cloud-Computing/How-to-Achieve-the-Strategic-Value-of-Cloud-while-Delivering-Real-ROI

A 5-Step Cloud Adoption Reference Model
• Step 1 establishes the roadmap for transforming the IT infrastructure – moving from the traditional data center
approach to a centralized and consolidated infrastructure, through virtualization and automation, and finally
realizing an optimized IT infrastructure
• Step 2 establishes the architecture that will provide the capabilities needed to deliver cloud services effectively
and efficiently, considering the service consumer, provider and creator.
• Step 3 focuses on analyzing the workloads that are feasible to move to the cloud.
• Step 4 focuses on determining the right mix of delivery models to deploy and use the cloud services. Finally,
• Step 5 lays out the implementation approach for deploying the cloud services.
Source: http://www.jot.fm/issues/issue_2010_01/column3.pdf Mahesh H. Dodani, IBM, U.S.A.

Contrast of Conventional
Cloud Adoption
To Cloud Adoption and Modernization by
Means of Automated Code Conversion

B
Maximizing The ROI of Cloud Adoption
TSRI Minimizes One-Time Legacy Migration Cost and Risk to Maximize ROI
− Cloud ROI is composed of 3 major
benefit areas:
• Cost Reduction,
• Productivity Enhancement,
• Revenue Transformation.
− The cost piece is comprised of mainly
3 different areas:
• Ongoing Direct Costs,
• One-time Migration Costs,
• and Migration Risk.
− Companies developing and
implementing custom applications
on Force.com realized a total benefit
of $8.21 for every $1 invested
• a 1 to 3-year ROI of 721%.
Source: http://www.persistent.com/sites/default/files/Whitepaper-%20Assessing%20the%20ROI%20of%20Cloud.pdf
Benefits of Cloud
Cost Reduction
Productivity
Enhancement
Revenue
Transformation
-
+
+
Benefits of Cloud
Ongoing Direct
One-Time
Migration
Risk
+
+
= ROI of Cloud
Adoption
From IDC, “Force.com Cloud Platform Drives Huge Time to
Market and Cost Savings,” September 2009. W H I T E P A P E R
©

Migration Risks and Costs Increase with less Automation
TSRI Competitors are typically less than 80% automated
By contrast TSRI Conversion is virtually
100% automated
− The more manual the conversion the
more RISK and the more up front
planning cost.
− legacy migration becomes a simple
firm fixed price equation, a formula
Source: http://www.inteqsolutions.com/html/toxicology_labs.htm
TSRI’s AI Conversion Engine is JANUS Studio®
− JANUS Studio® achieves higher automation as
more systems are converted.
− As it does more systems in a language family
(e.g. FORTRAN or ADA) the more efficient
JANUS Studio® becomes.
Lines of
Code
Rate per
Line of Code
Cost of
Cloud Migration=x
TSRI Key Advantage
JANUS Studio® Targets
Reverse-Engineers
Documentation
Transformation and
Refactoring and Documents
Design and Architecture
With 100% Automation
JANUS Studio® Lowers Risk and Cost

B
Increasing Automation Reduces Key Risk and Cost Drivers
JANUS Studio® Targets Key Cost Components
− TSRI Automation Levels for Code and Data
Conversion is typically 100%
− TSRI Automates Reverse Engineering and Design
− TSRI Minimize Costs of Planning, UAT and
Stakeholder Requirements Reviews
− TSRI Minimizes Levels of Human Intervention
− TSRI Semi-Automated Design and Architecture Is
Machine Mediated Allowing Human Control and
Guidance
− Cost and Risks of Testing are Minimize Because of
Accuracy and Precision
Source: http://www.shreemitconsulting.com/web/application-legacy.html
Typical Migration Process is Shown Below
TSRI Advantage

The really difficult challenge is Legacy Systems.
Implications
− The low hanging fruits will go quickly as the post web developed systems get converted over
− The Hard Legacy Systems will take longer, but eventually they must be converted to Microservices
− Microservice conversion requires legacy systems to be transformed into modern languages and refactored.
Two Types of Application Architectures
Source: http://www.slideshare.net/Cloud-A/3-cloud-migration-strategies-that-you-should-consider
HARD NOT SO HARD
TSRI’s FOCUS
− is complex existing Legacy systems
− These systems pre-date the web
− This is where 80% of enterprise
software Lives
− Large organizations IT budgets
revolves around these kinds of
systems
TSRI Advantage
TSRI’s sweet spot is the legacy systems
which account by some estimates for 80%
of a typical large corporate/governmental
budget.

TSRI Approach to Legacy
Modernization to the Cloud
Cost and Risk Reduction
Legacy Software Modernization and Migration
Cost and Risk is the Key factor inhibiting
enterprise IT adoption of the Cloud

TSRI Modernization Mission Statement
Modernize valuable and often irreplaceable legacy system software and databases
into
− Modern platform-independent target languages and computing environments
− Without the requirement for manual intervention
Conform to standards-based Architecture-Driven Modernization (ADM) technology
and services that support
− Highly automated, cost-effective legacy system modernization
− At a fixed-price and guaranteed quality
− Between any practical combination of source and target languages

About TSRI
Offices in Kirkland, Washington
Technology Rooted in Early Artificial Intelligence Projects
− 1983 USAF Knowledge Based Software Assistance (KBSA) Program
− 1988 - 1994 Boeing Artificial Intelligence Lab
Member of the OMG Architecture-Driven Modernization (ADM) Task Force
− Author of Abstract Syntax Tree Meta-Modeling (ASTM) Standard
− ASTM Tutorial, leading ASTM Joint Submission Team
Awards
− Northrop Grumman “Small Business of Year” Award 2002
− Raytheon “Supplier of Value” Award 2005
− Small Business Administration’s 2005 “Administrators Award of Excellence”
− Philip Newcomb, TSRI CEO, is the 2011 Stevens Award recipient, for being the Principal Leader of Re-
Engineering and Automated Software Modernization.
− Fujitsu Legacy Modernization Global Partner Award 2013
− Most Promising Defense Technology Solution, CIO Review, 2014
Over 130+ Automated Modernization Projects since 2000
− 100% Customer Satisfaction
− All are Reference Accounts

TSRI Modernization Customers/Partners

Integrator System Source Language Target Language SLOC TTC
COMMERCIAL
SAIC & Open Source Fileman, VistA Pilot and Open VistA MUMPS Java 2.5M 6 months
Health Care Insurance Co. BlueCross Provider System PowerBuilder & Magna X Java 1.2M 3 months
AMDOCS Billing System COBOL C 5.1M 7 months
Thales Air Systems French Air Traffic Management Ada Java 495K 12 months
Thales Air Systems Nordic Air Traffic Management Ada Java 541K 9 months
Thales Air Systems Australian Air Traffic Management Ada Java 638K 9 months
Unisys NY State Dept. of Criminal Justice COBOL Documentation 308K 2 months
NEA Grant & Business Systems COBOL C++ 656K 7 months
SAIC Veteran’s Health Administration MUMPS Java 300K 4 months
State of Oregon Employee Retirement System COBOL C# .NET 250K 4 months
State of Washington Office of Superintendent of Public Instruction COBOL C# .NET 191K 5 months
TriGeo Sim v4.0 (Internal Product) Java Documentation & Re-Factoring 370K 2 months
EDS Proof-of-Concept PL/1 Java 50K 7 months
CSC Bureau of Immigration COBOL C++ 17K 3 months
Peridot Solutions Railroad Retirement Board COBOL to C++ Documentation 14M 2 months
The Boeing Company WIRS COBOL C++ 1.3M 12 months IP
GOVERNMENT
CGI/Stanley Advanced Field Artillery Tactical Data System ADA Java 5.5M 9 months
BAE Systems Korean F-16 Jovial C++ 500K 6 months
LMCO P-3C ADA C++ 656K 14 months
ITT BMEWS – Cobra Dane ADA/Fortran C++ 380K 8 months
Raytheon Satellites ADA/Fortran C++ 284K 5 months
L-3 VTT ADA C++ 77K 3 months
LMCO SAC Strategic Planning System ADA C++ 40K 2 months
DSR E-2C ACFT ADA C++ 20K 5 months
USAF CAMS COBOL Documentation 1M 6 months
NGC REMIS COBOL C++ 400K 7 months
Dyncorp WCSRS COBOL C++ 90K 5 months
ITT BMEWS – ROSA Fortran to C Documentation 2M 4 months
Raytheon Patriot Missile Fortran C++ 200K 6 months
Litton PRC Strategic Air Command Fortran C++ 50K 4 months
Raytheon WDAC Fortran C++ 40K 1 month
SAIC EOSS VAX Basic Java 38K 5 months
TRW MILSTAR Jovial C++ 143K 1 month
USAF F-16 Decis Jovial C++ 50K 4 months
General Dynamics - AIS Naval Undersea Warfare Center (NUWC) Weapons Control System (WCS) ADA C++ 800K 7 months
Leidos SPAWAR NGC2P CDLMS CMS-2Y Documentation 258K 3 months
Array Information Technology AFLCMC SBSS ILS-S/Pre-Award Work COBOL Java 34K 3 months
Lowest Risk and a Fraction of the Time and Cost Modernization

B
TSRI Modernization Value Proposition
Low Risk,
High-Quality,
Highly Scalable,
Automated Modernization
Failure-Prone,
High-Risk,
Long Schedule,
Manual Rewrite
Manual Redevelopment vs. Automated Modernization

TSRI Modernization Methods
TSRI delivers the highest quality modernized code at 100% automation levels.
Our component-oriented, model-based, architecture-first, and supports UML and MDA.
All change is iterative, accomplished by rules applied to models.
Rigorous, Iterative and Agile

B
JANUS Studio® Language Conversion Table
Supported Language Input
Language
Output
Language
Source
Language
Roundtrip with
Refactoring
Source to Target
Transformation with
Refactoring, Redesign and Re-
architecture
Application Blueprint
Documentation
For Source
Transformation
Blueprint® from
Source to Target
Ada Yes Yes Yes Source Yes Yes
C Yes Yes Yes Source Yes Yes
C# Partial Yes Yes Partial Source and Full Target No Partial Yes
C++ No Yes No Target No Partial Yes
COBOL Yes Yes Yes Source Yes Yes
DCL Yes Yes Yes Source Yes Yes
EGL No Yes No Target No No Yes
FORTRAN Yes Yes Yes Source Yes Yes
Java Yes Yes Yes Source and Target Yes Yes Yes
JCL Yes Yes Yes Source Yes Yes
Jovial Yes Yes Yes Source Yes Yes
MagnaX Yes Yes Yes Source Yes Yes
MUMPS Yes Yes Yes Source Yes Yes
Natural Partial Yes Yes Source Yes Partial
PL/1 Yes Yes Yes Source Yes Yes
Powerbuilder Yes Yes Yes Source Yes Yes
WANG PROC Yes Yes Yes Source Yes Yes
SQL Yes Yes Yes Source and Target Yes Yes
VAXBASIC Yes Yes Yes Source Yes Yes
VB6 Yes Yes Yes Source Yes Yes
VB.NET No Yes No Target Yes No Yes
XML Yes Yes Yes Source and Target No Yes
PL/SQL Yes Yes Yes Source and Target Yes Yes Yes

C
TSRI Modernization Technology and Process
JPGEN™ is TSRI’s Grammar Specification Engine
Parses code, generates models (ASTs), prints and formats code from ASTs
JRGEN™ is TSRI’s Rule-Based Transformation Engine
Matches patterns and transforms source code AST models to target code models
Legacy
Source
Files
Legacy
AST
IOM
AST
Target
AST
Target
Source
Files
IOM2Target
Rules
Legacy2IOM
Rules
Code
Lexer &
Parser
Constrainer
Automatic
Refactoring
For Target
JPGEN™
JRGEN™
Code
Formatter
Printer
Modern
IDE/SDK
Modern
OS/HW/DB

Page 56D
TSRI Modernization Project Engagement Phases
Free Transformation
Blueprint®
Preview
Free
Proposal
Preparation
Step 1: Pre-Project
Phase 1
Assessment
Phase 2
Transform
Phase 3
Refactor
Phase 4
Final Iteration
Free
Application Blueprint®
Preview
Set Up (FFP)
Detailed Refactoring Plan
and Specification
(FFR)
Step 2: Phased Project Execution
Auto Refactoring (FFP)
Semi-Auto Refactoring
(FFR)
Regression Testing (FFR)
Final Transformation
“To-Be” Blueprint®
(FFR)
Reiterate
Phase 1, 2, 3
(FFR)
Target Architecture Design (FFR)
Internal/External Dependency
Analysis (FFR)
Baseline Transformation
“To-Be” Blueprint® (FFP)
Transformation
(Developer-Ready) (FFP)
Resolve External Interfaces
(FFR)
Compilation (Deployment-
Ready)
(FFR) or (FFP)
Equivalence Testing (FFR)
Merge Code
Deltas Since First Drop (FFR)
Custom Refactoring (FFR)
Resolve Deployment
Architecture (FFR)
DB Transformation
(FFR) or (FFP)
Application “As-Is”
Blueprint® (FFP)
Client Go-Forward
Decision

B
TSRI Modernization Project Deliverables
FFP - Setup – JANUS Studio® legacy application code as AST (Abstract Syntax Tree) model
FFR - Dependency Analysis – Analysis of internal dependencies to support deployment & testing of application components
FFP - Application Blueprint® (Legacy Documentation) – A detailed presentation of structure & flow of the legacy code
FFP - Transformation Blueprint® (Final Documentation) – A detailed presentation of structure & flow of the modernized code
FFP - Compilation (Transformation Deployment-Ready) – Application is transformed cleanly to compile and link
FFR - Resolve External Interfaces – System adaptations to integrate with external interfaces
FFR - Deployment Architecture Enhancement – Optimize performance, Web/Cloud enable, refine application structure
FFP - Auto Re-factoring – Remove dead and redundant and consolidate code, introduce design patterns
FFR - Semi-Auto/Custom Re-factoring – Customer driven refinements and enhancements to improve design and architecture
FFR - Merge Code Deltas Since Initial Drop – Merge-in application updates since previous transformation iteration
FFP - Firm Fixed Price – Task will be accomplished at a pre-contracted fixed rate per unit volume price
FFR - Firm Fixed Rate – Task will be accomplished and charged in accordance with actual hours expended

TSRI Automated Transformation
Transforms legacy code into object-oriented code:
− C++, Java, C#, VB
− Couple to relational or object-oriented databases
− Convert user interface, database and database interface
Achieves target object-oriented software:
− Uniform & Native
− Compiler-Ready
− Fully Documented
− Test-Ready
Transformation Benefits
• Reduces hardware & software
ownership costs
• Avoids time & cost of COTS-based
solutions
• Provides greater flexibility for
tailoring system architecture &
functionality

TSRI Automated Refactoring
Starts the Re-engineering of Target Components
− Automatic Refactoring
• Removes dead and redundant code and data
− Semi-automatic Refactoring
• Merges and consolidates duplicate code and data
• Reorganizes and improves design of code and data
• Removes “As-Is” flaws from “To-Be” software
Creates reusable components for:
− Optimization, packaging, and redistribution
− Integration into/with modern
• Parallel
• multi-processor
• Distributed
• N-Tier operational environments
Refactoring Benefits
• Improves software
maintainability
• Enhances software performance
• Supports component-based
reusability
• Supports consolidation of “Stove-
Pipe” systems

TSRI Automated Web-Enablement
Adapt transformed system services to use:
− J2EE components (JDBC, JSP, JavaScript, HTML)
− Microsoft .NET components (ADO, ASP)
− GCSS framework components
Re-factor derived components to segregate:
− Client-side Web-browser and UI code
− Server-side data manipulation and access code
Generate multi-tier application architecture separating:
− Business logic
− Client-side presentation
− Low-level database definition and manipulation
Create flexible and extensible components for:
− Future enhancements
− Code reuse
Web Enablement Benefits
• Quick Exploitation of Web-
Environment Leveraging Legacy
System
• Improved product & Service Quality
Through Enhanced Communications
• Supports Lower Cost hardware
Options & Flexible Operational
Environment

B
TSRI Automated Data Base Conversion
Original
DB
Native DDL
Extracted or
Exported
Transformed
DDL
DAO
Artifacts
Target
DB
3. Round-Trip Data To Prove Equivalence
Original
Data
Target
Data
Round Trip Data
Comparison
Original
Data
Target
Data
2. Export Legacy Data and Import Into Modern DB
1. Derive Meta-Data and DB Schema
Data
Re-factoring
Data
Scrubbing

B
3-Tier Legacy Data Base Architecture
Isolate business logic from the data
access logic in cleanly separate
application tiers
− The business logic layer is isolated from
changes in the Data Access Object (DAO)
layer (Tier B)
− The DAO layer is a fully object-oriented
logical data interface
− The DAO layer encapsulates the
underlying details of db manipulation
from the business logic layer (Tier C)
− The DAO layer encapsulates the
underlying details of db manipulation
from the business logic layer (Tier C)
Tier A
Modern RDBMS
Tier C
Business Logic Layer
Tier B
DAO Pattern
JDBC / ODBC
ADO.NET
ORM / Hibernate

TSRI Technology Summary
JANUS Studio® Parses Source Code into an Abstract Syntax Tree Model (ASTM)
ASTM Transformed Into a Language-neutral Intermediate Object Model (IOM) which Simplifies Application
Transformation to an O(N+N) Complexity Problem.
Conversion to The Object-oriented Design
− Is Fully Automatic and Is Accomplished by Applying Pattern-Driven Model-Based Transformation Rules
− Along with Semi-automated, Human-directed Re-factoring plans
Re-Factoring Strategies Developed To Client Specification To:
− Improve Modernized System’s Code, Design and Architecture
Detailed Transformation Blueprint® of the Source/Target Code and its Design Provides a Detailed Roadmap for
Follow-On Refinements/Enhancements.

TSRI Modernization Advantages
Proven Technology
− 130+ Successful Projects To-Date (references available)
− 100% Customer Satisfaction
Award Winning
− Philip Newcomb, TSRI CEO, is the 2011 Stevens Award recipient
− Most Promising Defense Technology Solution, CIO Review, 2015
− Fujitsu Legacy Global Partner Award 2013
− Small Business Administration’s 2005 “Administrators Award of Excellence”
− Raytheon “Supplier of Value” Award 2005
− Northrop Grumman “Small Business of Year” Award 2002
Provides Lowest Cost Option
− Fraction of the price of other methods
− Segmented pricing structure
Proven Low Risk Solution
− Dramatically improves project success rate
− Compresses project schedules
− Reduces operational risks
− Is highly scalable and adaptable
Delivers Modernized Code and Databases
− Highly uniform, maintainable and extensible
− Fully integrated, tested and operational

Page 65
Modernization Strategies Pros & Cons
Back
Manual Approach
Failure Rates
COTS Approach
Failure Rates
Superiority of
Automated
Modernization
Approach
Manual Rewrite or
Redevelopment
COTS Standardization
Automated Code
Modernization
Cultural Acceptance
Cycle time reduces stake
holder confidence, lowers
buy-in
Disruption due to changes
in business process
Excellent, retained UI.
Short time line reduces
resistance
Retention of Agency
Processes & Rules
Positive Potential for
retention of business
processes, but highly risky
Requires adopt business
process already integrated
in COTS product
Excellent, business logic is
retained. Technical logic
is replaced. Refresh
extends life of
applications.
Ability to leverage existing
investments
New Development often
leads to “rip and replace”
Most COTS require
infrastructure upgrade
Retains investment in
people, process and
technology
Risk and Cost
Most costly, and risky per
OMB, 70% to 83.9% failure
rate
Excellent ROI if COTS
process are perfect fit.
High costs and risks occur
with package adaptation.
Lowest risk and cost
option thanks to
innovations
Side-By-Side Comparison of Alternatives

Additional Slides
Additional Slides

TSRI Modernization European Flight Operation System
Minimal Defects During 18 Months of Behavioural Testing
− 495 KLOC Project
− Less than 60 defects total due to translation in first 4 months.
− Less than < 1 defect per 10,000 Lines of translated code.
− Less than 25 defects introduced during 14 months due to Re-factoring.
0
10
20
30
40
50
60
70
80
90
Cumulated Nb of Translation Bugs Found
Nb of Translation
Bugs Found
Courtesy of
Air Systems Division

TSRI Modernization of 5.1 Million Line Army System
Pre-Functional Testing “Compile and Link” Error Resolution Trend Line
Begin extended requirements
support
Current error
count
1,000 LOC Source Ada
Predicted Data
Trend line for compilations errors
Hand Fix Threshold Compilation errors per 1,000 LOC

B
TSRI CEO Receives 2011 Stevens Award for TSRI Modernization of
High Assurance Flight Operations Software for European ATC
Shannon Centre, Ireland – Flight Operation Center Philip Newcomb receives 21st Stevens Award
His dedicated work has advanced
the application of AI- and rule-based
technologies for reverse
engineering, architecture
reassessment, testing, and
redevelopment, providing innovative
products and services for reliable
reengineering of mission-critical and
high assurance systems.” - Stevens
Award Committee (2011)
“A principal leader in
architecture-driven
reengineering and
modernization, Philip
Newcomb has been
instrumental in both
research and
development and
commercialization of
automated renovation
methods and tools.”
Philip Newcomb (2011)
Barry Boehm (2011)
Jared Spool (2011)
Peter Aiken (2010)
Watts Humphrey (2010)
Larry Constantine (2009)
Harry Sneed (2008)
Nicholas Zvegintzov (2007)
Grady Booch (2006)
Mary Shaw (2005)
Jim Highsmith (2005)
François Bodart (2004)
Manny Lehman (2003)
Cordell Green (2002)
Peter Chen (2001)
Gerald Weinberg (2000)
Tom DeMarco (1999)
Tom McCabe (1998)
Michael Jackson (1997)
David Harel (1996)
Tony Wasserman (1995)
Stevens Award
Recipients – 1995 to 2011

B
TSRI CEO Wrote The Book on Architecture Driven Modernization
Information Systems Transformation: Architecture-Driven Modernization Case Studies
By William M. Ulrich and Philip H. Newcomb
Published by Morgan Kaufmann
 Acts as a one-stop shopping reference and complete guide for implementing various
modernization models including core concepts, common scenarios, and a guide for getting
started.
 Concepts are illustrated with real-life examples from various modernization projects,
allowing you to immediately apply tested solutions and see results.
 Ten chapters containing in-depth modernization case studies, covering multiple platforms,
industries and government agencies from four different countries.
Grady Booch - Book Review
Ulrich and Newcomb's book offers a comprehensive examination of the challenges of growing software-intensive systems. Every system has an architecture, but as the authors explain, it is only by
continuous, intentional architectural transformation that one can attend to costs while simultaneously creating a mechanism wherein innovation may flourish.
I enjoyed the many case studies. Every circumstance is unique, but the authors have offered up best practices for systems modernization from their experience. Their focus on architecture as an
artifact for governance is sound, but they go far beyond the technical issues and address many of the social and economic practices that help one evolve a good technical architecture.
From the moment one writes a line of code, it becomes legacy, and that legacy accumulates. Whether it becomes a cause of innovation inertia or a source of future value is a factor of how it is
continuously modernized.

Greg Tadlock, VP of Sales & Marketing
gtadlock@tsri.com
Philip Newcomb, CEO & Founder
philip.newcomb@tsri.com
Kirkland, WA
+1 (425) 284-2770
www.tsri.com
Quick start your legacy system modernization with a Transformation Blueprint® preview.
Short Case Studies on Modernizing and Transitioning
Legacy Enterprise Applications to the Cloud Computing
Architectures

TSRI Cloud Modernization Reference Models
Several Case Studies are Presented in Depth in the Presenter’s Book:
Information Systems Transformation: Architecture Driven Modernization Case Studies,
Newcomb and Ulrich, Morgan-Kauffman, Feb, 2010 (OMG Press)
• Chapter 5: “Modernization of the Eurocat Air Traffic Management System”
• Chapter 6: “Powerbuilder/4GL Modernization Pilot ”
• Chapter 8: “Maintainability Information System (REMIS) into the Global Combat Support
System-Air Force(GCSS-AF) Framework”
• Chapter 10: “Legacy System Modernization of the Engineering Operational
Sequencing System”
• Chapter 12: “Veterans Health Administration’s VistA MUMPS Modernization Pilot”

B
TSRI Case Study: SAIC EOSS
• Legacy Application Blueprint of Legacy “As-
Is” VMS Vax Basic Code with UML Design
• Supported Target Architecture & Interface
Design Analysis and DON Opportunity
Analysis
• Automated Transformation and Re-Factoring
of VMS VAX Basic into N-Tiered Object-
Oriented Java
• ISAM to Relational (Oracle) Database
Conversion
• System Integration, Testing &
Implementation Support
• Transformation Blueprint™ of VMS VAX
BASIC and Java Showing Side-by-Side Code
with UML Design Documentation
Services Results
• Project successfully completed in 5 months
(Jun-04)
• JANUS Studio® rules engine parser was
extended to address the EOSS VAX-Basic
• Design new target architecture & fully
modernized 37,483 LOC of highly complex
mission-critical VAX-BASIC to Java
• Converted EOSS database structure form
multi-ISAM ASCII to Oracle 9i
• Navy calculated that effort provided a 2.47:1
ROI with much higher ROI expected for
languages already addressed by TSRI
The Software Revolution, Inc. (TSRI) was awarded a sole-source contract by SAIC and the Navy to
modernize the Navy’s Engineering Operational Sequencing System (EOSS).
ADM Scenarios :
1, 2, 3, 4, 7, 10, 12, 13
IV.
Platform
To
Platform
Migration
III.
Language
To
Language
Conversion
II.
Application
Improvement
I.
Application
Portfolio
Management
VII.
Data
Architecture
Migration
VI
SOA
Transformation
V.
SOA
Enablement
VIII.
Application
& Data
Architecture
Consolidation
IX.
Data
Warehouse
Deployment
X.
Application
Package
Replacement
XI.
Reusable
Software
Assets /
Component
Reuse
XII.
Model-Driven
Architecture
Transformation
XIII.
Software
Quality
Assurance
Project Contacts:
Upon Request
Project Summary
The project’s detailed case study is published
as Chapter 10: “Legacy System Modernization
of the Engineering Operational Sequencing
System” in:
Information Systems Transformation:
Architecture-Driven Modernization Case
Studies
By William M. Ulrich and Philip H. Newcomb
Published by Morgan Kaufmann ISBN: 978-0-
12-374913-0 Copyright Feb 2010

B
TSRI Case Study: Thales EATMS
• Application Blueprint of Legacy “As-Is” Code with
UML Design
• 1,700,000 line Ada to C++ and Java
Transformation and Refactoring of Ada into RT
Java
• Architecture-Driven Semi-Automatic Incremental
Re-Factoring of Target Design
• System Integration & Test Support
• Transformation Blueprint™ of Final Ada to RT
Java “Showing Side-by-Side” Code with UML
Design Documentation
Project Contacts:
Available Upon Request
Services Results
• Addressed the Flight Profile Library, Minimum
Safe Altitude Warning System, and Air-Ground
Data Processor modules of Eurocat
• JANUS Studio® rules engine parser was tuned to
address the legacy Ada code of these EATMS
modules
• Fully modernized nearly 1,700,000 LOC of Ada
code to Real Time Java
• Effort included extensive automated and semi-
automated re-factoring to meet precise, mission-
critical coding standards
• Achieved Ultra High Assurance Air Traffic Control
Software compliant with EATMS
The Software Revolution, Inc. (TSRI) performed multiple contracts for Thales Air Systems
to modernize several versions of Eurocat into the next generation European Air Traffic
Management System (EATMS).
The project’s detailed case study is published as Chapter 5:
“Modernization of the Eurocat Air Traffic Management System”
in:
Information Systems Transformation:
Architecture-Driven Modernization Case Studies By William M. Ulrich
and Philip H. Newcomb Published by Morgan Kaufmann ISBN: 978-0-12-
374913-0
Copyright Feb 2010
ADM Scenarios
1, 2, 3, 4, 8, 10, 11, 12, 13
IV.
Platform
To
Platform
Migration
III.
Language
To
Language
Conversion
II.
Application
Improvement
I.
Application
Portfolio
Management
VII.
Data
Architecture
Migration
VI.
SOA
Transformation
V.
SOA
Enablement
VIII.
Application
& Data
Architecture
Consolidation
IX.
Data
Warehouse
Deployment
X.
Application
Package
Replacement
XI.
Reusable
Software
Assets /
Component
Reuse
XII.
Model-Driven
Architecture
Transformation
XIII.
Software
Quality
Assurance
Project Summary

B
TSRI Case Study: 4GL/PB Conversion
• Transformation from Powerbuilder and
MagnaX into J2EE/Java and C++
• Automated Transformation, Re-Factoring,
Transformation Blueprinting, System
Integration & Test Support
• Powerbuilder and MagnaX Redesigned and
Reengineered Application Architecture into N-
Tier SpringBoard framework.
• Web-Enablement and Generated SOA
Interface Between.
Services Results
• Developed 100% Automated PowerBuilder
and MagnaX Modernization into Java/JEE
Spring Board
• JANUS Studio® Rules Engine & Parser was
Tuned to address both PowerBuilder and
MagnaX for 3.5MLOC follow-on.
• Full Modernization of Over 200,000 lines of
PowerBuilder and MagnaX to Java/JEE
• SOA API Interfaces Generated and Integrated
with Springboard Web Architecture and
DOJO/Ajax GUI and Back-End Business Logic
A Health Care service provider awarded The Software Revolution, Inc. (TSRI) two contracts to
demonstrate automated transformation of Power Builder and Magna applications of core HCSC
applications into the Java/JEE Spring Board framework.
The project’s detailed case study is published as Chapter 6:
“Powerbuilder/4GL Modernization Pilot ”in:
Information Systems Transformation: Architecture-Driven
Modernization Case Studies By William M. Ulrich and Philip H.
Newcomb Published by Morgan Kaufmann ISBN: 978-0-12-
374913-0
Copyright Feb 2010
IV.
Platform
To
Platform
Migration
III.
Language
To
Language
Conversion
II.
Application
Improvement
I.
Application
Portfolio
Management
VII.
Data
Architecture
Migration
VI.
SOA
Transformation
V.
SOA
Enablement
VIII.
Application
& Data
Architecture
Consolidation
IX.
Data
Warehouse
Deployment
X.
Application
Package
Replacement
XI.
Reusable
Software
Assets /
Component
Reuse
XII.
Model-Driven
Architecture
Transformation
XIII.
Software
Quality
Assurance
Project Summary

B
TSRI Case Study: Northrop Grumman REMIS
• Application Blueprint of Legacy “As-Is”
Tandem COBOL Code with UML Design
• Transformation and Refactoring of COBOL
into Object-Oriented Java and C++
• Semi-Automatic Re-Factoring for Data
Consolidation and Rationalization.
• System Integration & Test Support
• Transformation Blueprint™ of Tandem
COBOL to Java and C++ “Showing Side-by-
Side” Code with UML Design Documentation
Project Contacts:
Upon Request
Services Results
• Transformation successfully completed in
several increments spanning Feb/02 to Apr-
07
• JANUS Studio® grammar system and rules
engine parser was tuned to address REMIS’
Tandem COBOL code
• Fully modernized over 400,000 LOC of
Tandem COBOL into both C++ & Java code
• Supported development of the API layer to
allow system interface to the Air Force GCSS
Integration Framework
Northrop Grumman awarded three separate sole-source contracts to The Software Revolution,
Inc. (TSRI) for a transformation demonstration and subsequent modernization of the three
increments of the Air Force’s REMIS system
The project’s detailed case study is published as Chapter 8: “Modernization of
the Reliability Maintainability Information System (REMIS) into the Global
Combat Support System-Air Force(GCSS-AF) Framework”
in:
Information Systems Transformation: Architecture-Driven Modernization Case
Studies By William M. Ulrich and Philip H. Newcomb Published by Morgan
Kaufmann ISBN: 978-0-12-374913-0
Copyright Feb 2010
ADM Scenarios 1,
2, 3, 4, 7, 8, 9,12, 13
IV.
Platform
To
Platform
Migration
III.
Language
To
Language
Conversion
II.
Application
Improvement
I.
Application
Portfolio
Management
VII.
Data
Architecture
Migration
VI.
SOA
Transformation
V.
SOA
Enablement
VIII.
Application
& Data
Architecture
Consolidation
IX.
Data
Warehouse
Deployment
X.
Application
Package
Replacement
XI.
Reusable
Software
Assets /
Component
Reuse
XII.
Model-Driven
Architecture
Transformation
XIII.
Software
Quality
Assurance
Project Summary

Philip Newcomb, CEO, TSRI - Legacy to Cloud modernization

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (17)

Similar to Philip Newcomb, CEO, TSRI - Legacy to Cloud modernization

Similar to Philip Newcomb, CEO, TSRI - Legacy to Cloud modernization (20)

Recently uploaded

Recently uploaded (20)

Philip Newcomb, CEO, TSRI - Legacy to Cloud modernization