Enterprise Architecture and
TOGAF (The Open Group
Architecture Framework)
Alan McSweeney
January 27, 2010
2
Objectives
• To provide an overview of the importance of Enterprise
Architecture and to provide an overview of The Open
Group Architecture Framework (TOGAF) version 9
concepts and structure
January 27, 2010
3
Agenda
• Enterprise Architecture
• The Open Group Architecture Framework (TOGAF)
• Using TOGAF Effectively
• Establishment of an Enterprise Architecture Function
January 27, 2010
4
Enterprise Architecture
January 27, 2010
5
Enterprise Architecture
• The phrase “Enterprise Architecture” was first used in 1987 by John
Zachmann in an IBM Systems Journal article titled “A Framework for
Information Systems Architecture” (see
http://www.zachmaninternational.com/images/stories/ibmsj2603e.
pdf)
• Intended to address two problems
− System complexity - organisations were spending more and more money
building IT Systems
− Poor business alignment - organisations were finding it more and more
difficult to keep increasingly expensive IT systems aligned with business needs
• The cost and complexity of IT Systems have exponentially increased
while the chances of deriving real value from the systems has
decreased
January 27, 2010
6
Key Messages Relating to Enterprise Architecture
• IT-business alignment has never been so important
• Alignment must be pursued in the context of
understanding business processes and priorities
• Service-orientation is not just for applications
• Service contracts are not just about function: they
encapsulate and communicate business priorities to IT
delivery organisations
• Enterprise architecture needs to be more inclusive,
sophisticated, flexible and integrated
• IT governance models must take all this into account
January 27, 2010
7
Business Pressures are Driving Business and IT Change
• Globalisation
− Customers, partners, suppliers and greater competition
− Connectedness driving value chains
• Transparency
− Industry regulations, consumer pressure and competition d