SOA Today: How to get Started on an SOA Journey and Achieve Rapid Results Jordan Braunstein Business Solutions Group Rolta TUSC October 28, 2009
Myth #1: Business is Constant Customer Demands Changing Marketplace Re-Organization New Leadership Corporate Regulations New Legislation Optimizing Processes New Technologies TUSC Opinion: A PRACTICAL SOA & Modernization Approach can enable legacy, ERP, and silo data stores to share information for the benefit of the business. 2
SOA Concept Composite Apps Business Processes Retrieve Data Verify Details Order Entry Order Review Order Management Approve Order Initiate Shipment Business Service Orchestration Customer Information Order Management Order Compensation Data Services Legacy Systems Customer Data Customer Interaction Order History Order Policy Shipment Customer Data CRM ERP Orders Logistics 3
The new delivery model: digital business Break down silos: Architect and digitize the business Order-to-cash Business and IT as one thing Executive portal Concept-toproduct Trouble-toresolution Requisitionto-payment Sales process portal Service process dashboard Product developer desktop Financial workstation Fulfillment workbench Field service device Business services Update customers Submit orders Schedule shipment Finalize compensation Merge accounts Order supplies Virtualized enterprise data Customer Contracts Products Inventory Accounts 4
Traditional Approaches to SOA aren t working Difficult Planning Cycles Organizational Confusion Cumbersome Methodologies Business Distrust Lack of Current State Awareness Deployment lag Lack of Agility Risk of non-compliance Increased biases Increased Business risk Broken Systems Rogue Employees Political Alliances Increased turnover Loss of Knowledge Decrease Morale Reduced-buying Shifting cultures Increased Resource Cost Increased Software Cost Longer deployment lag times Project delays Project cancellation Difficult Messaging Lack of awareness Reduced Cooperation Cross-Dept. infighting Business Process Failures Customer dissatisfaction Misguided Focus False Vision & Future State Lack of Control Improper Roadmap 5
Traditional: over the wall delivery model Requirements Business Design the business: Business metrics Transaction entry Process efficiency Adapt to application silos IT Build to requirements: Order taker Project delivery Technology usage Give them what they ask for 6
What percentage of software is never or rarely used? 7
8
Comparisons of Approaches Traditional SOA SOA-Today Jump Start Non-SOA Approach Approach 1. Define all your Business Processes 2. Define all Governance policies 3. Implement Technology Stack Approach 1. Prove viability of SOA (1-3 week) 2. Get Business Requirements 3. Build Services Rapidly Approach 1. Build IT Infrastructure & Stack 2. Build vendor driven Integrations 3. Revise to Business Needs Results Cumbersome SOA 1-3 year ROI Business must wait Results Quick SOA 1-3 month ROI Business Aligned Results IT Driven; Upfront costs Lacks Agility Where s the business? 9
The Agile Manifesto Individual Interactions (over processes and tools) Working Software (over comprehensive documentation) Customer Collaboration (over contract negotiation) Responding to Change (over following a plan) 10
A Potential SOA Manifesto Architecture driven (over product implementation) Integrated Systems, Processes, People (over individual silos) Business Visibility and Understanding (over IT priorities) Re-usability (over redundant efforts) Standards and Governance (over non structure) Agility and Adaptability (over non flexibility) 11
SOA and Agile Similarities Focus on the business Built for change Incremental structure Keep it Simple Collaboration is King Team dictates success Decomposition 12
Agile Approach Efficient development Build services in minutes! Integrate with business app easily Improve services usage Collaborative with business client Metrics select the best, delete the rest Reduces risk Shorter time-to-solution Simple approach Built-in precision tuning REVISE Show the user and get immediate feedback RAPID DELIVERY Metrics Selection TRY Integrate into simple display tools BUILD Quickly create or change services to expose data and processes 13
Why use Agile on SOA Quicker Feedback from business team Ensure Business & IT Alignment Production ready code is built faster, shorter iterations Improved Quality Flexibility Faster Time to Market Reduced Waste Increase in Predictability Better Morale 14
Adoption Path First Experiments 1-5 Services What is it? Can we use it? Pilot Projects 5-10 Services Prove it Standards solidify Enterprise Framework 10-50 Services Corporate-wide approach Optimized Business Services 50+ Services B2B II Federated systems Large organizations 15
SOA is not just webservices SOA is about expediting business processes via services while EAI is traditionally about data integration via near-real time messaging (i.e., EAI connects silos, SOA breaks them apart) SOA webservices The business orchestration of SOA is the real driver to the reusability strategy, agility and flexibility. Service orchestration brings to an enterprise a business process model that can significantly improve the flexibility and agility with which business processes are remodeled in response to changes. 16
Principle: Standards Standard way to work with other devices Standard way to plug in anywhere My phone works at your house A phone from overseas can work here with an adapter Standard way to address other systems (703-555-1212) Architecture enriches experience with additional services Caller ID Voicemail Call Waiting Additional features can be added (and ignored) Vendor Independent Doesn t matter what kind of phone I have Doesn t matter how old my phone is 17
SOA borrows from other disciplines SOA shares characteristics with many established disciplines and draws upon these disciplines Strategy development and transformation planning Managing a portfolio of IT-related business investments, shared services, and shared information Enterprise Architecture Executive commitment Stakeholder alignment, communication and training User/COI facilitation Planning and management across multiple projects, agencies and organizations Program Mgmt SOA Change Mgmt Design, development, testing and deployment of IT Governance Rqmts Mgmt SDLC Business Services Technical Services Composite Apps Shared Infrastructure Enterprise-wide management of Portfolio of Shared Infrastructure Change Control Quality Assurance Disciplined approach to gathering, validating and managing business, mission and technical rqmts 18
Governance Connectivity Infrastructure System, Error, Transaction Monitoring Data Analytics (BAM) Transactional & Journal Logging Business Process Management & Modeling Security Identification Validation Mapping & Data Model Transport Transaction Management Translation Business Rules Interface Integration Practices 19
Recommended SOA Approach 1. Assessment Define target functional requirements, business strategy, Define status and expectations Build a Roadmap; adapt infrastructure and governance, plan how to reach the target maturity 2. Define goals and means Select pilot, evaluate technology, implement it and assess results 4. Define rollout and Governance plan 3. Select and execute pilot project Spread SOA throughout the organization and reach target maturity 5. Execute rollout plan 20
Does Governance Matter? 21
Governance does Matter Governance provides Authorities and responsibilities Clear rules and rule enforcement Organizational and technical transparency SOA Governance allows to Master complexity of IT Support business process change SOA Governance saves businesses time and money 22
Single Version of the Truth <many to many> growth <many to one> growth 400 400 350 300 250 200 150 100 50 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 350 300 250 200 150 100 50 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 # of Connections # of Connections results in lower total cost of ownership 23
SOA is collaberative Strategy & Roadmap Requirements Reference Architecture Transformation Plan Implementation Plan Guidelines Best Practices Policies Technical Standards Data Exchange Stds Center of Excellence Quality Assurance Service Certification Organization B System Organization A System Governance Committee PMO COIs Communication Training Organization C System Stakeholders Affiliated Orgs/Systems Architects Developers/Integrators Testers System Admin Interfaces/Contracts Service Requesters Service Providers Shared Services Shared Data Shared Infrastructure MOUs/MOAs/SLAs Operational Metrics Governance can encompass all aspects. However, the actual scope depends on the organization. 24
The SOA Team Typically 5-10 people Cross-functional -- QA, Programmers, UI Designers, etc. Members should be full-time -- May be exceptions (e.g., System Admin, etc.) Teams are self-organizing -- Ideally, no titles but rarely a possibility Membership can change only between iterations 25
baby steps 26
step one get into the flow 27
time-boxedrhythm of high-quality value delivery 28
sustainable achieve a pace 29
command and control 30
Advisory Services SOA School Not Difficult to get started 2-5 business services Comprehensive Design Demonstrate Re-usability Increment 4: Technical Services SOA Jumpstart SOA Jump Start Current State Gap & Maturity Analysis Roadmap Increment 1: Requirements Workshop TUSC SOA Framework Increment 3: SOA Assessment Organizational Review Scoping Document Our Understanding Innovative Services Increment 2: SOA Boot Camp SOA 101 Concepts Business Drivers IT Drivers Why SOA 31
Learn more about Rolta s Agile SOA Solutions! www.soa-today.com http://soa-today.blogspot.com Twitter: SOAToday 32
33