SOA Practitioners Guide Best Practices for Enterprise Transformation

SOA Practitioners’ Guide: Best Practices for Enterprise Transformation and Modernization Painting by Surekha Durvasula © Burc Oral, Ph. D, Cell. Exchange, Inc. , Peter Bostrom, BEA Systems 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, W 3 C, 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, Cell. Exchange, Inc. Yogish Pai, Chief Architect Aqua. Logic Composer, BEA Systems, Inc. Tom Sedlack, Enterprise Architecture and Engineering, Sun. Trust Banks, Inc. Dr. Harsh Sharma, Senior Information Architect, Met. Life Sankar Ram-Sundaresan, Chief Architect e-Business, HP-IT SOA Practitioners’ Guide 2 Third Service Oriented Architecture for E-Government Conference, May 1 -2, 2007

The Practitioner’s Guide: A Collective Bo. K 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 SOA Practitioners’ Guide 3 Third Service Oriented Architecture for E-Government Conference, May 1 -2, 2007

traditional approach Business Value soa Different Paths to the Same Future Vision future vision business services (Business) Portals Integration App Server Database COTS packages, etc. current state Process Driven Enterprise Business Priority infrastructure services (IT) Business Complexity IT Priority SOA Practitioners’ Guide 4 Third Service Oriented Architecture for E-Government Conference, May 1 -2, 2007

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 SOA Practitioners’ Guide 5 Third Service Oriented Architecture for E-Government Conference, May 1 -2, 2007

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 6 Third Service Oriented Architecture for E-Government Conference, May 1 -2, 2007

Establish Services Lifecycle Three Stages of Services Lifecycle Governance 1. Accurately capture the Business Requirements business requirements 1 2. Develop the IT solutions to business requirements Service Repository 3 IT Operations service to business 2 requirements Solution Development Governance SOA Practitioners’ Guide 3. Deploy and maintain the 7 Third Service Oriented Architecture for E-Government Conference, May 1 -2, 2007

Services Lifecycle Business Requirements Business Services Business Process BAM Executable Services Service Logic Develop missing services Service Matrix SOA Repositor y 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 Service Assembly Model Approved Services Logical Deployment Srv Srv Submit developed services Prod 1 Prod 2 Portal Prod 3 ESB Prod 1 Prod 2 Data Services Shared DS Infrastructure I&AM Storage SOA Practitioners’ Guide 8 ETL DQ Third Service Oriented Architecture for E-Government Conference, May 1 -2, 2007

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 SOA Practitioners’ Guide 9 Third Service Oriented Architecture for E-Government Conference, May 1 -2, 2007

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 SOA Practitioners’ Guide 10 Third Service Oriented Architecture for E-Government Conference, May 1 -2, 2007

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

SOA Lifecycle 1. Initiate SOA Ø Establish the process for getting started Ø Establish objectives, project teams, timelines, deliverables, etc. 2. Develop Roadmap Ø Establish SOA Principles Ø Develop Reference Architecture Ø Develop SOA roadmap based on business priority 3. 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 Practitioners’ Guide 12 Third Service Oriented Architecture for E-Government Conference, May 1 -2, 2007

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 Practitioners’ Guide 13 Third Service Oriented Architecture for E-Government Conference, May 1 -2, 2007

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 rapidl 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 Practitioners’ Guide 14 Third Service Oriented Architecture for E-Government Conference, May 1 -2, 2007

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) SOA Practitioners’ Guide 15 Third Service Oriented Architecture for E-Government Conference, May 1 -2, 2007

Mapping SOA Reference Architecture to the Enterprise SOA Maturity Model Traditional Development Develop Web Applications Composite Applications Automate BP Enterprise Services: Basic services required across the enterprise. Examples: Directory Service, Content Management, Search, e. Mail, Calendar, IM, Discussion Forum, White Board, etc. 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 Enterprise Portal: Role based portal that is available 24 x 7. Provides single point of entry for all users, multi-channel support, consistent look and feel, access to business capabilities based on role. 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. Business Process Manager: Configure Shared Data Services: Extract, and automate business process. Provide business users the capability to modify the business process & policies. Transform & Load (ETL), Electronic Data Interchange (EDI), Enterprise Information Integration Data Quality (Matching Engine, Master Data Management) Service Registry: Service registry containing service properties such as service capabilities, parameters, service levels, etc. Service Manager: Manage service lifecycle across the enterprise. 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. . Business Service Management: Monitoring, capacity planning, utility computing Enterprise Security: Provide user authentication, authorization, identify management, profile management, delegated admin, etc. SOA Practitioners’ Guide Mainframe Application : Access data via gateways 16 Legacy Application : Applications that do not open APIs & are not web based Third Service Oriented Architecture forhave E-Government Conference, May 1 -2, 2007

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: //dev 2 dev. bea. com/pub/a/2006/09/soa-practitionersguide. html) Living Document at http: //soaalliance. jot. com/Member. Publications which shall be constantly updated based on the SOA Practitioners experience Download at http: //www. cellexchange. com/soa SOA Practitioners’ Guide 17 Third Service Oriented Architecture for E-Government Conference, May 1 -2, 2007

Thanks Ready for Q/A about how to Transform and Modernize your Enterprise with SOA Practitioners’ Guide Burc Oral, Ph. D, Cell. Exchange, Inc. boral@cellexchange. com http: //www. cellexchange. com SOA Practitioners’ Guide 18 Third Service Oriented Architecture for E-Government Conference, May 1 -2, 2007