Enterprise Architecture and TOGAF, Quick Look

1. ENTERPRISE
ARCHITECTURE

2. Enterprise : A company, business, organization, or other purposeful endeavor.
Architecture : The process and the product of planning, designing, and constructing buildings and other
physical structures
Latin : Architectūra
Ancient Greek arkhitéktōn (“architect”)
Arche(principal,chief)+Tecton(craftsman,builder).
IEEE: “An architecture is the fundamental organization of a system embodied in its components, their
relationships to each other, and to the environment, and the principles guiding its design and evolution.”
TOGAF: “Architecture has two meanings depending upon its contextual usage:
(1) A formal description of a system, or a detailed plan of the system at component level to guide its
implementation;
(2) The structure of components, their interrelationships, and the principles and guidelines governing their
design and evolution over time.”
The Netherlands Architecture Forum(NAF):“a normative restriction of design freedom and operationally as
a set of design principles.”

3. What is Enterprise Architecture?

4. Enterprise
Architecture
(City)
Portfolio
Architecture
(Street)
System
Architecture
(Building)
Architecture Continuum
An Analogy

5. • Strategic Layer: refers to a layer which all major decisions of
an organisation are taken there.
• Mission Layer: All processes of the organization
• It contains: Supreme Management, Intermediate Management and
Operational Management
• ICT Layer: This Layer contains all informational and
communicational processes which are used to do mission
layer tasks.
Enterprise layers and views

6. Competitors can use
new Techs against us
New Techs are cheaper
New Techs are more
efficient
Expectations of
customers are rising
Supporting old tech is
too expensive
Change in Enterprise IT, What Drives the Change
_. Changes in business
_. Changes in Technology

7. 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!

8. How To do Enterprise Architecture?
As-Is -> To-Be
•EA planning entails the definition of a current state (called AS-IS) or as-is architecture in four
categories:
• business processes
• application programs
• information/data
• infrastructure technology.
•Then the business plans are reviewed and an appropriate future state (called TO-BE) is created
for each category.
•The future state is compared to the current state in a gap analysis, and a sequencing plan is
developed to progress from the current state to the future state.

9. Enterprise Architecture: The analysis and documentation of an enterprise in its current and
future states from a strategy, business, and technology perspective.
EA = S + B + T
Network
Infrastructure
Network
Infrastructure
Network
Infrastructure
Network
Infrastructure
Network
Infrastructure
Network
Infrastructure
Network
Infrastructure
Network
Infrastructure
OptimizedNetworks
andInfrastructure
IntegratedSystems
andApplications
EnhancedDataand
InformationFlows
ImprovedBusiness
ProductsandServices
Network
InfrastructureNetwork
InfrastructureUpdatedStrategic
Goals&Initiatives
Network
Infrastructure
Network
Infrastructure
Network
Infrastructure
Network
Infrastructure
Network
Infrastructure
Network
Infrastructure
Network
Infrastructure
Network
Infrastructure
OptimizedNetworks
andInfrastructure
IntegratedSystems
andApplications
EnhancedDataand
InformationFlows
ImprovedBusiness
ProductsandServices
Network
InfrastructureNetwork
InfrastructureUpdatedStrategic
Goals&Initiatives
CURRENTCURRENT
ARCHITECTUREARCHITECTURE
FUTUREFUTURE
ARCHITECTUREARCHITECTURE
Architecture
Management&
TransitionPlan
LinesofBusiness
C
O
M
P
O
N
E
N
T
S
NetworkNetwork
InfrastructureInfrastructure
NetworkNetwork
InfrastructureInfrastructure
NetworkNetwork
InfrastructureInfrastructure
NetworkNetwork
InfrastructureInfrastructure
NetworkNetwork
InfrastructureInfrastructure
NetworkNetwork
InfrastructureInfrastructure
NetworkNetwork
InfrastructureInfrastructure
NetworkNetwork
InfrastructureInfrastructure
NetworksNetworks&&
InfrastructureInfrastructure
SystemsSystems&&
ApplicationsApplications
DataData&&
InformationInformation
ProductsProducts&&
ServicesServices
NetworkNetwork
InfrastructureInfrastructureNetworkNetwork
InfrastructureInfrastructureGoalsGoals&&
InitiativesInitiatives
LinesofBusinessLinesofBusiness
CC
OO
MM
PP
OO
NN
EE
NN
TT
SS
Security/Standards/WorkforceSecurity/Standards/Workforce
TechnologyTechnology––BusinessBusiness––StrategyStrategy
NetworkNetwork
InfrastructureInfrastructure
NetworkNetwork
InfrastructureInfrastructure
NetworkNetwork
InfrastructureInfrastructure
NetworkNetwork
InfrastructureInfrastructure
NetworkNetwork
InfrastructureInfrastructure
NetworkNetwork
InfrastructureInfrastructure
NetworkNetwork
InfrastructureInfrastructure
NetworkNetwork
InfrastructureInfrastructure
NetworksNetworks&&
InfrastructureInfrastructure
SystemsSystems&&
ApplicationsApplications
DataData&&
InformationInformation
ProductsProducts&&
ServicesServices
NetworkNetwork
InfrastructureInfrastructureNetworkNetwork
InfrastructureInfrastructureGoalsGoals&&
InitiativesInitiatives
LinesofBusinessLinesofBusiness
CC
OO
MM
PP
OO
NN
EE
NN
TT
SS
Security/Standards/WorkforceSecurity/Standards/Workforce
TechnologyTechnology––BusinessBusiness––StrategyStrategy

