Adaptive Enterprise Architecture - IBM · Defining Enterprise Architecture & Solution Architectures Guru Vasudeva ... Agenda 9What are Patterns? 9 ... message format 1:N

Architecture Center of Excellence - Federal IBM Global Services© IBM Global Services, 2003

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

Guru VasudevaArchitecture Center of Excellence - FederalIBM Global Services

e-mail: [email protected]: 301-803-3181

Patterns for e-business web site:http://www.ibm.com/developerworks/patterns

mailto:[email protected]

http://www.ibm.com/developerworks/patterns


Architecture Center of Excellence - Federal 2© IBM Global Services, 2003

Agenda

What are Patterns?

IBM Patterns for e-business Overview

Leveraging architectural patterns in Solution Architecture definition

Applying architectural patterns at Enterprise Architecture level


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


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 riskIncreasing qualityImproving 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


There are four main categories of "patterns" in Software Engineering

Reference architecturesIndustry-related:- Insurance- Banking

Technical:- ESS Reference Arch.

Architectural PatternsBusiness Application Focused- Patterns for e-business

Analysis PatternsPartyOrganizationAccount

Abstract FactorProxyFacade

Design Patterns

Abstract Technology Focused- Layers- Pipes & Filters

A reference architecture is often composed of multiple architectural patterns. Similarly, an architectural pattern may leverage multiple design patterns and analysis patterns.


Agenda

What are Patterns?





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” BookJonathan Adams, Srinivas Koushik, Guru Vasudeva, and George Galambos

Book Web site : http://www.iirpubs.com/ibmpress/5206.cfm

http://www.iirpubs.com/ibmpress/5206.cfm


Patterns for e-business: Business Patterns

Business patterns identify the most commonly observed interactions betweenUsers, Businesses, and Data.

Self Service (a.k.a. User to Business)

Users accessing transactions on a 24x7

basis

Collaboration(a.k.a. User to User)

Users working with one another to share data and information

Information Aggregation(a.k.a. User to Data)

Data from multiple sources aggregated

and presented across multiple channels

Extended Enterprise(a.k.a. Business to Business)

Integrating data and processes across

enterprise boundaries


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" betweenBusiness patterns.

Acc

ess

Inte

grat

ion

Provide seamless and consistent access to business functions.

Typical functions provided include Single-signon, Personalization, Transcoding etc.

App

licat

ion

Inte

grat

ion

Connect, Interface or Integrate databases and systems

Typical integration can be based on Function, Type of Integration, Mode of Integration and by Topology


Patterns for e-business: Cardinality between different types of Patterns

Business & Integration Patterns

Business orIntegration

pattern

Runtime pattern

Runtime pattern

Runtime pattern

Runtime pattern

Application pattern

Application pattern

Cardinality between different types of Patterns

App

licat

ion

Inte

grat

ion

Self Service (a.k.a. User to Business)

Information Aggregation(a.k.a. User to Data)

Collaboration(a.k.a. User to User)

Extended Enterprise(a.k.a. Business to Business)

Acc

ess

Inte

grat

ion


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


Legend used for expressing Application Patterns

Read only dataApplication node containing new or modified components

Transient data• Work in progress• Cached committed• StagedApplication node

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 process are well-defined

Meta Data•Templates


Application Patterns for Self-Service

2.Pres.

Pres.synch App.

App. App.synch/asynch

1. Pres.synch

App.

Stand Alone Single Channel

Directly Integrated Single Channel

6.

5. synchRouter

synchPres2

Pres1

App 2

App1

Decomp

Pres2

Pres1 synch synch/asynch

App 2

App1

Decomposition

Router

App 2

App17.

CRM LOB

synch/asynch

synch/asynch

Pres2

Pres1 Agent

WIP

Agent


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


Application Patterns for Information Aggregation

Categorized Index

Read-write

Crawl & DiscoverTier

Write

Retrieve & Parse Documents

Read-Only 1

Crawl Space

Read-Only 2

SelectionCriteria

Meta Data

Categorized Index with Summary

Read-write

Crawl, Discover,& SummarizationTier

Write

Retrieve & Parse Documents

Read-Only 1

Crawl Space

Read-Only 2

SelectionCriteria

Meta Data

Population – Summarization

Population – Crawl and Discover

Read-write

PopulationApplicationTier

Read-Write

Meta Data

Read

Write

Population – Single Step

Population – Multiple Step


Application Patterns for Extended Enterprise

Backend Application 2

Read-write

Translator Tier


Read-write

Work in Progress

Partner Tier

Partner A Partner B

Asynchronous,Mutually agreedmessage format

1:N

Private and Public processes

Document Exchange

Exposed Application 2

Read-write

Exposed Application 1

Read-write

Partner Tier

Partner A Partner B

Asynchronous

1:N


Exposed Application


Read-write

Exposed Business Services Tier Backend

Application 1

Read-write

Read Only

Partner Tier

Partner A Partner B

Asynchronous,Mutually agreedmessage format

1:N


N:1

Synchronous,Asynchronous

Exposed Business Services

Managed Public Process


Read-write


