convergence soa & bi presentation june 2010

37
Convergence Of SOA & BI Convergence Of SOA & BI Robert J. Abate, CBIP, CDMP Robert J. Abate, CBIP, CDMP Principal Practice Consultant 6/8/2010 1 Presented: May, 2010 Presented: May, 2010

Upload: robert-j-abate-cbip-cdmp

Post on 18-Jan-2017

194 views

Category:

Documents


0 download

TRANSCRIPT

Convergence Of SOA & BIConvergence Of SOA & BIRobert J. Abate, CBIP, CDMPRobert J. Abate, CBIP, CDMP

Principal Practice Consultant

6/8/2010 1

Presented: May, 2010Presented: May, 2010

AgendaAgenda

TopicTopic Duration Duration (minutes)(minutes)

Setting Up The Problem 20

Defining Information 15

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 22

Defining Information 15

Defining Services 15

Effective Governance 5

The Value Proposition Of 5

Questions & Answers 30

�� A Services Based Architecture [SBA] RequiresA Services Based Architecture [SBA] Requires� “Common Communications Mechanisms & Definitions”� (ESB or Middleware)

� Defined Integration architecture� Business Architecture or defined business rules (or chestration/choreography)� Information Architecture with defined Metadata and layers of abstractions

� Similar foundation to a Business Intelligence solut ion

Setting Up The ProblemSetting Up The ProblemAn IntroductionAn Introduction

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 33

� Similar foundation to a Business Intelligence solut ion�� Industry Now Being Dominated By SBA’sIndustry Now Being Dominated By SBA’s

� Gartner notes that in 2008, SBA’s Are “Mainstream”� Flexibility, Agility, Scalability & Reusability are all benefits of

�� This Presentation Will Review “The Convergence Of”This Presentation Will Review “The Convergence Of”� Definitions of Business Intelligence and SOA soluti ons� Why there is a convergence of these type of solutio ns� Key Features and Requirements� Best Practices And Trends

�� In the Gartner report: “Information & Application A rchitectures In the Gartner report: “Information & Application A rchitectures 2007,” they note convergence of layers2007,” they note convergence of layers� New architectures (SOA) have unprecedented info sha ring

� A single common vocabulary and methodology required

Setting Up The ProblemSetting Up The ProblemLayers Are ConvergingLayers Are Converging

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 44

Setting Up The ProblemSetting Up The ProblemTension Between IT & BusinessTension Between IT & Business

�� IT is perceived as not performing wellIT is perceived as not performing well� Inhibitor to corporate progress – IT systems cannot be

changed fast enough to meet market demands, seize opportunity or comply with a new requirement.

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 55

��Weak alignment between IT and business Weak alignment between IT and business strategystrategy� Marked by an intractable language barrier

� Not strategically aligned – IT does not know or foll ow corporate strategy.

�� IT is almost never the source of innovations.IT is almost never the source of innovations.

�� Harris Interactive recently polled 23,000 U.S. empl oyees Harris Interactive recently polled 23,000 U.S. empl oyees in key industries and functional areas and found th at:in key industries and functional areas and found th at:� Only 37% said they have a clear understanding of what

their organization is trying to achieve and why

� Only one in five was enthusiastic about their team and the

Setting Up The ProblemSetting Up The ProblemWhy Is Alignment ImportantWhy Is Alignment Important

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 66

� Only one in five was enthusiastic about their team and the organization’s / corporation’s goals

� Only one in five said they have a clear “line of sight” between their tasks and their team and organization ’s goals

� Only 15% felt that their organization fully enables them to execute key goals

� Only 20% fully trusted their organization or the data within it

If a football team had these If a football team had these players on the field:players on the field:

– Only 4 of the 11 players on the field would know which goal is theirs

– Only 2 of the 11 would care

Setting Up The ProblemSetting Up The ProblemAlignment Viewed Another WayAlignment Viewed Another Way

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 77

– Only 2 of the 11 would care

– Only 2 of the 11 would know what position they play and what they are supposed to do

– 9 players out of 11 would, in some way, be competing against their own team rather than the opponent

Book Excerpt: The 8th Habit, FORTUNE Magazine, November 29, 2004, page 162

