11/01/2007Legacy Migration and Modernization - NYC Technology ForumPage 1 Legacy Migration and Modernization: Leveraging the Value of Your Existing Applications

11/01/2007Legacy Migration and Modernization - NYC Technology Forum Page 1

Legacy Migration and Modernization:Leveraging the Value of Your Existing Applications in a Modern Enterprise Architecture

Bob Mastro – Vice President Health and Human ServicesNYC Technology Forum, November 1, 2007


Leveraging the value of your existing applications…

EnterpriseArchitecture

Unisys ADM Vision and practice

ModernizationStrategy & tactics

Model-DrivenArchitecture

Service-OrientedArchitecture

OMG ADMefforts

Architecture-Driven

Modernization

ExistingSoftware

EnterpriseArchitecture

Model-DrivenArchitecture

Service-OrientedArchitecture

Architecture-Driven

Modernization

ModernizationStrategy & tactics

OMG ADMefforts

Unisys ADM Vision and practice


The Reality

The Assumption

The field is rarely green


Knowledge-Based Modernization

Critical Business Knowledge is locked inside three sources of knowledge

Documentation Subject Matter Experts

Applications (most accurate)


The “legacy” application: an asset and a liability

It’s an asset!– Functional– Customized– Well-tuned– Supports mission critical

operations– Provides a competitive edge

It’s a liability!– Uses old technology – Requires hard-to-find skills– Lacks documentation – Hard to maintain– Resists change, integration,

and replacement

The moment an application goes into production, it becomes “legacy”

“You got to ac-cent-tchu-ate the positive, E-lim-i-nate the negative!”— Song lyric by Johnny Mercer, 1944


Architectural “big picture” view• Align software assets with enterprise architecture vision:

Architecture-Driven Modernization (ADM)

Ongoing management process view• Disciplined, strategic planning for old and new applications:

Application Portfolio Management (APM)

Cost-benefit view• Apply across all software assets:Application Portfolio Analysis (APA)

Reduce the negatives through modernization

“Home Improvement” view• Never-ending

• Plan to spend money


• The process of understanding & evolving existing software assets within an architectural framework

• The mirror image of Model-DrivenArchitecture (MDA)

Architecture-Driven Modernization (ADM)

Reverse Engineering

A D M

Forward Engineerin

g

M D A


ADM & MDA

• Modernization begins with the extraction and abstraction of knowledge from the existing application

• How far to abstract? It depends on the type of modernization

New orRenewed

Application

ExistingApplication

“As is” “To be”

ADM

Extract,Abstract,

andModel

Knowledge

ComputationIndependent

Viewpoint

PlatformIndependent

Viewpoint

PlatformSpecific

Viewpoint

MDA

domain

design

codeUnderstand

&

Evolve


Enterprise Modernization (EM) is a discipline concerned with • evolving existing systems to meet future needs• identification of the gap between existing system and enterprise’s current

requirements• preserving investments in existing systems (including proven business logic

and expertise of current staff)• understanding existing software and other IT assets

Architecture-Driven Modernization (ADM) is the process of understanding & evolving existing software assets for purposes of:• application portfolio management• code improvement• programming language translation• integration• platform migration• data migration

— Object Management Group ADM Task Force

• consolidation• data warehousing • reuse• package selection • service-oriented architecture • model-driven architectures

EM (a.k.a. ADM) covers a broad scope

3D-VE uses the terms “ADM”, “Enterprise Modernization”, “Enterprise Asset Modernization”, “Legacy Modernization” and “IT Modernization” as synonyms


Six modernization styles

Style Definition Results

1. Discover Mine knowledge and abstract it to the right level

As-Is model at the appropriate level of abstraction

2. Refactor Improve application without changing language or platform

Streamlined application with no dead code, no database redundancy, etc.

3. Translate Highly automated language-to-language translation

Application in the target language replicates functionality

4. Wrap Encapsulate cohesive functionality in a SOA harness

Portions of original application turned into components providing services

5. Replace Replace applications with new custom or packaged solutions

New, modern components that provide services that replace the legacy system

6. Orchestrate Orchestrate wrapped and newly replaced services

The composite solution using existing and new services


MineKnowledge

Unisys ADM framework

Translate Wrap Replace OrchestrateRefactor

MODERNIZATION BUILDING BLOCKS

“TO BE” APPLICATION

Discover &Understand

“AS IS”APPLICATION

Application

Business

Realization

Implemen-tation

PE

RS

PE

CT

IVE

Physical data model Interface definitions Execution flows

Logical data model Application boundariesApplication logic

Program logic

MODERNIZATION BUILDING BLOCKSMODERNIZATION BUILDING BLOCKS

Business processes

Business info reqsBusiness rules


Abstracting knowledge to business rules model level

“Your Application”

Spaghetti code, hiding business knowledge

Enables

Legacy asset preservation

Business model optimization

Forward engineering

Abstract

Business Rules

Business Vocabulary

