www cbdiforum com Application Modernization Framework David Sprott

www. cbdiforum. com Application Modernization Framework David Sprott Independent Guidance for Service Architecture and Engineering 1

Top Priorities are to “Slim Bloated Software Portfolios” £ £ £ Modernizing legacy applications – 59% of IT leaders place modernization as the top software issue Packaged applications bloat - 49% will consolidate or rationalize their enterprise applications, Version upgrades - 51% plan to upgrade The top three software concerns named by IT decision-makers in the 2009/2010 Enterprise Software Survey by Forrester Research all point to their desire to slim bloated software portfolios. 2 © 2010 Everware-CBDI International

Modernization Use Cases £ £ US Regional Bank - Account and Customer modernization £ Strong business improvement theme. Common customer and channel services. £ UK Retail Bank – Complete portfolio moved from MSP to in-house £ Application re-platforming – new packages; 90% functional equivalence. Core service architecture. £ Government department using 20 yr old development technology £ Move to SOA to componentize, standardize process across delivery channels £ UK Corporate Banking Div. using COBOL and assembler mainframe applications £ Façade service architecture as first step to legacy CBS retirement and upgrade. £ 3 UK Retail Bank Mortgage Sales rebuild £ High functional equivalent, but with process improvement – standardize brand processes, common channel process. Adopt SOA. Major Airline – End of life support on mainframe reservations product. £ Rewriting entire operations processes as SOA. Standardization of business process. © 2010 Everware-CBDI International

Modernization Maturity Model Architecture Driven Modernization Delivery Process Modernization Delivery Technology Modernization Service Enable, Service Façade Restructure Business Driven Modernization Re-process, Restructure E. G Agility metrics driven Architecture. Continuously Evolving; Integrated business and IT governance E. G Componentize, SOA, EDA, CEP Re-platform, Re-host E. G Server Virtualization Offshore, BPO, Cloud Re-skin, Recode E. G PL 1, Cobol, Assembler to Java; Mainframe to Application Server 4 © 2010 Everware-CBDI International

Architecture n Architecture 3 Architecture 2 Transitional Physical Implementation Sequence Planning Transitional Physical Architecture Harvesting Logical Architecture Operations Infrastructure As-Is Rapid Delivery Business Architecture 1 Modernization Context To-Be Transition Strategy Deliver agile cor e with mini mum funct ional change Business Case Analysis Information Architecture Project Management/SDLC 5 © 2010 Everware-CBDI International

The Horseshoe Model (Source SEI) 6 © 2010 Everware-CBDI International

Business Driven? AP AS-IS AP TO-BE P New business events need to be managed 1 7 . 8 New complex events need to be communicated 1 7 . 8 Change in process logic 4 4 . 9 New process steps 4 6 . 9 White labeling 5 5 . 6 Additional attributes 5 5 . 7 7 5 . 9 4 7 . 9 6 8 . 7 New technology channels 1 7 . 9 New business channels 1 8 . 9 Consumer Mobile channel 1 1 . 2 Technology Web 2. 0 channel. 1 5 . 5 Business Capability Areas of Potential Change Business Process User Interface E Simple validation Complex validation New forms Channels A EX L MP AGILITY POTENTIAL (AP) - the relative potential agility that a business capability or business process requires. PROBABILITY (P) - probability in the range 0 (zero) to 1, where 0 = impossible to 1 which = certain 7 © 2010 Everware-CBDI International

Example Agility Assessment Matrix (Partial) Increase number of suppliers Offer platform for business services 8 ss Proce s roces Sales Multi-channel customer process 3 8 5 5 2 9 2 7 2 AS-IS AP 9 TO-BE AP Agility Potential - Now / Required Common view of customer Risk P Objectives Custo mer P roces s Scoping Units – Business Process, Capabilities © 2010 Everware-CBDI International