�� The complexity of systems has caused IT to be react ive rather than The complexity of systems has caused IT to be react ive rather than proactive proactive –– “Heroic Approach To Integration With Cha os”“Heroic Approach To Integration With Chaos”� Silo’d solutions, db’s and applications with trappe d business rules

� Multiple sources of information and no single “trut h”

� No “Architectural Blueprints” to the enterprise…

Setting Up The ProblemSetting Up The ProblemEver Increasing ComplexityEver Increasing Complexity

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 88

Setting Up The ProblemSetting Up The ProblemComplexity BegetsComplexity Begets

�� So, the complexity of IT systems has caused…So, the complexity of IT systems has caused…

WEB /eCommerce

LicensingOLTP

SystemFinancialSystem

�Mix of batch and real time transfers

�For every added system, have ( N - 1 ) interfaces

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 99

ERP

eCommerceSystem

System System•[AP/AR/GL]

BusinessPlanningSystem

InventorySystem

VendorIntegration

DataWarehouse

( N - 1 ) interfaces�Multiple security

mechanisms�Multiple,

disparate copies of data

� Inconsistent semantics

�No single dictionary / metadata

Setting Up The ProblemSetting Up The ProblemComplexity BegetsComplexity Begets

�� Business Intelligence / Data Warehouse and SOA must have an Business Intelligence / Data Warehouse and SOA must have an “agreed upon” terminology (metadata, meta“agreed upon” terminology (metadata, meta--processes, models) processes, models) ––this is not a technology this is not a technology –– which is used across the business so work which is used across the business so work is accomplished effectively. is accomplished effectively. �� ArchitectedArchitected� Independent of

technology (.NET, J2EE, and so forth) WEB /

eCommerce

OLTPSystem Financial

System(s)

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 1010

J2EE, and so forth)

�Agreed upon terminology and processes

�Built on consistent semantics, taxonomy, classifications & rules

�A single security mechanism

�Defined events and processing aligned with business operations

ERP(s)

eCommerceSystem

System(s)[AP/AR/GL]

WMSWarehouseMngt. Sys.

InventoryPlanningSystem TMS

TransportMngt. Sys.

DataWarehouse

Agreed UponAgreed UponTerminologyTerminology

Business & InformationBusiness & InformationArchitecturesArchitectures

Business processOrganization structure

Corporate cultureUnderlying IT systems

CEOs and Boards Major inhibitors to strategic change

Business processOrganization structure

Corporate cultureUnderlying IT systems

CEOs and Boards

Business processOrganization structure

Corporate cultureUnderlying IT systems

CEOs and Boards Major inhibitors to strategic change

Setting Up The ProblemSetting Up The ProblemManagement Is Not Getting The Right InfoManagement Is Not Getting The Right Info

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 1111

0% 10% 20% 30% 40% 50%0% 10% 20% 30% 40% 50%0% 10% 20% 30% 40% 50%

64% of CIO’s answer ‘No’ to the question: “ Is management getting the right (secure)

access and integrated information for making smart business decisions?”

3. As designed by the Senior Analyst1. As proposed by the project sponsor 5. As installed at the user’s site

Setting Up The ProblemSetting Up The ProblemWhat Is The Business Problem AnywayWhat Is The Business Problem Anyway

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 1212

2. As defined by the requirements doc’s 4. As produced by the programmers 6. What The User Really Wanted!

“Analysts report that as many as 71% of software pro jects that fail do so because of poor requirements management, making it the single bigge st reason for project failure”

– CIO Magazine, November 15th, 2005

Dictates

Dictates

Supplem

ents

Dictates

DictatesBusiness /

SBU StrategyBusiness

Architecture

BusinessProjects &Programs

Implies

Con

trib

utes

& S

uppo

rts

Con

trib

utes

& S

uppo

rts

Con

trib

utes

& S

uppo

rts

There Is An “Implied” Relationship Between Business & Technology Building Blocks

Setting Up The ProblemSetting Up The ProblemWe Are Missing Key RelationshipsWe Are Missing Key Relationships

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 1313

Enables

Dictates

Enables

Dictates

Supplem

ents

Dictates

DictatesTechnology

Strategy

App. & Info.TechnologyArchitecture

TechnologyProjects &Programs