10. Why Enterprise Architecture?
Enterprise Architecture is justified for businesses:
• which have significant application assets.
• which have a long history in information technology.
• where information technology is strategic.
It may also be justified in:
• Mergers/Acquisitions
• Enterprises dependent on software packages
• They must be low key, with no negative impact on other projects.
• Optimise the often fragmented legacy of processes (both manual and automated) into an
integrated environment that is responsive to change and supportive of the delivery of the business
strategy
• Effective management and exploitation of information through IT is a key factor to business success,
and An enterprise architecture addresses this need, by providing a strategic direction for IT
activities.
• Good enterprise architecture helps achieve the right balance between IT efficiency and business
innovation.

11. Enterprise Architecture
A spectrum of goals, scopes, and entry points
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
Actionable EA
 Develop business
strategy
 Value propositions,
capabilities,
resources?
 Refine into to-be
 Compare to as-is
 Create transition plan
 Execute
Enabling Organizations to Turn Change into a Competitive Advantage

12. • A more efficient business operation:
— Lower business operation costs
— More agile organization
— Business capabilities shared across the organization
— Lower change management costs
— More flexible workforce
— Improved business productivity
• A more efficient IT operation:
— Lower software development, support, and maintenance costs
— Increased portability of applications
— Improved interoperability and easier system and network management
— Improved ability to address critical enterprise-wide issues, such as security
— Easier upgrade and exchange of system components
Benefits of Enterprise Architecture

13. • Better return on existing investment, reduced risk for future investment:
— Reduced complexity in the business and IT
— Maximum return on investment in existing business and IT infrastructure
— The flexibility to make, buy, or out-source business and IT solutions
— Reduced risk overall in new investments and their costs of ownership
• Faster, simpler, and cheaper procurement:
— Simpler buying decisions, because the information governing procurement is readily available in
a coherent plan
— Faster procurement process, maximizing procurement speed and flexibility without sacrificing
architectural coherence
— The ability to procure heterogeneous, multi-vendor open systems
— The ability to secure more economic capabilities
Benefits of Enterprise Architecture

14. Two major approaches to
enterprise architecture (EA)
have evolved
•A top-down approach that
assumes comprehensive
scope and strictly follows a
formal process
•A bottom-up approach that
starts with infrastructure
technology standardization
and then moves up the food
chain to target high-priority
problem areas and eventually
influence business
architecture
Approaches