Read-write

Read Only

Partner Tier

Partner APartner B

Asynchronous,Server-specified ormutually agreedmessage format

N:1


Public Process Rules Tier

1:N

Work in Progress

Private processes Public processes


Application Patterns for Collaboration

CollaborationClient

LocalSettings

CollaborationClient

Synchronous

LocalSettings

Point-to-Point Collaboration

SharedData

CollaborationClient

CollaborationServer

CollaborationClient

synchronous

asynchronous

LocalData

Store and Retrieve Collaboration

SharedData

CollaborationServer

CollaborationClient

synchronous

DirectoryLocalAddress

Book

SharedApplication

CollaborationClient

LocalAddress

Book

SharedApplication

synchronous

synchronous

Directed Collaboration

SharedSharedApplicationApplication

Synch

Asynch

DirectoryDirectory SharedSharedDataData

WorkflowWorkflowRulesRules

CollaborationCollaborationClientClientCollaborationCollaboration

ClientClient Synch

Asynch

CollaborationCollaborationServer

WorkflowWorkflowApplicationServer Application

LocalLocalAddress BookAddress Book

WIPWIPDataData

Managed Collaboration


Application Patterns for Access Integration

SynchronousPervasiveDevice Access

Tier

Application 1

Application 2

PervasiveDevice Asynchronous

Synchronous

Read-Write

Meta-Data

Pervasive Device Access

ClientTier

Application1

Application2

Single Sign-OnTier

synchronoussynchronous

Read-Write Read-Write

Read-Write

Web Single Sign-On

A p p lic a t io n 1

A p p lic a t io n 2

P e rs o n a liz a tio nR u le s

C lie n tT ie r

Personalized Delivery

EnterpriseApplication

ClientTier

SecurityIntegration

Application 1

Application 2

Single Sign-On & Role-Based

Access


ClientTier

SecurityIntegration

Application 1

Application 2


Access


ClientTier

SecurityIntegration

Application 1

Application 2


Access

Extended Single Sign-On


Application Patterns for Application Integration (Process Focused)

BrokerDirect Connection

Work in Progress

Broker Rules Tier

Read-write

ApplicationTier

Read-write

Read-write

ApplicationTier

ApplicationTier

1 : NApplication

TierSynchronous Application

TierAsynchronous

Managed Process

Work in Progress

BPM Rules Tier

Read-write

ApplicationTier

Read-write

Read-write

ApplicationTier

ApplicationTier


Application Patterns for Application Integration (Data Focused)

App 2App 1

population TransformRules

App 3

Propagation Replication

Operational Data Store Federated Repository

App 2App 1

population

feedback

App 2App 1

population

App N

...TransformRules

App 2App 1

App N

...UnifiedQuery


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 & IT Drivers

Service Level Characteristics


Self-Service: Application Patterns, Runtime Patterns & Product Mapping

Stand Alone Web-Up

7 Application Patterns for Self-Service

synchsynchPres2

Pres1

App 2

App1

Self-Service::Router Application Pattern

Self Service

Directly Integrated Web-Up

As-is Host

Customized Presentation

Router

Decomposition

Agent

Select based onBusiness & IT Drivers

Router

Select based onService Level Characteristics

Self-Service::Router Product Mapping & Redbook

Self-Service::Router Runtime Pattern

Select based onproductdecisions


Extended Enterprise: Application Patterns & Runtime Patterns

ExtendedEnterprise

Document Exchange

Exposed Application

Exposed Business Services

Managed Public Process

5 Application Patterns for Extended Enterprise

Select based onBusiness & IT Drivers

Managed Public Process Application Pattern

Select based on Service Level Characteristics


Read-write


Read-write

Read Only

Partner Tier

Partner APartner B


N:1



1:N

Work in Progress


Managed Public Process Runtime Pattern


Patterns for e-business: Composite Patterns

Does a Composite Pattern already exist ?



Patterns for e-business: Composite Patterns

Composite Pattern for PortalsComposite Pattern for Electronic Commerce Solutions

Self Service

Acc

ess

Inte

grat

ion

App

licat

ion

Inte

grat

ion

Collaboration

Extended Enterprise

Information Aggregation

Self Service

Acc

ess

Inte

grat

ion

App

licat

ion

Inte

grat

ion

Collaboration

Extended Enterprise


App

licat

ioIn

tegr

atio

nComposite Pattern for Enterprise Intranet Portal

Self Service

Acc

ess

Inte

grat

ion

Collaboration


Composite Pattern for a Collaboration ASP

Acc

ess

Inte

grat

ion

Collaboration

Blue – Mandatory Business Patterns

Red – Optional Business Patterns - Variations

n


Agenda

What are Patterns?





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


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.


e-Gov GeoSpatial Initiative – Step 1 & 2 Develop SOD

Various National Libraries

Sensors / Data Providers

GeoSpatial Information Users from Local & StateGovt

Search

Download &Exploit

Virtual Knowledge Store

(Federation)

MetadataAbout available

Information(ODS)

National TechnicalMeans

CommercialSources

Request for New Data

Supply Chain Management