Implies

Con

trib

utes

& S

uppo

rts

Con

trib

utes

& S

uppo

rts

Con

trib

utes

& S

uppo

rts

Business Architecture is a comprehensive framework for the representation of the business processes, information, rules, and organizational designs that result directly from the business strategy. It provides a coherent graphical means for the capture, management, and communication of business knowledge and

needs to support business solutions in the form of actionable requirements.

IT Confined ByProject Budgets

And Define App/InfoArchitecture

True Relationship Between Business & Technology Bui lding Blocks

Setting Up The ProblemSetting Up The ProblemWe Are Missing Key RelationshipsWe Are Missing Key Relationships

Business Architecture

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 1414

Infrastructure Architecture

Information Architecture

Applications Architecture

�� InnovationInnovation� Defined as: “Process of making change to do somethi ng new”

� SBA’s support rapid change of applications “functio nality”

�� AgilityAgility

Setting Up The ProblemSetting Up The ProblemWhy Are Integrated Architectures (SOA/EIM) ValuableWhy Are Integrated Architectures (SOA/EIM) Valuable

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 1515

�� AgilityAgility� Agility means the capability of rapidly and cost ef ficiently

adapting to changes

� SBA’s built on easy to assemble and re-configure co mponents

�� ReuseReuse� Services architectures support very high re-use of components

� Governance / traceability are foundational pillars of SBA’s

© 2009 RCG Information Technology, Inc. [RCG IT] All rights reserved.

“ Business intelligence (BI) refers to skills, knowledge, technologies, applications, quality, risks, security issues and p ractices used to help a business to acquire a better understanding of market behavio r and commercial context.”

Wikipedia

Defining InformationDefining InformationWhat Is Business IntelligenceWhat Is Business Intelligence

•• Data = Documents, Pages, Files, ... Data = Documents, Pages, Files, ... •• Structured Data / Metadata = Data + Syntax Structured Data / Metadata = Data + Syntax •• Semantics = Meaning of Structured Data elements Semantics = Meaning of Structured Data elements •• Information = Structured Data + Semantics Information = Structured Data + Semantics •• Knowledge = Purposeful Combination of Information Knowledge = Purposeful Combination of Information

•• Data = Documents, Pages, Files, ... Data = Documents, Pages, Files, ... •• Structured Data / Metadata = Data + Syntax Structured Data / Metadata = Data + Syntax •• Semantics = Meaning of Structured Data elements Semantics = Meaning of Structured Data elements •• Information = Structured Data + Semantics Information = Structured Data + Semantics •• Knowledge = Purposeful Combination of Information Knowledge = Purposeful Combination of Information

Business Performance ManagementBusiness Performance ManagementOptions = “Benefits

Abate Wisdom Triangle

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 1616

Wisdom

Knowledge

Information

Data

Making coherent judgments and inferences from the Making coherent judgments and inferences from the knowledge gained by evaluating all the possible out comes.knowledge gained by evaluating all the possible out comes.

Making sense of these facts so that we can now deri veMaking sense of these facts so that we can now deri veconclusions from related and nonconclusions from related and non --related information.related information.

Placing these facts into the context of yourPlacing these facts into the context of yourBusiness model and operations processBusiness model and operations process

Structured & Unstructured raw elementsStructured & Unstructured raw elementsor images (structured vs. unstructured)or images (structured vs. unstructured)

Business Intelligence & D/W

Business Performance Management

Performance Reporting

Raw Data Reporting

Making coherent judgments and inferences from the Making coherent judgments and inferences from the knowledge gained by evaluating all the possible out comes.knowledge gained by evaluating all the possible out comes.

Making sense of these facts so that we can now deri veMaking sense of these facts so that we can now deri veconclusions from related and nonconclusions from related and non --related information.related information.

Placing these facts into the context of yourPlacing these facts into the context of yourBusiness model and operations processBusiness model and operations process

Structured & Unstructured raw elementsStructured & Unstructured raw elementsor images (structured vs. unstructured)or images (structured vs. unstructured)

Business Intelligence & D/W

Business Performance Management

Performance Reporting

Raw Data ReportingUnstructured

Data In Context = “Related”

Understanding Patterns = “Context & Function”

