What Does Reconciliation Mean?
Reconciliation
A reconciling or being reconciled
Reconcile
To bring together again in love or friendship
To induce to accept something disagreeable
To reach a compromise agreement about
To make or show to be consistent
We’ ll focus on 4 today -we think that TOGAF and TBI are consistent
Position
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 Architecture
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 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..
Pressures on IT
Align Information Technology to Business
Increase accountability to improve cost performance
Drive accountability of spending
Ensure network availability
Ensure security
Drive standardization
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
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
TOGAF 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!
TBI Deliverables Map
TOGAF ADM Deliverables Map
Intersections at
TOGAF ADM Feeds to TBI
Summary
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!
Contact Details
Backups
Presentation Outline
Background
Why Enterprise Architecture is Important
TOGAF and TOGAF History
TOGAF and TBI
Summary
Integration Is a Big Issue
Gartner Dataquest forecasts Worldwide End-User IT Spending will grow
from $2.7 US trillion in 2001
to greater than $3.0 US trillion in 2002 and
reach $3.4 US trillion 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, according to IDC
CIO magazine survey says companies spend over 35% on integrating systems and processes
Presentation Outline
Background
Why Enterprise Architecture is Important
TOGAF and TOGAF History
TOGAF and TBI
Summary
CIOs Have Issues in Common
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
Presentation Outline
Background
Why Enterprise Architecture is Important
TOGAF and TOGAF History
TOGAF and TBI
Summary
TOGAF 8 Scope
TOGAF covers the development of four related types of architecture:
Business architecture
Data or information architecture
Application architecture
Technology architecture
TOGAF 8 -Enterprise Edition
Enterprise ADM
The Enterprise Continuum
Resource 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
TOGAF Origins
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 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