Unit of Modernization Scope Definition Enterprise or An enterprise, or division of Ecosystem An ecosystem TOGAF SAE Architecture A portfolio of applications Multiple A set of applications and/ or set of Applications services Architecture or Platform e. g. To support a Business Domain, Business Unit, or Business Process Solution Architecture Service Architecture or running on a hardware or operating system platform that must be modernized Application An individual application Application Component Element An individual element of an applications, or a set of related elements Logical Application Service Component Automation Unit Data Entity May be common to many applications e. g. Database 9 Solution Information System Service © 2010 Everware-CBDI International

Decomposition of Scope May Result in Multiple Approaches Portfolio Application 1 Replace (build) Application 2 Replace (buy) Application 3 Restructure Element 3. 1 Recode Element 3. 1 10 Service Enable Element 3. 2 Service Facade Replace (buy) Rehost © 2010 Everware-CBDI International

Application Modernization Approaches Objective Replace Approach Description Applies to Scope Other Approaches Replace (Build) New build, in-house, outsourced All Service Facade Replace (Buy) New COTS All Service Facade Consolidate and rationalize or Ecosystem Multiple Applications Service Façade Reengineer Replace Re-skin New UI Web 2. 0 enablement Application Service Enable Re-process New Business Process Multiple Applications May Service Enable be single application Service Facade Recode Reengineer implementation Application Element Restructure Componentize implementation Application Re-platform Migrate to new platform Application Multiple Applications Recode Restructure Re-host Migrate to new servers Virtualization/Cloud Application Multiple Applications Re-platform Restructure Rationalize Modernize Component Reengineering Modernize Service Reengineering 11 Service Enable New Service Interface New Data, Underlying or Exclusive service Application Element (e. g. Database) Service Facade New Core Business Services layer or Process services layer Portfolio Service Enable (Underlying Services) © 2010 Everware-CBDI International

Approach Determines Type/Level of Activity TO-BE Business Model AS-IS Business Model Service Specification Architecture Application Architecture <<Application>> Implementation Architecture Logical <<module>> <<database>> Physical Implementation <<module>> If, then, else <<database>> table, column Deployment Architecture Technology Architecture 12 Architecture Recovery <<Application>> Rationalize Re-skin Re-process Service Facade Service Enable Recode Restructure Architecture-based Development Replace (Build) Replace (Buy) Service Specification Internal Architecture <<component>> Service Implementation Architecture <<component>> If, then, else <<database>> <<message>> Re-platform Re-host © 2010 Everware-CBDI International

Reference Model Principles Meta Model £ £ £ £ £ 13 Glossary Life Cycle Service enabled Component based Contract based Standardized (IT and business) Platform independent Virtualized Model driven architecture and design Application knowledge Defined change management capability © 2010 Everware-CBDI International

Reference Architecture Stakeholder Views Best Practice Business Standards Patterns Techniques Models Deployment Policy Implementation Deliverables Specification Infrastructure 14 © 2010 Everware-CBDI International

The Twin Architecture Views of SAE 2 Sample As-Is Artifacts View Sample To-Be Artifacts Business Service Level Agreement Service Catalog Service Portfolio Plan SO Security Architecture Code & Action Artifacts UI Artifacts Events Artifacts Data Artifacts Service Specification Service Implementation Architecture Automation Unit Specification Service Implementation Service Deployment Architecture Service Platform Design Specification Technical Architecture Platform Artifacts Deployment Infrastructure Service Specification Architecture Build Artifacts Implementation SO Business Model Structure Artifacts Conceptual Artifacts Specification SO Business Plan Logical Network Services Physical Network 15 © 2010 Everware-CBDI International

Process SAE 2 Process Consume Provide Enable Business Improvement Consume Business Modeling Manage Solution Provisioning Solution Architecture & Design Legacy Application Reengineering Application Modernization Planning Provide Knowledge Discovery Solution Assembly/ Implementation Legacy to Service Reengineering Service Oriented Architecture & Design Service Provisioning Service Implementation Information Architecture Enable Solution/Service Platform Architecture Solution/Service Platform Design & Installation Solution/Service Deployment Solution/Service Operations & Management SOA Adoption & Excellence SOA Governance SOA Quality Management Manage SOA Delivery Management Modernization Change Management 16 © 2010 Everware-CBDI International

