Transcript EAI - The Open Group

Global EAI Summit 2004
TBI and TOGAF Reconciliation
Terence Blevins, VP and CIO
10:10 am/Monday May 24th
DC Coleman Room
What Does Reconciliation
Mean?
• Reconciliation
– A reconciling or being reconciled
• Reconcile
1.
2.
3.
4.
To
To
To
To
bring together again in love or friendship
induce to accept something disagreeable
reach a compromise agreement about
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..“
Raymond Slot M.Sc, MBA, Principal Consultant and Enterprise Architect
for Cap Gemini Ernst & Young
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
Understand
where change
is needed
How do we
keep
alignment
How do we
impact what
is being
deployed
How do we
incorporate
a new
system
What
direction is
appropriate
Create
Alignment
How do we
pick the right
solutions and
ensure
support for
stds
What process
are in most
need of
support
How do we
ensure
information
security
How do we
ensure that
the technical
components
are fit
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
Understand
where change
is needed
How do we
keep
alignment
How do we
impact what
is being
deployed
How do we
incorporate
a new
system
What
direction is
appropriate
Create
Alignment
How do we
pick the right
solutions and
ensure
support for
stds
What process
are in most
need of
support
How do we
ensure
information
security
How do we
ensure that
the technical
components
are fit
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
Understand
where change
is needed
How do we
keep
alignment
How do we
impact what
is being
deployed
How do we
incorporate
a new
system
What
direction is
appropriate
Create
Alignment
How do we
pick the right
solutions and
ensure
support for
stds
What process
are in most
need of
support
How do we
ensure
information
security
How do we
ensure that
the technical
components
are fit
TOGAF 8 ADM
Prelim:
Framework and
Principles
• 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!
A
H
Architecture
Vision
Architecture
Change
Management
B
Business
Architecture
C
G
Implementation
Governance
Requirements
F
Migration
Planning
Information
System
Architectures
D
E
Opportunities
and Solutions
http://www.opengroup.org/architecture/togaf8/index8.htm
Technology
Architecture
TBI Deliverables Map
Business
Process
Analysis
Tech Req
Document
Software
QA Plan
Req WT
report
DESIGN
DEPLOY
Unit Test
Results
System
Test Cases
Design WT
Report
Integration
Test Cases
Architect.
Document
Logical
Design
Integration
Test
Results
Integration
WT Report
Integration
Design
System
Test Result
Error
Handling
Guide
TDB
Code
Reviews
Simulation
Document
Developer
Governance
BUILD
Logical
Architect /
Designer
Quality
Manager
Business
Analyst
DEFINE
Unit Test
Cases
FDR Rpt
FDR Rpt
FDR Rpt
Repository
Repository
Repository
Source
Code
FDR Rpt
CTQ Signoff
Repository
Lessons
Learned
TOGAF ADM Deliverables
Map
PD
DP
TP
EC
RFAW
EC
EC
RFAW
SOW
RFAW
RFAW
SOW
TISA
RFAW
BS
SOW
TISA
TTA
EC
AP
BS
BA2
BA2
EFW
IGS
BD
AP
RFAW
I
I
I
Prel Phase
Phase A
Phase B
I
Phase C
I
I
Phase D
Phase E
I
BD
RFC
EC
SD
AP
RFAW
TD
BS
SOW
RFC
BA2
I
Phase F
I
Phase G
O
O
O
O
O
O
O
O
BD
BD
BD
IA
TP
IA
IA
AC
FWD
SOW
SOW
TISA
TTA
AP
BS
BA2
BA2
Phase H
O
RFAW
I
Reqs Mgmt
O
SRS
IA
BA1
AP
External Input
BD:Business
Data
Internal Input
AP:Arch
Principles
Output
EFW:External IGS:IT Govern PD:Product RFC:Req for SD:Standards
Frameworks
Strategy
Definitions
Changes
Devs
FRAW:Req
for Arch Work
BD:Business FWD:Framework AP:Arch
Data
Definition
Principles
EC:Enterprise DP:Data
Continuum
Principles
BS:Business
Scenario
BA:Business
Architecture
TP:Technical
Principles
ABL:Application
Baseline
TD:Tech
Devs
DBL:Data
Baseline
SOW:Statement TISA:Target TTA:Target
Of Work
IS Architecture Tech Arch
IA:Impact AC:Architecture SRS:Structured
Analysis
Contract
Req Statement
Intersections at…
Business
Process
Analysis
Tech Req
Document
Software
QA Plan
Req WT
report
DESIGN
DEPLOY
Unit Test
Results
System
Test Cases
Design WT
Report
Integration
Test Cases
Architect.
Document
Logical
Design
Integration
Test
Results
Integration
WT Report
Integration
Design
System
Test Result
Error
Handling
Guide
TDB
Code
Reviews
Simulation
Document
Developer
Governance
BUILD
Logical
Architect /
Designer
Quality
Manager
Business
Analyst
DEFINE
Unit Test
Cases
FDR Rpt
FDR Rpt
FDR Rpt
Repository
Repository
Repository
Source
Code
FDR Rpt
CTQ Signoff
http://www.opengroup.org/architecture/togaf8/index8.htm
Repository
Lessons
Learned
TOGAF ADM Feeds to TBI
PD
DP
TP
EC
RFAW
EC
EC
RFAW
SOW
RFAW
RFAW
SOW
TISA
RFAW
BS
SOW
TISA
TTA
EC
AP
BS
BA2
BA2
EFW
IGS
BD
AP
RFAW
I
I
I
Prel Phase
Phase A
Phase B
I
Phase C
I
I
Phase D
Phase E
I
BD
RFC
EC
SD
AP
RFAW
TD
BS
SOW
RFC
BA2
I
Phase F
I
Phase G
O
O
O
O
O
O
O
O
BD
BD
BD
IA
TP
IA
IA
AC
FWD
SOW
SOW
TISA
TTA
AP
BS
BA2
BA2
Phase H
O
RFAW
I
Reqs Mgmt
O
SRS
IA
BA1
AP
External Input
BD:Business
Data
Internal Input
AP:Arch
Principles
Output
EFW:External IGS:IT Govern PD:Product RFC:Req for SD:Standards
Frameworks
Strategy
Definitions
Changes
Devs
FRAW:Req
for Arch Work
BD:Business FWD:Framework AP:Arch
Data
Definition
Principles
EC:Enterprise DP:Data
Continuum
Principles
BS:Business
Scenario
BA:Business
Architecture
TP:Technical
Principles
ABL:Application
Baseline
TD:Tech
Devs
DBL:Data
Baseline
SOW:Statement TISA:Target TTA:Target
Of Work
IS Architecture Tech Arch
IA:Impact AC:Architecture SRS:Structured
Analysis
Contract
Req Statement
Summary
•
•
•
•
•
•
•
•
Prelim:
Framework and
Principles
TBI and TOGAF ADM are both great
for GIF
Any large effort requires enterprise
architecture and doing so requires
A
an open ADM
Architecture
Vision
H
Enterprise architecture method
Architecture
includes consideration of integration
Change
Management
An open architecture method is less
likely to create new integration
challenges
G
Any large project requires
Requirements
Implementation
integration implementation plans
Governance
TBI is a proven method for dealing
with integration details
We can harden the points of
F
Migration
interaction between TOGAF ADM and
Planning
E
TBI to ensure interoperability for GIF
Opportunities
Leverage will get us all to the top!
and Solutions
http://www.opengroup.org/architecture/togaf8/index8.htm
B
Business
Architecture
C
Information
System
Architectures
D
Technology
Architecture
Contact Details
Terence Blevins
VP and CIO
Mobile +1 650 888 6950
[email protected]
44 Montgomery Street
Suite 960
San Francisco, CA
94104 USA
Tel +1 415 374 8280 ext. 231
Fax 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
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…
IT demand
Ever widening gap!
IT budget
- run rates are declining!
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 TOGAF 7 “Technical Edition”
Data or information architecture
TOGAF 8
Application architecture
“Enterprise Edition”
Technology architecture TOGAF 7 “Technical Edition”
TOGAF 8 – Enterprise
Edition
Target
Enterprise Architectures
Architecture Development Method
Enterprise Continuum
Resource Base
Enterprise ADM
Prelim:
Framework and
Principles
• An iterative method
• Each iteration = new
decisions:
–
–
–
–
A
H
Enterprise coverage
Level of detail
Time period
Architecture asset re-use
• Decisions based on:
Architecture
Vision
Architecture
Change
Management
Business
Architecture
C
G
Implementation
Governance
– Competence / resource
availability
– Value accruing to the enterprise.
B
Requirements
F
Migration
Planning
Information
System
Architectures
D
E
Opportunities
and Solutions
Technology
Architecture
The Enterprise Continuum
Technology Architecture Continuum
Foundation
Architectures
Guides &
Supports
Common Systems
Architectures
Guides &
Supports
Products &
Services
Industry
Architectures
Guides &
Supports
Systems
Solutions
Organisation
Architectures
Guides &
Supports
Industry
Solutions
Solutions Continuum
Organisation
Solutions
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
Proof of need
Proof of concept
Proof of application
Relevance to practical
architectures (building blocks)
1998: TOGAF Version 4
Enterprise Continuum (TOGAF in
context)
•
1999: TOGAF Version 5
Business Scenarios (architecture
requirements)
•
2000: TOGAF Version 6
•
2001: TOGAF Version 7
Architecture Principles;
Compliance Reviews
•
2002: TOGAF Version 8
Extension for Enterprise
Architecture
•
Architecture views - IEEE 1471