Scribd
Upload
232 views

The Analysis and Documentation Framework

The document discusses the history and evolution of enterprise architecture frameworks from the 1960s to present. It notes that early frameworks from IBM in the 1960s focused mainly on technical infrastructure, while frameworks from the 1980s-1990s like the Zachman Framework and NIST EA began including applications and data integration. Modern frameworks from the late 1990s onward, like TOGAF, aim to provide solutions integrating all layers of an enterprise from strategy to technology. Enterprise architecture frameworks are useful for translating business strategy into concrete plans and solutions to achieve organizational goals.

Uploaded by

Don Xiao
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
232 views

The Analysis and Documentation Framework

The document discusses the history and evolution of enterprise architecture frameworks from the 1960s to present. It notes that early frameworks from IBM in the 1960s focused mainly on technical infrastructure, while frameworks from the 1980s-1990s like the Zachman Framework and NIST EA began including applications and data integration. Modern frameworks from the late 1990s onward, like TOGAF, aim to provide solutions integrating all layers of an enterprise from strategy to technology. Enterprise architecture frameworks are useful for translating business strategy into concrete plans and solutions to achieve organizational goals.

Uploaded by

Don Xiao
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 19

Module 5: The Analysis and

Documentation Framework
Enterprise Architecture
(Framework and Methodology)
EA Framework
Refers to any framework, process, or methodology which informs
how to create and use an enterprise architecture.
HISTORY of EA Framework
A commonly held tenet is that enterprise architecture
frameworks date to the mid-1980s, in accordance with the
publication of the Zachman Framework, developed by then-IBMer
John Zachman.
But deeper historic inquiries indicate that enterprise architecture
frameworks actually got their start two decades earlier, when IBM
produced their business systems planning (BSP), an effort that
Zachman helped found.
Pre-EAF
Originating with IBM, the BSP formalized a methodology that
indicates a theory for information systems architecture. It included
both a top-down planning approach and an architecture planning
process that was divided into a series of steps for a company to
follow. The plan, with diagrams and matrices to illustrate its system,
can be traced through all EAFs even today.
The Method process by Arthur Andersen as well as other BSP-like
methodologies from consulting firms and tech experts also
originated in this era. Overall, these approaches focused strictly on
technical infrastructure, like how to deploy hardware and servers.
Early EAF (1980s-1990s)
This era codifies the term “enterprise architecture”. The initial
wave of EAF theories include the PRISM, sponsored by IBM among
others, released in 1986, the Zachman Framework in 1987, and the
NIST EA in 1989.
Later entries marked a newer approach in this era including
Steven Spewak’s Enterprise Architecture Planning (EAP), which has
direct roots to the original BSP, as well as the TAFIM. These later
frameworks began including applications and data integration, as
systems became more sophisticated.
Modern EAF (Late 1990s - Present)
Newer frameworks include the FEAF, which is based on Spewak’s
EAP, as well as the TOGAF, a well-known version today, with roots in
the TAFIM.
Today’s frameworks aim to provide tangible solutions beyond
only IT, integrating all layers of an enterprise, including overall
strategy, business needs, IT infrastructure, and applications.
Why use EAF?
An enterprise architecture framework makes sense of the
complexities of achieving business strategy via IT strategy,
technology, and business needs across all silos of the company.
When performed at its best, an enterprise architecture translates the
vague and intangible business strategy to practical, concrete plans
and actions. Then, these designs are translated into solutions that
achieve business strategy.

~ Improved agility within the business ~


Spewak EA Planning Method
 the process of defining architectures
for the use of information in support
of the business and the plan for
implementing those architectures.
 focuses on the business implications
of architecture planning
 The business mission was the primary
driver, followed by the data required,
applications that use the data, and
the technology used to implement
the applications.
EA³ FRAMEWORK

You might also like