LZA SOA Boot Camp Version 8.0

Day 1

Module 1: The Enterprise Context for SOA

• Business Constant: Change
• The Voice of Doom?
• Business Agility
• Defining SOA
• Why SOA?
• Business Drivers for SOA
• When Not to Apply SOA
• The Distributed Computing Pendulum
• SOA: Paradigm Shift?
• So, How to Implement SOA?
• Is SOA New?
• One Difference is Web Services
• Confusing SOA & Web Services
• How to Get a SOA
• If not Web Services, Then What?
• What is Architecture?

• Architecting SOA: Beyond Use Cases
• SOA Implementation as Complex System
• Examples of Complex Systems
• The Focus of CSE
• CSE: Overall Coherence
• SOA as Enterprise Architecture
• The Zachman Framework
• Pros & Cons of Zachman
• Services Thinking
• Why is SOA Difficult?
• Case Studies: Mini-Studies on SOA Use

  • Shared Services: US PTO
  • Reducing Integration Costs: Aeroplan
  • Compliance & Volume: .Wells Fargo Bank
  • Meeting Client Needs: MITRE

Module 2: SOA Design Principles

• Design Principle #1: Abstraction
  • What’s a Service?
  • Levels of Service Abstraction
  • Service as Interface & Implementation
  • Interoperability vs. Portability
  • Service Interfaces Aren’t Good Enough!
  • Abstractions: Simple on the Outside
  • Abstraction = Working Illusion
  • Building a Working Illusion
  • The Fundamental Technical Challenge of SOA
  • Multiple Interfaces per Implementation
  • Multiple Implementations per Interface
  • Multiple Interfaces per Business Service
  • Actualizing the Business Service Abstraction
• SOA Design Principle #2: Standardized Service Contract
  • What’s a Service Contract?
  • Consumers & Providers
  • WSDL: Service Contract Starting Point
  • WSDL Basics
  • Contract Metadata Beyond WSDL
  • What’s Missing from WSDL?
  • Sample Service Contract Template
• Design Principle #3: Encapsulation
  • What’s NOT in the Contract
  • Physical Service Architecture
• Design Principle #4: Discoverability
  • What are Metadata?
  • Metadata for SOA
  • SOA Registry as Discovery Agency
  • Location Independence
  • Design Principle #5: Reusability
  • Reusability vs. Usability
  • Achieving Reusability: Service Agnosticism

• • Designing for Reuse:Agnostic Context
  • Reuse over Time
• Design Principle #6: Granularity
  • Key Service Abstraction Enabler: Proper Granularity
  • Granularity Example
  • Achieving Proper Granularity
  • Example: Too Fine Grained vs.Too Coarse Grained
  • Service Refactoring
  • Refactoring Scenario
  • After Refactoring
• Design Principle #7: Autonomy
  • Autonomy Issue: Overlapping Functional Control
  • Autonomy Issue: Concurrency
  • Autonomy Issue: Scalability
  • Autonomy Issue: Dependency
  • Composition Autonomy: Problem
  • Composition Autonomy: Solution
• Design Principle #8: Loose Coupling
  • What about Coupling?
  • Full Decoupling?
  • Loose Coupling: Separation of Concerns
  • Levels of Coupling
  • RPC vs. Document Style
  • Loose Coupling and Context
• Design Principle #9: Statelessness
  • Maintaining Process Instance State
  • Three Approaches to State
  • Stateful Services
• Design Principle #10: Composability
  • Metadata-Driven Applications
  • Programmatic vs. Declarative
  • Challenges with Declarative Approach
  • Introducing “SOBA”

Module 3: The SOA Reference Architecture

• What is a Reference Architecture?
• Recommended SOA Reference Architecture Structure
• What’s Different about a SOA Reference Architecture?
• End-to-End Architecture: The SOA Metamodel
• SOA Foundation: Model-Driven Architecture
• SOA Foundation: The 4+1 View Model
• The 4+1 View Model & .The SOA Metamodel
• The Agility Model
• Service Architecture
• Building the Service Model
• Introducing “ZapElectric”

