Price: $2,495.00 [converted to 2495.00 USD]

Early registration expires: Sep 09, 2012

ZapThink SOA Training & Certification: The Leading Vendor Independent, Architect-Focused SOA Training

ZapThink’s Licensed ZapThink Architect (LZA) SOA Training & Certification Boot Camp is recognized around the world as the best single Service-Oriented Architecture training course available anywhere.

The LZA SOA Boot Camp is an intensive, four day “fire hose” of information that prepares you to succeed with your SOA efforts, whether you’re just beginning them or are well down the road with SOA. ZapThink’s LZA SOA Training reflects the best thinking and research that ZapThink produces.

What makes the LZA SOA Boot Camp so special?

• Vendor independent – We discuss vendors in context, both good and bad. You get a balanced perspective on each vendor we discuss.
• Architect focused – The course concentrates on what architects have to do to be successful with SOA in their own organizations. We balance technology details with organizational approaches. If you’re not an architect you’ll learn how to think like one in this class!
• Practical – we connect theory to practice with what really works in organizations like yours.
• Current – we refresh the course on a regular basis to reflect the latest SOA best practices, as well as how SOA relates to other architectural challenges in the enterprise.
• Enterprise context – SOA is an approach to organizing enterprise IT resources to meet changing business needs. We place SOA into the context of large organizations, with complex, heterogeneous IT environments and all the politics and bureaucracy that every large organization faces.
• Globally recognized certification – Everybody who completes the LZA SOA Boot Camp obtains a certificate representing their LZA credential, giving you the right to call yourself a Licensed ZapThink Architect with all the privileges that come along with this exclusive credential.
• Led by globally recognized SOA thought leader – All ZapThink’s courses are developed and led by Jason Bloomberg, ZapThink Managing Partner. Jason has been an analyst with ZapThink since 2001 and is the co-author of Service Orient or Be Doomed!
• Not too technical, not too high-level – Unlike courses offered by others, we cover the technology without getting lost in the details. We discuss the big picture but connect it to the day-to-day reality of the IT shop.
• Available around the world – See the event schedule on this page for all the locations we’re offering the LZA SOA Boot Camp!

Defining SOA

• What is Architecture?
• ZapThink’s Definition of SOA
• Architectural Styles
• SOA Basics

Composability & Business Services
SOA by Any Name
SOA = Best Practices
Iconoclastic vs. Dogmatic Architecture
Thinking Outside the SOA Box

Why SOA?

• Business Drivers for SOA
• When Not to Apply SOA

So, How to Implement SOA?
There’s No Such Thing as a SOA Wizard!
Is SOA New?
XML to the Rescue!
What about Web Services?
Pros & Cons of Web Services
What about REST?
Technical Architecture vs. Enterprise Architecture?Architecture is not About the Technology
Architecting SOA: Beyond Use Cases

SOA Implementation as Complex System

• Examples of Complex Systems
• The Focus of CSE
• CSE: Overall Coherence
• Governance: Architecting People
• Achieving Business Agility

Quality & Complex Systems

• The SOA Quality Star
• Best Effort SOA

SOA as Enterprise Architecture
The Enterprise Context for SOA
Services Thinking
Why is SOA Difficult?

Case Studies: Mini-Studies on SOA

• Information Sharing: FAA
• 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
• Consumers & Providers
• What are Services? (Technically, Service interfaces)
• 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

SOA Design Principle #2: Service Contracts

• What’s a Service Contract?
• Service Contract vs. Service Description

Design Principle #3: Encapsulation

• What’s NOT in the Contract

Design Principle #4: Discoverability

• What are Metadata?
• Metadata for SOA
• SOA Registry as “Discovery Agency”
• Location Independence

Design Principle #5: Reuse

• 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
• Zeroing in on Proper Granularity
• Example: Too Fine Grained vs.Too Coarse Grained
• Service Refactoring

Design Principle #7: Service Autonomy

• Autonomy Issue: Overlapping Functional Control
• Autonomy Issue: Concurrency
• Autonomy Issue: Dependency

Design Principle #8: Loose Coupling

• What about Coupling?
• Full Decoupling?
• Loose Coupling: Separation of Concerns
• Levels of Coupling
• Loose Coupling and Context

Design Principle #9: Statelessness

• Maintaining Process Instance State
• Web Services’ Achilles Heel
• “Stateful Services”

Design Principle #10: Composability

• Metadata-Driven Applications
• Imperative vs. Declarative
• Programmatic vs. Declarative
• Challenges with Declarative Approach

