• Save
Develop  Composite  Business  Services To  Enable  Reuse In A  Service  Oriented  Architecture
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Develop Composite Business Services To Enable Reuse In A Service Oriented Architecture

  • 1,036 views
Uploaded on

 

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
1,036
On Slideshare
1,033
From Embeds
3
Number of Embeds
1

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 3

http://www.slideshare.net 3

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Ibm.com/software/ Google soa foundation
  • Replace IFW/BDW banking industry model

Transcript

  • 1. Develop Composite Business Services(CBS) to Enable Reuse in a Service-Oriented Architecture Carl Osipov, Software Architect, IBM Software Group Strategy [email_address] Dr. German Goldszmidt, Distinguished Engineer, IBM Software Group Strategy [email_address]
  • 2. Agenda
    • Introduction
      • Service-Oriented Architecture (SOA)
      • Composite Business Service (CBS)
        • Business Intents/Non-functional Requirements
        • Key Architectural Decisions
      • Customer relationship management (CRM) Incubation Project
        • CBS for CRM
        • Demo
    • Business Architecture
    • Transformation into solution architecture
    • Re-use approach
    • Conclusion
  • 3. The Team German Goldszmidt Mgr, SWG STAI Vamsi Mudiam Mgr, ISL Devaprasad Nadgir ISL, IT Architect Kirill Osipov (Carl) STAI, Software Architect Jatinder Malik ISL Mary Taylor, STAI Software Engineer Sobha Warrier ISL http://tssi.raleigh.ibm.com/pmwiki.php?n=Projects.Seminole CBS Incubation Project Strategy, Technology, Architecture and Incubation India Software Labs Dharan Veetil ISL
  • 4. … service oriented architecture (SOA)? An IT architectural style that supports service orientation What is …? … service orientation? A way of integrating your business as linked services and the outcomes that they bring … a business service? A repeatable business task – e.g., check customer credit; open new account. Business services can be developed as coarse grained web services … a composite business service (CBS)? A collection of business services built around a complex, end-to-end business process and may be optimized to a specific industry
  • 5. Service Oriented Architecture Different Things to Different People A programming model complete with standards, tools, methods and technologies such as web services A set of services that a business wants to expose to customers and clients Roles An architectural style which requires a service provider, requestor and a service description A set of architectural principles and patterns which address characteristics such as modularity, encapsulation, loose coupling, separation of concerns, reuse, composable and single implementation Implementation Architecture Business
  • 6. CBS Business Intents: Nonfunctional Requirements Policy and role based authentication and authorization Secure Conformance to prevailing standards Standards-based The ability to accommodate change and support multiple concurrent releases/versions Flexible Creation of an environment that supports IBM , Business Partner and 3rd party services Ecosystem Ability to measure the business value of using a service Measurable Ability to tailor behavior using business policies , business rules , and configuration parameters Configurable The replacement of predominantly manual tasks with a computerized process Automation Publishing of CBSs to allow for viewing and subscription through service contracts Published Ability to service multiple clients from a shared, common environment Multi-tenant The ability to react to events that occur at run time Dynamic Description Intents
  • 7. Overview of Architectural Decisions WSRR for IT level services and metadata Published Tivoli Access Manager, Federated Identity Manager, Directory Integrator Secure Industry de facto standards for banking/insurance models Standards-based SOA architecture WSRR to help with service change management Flexible WSRR to expose services to 3 rd parties through Portal UI. WBSF mediation modules for integration with 3 rd party services Ecosystem Apache Ant for end-to-end task orchestration of IBM WebSphere wsAdmin scripting, IBM WebSphere Portal xmlAccess scripting Automation WPF dashboard framework for ad-hoc measurements WebSphere Business Monitor for business process KPIs Measurable WPS Business Rule Manager WebSphere Service Registry & Repository(WSRR) for storage of metadata Configurable WebSphere Portal virtual portals to enable multi-tenancy Multi-tenant WebSphere Business Services Fabric (WBSF) for points of variability (PoV) using SCA, ESB WebSphere Portlet Factory dynamic profiles Dynamic Architectural Decision Intents
  • 8. The SOA Development Lifecycle
    • Regulatory transparency
    • Business/IT alignment
    • Process control
    • Gather requirements
    • Design
    • Model & Simulate
    • Discover & Source
    • Construct & Test
    • Compose
    • Integrate
      • People
      • Process
      • Information
    • Manage applications & services
    • Manage identity & compliance
    • Monitor business metrics
  • 9. Goal & Objectives of the CRM pilot
    • Goal: demonstrate how to build innovative CBS solutions
      • apply a structured business architecture (BA) specification , existing industry assets & SOA Foundation tooling and middleware
    • The objectives of the customer relationship management (CRM) banking project include:
      • Transform a BA specification into a CBS solution
      • Define an iterative model-driven development technique
      • Use banking industry models to design, develop and deploy re-usable assets
      • Enable artifact traceability through tooling / SOA Foundation
      • Explore cross-industry reuse
      • Document lessons learned on SWG products in support of CBS
  • 10. Example Scenario: Structured Business Model (Extension) - Customer Servicing
    • CSR verifies customer identity (2)
    Customer Recognition 2 Product Matching 7 Product Development 8 9 Customer Agreements 10 Contact Handler 5 Contact Routing 3 12 Contact/ Event History verify customer initiate dialogue check recent activity check eligibility get product specifics negotiate terms initiate set-up wrap up contact update history Training & Awareness CSR 11 Update Address 4 1 James Conner
    • James Conner calls Bank (1)
    • Mr. Conner informs CSR he’d like to update his address (3)
    • CSR reviews Mr. Conner’s recent contacts with the Bank (5) and notices he’s targeted for a Credit Card promotion.
    • … . Additional steps involved in the sale of the credit card
    • CSR completes the call (12).
    • CSR updates Mr. Conner’s address (4)
    • CSR checks Mr. Conner’s eligibility for the CC (7)
    • CSR checks Training and Awareness on steps involved in selling a credit card (6)
    get sales guidance 6
  • 11. Demo
  • 12. Agenda
    • Introduction
    • Business Architecture
      • Demo and Business Architecture & Industry Models
      • Business Component (BC) map
      • Scenario Interaction “Bubble” Diagram & Description
      • BC definition & example
      • BC template specification
      • Example: Customer Servicing
    • Transformation into solution architecture
    • Re-use approach
    • Conclusion
  • 13. Demo in Context of Business Architecture and Banking Industry Models Customer Recognition
    • Data
    getCustomerName() getStreetAddress() getPhoneNumber() getSSN() getCityStateZip() Demo screenshot retrieveCustomerProfile()
  • 14. Scope : Business Components (BCs) Retail Banking Component Business Model (CBM) Component Component Primary BCs: All component feature services implemented Secondary BCs: scenario service interfaces implemented Financial Management Business & Resource Admin Business Portfolio Management Customer Sales & Servicing New Business Development Product Delivery Customer Management Distribution Services Operational Services Financial Policies & Plans Staff Planning Systems Planning External Relations Asset & Liability Policy & Planning Segment Analysis & Planning Acquisition Planning Product Fulfillment Planning Credit Policy & Planning Product Services Planning Account Services Planning Business & Systems Architecture Business Unit Tracking Audit & Legal Compliance Product Design Oversight Relationship & Credit Oversight Business Unit Planning Building & Facilities Planning Product Portfolio Planning Financial Control Asset & Liability Oversight Product Services Oversight Account Services Oversight Product Tracking Facilities Maintenance & Operations Systems Development & Deployment Production Assurance (Help Desk) Business Unit Administration Staff Administration Systems Operations Customer Sale &Servicing Planning Customer Base (Portfolio & Analysis) Sales/ Servicing Administration Treasury/ Trading Asset & Liability Tracking General Ledger Financials Consolidation Fixed Asset Register Collections & Recovery Card Fulfilment Retail Advisory Services Retail Lending Fulfillment Wholesale Products Campaign Management Securitization/ Syndication Decisioning Account Reconciliation Case & Exception Handling Product Operations Oversight Fraud/AML Detection Application Processing Oversight Commissions Product Development Campaign Execution Marketing & Advertising Collateral Handling Credit Administration Branch non-cash Inventory Cash & Currency Handling Information Dissemination Document Administration Payments Deposit Fulfilment Customer Behavior Modeling Product Deployment Oversight Product Bundling Contact Routing Contact Handler Product Matching Contact/ Event History Customer Recognition Relationship Management Rewards Administration Correspondence Customer Accounting Customer Agreements Branch Design (all channels) Branch Operations Channel (non-branch) Operations Market Analysis Training & Awareness Internal Acquisition
  • 15. BC Interaction “Bubble” Diagram (PowerPoint) Up-sell/Cross-sell Identification Customer Servicing Customer Sales Initiation Customer Behavior Modeling Customer Base (Portfolio & Analysis) Relationship Management 7 Customer Recognition Deposit Fulfillment Product Development Training & Awareness Product Matching Customer Agreements Contact Handler 19 Contact Routing 9 25 Contact/ Event History Internal Acquisition 1 3 Selected components and descriptive interactions for 3 CRM Banking scenarios get filtering model 4 Segment shortfalls 2 initiate sales discussion 21 14 get sales guidance tagged for eligibility 6 5 select candidates 6a deposit activity 8 hot prospect 10 verify customer 11 initiate dialogue 13 check recent activity 15 get product specifics 17 initiate set-up 20 get campaign guidance 22 initiate set-up 23 update campaign 24 wrap up contact 26 update history check eligibility 14 16 negotiate terms detect hot prospect 18 12 update address
  • 16.
    • Internal Acquisition - is looking for business development opportunities
    • Customer Base – identifies sectors to acquisition that are not reaching their targets
    • Internal Acquisition – develops a campaign to drum up business
    • Behavior Models – is asked to develop an algorithm to isolate candidates
    • Internal Acquisition asks Customer Base to run the model and create a list
    • Internal Acquisition runs through the list notifying Relationship Management meanwhile… Deposit Fulfillment is keeping track of deposit activity
    • Relationship Management matches the campaign to the deposit activity…
    • … and where the fit looks good, flags the candidate in Customer Recognition
    • later a customer calls in ( Customer Contact Routing ), to update their address information
    • Customer Recognition verifies their identity and presents snapshot information
    • the call is passed to Contact Handler where the rep determines the call purpose
    • it’s a product request so the rep checks Contact Event History for recent activity
    A textual description of the "bubble" diagram a typical customer experience
    • the rep is new, so pulls up Training & Awareness for support
    • the rep is prompted to check customer eligibility by calling Product Matching - OK
    • next the rep is advised to get the latest product spec from Product Development
    • Product Matching takes over the sales dialogue and makes disclosures, captures triggers and negotiates terms
    • the customer accepts and Customer Agreement is initiated (not modeled here)
    • now the rep sees Customer Recognition has them flagged as hot prospect
    • the rep initiates the discussion for the internal campaign ( Contact Handler )
    • it’s a new campaign so advice is again sought from Training & Awareness
    • into selling with Product Matching – the customer is pre-approved for a new deposit product
    • the customer bites and a second Customer Agreement is initiated
    • Product Matching notifies Internal Acquisition of the sale
    • the rep finally wraps up the call in Contact Handler
    • Customer Contact Routing retrieves control and determines the contact is over
    • a log of the call activity – sales events and triggers is written to Contact History
    1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 6a
  • 17. Agenda
    • Introduction
    • Business Architecture
    • Transformation into solution architecture
      • Overview: Design Technique and Artifacts
      • Model Phase and Assemble & Deploy Phases
      • Structural Mapping of a BC to UML
      • Formalization of Associations
      • Capture Structured Business Models in UML
      • Structural Elements of Existing Asset Analysis
      • Structure elements of Top-Down
      • Service Identification Bottom-up
      • Example of Applying Technique
      • Use Cases
    • Re-use approach
    • Conclusion
  • 18. Design Technique and Artifacts Technical arch. specifications analyzed bottom-up Requirements (Bus. Use Cases) Bus. Component Specifications Banking Industry Models (IFW) 1 2 Bus. arch. specifications in PPT (informative) Map of Business Components Services Candidate Services ReqPro maintained by defined by analyzed top-down specified by derived from derived from Process/Interface Design Model organize & specify Bus. Use Case Associations & Collaborations Bus. Component Collaborations defined by Logical Data Model Physical Data Model Service Specifications User Experience Model Operational Model
  • 19. CBS Model Phase
    • 1. Create UML business use cases: actors, collaborations, interaction use cases
      • create UML classifiers to represent BizArch concepts
      • formalize associations between UML classifiers in line with BA semantics
      • represent the 3 CRM Banking scenarios
    • 2. Identify and map data objects required for the use cases
      • Map to BDW entities
    • 3. Identify candidate software services (use SOMA)
      • Top-down Domain Decomposition using BDW
      • Existing/Bottom-up leveraging IFW
    • 4. Specify the application architecture
      • Physical Data Model, Service Specifications, Operational Model, User Experience
    application architecture requirements application architecture specifications Requirements (Bus. Use Cases) Bus. Component Specifications IFW 1 2 Bus. architecture spec. in PPT (Informative) application architecture requirements application architecture specifications Requirements (Bus. Use Cases) Bus. Component Specifications IFW 1 2 Bus. architecture spec. in PPT (Informative) Heat map with Core Business Components Services Candidate Services ReqPro maintained by defined by analyzed top-down specified by analyzed bottom-up derived from derived from FS-BOM/IDM Activities/ Process Model organize & specify Bus. Use Case Associations & Collaborations Bus. Component Collaborations BDW Logical Data Model Physical Data Model Service Specifications User Experience Model Operational Model Heat map with Core Business Components Services Candidate Services ReqPro maintained by defined by analyzed top-down specified by analyzed bottom-up derived from derived from FS-BOM/IDM Activities/ Process Model organize & specify Bus. Use Case Associations & Collaborations Bus. Component Collaborations BDW Logical Data Model Physical Data Model Service Specifications User Experience Model Operational Model
  • 20. CBS Assemble, Deploy Phases
    • Implement the services selected
        • SCA, DB Schema, XSD schema
    • Implement multi-role, multi-channel presentation layer
        • Portlets, etc.
    • Expose Points of Variability
        • includes definition of the business policies and rules
    • Set up & configure execution runtime environment
        • WPS, WESB and WSRR
    • Package and Publish all artifacts
    • Deploy executables
    • (*) at each step maintain associations to ensure traceability
    Executable Artifacts Apply the standard SOA foundation development practices
  • 21. Use the Segment Shortfalls as an Example Up-sell/Cross-sell Identification Customer Servicing Customer Sales Initiation Customer Behavior Modeling Relationship Management 7 Deposit Fulfillment Product Development Training & Awareness Product Matching Customer Agreements Contact Handler 19 Contact Routing 9 25 Contact/ Event History Customer Recognition get filtering model 4 detect hot prospect 18 initiate sales discussion 21 13 get sales guidance tagged for eligibility 6 5 select candidates 6a deposit activity 8 hot prospect 10 verify customer 11 initiate dialogue 12 check recent activity 15 get product specifics 17 initiate set-up 20 get campaign guidance 22 initiate set-up 23 update campaign 24 wrap up contact 26 update history check eligibility 14 16 negotiate terms Customer Base (Portfolio & Analysis) Segment shortfalls 2 Internal Acquisition AO-OpInd 1 3
  • 22. Structural Mapping of a BC to UML Business Activities Business Features Internal Acquisitions BC Services BC Business Term Model Internal Campaign … Propose Campaign Plan << businessTerm >> Internal Campaign <<businessComponent >> Internal Acquisitions <<businessActivity>> Operate on Internal Campaign <<businessService >> Propose Campaign Plan Business Information Business Information << businessTerm >> Campaign Approach << businessTerm >> Campaign Analysis <<feature>> Schedule and initiate campaign activity across all involved parties derived from derived from Bus. Use Case Associations & Collaborations organize & specify Bus. Component Specifications
  • 23. Formalization of Associations between BC elements in UML Business Activities Business Features Internal Acquisitions BC Services BC Business Term Internal Campaign <<businessActivity>> Operate on Internal Campaign <<businessComponent >> Internal Acquisitions … Propose Campaign Plan Business Information Business Information <<businessTerm >> Internal Campaign << businessTerm >> Campaign Approach << businessTerm>> Campaign Analysis <<feature>> Schedule and initiate campaign activity across all involved parties <<businessService >> Propose Campaign Plan derived from derived from Bus. Use Case Associations & Collaborations organize & specify Bus. Component Specifications
  • 24. Capture Structured Business Models in UML
    • Specified a CRM Retail Banking scenario
      • Done by GBS S&C
      • Include Business Components (BCs) and their actions and business information
      • Improved based on feedback from the formal models
    • Model UML entities for the BCs
      • component package, UML component, actors
    • Capture scenario as sequence of collaborating UML-BCs
      • The entire scenario is represented as a business use case
      • The individual interactions of UML-BCs are application use cases
    • Update the original CBM II designs
      • Identify gaps in the PowerPoint designs
    • Build a use case model
      • Document use cases (refer to business information for data model)
        • Provide a textual description
      • Capture participating actors/ BCs
      • Associate the BC actions with the use cases
    • Augment the UML BC interactions
      • Update business use cases with associations to CBM II actions
    UML Representation of Component Interactions (RSA ) CBM II Scenario (PowerPoint) Business Use Cases (RSA) Segment shortfalls get filtering model tagged for eligibility Customer Behavior Modeling 4 Customer Base (Portfolio & Analysis) 2 5 Relationship Management 7 Customer Recognition 18 8 10 Internal Acquisition 1 3 6 23 select candidates hot prospect derived from Bus. Use Case Associations & Collaborations organize & specify Bus. Component Collaborations Segment shortfalls get filtering model tagged for eligibility Customer Behavior Modeling 4 Customer Base (Portfolio & Analysis) 2 5 Relationship Management 7 Customer Recognition 18 8 10 Internal Acquisition 1 3 6 23 select candidates hot prospect
  • 25. Structural Elements of Top-down Service Identification Internal Campaign realize has substitution Campaign Analysis realize for analyzed by <<businessTerm>> Campaign Approach <<businessTerm>> Campaign Analysis use case independent use case specific i.e. Segment Shortfalls CRM Retail Banking use case UML representation of BA Industry Model Service Endpoints & Implementation Campaign Segment Activity <<businessTerm>> Internal Campaign <<businessComponent >> Internal Acquisitions Services Candidate Services analyzed top-down specified by BDW Logical Data Model
  • 26. Example of Applying Top-down Service Identification
    • Pick a BC from a use case
      • e.g. Internal Acquisitions BC from Segment Shortfalls
      • Ensure existence of the structural mapping for BC
        • use case is associated with BC
        • business info. is defined for BC
    • Define a concrete realization for the BC business terms
      • Map BC business term to an industry model entity, using BDW subject areas
        • OM structural/transactional components
        • RSA/RDA model query
      • Assume one-to-one mapping between business information and an industry model entity may not be possible
      • Use existing asset/bottom up analysis when not possible
    Internal Campaign Campaign Segment Activity realize contain substitution Campaign Analysis realize for analyzed by <<businessTerm >> Internal Campaign <<businessComponent >> Internal Acquisitions <<businessTerm>> Campaign Approach <<businessTerm >> Campaign Analysis use the IFW model as a &quot;pre-defined&quot; domain decomposition for the banking industry Services Candidate Services analyzed top-down specified by BDW Logical Data Model
  • 27. Structural Elements of Existing Asset Analysis IFW Process Model Service Endpoints BPEL Workflow SCA Components Define Campaign Universe Define Campaign Schedule Select Market Segment
    • Identified workflow steps
      • Use case specific
    • Partner links
      • Concrete endpoint
      • Dynamic (registry) endpoint
    • Implementation
      • Integrate
      • Develop
    Develop Market Offering Campaign MarketSegmentMgmt CampaignPlanMgmt CampaignMgmt CampaignAnalysis Services Candidate Services analyzed top-down analyzed bottom-up FS-BOM/IDM Activities/ Process Model
  • 28. Example of Applying Existing Asset Analysis Technique
    • Pick a business process model
      • describe a process related to one of three phases of an interaction between 2 BCs
        • pre-conversational processing by the BCs
        • conversational (messaging) across 2 BCs
        • post-conversational processing by the BCs
      • e.g. there are approximately 80 processes in IFW OM 26
    • Identify activities from the process model
    • Define candidate services from the identified activities
    • Prepare to make realization decisions about the candidate services
    SCA Implementation 1 2 3 CampaignMgmt IFW Process Model Candidate Activity Define Campaign Universe Candidate Service Service Endpoints Services Candidate Services analyzed top-down analyzed bottom-up FS-BOM/IDM Activities/ Process Model
  • 29. Example of Applying Existing Asset Analysis Technique (continued)
    • Identify activities from the process model
      • Choose activity if it
        • Operates on business information of either of the 2 BCs
        • Sends messages across BC
      • Ignore activities that
        • Provide features that are out of scope for the project
          • e.g. Population Recount
        • Address application/technology aspects of the implementation
          • e.g. Define Database Extract
      • Include auxiliary activities that produce required information or state
        • Consider the activities in order (as a workflow)
        • Focus on pre/post conditions of the activities
    SCA Implementation 1 2 3 CampaignMgmt IFW Process Model Candidate Activity Define Campaign Universe Candidate Service Service Endpoints Services Candidate Services analyzed top-down analyzed bottom-up FS-BOM/IDM Activities/ Process Model
  • 30.
    • Define candidate services from the identified activities
      • Ensure that input/output for the services is well defined in terms of business information
        • e.g. business object as XSD, UML class or info. engineering (RDA) entity
      • Adopt a namespace scheme for the services (if one doesn't exist)
      • Assign a unique service name using the namespace scheme
    • Prepare to make realization decisions about candidate services
      • Plan to
        • Choose the services that will be needed for implementation
        • Generate (using Modeler, RSA or manually) WSDL definitions for the services
    Example of Applying Existing Asset Analysis Technique (continued) SCA Implementation 1 2 3 CampaignMgmt IFW Process Model Candidate Activity Define Campaign Universe Candidate Service Service Endpoints Services Candidate Services analyzed top-down analyzed bottom-up FS-BOM/IDM Activities/ Process Model
  • 31. Agenda
    • Introduction
    • Business Architecture
    • Transformation into solution architecture
    • Re-use approach
      • An insurance scenario
      • Challenge and Approach
      • Business components in the scenario
      • Reuse Technique Steps
      • Runtime CBS with Industry Specific Features
      • Business component template with industry features
    • Conclusion
  • 32. CRM Business Components Targeted for Reuse Component Component Reused Components Non-reused Components Financial Management Business & Resource Admin Business Portfolio Management Customer Sales & Servicing New Business Development Product Delivery Customer Management Distribution Services Operational Services Financial Policies & Plans Staff Planning Systems Planning External Relations Asset & Liability Policy & Planning Segment Analysis & Planning Acquisition Planning Product Fulfillment Planning Credit Policy & Planning Product Services Planning Account Services Planning Business & Systems Architecture Business Unit Tracking Audit & Legal Compliance Product Design Oversight Relationship & Credit Oversight Business Unit Planning Building & Facilities Planning Product Portfolio Planning Financial Control Asset & Liability Oversight Product Services Oversight Account Services Oversight Product Tracking Facilities Maintenance & Operations Systems Development & Deployment Production Assurance (Help Desk) Business Unit Administration Staff Administration Systems Operations Customer Sale &Servicing Planning Customer Base (Portfolio & Analysis) Sales/ Servicing Administration Treasury/ Trading Asset & Liability Tracking General Ledger Financials Consolidation Fixed Asset Register Collections & Recovery Card Fulfilment Retail Advisory Services Retail Lending Fulfillment Wholesale Products Campaign Management Securitization/ Syndication Decisioning Account Reconciliation Case & Exception Handling Product Operations Oversight Fraud/AML Detection Application Processing Oversight Commissions Product Development Campaign Execution Marketing & Advertising Collateral Handling Credit Administration Branch non-cash Inventory Cash & Currency Handling Information Dissemination Document Administration Payments Customer Behavior Modeling Product Deployment Oversight Product Bundling Contact Routing Contact Handler Product Matching Contact/ Event History Rewards Administration Correspondence Customer Accounting Customer Agreements Branch Design (all channels) Branch Operations Channel (non-branch) Operations Market Analysis Internal Acquisition Customer Agreements Product Matching Contact Routing Product Development Training And Awareness Training & Awareness Deposit Fulfillmenth Deposit Fulfilment Relationship Management Relationship Management Customer Recognition Customer Recognition Business components referenced in a Request Quote insurance scenario Customer Behavior Modeling Relationship Management Customer Recognition Internal Acquisition Deposit Fulfilment Training & Awareness Retail Banking Component Business Model (CBM)
  • 33. Technique Re-usability of a BC (businessService, businessAction and Features) across industries <<businessService >> Manage Customer Profile Information <<feature>> Support multiple tiers of ID verification/ authorization <<feature>> Support various combinations of flags and indicators retrieveCustomerDetails() retrieveContactHistory() getCustomerName() getAccessToken() getCreditRating() getImportanceLevel() getPropensityScore()
      • IFW
      • IAA
    S6: Illustrated potential decomposition of a businessService (e.g. ManageCustomerProfileInformation) into multiple IFW and IAA operations S5: Identified Features supporting businessOperations for common BC-interaction - Banking: Support multiple tiers of ID verification / authorization - Insurance: Support various combinations of flags and indicators S4: Identified the businessAction invoked from the businessService - e.g. Operate on Customer Snapshot (AO-OpInd) S3: Identified the businessService used by the BC-interaction - e.g. ManageCustomerProfileInformation in Verify Customer S2: Identified BC-interactions that were common between the scenarios - Retail banking CRM and insurance Request Quote, e.g. Verify Customer S1: Created a ‘bubble’ diagram to represent the BC-interactions Artifacts Steps <<businessOperation>> Operate on Customer Snapshot 24 Customer Recognition 24 Contact Routing verify customer
  • 34. Common businessService - ManageCustomerProfileInformation Customer Recognition
    • Segment Data
    Customer User Details Service Customer Personal Details Service Customer Segment Details Service
    • Personal Details Data
    • User Details Data
    getSegment() getProfileID() isHomeOwner() getCustomerName() getStreetAddress() getPhoneNumber() Manage Customer Profile Information
  • 35. Illustrated decomposition of a businessService into IFW and IAA operations Retail Banking Feature Insurance Feature IFW IAA BPEL BPEL getCustomerName() getAccessToken() getCreditRating() getImportanceLevel() getPropensityScore() retrieveCustomerDetails() retrieveContactHistory() GetRiskSegment GetCustomerPersonalDetails <<feature >> Support various combinations of flags and indicators <<feature >> Support multiple tiers of ID verification/ authorization GetCustomerPersonalDetails GetMarketSegment GetUserDetails
  • 36. Runtime CBS with Industry Specific Features Runtime Integration getCustomerPersonalDetails() getMarketSegment() getUserDetails() getRiskSegment() WebSphere Process Server WebSphere Service Registry and Repository Multi-Role Multi- Channel IVR WebSphere Portal Server Broker CSR Operational Capability exposed as Web Service GetRiskSegment GetCustomerPersonalDetails Bind Common services Enforce Mediate GetCustomerPersonalDetails GetMarketSegment GetUserDetails WebSphere Business Service Fabric (WBSF) <<businessService >> Manage Customer Profile Information Banking Services Insurance Services
  • 37. Customer Recognition Contact Routing 2 verify customer <<businessOperation >> Operate on Customer Snapshot <<businessService >> Manage Customer Profile Information GetRiskSegment GetCustomerPersonalDetails GetCustomerPersonalDetails GetMarketSegment <<feature >> Support multiple tiers of ID verification/ authorization <<feature >> Support various combinations of flags and indicators Retail Banking Feature Insurance Feature <<businessComponent >> Customer Recognition GetUserDetails IFW IAA Interaction Diagram UML Representation BPEL on Process Server IFW/IAA Services at runtime getCustomerName() getAccessToken() getCreditRating() getImportanceLevel() getPropensityScore() retrieveCustomerDetails() retrieveContactHistory()
  • 38. developerWorks Articles
    • Make composite business services adaptable with points of variability
      • Choosing the right implementation
      • Using dynamic service mediation in WebSphere Business Services Fabric
    • Building SOA composite business services
      • Develop SOA composite business services
      • Migrate business integration projects from WebSphere Application Developer-IE v5.1 to WebSphere Integration Developer v6.0.1
      • Build consumable Web Services using the REST architectural style in WebSphere
      • Develop measurable composite applications with the Common Event Infrastructure
      • Using IBM WebSphere Business Modeler
      • Automate build and deployment steps
      • Supporting multi-tenancy for composite business services
  • 39. Agenda
    • Introduction
    • Business Architecture
    • Transformation into solution architecture
    • Re-use approach
    • Conclusion
      • Review
        • Showed a demo of a the retail banking CRM project
        • Described a business architecture in terms of collaborating business components
        • Reviewed a technique for producing solution architecture specifications linked to a business architecture
        • Described an approach to reuse
  • 40. Questions
  • 41. Thank You