SOA-Enabled Modernization
Dr. Vitaly Khusidman
[email protected]
Page 1
In Brief …
• Why modernization?
• How SOA helps in modernization?
• SOA enables Legacy Integration
• SOA enables Enterprise Modernization
• Points to remember
Page 2
Why modernization?
Two Sides of Legacy Applications
It’s an asset!
–
–
–
–
Functional
Customized
Well-tuned
Supports mission critical
operations
– Robust
– Secure
It’s a liability!
–
–
–
–
–
Uses old technology
Requires hard-to-find skills
Lacks documentation
Is hard to maintain
Resists change, integration,
and replacement
– Inhibits organizational agility
ADM (Architecture Driven Modernization – OMG name for Enterprise
Modernization) preserves the asset value while eliminating the liabilities
Page 3
Why are businesses considering
application modernization?
• Agility
– Existing systems do not support new business
models
– Modification of existing systems is too risky
• Intellectual Property
– People with business knowledge are retiring
– People with application knowledge are retiring
– Knowledge hidden in application code
• Total Cost of Ownership
– Operation cost of Mainframe systems is too high
– Maintenance cost of existing software is too high
– Skills set is rare and too expensive
Page 4
How SOA helps in modernization?
Short and Tall ADM Horseshoe Models
New Business Requirements/Model Optimization
Business Domain
Most modernization
projects using this
approach
SBVR, BPEL, BPDM, etc.
As-Is Business Model
To-Be Business Model
Tall Horseshoe
Services Definitions
As-Is App Model
UML, WSDL, BPEL
Discover
To-Be App Model
+
Short Horseshoe
Replace
Discover
+
+
Orchestrate
Wrap
Existing Solution
SOA
Definition
Target Solution
Existing Solution
Two Proof of
Concepts were
completed for
the NYC and NY
State agencies
Target Solution
IT Domain
Page 5
SOA enables Legacy Integration
Applying short ADM Horseshoe
Legacy Systems
SOA-Enabled Integrated Enterprise
Mainframe
SOA Wrapper
Mainframes
Client-Server
SOA Enabled
Components
SOA Wrapper
Client - Server
Enterprise
Service Bus
Page 6
SOA enables Legacy Integration
Create SOA wrapped legacy services
Steps:
1. Break down monolithic legacy application into components
Language: UML
2. Define services exposed by components (service interfaces)
Service
Language: WSDL
3. Specify how services collaborate with external world (service choreography)
External World
Languages: BPEL, BPDM
Service
Page 7
SOA enables Enterprise Modernization
Applying tall ADM Horseshoe
New Business Requirements / Optimization Criteria
As-Is Business Model
(Vocabulary + Rules + Processes)
Business Domain
To-Be Business Model
(Vocabulary + Rules + Processes)
Upgrading & Optimization
Mine
To-Be SOA Application Model
(Data + Choreography
+ Orchestration)
Generate
Existing Solution
Forward Engineering
As-Is Application Model
(Data + Logic + Flows)
Reversed Engineering
ADM
Target Solution
IT Domain
Page 8
SOA enables Enterprise Modernization
Applying tall ADM Horseshoe – Define SOA
Steps:
1. Define boundary of automation
for business processes and identify
services
2. Define services interfaces
3. Specify how services collaborate with
processes (choreography)
Service
Process
Service
4. Specify how processes invoke services
(orchestration)
Page 9
Points to remember
• Legacy application is an asset and liability
• Architecture Driven Modernization (ADM) is an
OMG name for Modernization
• ADM addresses Agility, IP Preservation and TCO
• ADM Horseshoe can be either short or tall
• Short Horseshoe-based SOA enables Legacy
Integration – first phase in modernization
• Tall Horseshoe-based SOA enables Enterprise
Modernization – maximum business value
Page 10