NIST Enterprise Architecture Model initiated in 1989, one of the earliest frameworks for Enterprise Architecture.[1]

1
Enterprise Architecture framework
NIST Enterprise Architecture Model initiated in
1989, one of the earliest frameworks for
Enterprise Architecture.1 An Enterprise
Architecture Framework (EA Framework) is a
framework for an Enterprise Architecture which
defines how to organize the structure and views
associated with an Enterprise Architecture.
2
(No Transcript)
3
(No Transcript)
4
Impression of Enterprise Architecture Frameworks
evolution (1987-2003).2 On the left The
Zachman Framework 1987, NIST Enterprise
Architecture 1989, EAP 1992, TISAF 1997, FEAF
1999 and TEAF 2000. On the right POSIX, TAFIM,
JTA, JTAA, TOGAF 1995, DoD TRM and C4ISR 1996,
and DoDAF 2003.
5
Enterprise Architecture started with the Zachman
Framework in 1987. Another early implementation
of an Enterprise Architecture framework was the
"Technical Architecture Framework for Information
Management" (TAFIM). The first draft of TAFIM was
completed in 1991 with the TAFIM Technical
Reference Model (TAFIM TRM). This technical
reference model wanted to use open systems and
new technologies available in the commercial
market, to develop a DoD-wide application
6
The TOGAF TRM was originally derived from the
Technical Architecture Framework for Information
Management (TAFIM), which in turn was derived
from the IEEE model 1003.04 or POSIX Open
System Environment a standard "to construct an
information processing system, including
consumers, system integrators, application
developers, system providers, and procurement
agencies".5
7
In recent years, it has become apparent that a
key benefit to be gained from Enterprise
architecture is the ability to support decision
making in changing businesses. Because Enterprise
Architecture brings together business models
(e.g. process models, organizational charts,
etc.) and technical models (e.g. systems
architectures, data models, state diagrams, etc.)
it is possible to trace the impact of
organizational change on the systems, and also
the business impact of changes to the systems. As
this benefit has emerged, many frameworks such as
DoDAF, MODAF, or AGATE have adopted a standard
meta model which defines the critical
8
architectural elements and the dependencies
between them. Applications based on these models
can then query the underlying architectural
information, providing a simple and strong
mechanism for tracing strategies to
organizational and technological impacts.
9
EA Framework topics
Persons who have ever remodeled their home, know
how important building codes, blueprints, and
city or county inspections are to successfully
complete the project. The architect operates
within a "framework" of building codes, preparing
blueprints for each phase of the project, from
the structural changes to the size and layout of
the rooms. Detailed drawings specify plumbing,
electrical, and building construction information
for the entire structure. Enterprise Architecture
works in a similar manner.6
10
An architecture framework for Information
Technology (IT) affects every aspect of the
enterprise. An Enterprise Architecture framework
is similar to building codes that ensure the
building is soundly constructed. The IT
governance bodies and procedures serve as the
city and county inspectors for building
improvement projects. Frameworks contain models
and standards that will be used to develop IT
architecture descriptions. The architecture
description is the blueprint.6
11
An architecture framework for Information
Technology (IT) affects every aspect of the
enterprise. An Enterprise Architecture framework
is similar to building codes that ensure the
building is soundly constructed. The IT
governance bodies and procedures serve as the
city and county inspectors for building
improvement projects. Frameworks contain models
and standards that will be used to develop IT
architecture descriptions. The architecture
description is the blueprint.6
12
Architecture domain
Example of the Federal Enterprise Architecture,
which has defined five architectural layers.
13
In the context of the creation of enterprise
architecture it is common, according to Pter
Bernus (2005)8, to recognise three or four
types of architecture, each corresponding to its
particular architecture domain. Examples of such
domains are Business architecture, Information
systems architecture, often subdivided into Data
architecture, and Application architecture, and
Technical architecture.
14
Architectural domains are a structuring criterion
for a collection of architecture products. They
should not be confused with the application
domain of the framework as such.
15
Layers of the Enterprise Architecture
16

• Contemporary federal guidance suggests thinking
  about layers of the enterprise architecture
• Business processes and activities
• Applications such as custom or off-the-shelf
  software tools
• Data that must be collected, organized,
  safeguarded, and distributed
• Technology such as computer systems and telephone
  networks