“Benefits Driven Usage”

Intelligence Presentation and Visualization

Competitive Intelligence

BusinessStrategy

Business Focus

Business Audience

Top Executives

Intelligence Analysts

BI Skills Community

Enterprise Dashboards

Intelligence Needs

Defining InformationDefining InformationWhat Is Business IntelligenceWhat Is Business Intelligence

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 1717

Data Analytics

Ad hoc Queries and Reports

Reporting

Data Analytics

Predictive Analytics

Heuristic Pattern Recognition

BI & Data Delivery Technologies Must Tie This All Together!

TransactionProcessing

OperationsAnalysis

OperationsPerformance

Operations Directors

Operations Supervisors

Operations Staff

Information Developers

Knowledge Workers

Power Users

Access to Needed Facts

Exceptions & Key Items

Performance Analysis

For SOA-enabled applications to satisfy this wide r ange of diverse needs and users, this requires a new class of services: Data Delivery Services

Strategic Components�� Business DriversBusiness Drivers� MDM needs, initiatives and priorities

�� Data ManagementData Management� Metadata and master data� Standardization and quality� Security, compliance, and governance

�� Information architectureInformation architecture

INFORMATION ARCHITECTURE

Data Rules

Data & Data Audit MetadataEnterprise Reporting

Integrated KPIs & Dashboards ETL / Data

Integration

Managed Data Environment

Defining InformationDefining InformationBI Requires A Managed Data EnvironmentBI Requires A Managed Data Environment

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 1818

�� Information architectureInformation architecture� Modeling and structuring data� ETL data integration and rules� OLAP and reporting management� Data delivery services (SOA-compliant)� Data technologies compatibility

�� Performance managementPerformance management� KPI relationships and metrics structure� Dashboard development and integration

�� Analytics managementAnalytics management� Enterprise reporting� Analytics in transaction processing� “Real-time” analytics� Business activity monitoring (BAM)

Data Rules

Data Quality,Profiling & Cleansing

Integration Hub

Enterprise Data Structures

Sync

Sync Sync Integrated Trx Data Store

Trx Processing

Recent Data, Normalized, Fine-grained, Unit-of-Work (UoW)

Processing

EDW & Data Marts

ReportingGranular,

Denormalized, Current / History

AnalyticsAggregates, Dimensional, Conformed

Master Data

CustomerValue, Control Data, ID X-ref

ProductValue, Control Data, ID X-ref

Orgn ChartValue, Control Data, ID X-ref

Enterprise Data Structures

Sync

Sync Sync Integrated Trx Data Store

Trx Processing

Recent Data, Normalized, Fine-grained, Unit-of-Work (UoW)

Processing

EDW & Data Marts

ReportingGranular,

Denormalized, Current / History

AnalyticsAggregates, Dimensional, Conformed

Master Data

CustomerValue, Control Data, ID X-ref

ProductValue, Control Data, ID X-ref

Orgn ChartValue, Control Data, ID X-ref

Data Delivery Svcs

A Managed Data Environment is more than ‘the single source of truth ’,

it is the business’s ‘information assurance and delivery mechanism ’

Defining InformationDefining InformationThe Value Of Data Changes With TimeThe Value Of Data Changes With Time

Valu

e Lo

stVa

lue

Lost

Value

Business EventBusiness Event

Capture Capture

THE TIME VALUE CURVE©:© Dr. Richard Hackathorn, Bolder Technology, Inc., 2 007. All Rights Reserved. Used with Permission.

Right-Time, NOT Real Time Right-Time, NOT Real Time

. . . because it cannot easily address these critical aspects of Business Intelligence

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 1919

Action Time

Valu

e Lo

st

Action Time

Valu

e Lo

st

Time

Action TakenTaken

Capture Latency

AnalysisLatency

Decision Latency

Data Ready For Analysis

Information Delivered

Capture Latency

AnalysisLatency

Decision Latency

Data Ready For Analysis

Information Delivered

SOA can connect these two points in time, but it cr eates a false sense that technology solves the problem . . .SOA can connect these two points in time, but it cr eates a false sense that technology solves the problem . . .

�� What is Master Data?What is Master Data?� Master data is the critical information that provid es context and integrity to

