Painting by Surekha Durvasula © SOA Practitioners’ Guide: Best Practices for Enterprise Transformation and Modernization Burc Oral, PhD, CellExchange, Inc., Peter Bostrom, BEA Systems Painting by Surekha Durvasula © Third Service Oriented Architecture for E-Government Conference, May 1-2, 2007, at MITRE: Responsibility to Provide Best Practices for An Information Sharing Environment - Bringing Together the Global Information Grid, W3C, SOA Consortium, and Shared Services

SOA Practitioners Authors are also the founding members of the SOA Consortium Surekha Durvasula, Enterprise Architect, Kohls Martin Guttmann, Principal Architect, Customer Solutions Group, Intel Corp Ashok Kumar, Manager, Director – Services Architecture, Avis/Budget Jeffrey Lamb, Enterprise Architect, Wells Fargo Tom Mitchell, Lead Technical Architect, Wells Fargo Private Client Services Dr. Burc Oral, Sr. Architect, CellExchange, Inc. Yogish Pai, Chief Architect AquaLogic Composer, BEA Systems, Inc. Tom Sedlack, Enterprise Architecture and Engineering, SunTrust Banks, Inc. Dr. Harsh Sharma, Senior Information Architect, MetLife Sankar Ram-Sundaresan, Chief Architect e-Business, HP-IT

The Practitioner’s Guide: A Collective BoK Collaborative work of dedicated expert SOA practitioners, brought together by BEA and Intel in 2005 Authors are also the founding members of the SOA Consortium A series of living documents Collective body of knowledge about SOA Develops a shared language Describes and documents best practices and key learnings Helps fellow practitioners address the challenges of SOA A reference encyclopedia for all SOA stakeholders Guide to Enterprise Transformation and Modernization

Different Paths to the Same Future Vision business services (Business) future vision Process Driven Enterprise soa Business Value Business Priority Portals Integration App Server Database infrastructure services (IT) traditional approach COTS packages, etc. current state Business Complexity IT Priority

Impetus for the Practitioners’ Guide Relieve Business and IT Pain Points Expand Current Enterprise Architectures Business Solutions through Applications Create Future Vision Business Solutions through Infrastructure Align IT and Business Paths

Best Practices for Alignment Understand Business Services Define Key Performance Metrics Build out the Infrastructure While Meeting Immediate Business Needs Identify “quick wins” Using SOA Design and Build Infrastructure Services as Required Develop SOA Blueprint and Follow SOA Practitioners’ Guide

Establish Services Lifecycle Three Stages of Services Lifecycle Governance Accurately capture the business requirements Develop the IT solutions to business requirements Deploy and maintain the service to business requirements Business Requirements 1 Service Repository 3 IT Operations 2 Solution Development Governance

Services Lifecycle BAM SOA Repository Business Requirements Business Services Business Process BAM Executable Services Service Logic Develop missing services Service Matrix SOA Repository Service Assets Requirements / Use case Design Specifications Inputs & Outputs Data elements required Dependent on services Service used by Versions Source code (location) Builds (location) Product Type Service Deployment Submit developed services Service Assembly Model Prod 1 Prod 2 Portal Prod 3 Approved Services Prod 1 ESB Prod 2 Logical Deployment Data Services Shared DS Srv Srv Srv Infrastructure I&AM ETL DQ Storage

Elements of a Lifecycle Stage Actors Tools Artifacts/Deliverables Service Lifecycle Key Considerations Stage Recommended Process Best Practices and Requirements Download SOA Practitioners’ Guide for Details

Services Lifecycle Selected Best Practices Requirements Stage Best Practice Capture all business requirements in the form of business processes such as activities, rules, and policies Application Design Stage Best Practice Have business analysts focus on business process modeling and architects focus on service orchestration modeling Application Design & Development Stage Best Practice Architects define the service, implementation, properties, interfaces, and bindings. The development team then leverages this service model for developing and modifying the service. SOA Governance and Organizations Best Practice Spur organizational agility by creating teams based on technical capabilities not on projects

Getting There with SOA Lifecycle Project Objectives Develop SOA Roadmap Team Members FTE & PT Timeline & Deliverables 6-12 weeks Initiate SOA Initiate Business Principles Application Principles Technology Principles Data Principles Business Architecture BPM, COTS, etc. Infrastructure Arch Portal, SO, ES, etc. Information Arch MDM, ODS, DW, etc. SOA Principles Reference Architecture Develop Roadmap Based on Biz Priorities Develop SOA Roadmap Execute SOA Roadmap Execute Plan Portfolio Management Project Management Application Infrastructure Data Testing Publish Discover Governance Organization Skills Mapping Review and Update Roadmap

