CBM SOMA - SCA Techniques and Standards to Increase and IT Flexibility Jouko Poutanen Senior IT Architect, IBM Software Group 2008 IBM Corporation
Agenda Component 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 2 CBM SOMA SCA 2008 IBM Corporation
Phases of External Specialization 3 CBM SOMA SCA 2008 IBM Corporation
Stages of Internal Specialization 4 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 Cost Cost Reduce FTE, minimize overlap, improve control Type 1 Rationalization Reduce Capacity X Type 2 Structural Change Transform Fixed into Variable Costs Change IT operating model Volume x X Volume x 5 CBM SOMA SCA 2008 IBM Corporation
Common Challenges Facing Enterprises Today Demand the Fusion of and IT Increase revenue Create new routes to market, create new value from existing systems Provide a flexible business model React to market changes more quickly Integrate across the enterprise Integrate historically separate systems, facilitate mergers and acquisitions of enterprises Each represents a SOA value proposition Reduce cycle times and cost for external business partners Move from manual to automated transactions, facilitate flexible dealings with business partners Drive down cost Eliminate duplicate systems, build once and leverage, improve time to market Reduce risk and exposure Improve visibility into business operations 6 CBM SOMA SCA 2008 IBM Corporation
What is a Component? 7 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 8 CBM SOMA SCA 2008 IBM Corporation
Example CBM Map from Retail Sector 9 CBM SOMA SCA 2008 IBM Corporation
Heat Maps Identify Hot Areas to Exploit Value 10 CBM SOMA SCA 2008 IBM Corporation
Phases of CBM Analysis 11 CBM SOMA SCA 2008 IBM Corporation
12 CBM SOMA SCA 2008 IBM Corporation
There are two levels of deploying CBM, that are both supported by the CBM framework Classical organization 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 Transformation Incremental or full fledged Evaluation criterion differentiation often as facilitator Componentized organization 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 13 CBM SOMA SCA 2008 IBM Corporation
Scenario: Improve customer service and operational efficiency challenge: U.S. division of a global insurance group seeking an operating model that increases flexibility while freeing up capital. Approach: CBM Used Component Modeling (CBM) to determine which applications deliver the most value to the business and streamline processes that can be refined, consolidated or eliminated. 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 14 CBM SOMA SCA 2008 IBM Corporation
Agenda Component 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 15 CBM SOMA SCA 2008 IBM Corporation
and the Supporting IT Environment Must be Componentized to Support Flexibility Flexible Transformation Process Outsourcing Mergers, Acquisitions & Divestitures Composable Processes (CBM) Component Modeling Requires Flexible IT On demand Operating Environment Service Oriented Architecture (SOA) Development Infrastructure Management Composable Services (SOA) Software Development Integration Infrastructure Management 16 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 Component Modeling (CBM) KPI Metrics Flows / Activities Analysis Map Attribution Processes Components SOMA BPEL WSDL Services BPEL: Process Execution Language WSDL: Web Service Description Language SOMA: Service Oriented Modeling and Architecture Use Cases OOAD Information Technology Patterns Frameworks Service-oriented architecture (SOA) Standards Programming Model Reasons for SOMA 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 serviceoriented 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 17 CBM SOMA SCA 2008 IBM Corporation
CBM and the industry models & Resource Admin New Development Customer Management Customer Sales & Servicing Product Delivery Product Services Account Services Portfolio Management Financial Management Direct and Resource Planning Policies & Procedures External Relations Segment Analysis & Planning Acquisition Planning Customer Portfolio & Analysis Credit Policy & Planning Customer Sales & Servicing Planning Product Operations Planning Product Services Planning Account Services Planning Asset & Liability Policy & Planning Finance Policies Architecture Product Oversight Customer Behavior & Models Sales/ Service Administration Product Operations Oversight Product Services Oversight Account Services Oversight Risk/Portfolio Management Financial Control Control Unit Tracking Unit Administration Campaign Management Product Development & Deployment Relationship Oversight Each Audit/Assur-CBance/Legal/ component is responsible Compliance for business activities and processes Application Processing Credit Administration Case & Exception Handling Authorizations DDA/Check- Specific Processing Inventory Management Fraud/AML Detection Customer Accounting Consolidated Book/Position Maintenance Reconciliations Treasury Execute Human Resource Management Facilities Operation & Maintenance Systems Development & Operations Market Research Marketing Relationship Management processes and activities are Product automated Directory by business services Collateral Handling Customer Profile Transaction Consolidation Transaction Capture Services Sales Retail Lending Card-specific Processing Card Financial Capture Cash Inventory Market Information Correspondence Billing & Payments Collections & Recovery Securitization/ Syndication Inter-bank Account Management Financials Consolidation Accounting General Ledger Fixed Campaign Asset These Register are supported Execution by Production collaborating fine Assurance grained (Help Desk) services and object interactions Contact/ Event History Dialogue Handler Smart Routing Merchant Operations Document Management & Archive Rewards Administration 18 CBM SOMA SCA 2008 IBM Corporation
SOA People (Service consumers) Web Collaboration Device Process External Services (Application & Information) Operational Systems (Application & Information Assets) Application Application Content Data Registry Connectivity (Enterprise Service Bus) Infrastructure and Management for SOA SOA Governance and Lifecycle Management 19 CBM SOMA SCA 2008 IBM Corporation
Services have a different level of granularity; they are aggregated to a business process (flexible workflows) Process Long running One or more persons interacting Multiple valid business process states Alternative workflows for nonnormal conditions Member Requests an Rx Refill (Call Center IVR or Online) PC Physician Approves or Denies Request (WS or Email) Request Denied Request Approved Rx Dept Processes Refill Member Informed that Request has been Denied Member Informed that Refill is Ready 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 Validate Member is Authorized to Make Request Determine Member s Coverages and Primary Care Physician WS Enabled Not WS Enabled Send Request Notification to Notes Send Request Notification to pharmacy Function Service Collaborations to implement a single web service Collaborating apps encapsulated via web services Performance favored over loose coupling Authorization Service Patient Records Masters Service Credit Verification Office Scheduling Email Service Email System Outpatient Service HR 20 CBM SOMA SCA 2008 IBM Corporation
The Process of Service-Oriented Modeling and Architecture 21 CBM SOMA SCA 2008 IBM Corporation
Example Case Study 22 CBM SOMA SCA 2008 IBM Corporation
Scenario: Enable self-service using existing assets challenge: Government agency required to comply with mandate to make 80 percent of its transactions electronic by 2007. Approach: SOMA 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 SOAbased 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 CIR 23 CBM SOMA SCA 2008 IBM Corporation
IBM Techniques to Help Accelerate Innovation priority Drive growth and achieve differentiation by leveraging core competencies Develop a flexible set of business-aligned IT services that collectively fulfill an organization s business processes and goals while leveraging existing IT assets Perform a holistic analysis of the IT function to make it run as an integrated and seamless part of the business Identify changes necessary to increase IT infrastructure flexibility and reduce costs, based on business goals IBM technique Component Modeling Services SM CBM Service-Oriented Modeling and Architecture SOMA Component Modeling for the of IT CBM-BoIT Component Infrastructure Roadmap CIR Outcome 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 An SOA design recommendation that includes a detailed description of the SOA service model and solution architecture An IT process map of the activities and resources required to run the IT organization most effectively to support the organization s business objectives An incremental roadmap for IT based on analysis of current and desired target state of IT infrastructure capabilities, business initiatives and goals 24 CBM SOMA SCA 2008 IBM Corporation
Agenda Component 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 25 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 logic implementation of a service. Service Assembly Composition of components and services. Service Data data exchanged by services. 26 CBM SOMA SCA 2008 IBM Corporation
Open Service Component Architecture Developed by OSOA, a consortium of industry vendors. Standardization effort under way at OASIS. Open-source SCA runtime available in Apache Tuscany. > 44,000 downloads since early 2007 27 CBM SOMA SCA 2008 IBM Corporation
Service Oriented Architecture programming model Processes Human Tasks State Machines Rules BPEL + Extensions SCA Interface Selectors Maps Service Component Architecture Relationships Object Maps Common Event Objects Infrastructure WebSphere Application Server (J2EE Runtime) SCA in WebSphere Process Server v6 Objects (SDO-based technology) Service Component Architecture (SCA) 28 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 29 CBM SOMA SCA 2008 IBM Corporation
Service Component: Overview Java WSDL Port Type Interface Reference Java WSDL Port Type Java BPEL State Machine Rules Human Task Selector Interface Maps Implementation Types 30 CBM SOMA SCA 2008 IBM Corporation
Service Module: Overview SCA SCA Service Module Export Service Component Service Component SCA non-sca Standalone Reference Import Wire non SCA 31 CBM SOMA SCA 2008 IBM Corporation
Programming Model Modules are contain wired Service Components Service Components use SDOs for data Solutions are a collections of Modules Module B Web Client Module A Export Component Component Component Export Import Services Wires I Interfaces n t e References 32 CBM SOMA SCA 2008 IBM Corporation SDO
SCA Invocation Patterns SCA Export Component SCA Import Pseudo Synchronous Asynchronous Callback 33 CBM SOMA SCA 2008 IBM Corporation
WebSphere Integration Developer Key Features Objects Component Interfaces Visual Snippets Event Monitoring Used in Component Creation A s s e m b l y D i a g r a m Processes Exports Human Tasks Imports Selectors State Machines Mapping Components Rules Components Wired in Assembly Editor Resource Adaptors Web Services EJBs Java J2EE Artifacts 34 CBM SOMA SCA 2008 IBM Corporation
Component Assembly Editor Interface Reference Import Module Export 35 CBM SOMA SCA 2008 IBM Corporation
Composition - Process WS-BPEL compliant business process engine Simplified Process Editor Optional Generic Process Operations / Parameters Service Implementation Details hidden Transactions / Compensation 36 CBM SOMA SCA 2008 IBM Corporation
Integration Developer: Concepts Module Module Module Shared Library Shared Library Interfaces Objects Object Maps Relationships 37 CBM SOMA SCA 2008 IBM Corporation
Module 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 38 CBM SOMA SCA 2008 IBM Corporation
How to Build a Process Integration solution using BDD Rational RequisitePro Rational Portfolio Manager CIO Project Manager Understand Risk, Project Costs, and ROI Rational Data Architect Data Architect Identify and Manage Projects and Resources Model Relational Database Schemas RDB Mapping WebSphere Modeler Create, Simulate & Analyze As-Is Model Analyst Create & Manage System Requirements Trace Requirements & Create System Use Case Realizations Architect Create, Simulate, Analyze and Optimize To-Be Model UML Rational Software Architect Create Observation Model with KPIs & export to Monitor Create Financial Reports & ROI Estimates Test Model & Implement Services, & expose as Web Services Java Developer BPEL WSDL Rational Functional & Performance Tester Develop Portlets (App UI and Monitor) Portal Developer Choreograph services using BPEL, WSDL, etc. WebSphere Integration Developer Configure Human Task Manager (including Ad-Hoc) & Client Integration Developer Assemble Solution (BPEL, Human Task Manager, Rules, etc) 39 CBM SOMA SCA 2008 IBM Corporation Tester IBM Rational Team Unifying Platform WSDL EAR DBA Run-time Statistics Measures Model Runtime WebSphere Process Server WebSphere Portal WebSphere Monitor Deploy/Run Monitor WSDL EAR Operations Analyst
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 CBM SOMA SCA 2008 IBM Corporation