Professional Documents
Culture Documents
CBM Soma Sca
CBM Soma Sca
Jouko Poutanen
Senior IT Architect, IBM Software Group
Agenda
Component Business Modeling (CBM)
Drivers: specialization, cost reduction, differentiation, need for flexibility
Concepts
Engagements
Type 1 Rationalization
Reduce Capacity
Hiring freeze
New IT project budget freeze
Cost
X
Reduce
FTE,
minimize
overlap,
improve
control
Volume
Relocation of resources/applications
Cost
Maintenance/process outsourcing
X
Change IT
operating
model
Volume
5
Each represents a
SOA value
proposition
CBM Framework
Make internal and external specialization practical by organizing activities
by accountability level and competency
Operations Management ? Analysing by Four Vs: volume, variety, variation, visibility etc.
Operations and Process Management, Slack et.al, 2006
8
10
11
12
Classical
organization
Transformation
Incremental or full fledged
Evaluation criterion differentiation often
as facilitator
Componentized
organization
Business challenge:
U.S. division of a global insurance
group seeking an operating model that
increases flexibility while freeing up
capital.
CBM
Approach:
Used Component Business Modeling
(CBM) to determine which applications
deliver the most value to the business
and streamline processes that can be
refined, consolidated or eliminated.
14
Outcomes:
Identified overlaps and redundancies to
reduce the cost of running and
maintaining the number of applications
by as much as 70%.
Improved customer service and could
save the company an estimated
US$200M.
Connected independent agents into its
central system to speed delivery of
policy quotes.
Next step: Design and implement a
Service-Oriented Architecture (SOA)
to help consolidate costly, redundant
applications. SOMA
Agenda
Component Business Modeling (CBM)
Drivers: specialization, cost reduction, differentiation, need for flexibility
Concepts
Engagements
15
Composable
Processes
(CBM)
Component
Business Modeling
Requires
Flexible IT
On demand Operating Environment
Service Oriented Architecture (SOA)
Development
Software
Development
16
Infrastructure
Management
Integration
Infrastructure
Management
Composable
Services
(SOA)
The use of new design techniques, combined with current approaches and
appropriate standards, is the most successful way to define services
Reasons for SOMA
Component Business
Modeling (CBM)
KPI
Metrics
Flows /
Activities
Business Analysis
Service-oriented
architecture (SOA)
SOMA
Use
Cases
BPEL
WSDL
OOAD
Information Technology
Map
Attribution
Processes
Components
Patterns
Services Frameworks
Standards
Programming
Model
Domain Analysis
Functional Areas grouping
Variability-Oriented Analysis
(VOA)
Process Modeling
Component-Based Development
(CBD)
Object-Oriented Analysis and Design
(OOAD)/Use Case Modeling
Service-oriented modeling
introduces new techniques
Goal-Service Modeling
Service Model creation
2008 IBM Corporation
Direct
Business
& Resource
Admin
New
Business
Development
Product
Delivery
Product
Services
Account
Services
Business
Portfolio
Management
Business
and Resource
Planning
Segment
Analysis &
Planning
Customer
Portfolio &
Analysis
Customer
Sales & Servicing
Planning
Product
Operations
Planning
Product
Services
Planning
Account
Services
Planning
Asset &
Liability Policy
& Planning
Finance
Policies
Business
Policies &
Procedures
Acquisition
Planning
Credit
Policy &
Planning
Product
Oversight
Customer
Behavior
& Models
Sales/
Service
Administration
Product
Operations
Oversight
Product
Services
Oversight
Account
Services
Oversight
Risk/Portfolio
Management
Financial
Control
Relationship
Oversight
Case &
Exception
Handling
Financial
Management
External
Relations
Business
Architecture
Control
Execute
Business
Unit Tracking
Campaign
Management
Reconciliations
Unit
Administration
Development
& Deployment
Administration
Authorizations
DDA/CheckSpecific
Processing
Inventory
Management
Customer
Accounting
Consolidated
Book/Position
Maintenance
Treasury
Human
Resource
Management
Market
Research
Relationship
Management
Transaction
Consolidation
Retail
Lending
Cash
Inventory
Billing &
Payments
Securitization/
Syndication
Financials
Consolidation
Transaction
Capture
Services
Card-specific
Processing
Market
Information
Collections
& Recovery
Inter-bank
Account
Management
Accounting
General
Ledger
Customer
Profile
Sales
Card Financial
Capture
Correspondence
Contact/
Event
History
Dialogue
Handler
Systems
Development &
Operations
Marketing
Fixed
Asset Register
Campaign
These are supported
Execution
by
collaborating
fine
Production
Assurance
grained
services and
(Help Desk)
object interactions
18
Fraud/AML
Detection
Each
is
Audit/Assur- CBM componentApplication
ance/Legal/
Processing
Compliance
responsible
for business
activities
and
processesCredit
Business
Product
Smart
Routing
Document
Management
& Archive
Merchant
Operations
Rewards
Administration
SOA
Web
Collaboration
Device
People
(Service consumers)
Business
Process
External
Services
(Application &
Information)
Operational
Systems
(Application &
Information Assets)
Application
Application
Content
Data
Registry
Long running
One or more persons interacting
Multiple valid business process states
Alternative workflows for nonnormal conditions
Business Transaction
Short term, non-interactive
One change of business state
Consumes one or more enterprise
service
Targeted level of service reuse
Loose coupling important
May require compensation
Function Service
Collaborations to implement a
single web service
Collaborating apps encapsulated
via web services
Performance favored over loose
coupling
20
Member Requests an Rx
Refill (Call Center IVR or
Online)
Request
Denied
PC Physician
Approves or
Denies Request
(WS or Email)
Validate
Member is
Authorized to
Make Request
Member Informed
that Refill is Ready
Request
Approved
Send Request
Notification to
pharmacy
Send Request
Notification to Notes
Not WS
Enabled
Authorization Service
Email Service
Outpatient Service
Masters Service
Patient
Records
Credit
Verification
Office
Scheduling
Email
System
HR
21
22
Outcomes:
Approach:
SOMA
CIR
23
24
Business priority
IBM technique
Outcome
Service-Oriented Modeling
and Architecture
Component Infrastructure
Roadmap
CBM
SOMA
CBM-BoIT
CIR
Agenda
Component Business Modeling (CBM)
Drivers: specialization, cost reduction, differentiation, need for flexibility
Concepts
Engagements
25
Core Elements
Service Component Business logic implementation of a service.
Service Assembly Composition of components and services.
Service Data Business data exchanged by services.
26
Business
Processes
Interface
Maps
BPEL + Extensions
SCA
Human
Tasks
Tasks
Business
Business
State
Machines
Machines
Selectors
Business
Object Maps
Service Component
Architecture
Business
Objects
Business
Rules
Rules
Relationships
Common Event
Infrastructure
Business Objects
(SDO-based technology)
28
Service Component
Architecture (SCA)
29
Session beans
Web Services
Java class
BPEL
etc
Java
Java
WSDL
Port Type
WSDL
Port Type
Java
Interface
BPEL
State
Machine
Reference
Business
Rules
Human
Task
Selector
Interface
Maps
Implementation Types
30
Service Module
Service
Component
Export
Service
Component
non-SCA
SCA
Standalone
Reference
Import
Wire
non
SCA
31
Programming Model
Modules are contain wired Service Components
Service Components use SDOs for data
Solutions are a collections of Modules
Module B
Web Client
Export
Module A
Component
Component
Component
Wires
Interfaces
Import
References
Services
Export
SDO
I
32
CBM SOMA n
SCA
t
e
SCA
Export
Pseudo Synchronous
33
SCA
Component
Asynchronous
Import
Callback
Business
Objects
Component
Interfaces
Assembly
Business Event
Monitoring
Selectors
Mapping
Components
Exports
Imports
Business
State
Machines
Business
Rules
Resource
Adaptors
Web Services
EJBs
Java
Used in
Component
Creation
Diagram
Human
Tasks
Business
Processes
34
Visual
Snippets
Components
Wired in
Assembly
Editor
J2EE
Artifacts
2008 IBM Corporation
Interface
Reference
Import
Module
Export
35
Transactions / Compensation
36
Shared Library
Shared Library
Interfaces
Business Objects
Business Object Maps
Relationships
37
Module
Business Integration project type for developing SCA
based applications
Basic unit of deployment to the runtime environment
A module is packaged in an EAR file
Module
38
Rational RequisitePro
Rational Portfolio
Manager
Understand
Risk, Project
Costs, and ROI
Project
Manager
Create Observation
Model with KPIs &
export to Monitor
services using
BPEL, WSDL,
etc.
Create, Simulate,
Analyze and Optimize
To-Be Business Model
CIO
Identify and
Manage
Projects and
Resources
WebSphere Integration
Developer
Choreograph
Create Financial
Reports & ROI
Estimates
Business
Analyst
BPEL
WSDL
Integration
Developer
Assemble Solution
(BPEL, Human Task
Manager, Business
Rules, etc)
Configure Human
Task Manager
(including Ad-Hoc)
& Client
WSDL
EAR
UML
Rational Data
Architect
Model
Relational
Database
Schemas
Trace Requirements
& Create System
Use Case
Realizations
Tester
RDB
Mapping
Data
Architect
Architect
Rational
Software
Architect
Develop
Portlets
(App UI
and
Monitor)
Runtime
WebSphere Process Server
WebSphere Portal
WebSphere Business Monitor
WSDL
EAR
Deploy/Run
Monitor
Java
Developer
Portal
Developer
Business
Operations
Analyst
DBA
More Information
CBM
www-935.ibm.com/services/us/imc/pdf/g510-6163-componentbusiness-models.pdf
SOMA
Case Study
http://www.redbooks.ibm.com/abstracts/REDP4467.html?Open
Arctile
http://www.ibm.com/developerworks/webservices/library/ws-soadesign1/
40