transactional data in the enterprise

� Some of the typical characteristics of Master Data that help understand it better are:� Master Data usually contains hierarchies that provi de ways to aggregate transactional

data, e.g., customers roll up to households, days r oll up to weeks/months/quarters etc.

Defining InformationDefining InformationMaster Data Management Requires Real Time Services…Master Data Management Requires Real Time Services…

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 2020

data, e.g., customers roll up to households, days r oll up to weeks/months/quarters etc.� Master Data typically changes less frequently than transactional data and share a “one-

to-many” relationship, e.g., one claim may have mul tiple payment transactions� Master Data is almost always cross-functional, e.g. , the list of customers is used by

Marketing, Sales, Finance etc.

Enterprise Data

Function-specific Information

Cross-functional Information

Transaction DataTransaction Data

Corporate Reference DataCorporate Reference Data

Master DataMaster DataApplication Control DataApplication Control Data

Transaction Data

Reference Data

�� Why Master Data Is ImportantWhy Master Data Is Important� Master data, or reference data, is information that is key to the operation of

business . . . . This key business information may include data about customers, products, employees, materials, suppliers, etc. whi ch often turns out to be non-transactional in nature.

� In this regard, master data can support transaction al processes and operations, but its use is certainly not limited to such (analy tics/reporting is another area

Defining InformationDefining InformationSOA Enables Master Data ManagementSOA Enables Master Data Management

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 2121

but its use is certainly not limited to such (analy tics/reporting is another area greatly dependent on an organization's master data) .

� Master data is often used by several functional gro ups and stored in different data systems across an organization and may or may not b e referenced centrally; therefore, the possibility exists for duplicate and /or inaccurate master data.

� Thus Master Data is that persistent, non-transactio nal data that defines a business entity for which there is, or should be, an agreed upon view across the organization.

�� The Consistency, Correctness, and Control That Mast er The Consistency, Correctness, and Control That Mast er Data Provides Enables SOA and the BusinessData Provides Enables SOA and the Business

Wikipedia

�� What Is A “Service”?What Is A “Service”?� A service is an application that operates on or del ivers a Unit Of Work

� Is Designed To Receive Requests From Any Source Mak ing No Assumptions As To The Functional Correctness (Syntactic Or Semantic) Of An Incoming Request.

� Within Each Request, Encompasses A Complete & Indep endent Unit Of Work (Business Or Technical)

Defining SOADefining SOAWhat Is A Service ?What Is A Service ?

�� What Is A “Service”?What Is A “Service”?� A service is an application that operates on or del ivers a Unit Of Work

� Is Designed To Receive Requests From Any Source Mak ing No Assumptions As To The Functional Correctness (Syntactic Or Semantic) Of An Incoming Request.

� Within Each Request, Encompasses A Complete & Indep endent Unit Of Work (Business Or Technical)

�� What Is A “Service”?What Is A “Service”?� A service is an application that operates on or del ivers a Unit Of Work

� Is Designed To Receive Requests From Any Source Mak ing No Assumptions As To The Functional Correctness (Syntactic Or Semantic) Of An Incoming Request.

� Within Each Request, Encompasses A Complete & Indep endent Unit Of Work (Business Or Technical)

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 2222

� May Stand On It’s Own Or Be Part Of A Larger Set Of Functions That Constitute A Larger Service; But It’s Scope Is Such That Each Re quest Leaves The System In A Long Term Steady State

� Is Designed For And Provides For A Network-Accessib le Interface

� Keep UOW’s Together That Change Together (High Cohe sion) & Build Separation Between Units That Change Independently (Low Coupli ng).

The means by which the needs of a service consumer are brought together with the capabilities of a service provider.

� May Stand On It’s Own Or Be Part Of A Larger Set Of Functions That Constitute A Larger Service; But It’s Scope Is Such That Each Re quest Leaves The System In A Long Term Steady State

� Is Designed For And Provides For A Network-Accessib le Interface

� Keep UOW’s Together That Change Together (High Cohe sion) & Build Separation Between Units That Change Independently (Low Coupli ng).

The means by which the needs of a service consumer are brought together with the capabilities of a service provider.

� May Stand On It’s Own Or Be Part Of A Larger Set Of Functions That Constitute A Larger Service; But It’s Scope Is Such That Each Re quest Leaves The System In A Long Term Steady State

� Is Designed For And Provides For A Network-Accessib le Interface

� Keep UOW’s Together That Change Together (High Cohe sion) & Build Separation Between Units That Change Independently (Low Coupli ng).

The means by which the needs of a service consumer are brought together with the capabilities of a service provider.

��What Is A “Unit Of Work” of “UOW”?What Is A “Unit Of Work” of “UOW”?� Group of data attributes (or elements) that provide s for a complete

business or technical transaction (function like up date address)

� Should conform to the rules of “ACID” (SOA & EDA)� Atomicity – Guarantee all the tasks of a transaction are perfor med

Defining SOADefining SOAWhat Is A Unit Of Work ?What Is A Unit Of Work ?

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 2323

� Atomicity – Guarantee all the tasks of a transaction are perfor med� Consistency – Ensures the database remains in a cons istent state� Isolation – Cannot see the data in an intermediate s tate� Durability – Guarantee the transaction will persist, and not be undone

Customer Address UOWAddress Line #1Address Line #2

City, State Zip Code

Product ID UOWProduct Full NameProduct Acronym

Product ID(Vendor ID)

Customer Address UOWAddress Line #1Address Line #2

City, State Zip Code

Product ID UOWProduct Full NameProduct Acronym

Product ID(Vendor ID)

�� Business ArchitectureBusiness Architecture� Defines requirements and needs in a top-down method ology

�� ModelModel--driven developmentdriven development� Foundation is reusable/iteratively developed integr ation approach

�� Managed Information EnvironmentManaged Information Environment� Information architecture, metadata and delivery ser vices defined

Defining SOADefining SOAWhat Are The Basic Components OfWhat Are The Basic Components Of

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 2424

� Information architecture, metadata and delivery ser vices defined

�� Process Integration (messaging component)Process Integration (messaging component)� Orchestration, choreography & event correlation (re al-time)

�� Governance and Security ArchitectureGovernance and Security Architecture� Architecture governance (Frameworks, Methods, Stand ards, etc.)� Development control (Reference Arch., SLA’s, etc.)� Security Architecture

�� Resources and Tools IntegrationResources and Tools Integration� Organization (Reuse planning, component management, etc.)

��A services based architecture can be built A services based architecture can be built minimally in one of four architectural paradigmsminimally in one of four architectural paradigms� Services Oriented Architecture [SOA]� Utilizes common metadata/processes with real-time s ervices

� Event Driven Architecture [EDA]

Defining SOADefining SOAArchitectural ParadigmsArchitectural Paradigms

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 2525

� Utilizes common metadata/processes with event-based services� Event “Sources” & “Sinks”

� Web Oriented Architecture� Does not use metadata� Handles complex events

� Web Services Architecture� Does not use metadata� Processing only� No event processing

ServicesServicesOrientedOrientedArchitectureArchitecture

Web Services Web Services ArchitectureArchitecture

Event Driven Event Driven ArchitectureArchitecture

Services Based Architectures

Venn Diagram Of Services Architectures

�� A services based architecture can be implemented A services based architecture can be implemented minimally using one of three approachesminimally using one of three approaches� Top-Down Approach� Referred to as “Business Process Decomposition”�Original, Model-Driven Development approach to buil ding SOA’s

� Bottom -Up Approach

Defining SOADefining SOAApproaches To Building…Approaches To Building…

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 2626

� Bottom -Up Approach� Referred to as “Legacy Wrapping Approach”� Creates “Wrappers” that create interfaces to Mainfr ames and ERP’s

� Inside-Out or “Darwinian” Approach� This method utilizes a “Information-Centric approac h”� Used commonly when implementing “Master Data Manage ment”�Originally popularized by Robert Abate & Dr. Peter Aiken

Always Developed Iteratively – Never “Big Bang”!

Gartner: “SOA Is Now Mainstream”

Defining SOADefining SOAIt Is The Future Of Development…It Is The Future Of Development…

Gartner: “SOA Is Now Mainstream”

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 2727

�� SOA is a process not a SOA is a process not a product or toolproduct or tool

�� “Culture Shift”“Culture Shift”

�� SOA makes change easier SOA makes change easier with rewith re--usable componentsusable components

�� Define business requirements in a Define business requirements in a manner that aligns IT and Businessmanner that aligns IT and Business

�� “Business Architecture” is graphical “Business Architecture” is graphical (pictures) and easy to understand(pictures) and easy to understand

�� Supports both application and Supports both application and information architecturesinformation architectures

Defining SOADefining SOAImplementing Iteratively With High Reuse Implementing Iteratively With High Reuse –– The MDD ParadigmThe MDD Paradigm

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 2828

information architecturesinformation architectures�� Process is vendor agnosticProcess is vendor agnostic�� A picture is worth a thousand wordsA picture is worth a thousand words�� Provide for checking consistency Provide for checking consistency

and completeness throughout and completeness throughout (Requirements Traceability)(Requirements Traceability)

�� Supports incorporation of quality Supports incorporation of quality control and governance processescontrol and governance processes

�� ModelModel--driven approach should use a driven approach should use a repositoryrepository--based toolbased tool

Des

ign

& B

uild

Req

uire

-m

ents

Test

ing

Requirements andAcceptance Criteria

Design Component and/or Use Case that

Satisfies each Requirement

Test Groups, Test CasesOf Each Design Component

Defining SOADefining SOAAbate SOA Conceptual PictorialAbate SOA Conceptual Pictorial

FSD

BA

IODS

INFRABS

Enterprise-Wide Architecture

ETL

Information

LEGACY

App 1

AA

AS

Applications

DS

OperationsBusiness

BS CS

IA

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 2929

OID

ADD

Function

Responsibility

Function

Responsibility

Entity from ADD

Entity from ADD

Function

Location

SOD

PH

YS

ICA

L

PortfolioPortfolioReviewReviewPrioritizationPrioritizationProcessProcessImprovementImprovement

STRATEGY

LOG

ICA

L

BS

BS

BS

ETL

App 3

App 4

App n

AS

AS

AS

AS

App 2

ETLDS

DS

DS

DS

CS

CS

CS

Reporting

Master Data

Analytics

Security (LDAP, …)

�� Governance is the Governance is the development and development and integration of a set of integration of a set of rules (policies, rules (policies, guidelines, and guidelines, and standards) for standards) for

MissionMission

ManagementManagement

GovernanceGovernance provides a link provides a link between technology and between technology and business.business.� That link is a common

language and understanding of shared business data.

� It should facilitate the development of business around that data.

Effective GovernanceEffective GovernanceGovernance & Stewardship DefinedGovernance & Stewardship Defined

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 3030

standards) for standards) for managing the managing the corporation’s assets corporation’s assets (i.e.: Data)(i.e.: Data)

