My notes from IBM SOA Architecture Summit

IBM SOA Architecture Summit, Mumbai, 9th May, 2006

SOA Reference Architetcure
- Process
- People
- Information
- Non-functional Requirements
- Manage Environment

SOA Solution Layering

Comsumers
---------------------------

Business Process

---------------------------

Services (Atomic & Composite)

---------------------------

Service Components

---------------------------

Operational Systems

---------------------------

Above is quite similar to RUSA -> APIs -> GeneS -> Products -> Solutions hierarchy

SOA Programming Model Aspects

o Design
- Role Based Collaboration
- Declarative Policy to control execution behaviour
o Invocation
- Loose Coupling
o User Interface
o Composition of Business Level Applications
o Information
o Business Components

SOA Reference Architecture : Key Principles
o ESB
o Component based programming & Solution development
o Service Integration Maturity Model (SIMM)

SOA Adoption Considerations
o Business Drivers
o Organization Readiness
o Current Architecture Environment
o Operational Readiness

SOA Governance
- Catalyst for improving overall IT governance
- IT Governance
- SOA Governance Life Cycle
Plan --> Define --> Enable ->+
+<--------------------------|

Business Driven Development
- Align Technology & Business Priorities
- Improve efficiency & responsiveness
- Address Governance & Compliance requirements

SOA Programming Models
- JavaServer Faces -> for UI
- Service Component Architetcure
- Service Data Objects
- Business Process Execution Language

SOA Governance - Challenges
o Establish Decision Rights
- Funding & Ownership of shared services
- Execution Committee
- Organization Change
o Define high value business services
o Managing life-cycle of assets
o Measuring effectiveness