Upload
dinh
View
38
Download
1
Tags:
Embed Size (px)
DESCRIPTION
Global EAI Summit 2004. TBI and TOGAF Reconciliation Terence Blevins, VP and CIO 10:10 am / Monday May 24 th DC Coleman Room. What Does Reconciliation Mean?. Reconciliation A reconciling or being reconciled Reconcile To bring together again in love or friendship - PowerPoint PPT Presentation
Citation preview
TBI and TOGAF Reconciliation
Terence Blevins, VP and CIO
10:10 am/Monday May 24th
DC Coleman Room
Global EAI Summit 2004Global EAI Summit 2004
What Does What Does ReconciliationReconciliation Mean?Mean?
• Reconciliation– A reconciling or being reconciled
• Reconcile1. To bring together again in love or friendship2. To induce to accept something disagreeable3. To reach a compromise agreement about4. To make or show to be consistent
• We’ll focus on 4 today – we think that TOGAF and TBI are consistent
PositionPosition
• TBI and TOGAF ADM are both great candidates for a Global Integration Framework
• Why TOGAF ADM– Any large effort requires enterprise architecture– Doing enterprise architecture requires an architecture
development method– An enterprise architecture method will include consideration of
integration given the appropriate situation – in most cases– An open architecture method is less likely to create new
integration challenges• Why TBI
– Any large project requires integration implementation plans– TBI is a proven method for dealing with integration details
• What can be done downstream… harden the points of interaction between TOGAF ADM and TBI to ensure interoperability
A Definition of Enterprise A Definition of Enterprise ArchitectureArchitecture
• The structure of components, their interrelationships, and the principles and guidelines governing their design and evolution over time
• Enterprise architecture– Covers the components in an enterprise
• organizations, processes, humans, data, applications, technology etc.
• Enterprise means enterprise-wide, not everything in the enterprise … An enterprise architecture effort must address a specific problem, not all problems at once!
The Role of ArchitectureThe Role of Architecture
• “Architecture is fast becoming one of the main instruments for improving Business IT Alignment.”
• “It is time to broaden our view and build systems that last and that keep delivering value to the business. Business and IT Architecture play a pivotal role in achieving this goal..“
Raymond Slot M.Sc, MBA, Principal Consultant and Enterprise Architect for Cap Gemini Ernst & Young
• Align Information Technology to Business
• Increase accountability to improve cost performance
• Drive accountability of spending
• Ensure network availability • Ensure security• Drive standardization
What direction is appropriate
How do we keep
alignment
How do we impact what
is being deployed
How do we ensure
information security
What process are in most
need of support
How do we pick the right solutions and
ensure support for
stds
How do we incorporate
a new system
Understand where change
is needed
How do we ensure that
the technical components
are fit
Create Alignment
Pressures on IT …Pressures on IT …
Other Pressures …Other Pressures …
• Effective business process to reconcile and adequately govern
• Short term spending• Short product life cycles• Rapid technological
change• Sub-optimal spending• Dealing with “hidden”
costs• Sub-optimal vendor
management
What direction is appropriate
How do we keep
alignment
How do we impact what
is being deployed
How do we ensure
information security
What process are in most
need of support
How do we pick the right solutions and
ensure support for
stds
How do we incorporate
a new system
Understand where change
is needed
How do we ensure that
the technical components
are fit
Create Alignment
And the Impact?And the Impact?
• Proliferation of point solutions
• High costs of integration• Not leveraging standards
–Few discount deals–Higher support costs–Less responsive support
• High costs and long lead times to deliver security
• Higher risk of security• Disconnected decisions• Lack of effectiveness
What direction is appropriate
How do we keep
alignment
How do we impact what
is being deployed
How do we ensure
information security
What process are in most
need of support
How do we pick the right solutions and
ensure support for
stds
How do we incorporate
a new system
Understand where change
is needed
How do we ensure that
the technical components
are fit
Create Alignment
AArchitecture
VisionH Architecture
Change Management
G Implementation
Governance
CInformation
System Architectures
Requirements
BBusiness
Architecture
EOpportunitiesand Solutions
F MigrationPlanning
Prelim: Framework and
Principles
DTechnology Architecture
TOGAF 8 ADMTOGAF 8 ADM
• Designed to address key issues!– Lowering costs– Control costs– Delivering new value– Better operational
efficiency of business– Better understand impact
of change– Holistic requirements
management– Lower risk– Faster decisions
• The journey provides benefits at each step!
http://www.opengroup.org/architecture/togaf8/index8.htmhttp://www.opengroup.org/architecture/togaf8/index8.htm
TBI Deliverables MapTBI Deliverables Map
Repository Repository Repository RepositoryCTQ Signoff
FDR Rpt FDR Rpt FDR Rpt FDR RptLessonsLearned
BusinessProcess Analysis
Tech ReqDocument
Software QA Plan
Req WTreport
System Test Cases
TDBLogicalDesign
Logical
Design WTReport
SimulationDocument
Integration
Test Cases
Architect.Document
Integration
WT Report
Unit TestResults
SystemTest Result
IntegrationTestResults
Integration
Design
CodeReviews
ErrorHandlingGuide
Unit TestCases
SourceCode
DEFINE
Bu
sin
es
s
An
aly
st
Qu
ali
ty
Ma
na
ge
rG
ov
ern
an
ce
DESIGN
Arc
hit
ec
t /
De
sig
ne
r
BUILD
De
ve
lop
er
DEPLOY
TOGAF ADM Deliverables TOGAF ADM Deliverables MapMap
Prel Phase
BD
BD
FWD
AP
AP
EFW
IGS
PD
RFC
SD
TD
Phase A Phase B Phase C Phase D Phase E Phase F Phase G Phase H Reqs Mgmt
I IIIIIIIII
BD:BusinessData
EFW:ExternalFrameworks
IGS:IT GovernStrategy
PD:ProductDefinitions
RFC:Req forChanges
SD:StandardsDevs
TD:TechDevs
AP:Arch Principles
BD:BusinessData
FWD:FrameworkDefinition
AP:Arch Principles
O O O O O O O O O O
RFAW
FRAW:Req for Arch Work
BS:BusinessScenario
BA:BusinessArchitecture
SOW:StatementOf Work
SOW
BS
BA1
AP
RFAW
EC
EC:EnterpriseContinuum
BD BD
SOW
BA2
AP
RFAW
EC
BS
BA2
DP
DP:DataPrinciples
TTA:TargetTech Arch
IA:ImpactAnalysis
TISA
IA
RFAW
EC
SOW
BS
TP
TP:TechnicalPrinciples
ABL:ApplicationBaseline
DBL:DataBaseline
TISA:TargetIS Architecture
TTA
TP
BA2
TISA
IA
BA2
TISA
RFAW
EC
SOW
RFAW
SOW
IA
TTA
AC
RFAW
EC
SOW
AC:ArchitectureContract
BD
RFAW
IA
AP
BS
BA2
RFC
SRS:StructuredReq Statement
SRS
External Input
Internal Input
Output
http://www.opengroup.org/architecture/togaf8/index8.htmhttp://www.opengroup.org/architecture/togaf8/index8.htm
Intersections at…Intersections at…
Repository Repository Repository RepositoryCTQ Signoff
FDR Rpt FDR Rpt FDR Rpt FDR RptLessonsLearned
BusinessProcess Analysis
Tech ReqDocument
Software QA Plan
Req WTreport
System Test Cases
TDBLogicalDesign
Logical
Design WTReport
SimulationDocument
Integration
Test Cases
Architect.Document
Integration
WT Report
Unit TestResults
SystemTest Result
IntegrationTestResults
Integration
Design
CodeReviews
ErrorHandlingGuide
Unit TestCases
SourceCode
DEFINE
Bu
sin
es
s
An
aly
st
Qu
ali
ty
Ma
na
ge
rG
ov
ern
an
ce
DESIGN
Arc
hit
ec
t /
De
sig
ne
r
BUILD
De
ve
lop
er
DEPLOY
TOGAF ADM Feeds to TBITOGAF ADM Feeds to TBI
Prel Phase
BD
BD
FWD
AP
AP
EFW
IGS
PD
RFC
SD
TD
Phase A Phase B Phase C Phase D Phase E Phase F Phase G Phase H Reqs Mgmt
I IIIIIIIII
BD:BusinessData
EFW:ExternalFrameworks
IGS:IT GovernStrategy
PD:ProductDefinitions
RFC:Req forChanges
SD:StandardsDevs
TD:TechDevs
AP:Arch Principles
BD:BusinessData
FWD:FrameworkDefinition
AP:Arch Principles
O O O O O O O O O O
RFAW
FRAW:Req for Arch Work
BS:BusinessScenario
BA:BusinessArchitecture
SOW:StatementOf Work
SOW
BS
BA1
AP
RFAW
EC
EC:EnterpriseContinuum
BD BD
SOW
BA2
AP
RFAW
EC
BS
BA2
DP
DP:DataPrinciples
TTA:TargetTech Arch
IA:ImpactAnalysis
TISA
IA
RFAW
EC
SOW
BS
TP
TP:TechnicalPrinciples
ABL:ApplicationBaseline
DBL:DataBaseline
TISA:TargetIS Architecture
TTA
TP
BA2
TISA
IA
BA2
TISA
RFAW
EC
SOW
RFAW
SOW
IA
TTA
AC
RFAW
EC
SOW
AC:ArchitectureContract
BD
RFAW
IA
AP
BS
BA2
RFC
SRS:StructuredReq Statement
SRS
External Input
Internal Input
Output
AArchitecture
VisionH Architecture
Change Management
G Implementation
Governance
CInformation
System Architectures
Requirements
BBusiness
Architecture
EOpportunitiesand Solutions
F MigrationPlanning
Prelim: Framework and
Principles
DTechnology Architecture
SummarySummary
• TBI and TOGAF ADM are both great for GIF
• Any large effort requires enterprise architecture and doing so requires an open ADM
• Enterprise architecture method includes consideration of integration
• An open architecture method is less likely to create new integration challenges
• Any large project requires integration implementation plans
• TBI is a proven method for dealing with integration details
• We can harden the points of interaction between TOGAF ADM and TBI to ensure interoperability for GIF
• Leverage will get us all to the top!
http://www.opengroup.org/architecture/togaf8/index8.htmhttp://www.opengroup.org/architecture/togaf8/index8.htm
Contact DetailsContact Details
Terence BlevinsVP and CIO
Mobile +1 650 888 6950
44 Montgomery StreetSuite 960
San Francisco, CA94104 USA
Tel +1 415 374 8280 ext. 231Fax 413-683-4199
www.opengroup.org
TOGAF 8 represents an industry consensus framework and method for Enterprise Architecture that is available for use internally by any organization around the world - members and non-members of The Open Group alike - under a free, perpetual license.
http://www.opengroup.org/architecture/togaf8/index8.htm
TOGAF 8 represents an industry consensus framework and method for Enterprise Architecture that is available for use internally by any organization around the world - members and non-members of The Open Group alike - under a free, perpetual license.
http://www.opengroup.org/architecture/togaf8/index8.htm
BackupsBackups
Presentation OutlinePresentation Outline
• Background • Why Enterprise Architecture is Important• TOGAF and TOGAF History• TOGAF and TBI• Summary
Integration Is a Big IssueIntegration Is a Big Issue
• Gartner Dataquest forecasts Worldwide End-User IT Spending will grow – from $2.7 US trillion trillion in 2001 – to greater than $3.0 US trilliontrillion in 2002 and– reach $3.4 US trilliontrillion in 2003
• The worldwide integration services market is expected to see a 25% compounded annual growth rate between 2001 and 2005 to $116.5 US billion,billion, according to IDC
• CIO magazine survey says companies spend over 35% on integrating systems and processes
Presentation OutlinePresentation Outline
• Background • Why Enterprise Architecture is Important• TOGAF and TOGAF History• TOGAF and TBI• Summary
CIOs Have Issues in CIOs Have Issues in CommonCommon
• In general there is a trend –Demands on IT increasing–IT budgets are decreasing or flat
• CIOs must do more for less, so
–Look for leverage• Outsourcing• Off shore development• Open source• Collaborative
development• Reusable building
blocks…
Ever widening gap!
IT demand
IT budget- run rates are declining!
Presentation OutlinePresentation Outline
• Background • Why Enterprise Architecture is Important• TOGAF and TOGAF History• TOGAF and TBI• Summary
TOGAF 8 ScopeTOGAF 8 Scope
• TOGAF covers the development of four related types of architecture:
– Business architecture– Data or information architecture– Application architecture– Technology architectureTOGAF 7 “Technical Edition”
TOGAF 8“Enterprise Edition”
TOGAF 7 “Technical Edition”
TOGAF 8 – Enterprise TOGAF 8 – Enterprise EditionEdition
Enterprise Continuum
Resource Base
Architecture Development Method
Target Enterprise Architectures
Enterprise ADMEnterprise ADM
• An iterative method• Each iteration = new
decisions:– Enterprise coverage– Level of detail– Time period– Architecture asset re-use
• Decisions based on:– Competence / resource
availability– Value accruing to the
enterprise.
AArchitecture
VisionH Architecture
Change Management
G Implementation
Governance
CInformation
System Architectures
Requirements
BBusiness
Architecture
EOpportunitiesand Solutions
F MigrationPlanning
Prelim: Framework and
Principles
DTechnology Architecture
The Enterprise ContinuumThe Enterprise Continuum
FoundationArchitectures
Common SystemsArchitectures
Industry Architectures
Organisation Architectures
SystemsSolutions
IndustrySolutions
OrganisationSolutions
Products &Services
Solutions Continuum
Technology Architecture Continuum
Guides &Supports
Guides &Supports
Guides &Supports
Guides &Supports
Resource BaseResource Base
• Architecture Compliance Reviews
• Architecture Principles• Architecture Views• Architecture Tool evaluation
criteria• Business Scenarios• Architecture Governance• Case Studies• Comparisons with other
Frameworks• Mapping to Zachman
Framework
• A customer initiative• A framework, not an architecture
– A framework for developing architectures to meet different business needs
– Not a “one-size-fits-all” architecture
• Originally based on Technical Architectural Framework for Information Management (TAFIM) from US Department of Defense
TOGAF Origins TOGAF Origins
TOGAF DevelopmentTOGAF Development
• 1994: Requirement
• 1995: TOGAF Version 1
• 1996: TOGAF Version 2
• 1997: TOGAF Version 3
• 1998: TOGAF Version 4
• 1999: TOGAF Version 5
• 2000: TOGAF Version 6
• 2001: TOGAF Version 7
• 2002: TOGAF Version 8
Proof of need
Proof of concept
Proof of application
Relevance to practical architectures (building blocks)
Enterprise Continuum (TOGAF in context)
Business Scenarios (architecture requirements)
Architecture views - IEEE 1471
Architecture Principles; Compliance Reviews
Extension for Enterprise Architecture