15. What is an architecture framework
• Foundational structure, or set of structures, that can be used for developing a broad range
of different architectures (guides the development of specific architectures)
• Provides a method to help design a target state of the enterprise in terms of building
blocks, and to show how the building blocks fit together
• Set of tools and common vocabulary
• It recommends a set of services, standards, design concepts, components and
configurations
Speed up and simplify architecture development, ensure more complete coverage of the
designed solution, and make certain that the architecture selected allows for future growth
in response to the needs of the business.
Why do I Need a Framework for Enterprise Architecture?

16. • Many Enterprise Architecture frameworks have
been created
– Zachman Enterprise Framework
– The Open Group Architecture Framework (TOGAF)
– OMB Federal Enterprise Architecture (FEA)
– Department of Defense Architecture Framework
(DODAF)
– Treasury Enterprise Architecture Framework (TEAF)
– 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, strategies
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

17. TOGAF – A Summary
What is TOGAF?
 The Open Group Architecture Framework is a framework – a detailed method and a set of
supporting tools – for developing an enterprise architecture for use within that organisation
 TOGAF is developed and maintained by members of The Open Group, working with the
architecture forum
 Being consideerd as de facto standard
History of TOGAF
• 1994 the US Department of Defense gave their Technical Architecture Framework for
Information Management (TAFIM) to TOGAF for development
• 1995 TOGAF version 1 was released
• 2009 TOGAF version 9 was released
• 2011 TOGAF version 9.1 was released

18. TOGAF - Concepts
TOGAF Capability
Framework
TOGAF Enterprise
Continuum & Tools
TOGAF ADM
and
Content Framework
Architecture Capability Framework
(Part 7)
Architecture Development Method (Part 2)
ADM Guidelines and Techniques
(Part 3)
Introduction and Core Concepts ( Part 1)
Architecture Content Framework
(Part 4)
Enterprise Continuum and Tools (Part 5)
TOGAF Reference Models ( Part 6)
High level introduction and key
concepts, definition of terms
and release notes
Structured Meta-model for
architectural artifacts. Re-
useable architecture building
blocks
Taxonomies and tools to
categorise and store outputs
How to establish and operate
EA with an Organisation
Core of TOGAF, a step by step
guide to developing enterprise
architecture
Collections of Guidelines and
Techniques to apply with using
ADM
Two reference models that can
be applied to EA

19. TOGAF ADM

20. TOGAF ADM - Iterations

21. TOGAF - Types of architecture domains
Enterprise
Architecture
Business Architecture
How the business is
organised to met
itsobjectives
How the information
System support the
objective of the business
Applications Architecture
Technology Architecture
Data Architecture
How the technology fits
together
Information Systems Architecture

22. TOGAF - Architecture Domains : Definitions
• Architecture Domain: The architecture area being considered
• Business architecture: The business strategy, governance, and key business processes information as
well as the interaction between these concepts
• Application architecture: A description of the major logical groups of capabilities that manage the data
objects necessary to process the data and support the business
• Data architecture: The structure of an organisation’s logical and physical data assets and data
management resources
• Technology architecture : The Logical software and hardware capabilities that are required to support
deployment of business, data and application services, includes middleware, networks,
communications etc

23. Architecture Landscapes.

25. Value of Enterprise Architecture
• Provides a clear view of how the business and technology resources
will support and achieve an organization’s business goals and
initiatives.
• Understand the strategy, the business, the systems and the
infrastructure and how they interrelate.
• Moving "need to know" information to those that "know they need"
upstream and down stream and in both directions.
• Helps us prioritize and decide which things to do and in what order.
• “Doing the Right Things”
• Governs the change and building of things.
• “Doing the Things Right”

26. ♦ Achieve strategic goals that depend on IT resources
♦ Improve business performance by maximizing IT efficiency
♦ Strategic priorities/business requirements drive IT solutions
♦ Total visibility of multiple IT networks, systems, applications, services, and
databases across the entire enterprise
♦ Share information between lines of business
♦ Reduce duplicative IT resources across the enterprise
♦ Protect data and IT assets that rely on enterprise-wide approaches
♦ Maximize the effective use of limited budgets
Result of Implementing Enterprise Architecture