CBM – SOMA - SCA - Jyväskylän · PDF fileCBM – SOMA - SCA Techniques and...
Transcript of CBM – SOMA - SCA - Jyväskylän · PDF fileCBM – SOMA - SCA Techniques and...
© 2008 IBM Corporation
CBM – SOMA - SCA
Techniques and Standards to Increase Business and IT Flexibility
Jouko PoutanenSenior IT Architect, IBM Software Group
2 CBM – SOMA – SCA © 2008 IBM Corporation
Agenda
�Component Business Modeling (CBM)
– Drivers: specialization, cost reduction, differentiation, need for flexibility
– Concepts
– Engagements
� Service Oriented Modeling and Architecture (SOMA)
– From business services to SOA services
– Process demo
� Service Component Architecture (SCA)
– SOA programming model
3 CBM – SOMA – SCA © 2008 IBM Corporation
Phases of External Specialization
4 CBM – SOMA – SCA © 2008 IBM Corporation
Stages of Internal Specialization
5 CBM – SOMA – SCA © 2008 IBM Corporation
Structural Change Is Required to Achieve Further Cost Reductions
� Typical initial cost reduction measures (Type 1)
– Hiring freeze
– New IT project budget freeze
– Termination of sub-contracting agreements
– Voluntary departure plans
– Early retirement
� Typical advanced cost reduction initiatives (Type 2)
– Relocation of resources/applications
– Central vs. decentralized IT governance
– Strategic alignment & prioritization
– Maintenance/process outsourcing
– Process optimization
Type 1 Rationalization“Reduce Capacity”
Type 2 Structural Change“Transform Fixed into Variable Costs”
Co
st
x
X’
Volume
Change IT operating model
Volume
ReduceFTE,
minimizeoverlap,improvecontrol
X’
x
Co
st
6 CBM – SOMA – SCA © 2008 IBM Corporation
Drive down cost
Eliminate duplicate systems, build once and leverage, improve time to market
Provide a flexible business model
React to market changes more quickly
Increase revenue
Create new routes to market, create new value from existing systems
Reduce cycle times and cost for external business partners
Move from manual to automated transactions, facilitate flexible
dealings with business partners
Integrate across the enterprise
Integrate historically separate systems, facilitate mergers and acquisitions of enterprises
Reduce risk and exposure
Improve visibility into business operations
Each represents a SOA value proposition
Common Business Challenges Facing Enterprises Today Demand the Fusion of Business and IT
7 CBM – SOMA – SCA © 2008 IBM Corporation
What is a Business Component ?
8 CBM – SOMA – SCA © 2008 IBM Corporation
CBM Framework
Make internal and external specialization practical by organizing activities
by accountability level and competency
Operations Management ? Analysing by Four V’s: volume, variety, variation, visibility etc. ’Operations and Process Management’, Slack et.al, 2006
9 CBM – SOMA – SCA © 2008 IBM Corporation
Example CBM Map from Retail Sector
10 CBM – SOMA – SCA © 2008 IBM Corporation
Heat Maps Identify “Hot” Areas to Exploit Business Value
11 CBM – SOMA – SCA © 2008 IBM Corporation
Phases of CBM Analysis
12 CBM – SOMA – SCA © 2008 IBM Corporation
13 CBM – SOMA – SCA © 2008 IBM Corporation
There are two levels of deploying CBM, that are both supported by the CBM framework
� Majority of present CBM assignments use component maps to
– Analyze and frame client issues from a new dimension
– Identify and prioritize areas for improvement
� Component map need not to correspond to any existing organizational structure
� Implementation horizon is typically 0 to 2 years
� New organizational paradigm as CBM end vision: the organization is a set of components that are networked together
– Internally: the networked organization
– Externally: the value network
� Interfaces between components have a physical component (services, products) and a technological component (real time connectivity)
� Implementation horizon is typically 3 to 5 years
Transformation
� Incremental or full fledged
� Evaluation criterion ‘differentiation’ often
as facilitator
Componentized organization
‘Classical’organization
14 CBM – SOMA – SCA © 2008 IBM Corporation
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.
Scenario: Improve customer service and operational efficiency
Business challenge:
U.S. division of a global insurance group seeking an operating model that increases flexibility while freeing up capital.
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.
CBM
SOMA
15 CBM – SOMA – SCA © 2008 IBM Corporation
Agenda
� Component Business Modeling (CBM)
– Drivers: specialization, cost reduction, differentiation, need for flexibility
– Concepts
– Engagements
�Service Oriented Modeling and Architecture (SOMA)
– From business services to SOA services
– Process demo
� Service Component Architecture (SCA)
– SOA programming model
16 CBM – SOMA – SCA © 2008 IBM Corporation
Business and the Supporting IT Environment Must be Componentized to Support Flexibility
Composable
Services
(SOA)
Flexible Business
TransformationBusiness Process Outsourcing
Mergers, Acquisitions & Divestitures
Flexible IT
On demand Operating Environment
Software Development Integration
InfrastructureManagement
Requires
Development Infrastructure Management
Service Oriented Architecture (SOA)
Composable
Processes
(CBM)Component
Business Modeling
17 CBM – SOMA – SCA © 2008 IBM Corporation
The use of new design techniques, combined with current approaches and appropriate standards, is the most successful way to define services
� Object-Oriented Analysis and Design (OOAD) is necessary to define object-oriented systems and component-based development is used to define component-based architectures
� Service-oriented modeling is necessary to build a service-oriented architecture
– SOMA builds on current techniques
– 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
Reasons for SOMA
� BPEL: Business Process Execution Language� WSDL: Web Service Description Language� SOMA: Service Oriented Modeling and
Architecture
KPI Metrics
Flows /Activities
Use Cases
OOAD
ProcessesComponents
Business Analysis Information Technology
MapAttribution
SOMAComponent Business
Modeling (CBM)Service-oriented
architecture (SOA)
PatternsFrameworks
StandardsProgramming
ModelServices
BPELWSDL
18 CBM – SOMA – SCA © 2008 IBM Corporation
Direct
Execute
Control
Financial
Management
Business
& Resource
Admin
Business
Portfolio
Management
Customer Sales
& Servicing
New
Business
Development
Product
Delivery
Customer
Management
Product
Services
Account
Services
Treasury
AccountingGeneralLedger
FinancialsConsolidation
FacilitiesOperation &Maintenance
SystemsDevelopment &Operations
ProductionAssurance(Help Desk)
FixedAsset Register
BusinessUnit
Administration
HumanResource
Management
ConsolidatedBook/PositionMaintenance
Securitization/Syndication
Inter-bankAccount
Management
SmartRouting
Sales
TransactionCaptureServices
DialogueHandler
TransactionConsolidation
AuthorizationsProduct
Development& Deployment
MarketResearch
CampaignExecution
ProductDirectory
Marketing
MerchantOperations
Card FinancialCapture
DDA/Check-Specific
Processing
Card-specificProcessing
RetailLending
Contact/EventHistory
CollateralHandling
CustomerProfile
RelationshipManagement
CreditAdministration
RewardsAdministration
InventoryManagement
CashInventory
MarketInformation
Correspondence
DocumentManagement& Archive
Billing &Payments
CustomerAccounting
Collections& Recovery
FinancePolicies
Businessand ResourcePlanning
BusinessPolicies &Procedures
ExternalRelations
Asset &Liability Policy& Planning
CustomerSales & Servicing
Planning
SegmentAnalysis &Planning
AcquisitionPlanning
ProductOperationsPlanning
CustomerPortfolio &Analysis
CreditPolicy & Planning
ProductServicesPlanning
AccountServicesPlanning
Reconciliations
FinancialControl
BusinessArchitecture
BusinessUnit Tracking
Audit/Assur-ance/Legal/Compliance
Risk/PortfolioManagement
Case &ExceptionHandling
Sales/Service
Administration
CampaignManagement
ProductOversight
ProductOperationsOversight
CustomerBehavior& Models
ApplicationProcessing
RelationshipOversight
ProductServicesOversight
Fraud/AMLDetection
AccountServicesOversight
Each CBM component is responsible for business activities and processes
Business processes and activities are automated by business services
These are supported by collaborating fine grained services and object interactions
CBM and the industry models
19 CBM – SOMA – SCA © 2008 IBM Corporation
Infrastructure and Management for SOA
Services(Application & Information)
Operational Systems(Application & Information Assets)
People(Service consumers)
Business Process
Connectivity (Enterprise Service Bus)
Web Device
Data Registry
Application Application
Content
Collaboration
External
SOA…
SOA Governance and Lifecycle Management
20 CBM – SOMA – SCA © 2008 IBM Corporation
Services have a different level of granularity; they are aggregated to a business process (flexible workflows)
Member Requests an Rx
Refill (Call Center IVR or
Online)
Request
Denied
Rx Dept
Processes
RefillPC Physician
Approves or
Denies Request
(WS or Email)
Member Informed
that Refill is Ready
Validate
Member is
Authorized to
Make Request
Determine Member’s Coverages
and Primary Care Physician
Send Request Notification to pharmacy
Send Request Notification to Notes
Patient
Records
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
Member Informed that
Request has been Denied
Request
Approved
WS Enabled
Not WS Enabled
Credit
Verification Office
Scheduling
System
Authorization Service
Email ServiceOutpatient Service
Masters Service
HR
Function Service� Collaborations to implement a
single web service� Collaborating apps encapsulated
via web services� Performance favored over loose
coupling
Business Process� Long running� One or more persons interacting� Multiple valid business process states� Alternative workflows for non-
normal conditions
21 CBM – SOMA – SCA © 2008 IBM Corporation
The Process of Service-Oriented Modeling and Architecture
22 CBM – SOMA – SCA © 2008 IBM Corporation
Example Case Study
23 CBM – SOMA – SCA © 2008 IBM Corporation
Scenario: Enable self-service using existing assets
Business challenge:
Government agency required to comply with mandate to make 80 percent of its transactions “electronic” by 2007.
Approach:
�The Service-Oriented Modeling and Architecture (SOMA) technique was applied to treat e-filing submissions as a shared service by building a robust, scalable SOA-based system linking external trading partners with new applications.
�The approach leverages existing IT assets and introduced new application capabilities.
Outcomes:
� By implementing suggested SOA-based solution, client complied with government mandate and completed project ahead of schedule.
� Error rates associated with manual adjustments to transmitted data were reduced from 25% to 6%.
� Employee productivity increased through online availability of submission data.
� Next step: Create customized IT roadmap to support new information services identified by SOA model
SOMA
CIR
24 CBM – SOMA – SCA © 2008 IBM Corporation
IBM Techniques to Help Accelerate Business Innovation
OutcomeIBM techniqueBusiness priority
Developing the business case for transformation by creating a logical representation of a business, making it easier to analyze business process performance and define differentiating components
Component Business Modeling ServicesSM
Drive growth and achieve differentiation by leveraging core competencies
An SOA design recommendationthat includes a detailed description of the SOA service model and solution architecture
Service-Oriented Modeling and Architecture
Develop a flexible set of business-aligned IT services that collectively fulfill an organization’s business processes and goals while leveraging existing IT assets
An IT process map of the activities and resources required to run the IT organization most effectively to support the organization’s business objectives
Component Business Modeling for the Business of IT
Perform a holistic analysis of the IT function to make it run as an integrated and seamless part of the business
An incremental roadmap for IT based on analysis of current and desired target state of IT infrastructure capabilities, business initiatives and goals
Component Infrastructure Roadmap
Identify changes necessary to increase IT infrastructure flexibility and reduce costs, based on business goals
CBM-BoIT
CBM
CIR
SOMA
25 CBM – SOMA – SCA © 2008 IBM Corporation
Agenda
� Component Business Modeling (CBM)
– Drivers: specialization, cost reduction, differentiation, need for flexibility
– Concepts
– Engagements
� Service Oriented Modeling and Architecture (SOMA)
– From business services to SOA services
– Process demo
�Service Component Architecture (SCA)
– SOA programming model
26 CBM – SOMA – SCA © 2008 IBM Corporation
Elements of a SOA Programming Model
� A good SOA programming model supports:
– Services as abstract encapsulations of business function.
– Building, publishing, discovering and using services.
– Assembling solutions from loosely coupled services.
– Separation of concerns between business and infrastructure.
– Freedom to choose / mix implementations, protocols, policies, …
� Core Elements
– Service Component – Business logic implementation of a service.
– Service Assembly – Composition of components and services.
– Service Data – Business data exchanged by services.
27 CBM – SOMA – SCA © 2008 IBM Corporation
Open Service Component Architecture
� Developed by OSOA, a consortium of industry vendors.
� Open-source SCA runtime available in Apache Tuscany.
� Standardization effort under way at OASIS.
> 44,000 downloads since early 2007
28 CBM – SOMA – SCA © 2008 IBM Corporation
Service Oriented Architecture programming model
Service Component Architecture (SCA)
Business Objects(SDO-based technology)
�BPEL + Extensions�SCA
Service Component Architecture (SCA)
Business Objects(SDO-based technology)
�BPEL + Extensions�SCA
Service ComponentArchitecture
BusinessObjects
Common EventInfrastructure
HumanTasks
HumanTasks
BusinessState
Machines
BusinessState
Machines
BusinessRules
BusinessRules
BusinessProcesses
BusinessProcesses
WebSphere Application Server (J2EE Runtime)
InterfaceMaps
BusinessObject Maps
RelationshipsSelectors
Service ComponentArchitecture
BusinessObjects
Common EventInfrastructure
HumanTasks
HumanTasks
BusinessState
Machines
BusinessState
Machines
BusinessRules
BusinessRules
BusinessProcesses
BusinessProcesses
WebSphere Application Server (J2EE Runtime)
InterfaceMaps
BusinessObject Maps
RelationshipsSelectors
SCA in WebSphere Process Server v6
29 CBM – SOMA – SCA © 2008 IBM Corporation
Goals of the new programming model
� J2EE is too difficult – SCA, SDO significantly simplify the programming model
� Strong isolation between business logic and the technical infrastructure code
� Dramatically reduced learning curve for “classical” application developers
� Provides a client programming model allowing client access to service components
� SCA is a service oriented component model for business services that publish or operate on business data
� SCA provides a single abstraction for service types that may already be expressed as– Session beans
– Web Services
– Java class
– BPEL
– etc…
30 CBM – SOMA – SCA © 2008 IBM Corporation
Service Component: Overview
Java BPELBusiness
Rules SelectorHumanTask
StateMachine
Implementation Types
Java
WSDLPort Type Interface Reference
Java
WSDLPort Type
Interface Maps
31 CBM – SOMA – SCA © 2008 IBM Corporation
Service Module: Overview
nonSCA
SCASCA
Import
Export
StandaloneReference
ServiceComponent
ServiceComponent
Service Module
Wire
non-SCA
SCA
32 CBM – SOMA – SCA © 2008 IBM Corporation
Component
Export
Module A
Import
Component
Programming Model
� Modules are contain “wired” Service Components
� Service Components use SDOs for data
� Solutions are a collections of Modules
Wires
Inte
SDOInterfaces References
Module B
Serv
ices
Web ClientComponent
Export
33 CBM – SOMA – SCA © 2008 IBM Corporation
SCA Invocation Patterns
SCA SCA
ExportExport Component
SCA
Import
Pseudo SynchronousPseudo Synchronous CallbackCallbackAsynchronousAsynchronous
34 CBM – SOMA – SCA © 2008 IBM Corporation
WebSphere Integration Developer – Key Features
Components Wired in
Assembly Editor
BusinessProcesses
Mapping Components
BusinessRules
BusinessState
Machines
HumanTasks
Selectors
A s s e m b l y D i a g r a m
Exports Imports
Resource Adaptors
Web Services EJBs JavaJ2EE
Artifacts
Used in Component
Creation
Business EventMonitoring
VisualSnippets
ComponentInterfaces
BusinessObjects
35 CBM – SOMA – SCA © 2008 IBM Corporation
Component Assembly Editor
ImportReference
Export
Module
Interface
36 CBM – SOMA – SCA © 2008 IBM Corporation
Composition - Business Process
� WS-BPEL compliant business process engine
� Simplified Process Editor
– Optional
� Generic Business Process
– Operations / Parameters
– Service Implementation Details hidden
� Transactions / Compensation
37 CBM – SOMA – SCA © 2008 IBM Corporation
Integration Developer: Concepts
Shared Library
Shared Library
Module
Module
Module
• Interfaces• Business Objects• Business Object Maps• Relationships
38 CBM – SOMA – SCA © 2008 IBM Corporation
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
� Contains the following artifacts
– SCA resources and module assembly
– J2EE projects
– Java projects
– Dependent libraries
Module
39 CBM – SOMA – SCA © 2008 IBM Corporation
How to Build a Process Integration solution using BDD
Rational RequisitePro
Create, Simulate & Analyze As-Is
Business Model
WebSphere Business Modeler
Create FinancialReports & ROI
Estimates
Create Observation Model with KPIs & export to Monitor
Create, Simulate, Analyze and Optimize To-Be Business Model
BusinessAnalyst
Integration Developer
WebSphere Integration Developer
Choreograph services using BPEL, WSDL,
etc.
Configure Human Task Manager
(including Ad-Hoc) & Client
Assemble Solution(BPEL, Human Task Manager, Business
Rules, etc)
Understand Risk, Project
Costs, and ROI
Identify and Manage
Projects and Resources
CIO
ProjectManager
Rational PortfolioManager
DataArchitect
ModelRelationalDatabaseSchemas
Rational DataArchitect
RDB Mapping
Trace Requirements & Create System
Use Case Realizations
Model & Implement Services, & expose as
Web Services
Test Create & Manage
SystemRequirements
Architect
RationalSoftwareArchitect Java
Developer
Develop Portlets(App UI
and Monitor)
PortalDeveloper
Tester
Rational Functional & Performance Tester
IBM Rational Team Unifying Platform
BPELWSDL
UML
DBA
Deploy/Run
MonitorBusiness
OperationsAnalyst
Runtime�WebSphere Process Server�WebSphere Portal �WebSphere Business Monitor
WSDLEAR
WSDLEAR
Business Measures Model
Run-time Statistics
40 CBM – SOMA – SCA © 2008 IBM Corporation
More Information
� CBM
– www-935.ibm.com/services/us/imc/pdf/g510-6163-component-business-models.pdf
� SOMA
– Case Study
– http://www.redbooks.ibm.com/abstracts/REDP4467.html?Open
– Arctile
– http://www.ibm.com/developerworks/webservices/library/ws-soa-design1/