Patterns for e-business :
Leveraging Architectural Patterns in
Defining Enterprise Architecture &
Solution Architectures

...
Agenda




  What are Patterns?
  IBM Patterns for e-business Overview
  Leveraging architectural patterns in Solution Arc...
What are Patterns?


  A pattern is a "generalized, named problem to solution mapping“

  A pattern captures a successful ...
Why are patterns important?


  A pattern is a reusable generalization (or abstraction) that can be used
  as the starting...
There are four main categories of "patterns" in Software Engineering


                                                   ...
Agenda




  What are Patterns?
  IBM Patterns for e-business Overview
  Leveraging architectural patterns in Solution Arc...
Patterns for e-business


                                                Patterns for e-business identify
               ...
Patterns for e-business: Business Patterns

Business patterns identify the most commonly observed interactions between
Use...
Patterns for e-business: Integration Patterns

Complex applications can be built by combining multiple Business patterns t...
Patterns for e-business:
 Cardinality between different types of Patterns
                     Business & Integration Patt...
Patterns for e-business: Application Patterns


Each of the Business & Integration patterns can be implemented using one o...
Legend used for expressing Application Patterns



                                                                     Re...
Application Patterns for Self-Service



  Stand Alone Single Channel
   1.   Pres.
                     synch
           ...
Patterns for e-business: You choose between one or the other
Application Pattern based on Business & IT Drivers.

The foll...
Application Patterns for Information Aggregation


    Population – Single Step                                           ...
Application Patterns for Extended Enterprise

Document Exchange
Partner A                                                 ...
Application Patterns for Collaboration


                          Synchronous
       Collaboration                    Col...
Application Patterns for Access Integration



Pervasive Device Access                                                    ...
Application Patterns for Application Integration (Process Focused)


             Direct Connection                       ...
Application Patterns for Application Integration (Data Focused)



 Propagation                                           ...
Patterns for e-business: Runtime Patterns


Runtime Patterns capture the logical topology of the architecture that is nece...
Self-Service: Application Patterns, Runtime Patterns & Product Mapping
  7 Application Patterns for Self-Service          ...
Extended Enterprise:                      Application Patterns & Runtime Patterns
5 Application Patterns for Extended Ente...
Patterns for e-business: Composite Patterns




                                               Does a Composite Pattern al...
Patterns for e-business: Composite Patterns

Composite Pattern for Electronic Commerce Solutions                          ...
Agenda




  What are Patterns?
  IBM Patterns for e-business Overview
  Leveraging architectural patterns in Solution Arc...
Technique for leveraging Patterns for e-business in
Solution Architecture definition


This technique and the associated s...
Example: e-Gov GeoSpatial Information One-Stop Initiative



The Geospatial Information One-Stop will provide access to th...
e-Gov GeoSpatial Initiative – Step 1 & 2 Develop SOD


                                                                   ...
e-Gov GeoSpatial Initiative – Step 3 Identify Business Patterns


                Self-Service                       Infor...
e-Gov GeoSpatial Initiative – Step 4 Identify Integration Patterns



                Self-Service                        ...
e-Gov GeoSpatial Initiative – Step 6 & 7 Identify Application Patterns



                Self-Service ::Agent            ...
e-Gov GeoSpatial Initiative –
   Step 8 & 9 Integrate Packages and develop Technical Architecture

Identify runtime patter...
Agenda




  What are Patterns?
  IBM Patterns for e-business Overview
  Leveraging architectural patterns in Solution Arc...
Enterprise Architecture



                             Performance Reference Model (PRM)
                               •...
Applying architectural patterns at Enterprise Architecture level


At Enterprise Architecture level, Patterns for e-busine...
Insurance Company Example: Application Function Model


                                                                  ...
Insurance Company Example: Identify Business Patterns
      Self-Service                                                  ...
Insurance Company Example: Identify Integration Patterns
      Self-Service                                               ...
