Nitin Singhal

1
SOA and Enterprise ArchitectureA Natural
Convergence

• Nitin Singhal
• SOA Tech Sales

2
Agenda

• Enterprise Architecture why should we care?
• SOA and Enterprise Architecture
• Best Practices for Enabling SOA at the Enterprise
• Summary

3
Enterprise ArchitectureBridges the Gap Between
Business and IT
Strategy
Information TechnologyStrategy
BusinessStrategy
Business Opportunity
Technology Availability
Enterprise Architecture

• Business Architecture
• Processes
• Information
• People

• IT
• Architecture
• Applications
• Information
• Technology

Enterprise wide focus
Planning
Transition Plan EA Governance
Business Operating Environment and IT
Infrastructure
Project focus
Design and Delivery
IT Solutions
4
EA is more than Architecture
5
EA Context
Business Environment (external influences) Custome
rs, Regulators, Market, ...
influences
value
Business Model Intent (strategies, drivers,
principles, plans), Value (products
services), Capabilities, Business Processes,
Information Model, Business Roles Locations, ...
Assets

• Governance
• Architecture Management Framework
• Leadership
• Sponsorship
• Ownership
• Resources
• Charter
• Structure
• Vision
• Principles
• Roles Responsibilities
• Processes
• NFRs
• Roadmaps
• Metrics

People, Process, Technology Architecture
Models Reference Architectures Infrastructure P
ackages Tools Processes Services Skills
influences
feedback
Enterprise Architecture Business, Applications,
Information, Technical, Governance
Update
influences
feedback
Solution Architectures (many, including SOA)
Reuse
Solution Architectures (many, including SOA)
Solution Architectures (many, including SOA)
influences
feedback
Information
Applications
Infrastructure
6
Agenda

• Enterprise Architecture why should we care?
• SOA and Enterprise Architecture
• Best Practices for Enabling SOA at the Enterprise
• Summary

7
SOA means different things to different people
Roles
A model of the business and related key
performance indicators
Business
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.
Architecture
A programming model complete with standards,
tools, methods and technologies such as Web
services
Implementation
A set of agreements and contracts among service
requestors and service providers that specify the
quality of service.
Operations
8
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
Integration Layer
Management
Application Development
Channels Layer
Self service
Branches
Call Center
Mobility
Electronic
Partners
Protocols
Functions
Components
Availability
Presentation Layer
Collaboration
Personalization
Access Control
Authentication
Content
W
ID management
E
e
Services Layer
S
b
Transport

B
S
e
r
v
Atomic Services
Composite Services
i
Change Management
c
e
s
(
S
B
Directory management
O
P
Components Layer
A
M
Routing
P

s
Business components
o
Quality Management
b
r
e

Investments
Insurance
Credit
Banking Applic.
CRM
H
T
T
P
Configuration

(
Data Transformation
s
)
Architecture Control
,
UDDI Repository

Risk and Compliance
M
Loans
Treasury
Payments
Credit Cards
Q


o


u


J
M
Portfolio and Process Control
Common Components
S
Provisioning

)
,

J
Cash Management
Product Transformation
M
Asset Mgmt
Collecting
S
Accounting
Auditing
HR
Legal
,

Messaging
H
T
T

P
Security Management
(
s
)
Information Layer

o
u

A
Client/Product/Segment Views
Analytics
d
Workflow Orchestration
a
p
E
t
Client History
a
Client Catalog
T
Product Catalog
Client Relationship
d
L
Information
Data Marts
DW
BI
o
r
Monitoring
e
s
14
Agenda

• Enterprise Architecture why should we care?
• SOA and Enterprise Architecture
• Best Practices for Enabling SOA at the Enterprise
• Summary

15
SOA and Enterprise Architecture Best Practices
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