SOA Lifecycle Initiate SOA Develop Roadmap Execute SOA Roadmap Establish the process for getting started Establish objectives, project teams, timelines, deliverables, etc. Develop Roadmap Establish SOA Principles Develop Reference Architecture Develop SOA roadmap based on business priority Execute SOA Roadmap Initiate Enterprise Transformation in Business and IT by establishing SOA Governance Manage Services Portfolio and execute roadmap Revise and update roadmap on a periodic basis, based on internal and external environmental changes

SOA Reference Architecture Approach SOA Foundation Components Business Architecture Infrastructure Architecture Data Architecture Information Architecture Complementary Disciplines (MDA, EDA, CEP, BPM) SOA Maturity Model

SOA Maturity Model enables enterprises to develop the roadmap to achieve “Future Vision” A Three Stage Model Phase 1: Develop Web Applications demonstrate “quick wins” to business by rapidly deploying new business solution by reusing services Phase 2: Develop composite applications such as single view of the customer or automate integration points between systems Phase 3: Automate Business Processes across the enterprise or LOB/Agency It is not necessary to exit one stage to start the next

SOA Enterprise Reference Architecture – “Future State Architecture” Establish Business Capabilities in Three Tiers Web Application Tier Multi-channel web presence for the enterprise Service Tier Service lifecycle management, Service discovery and composition capability Services that cross application boundaries Application Tier Traditional legacy or mainframe applications and EAI SOA Framework Design of an enterprise-wide SOA implementation Architecture diagrams, component descriptions, detailed requirements, design patterns, opinions about standards, patterns on regulation compliance, standards templates)

Mapping SOA Reference Architecture to the Enterprise SOA Maturity Model Traditional Development Develop Web Applications Composite Applications Automate BP Enterprise Service Bus: Route services to the appropriate destination; receive and transmit messages in any protocol, provide message transformation, routing, validation, auditing, security, monitoring and reporting services. Enterprise Services: Basic services required across the enterprise. Examples: Directory Service, Content Management, Search, eMail, Calendar, IM, Discussion Forum, White Board, etc. Business Process Manager: Configure and automate business process. Provide business users the capability to modify the business process & policies. Shared Data Services: Extract, Transform & Load (ETL), Electronic Data Interchange (EDI), Enterprise Information Integration Data Quality (Matching Engine, Master Data Management) Enterprise Application Integration: Traditional enterprise integration approach. Provide Application Adapters, Business Process, Messaging, Security, etc. capabilities. Mostly proprietary in nature and application integration generally implemented as a point-to-point integration on a Hub.. Packaged Applications (COTs): These are the best of the breed packaged application that also act as the system of record for a particular business function. Custom Applications: These are either built on an App Server, Portal or proprietary thick client. Application Framework required to leverage reuse. Examples: Logging, Exception handling, data services, application configuration, monitoring, search framework, notification framework, service proxy, Single Sign-On Service Registry: Service registry containing service properties such as service capabilities, parameters, service levels, etc. Service Manager: Manage service lifecycle across the enterprise. Business Service Management: Monitoring, capacity planning, utility computing Enterprise Portal: Role based portal that is available 24x7. Provides single point of entry for all users, multi-channel support, consistent look and feel, access to business capabilities based on role. Enterprise Security: Provide user authentication, authorization, identify management, profile management, delegated admin, etc. Mainframe Application : Access data via gateways Legacy Application: Applications that do not have open APIs & are not web based

Where to find SOA Practitioners’ Guide SOA Reference Architecture published at the Global Integration Summit held at Boston in May 2006 Three part SOA Practitioners Guide published at the BEA World held at San Francisco in September 2006 http://dev2dev.bea.com/pub/a/2006/09/soa-practitioners- guide.html) Living Document at http://soaalliance.jot.com/MemberPublications which shall be constantly updated based on the SOA Practitioners experience Download at http://www.cellexchange.com/soa

Burc Oral, PhD, CellExchange, Inc. Thanks Ready for Q/A about how to Transform and Modernize your Enterprise with SOA Practitioners’ Guide Burc Oral, PhD, CellExchange, Inc. boral@cellexchange.com http://www.cellexchange.com