Case Study: ABN Amro

Exercise: SOA Return on Investment

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
• Typical Service Layers
• ZapElectric Service Layer Model

Component & Implementation Models
ZapElectric Logical Architecture Model

Homework: Service ModelClass Ends at 5:00 PM

Day Two

Class Begins at 8:30 AM

Module 4: Intermediaries & Integration

SOA Infrastructure Starting Point: The Intermediary

• Some Intermediary Roles
• Intermediaries and Service Façades

SOA “Magicians’ Tricks”

• Multiple Interfaces per Implementation
• Multiple Implementations per Interface
• Multiple Interfaces per Business Service
• Actualizing the Business Service Abstraction

Intermediaries & Messaging
Buying an Intermediary?

The Great ESB/SOA Middleware Boondoggle

• Buy More Middleware for SOA?
• ESB Federation?
• Difference Between Traditional Integration & SOA
• Compounding the Problem: No Clear ESB Definition
• The ESB Pattern

• Do You need an ESB for Service Mediation?
• Intermediary-Based Service Abstraction
• Another Approach: XML Appliances
• Building Intermediary-Based SOA Infrastructure

SOA Message Exchange Patterns

• SOA Tenet: Asynchrony
• Messages vs. Events

SOA, Integration & Legacy

• The Continued Value of Legacy
• Legacy Migration
• Legacy Enablement
• Legacy Rejuvenation
• Migration vs. Rejuvenation
• Cloud Deployment Choices
• Business Driver: Cost Savings
• Reducing Integration Cost

Case Study: SOA at The Hartford

Module 5: The Role of Data & Semantics

Data: Foundation for SOA
The Data Services Layer
Application Services vs. Data Services
Designing Data Services
Performance vs. Flexibility
Supporting Data Services with Data Integration
Leveraging Data Services Layer
What’s Missing?
Semantic Level Understanding
Role of Application Semantics
Semantics: The Greatest Integration Challenge of SOAStill a Manual Process
Resolving Semantic Issues

Semantic Model Example: Maritime Information Exchange Model

• MIEM Business Case

Best Practices in Industry
Industry-Specific Semantic Standards

Case Study: MyFoodAlerts.com

Module 6: SOA Governance

The Need for Governance
What is Organizational Governance?
How to Tackle Governance?
The Cornerstone of IT Governance is Architecture
Elements of IT Governance Strategy
Architecture Board

What is SOA Governance?

• SOA Governance ”in the Narrow”
• SOA Governance “In the Broad”
• SOA Governance Activities

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
• Supporting Policy Changes
• Decoupling Policies from Services
• Policy Management & Enforcement

Creating the Governance Framework

Extending SOA Governance to the Cloud

Governance Challenge: Reuse = Sharing

• Publishing & Discovery Governance
• Is Reuse a Real SOA Benefit?

Challenge: The Right Amount of Governance

SOA Governance Infrastructure

• Complexities of SOA Governance Marketplace
• What is a Registry?
• What is a Repository?
• The Registry/Repository
• Management & Loose Coupling
• SOA Management: Many Facets
• The Problem with SOA Management
• The SOA Management Conundrum
• SOA Monitoring & Management
• Continuous Quality Activities
• The First Rule of SOA Management

ZapElectric Physical Architecture Model

Case Study: SOA Organizational Change & Funding at Novartis

Exercise: Governance FrameworkHomework: Business CaseClass Ends at 5:00 PM

Day Three

Class Begins at 8:30 AM

Module 7: Service Composition & Business Process

What is a Business Process?
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
What is the Sweet Spot for Service Composition?
SOA Composite Application ExampleEnterprise Applications and Process
Example: SAP NetWeaver

Transactions and SOA

• Compensating Transactions
• Compensating Transaction Example

Case Study: SOA Journey at BP

Module 8: Web Services-Based SOA

Confusing SOA & Web Services
How to Get a SOA
If not Web Services, Then What?

WSDL: Service Contract Starting Point

• WSDL Basics
• Concrete Description
• Abstract Description
• RPC vs. Document Style
• Vendor Bozo Filter
• Contract Metadata Beyond WSDL
• What’s Missing from WSDL?
• Sample Service Contract Template

OASIS Web Services Interoperability Organization (WS-I)
SOAP: Verbose Message Transport
What’s the Deal with UDDI?

Critical SOA Challenge: Security