�� Stewardship is the Stewardship is the execution of the execution of the policies and policies and procedures set forth procedures set forth by the Governance by the Governance Framework.Framework.

ManagementManagement

ExecutionExecution StewardshipStewardship provides the provides the mechanism to implement the mechanism to implement the policies and limitations imposed policies and limitations imposed by the Data Governance Plan or by the Data Governance Plan or management.management.� It should manage the

development and execution of business data and day to day exceptions around that data.

Effective GovernanceEffective GovernanceManaging Data UsageManaging Data Usage

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 3131

�� Data Governance isData Governance iswhat an organization doeswhat an organization doesthat yields:that yields:� The highest quality decisions made at the lowest co st.

� Increased efficiency in conducting/completing IT pr ojects for the business.

�� With SOA, Architecture & Governance are inseparableWith SOA, Architecture & Governance are inseparable�� Areas to consider wrapping with Governance / Qualit yAreas to consider wrapping with Governance / Qualit y� Business Processes – governing business processes ensures compliance,

control, consistency, and management of core proces ses used in the business� Architectures – governing architectures addresses the design ‘blue print’ that

binds business processes, applications and services , and data, together� Data – governing data addresses master data, metadata, dat a lifecycle, data

Effective GovernanceEffective GovernanceArchitecture & Governance Are InseparableArchitecture & Governance Are Inseparable

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 3232

