architecture-driven modernization ----------------------------------------- the legacy systems...

Architecture-Driven Architecture-Driven ModernizationModernization

----------------------------------------- ----------------------------------------- The Legacy Systems ChallengeThe Legacy Systems Challenge

OMG Government Information Day – March 2008OMG Government Information Day – March 2008

------------------------------------------------------------

William Ulrich - TSG, Inc.William Ulrich - TSG, Inc.

www.systemtransformation.com

http://www.systemtransformation.com/

Defining Architecture-Driven Defining Architecture-Driven Modernization (ADM)*Modernization (ADM)*

Process of understanding & evolving existing Process of understanding & evolving existing software assets for:software assets for: Software improvementSoftware improvement ModificationsModifications Interoperability Interoperability RefactoringRefactoring RestructuringRestructuring ReuseReuse Porting Porting MigrationMigration Translation into another languageTranslation into another language Enterprise application integrationEnterprise application integration Service-oriented architectureService-oriented architecture Other initiatives as they relate to existing systemsOther initiatives as they relate to existing systems

* Source: Object Management Group (OMG) Architecture-Driven Modernization Task Force – http://adm.omg.org/ Copyright TSG Inc., 2008, All Rights ReservedCopyright TSG Inc., 2008, All Rights Reserved

http://adm.omg.org/

Enterprise Impacts of Aging IT Enterprise Impacts of Aging IT ArchitecturesArchitectures

Existing Data & Application Architectures:Existing Data & Application Architectures: Contain redundancy, obsolete functionality mixed with Contain redundancy, obsolete functionality mixed with

mission critical code across stovepipe structuresmission critical code across stovepipe structures Delay and undermine critical IT projectsDelay and undermine critical IT projects

Business Impacts of Aging IT Architectures:Business Impacts of Aging IT Architectures: Inefficiency, high operating costs, spiraling head-countInefficiency, high operating costs, spiraling head-count Poor responsiveness to customers / constituent basePoor responsiveness to customers / constituent base Lost / delayed revenue realizationLost / delayed revenue realization Creation of Shadow Systems* Creation of Shadow Systems* Erosion of ability to respond to tactical & strategic Erosion of ability to respond to tactical & strategic

objectivesobjectives

* * Spreadsheets, faxes, email, Access, dual entry, paper/pencilCopyright TSG Inc., 2008, All Rights ReservedCopyright TSG Inc., 2008, All Rights Reserved

Traditional Approaches to Meet Traditional Approaches to Meet Existing IT Architecture ChallengesExisting IT Architecture Challenges

ExistingExistingITIT

ArchitecturesArchitectures

GreenfieldGreenfieldReplacementReplacement

MiddlewareMiddlewareBasedBased

IntegrationIntegration

ERP (Package) SolutionsERP (Package) Solutions

Existing IT architectures include application and data architectures as well as Existing IT architectures include application and data architectures as well as technical architectures. technical architectures.

Copyright TSG Inc., 2008, All Rights ReservedCopyright TSG Inc., 2008, All Rights Reserved

Greenfield Replacement:Greenfield Replacement:Costly & RiskyCostly & Risky

Greenfield replacement implies from scratchGreenfield replacement implies from scratch

Real cost of application rewrites is in the range Real cost of application rewrites is in the range of $15-30 / line of code (Gartner)of $15-30 / line of code (Gartner)

Greenfield replacement results in: Greenfield replacement results in: Missing or incorrect data & business rulesMissing or incorrect data & business rules

Significant reworking of deliverablesSignificant reworking of deliverables

Loss of critical business knowledgeLoss of critical business knowledge

If Greenfield replacement fails – there is no If Greenfield replacement fails – there is no fallbackfallback


Commercial-Off-the-Shelf Software Commercial-Off-the-Shelf Software Comes with Risks & CostsComes with Risks & Costs

* Source: Cutter Report – Vol. 6, No. 9 – Sept. 2006

Integrating packages with existing data and Integrating packages with existing data and systems was very challengingsystems was very challenging

98% of package users were forced to change 98% of package users were forced to change business practices (tail wagging the dog)business practices (tail wagging the dog)

60% of business users favored the existing 60% of business users favored the existing legacy applications over the new packagelegacy applications over the new package

Only 18% of package users found it easy to Only 18% of package users found it easy to realize package benefitsrealize package benefits


New IRS system allows $200M in bogus refunds (USA Today – 2006)

Telecommunications company cancels package implementation effort - $70-80 million failure

FBI throws out a $100 million system as a total failure

U.S. Federal Agency cancels $70 million SAP implementation

Health insurance provider shuts down $60 million major systems replacement project

Hershey distribution package failure drives down stock value (1999)

Unacceptable Results of Greenfield Unacceptable Results of Greenfield Replacement & Package OptionsReplacement & Package Options


