What is an Enterprise Architecture?

*
Enterprise Architecture is the description of the current and/or future structure
and behavior of an organization's processes, information systems, technology,
personnel and organizational sub-units, aligned with the organization's core
goals and strategic direction. Although often associated strictly with information
technology, it relates more broadly to the practice of business optimization in
that it addresses business architecture, performance management,
organizational structure and process architecture as well.

An Enterprise Architecture Framework defines how to organize the structure and

views associated with an Enterprise Architecture. Because the discipline of
Enterprise Architecture is so broad, and because the enterprises it describes
tend to be large and complex, the models associated with the discipline also
tend to be large and complex. To manage this scale and complexity, an
Architecture Framework defines complementary projections of the enterprise
model called Views, where each View is meaningful to different system
stakeholders.
* Extract from Wikipedia
1
 Some examples of Enterprise Architecture Models
National Institute of Health Enterprise Architecture Federal Enterprise Architecture Framework Institute for Enterprise Architecture Developments

Treasury Enterprise Architecture Framework Zachman Enterprise Architecture Framework Lawrence Berkeley National Laboratory

2
What are the common elements in an Enterprise
Architecture structure? A Business Strategy Architecture - defines
the overall strategic direction of the business,
the vision, mission, business plans and
overall business objectives.
Strategy A Business Process Architecture describes
the business processes that have to be put in
place in order for the business to operate
efficiently and support effectively the
Business enterprise business objectives.
An Applications Architecture provides a
blueprint for the individual application systems
Applications to be deployed, their interactions, and their
relationships to the core business processes
of the organization
Data/Information
A Data/Information Architecture describes the
structure of an organization's logical and
physical data assets and data management
Technology resources.
A Technology Architecture describes the
software and hardware infrastructure intended
to support the deployment of core, mission-
critical applications.
 The Requirements Paradigm
Requirements • A Business Architecture - defines the
business strategy, governance,
organisation, and key business
Business Architecture processes.

• An Applications Architecture provides a

blueprint for the individual application
Data Architecture systems to be deployed, their interactions,
and their relationships to the core
business processes of the organization1

Applications Architecture • A Data Architecture describes the

structure of an organization's logical and
physical data assets and data
management resources1
Technology Architecture
• A Technology Architecture describes the
software infrastructure intended to support
the deployment of core, mission-critical
Capabilities applications.

1 The combination of Data Architecture and Application Architecture is also

referred to as the Information System Architecture.
4
How about Integration and Security?

Business
Integration

Applications

Security
Data/Information

Technology
 How about Integration?
Information fuels a lean
operator. An information Processes execute a
architecture forms one of lean operator’s
Business The
the three cornerstones
NGOSS Perspective
strategies and tactics
upon which a lean operator to achieve the
thrives entreprise’s
objectives and goals.
Integration

Applications

Data/Information Information Process

Architecture Architecture

The integration Integration

Technology
architecture brings
together lean operator’s
Architecture

information and process

architectures.
 How about Security?
The eTOM perspective with FCAPS
mapping
Business

Applications
Security

Data/Information

Technology
Looking in further detail at the architecture domain breakdown

Business Strategy Layer

Business Architecture Business Processes Layer

Org/Functional Layer

Applications Architecture
Applications/Services Layer

Data/Information Layer
Data Architecture

Software/Control Layer

Technology Architecture
Technology/Infrastructure Layer
 The Big Picture
Business Strategy Layer

Business Processes Layer

Organisational/Functional Layer

Data/Information Layer

Applications/Services Layer

Software/Control Layer

Technology/Infrastructure Layer

9
Business Strategy Layer

Extract from Accenture’s former Business Integration Methodology (BIM)

Business Process Layer
 Organizational / Functional Layer
Resource Management – Functional Function
Organization Example Chart Etymology
From Middle French fonction <
Old French function < Latin
functio gen. functionis
"performance, execution" <
Latin functus pp. of fungi
"perform, execute,
discharge".

function (plural functions)

What something does or is used
for.
A professional or official position.

Functionality
The ability to perform a task or
function; that set of
functions that something is
able or equipped to
perform.

Functional requirement
Describes a condition or
capability that a system,
person or object has to
satisfy, fulfill or comply with.
Application Layer
Information / Data Layer
Software / Control Layer
Technology Layer
 The Zachman Framework

15/10/2008 18
 The TOGAF model
TOGAF is a framework - a detailed method and a set of supporting
tools - for developing an enterprise architecture. It is described in a set
of documentation published by The Open Group
(http://www.opengroup.org/) on its public web server, and may be used
freely by any organization wishing to develop an enterprise
architecture for use within that organization. The architecture is
typically modeled at four levels or domains; Business, Application,
Data, Technology. A set of foundation architectures are provided to
enable the architecture team to envision the current and future state of
the architecture.

19
 The TOGAF model
The Open Group's Architectural
Framework has gained significant
momentum. Its purpose, as will all
architectural frameworks, is to
avoid starting with a blank sheet
of paper when creating an
architecture. Just as with RUP, it
contains tried and tested ways,
best practices and foundations
upon which things are built. It is
an industry wisdom consensus,
tool and technology neutral and
cross industry method.
Architecture Development Cycle

20
The TOGAF model

21
 NGOSS vs. Zachman & TOGAF Frameworks

New Generation OSS Initiative

Business Process Enterprise-wide

Framework Framework
( Enhanced Telecom Operations ( Shared Information and Data
Map - eTOM ) Model – SID )

vs
Applications Systems Integration
Requirements
Framework Framework
( Telecom Applications Map - TAM ) ( Technology Neutral Architecture –
TNA ) Business Architecture

Data Architecture

Applications Architecture

Technology Architecture

Capabilities

15/10/2008 22