Nitin Singhal SOA Tech Sales

1. SOA and Enterprise Architecture:A Natural Convergence Nitin Singhal SOA Tech Sales

2. Agenda • Enterprise Architecture … why should we care? • SOA and Enterprise Architecture • Best Practices for Enabling SOA at the Enterprise • Summary

3. Enterprise ArchitectureBridges the Gap Between Business and IT Strategy Information TechnologyStrategy BusinessStrategy Business Opportunity Technology Availability Enterprise Architecture • Business Architecture • Processes • Information • People • IT • Architecture • Applications • Information • Technology Enterprise wide focus Planning Transition Plan EA Governance Business Operating Environment and IT Infrastructure Project focus Design and Delivery IT Solutions

4. EA is more than Architecture

5. Business Environment (external influences) Customers, Regulators, Market, ... EA Context influences value Business Model Intent (strategies, drivers, principles, plans), Value (products & services), Capabilities, Business Processes, Information Model, Business Roles & Locations, ... Assets Governance Architecture Management Framework Leadership Sponsorship Ownership Resources Charter Structure Vision Principles Roles & Responsibilities Processes NFRs Roadmaps Metrics … People, Process, Technology Architecture Models Reference Architectures Infrastructure Packages Tools & Processes Services Skills … influences feedback Enterprise Architecture Business, Applications, Information, Technical, Governance Update influences feedback Solution Architectures (many, including SOA) Reuse Solution Architectures (many, including SOA) Solution Architectures (many, including SOA) influences feedback Information Applications Infrastructure

6. Agenda • Enterprise Architecture … why should we care? • SOA and Enterprise Architecture • Best Practices for Enabling SOA at the Enterprise • Summary

7. SOA means different things to different people Roles A model of the businessand related key performance indicators Business Anarchitectural stylewhich requires a service provider, requestor and a service description. It addresses characteristics such as loose coupling, reuse and simple and composite implementations. Architecture Aprogramming modelcomplete with standards, tools, methods and technologies such as Web services Implementation A set of agreements and contracts among service requestors and service providers that specify the quality of service. Operations

8. SOA Solution Stack

9. Enterprise Architecture: SOA Aspects • Intent: Ensuring SOA links to business value propositions • Solution Architecture: Designing SOA Solutions • Component Approach: Enabling a building block approach • Governance: Processes, roles and responsibilities • Planning: Planning/prioritization of SOA programs • Development: Building/composing SOA Solutions • Operations: Management of SOA-based runtime solutions • Deployment: "Publishing" SOA solutions and Change Management • Transition: Moving from "As-Is" to the "To-Be" SOA Environment

10. Components in an Enterprise Architecture

11. Mapping Solution Approaches to an EA

12. SOA-Based Enterprise Technology FrameworkApplication Architecture

13. Application Architecture – Banking Integration Layer Management Application Development Channels Layer Self service Branches Call Center Mobility Electronic Partners Protocols Functions Components Availability Presentation Layer Access Control Collaboration Personalization Content Authentication W ID management E e Services Layer S b Transport B S e r v i Atomic Services Composite Services Change Management c e s ( S B Directory management O P A Components Layer Routing M P s Business components o Quality Management b r e Investments Insurance Credit Banking Applic. CRM H T T P Configuration ( Data Transformation s ) Architecture Control , UDDI Repository Risk and Compliance M Payments Credit Cards Treasury Loans Q o u J M Portfolio and Process Control Common Components S Provisioning ) , J Cash Management Product Transformation M Asset Mgmt Collecting S Auditing HR Accounting Legal , Messaging H T T P Security Management ( s ) Information Layer o u A Client/Product/Segment Views Analytics d Workflow & Orchestration a p E t Client History a T Client Catalog Product Catalog Client Relationship d L Data Marts Information BI DW o r Monitoring e s

14. Agenda • Enterprise Architecture … why should we care? • SOA and Enterprise Architecture • Best Practices for Enabling SOA at the Enterprise • Summary