Middleware Solutions Can Even Middleware Solutions Can Even Complicate Business ArchitecturesComplicate Business Architectures

Source: “Aligning Technology and Business: Applying Patterns for Legacy Transformation”, Howard Hess, IBM Systems Journal, Volume 44 Number 1, 2005

http://www.research.ibm.com/journal/sj/441/hess.pdf

“…recent advances in integration middleware technology have provided some relief by making it possible for financial institutions to move customer information across channels. But in many cases the technology has been laid over flawed legacy architecture and has merely created more duplication.”


http://www.research.ibm.com/journal/sj/441/hess.pdf

Why Consider Modernization as a Strategy to Why Consider Modernization as a Strategy to Augment or Displace Traditional IT OptionsAugment or Displace Traditional IT Options

Traditional replacement approaches have Traditional replacement approaches have fallen shortfallen short

Non-invasive integration options have hit a Non-invasive integration options have hit a wallwall

Modernization offers solutions to address Modernization offers solutions to address critical, core IT architecture challengescritical, core IT architecture challenges


Modernization: Shifting from Modernization: Shifting from Tactical to StrategicTactical to Strategic

““Most CIOs will need to develop new skills and Most CIOs will need to develop new skills and competencies in their management teams to deal with competencies in their management teams to deal with the significant challenges of IT modernization” the significant challenges of IT modernization”

““IT modernization reinstates IT strategic planning at IT modernization reinstates IT strategic planning at the heart of the CIO cabinet”the heart of the CIO cabinet”

““An organization's first act is to modernize its strategic An organization's first act is to modernize its strategic planning capabilities and immediately focus these planning capabilities and immediately focus these competencies toward IT asset modernization”competencies toward IT asset modernization”


* * Source: Gartner, Inc., “What the CIO Should Know and Do About IT Modernization “, Vecchio & Kyte, 6 February 2008

Architecture-Driven Modernization: Aligns Architecture-Driven Modernization: Aligns Business & IT Domain InitiativesBusiness & IT Domain Initiatives

Adopted from early horseshoe models from Unisys/TSG, Inc.

Bu

sin

ess D

om

ain

IT D

om

ain

IT D

om

ain

Existin

g

Existin

g

Enviro

nmen

t

Enviro

nmen

t Target

Target

Environment

Environment

Physical SystemPhysical SystemImplementationImplementation

Program DesignProgram DesignLevelLevel

System Design LevelSystem Design Level

Analysis LevelAnalysis Level

Requirements LevelRequirements Level

UML / SystemUML / SystemModelsModels

Business ModelsBusiness Models

Business Strategy

Mod

erni

zatio

n A

naly

sis

Dom

ain

AD

MR

efac

torin

gD

omai

n

AD

MT

rans

form

atio

nD

omai

n


Architecture-Driven Architecture-Driven Modernization ScenariosModernization Scenarios

ADM Scenario: An initiative (e.g. portfolio ADM Scenario: An initiative (e.g. portfolio

management), project (e.g. migrating management), project (e.g. migrating

platforms) or series of projects (e.g. platforms) or series of projects (e.g.

consolidating, redesigning and redeploying an consolidating, redesigning and redeploying an

application in model driven architecture) application in model driven architecture)

applied to one or more existing systems.applied to one or more existing systems.


Modernization Scenarios (Projects) Driven by Modernization Scenarios (Projects) Driven by Degree of Abstract from Physical SystemsDegree of Abstract from Physical Systems

Adopted from earlier horseshoe models from Unisys/TSG, Inc.

Bu

sin

ess D

om

ain

IT D

om

ain

IT D

om

ain

-Data ConversionData Conversion-Language TransliterationLanguage Transliteration

-Language MigrationLanguage Migration-Platform MigrationPlatform Migration

-Replacement ScenariosReplacement Scenarios-Greenfield RewriteGreenfield Rewrite-ERP/Package DeploymentERP/Package Deployment

UML / SystemUML / SystemModelsModels

Business ModelsBusiness Models

ADM Scenario MappingM

od

ern

izat

ion

Pro

ject

Sce

nar

ios

-SOA TransformationSOA Transformation-Data Architecture RedesignData Architecture Redesign-Procedural to Object Lang. MigrationProcedural to Object Lang. Migration

-Knowledge ReclamationKnowledge Reclamation-Model Driven Architecture MigrationModel Driven Architecture Migration-Architecture ConsolidationArchitecture Consolidation

Target

Target

Environment

Environment

Existin

g

Existin

g

Enviro

nmen

t

Enviro

nmen

t


Converts source code to new language or language level with run time environment

Objective: Convert system to new language and / or run time platform.

Migrates application to new hardware and / or operating system

Sample ADM Scenario:Sample ADM Scenario:Language & Platform Migration ScenarioLanguage & Platform Migration Scenario

•Scenario (s) not model driven.•Typically 1-to-1 correspondence between current and target system•Can mix & match with module / system redesign or consolidation.