SAE 2 Process Disciplines – Planning and Architecture Business Improvement As-Is Business Modeling Business Plans Business Models Solution Architecture & Design Solution Architecture Current Assets Solution Architecture Business Plans Application Modernization Planning Information Architecture Application Modernization Plan Candidate Component Inventory Knowledge Discovery Current System Model Service Portfolio Plan (Service Architecture) Service Requirements Service Oriented Architecture & Design Business Models Information Architecture As-Is Architecture Information Architecture 17 KDM Package Service Architecture (Service Portfolio Plan) (Note: Primarily showing Application Modernization context) © 2010 Everware-CBDI International

SAE 2 Process Principles Supporting new business requirements mapping Transition AS-IS Understanding current implementation £ £ £ £ 18 Managing the transition TO-BE Detailing new implementation Deliver agile core for continuous evolution Scoping and decomposing activities into manageable Work Packages. Iteration through the various Work Packages leading to revisions at all levels to fine-tune the next iteration. Continuous improvement of the assessment and plan Separation of Solution and Service Architecture, and Solution and Service Delivery, to deliver a layered Service Architecture that is not too tightly bound to a single solution Incremental delivery of an inventory of shared services and solution components that reduce time and effort in subsequent projects. Agile methods used within Work Package © 2010 Everware-CBDI International

Modernization in Parallel with Phased Modernization Iterations Plan Assess Analyze Deliver Evolve Revisions to Assessment For each Improvement Revisions to Plan Assess Revisions to Solution Plan (scope) Realize Modernization Solution 1 For each Solution For each Unit of Planning Scope For each Service Realize Modernization Solution 2 Realize Service 1 Realize Service 2 Revision to Plan Deploy Solution 1 Deploy Solution 2 Deploy Service 1 Operate Solutions/ Services Measure Deploy Service 2 Revisions to Service Plan (scope) Modernization Roadmap Assess 19 Plan Manage © 2010 Everware-CBDI International

Agile Approach to Realization Analyze Deliver Realize Modernization Solution 1 Outline Architecture and Plan Detailed Architecture and Plan Ongoing iteration and refinement Prioritized, Coherent Set Delivery Activities Solution Component and Service Requirements Working Solution Component or Service For each Solution Component or Service Revisions to Architecture and Plan 20 © 2010 Everware-CBDI International

SAE 2 Reference Framework Service Architecture & Engineering (SAE 2) Reference Model Principles Process Consume Glossary Provide Meta Model Life Cycle Enable Reference Architecture Stakeholder Views Manage Best Practice Business Organization Standards Patterns 21 Techniques Infrastructure Models Deployment Policy Implementation Deliverables Specification Roles & Responsibilities Policy Funding Models © 2010 Everware-CBDI International

Summary £ Application Modernization is more than technology transformation £ Business driven doesn’t mean “functional requirements driven” £ Agility Potential (AP) provides structure to customer communications £ Objective is to deliver agile platform for tomorrow’s business needs, . . NOT today’s business needs £ 22 Formal, defined reference framework is essential © 2010 Everware-CBDI International

Everware-CBDI and CBDI Forum £ Independent specialist AM/SOA firm £ Located UK and USA CBDI Forum £ Practices Co. E £ Documented, published best practices, reference architecture, repeatable processes £ Structured, meta model based, model driven, agile practices £ Approach widely used by F 1000 companies, consultancies/integrators and government departments £ Facilitating SOA standards £ £ £ Everware-CBDI £ 23 25, 000+ subscribing architects worldwide AM/SOA Solution Business including Consulting, Education and Knowledge products and tools Independent Guidance for Service Architecture and Engineering © 2010 Everware-CBDI International