� Data – governing data addresses master data, metadata, dat a lifecycle, data quality, and data access in applications, analytics , reporting, B2B, and self-service for customers, suppliers, and employees� Applications & Services – governing business processes for consistency

requires governing the applications and web- and SOA -services that support them� IT Portfolio – governing the IT portfolio addresses the combinati on of

applications and services, data, and architectures IT manages at the application and service level and the technology level to ensur e interconnectivity and interoperability� Security – governing security manages the risks associated wi th a world of

business interconnectivity and application interope rability� Service-level agreement [SLA] – governing SLA’s establishes and monitors the

performance expectations for the data center and IT responsiveness.

�� Build A Managed Information EnvironmentBuild A Managed Information Environment� Incrementally to align business strategies and goal s with applications and

systems (as business units and IT learn to work tog ether)� Implement through business & IT management policies and practices (Data

Governance, Data Quality) – expandable to the enterp rise!

�� Focus On Business Context And Develop A True Focus On Business Context And Develop A True

The Value PropositionThe Value PropositionArchitect A Solution…Architect A Solution…

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 3333

�� Focus On Business Context And Develop A True Focus On Business Context And Develop A True Integrated Information / Application ArchitectureIntegrated Information / Application Architecture� Provide for architectural alignment with business a rchitecture� Separate data from applications architecturally