Business Administration
New Business Development
Relationship Management
Servicing Sales
Product Fulfillment
Financial Control and Accounting
Business Planning
Sector Planning
Directing
Account Planning
Portfolio Planning
Sales Planning
Fulfillment Planning
Sales Management
Compliance
Relationship Management
Sector Management
Fulfillment Monitoring
Controlling
Business Unit Tracking
Reconciliation
Credit Assessment
Product Management
Staff Appraisals
Executing
Product Fulfillment
Sales
Product Directory
Credit Administration
Customer Accounts
Account Administration
Product Administration
Marketing Campaigns
Document Management
Customer Service
Purchasing
General Ledger
Collections
Branch/Store Operations
17
Service Integration Maturity Model (SIMM)
18
Service Integration Maturity Model (SIMM)
Isolated Business Line Driven
Geographically Independent Service Centers
Mix and Match Business and Location Capabilities
Business Process Integration
Processes Through Service Composition
Business
Application Specific Skills
Emerging SOA Governance
SOA and IT Infrastructure Governance Alignment
Governance through Policy
IT Transformation
IT Governance
SOA and IT Governance Alignment
Define Enforce SOA Governance
Organization
Move to SOA-based Design Methodology
Structured Analysis Design
Service Oriented Modeling
Business Grammar Oriented Modeling
Component Based Development
Service Oriented Modeling
Service Oriented Modeling
Object Oriented Modeling
Methods
Process Choreography Assembly
Modules
Services
Process Integration via Services
Dynamic Application Assembly
Objects
Components
Process Integration via Services
Applications
Monolithic Architecture
Emerging SOA
Grid Enabled SOA
Dynamically Reconfigurable Architecture
Layered Architecture
Component Architecture
SOA
Focus on SOA Foundation
Architecture
Deploy Common Information Services
LOB or Enterprise Specific
Application Specific
Virtualized Data Services
Semantic Data Vocabularies
Canonical Models
Enterprise Data Dictionary and Repository
Information As a Service
Information
LOB Platform Specific
Project-based SOA Environment
Virtual SOA Environment
Dynamic Sense Respond
Common Reusable Infrastructure
Enterprise Standards
Common SOA Environment
SOA Infrastructure Standard
Infrastructure
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

20
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

• 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

• Enable the Governance Model Incrementally
• Deploy governance mechanisms
• Deploy governance IT infrastructure
• Educate and deploy on expected behaviors and
  practices
• Deploy policies

• Monitor and Manage the Governance Processes
• Monitor compliance with policies
• Monitor compliance with governance arrangements
• Monitor IT effectiveness metrics

21
Implementing A Center of Excellence (COE)
Manage the SOA Lifecycle Change management
including policies for publishing, using and
retiring services Infrastructure to help govern
access and monitor service vitality
Provide SOA Measuring Best Practices Visibility
to usage and project information Business and IT
dashboards
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
Provide Architecture Vitality Thought
Leadership Continuously assess, refine and
architecture framework and supporting assets
based on internal external influences
Center of Excellence
Define High Value Business Services Modeling
business processes, information services Best
practices for identifying and defining shared
services
Conduct SOA Architecture Reviews Perform
independent design and architecture reviews for
key applications and infrastructure
Establish Decision Rights Service portfolio
planning and organizational design Assets and
best practices
22
Business IT Lessons

• Start with the business dont 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 projects
  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)
• Dont forget about enabling the infrastructure
  for SOA

23
Enabling SOA with IBM tools
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
  companys 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

25
Remember SOA Adoption Is A Journey
26

• Thank you

27
Business Strategy Drives IT DecisionsITs Goal
is to Flexibly Support Business Requirements
BusinessIntent
MeetingStrategicGoals?
Business Strategy Design
Align
Strategic KPIs
Business Services
BusinessUnderstanding
MeetingBusinessCommitments?
Business Operations
Optimize
Operation Models
Business Performance Management
Operation Models
SolutionFlexibility
Response to Business Situations
Solution Composition
Correct
Executable Solution
Executable Solution
Quality ofService
Detecting Business Situations
IT Implementation
Monitor
28
Architectural evolution in the enterprise
Business flexibility through technical agility
Services based architectures enabled by open
standards is the next major computing shift
1980s to mid 1990s
Mid 1990s to early 2000s
Future
Today
Pre 1980
Client-Server Architecture
Monolithic Architecture
Service- Oriented Architecture / Web Services
Network Centric Architecture
Dynamically Re-configurable Architecture

• Service Oriented Computing
• Web Services Architecture
• Open Standards

• Mainframe

• Visual Basic
• PowerBuilder

• eBusiness
• eCommerce

Key Point SOA is NOT integration . SOA makes
integration solutions better
29
Business Components Defining Key Business
Functions
Component Name Account Administration Resources
Account Data, CRM People Call Center,
Customers Technology CICS Customer Account,
SAP SLA/KPIs Time to Open Account Description Fu
nctional aspects of administration including
account opening, account management, account
closure

• A business component is a grouping of the
  people, technology, resources delivering
  specific business value
• Components have well-defined interfaces, allowing
  them to interact smoothly with each other and to
  be 'snapped' in and out at will, like building
  blocks
• The Interfaces of the Business Components Enable
  Identification of Candidate Business Services

AccountAdministration
30
SOA Security and Management Aspects
Service Registry and Version Management Validate
the quality and accuracy of the contents in the
service registry. Version management is carried
out effectively
Define SOA Governance Model
Manage Existing Services
Governance
Ownership and Funding Models
Security and Management
Reg. New Service Creation
SLA Compliance Monitoring Enforce the correct
execution metrics for every service invocation
Strategic
Deployment Options Validate that services are
configured to use the infrastructure most
effectively
Tactical
Security Management Services correctly implement
security decisions for authentication,
authorization, auditing, transport security,
threat protection
SGMM - SOA Governance and Management Method
SOA Governance Implementation Capability Pattern