Nitin SinghalSOA Tech Sales
SOA and Enterprise Architecture:A Natural Convergence
2
Agenda
• Enterprise Architecture … why should we care?• SOA and Enterprise Architecture• Best Practices for Enabling SOA at the Enterprise• Summary
Enterprise ArchitectureBridges the Gap Between Business and IT
Enterprise Architecture
Transition Plan
EA Governance
Business Operating Environment and IT Infrastructure
IT Solutions
Information Technology
Strategy
BusinessStrategy
Business Opportunity
Strategy
Planning
Design and Delivery
TechnologyAvailability
En
terp
rise
wid
e fo
cus
Pro
jec
t f
ocu
s
Business Architecture Processes Information
People
IT Architecture Applications
Information
Technology
EA is more than Architecture
5
Solution Architectures(many, including SOA)
Solution Architectures(many, including SOA)
Business ModelIntent (strategies, drivers, principles, plans),
Value (products & services),Capabilities, Business Processes, Information Model,
Business Roles & Locations, ...
Business ModelIntent (strategies, drivers, principles, plans),
Value (products & services),Capabilities, Business Processes, Information Model,
Business Roles & Locations, ...
Enterprise ArchitectureBusiness, Applications, Information,
Technical, Governance
InformationInformation
ApplicationsApplications
Infrastructure Infrastructure
Governance
Architecture Management Framework
Leadership
Sponsorship
Ownership
Resources
Charter
Structure
Vision
Principles
Roles & Responsibilities
Processes
NFRs
Roadmaps
Metrics
…
Governance
Architecture Management Framework
Leadership
Sponsorship
Ownership
Resources
Charter
Structure
Vision
Principles
Roles & Responsibilities
Processes
NFRs
Roadmaps
Metrics
…
Business Environment(external influences)
Customers, Regulators, Market, ...
Business Environment(external influences)
Customers, Regulators, Market, ...
AssetsAssets
UpdateUpdate
ReuseReuse
influences value
influences
influences
influences feedback
feedback
feedback
People, Process,
Technology
Architecture Models
Reference Architectures
Infrastructure
Packages
Tools & Processes
Services
Skills
…
Solution Architectures(many, including SOA)
Solution Architectures(many, including SOA)
Solution Architectures(many, including SOA)
Solution Architectures(many, including SOA)
EA Context
6
Agenda
• Enterprise Architecture … why should we care?• SOA and Enterprise Architecture• Best Practices for Enabling SOA at the Enterprise• Summary
7
A programming model complete with standards, tools, methods and technologies such as Web services
A model of the business and related key performance indicators
Roles
SOA means different things to different people
An architectural style which requires a service provider, requestor and a service description. It addresses characteristics such as loose coupling, reuse and simple and composite implementations.
Implementation
Architecture
Business
OperationsA set of agreements and contracts among service requestors and service providers that specify the quality of service.
IBM IT Service Management
IT Process ManagementIT ProcessManagement Products
IT Service Management Platform
Best Practices
IT OperationalManagement Products
IBM IT Service Management
IT Process ManagementIT ProcessManagement Products
IT Service Management Platform
Best Practices
IT OperationalManagement Products
SOA Solution Stack
9
Enterprise Architecture: SOA Aspects
• Intent: Ensuring SOA links to business value propositions
• Solution Architecture: Designing SOA Solutions
• Component Approach: Enabling a building block approach
• Governance: Processes, roles and responsibilities
• Planning: Planning/prioritization of SOA programs
• Development: Building/composing SOA Solutions
• Operations: Management of SOA-based runtime solutions
• Deployment: "Publishing" SOA solutions and Change Management
• Transition: Moving from "As-Is" to the "To-Be" SOA Environment
10
Components in an Enterprise Architecture
11
Mapping Solution Approaches to an EA
12
SOA-Based Enterprise Technology FrameworkApplication Architecture
13
Application Architecture – Banking
Components Layer
Business components
Information Layer
Client/Product/Segment Views
Channels Layer
Services Layer
Atomic Services Composite Services
Presentation Layer
Authentication Content
Integration Layer
Client History
Management
Availability
Configuration
Prod
uct
Tran
sform
atio
n
Web Services
(SOAP sobre H
TTP(s), MQ
ou JMS), JM
S, HTTP(s) ou Adaptadores
Functions
ESBBPM
Information
Electronic
Client
Relationship
Collaboration Personalization
ClientCatalog
ETL
Self service Partners
Credit Investments Banking Applic. CRM Insurance
Loans Treasury Payments Risk and Compliance Credit Cards
Security Management
Provisioning
Monitoring
Analytics
DWBI Data Marts
ApplicationDevelopment
Portfolio andProcess Control
ProductCatalog
Common Components
Asset MgmtAccounting
Cash
ManagementAuditingCollecting HR Legal
Branches Call Center Mobility
Access Control
Protocols
Com
ponentsU
DD
I Repository
Messaging
ID management
Directorymanagement
Transport
Routing
Data
Transform
ation
Workflo
w &
Orch
estra
tion
Change Management
QualityManagement
Architecture Control
14
Agenda
• Enterprise Architecture … why should we care?• SOA and Enterprise Architecture• Best Practices for Enabling SOA at the
Enterprise• Summary
15
Are we still moving in the
right direction?
Are our target architectures
still right?
Are we doing these things the way we said we want
them done?
Determine the Governance Focus
Plan Define Enable MeasureDefine the SOA
Governance ModelImplement the SOA Governance Model
Refine the SOA Governance Model
SGMM
This is the way things should be architected
<< Input from Business Analysis >>
<<Output to SOA Implementation >>
SOMA
SOA and Enterprise Architecture: Best Practices
Projects
Enterprise Architecture
ModelsGovernanceTransition
Planning
Project Prioritization & Planning
These are the things we should
do
SIMM
16
Component Analysis• The enterprise is mapped out as a set of categorized business components• Heat map highlights components for analysis based on criteria such as gaps and efficiency• Enables approaches to understanding how the business can be improved
Controlling
Executing
DirectingBusiness Planning
Business Unit Tracking Sales
ManagementCredit
AssessmentReconciliation
Compliance
Staff Appraisals
Relationship Management
Sector Management
Product Management
Product Administration
Product Fulfillment
Sales
Marketing Campaigns
Product Directory
Credit Administration
Customer Accounts
GeneralLedger
Document Management
CustomerService
Collections
AccountAdministration
BusinessAdministration
New Business Development
Relationship Management
Servicing & Sales
Product Fulfillment
Financial Control and Accounting
Sector Planning Portfolio Planning
Account Planning
Sales PlanningFulfillment Planning
Fulfillment Monitoring
Purchasing
Branch/Store Operations
17
Service Integration Maturity Model (SIMM)
Silo ServicesComposite
ServicesVirtualizedServices
DynamicallyRe-Configurable
ServicesComponentizedIntegrated
Level 1 Level 4 Level 5 Level 6 Level 7Level 3Level 2
Applications
Methods
Organization
Infrastructure
Information
Business
Modules ServicesProcess
Integration via Services
Dynamic Application Assembly
ComponentsObjects
Structured Analysis &
Design
Service OrientedModeling
Service OrientedModeling
Business GrammarOrientedModeling
Component Based
Development
Object OrientedModeling
Application Specific Skills
Emerging SOA Governance
SOA and IT Infrastructure
Governance Alignment
Governance through Policy
IT GovernanceIT TransformationSOA and IT Governance Alignment
Service Oriented Modeling
Process Integration via Services
LOB Platform Specific
Project-based SOA
Environment
VirtualSOA Environment
Dynamic Sense & Respond
Common Reusable
Infrastructure
Enterprise Standards
Application Specific
InformationAs a Service
VirtualizedData Services
Semantic Data Vocabularies
Canonical ModelsLOB or Enterprise
Specific
Enterprise Data Dictionary and
Repository
Isolated Business Line
Driven
ComponentizedBusiness offers
Services
Geographically Independent
Service Centers
Mix and Match Business and
Location Capabilities
Componentized Business
BusinessProcess
Integration
Processes Through Service
Composition
Monolithic Architecture
Emerging SOA
Grid Enabled SOADynamically
Reconfigurable Architecture
ComponentArchitecture
Layered Architecture
SOAArchitecture
CommonSOA Environment
Service Integration Maturity Model (SIMM)
Silo ServicesComposite
ServicesVirtualizedServices
DynamicallyRe-Configurable
ServicesComponentizedIntegrated
Level 1 Level 4 Level 5 Level 6 Level 7Level 3Level 2
Applications
Methods
Organization
Infrastructure
Information
Business
Modules ServicesProcess
Integration via Services
Dynamic Application Assembly
Objects
Structured Analysis &
Design
Service OrientedModeling
Business GrammarOrientedModeling
Component Based
Development
Application Specific Skills
Emerging SOA Governance
SOA and IT Infrastructure
Governance Alignment
Governance through Policy
IT Transformation
Service Oriented Modeling
LOB Platform Specific
Project-based SOA
Environment
VirtualSOA Environment
Dynamic Sense & Respond
Common Reusable
Infrastructure
Application Specific
VirtualizedData Services
Semantic Data Vocabularies
Canonical ModelsEnterprise Data Dictionary and
Repository
Isolated Business Line
Driven
Geographically Independent
Service Centers
Mix and Match Business and
Location Capabilities
BusinessProcess
Integration
Processes Through Service
Composition
Monolithic Architecture
Emerging SOA
Grid Enabled SOADynamically
Reconfigurable Architecture
Layered Architecture
Architecture
Enterprise Standards
Common SOA Environment
SOA Infrastructure Standard
Deploy Common Information Services
InformationAs a Service
LOB or Enterprise
Specific
ComponentArchitecture
SOAFocus on SOA
Foundation
ComponentsProcess
Integration via Services
Process Choreography Assembly
Service OrientedModeling
Object OrientedModeling
Move to SOA-based Design Methodology
IT GovernanceSOA and IT Governance Alignment
Define & Enforce SOA Governance
ComponentizedBusiness offers
Services
Business Process
Integration
Business Service Decomposition
19
Service Oriented Modeling and Architecture (SOMA) Links Business Intent with IT Implementation
• SOMA gets inputs from business analysis activities, and produces outputs necessary for SOA implementation
• The analysis and modeling performed during SOMA is technology and product agnostic, but establishes a context for making technology and product specific decisions in later phases of the lifecycle
<< Input from Business Analysis >>
<<Output to SOA Implementation >>
SOMA
Service Identification
Service Specification
Service Realization
SOA Governance Lifecycle
Define the Governance Approach Define/modify governance processes Design policies and enforcement mechanisms Identify success factors, metrics Identify owners and funding model Charter/refine SOA Center of Excellence Design governance IT infrastructure
Monitor and Manage the Governance Processes Monitor compliance with policies Monitor compliance with governance
arrangements Monitor IT effectiveness metrics
Enable the Governance Model Incrementally Deploy governance mechanisms Deploy governance IT infrastructure Educate and deploy on expected behaviors
and practices Deploy policies
Plan the Governance Need Document and validate business strategy
for SOA and IT Assess current IT and SOA capabilities Define/Refine SOA vision and strategy Review current Governance
capabilities and arrangements Layout governance plan
21
Provide SOA Measuring Best Practices
Visibility to usage and project information
Business and IT dashboards
Manage the SOA Lifecycle
Change management includingpolicies for publishing, using and
retiring servicesInfrastructure to help govern
access and monitor service vitality
Centerof
Excellence
Implementing A Center of Excellence (COE)
Provide Skills Transfer & Early Proof of Concepts
Identify skills gaps and create development roadmaps
Drive use of new technologies and techniques such as BPM
Provide Architectural Authority
Single point of accountability and communicates SOA best practices,
assets, and patterns
Define High Value Business Services
Modeling business processes, information services Best practices
for identifying and defining shared services
Establish Decision Rights
Service portfolio planning and organizational design
Assets and best practices
Conduct SOA Architecture Reviews
Perform independent design and architecture reviews for key
applications and infrastructure
Provide Architecture Vitality & Thought
LeadershipContinuously assess, refine and
architecture framework and supporting assets based on internal
& external influences
Business & IT Lessons• Start with the business – don’t lead with IT SOA solutions• Difficult to ‘sell’ SOA business value by itself –need to
focus on the business value of enterprise-wide reusable services
• Initially will have higher cost to develop for reusability when compared for a single project’s use
• SOA is not standalone – ideally be part of a comprehensive Enterprise Architecture
• SOA Governance required fairly early in the picture• SOA acceleration should be a combination of top-down
(Business) and bottom-up approach(IT)• Don’t forget about enabling the infrastructure for SOA
23
Enabling SOA with IBM tools
Business Services
Enterprise Service Bus
Interaction Services Process Services Information Services
DevelopmentServices
Partner Services Business App Services Access Services
Management Services
Infrastructure Services
Ap
ps
&
Info
As
sets
Rational Application Developer
WebSphere Integration Developer
Rational Software Architect
Tivoli Federated
Identity Manager
Tivoli Access Manager
Tivoli Composite Application
Monitor
Tivoli Identity Manager
WebSphere Network
Deployment
WebSphere Extended
Deployment
WebSphere Partner
Gateway
WebSphere Adapters
WebSphere Application
Server
WebSphere Process Server
Lotus Collaboration
Solutions
Lotus Expeditor
WebSphere Portal
DB2 Data Warehouse
WebSphere Information
Server
WebSphere Customer
Center
Data Power
WebSphere Service
Registry & Repository
WebSphere Transformation
Extender
WebSphere ESB
WebSphere Message Broker
WebSphere Business Modeler
WebSphere Business Monitor
WebSphere Business
Svcs Fabric
24
Summary
• SOA establishes an enterprise architecture that enables business flexibility and agility
• SOA is an important foundation of enterprise architecture – Companies are using SOA today to drive tangible business value– Investments in SOA will continue to drive competitive
differentiation.
• SOA is not one-size fits all
– Implementation of SOA varies according to the company’s business / IT environment and goals
– Companies should leverage well defined best practices derived from SOA experiences to make the SOA journey effective
– Start small, grow fast, and drive successful implementation through effective governance
Remember – SOA Adoption Is A Journey