Trace back

OMG SBVRStandard [3]


Mining knowledge from the outside in

• Start with “boundary elements” visible from the outside of the application, and follow paths through the code

• Tools are essential, but...

“Your Application”

GreenScreen Field

Report Field

Error Message

Business rule

First law of knowledge mining

"Only a computer can analyze vast

quantities of code, but only a human being can recognize what has business value."


The modernization journey…

…begins with mining of knowledge from existing

applications…

SOA?

…and heads towards Service Oriented

Architecture (SOA)

SOA what!


SOA enablement: Wrap and reuse

Conceptual “service bus” based on messaging

Eligibility

Determination

Call

Center

Web self-service

Casemanagement

Opencase

Addresschange

Calculatebudget

Reusableservices

Multiple clientapplications

sharing servicesmessages messages messages

messagesmessages

Serviceinterface

ServiceConsumer

(Client)

Back-endsystems

(Black box)

Requestmessage

Resultmessage

Servicewrapping

Standard & visible Implementation is hidden


SOA: avoiding spaghetti on top of spaghetti

Source: Gartner Group


Turning spaghetti code into services

“PastaTransformati

on”


SOA enables composite applications

Composite applications represent a design pattern that combines current applications, new application logic and

application integration to provide new functionality

Service Service Service Service Service Service Service Service Service

Composite Application

CompositeService

CompositeService

CompositeService

COBOL System .Net ComponentJava EE Component

SOA provides a way to assemble composite applicationsin a productive and flexible manner


Part 2: The Unisys vision for Architecture-Driven Modernization: Theory into practice


Knowledge-Based Modernization

ADM

Business Domain

Re

ve

rse

d E

ng

ine

eri

ng

Ge

ne

rate

Existing Solution Target Solution

Ab

stra

ct

As-Is Business Model (Vocabulary + Rules + Processes)

Fo

rwa

rd E

ng

ine

erin

g

IT Domain

Upgrading & Optimization

New Business Requirements / Optimization Criteria

To-Be Business Model (Vocabulary + Rules + Processes)

Min

e

As-Is Application Model (Data + Logic + Flows)

Defin

e SO

A

To-Be SOA Application Model (Data + Choreography

+ Orchestration)


Applications Wrapping – SOA

• Using Unisys tools from partners Relativity Technologies and KDM Analytics

• Document your legacy assets– Expose, navigate & provide a flow of

the application logic– Diagram all input and outputs– Excavate architecture – identify

deficiencies (unnecessary dependencies, lack of structure, etc.)

– Show database accesses & schema– Discover & define application rules

• Complete inventory of all legacy assets• Streamline applications

– Identify and eliminate dead code and code defects

– Remove unnecessary dependencies• Transform applications

– Break down application into modules– Transform modules into services– Replace presentation with HTML, Java


Code implementation discovered by 3rd-party mining tool

Unisys 3D-VE Rules Modeler Technology is embedded in KM

Inventory contains references to the

source code

Links between business vocabulary and rules and their implementations in the code

business vocabulary and rules implementations in the code

Example: linking rules to code


Unisys KMA for Business Rules• Discover intellectual property using Relativity

– Reverse engineering of application code– Mines ‘programmatic’ rules

• Create Business Rules Model using Unisys Rules Modeler

• Maintain traceability between business rules and program rules

• Enables a model-driven approach to forward engineering

– Enables application re-partitioning from the business process perspective

– Application can be restructured to optimize performance and maintenance

– New requirements can be added at the “to-be” modeling stage

– Can take advantage of model-driven code generation capabilities

– Enables ‘gap analysis’ for replacement with ‘off-the-shelf’ application


Building a modernization strategy on Unisys ADM building blocks

•The ADM approach for a given application may involve several ADM building blocks.

•Discovery of existing application knowledge is required for all scenarios…… but extent of discovery (“knowledge mining”) and level of abstraction varies by scenario

Translate

Wrap

Replace

Orchestrate

Refactor

Your Application Portfolio

App 1 App 2 App 3 App 4 App 5

Discover √ √ √ √ √

√ √ √

√

√ √ √

√

√ √ √

ADMBuilding

Block

The decision of what to do for each piece depends as much as on business goals, migration logistics, and economics as on the state of the technology


Summary

• Modernization strategy:– Let enterprise architecture

drive your strategy– Apply across your entire

software portfolio

• Modernization tactics:– Apply a combination of

modernization building blocks: Refactor, translate, wrap, replace, orchestrate

– Mine knowledge and abstract to appropriate level

• Modernization journey:– Begin with understanding existing software– Head in the direction of Service Oriented Architecture– Unisys can help, using its expertise, methodology and partnerships

Modernization strategy

Modernization tactics

Modernization journey


Questions?

For further information contact: [email protected]


Documents

11/01/2007Legacy Migration and Modernization - NYC Technology ForumPage 1 Legacy Migration and Modernization: Leveraging the Value of Your Existing Applications