15. Are we still moving in the right direction? Are our target architectures still right? Transition Planning Governance Enterprise Architecture Models << Input from Business Analysis >> Plan Define Enable Measure Determine the Governance Focus Define the SOA Governance Model Implement the SOA Governance Model Refine the SOA Governance Model SOMA SIMM SGMM These are the things we should do This is the way things should be architected Are we doing these things the way we said we want them done? Projects Project Prioritization & Planning <<Output to SOA Implementation >> SOA and Enterprise Architecture: Best Practices

16. Component Analysis • The enterprise is mapped out as a set of categorized business components • Heat map highlights components for analysis based on criteria such as gaps and efficiency • Enables approaches to understanding how the business can be improved Business Administration New Business Development Relationship Management Servicing & Sales Product Fulfillment Financial Control and Accounting Business Planning Sector Planning Directing Account Planning Sales Planning Fulfillment Planning Portfolio Planning Sector Management Relationship Management Sales Management Fulfillment Monitoring Compliance Controlling Business Unit Tracking Reconciliation Product Management Credit Assessment Staff Appraisals Product Directory Credit Administration Sales Product Fulfillment Customer Accounts Executing Account Administration Product Administration Marketing Campaigns Customer Service Document Management Purchasing General Ledger Collections Branch/Store Operations

17. Dynamically Re-Configurable Services Virtualized Services Composite Services Isolated Business Line Driven Business Process Integration Componentized Business Componentized Business offers Services Processes Through Service Composition Geographically Independent Service Centers Mix and Match Business and Location Capabilities Integrated Componentized Silo Services Business Application Specific Skills IT Transformation IT Governance Emerging SOA Governance SOA and IT Governance Alignment SOA and IT Infrastructure Governance Alignment Governance through Policy Organization Structured Analysis & Design Object Oriented Modeling Component Based Development Service Oriented Modeling Service Oriented Modeling Service Oriented Modeling Business Grammar Oriented Modeling Methods Modules Objects Components Services Process Integration via Services Process Integration via Services Dynamic Application Assembly Applications Monolithic Architecture Layered Architecture Component Architecture Emerging SOA SOA Grid Enabled SOA Dynamically Reconfigurable Architecture Architecture Application Specific LOB or Enterprise Specific Canonical Models Information As a Service Enterprise Data Dictionary and Repository Virtualized Data Services Semantic Data Vocabularies Information LOB Platform Specific Enterprise Standards Common Reusable Infrastructure Project-based SOA Environment Virtual SOA Environment Dynamic Sense & Respond Common SOA Environment Infrastructure Level 1 Level 2 Level 3 Level 4 Level 5 Level 6 Level 7 Service Integration Maturity Model (SIMM)

18. Business Process Integration Componentized Business offers Services Business Service Decomposition Dynamically Re-Configurable Services Composite Services Virtualized Services Silo Services Integrated Componentized Level 1 Level 2 Level 3 Level 4 Level 5 Level 6 Level 7 Service Integration Maturity Model (SIMM) Isolated Business Line Driven Business Process Integration Processes Through Service Composition Geographically Independent Service Centers Mix and Match Business and Location Capabilities Business Application Specific Skills IT Transformation IT Governance Emerging SOA Governance SOA and IT Governance Alignment SOA and IT Infrastructure Governance Alignment Governance through Policy Define & Enforce SOA Governance Organization Move to SOA-based Design Methodology Structured Analysis & Design Object Oriented Modeling Component Based Development Service Oriented Modeling Service Oriented Modeling Service Oriented Modeling Business Grammar Oriented Modeling Methods Process Choreography Assembly Modules Objects Components Services Process Integration via Services Process Integration via Services Dynamic Application Assembly Applications Focus on SOA Foundation Monolithic Architecture Layered Architecture Component Architecture Emerging SOA SOA Grid Enabled SOA Dynamically Reconfigurable Architecture Architecture Deploy Common Information Services LOB or Enterprise Specific Application Specific Canonical Models Information As a Service Enterprise Data Dictionary and Repository Virtualized Data Services Semantic Data Vocabularies Information LOB Platform Specific Enterprise Standards Common Reusable Infrastructure Project-based SOA Environment Virtual SOA Environment Dynamic Sense & Respond Common SOA Environment SOA Infrastructure Standard Infrastructure