• ZapElectric Service Model
• Entity Services
• Task Services
• Utility (IS) Services
• Service Relationships Example
• Process Isomorphism
• Service Layers
• ZapElectric Service Layer Model
• Component & Implementation Models
• ZapElectric Logical Architecture Model

Day Two

Module 4: Intermediaries & Integration

• SOA Infrastructure Starting Point: The Intermediary
• Some Intermediary Roles
• Intermediaries and Service Facades
• Intermediaries & Messaging
• Buying an Intermediary?
• Don’t we just mean an Enterprise Service Bus?
• The Great ESB/SOA Middleware Boondoggle
• Buy More Middleware for SOA?
• ESB Federation?
• Compounding the Problem: No Clear ESB Definition
• The ESB Pattern
• Do You need an ESB for Service Mediation?
• Intermediary-Based Service Abstraction
• Building Intermediary-Based SOA Infrastructure
• SOA Message Exchange Patterns
• SOA Tenet: Asynchrony
• Messages vs. Events
• Business Driver: Visibility
• Visibility & Heterogeneity
• SOA, Integration & Legacy
  • Exposing Existing Capabilities
  • The Continued Value of Legacy
  • Legacy Migration
  • Legacy Enablement

• • Legacy Rejuvenation
  • Migration vs. Rejuvenation
  • Business Driver: Cost Savings
  • Reducing Integration Cost
• SOA & Data
  • Data: Foundation for SOA
  • The Data Services Layer
  • Application Services vs. .Data Services
  • Application Services abstract application APIs
  • Application-centric .transactionality
  • Data Services abstract data queries
  • Designing Data Services
  • Performance vs. Flexibility
  • Supporting Data Services with Data Integration
  • Leveraging Data Services Layer
  • Semantic Level Understanding
  • Role of Application Semantics
  • Sample Semantic Model
  • Semantics: The Greatest Integration Challenge of SOA
  • Still a Manual Process
  • Resolving Semantic Issues
  • Industry-Specific Semantic Standards
• Case Study: SOA at The Hartford

Module 5: Service Composition, Business Process, & SOBAs

• What is a Business Process?
• The Automation Paradox
• Problems with Traditional BPM Tooling
• Business Process the Enterprise Application Way
• Business Process the Service-Oriented Way
• Service-Oriented Process
• Process Definitions
• Example: Orchestration vs. Choreography
• Web Services Orchestration Standard
• BPEL Example
• Limitations of BPEL
• BPMN to the Rescue?
• BPMN Example
• Limitations of BPMN
• How SOA Fills the Gap
• What is the Sweet Spot for SOBAs?
• SOBA Example

• Enterprise Applications and Process
• Example: SAP NetWeaver
• Transactions and SOA
• Transactions the .Loosely-Coupled Way
• Compensating Transactions
• What about Workflow?
• Workflow & SOA
• Ad Hoc Processes
• Mashups: Situational Apps for SOA
  • Data Mashup Example
  • Process Mashup in Action
  • Process vs. Data?
  • The Long Tail: Applications
  • The Enterprise 2.0 Long Tail
  • Without Governance, Mashups are Dangerous
  • Without SOA, .Mashups are Toys
• Case Study: SOA Journey at BP

Module 6: XML Infrastructure & Security

• Challenges at the Content Level
• Is XML Required for SOA?
• What about REST?
• XML: Foundation for Web Services
• The XML Processing Problem
• The XML Performance Crisis
• Solution: XML Appliances
• XML Firewall
• Intermediary Processing Challenges
• Performance analysis: where is the bottleneck?
• Critical XML Processing Challenge: Security
  • The Context of IT Security
  • The Open Systems Security Challenge
  • XML Threat Prevention
  • Mitigating XML Threats
  • WSDL protection

• • XML Firewalls
  • XML Encryption
  • Encryption provides confidentiality
  • XML Digital Signature
  • Message-Level Security: Is SSL Sufficient?
  • Core Requirements for Securing Services
  • Web Services Security
  • WS-Security Tokens
  • Security Assertion Markup Language (SAML)
  • SAML Assertions
  • Federated Security
  • Federated Security Illustration
  • The Security Context Challenge
  • Solving the Security Context Challenge: Single Sign-On
  • The Role of Entitlement Management