• Security Fundamentals
• The Context of IT Security
• XML Threat Prevention
• Mitigating XML Threats
• Web Services Security
• WS-Security Tokens
• Security Assertion Markup Language (SAML)
• SAML Assertions
• Federated Security
• Federated Security Illustration
• Message-Level Security: Is SSL Sufficient?
• Core Requirements for Securing Services

Policies

• Policy “Math”
• Computing Effective Policy
• WS-Policy Example
• WS-PolicyAttachment
• Policy Attachment to WSDL 1.1
• Some Policy Standards
• WS-SecurityPolicy Example (Policy & Conforming Message)

Governance Pitfall: Versioning

• Handling Service Versioning
• Versioning Concepts
• Versioning Strategies
• Strict Versioning
• Flexible Versioning
• Loose Versioning
• Versioning Policy Issues

Physical Service Architecture
Three Approaches to State

Web Services Orchestration

• BPEL Example
• Limitations of BPEL
• BPMN to the Rescue?
• BPMN Example
• Limitations of BPMN
• How SOA Fills the Gap
• What about Workflow?
• Workflow & Web Services

Exercise: Service Contracts

Module 9: REST-Based SOA

Problems with Web Services
Definition of REST
Dogmatic REST
REST Myths

Essential REST Terminology

• What is a Resource?
• Uniform Interface
• PUT vs. POST: Initializing a Resource
• What is a Uniform Resource Identifier (URI)?
• RESTful vs. RPC-based URIs
• What is a Representation?
• Negotiating Representation Type
• Content Negotiation
• What is Hypermedia?
• Is REST about APIs?

Architectural Constraints

• Four Architectural Constraints
• Separation of Resource from Representation
• Manipulation of Resources by Representations
• Self-Descriptive Messages
• Hypermedia as the Engine of Application State
• HATEOAS and URIs
• HATEOAS in Action
• Explicit State Transitions in REST

Custom Media Types
Contracted Services

Contract Metadata for REST
Intermediaries & REST
REST Starting Point
Caching Options
Proxy Pattern
Gateway (Reverse Proxy) Pattern
Asynchronous REST

REST Compositions

• REST-Based Orchestration
• REST-Based Choreography
• Choreographing Orchestrations
• Composite Representations vs. Composite RESTful Services
• Everything is a Resource
• Examples of Process Representations
• Example of REST Choreography
• Follow Links to Learn About Processes
• Some Benefits of REST-Based BPM
• RESTful BPM Essential for the Cloud

Scalability & State, The Old Way

• Here’s Your App in the Cloud:
• Here’s How it Works

REST-Based SOA

• Essential REST-Based SOA Policies
• Differences Between Web Services-Based SOA & REST-Based SOA

Case Study: US Coast Guard SPEAR (Semper Paratus: Enterprise Architecture Realization)

Homework: Service CompositionClass Ends at 5:00 PM

Day Four

Class Begins at 8:30 AM

Module 10: 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
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
Service Identification: Top Down vs. Bottom Up
Defining Services Approach
Performance: Chasing the Bottleneck

Implementing Services: Methodologies for change

• The Dual Lifecycle
• The Service Lifecycle
• Advanced Vision for Application Assembly
• Where Should the Code Be?
• The Agile SOA Lifecycle

Top-Down: Analyze Processes

• Process Analysis
• Process Optimization
• Discovering Existing Processes
• Service Identification: Process Decomposition
• Implementing Services
• Defining New Compositions

Technology Selection

• ZapElectric Component Model
• Purchasing SOA Technology
• Technology Selection: Choices

Exercise: SOA Roadmap

Module 11: Addressing SOA Organizational Challenges

Organizational Issues
Common SOA Pitfalls
SOA Growing Pains
Challenges in Calculating ROI
The Problems with “VDA”
Avoid Policy Bloat
Avoid “Checklist Architecture”

Is there an Architect in the House?

• Hiring Architects

EA Challenges: The Role of the EA

• Enterprise Architecture Challenges
• Questions to Ask Your EA

The SOA Consultant Conundrum

• The SOA School Bus
• Are “SOA” Consultants Qualified?

Interaction Challenges

• IT Governance Feedback Loop
• The “Ivory Tower” Problem
• Convincing Technical Specialists
• Working with IT Middle Management

Dealing with SOA Hype and Anti-Hype
Good Money after Bad…
The Power of the SOA Center of Excellence

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

Final Exam: SOA Jeopardy!Class Ends at 3:00 PM

Venue:

Dovel Technologies, Inc.
7918 Jones Branch Drive
Suite 100
McLean, VA 22102