19. SOMA gets inputs from business analysis activities, and produces outputs necessary for SOA implementation The analysis and modeling performed during SOMA is technology and product agnostic, but establishes a context for making technology and product specific decisionsin later phases of the lifecycle << Input from Business Analysis >> SOMA Service Identification Service Specification Service Realization <<Output to SOA Implementation >> Service Oriented Modeling and Architecture (SOMA) LinksBusiness Intent with IT Implementation

20. SOA Governance Lifecycle Define the Governance Approach • Define/modify governance processes • Design policies and enforcement mechanisms • Identify success factors, metrics • Identify owners and funding model • Charter/refine SOA Center of Excellence • Design governance IT infrastructure Plan the Governance Need • Document and validate business strategy for SOA and IT • Assess current IT and SOA capabilities • Define/Refine SOA vision and strategy • Review current Governance capabilities and arrangements • Layout governance plan Enable the Governance Model Incrementally • Deploy governance mechanisms • Deploy governance IT infrastructure • Educate and deploy on expected behaviors and practices • Deploy policies Monitor and Manage the Governance Processes • Monitor compliance with policies • Monitor compliance with governance arrangements • Monitor IT effectiveness metrics

21. Implementing A Center of Excellence (COE) Manage the SOA Lifecycle Change management including policies for publishing, using and retiring services Infrastructure to help govern access and monitor service vitality Provide Skills Transfer & Early Proof of Concepts Identify skills gaps and create development roadmaps Drive use of new technologies and techniques such as BPM Provide SOA Measuring Best Practices Visibility to usage and project information Business and IT dashboards Provide Architecture Vitality & Thought Leadership Continuously assess, refine and architecture framework and supporting assets based on internal & external influences Provide Architectural Authority Single point of accountability and communicates SOA best practices, assets, and patterns Center of Excellence Conduct SOA Architecture Reviews Perform independent design and architecture reviews for key applications and infrastructure Define High Value Business Services Modeling business processes, information services Best practices for identifying and defining shared services Establish Decision Rights Service portfolio planning and organizational design Assets and best practices

22. Business & IT Lessons • Start with the business – don’t lead with IT SOA solutions • Difficult to ‘sell’ SOA business value by itself –need to focus on the business value of enterprise-wide reusable services • Initially will have higher cost to develop for reusability when compared for a single project’s use • SOA is not standalone – ideally be part of a comprehensive Enterprise Architecture • SOA Governance required fairly early in the picture • SOA acceleration should be a combination of top-down (Business) and bottom-up approach(IT) • Don’t forget about enabling the infrastructure for SOA

23. WebSphere Business Modeler WebSphere Business Monitor WebSphere Process Server WebSphere Service Registry & Repository WebSphere Business Svcs Fabric WebSphere Information Server WebSphere Customer Center DB2 Data Warehouse Data Power WebSphere Portal Business Services WebSphere ESB Lotus Collaboration Solutions Information Services Process Services Interaction Services WebSphere Message Broker Lotus Expeditor Management Services DevelopmentServices WebSphere Transformation Extender Enterprise Service Bus Tivoli Composite Application Monitor Rational Software Architect Partner Services Business App Services Access Services Apps & Info Assets Tivoli Identity Manager Rational Application Developer Tivoli Federated Identity Manager Infrastructure Services WebSphere Integration Developer Tivoli Access Manager WebSphere Partner Gateway WebSphere Application Server WebSphere Adapters WebSphere Network Deployment WebSphere Extended Deployment Enabling SOA with IBM tools

24. SOA establishes an enterprise architecture that enables business flexibility and agility SOA is an important foundation of enterprise architecture Companies are using SOA today to drive tangible business value Investments in SOA will continue to drive competitive differentiation. SOA is not one-size fits all Implementation of SOA varies according to the company’s business / IT environment and goals Companies should leverage well defined best practices derived from SOA experiences to make the SOA journey effective Start small, grow fast, and drive successful implementation through effective governance Summary

25. Remember – SOA Adoption Is A Journey