Enterprise architecture is a discipline for proactively managing organizational change and complexity by aligning business strategy, goals, and processes with information technology solutions. It provides a framework for governing technology decisions and guiding the organization from its current to future state. Benefits include improved business-IT alignment, increased agility, standardization, and cost savings. Enterprise architecture frameworks like TOGAF provide common vocabulary, models, and processes to develop the current and target architecture states and transition plans.

1. 18 September 2013 1
Enterprise Architecture
Enterprise Architecture
Definition, Applications, Technology
Leo Shuster
Director, IT Architecture
Nationwide Insurance

2. 18 September 2013 2
Enterprise Architecture
Disclaimers
 Many competing perspectives on Enterprise
Architecture exist – this just one of them
 There is no single, agreed upon Enterprise
Architecture standard
 Information presented here will not make you an
instant Enterprise Architecture expert
 This presenter should not be held liable for any
misconceptions, misrepresentations, or mistakes you
make outside of class based on the information
presented here

3. 18 September 2013 3
Enterprise Architecture
The Architecture Continuum
Enterprise
Architecture
(City)
Portfolio
Architecture
(Street)
System
Architecture
(Building)
If enterprises were cities…
Architecture Continuum

4. 18 September 2013 4
Enterprise Architecture
Enterprise Architecture & the Enterprise
Enterprise Strategy
Fire and
hope!
Enterprise Architecture
Business Operating Environment
and IT Infrastructure
Transition
Planning
Architecture
Governance
Bus Architecture IT Architecture
AEI
Corporate
Yankee
Group
Saturn
Group
Yarn
Division
Knits
Division
Seneca
Plant
Raleigh
Plant
Cash
Management
Shipping
Accounting
Component
Design
Yarn Buying
Order Entry
Component
Scheduling
Yarn
Dyeing
Inventory
Assortment
Planning
Component
Knitting
Tagging &
Packing
Business
Structure
Business
Locations
Classically, EA is the “planning” function between strategy formulation and delivery…
ProgramfocusEnterprisewidefocus
Strategy
Planning
Design
and
Delivery
Change Programs
Soln Outline Macro Design Micro Design Devt, etc.
Program Architecture
Soln Outline Macro Design Micro Design Devt, etc.
Program Architecture
Enterprise
Architecture
= “the city plan”
System Design
= “the buildings”
Strategy
= “the city’s purpose & goals”Technology
Availability
Business
Opportunity
Bus Strategy IT Strategy
“Do the Right Things”
“Do the Right Things Right”

5. 18 September 2013 5
Enterprise Architecture
What is Enterprise Architecture?
MIT Center for Information Systems Research (2007)
• Enterprise architecture is the organizing logic for business processes and IT infrastructure reflecting the integration and
standardization requirements of the company's operating model
Enterprise Architecture Research Forum
• Continuous practice of describing the essential elements of a socio-technical organization, their relationships to each other
and to the environment, in order to understand complexity and manage change
Gartner (2013)
• Discipline for proactively and holistically leading enterprise responses to disruptive forces by identifying and analyzing the
execution of change toward desired business vision and outcomes. EA delivers value by presenting business and IT leaders
with signature-ready recommendations for adjusting policies and projects to achieve target business outcomes that
capitalize on relevant business disruptions.
• EA is used to steer decision making toward the evolution of the future state architecture.
The Open Group
• Enterprise architecture (EA) is the definition and representation of a high-level view of an enterprise‘s business processes
and IT systems, their interrelationships, and the extent to which these processes and systems are shared by different parts
of the enterprise
US Federal Enterprise Architecture Framework (FEAF)
• Enterprise architecture is a management practice to maximize the contribution of an agency’s resources, IT investments,
and system development activities to achieve its performance goals.
• Architecture describes clear relationships from strategic goals and objectives through investments to measurable
performance improvements for the entire enterprise or a portion (or segment) of the enterprise.

6. 18 September 2013 6
Enterprise Architecture
What is Enterprise Architecture?
Simple definition:
Enterprise Architecture is a strategy to minimize IT and business mistakes

7. 18 September 2013 7
Enterprise Architecture
What is NOT Enterprise Architecture?
System Architecture
and Design
Coding Standards and
Practices
Database Design
IT Governance
Enterprise
Architecture is a
discipline that
spans the entire
enterprise but
does not dive
into the minutia
of project
delivery

8. 18 September 2013 8
Enterprise Architecture
Enterprise Architecture Objectives
Align business and IT strategies
Increase business and IT agility
Establish and refine future
architecture vision
Govern technology decisions and
direction
The primary goal of EA is to make the organization as efficient and
effective as possible!

9. 18 September 2013 9
Enterprise Architecture
Enterprise Architecture Benefits
Business
• Better business
and IT
alignment
• Increased
business agility
• Business
process
efficiency
• Reduced time
to market
IT
• Increased
standardization
and technology
alignment
• Platform
consolidation
• Technology and
application
portfolio
simplification
Financial
• Better return
on existing
investment and
reduced risk for
future
investment
• Cost savings
• Predictable
investment
model

10. 18 September 2013 10
Enterprise Architecture
Objectives and Benefits of EA - Survey

