Enterprise Architecture

1
Enterprise Architecture

• TBTLA Quarterly Event November 2007
• Bill Webb
• Steven Young
• The University of Tampa
• Sam Joseph
• Gartner

2
What is Enterprise Architecture?

• Enterprise architecture is the business of
  architecting the enterprise.
• Noun and Verb
• The goal of the process is to take the business
  strategy and translate it into effective change
  of the enterprise
• The process itself involves creating key
  principals and models that describe the
  enterprises future and enable its evolution.

3
What is Enterprise Architecture?

• The scope of enterprise architecture includes the
  enterprises people, processes, information, and
  technology and their relationships to each other
  and the external environment
• Enterprise architects are the people who create
  the solutions to address the business challenges
  and support the enterprise in implementing those
  solutions.

4
Why is Enterprise Architecture Needed?

• System Complexity
• Information systems and business processes are
  complex and will become increasingly complex in
  the future.
• As system complexity increases, the costs to
  build and maintain those systems increase and
  take more of an organizations resources in time,
  money, and personnel.

5
Why is Enterprise Architecture Needed?

• Poor business alignment
• While costs are increasing, it is becoming harder
  for organizations to make sure that IT systems
  and spending are aligned with business needs
• IT costs are increasing while the value they
  bring to an organization is decreasing if the IT
  and business goals are not aligned.

6
History of Enterprise Architecture

• The field now known as enterprise architecture
  first came about 20 years ago.
• In 1987, J.A. Zachman wrote an article entitled
  A Framework for Information Systems
  Architecture in the IBM Systems Journal.
• Zachman originally described as information
  systems architectural framework, but it was soon
  renamed enterprise-architecture framework.

7
Zachman Framework for Enterprise Architectures

• John Zachman describes the framework as, Simply
  a logical structure for classifying and
  organizing the descriptive representations of an
  Enterprise that are significant to the management
  of the Enterprise, as well as the development of
  the Enterprises systems.

Source http//www.zachmaninternational.com/2/Home
.asp
8
Zachman Framework
Source http//www.zachmaninternational.com/2/Zach
manFramework.asp
9
How it works?

• Rows- illustrate different descriptions of an
  enterprise from a certain perspective.

Source http//www.zachmaninternational.com/2/Zach
manFramework.asp
10
How it works?

• Columns- One aspect of the enterprise from top to
  the bottom from different perspectives.

Source http//www.zachmaninternational.com/2/Zach
manFramework.asp
11
Strengths and Weaknesses

• Strength- End result (table)
• Weaknesses No process

12
The Open Group Architecture Framework (TOGAF)

• Divides enterprise architecture into four
  categories
• Business architectureDescribes the processes the
  business uses to meet its goals
• Application architectureDescribes how specific
  applications are designed and how they interact
  with each other
• Data architectureDescribes how the enterprise
  datastores are organized and accessed
• Technical architectureDescribes the hardware and
  software infrastructure that supports
  applications and their interactions

13
Architecture Development Method

• ADM or Architecture Development Method is the
  process for creating the enterprise architecture

14
How it works?
Sourcehttp//www.opengroup.org/architecture/togaf
8-doc/arch/Figures/prelim.gif
15
How it works?
Source http//www.developer.com/java/ent/article.
php/3374171
16
Strengths and Weaknesses

• Strengths- provides a process for developing an
  architecture.
• Flexible so can be tailored to a companys
  organization
• Weakness- Open/generic, no specific end result

17
Federal Enterprise Architecture (FEA)

• Technical Architecture Framework for Information
  Management (TAFIM) was one of the first attempts
  at enterprise architecture by the Department of
  Defense in the mid 90s
• Influenced the Clinger-Cohen Act which stated
  that federal agencies should improve their IT
  investments
• Over time Government efforts in enterprise
  architecture lead to the creation of FEA

18
How it works?

• An enterprise is built of segments
• There are two types of segments
• Core mission area segments
• Business-services segments
• Also use enterprise services which span political
  boundaries

19
Segment Map of the Federal Government
Sourcehttp//msdn2.microsoft.com/en-us/architectu
re/bb466232.aspx
20
FEA Process

• Step 1 Architectural AnalysisDefine a simple
  and concise vision for the segment, and relate it
  back to the organizational plan.
• Step 2 Architectural DefinitionDefine the
  desired architectural state of the segment,
  document the performance goals, consider design
  alternatives, and develop an enterprise
  architecture for the segment, including business,
  data, services, and technology architectures.
• Step 3 Investment and Funding StrategyConsider
  how the project will be funded.
• Step 4 Program-Management Plan and Execute
  ProjectsCreate a plan for managing and executing
  the project, including milestones and performance
  measures that will assess project success.

21
Strengths and Weaknesses

• Strengths- clearly defines output and provides a
  process for creating a framework
• Weakness- Government architecture so it has not
  been applied to a business before
• General Accounting Office (GAO) reported that,
  Only 20 of 96 agencies examined had established
  at least the foundation for effective
  architecture management. Further, while 22
  agencies increased in maturity since 2001, 24
  agencies decreased in maturity and 47 agencies
  remained the same.

22
Gartner

• Enterprise architecture is the process of
  translating business vision and strategy into
  effective enterprise change by creating,
  communicating and improving the key principles
  and models that describe the enterprise's future
  state and enable its evolution.

23
GEAF

• Three primary viewpoints
• enterprise business architecture (EBA)
• enterprise information architecture (EIA)
• enterprise technology architecture (ETA).
• Introduces the Enterprise Solution Architecture
  Framework (ESAF) - deals directly with
• combining and reconciling the loosely coupled and
  often conflicting viewpoints
• into a unified architecture for an enterprise
  solution.

24
Gartner process model
25
Strengths and Weaknesses

• Strengths
• Practice guidance
• Maturity model
• Business focus
• Weakness
• Information availability
• Reference models

26
Q A