This presentation is about the Unisys Architecture-Driven Modernization (ADM for short). The term ADM is not unique to Unisys—it is a term originating from the Object Management Group– but the Unisys approach to ADM is unique, built on a strong theoretical foundation and realized in practical and effective service offerings.
SOA-Enabled Modernization Dr. Vitaly Khusidman [email_address]
Why modernization? Two Sides of Legacy Applications
It’s an asset!
Supports mission critical operations
It’s a liability!
Uses old technology
Requires hard-to-find skills
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
Why are businesses considering application modernization?
Existing systems do not support new business models
Modification of existing systems is too risky
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
How SOA helps in modernization? Short and Tall ADM Horseshoe Models Business Domain IT Domain UML, WSDL, BPEL IT Domain Most modernization projects using this approach Two Proof of Concepts were completed for the NYC and NY State agencies SBVR, BPEL, BPDM, etc. Short Horseshoe To-Be App Model Existing Solution Target Solution Services Definitions As-Is App Model Existing Solution Discover + Wrap Tall Horseshoe Existing Solution Target Solution New Business Requirements/Model Optimization Discover + Replace + Orchestrate As-Is Business Model To-Be Business Model Existing Solution Target Solution New Business Requirements/Model Optimization Discover + Replace + Orchestrate As-Is Business Model To-Be Business Model SOA Definition
SOA enables Legacy Integration Applying short ADM Horseshoe SOA-Enabled Integrated Enterprise SOA Wrapper SOA Wrapper Enterprise Service Bus SOA Enabled Components Mainframe Client-Server Legacy Systems Mainframes Client - Server
SOA enables Legacy Integration Create SOA wrapped legacy services Steps: 1. Break down monolithic legacy application into components Language: UML 3. Specify how services collaborate with external world (service choreography) External World Service Languages: BPEL, BPDM 2. Define services exposed by components (service interfaces) Language: WSDL Service
SOA enables Enterprise Modernization Applying tall ADM Horseshoe ADM Business Domain Generate Existing Solution Target Solution IT Domain Reversed Engineering Abstract As-Is Business Model (Vocabulary + Rules + Processes) Forward Engineering Upgrading & Optimization New Business Requirements / Optimization Criteria To-Be Business Model (Vocabulary + Rules + Processes) Mine As-Is Application Model (Data + Logic + Flows) Define SOA To-Be SOA Application Model (Data + Choreography + Orchestration)
SOA enables Enterprise Modernization Applying tall ADM Horseshoe – Define SOA Steps: 2. Define services interfaces Service 3. Specify how services collaborate with processes (choreography) Process Service 1. Define boundary of automation for business processes and identify services 4. Specify how processes invoke services (orchestration)