11. 18 September 2013 11
Enterprise Architecture
Enterprise Architecture Program
Cost focus Value focus
EA is a journey, often non-linear
Tactical, opportunistic Strategic, systematic
Cost Reduction
 What do we have?
 Need all of it?
 Consolidate to
reduce costs?
 Desire for impact
analysis
Standardization
 Develop standards
and recommended
best practices (e.g.
technology stacks,
server platforms)
 Seeking repeatability
 Encourage IT
evolution
 Focusing on IT scope
only
Broaden Scope
 Meet business
needs by linking IT
to business
 Managing
architectures
outside IT
 Increasing focus on
business
architecture and
business processes
Realizing Strategy
 Develop business
strategy
 Value propositions,
capabilities,
resources?
 Refine into to-be
 Compare to as-is
 Create transition plan
 Execute
Enterprise Architecture has to be treated as an ongoing program that
continues to evolve together with the organization

12. 18 September 2013 12
Enterprise Architecture
Enterprise Architecture Frameworks
• Many Enterprise Architecture
frameworks have been created
– Zachman Enterprise Framework
– The Open Group Architecture
Framework (TOGAF)
– OMB Federal Enterprise Architecture
(FEA)
– The Gartner Methodology (formerly the
Meta Framework)
– Many others
• Each framework possesses different
strengths and weaknesses
– No ideal framework for all situations
– Each framework has to be customized
to fit the organization
EA Frameworks typically
include:
•Common
vocabulary, models, and
taxonomy
•Processes, principles, strate
gies and tools
•Reference architectures
and models
•Prescriptive guidance (EA
processes, architecture
content, implementation
roadmap, governance)
•Catalog of architecture
deliverables and artifacts
•Enterprise Architecture
Content Metamodel

13. 18 September 2013 13
Enterprise Architecture
EA Frameworks - Zachman

14. 18 September 2013 14
Enterprise Architecture
EA Frameworks - TOGAF

15. 18 September 2013 15
Enterprise Architecture
Enterprise Architecture Components
• Enterprise
Architecture consists
of several logical
components
– Each component
must identify its own
strategies, reference
models, and
directions
• EA serves as a
governance function
– Architecture Review
Board
– Processes and
policies
– Technology
– Funding
• EA Repository
– Central repository
for all EA artifacts * Based on Oracle Enterprise Architecture Framework

16. 18 September 2013 16
Enterprise Architecture
Enterprise Architecture Lifecycle
Create the Enterprise
Architecture vision
and program
structure
Document current
state architecture
Develop future state
architecture
Create a roadmap of
transitioning from
current state to
future state
Establish and execute
governance processes
Develop business
case(s) for the
initiative(s) identified
on the roadmap
EA lifecycle is a series
of continuous iterations
over these phases
* Based on Oracle Enterprise Architecture Framework

17. 18 September 2013 17
Enterprise Architecture
EA and IT Governance
• IT governance is a set
of processes and
policies that dictate
how IT work should
be performed
• EA governance is a
set of processes and
policies that dictate
how technology
decisions are made
• IT and EA governance
domains intersect in
the project delivery
space
* Courtesy of ebizQ

18. 18 September 2013 18
Enterprise Architecture
EA Governance
* Based on TOGAF
Alignment
• Enterprise Architecture
establishes a number of
governance mechanisms
– Architecture Board
serves as a governance
body ensuring IT
initiatives align with EA
– CTO and/or Chief
Architect provide
stewardship and
guidance
– Enterprise Architects
develop policies,
practices, and
processes that the
Architecture Board
supports
• Enterprise Architecture
and IT leadership ensures
alignment with business
goals, strategies, and
objectives

19. 18 September 2013 19
Enterprise Architecture
EA Governance - Technology
Enterprise
Architecture
Opportunity
Identification
Opportunity
Validation
Technology
Guidance
Design
Review
Identify
opportunities to
leverage enterprise
platforms
Validate platform
usage
opportunities
Validate solution
design to ensure
appropriate use of
technology
Guide efforts
towards the most
appropriate
technology platform

20. 18 September 2013 20
Enterprise Architecture
Measuring Enterprise Architecture Value
No single, comprehensive set of Enterprise Architecture metrics exist. Each
organization has to develop metrics most relevant to its EA objectives.

21. 18 September 2013 21
Enterprise Architecture
Q & A

22. 18 September 2013 22
Enterprise Architecture
About the Author
About
•Leo Shuster directed Enterprise Architecture and SOA for a number of organizations including
Nationwide Insurance, National City Corporation, and Ohio Savings Bank
•Presented on Enterprise Architecture, SOA, BPM, and related topics at a number of
conferences
•MS in Computer Science and Engineering from CWRU and MBA from Cleveland State
Publications
•Blog: http://leoshuster.blogspot.com
•SOA Governance Book with Thomas Erl: http://www.amazon.com/SOA-Governance-
Governing-Premise-Service-Oriented/dp/0138156751
•Service-Driven Approaches to Architecture and Enterprise Integration Book: http://www.igi-
global.com/book/service-driven-approaches-architecture-enterprise/74192
Contact Info
•E-mail: leo@incipienttech.com
•LinkedIn: http://www.linkedin.com/in/leoshuster