Sample ADM Scenario: Model Driven Sample ADM Scenario: Model Driven Architecture Transformation ScenarioArchitecture Transformation Scenario

Objective: Migrate existing data, business logic to an environment in which systems are maintained in models.

•Extract business rules & data definitions•Purge implementation dependent logic•Rationalize/consolidate data & logic as needed•Migrate/merge extracted logic & data definitions into applicable modelsExisting applications

& data definitionsSample models

RegisterClaim

ApproveClaim

Trigger

ObjectFrom objectdata model

PreconditionEmployee makes

a claim Register claim

Trigger

Daily claimreview process

Source: Martin/Odell

InsuredEmployee

Producepacking list

DecrementFGI

Ship orderShip order

Shipping Clerk

Drop shipfrom remotewarehouse


OMG’s Architecture-Driven Modernization OMG’s Architecture-Driven Modernization Task Force Driving Industry StandardsTask Force Driving Industry Standards

OMG ADM Task Force* established in 2003:OMG ADM Task Force* established in 2003: To create specifications and promote industry consensus on To create specifications and promote industry consensus on

modernization of existing applicationsmodernization of existing applications Major industry vendor, integrator participation Major industry vendor, integrator participation

ADM Standards ADM Standards Knowledge Discover Metamodel (KDM)Knowledge Discover Metamodel (KDM) Abstract Syntax Tree Metamodel (ASTM) in final submissionAbstract Syntax Tree Metamodel (ASTM) in final submission Software Metrics Metamodel (SMM) in final submissionSoftware Metrics Metamodel (SMM) in final submission Analysis Package submissions in progressAnalysis Package submissions in progress Visualization, refactoring & transformation under discussionVisualization, refactoring & transformation under discussion

Tool interoperability & standards offer organizations more Tool interoperability & standards offer organizations more options and confidence in long-term solutionsoptions and confidence in long-term solutions

*OMG Architecture-Driven Modernization Task Force *OMG Architecture-Driven Modernization Task Force

-- See: -- See: http://adm.omg.org/ Copyright TSG Inc., 2008, All Rights ReservedCopyright TSG Inc., 2008, All Rights Reserved

http://adm.omg.org/

Four Basic Ways to Implement Four Basic Ways to Implement Modernization on ProjectsModernization on Projects

Tool Centric:Tool Centric: License tool, get trained & do it License tool, get trained & do it yourself:yourself: Works where repeated use of tool is envisionedWorks where repeated use of tool is envisioned

Service Supported:Service Supported: License tool, engage outside License tool, engage outside support to work with in-house teamssupport to work with in-house teams

In-Sourced:In-Sourced: Bring in vendor with a tool & they Bring in vendor with a tool & they perform work onsite perform work onsite Works well for one-time projects Works well for one-time projects

Outsourced:Outsourced: Send your system out to a vendor Send your system out to a vendor Works only for very well defined tasksWorks only for very well defined tasks

In-house personnel still must do oversight, testingIn-house personnel still must do oversight, testingCopyright TSG Inc., 2008, All Rights ReservedCopyright TSG Inc., 2008, All Rights Reserved

Essential Elements of an Architecture-Essential Elements of an Architecture-Driven Modernization ProgramDriven Modernization Program

Understanding of how modernization fits into Understanding of how modernization fits into existing or planned IT & business projectsexisting or planned IT & business projects

Framework for understanding project scenarios, Framework for understanding project scenarios, work plans, estimates and cost analysiswork plans, estimates and cost analysis

Knowledge of and access to available tools, Knowledge of and access to available tools, technologies & service providerstechnologies & service providers

A starting point:A starting point: Current, high-level architecture assessmentCurrent, high-level architecture assessment

Strategy session outlining options, timelinesStrategy session outlining options, timelines


What You Should Think About What You Should Think About When Considering ModernizationWhen Considering Modernization

Do you really understand why you are Do you really understand why you are undertaking the initiative?undertaking the initiative?

Have you taken business architectural alignment Have you taken business architectural alignment into account?into account?

What are the impacts on interfacing & What are the impacts on interfacing & upstream / downstream systems?upstream / downstream systems?

Have you considered the condition & impact of Have you considered the condition & impact of the underlying data architecture?the underlying data architecture?

Are you leveraging established modernization Are you leveraging established modernization literature, approaches & knowledge?literature, approaches & knowledge?


Architecture-Driven Modernization:

The Legacy Systems Challenge

Questions?

OMG Government Information Day – March 2008OMG Government Information Day – March 2008

------------------------------------------------------------

William Ulrich - TSG, Inc.William Ulrich - TSG, Inc.

www.systemtransformation.com

architecture-driven modernization ----------------------------------------- the legacy systems...

Documents

existing systems

business users

package users

data architectures

new package

package benefits copyright

rights reserved slide

scratch greenfield replacement