• Case Study: SOA Security in the Real World — BP

Module 7: SOA Governance, Quality & Management (Part 1)

• The GQM Loop
• Corporate Governance
• Governance & Regulatory Compliance
• The Business Motivation for Governance
• How to Tackle Governance?
• Governance Relationships
• The Cornerstone of IT Governance is Architecture
• Elements of IT Governance Strategy
• What is SOA Governance?

• SOA Governance “in the Narrow”
• SOA Governance Activities
• Tiers of SOA Governance
• Enterprise/Strategic IT Governance
• SOA Operating Model .Governance
• Enterprise/Strategic IT Governance
• SOA Operating Model Governance
• Services Governance

Day Three

Module 7: SOA Governance, Quality & Management (Part 2)

• What is a Policy?
  • Policy “Math”
  • Computing Effective Policy
  • WS-Policy Example
  • S-PolicyAttachment
  • Policy Attachment to WSDL 1.1
  • Policy: Business vs. .Technical Examples
  • Design Time Policy Examples
  • Run Time Policy Examples
  • Change Time Policy Examples
  • The Challenge of Policy Automation
  • Steps for Automating Policies
  • Some Policy Standards
  • WS-SecurityPolicy Example
  • Supporting Policy Changes
  • The Policy Lifecycle
  • Policy Lifecycle: Architect
  • Policy Lifecycle: Administrator
  • Policy Lifecycle: PEP
  • Policy Lifecycle: Operations
  • Policy Management & Enforcement
• Creating the Governance Framework
• SOA Asset Management
• Consumer Management
• Design Time Governance
• Publishing & Discovery Governance
• Sample Publishing/Discovery Governance Processes
• Governance Challenge: Reuse = Sharing
• Is Reuse a Real SOA Benefit?
• Run Time Governance
• SOA Monitoring & Management
• Checkpoints
  • Analysis Checkpoint
  • Design Checkpoint
  • Implementation Checkpoint
  • Operational Readiness Checkpoint

• Governance Pitfall: Versioning
  • Handling Service Versioning
  • Versioning Concepts
  • Versioning Strategies
  • Strict Versioning
  • Flexible Versioning
  • Loose Versioning
  • Versioning Policy Issues
• Governance Pitfall: Interoperability
  • Web Services Interoperability Organization (WS-I)
  • Tool Interoperability: Governance Interoperability Framework (GIF)
  • GIF Capabilities
  • Tool Interoperability: CentraSite Community
  • CentraSite Community Members (Partial list)
• SOA Quality
  • Quality & Complex Systems
  • Policy Enforcement: Quality
  • Continuous Quality Activities
  • SOA Quality Organization Example
  • The Long-Term Challenge of SOA Testing
  • Testing in Production?
  • The SOA Quality Star
  • Best Effort SOA
• SOA Governance Infrastructure
  • Complexities of SOA Governance Marketplace
  • What is a Registry?
  • What’s the Deal with UDDI?
  • What is a Repository?
  • The Registry/Repository
  • Management & Loose Coupling
  • SOA Management: .Many Facets
  • The Problem with SOA Management
  • The SOA Management Conundrum
  • The First Rule of SOA Management
  • ZapElectric Physical Architecture Model
• Case Study: SOA Project Management & Governance – T-Mobile

Module 8: Planning & Running the SOA Initiative

• How Do You Eat an Elephant?
• Iterative: More than Step-by-Step
• Iterate your Architecture?
• Project Management for a SOA Project
• Defining SOA Roadmap
• Initial Assessments
• Building Support for SOA
• Building the SOA Business Case
• Milestone / KPI Plan
• The SOA Roadmap
• The ZapThink SOA Roadmap
• ZapElectric SOA Roadmap
• SOA Maturity Models
  • Analogous to CMMI
  • SOA Maturity Model Pointers
  • Using a SOA Maturity Model
  • SOA Maturity Model: HP
  • SOA Maturity Model: Wipro
  • Open Group Service Integration Maturity Model (OSIMM), .from IBM
  • “SOA” Maturity Model – Sonic/Systinet
  • SOA Maturity Model: Oracle
  • SOA Maturity Model: Software AG
