Enterprise Architecture

Dexter C. Hulleza
MIT Student - Philippine Christian University

25 June 2022
Overview
● Evolution of Enterprise Architecture (EA)
● Zachman Framework for EA
● Enterprise Engineering (EE) for Rapid Development
● Using EA of Enterprise Integration
● Balanced Scorecard and Strategy Maps (BSSM)
● Introduction, Basic Concepts of Balanced Scorecard
● Basic Concepts of Strategy Maps
● Examples of BSSM
● Steps on how to develop BSSM
Definition of Enterprise Architecture
A set of descriptive representations relevant for describing an enterprise that is intended to
be created and constitutes the baseline for changing the enterprise once it is created - John
Zachman

The organizing logic for a firm’s core business processes and IT capabilities captured in a set
of principles, policies and technical choices to achieve the business standardization and
integration requirements of the firm’s operating model - MIT Center for Information
Systems Research (CISR)

Enterprise architecture (EA) is a discipline for proactively and holistically leading enterprise
responses to disruptive forces by identifying and analyzing the execution of change toward
desired business vision and outcomes. EA delivers value by presenting business and IT
leaders with signature-ready recommendations for adjusting policies and projects to achieve
target business outcomes that capitalize on relevant business disruptions - Gartner
Definition of Enterprise Architecture

An enterprise architecture (EA) is a conceptual blueprint that

defines the structure and operation of an organization.

The intent of an enterprise architecture is to determine how an

organization can most effectively achieve its current and
perceived future objectives from an integrated strategy,
business and technology perspective.

4
Enterprise Architecture Helps You
Align business and IT with consistent design, documentation and
communication of architecture assets

Understand the full impact of changing business and IT capabilities in

support of strategic decision-making

Model and integrate complex strategy, process, application, data and

technology architectures

Collaborate with all stakeholders on innovation and transformation

initiatives

Retain organizational knowledge

Evolution of Enterprise Architecture

Business systems Early EA – PRISM

Planning BSP and Zachman Modern EA

•1986, PRISM Research service of

• Developed by IBM indexed systems, first to define •TOGAF
• BSP information systems plans Architecture for an enterprise; •FEAF
describe the relationship PRISM EA Framework
•DODAF
between organisation, Business •1987, John Zachman of IBM
introduced Zachman Framework,
processes, Data and Information who is also considered to be the
systems father of Enterprise Architecture by
many groups.
Evolution of Enterprise Architecture
Genesis: Business Systems Planning methodology

7
Evolution of Enterprise Architecture
Prism EA Framework

8
Zachman
Framework

9
 Evolution of Enterprise Architecture from 90s
Year 1987 1994 1995 1996 2002 2003 2006 2009 2017
Zachman’s TAFIM TOGAF 1.0 Clinger – FEA replaces TOGAF 8.0 FEA TOGAF 9 IndEA
Enterprise released Enterprise Cohen Bill FEAF Enterprise completed (~) released released
Activity Architecture Edition passed Edition
released released

The development of the above frameworks has paved the way for multiple Nations (Korea, Singapore, UAE, UK and USA) and Industry
(Microsoft and Oracle) to develop their own tailored enterprise architecture frameworks which are being consumed by enterprises.

The Open Group The Federal Enterprise

The Zachman Framework The Gartner Methodology
Architectural Framework Architecture

The Zachman Framework is The Open Group A federal enterprise Gartner Methodology is
an Enterprise Ontology Architecture Framework architecture (FEA) provides based on the amalgamation
which provides a formal and (TOGAF) is a framework a common approach for the of Gartner framework and
structured way of viewing for enterprise architecture integration of strategic, Meta architecture
and defining an enterprise. which provides an approach business and technology development process.
for designing, planning, management as part of
implementing, and organization design and
governing an enterprise performance improvement
information technology
architecture
Source: TOGAF and A comparison of top four EA methodologies, 2007 by Microsoft
 Zachman Framework
Overview

The Zachman Framework™ is a schema - the intersection

between two historical classifications that have been in use for
literally thousands of years. The first is the fundamentals of
communication found in the primitive interrogatives: What,
How, When, Who, Where, and Why. It is the integration of
answers to these questions that enables the comprehensive,
composite description of complex ideas.

The second is derived from the transformation of an abstract

idea into an instantiation that was initially postulated by
ancient Greek philosophers and is labeled in the Zachman
Framework™: Identification, Definition, Representation,
Specification, Configuration and Instantiation

Source:https://www.zachman.com/about-the-zachman-framework
 Why How What Who Where When

Organizational Geographical
Contextual Goal List Process List Material List Unit & Role List Locations List
Event List

Organizational
Entity
Goal Process Unit & Role Location
Conceptual Relationship
Relationship
Event Model
Relationship Model Model Model
Model

Role
Rules Process Data Model Location Event
Logical Relationship
Diagram Diagram Diagram Diagram Diagram Diagram

Process
Rules Data Entry Role Location Event
Physical Function
Specification Specification Specification Specification Specification Specification

Process Location
Detailed Rules Details Data Details Role Details Event Details
Details Details
Enterprise Engineering
and Enterprise Integration
What is a Enterprise Engineering ?
A body of knowledge, principles, and practices to design all or part of an
enterprise.

Enterprise Engineering is an enterprise life-cycle oriented discipline for the

identification, design, and implementation of enterprises and their continuous
evolution, supported by enterprise modelling - Kosanke, Vernadat and Selm.

A subdiscipline of industrial engineering and systems engineering.

What is a Enterprise Integration ?
A technical field of Enterprise Architecture which focused on the study of
topics such as system interconnection, electronic data interchange, product
data exchange, and distributed computing environments.

A concept in Enterprise Engineering to provides the right information, at the

right place, and at the right time. Enabling communication between people,
machines and computers.
Benefits of Enterprise Integration
● Reducing costs
● Increasing revenue
● Customer satisfaction
● Business process improvement
Levels of Enterprise Integration
● Application integration
● Information integration
● Process-driven integration
Enterprise Integration Applications
● Enterprise Resource Planning Systems (ERP)
● Customer Relationship Management Systems
(CRM)
● Management Information Systems (MIS)
Balanced Scorecard
and Strategy Maps
What is a Balanced Scorecard ?
Basically, a strategic performance management system with three (3)
components:

Strategic goals

Action plan

KPIs or metrics
 ● Financial
Four Perspectives ● Customers
of a Balanced Scorecard ● Internal Processes
● Learning and Growth
What is a Strategy Map ?
A simple graphic that shows a logical, cause-and-effect
connection between strategic objectives.
One of the most powerful elements in the balanced scorecard
methodology, as it is used to quickly communicate how value
is created in the organization.

Source: https://balancedscorecard.org/
Strategy Map
Strategy Map
Why Adopt a Strategy Map?
1. It provides better clarity on strategy
2. It assists in understanding and communicating
organizational strategy
This results in…
3. Better implementation of strategy - adopters perform
better (operationally and financially) than those who
don’t…i.e. they execute!
End of Presentation