Patterns for e-business can be customized based on agency
technology choices to provide prescriptive guidelines (not just
...
Leveraging Patterns for e-business in defining Enterprise
Architecture and Solution Architectures provides a number of
ben...
Thank You


                         Further information can be found at:

•    Patterns for e-business Web Site: http://w...
Upcoming SlideShare
Loading in …5
×

Adaptive Enterprise Architecture

997 views

Published on

  • Be the first to comment

  • Be the first to like this

Adaptive Enterprise Architecture

  1. 1. Patterns for e-business : Leveraging Architectural Patterns in Defining Enterprise Architecture & Solution Architectures Guru Vasudeva Architecture Center of Excellence - Federal IBM Global Services e-mail: vasudeva@us.ibm.com Phone: 301-803-3181 Patterns for e-business web site: http://www.ibm.com/developerworks/patterns Architecture Center of Excellence - Federal IBM Global Services © IBM Global Services, 2003
  2. 2. Agenda What are Patterns? IBM Patterns for e-business Overview Leveraging architectural patterns in Solution Architecture definition Applying architectural patterns at Enterprise Architecture level © IBM Global Services, 2003 Architecture Center of Excellence - Federal 2
  3. 3. What are Patterns? A pattern is a "generalized, named problem to solution mapping“ A pattern captures a successful solution to a repeating problem in a particular context In general, a pattern is documented using the following sections: − Name: A name used for identification − Problem: A repeating problem that occurs in a domain − Solution: Best practice solution to that problem − Consequences: Advantages and disadvantages of the recommended solution − Examples: A few examples where the recommended solution has already been applied Christopher Alexander's research on buildings and town design is often considered the pioneering work on pattern based thinking © IBM Global Services, 2003 Architecture Center of Excellence - Federal 3
  4. 4. Why are patterns important? A pattern is a reusable generalization (or abstraction) that can be used as the starting point in future solutions Benefits of patterns − Provide a mechanism to capture knowledge and experience − Provide a common vocabulary amongst architects and designers − Facilitate reuse of approaches that have been successful elsewhere and thus contribute towards the following aspects of a project : Reducing risk Increasing quality Improving delivery time "One thing expert designers know not to do is to solve every problem from first principles. Rather, they reuse solutions that have worked for them in the past. When they find a good solution, they use it again and again. Such experience is part of what makes them experts.“ Design Patterns, Gamma, Helm, Johnson & Vlissides 1995 © IBM Global Services, 2003 Architecture Center of Excellence - Federal 4
  5. 5. There are four main categories of "patterns" in Software Engineering Reference architectures Industry-related: Technical: - Insurance - ESS Reference Arch. - Banking Architectural Patterns Business Application Focused Abstract Technology Focused - Patterns for e-business - Layers - Pipes & Filters Design Patterns Analysis Patterns Abstract Factor Party Proxy Organization Facade Account A reference architecture is often composed of multiple architectural patterns. Similarly, an architectural pattern may leverage multiple design patterns and analysis patterns. © IBM Global Services, 2003 Architecture Center of Excellence - Federal 5
  6. 6. Agenda What are Patterns? IBM Patterns for e-business Overview Leveraging architectural patterns in Solution Architecture definition Applying architectural patterns at Enterprise Architecture level © IBM Global Services, 2003 Architecture Center of Excellence - Federal 6
  7. 7. Patterns for e-business Patterns for e-business identify and document proven architectural patterns & design guidelines gleaned from successful project. These patterns are like Lego blocks that help us to assemble solutions rapidly and achieve high levels of best practice & component reuse within an enterprise “Patterns for e-business – A Strategy for Reuse” Book Jonathan Adams, Srinivas Koushik, Guru Vasudeva, and George Galambos Book Web site : http://www.iirpubs.com/ibmpress/5206.cfm © IBM Global Services, 2003 Architecture Center of Excellence - Federal 7
  8. 8. Patterns for e-business: Business Patterns Business patterns identify the most commonly observed interactions between Users, Businesses, and Data. Users accessing transactions on a 24x7 Self Service basis (a.k.a. User to Business) Users working with one another to share data and information Collaboration (a.k.a. User to User) Data from multiple Information Aggregation sources aggregated (a.k.a. User to Data) and presented across multiple channels Integrating data and processes across Extended Enterprise enterprise boundaries (a.k.a. Business to Business) © IBM Global Services, 2003 Architecture Center of Excellence - Federal 8
  9. 9. Patterns for e-business: Integration Patterns Complex applications can be built by combining multiple Business patterns together. This is accomplished by using Integration patterns as the "glue" between Business patterns. Application Integration Access Integration Provide seamless and Connect, Interface or consistent access to business Integrate databases and functions. systems Typical functions provided include Typical integration can be based Single-signon, Personalization, on Function, Type of Integration, Transcoding etc. Mode of Integration and by Topology © IBM Global Services, 2003 Architecture Center of Excellence - Federal 9
  10. 10. Patterns for e-business: Cardinality between different types of Patterns Business & Integration Patterns Self Service (a.k.a. User to Business) Application Integration Access Integration Collaboration (a.k.a. User to User) Cardinality between different types of Patterns Information Aggregation (a.k.a. User to Data) Runtime pattern Extended Enterprise Application (a.k.a. Business to Business) pattern Runtime pattern Business or Integration pattern Runtime pattern Application pattern Runtime pattern © IBM Global Services, 2003 Architecture Center of Excellence - Federal 10
  11. 11. Patterns for e-business: Application Patterns Each of the Business & Integration patterns can be implemented using one or more application patterns. Each Application pattern describes structure, placement, & integration between logical tiers of the application. Business Actors & Interactions Business & IT Drivers © IBM Global Services, 2003 Architecture Center of Excellence - Federal 11
  12. 12. Legend used for expressing Application Patterns Read only data Application node containing new or modified components Transient data • Work in progress • Cached committed Application node • Staged containing existing components with no need for modification or which cannot be changed Read write data A process that is external and transparent to the current application. However the interfaces to this Meta Data process are well- •Templates defined © IBM Global Services, 2003 Architecture Center of Excellence - Federal 12
  13. 13. Application Patterns for Self-Service Stand Alone Single Channel 1. Pres. synch App. Router App 2 Pres2 synch synch App1 5. Pres1 Router Directly Integrated Single Channel Pres. synch App. synch/ Decomposition 2. Pres. App. App. Pres2 App 2 asynch synch synch/ Pres1 App1 Decomp asynch 6. Agent App 2 Pres2 synch/ synch/ App1 7. Pres1 Agent asynch asynch WIP CRM LOB © IBM Global Services, 2003 Architecture Center of Excellence - Federal 13
  14. 14. Patterns for e-business: You choose between one or the other Application Pattern based on Business & IT Drivers. The following Business & IT drivers guide organizations to choose Self-Service::Router Application Pattern Business Drivers − Improve organizational efficiency − Reduce the latency of business events − Easy to adapt during mergers and acquisitions − Integration across multiple delivery channels IT Drivers − Minimize total cost of ownership (TCO) − Leverage existing skills − Leverage legacy investment − Back end application integration − Minimize enterprise complexity − Maintainability − Scalability © IBM Global Services, 2003 Architecture Center of Excellence - Federal 14
  15. 15. Application Patterns for Information Aggregation Population – Single Step Population – Crawl and Discover Meta Data Selection Criteria Meta Data Crawl Space Population Read Application Read-Write Retrieve & Parse Tier Crawl & Discover Documents Tier Read-Only 1 Write Read-Only 2 Write Read-write Categorized Index Read-write Population – Multiple Step Population – Summarization Selection Criteria Meta Data Crawl Space Retrieve & Parse Crawl, Discover, Documents & Summarization Read-Only 1 Tier Read-Only 2 Write Categorized Index with Summary Read-write © IBM Global Services, 2003 Architecture Center of Excellence - Federal 15
  16. 16. Application Patterns for Extended Enterprise Document Exchange Partner A Partner B Backend Translator 1:N Partner Application 2 Tier Tier Backend Asynchronous, Application 1 Mutually agreed message format Work in Exposed Application Read-write Progress Partner A Partner B Read-write Private and Public processes Exposed 1:N Partner Application 2 Tier Exposed Asynchronous Application 1 Read-write Read-write Exposed Business Services Private and Public processes Partner A Partner B Backend N:1 Exposed 1:N Partner Applicatio Business Asynchronous, Tier Synchronous, Services n2 Mutually agreed Backend Asynchronous Tier message format Applicatio n1 Managed Public Process Read-write Read Only Partner A Partner B Read-write Private and Public processes Backend Public N:1 1:N Partner Applicatio Process Tier n2 Backend Synchronous, Rules Applicatio Asynchronous, Asynchronous Tier Server-specified or n1 mutually agreed Read-write Read Only message format Work in Read-write Progress Private processes Public processes © IBM Global Services, 2003 Architecture Center of Excellence - Federal 16
  17. 17. Application Patterns for Collaboration Synchronous Collaboration Collaboration Collaboration synchronous Collaboration Client Client Collaboration Client asynchronous Server Client Local Shared Local Local Data Data Settings Settings Point-to-Point Collaboration Store and Retrieve Collaboration Shared Local Application Address Shared Book Application Collaboration synchronous Client Collaboration Collaboration synchronous Collaboration Client Collaboration Workflow Server Client Synch Server Application Synch Collaboration synchronous Asynch Client Asynch Shared Local Directory Shared Local WIP Shared Workflow Directory Application Address Data Address Book Data Data Rules Book Directed Collaboration Managed Collaboration © IBM Global Services, 2003 Architecture Center of Excellence - Federal 17
  18. 18. Application Patterns for Access Integration Pervasive Device Access Web Single Sign-On Pervasive Application 1 Pervasive Synchronous Synchronous Device Access synchronous synchronous Device Single Sign-On Application1 Asynchronous Tier Client Application 2 Tier Tier Application2 Read-Write Meta-Data Read-Write Read-Write Read-Write Extended Single Sign-On Personalized Delivery P e rs o n a liz a tio n Client Single Sign-On Application 1 Security Enterprise R u le s Tier & Role-Based Integration Application Access Application 2 C lie n t A p p lic a tio n 1 T ie r A p p lic a tio n 2 © IBM Global Services, 2003 Architecture Center of Excellence - Federal 18
  19. 19. Application Patterns for Application Integration (Process Focused) Direct Connection Broker 1:N Application Application Application Broker Rules Application Synchronous Tier Tier Tier Asynchronous Tier Tier Application Tier Work in Read-write Progress Read-write Read-write Managed Process Application BPM Rules Application Tier Tier Tier Application Tier Work in Read-write Progress Read-write Read-write © IBM Global Services, 2003 Architecture Center of Excellence - Federal 19
  20. 20. Application Patterns for Application Integration (Data Focused) Propagation Replication App 1 App 2 App 1 App 2 App 3 population Transform Rules feedback population Operational Data Store Federated Repository App N App N App 1 App 2 App 2 Unified App 1 Query Transform ... ... Rules population © IBM Global Services, 2003 Architecture Center of Excellence - Federal 20
  21. 21. Patterns for e-business: Runtime Patterns Runtime Patterns capture the logical topology of the architecture that is necessary to support a selected Application Pattern. It identifies software, middleware, and hardware nodes required based on a set of Service Level Characteristics (e.g. availability, security, etc.) Business Actors & Interactions Business & IT Drivers Service Level Characteristics © IBM Global Services, 2003 Architecture Center of Excellence - Federal 21
  22. 22. Self-Service: Application Patterns, Runtime Patterns & Product Mapping 7 Application Patterns for Self-Service Self-Service::Router Application Pattern App 2 Pres2 Stand Alone Web-Up synch synch Pres1 App1 Router Directly Integrated Web-Up As-is Host Self Service Customized Presentation Select based on Router Business & IT Decomposition Drivers Select based on Agent Service Level Characteristics Self-Service::Router Product Mapping & Self-Service::Router Runtime Pattern Redbook Select based on product decisions © IBM Global Services, 2003 Architecture Center of Excellence - Federal 22
  23. 23. Extended Enterprise: Application Patterns & Runtime Patterns 5 Application Patterns for Extended Enterprise Managed Public Process Application Pattern Partner A Partner B Document Exchange Public Backend Partner Applicatio N:1 Process 1:N Exposed Application n2 Tier Backend Synchronous, Rules Extended Applicatio Asynchronous Tier Asynchronous, Enterprise Exposed Business Services n1 Server-specified or mutually agreed Select based on Read-write Read Only message format Managed Public Process Business & IT Work in Read-write Drivers Progress Private processes Public processes Select based on Service Level Characteristics Managed Public Process Runtime Pattern © IBM Global Services, 2003 Architecture Center of Excellence - Federal 23
  24. 24. Patterns for e-business: Composite Patterns Does a Composite Pattern already exist ? Business Actors & Interactions © IBM Global Services, 2003 Architecture Center of Excellence - Federal 24
  25. 25. Patterns for e-business: Composite Patterns Composite Pattern for Electronic Commerce Solutions Composite Pattern for Portals Self Service Self Service Application Integration Application Integration Access Integration Access Integration Collaboration Collaboration Information Aggregation Information Aggregation Extended Enterprise Extended Enterprise Composite Pattern for Enterprise Intranet Portal Composite Pattern for a Collaboration ASP Self Service Application Integration Access Integration Access Integration Collaboration Collaboration Information Aggregation Blue – Mandatory Business Patterns Red – Optional Business Patterns - Variations © IBM Global Services, 2003 Architecture Center of Excellence - Federal 25
  26. 26. Agenda What are Patterns? IBM Patterns for e-business Overview Leveraging architectural patterns in Solution Architecture definition Applying architectural patterns at Enterprise Architecture level © IBM Global Services, 2003 Architecture Center of Excellence - Federal 26
  27. 27. Technique for leveraging Patterns for e-business in Solution Architecture definition This technique and the associated steps outlined below are further elaborated with case studies in our book “Patterns for e-business – A Strategy for Reuse” Step 1: Develop High Level Business Description Step 2: Develop Solutions Overview Diagram Step 3: Identify Business Patterns Step 4: Identify Integration Patterns Step 5: Identify Composite Patterns Step 6: Identify Application Patterns Step 7: Summarize all the Application Patterns Required Step 8: Integrate a package into the Solution Step 9: Develop the Technical Architecture © IBM Global Services, 2003 Architecture Center of Excellence - Federal 27
  28. 28. Example: e-Gov GeoSpatial Information One-Stop Initiative The Geospatial Information One-Stop will provide access to the federal government's spatial data assets in a single location and help make state and local spatial data assets more accessible.federal agencies will also make their planned and future spatial data activities available to state and local governments to promote collaboration and reduce duplicative efforts.Data standards developed through an intergovernmental process will result in data that can be used multiple times for multiple purposes,saving taxpayer money.It will also help empower the private sector by communicating the characteristics of a desired standardized data product. © IBM Global Services, 2003 Architecture Center of Excellence - Federal 28
  29. 29. e-Gov GeoSpatial Initiative – Step 1 & 2 Develop SOD Various National Sensors / Data Providers Libraries Metadata About available Search Information (ODS) National Technical Means GeoSpatial Virtual Download & Information Knowledge Store Users from Exploit Local & State (Federation) Govt Commercial Sources Data Request for Supply Chain Provider New Data Management Specific Tasking © IBM Global Services, 2003 Architecture Center of Excellence - Federal 29
  30. 30. e-Gov GeoSpatial Initiative – Step 3 Identify Business Patterns Self-Service Information Aggregation Extended Enterprise Various National Sensors / Data Providers Libraries Metadata About available Search Information (ODS) National Technical Means GeoSpatial Virtual Download & Information Knowledge Store Users from Exploit Local & State (Federation) Govt Commercial Sources Data Request for Supply Chain Provider New Data Management Specific Tasking Self-Service Extended Enterprise © IBM Global Services, 2003 Architecture Center of Excellence - Federal 30
  31. 31. e-Gov GeoSpatial Initiative – Step 4 Identify Integration Patterns Self-Service Information Aggregation Extended Enterprise Various National Sensors / Data Providers Libraries Access Integration Metadata About available Search Information (ODS) National Technical Means GeoSpatial Virtual Download & Information Knowledge Store Users from Exploit Local & State (Federation) Govt Application Integration Commercial Sources Data Request for Supply Chain Provider New Data Management Specific Tasking Self-Service Extended Enterprise © IBM Global Services, 2003 Architecture Center of Excellence - Federal 31
  32. 32. e-Gov GeoSpatial Initiative – Step 6 & 7 Identify Application Patterns Self-Service ::Agent Information Aggregation:: Extended Enterprise :: Multi-Step Population Managed Public Process Various Access Integration:: National Sensors / Data Providers Single-Sign On & Personalized Delivery Libraries Metadata About available Search Information (ODS) National Technical Means GeoSpatial Virtual Download & Information Knowledge Store Users from Exploit Local & State (Federation) Govt Application Integration:: Commercial Federated Repository Sources Data Request for Supply Chain Provider New Data Management Specific Tasking Self-Service ::Router Extended Enterprise ::Managed Public Process © IBM Global Services, 2003 Architecture Center of Excellence - Federal 32
  33. 33. e-Gov GeoSpatial Initiative – Step 8 & 9 Integrate Packages and develop Technical Architecture Identify runtime patterns for the following selected application patterns and combine them into an integrated architecture Extended Enterprise::Managed Public Process Access Integration:: Web Single Sign-On Partner A Partner B synchronous synchronous Client Single Sign-On Application1 Backend Public Partner N:1 1:N Tier Applicatio Process Tier Tier n2 Backend Synchronous, Rules Asynchronous, Applicatio Application2 n1 Asynchronous Tier Server-specified or mutually agreed Read-write Read Only message format Work in Read-write Progress Read-Write Private processes Public processes Read-Write Read-Write Access Integration::Personalized Delivery Self-Service::Agent App 2 Pres2 Personalization synch/ synch/ App1 7. Pres1 Agent asynch asynch Rules WIP CRM Client Application1 LOB Tier Application2 Application Integration::Federated Repository App 2 App N Unified App 1 Query ... © IBM Global Services, 2003 Architecture Center of Excellence - Federal 33
  34. 34. Agenda What are Patterns? IBM Patterns for e-business Overview Leveraging architectural patterns in Solution Architecture definition Applying architectural patterns at Enterprise Architecture level © IBM Global Services, 2003 Architecture Center of Excellence - Federal 34
  35. 35. Enterprise Architecture Performance Reference Model (PRM) • Government-wide Performance Measures & Outcomes • Line of Business-Specific Performance Measures & Outcomes Business-Driven Approach Patterns for Business Reference Model (BRM) • Lines of Business e-business assets • Agencies, Customers, Partners are useful for the application & Service Component Reference Model (SRM) technology • Service Layers, Service Types • Components, Access and Delivery Channels architecture Data Reference Model (DRM) • Business-focused data standardization • Cross-Agency Information exchanges Technical Reference Model (TRM) • Service Component Interfaces, Interoperability • Technologies, Recommendations From the OMB FEA and Reference Models perspective Layered Architectural Patterns documented by Patterns for e-business can be used to establish a clear linkage between BRM and SRM/TRM. © IBM Global Services, 2003 Architecture Center of Excellence - Federal 35
  36. 36. Applying architectural patterns at Enterprise Architecture level At Enterprise Architecture level, Patterns for e-business can be used for analyzing a portfolio of applications. Based on this analysis one can identifying frequently occurring architectural patterns in the enterprise and thus establish prescriptive target architectures for those category of applications. Step 1: Develop enterprise level Application Function Model Step 2: Identify Business Patterns Step 3: Identify Integration Patterns Step 4: Based on this analysis, identify frequently occurring . architectural patterns in the application portfolio Step 5: Establish prescriptive target architectures for frequently occurring . category of applications in the portfolio © IBM Global Services, 2003 Architecture Center of Excellence - Federal 36
  37. 37. Insurance Company Example: Application Function Model Disability LOB Engines Life LOB Engines Customer Facing Functions P&C LOB Engines Insurance Electronic eMarketplaces Quotes Rating Underwriting Bill Payment $ $ $ Policy Claim Policy Billing Inquiry Submission Processing Customers Billing Application Claims Actuarial Inquiry Submission Processing $ $ $ Claims Inquiry CSRs Operational Analysis Data Stores Agent Productivity Tools Enterprise Integrated Data Warehouse $ $ $ Customer Info Contact Customer Decision Direct Management Acquisition Support Agents Integrated Marketing Systems Commission Product Info Management $ $ $ Corporate Functions (Back Office) Other Employee Self-Service Accounting Financials Employees Personal 401k Law & Profile Management Actuarial Compliance Benefits HR Management Management © IBM Global Services, 2003 Architecture Center of Excellence - Federal 37
  38. 38. Insurance Company Example: Identify Business Patterns Self-Service Extended Enterprise Disability LOB Engines Life LOB Engines Customer Facing Functions P&C LOB Engines $ Insurance $ $ Electronic eMarketplaces Quotes Rating Underwriting Bill Payment Customers Policy Claim Policy Billing Inquiry Submission Processing $ $ $ Billing Application Claims Actuarial Inquiry Submission Processing Information Aggregation CSRs Claims Inquiry Operational Analysis $ Data Stores $ $ Agent Productivity Tools Enterprise Integrated Data Warehouse Agents Customer Info Contact Customer Decision Direct Management Acquisition Support Integrated Marketing $ Systems $ $ Commission Product Info Management Other Employees Corporate Functions (Back Office) Employee Self-Service Accounting Financials Personal 401k Law & Profile Management Actuarial Compliance Benefits HR Management Management Self-Service © IBM Global Services, 2003 Architecture Center of Excellence - Federal 38
  39. 39. Insurance Company Example: Identify Integration Patterns Self-Service Extended Enterprise Disability LOB Engines Life LOB Engines Customer Facing Functions P&C LOB Engines Insurance Electronic eMarketplaces Quotes Rating Underwriting Bill Payment $ $ $ Policy Claim Policy Billing Inquiry Submission Processing Customers Billing Application Claims Actuarial Inquiry Submission Processing Information Aggregation $ $ $ Claims Application Integration Inquiry Access Integration CSRs Operational Analysis Data Stores Agent Productivity Tools Enterprise Integrated Data Warehouse $ $ $ Customer Info Contact Customer Decision Direct Management Acquisition Support Agents Integrated Marketing Systems Commission Product Info Management $ $ $ Corporate Functions (Back Office) Other Employee Self-Service Accounting Financials Employees Personal 401k Law & Profile Management Actuarial Compliance Benefits HR Management Management Self-Service © IBM Global Services, 2003 Architecture Center of Excellence - Federal 39
  40. 40. Patterns for e-business can be customized based on agency technology choices to provide prescriptive guidelines (not just WHAT technologies to use but also HOW to use it) Technical Reference Model (TRM): Defines Agency Technology and Product Choices Customized Runtime Patterns reflect the technology choices from the TRM and provide clear guidance for Systems Integrators Technical Reference Model: Also defines the technology adoption life cycle Current 2 Years 5 Years Current Tactical Strategic Retirement Mature Technologies List & Standards Containment Emerging List Technologies © IBM Global Services, 2003 Architecture Center of Excellence - Federal 40
  41. 41. Leveraging Patterns for e-business in defining Enterprise Architecture and Solution Architectures provides a number of benefits Easily link Business Architecture to Technology Architecture Promotes convergence of multiple business applications on similar architecture by providing clear direction to application development groups and systems integrators. Knowledge Management: Promotes sharing and reuse of best practices between application groups. Reduces risk and cost of multiple projects in an organization. Improves the quality and delivery speed of multiple projects in an organization. Enables server consolidation through convergence on similar architecture thus resulting in reduced Total Cost of Ownership (TCO). Leverage scarce technical skills across multiple similar projects. Enables effective architecture governance process. © IBM Global Services, 2003 Architecture Center of Excellence - Federal 41
  42. 42. Thank You Further information can be found at: • Patterns for e-business Web Site: http://www.ibm.com/developerworks/patterns • “Patterns for e-business – A Strategy for Reuse” Book Jonathan Adams, Srinivas Koushik, Guru Vasudeva, and George Galambos © IBM Global Services, 2003 Architecture Center of Excellence - Federal 42

×