• Define Initial Iteration

• SOA Pilots
• Implementation Planning
• Bottom Up/Top Down
• Service Identification: Top Down vs. Bottom Up
• Defining Services Approach
• Implementing Services: Methodologies for change
• The Dual Lifecycle
• The Service Lifecycle
• Advanced Vision for Application Assembly
• Where’s the code?
• The Agile SOA Lifecycle
• Top-Down: Analyze Processes
• Process Analysis
• Process Optimization
• Discovering Existing Processes
• Service Identification: Process Decomposition
• Implementing Services
• Defining New SOBAs
• Technology Selection
• ZapElectric Component Model
• Purchasing SOA Technology
• Technology Selection: Choices

Day Four

Module 9: Addressing SOA Organizational Challenges

• Organizational Issues
• Common SOA Pitfalls
• SOA Growing Pains
• The Wrong Question!
• Challenges in Calculating ROI
• Achieving Business Agility
• The Problems with “VDA”
• Challenge: The Right Amount of Governance
• Avoid Policy Bloat
• SOA by Any Name
• SOA = Best Practices
• Thinking Outside the SOA Box
• Dealing with SOA Hype and Anti-Hype
• Is there an Architect in the House?
• Hiring Architects
• EA Challenges: The Role of the EA
• Enterprise Architecture Challenges
• Questions to Ask Your EA
• Good Money after Bad
• The SOA Consultant Conundrum
• The SOA School Bus
• Are “SOA” Consultants Qualified?
• IT Governance Feedback Loop
• Interaction Challenges
• The Ivory Tower Problem
• The Power of the SOA Center of Excellence
• Convincing Technical Specialists
• Working with IT Middle Management
• Enabling Service Domains

• Service Domain Roles
• SOA Funding Models
  • Traditional IT Funding: Project Based
  • Initial SOA Funding
  • Funding Cross-Departmental SOA Initiatives
  • CapEx vs. OpEx
  • Budget Workarounds
• Case Study: ABN Amro
• Staffing
  • Building the right SOA team
  • Core SOA Governance Team
  • Architecture Board
  • SOA Steering Committee
  • SOA Architecture Team
  • Business Process Team
  • Infrastructure/Operations Team
  • Data Services Team
  • SOA Project Staffing
  • Project Leader
  • Data Specialists
  • Security Specialists
  • Legacy Systems Specialists
  • Service Development Specialists
  • BPM/Composition Specialists
  • Governance Tooling Specialists
  • Testing & Deployment Specialists
  • Project Archivists/Cybrarians
  • External Services Specialists
• Case Study: SOA Organizational Change & Funding @ Novartis

Module 10: Architecting with the Cloud

• Cloud Computing: Old Wine in New Bottles
• Formal Definition of Cloud Computing
• Essential Cloud Characteristics
• Cloud Service Models
• Cloud Deployment Models
• Vendor Spin
• Oracle’s Shopping List
• IBM’s Shopping List
• Cutting Through the Hype
• Cloud Computing Roadmap
• EA Cloud Strategy
• Cloud Service Lifecycle
• Capabilities Design Pattern
• Relationship between Cloud & SOA
• Cloud Deployment Choices
• Services as a Service

• Managed Hosting vs. Cloud Computing
• Some Cloud Realities
• Cloud Governance
  • SOA Governance & Cloud Synergies
  • Cloud: Raising the Governance Bar
  • Governance-Related Cloud Issues
  • Cloud Governance Challenges
  • Extending SOA Governance to the Cloud
  • Cloud Governance Pitfalls
  • Dealing with Cloud Reliability Example: Amazon EC2
  • Cloud Governance as VM Governance
  • Rogue Clouds
  • Cloud Governance: Run Time Considerations
  • Cloud Availability & Failover
  • Cloud Governance Technology
  • Cloud Governance Checklist