Understanding and Applying SOA for Business Analysts

This version of Understanding and Applying SOA is currently available for on-site presentation only.  
Get a quote for an on-site presentation. 
Related Seminars
Business Analyst Guide to SOA
Overview and Objectives 
This one-day seminar introduces the Services-Oriented Architecture from the perspective of the Business Analyst… the person who will obtain business requirements and design the SOA business application components. 
The seminar explains both the theory and reality of this important standards-based application framework and strategy for business application agility, integration and sharing of common business processes. Specifically tailored to meet the needs of Business Analysts new to SOA, seminar participants receive a comprehensive and independent overview of SOA that covers foundation concepts and facilities, as well as implementation strategies and issues.
Participants learn how SOA works and how the SOA approach adds business value via the deployment of shared and reusable application services in an open, platform-independent environment.  Topics include:
  • What’s a Service? 
  • What’s a SOA?  How does it work and why is it different? 
  • How do organizations typically evolve through the stages of SOA implementation? 
  • When and how should organizations use the SOA approach?
The seminar defines the typical SOA implementation phases and shows how organizations can begin with local, limited scope SOA usage and evolve to B2B Enterprise SOA, with special emphasis on the design issues at each stage on the SOA Journey:
  • Phase 1: Mashups, data integration and wrapping Legacy code with SOA interfaces
  • Phase 2: Internal SOA using collections of shared Web Services 
  • Phase 3: External SOA for B2B process interoperability
The seminar uses non-technical language, models and graphic illustrations to explain the components of Services-Oriented Architecture, including:
  • What’s a Web Service? 
  • What role does XML play in SOA? 
  • What do “abstraction”, “externalization” mean, and how do they promote agility?
  • What do “loosely-coupled” and “cohesion” mean and how do they promote agility? 
  • What are WSDL and SOAP, and how do they work together? 
  • What’s Coordination? Choreography? Orchestration? How do they work? 
  • What’s an Enterprise Service Bus? What does it do? When do you need one?
Who Should Attend?
This seminar is desinged for Business Analysts and business area staff who will design SOA applications composed of Web Services and automated workflows.

This seminar will serve as "SOA 101", building a solid conceptual foundation for more advanced Business Analyst skill-building classes, such as Service-Oriented Analysis & Design (SOAD).
Recommended participants include:
  • Business Analysts and business area staff who will design SOA applications comprised of Web Services and automated workflows
  • Project Leaders and Managers who will guide SOA application design projects
What You Will Learn

What is SOA?
  • What’s a Web Service and what’s their value?
  • What makes a shareable and reusable Web Service different?
  • How do transactions aggregate into Web Services and choreographed business processes?  
When and why would you use SOA?
  • What are the typical SOA implementation stages?
  • How does SOA support application flexibility, agility, scalability and quality?
  • What business scenarios are best for the SOA approach?
  • How does SOA help you address platform and application integration? 
How do you build a Services-Oriented Architecture?
  • How do Web Services work?
  • What makes “loosely-coupled” so good and “tightly-coupled” so bad?
  • What open standards does SOA rely on? Is there more than SOAP and WSDL?
  • What’s a Service Contract Language and why are they needed? 
What’s an Enterprise Service Bus (ESB)?
  • When and why would you need to add a middle-layer?
  • What does an Enterprise Service Bus do?
  • How is the middle-tier implemented in J2EE? In .NET?
  • What’s Coordination? Choreography? Orchestration? Are they the same?
  • What’s BPEL and how does it work?
Part 1 - SOA Definition & Philosophy- What is it? Why would you do that?
  • Case Study Demonstration
  • Service Example (Automotive Work Order)
  • Definitions & Philosophy: Principles, Concepts & Facilities
    - Service
    - SOA Definition
    - Service Sharing & Reuse
    - Agility
  • SOA Evolution: From Mashup to Enterprise Strategy
    - Service Scope: Mashups, EAI, Wrapping, Service Collections, Coordinated Processes
    - Enterprise Scope: Department, Division, Organization, Trusted Partner, Public
    - Implementation Stages: Pseudo-SOA, Tactical Web Services, Internal SOA, External B2B SOA
  • Multi-Dimensional Approach: Technology, Methodology & Sociology
Part 2 - Architecture Overview- Basic SOA for Tactical Web Services

  • SOA Framework: Original and Current
    - Architecture Components: From the Web and XML to Coordinated Workflows running on ESBs
    - Composite Application Architecture: From Requester-Server-Consumer to Find-Bind-Execute
  • Web Service Technologies and Approaches: What’s different?
    - Component Coupling: Tightly-coupled vs. Loosely-coupled
    - Cohesion: Why more is (usually) better
    - Request/Result Transport: Asynchronous messaging vs. Synchronous RPC
  • Key Web Service Interoperability Standards, APIs and Protocols
    - Find: Registration & Discovery via UDDI and Federated Registries
    - Describe: Metadata via WSDL
    - Connect: Establish Addressability via HTTP etc.
    - Transact: Function Request-Response SOAP
    - Transform: XML XSLT
  • Composite Application Architecture Revisited: Real-World Partitioning and Structures
Part 3:  Enterprise SOA- Evolution of the Middle Layer

  • Architecture Drivers: What’s different?
    - Complex workflows… Long-lived and parallel threading
    - Distributed workflows… Multiple servers, domains & organizations
  • 3-Layer SOA Composite Applications
    - Application layer functions: Logic, automated workflow, presentation
    - Coordination layer functions: Coordination, state, reconciliation, compensation
  • Business Process Coordination, Choreography and Orchestration
    - Sequencing, selection and execution of web services
    - Event handler or trigger
    - Maintain the State of the business process
  • Business Process Execution Language (BPEL)
    - Business process articulation
    - Workflow scripting
    - WSDL extensions
  • ESB: Enterprise Service Bus
    - Definition and Description
    - Features and Capabilities
    - Local or temporary storage of attribute values
    - Marshal and consolidate data between services
    - Format outputs
  • Middle Layer Implementation
    - J2EE architecture
    - .NET BizTalk architecture
Part 4 - Thinking About SOA

  • What’s different technically?
    - Loose Coupling
    - Asynchronous Messaging
    - Coarse Granularity
  • Architecture and Performance Issues: What price agility?
    - Abstraction and granularity options
    - Application and business process design impacts
    - Performance vs. flexibility
  • Core Principles
    - How business requirements drive architecture drive solutions