17
The Architecture Domains follow a pattern of
decomposition as one goes from top to the bottom
of the framework. The ownership can be divided
into 4 broad categories planner's view, owner's
view, designer's view and developer's view in
this order. All the views are mostly hierarchical
in nature. For business view the planner and
owner's level is typically called the value
chains (which are descriptive by nature). The
designer's view of business is also known as the
analytical view and there are various standards
for modeling this view. One mostly commonly used
modeling standard is the Business Process
Modeling Notation (BPMN). The designer's view
typically represents the execution level which
uses standards like Business Process Execution
Language (BPEL).
18
Enterprise Architecture Domains and Subdomains
19
Enterprise Architecture Reference Architecture
with Sub Domains The Application and Technology
Domains (which are not to be confused with
business domains) are characterized by domain
capabilities and domain services. The
capabilities are supported by the services. The
application services are also referred in
Service-oriented architecture (SOA). The
technical services are typically supported by
software products.
20
The data view starts with the data classes which
can be decomposed into data subjects which can be
further decomposed into data entities. The basic
data model type which is most commonly used is
called ERD (Entity Relationship Diagrams, see
Entity-relationship model). The Class, subject
and entity forms a hierarchical view of data.
Enterprises do have millions of instances of data
entities.
21
The Enterprise Architecture Reference Traditional
Model offers clear distinction between the
Architecture Domains ( Business ,
Information/Data , Application/Integration and
Technical/Infrastructure). These domains can be
further divided into Sub domain disciplines. An
Example of the EA Domain and Sub Domains is in
the image on the right.
22
Many Enterprise Architecture Teams consist of
Individuals with skills aligned with the
Enterprise Architecture Domains and Sub Domain
Disciplines. For Example  Enterprise Business
Architect , Enterprise Information Architect ,
Enterprise Application Architect , Enterprise
Infrastructure Architect .. etc. An Example of
the List of Reference Architecture Architecture
Patterns in the Application and Information
Architecture Domains are available at
Architectural pattern (computer science)
23
View model
A view model is a framework, which defines the
set of views or approaches to be used in systems
analysis or the construction of an enterprise
architecture. Since the early 1990s there have
been a number of efforts to define standard
approaches for describing and analyzing system
architectures. Many of the recent Enterprise
Architecture frameworks have some kind of set of
views defined, but these sets are not always
called "view models".
24
Types of Enterprise Architecture framework

• Consortia-developed frameworks
• EABOK (The Guide to the Enterprise Architecture
  Body of Knowledge) - a U.S. Federal-funded guide
  to EA in the context of legislative and strategic
  business requirements.
• Generalised Enterprise Reference Architecture and
  Methodology (GERAM)
• IDEAS Group - a four-nation effort to develop a
  common ontology for architecture interoperability
  
• RM-ODP - the Reference Model of Open Distributed
  Processing (ITU-T Rec. X.901-X.904 ISO/IEC
  10746) defines an enterprise architecture
  framework for structuring the specifications of
  open distributed systems.
• TOGAF - the Open Group Architecture Framework - a
  widely used framework including an Architectural
  Development Method and standards for describing
  various types of architecture.
• Good enough architecture methodology - a
  methodology based on experiences, results and
  best-practices gathered through real-life
  implementations of various building blocks that
  altogether provide a realizable architecture and
  working solutions.
• ARCON - A Reference Architecture for
  Collaborative Networks - not focused on a single
  enterprise but rather on networks of enterprises

25

• Open Source Frameworks
• TRAK - a general systems-oriented framework based
  on MODAF 1.2 and released under GPL/GFDL.

• Commercial frameworks
• Integrated Architecture Framework (IAF) - from
  Capgemini company in 1993
• CLEAR Framework for Enterprise Architecture -
  Atos Origin's Enterprise Architecture Framework

26

• OBASHI - the OBASHI Business IT methodology and
  framework
• Information FrameWork (IFW) - conceived by Roger
  Evernden in 1996
• Zachman Framework - an architecture framework,
  based on the work of John Zachman at IBM in the
  1980s
• The Enterprise Framework - an architecture
  framework, developed by Sam Holcman at the
  Enterprise Architecture Center of Excellence

27

• Defense industry frameworks
• DoDAF - the US Department of Defense Architecture
  Framework
• MODAF - the UK Ministry of Defence Architecture
  Framework
• NATO Architecture Framework
• AGATE - the France DGA Architecture Framework
• DNDAF - the DND/CF Architecture Framework (CAN)

28

• Government frameworks
• Government Enterprise Architecture (GEA) - a
  common framework legislated for use by
  departments of the Queensland Government
• FDIC Enterprise Architecture Framework
• Federal Enterprise Architecture Framework (FEAF)
  - a framework produced by the Office of
  Management and Budget for use within the U.S.
  Government
• NIST Enterprise Architecture Model
• Treasury Enterprise Architecture Framework (TEAF)
  - a framework for treasury, published by the US
  Department of the Treasury in July 2000.12
• Nederlandse Overheid Referentie Architectuur
  (NORA) - a reference framework from the Dutch
  Government E-overheid NORA