�� Foster A New Business Foster A New Business –– IT RelationshipIT Relationship� Change focus from managing resources and tasks to m anaging assets� Change IT focus from “tool jockeys” to “trusted adv isor architects” similar to

an external IT services provider adding business en ablement

�� Manage technology limitations and incompatibilitiesManage technology limitations and incompatibilities� Build integration “bridges” not “silo’s”

�� SOA provides agility and that means SOA provides agility and that means competitive advantage…competitive advantage…

�� SOA has high ROISOA has high ROI�� With Business Intelligence and Data With Business Intelligence and Data

Warehousing the business improves Warehousing the business improves the bottom line and high ROI’sthe bottom line and high ROI’s

SOASOA

The Value PropositionThe Value PropositionReturn On InvestmentReturn On Investment

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 3434

the bottom line and high ROI’sthe bottom line and high ROI’s

Source: IDC Business Value Report: “Reducing Operations Cost & Improving Customer Experience … SOA” , August 2008, Page 1

Business Intelligence & Data WarehousingBusiness Intelligence & Data Warehousing.. should expect to gain approximately $7.15 millio n in

cumulative benefits over five years. Savings come f rom a combination of labor productivity savings, cost avo idance,

software cost savings / avoidance, and hardware cos t savings / avoidance. The project is expected to generate $3 .3 million in

net benefits over five years, achieving an overall ROI of 172 percent and an internal rate of return of 52 percen t… investment is expected to pay for itself in 19 mont hs.

Source: TDWI What Works Report: ”Dell Consolidates European Support System to Achieve 172 Percent ROI in Five Years” , Volume 20, November 2005

The Value PropositionThe Value PropositionIt’s All About Change…It’s All About Change…

Portfo

lio o

f pro

jects

StrategyStrategyProcess FlowProcess FlowFunctionFunctionTimeTimeLocationLocationDataDataOrganizationOrganization

WHYWHYHOWHOWWHENWHENWHEREWHEREWHATWHATWHOWHO

Who

Wha

t

Whe

re

Whe

n

How

Why

DimensionsImplementing Change MeansRunning A Sequential Set Of

Projects (Portfolio) That, OverTime, Implement The Solution

Implementing Change MeansRunning A Sequential Set Of

Projects (Portfolio) That, OverTime, Implement The Solution

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 3535© 2008 RCG IT. All rights reserved. Proprietary and Confidential.

35

Information

Application

Infrastructure

Business

Portfo

lio o

f pro

jects

Arc

hite

ctur

al L

ayer

s

Questions & AnswersQuestions & Answers

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 3636

Contact InformationContact Information

Robert Abate, CBIP, CDMPRobert Abate, CBIP, CDMP

6/8/20106/8/2010 DAMA NE: “Convergence Of SOA & BI” May, 2010DAMA NE: “Convergence Of SOA & BI” May, 2010 3737

Managing Principal ConsultantManaging Principal Consultant(201) 745 (201) 745 –– [email protected]@emc.com