Data ProviderSpecific Tasking


e-Gov GeoSpatial Initiative – Step 3 Identify Business Patterns


Search

Download &Exploit


Sensors / Data ProvidersVarious National Libraries

CommercialSources




Information(ODS)


(Federation)


Extended Enterprise

Extended Enterprise Information AggregationSelf-Service

Self-Service


e-Gov GeoSpatial Initiative – Step 4 Identify Integration Patterns


Search

Download &Exploit



CommercialSources




Information(ODS)


(Federation)


Extended Enterprise

Extended Enterprise Information AggregationSelf-Service

Self-Service

Access Integration

ApplicationIntegration


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


Search

Download &Exploit



CommercialSources




Information(ODS)


(Federation)


Extended Enterprise ::Managed Public Process

Extended Enterprise :: Managed Public Process

Information Aggregation::Multi-Step Population

Self-Service ::Agent

Self-Service ::Router

Access Integration::Single-Sign On & Personalized Delivery

ApplicationIntegration::Federated Repository


e-Gov GeoSpatial Initiative –Step 8 & 9 Integrate Packages and develop Technical Architecture

Extended Enterprise::Managed Public Process


Read-write


Read-write

Read Only

Partner Tier

Partner APartner B


N:1



1:N

Work in Progress


Identify runtime patterns for the following selected application patterns and combine them into an integrated architecture

Access Integration:: Web Single Sign-On

ClientTier

Application1

Application2

Single Sign-OnTier

synchronoussynchronous

Read-Write

Read-Write Read-Write

Access Integration::Personalized DeliveryApp 2

App17.

CRM LOB

synch/asynch

synch/asynch

Pres2

Pres1 Agent

WIP

Self-Service::Agent

Application1

Application2

PersonalizationRules

ClientTier

Application Integration::Federated Repository

App 2App 1

App N

...UnifiedQuery


Agenda

What are Patterns?





Enterprise Architecture

Business Reference Model (BRM)• Lines of Business• Agencies, Customers, Partners

Service Component Reference Model (SRM)• Service Layers, Service Types• Components, Access and Delivery Channels

Technical Reference Model (TRM)• Service Component Interfaces, Interoperability• Technologies, Recommendations

Data Reference Model (DRM)• Business-focused data standardization • Cross-Agency Information exchanges

Business-Driven Approach

Performance Reference Model (PRM)• Government-wide Performance Measures & Outcomes• Line of Business-Specific Performance Measures & Outcomes

Patterns for e-business assetsare useful for the application & technology architecture

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.



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


Insurance Company Example: Application Function Model

Disability LOB Engines

Life LOB Engines

$ $ $

Customers

$ $ $

CSRs

$ $ $

Agents

$ $ $

OtherEmployees

Quotes

Policy Inquiry

Billing Inquiry

Claims Inquiry

Electronic Bill Payment

Claim Submission

Application Submission

P&C LOB Engines

Rating

Billing

ClaimsProcessing

Underwriting

Policy Processing

Actuarial

Customer Facing Functions

Operational Data Stores

IntegratedCustomer Info

IntegratedProduct Info

Corporate Functions (Back Office)

Accounting Financials

Actuarial Law & Compliance

HR Management

Analysis

Enterprise Data Warehouse

Decision Support Systems

Direct Marketing

Contact Management

CommissionManagement

Customer Acquisition

Agent Productivity Tools

Personal Profile

BenefitsManagement

401kManagement

Employee Self-Service

Insurance eMarketplaces


Insurance Company Example: Identify Business Patterns


Life LOB Engines

$ $ $

Customers

$ $ $

CSRs

$ $ $

Agents

$ $ $

OtherEmployees

Quotes

Policy Inquiry

Billing Inquiry

Claims Inquiry


Claim Submission


P&C LOB Engines

Rating

Billing

ClaimsProcessing

Underwriting

Policy Processing

Actuarial








HR Management

Analysis



Direct Marketing

Contact Management




Personal Profile

BenefitsManagement

401kManagement



Self-Service

Self-Service

Extended Enterprise

Info

rmat

ion

Agg

rega

tion


Insurance Company Example: Identify Integration Patterns


Life LOB Engines$ $ $

Customers

$ $ $

CSRs

$ $ $

Agents

$ $ $

OtherEmployees

Quotes

Policy Inquiry

Billing Inquiry

Claims Inquiry


Claim Submission


P&C LOB Engines

Rating

Billing

ClaimsProcessing

Underwriting

Policy Processing

Actuarial








HR Management

Analysis



Direct Marketing

Contact Management




Personal Profile

BenefitsManagement

401kManagement



Acc

ess

Inte

grat

ion

App

licat

ion

Inte

grat

ion

Self-Service

Self-Service

Extended Enterprise

Info

rmat

ion

Agg

rega

tion


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: Also defines the technology adoption life cycle

Current Tactical Strategic

RetirementList

Mature Technologies& Standards

ContainmentList

Emerging Technologies

Current 2 Years 5 Years

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


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.


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” BookJonathan Adams, Srinivas Koushik, Guru Vasudeva, and George Galambos
