Enterprise Architecture

Lecture 1. Basics and key definitions

Introduction to Enterprise Architecture
Let’s consider a reorganizational project of a manufacturing enterprise:
 Starting point is technological processes;
 Next - Reengineering of business processes and redesign of organizational structure;
 Next - Implementing Informational systems and DBMSs;
 What else and how to control complexity?

2
Introduction to Enterprise Architecture
What complexity is actually about:
 Fundamental organization of a system;
 Organizational components;
 Internal and external relationships;
 Basic principles to guide the design.

3
Business-IT alignment as
Internal factor

External
Business
IT Strategy
Strategy

Strategic Fit

Organizational
Internal

IT infrastructure
Infrastructure
And processes
and processes

Business Information Technology

Functional Integration 4
Regulatory framework as External factor
The regulatory framework increasingly demands that companies and governmental institutions can prove
that they have a clear insight into their operations and that they comply with the applicable laws on, for
example, financial transactions.

5
EA evolution. First step. Business System Planning
(BSP)
Gaining the Preparing for the Defining Business Defining Business
Starting the Study
Commitment Study Processes Data

Determining
Defining Information Analyzing Current Interviewing Defining Findings and
Architecture
Architecture Systems Support Executives Conclusions
Priorities

Reviewing
Developing
Information Resource Reporting Results
recommendations
Management

6
EA evolution. Next steps
Aspect BSP Early EA Modern EA

Time 1960s–1980s 1980s–1990s 1990s–present

Definitive source BSP (1975) Spewak and Hill TOGAF (2011)

(1992)

Domains Organization, processes, data, and Business, data, applications, and Business, data, applications, and
information systems technology technology

Modeling Relationship matrices, information Lists, relationship matrices, and Catalogs, matrices, and diagrams
systems networks, and flowcharts diagrams

Methodology Describe current and desired states, Describe current and future states, Describe baseline and target states,
prepare an action plan, and prepare an implementation plan, and prepare a transition plan, implement
implement it implement it the plan, and repeat the process

Difference from the N/A Pays more attention to technical Iterative in nature
predecessor aspects

7
 What are the standards behind?
 John A. Zachman is an American business and IT consultant, early pioneer of
enterprise architecture and originator of the Zachman Framework.
Zachman’s first article  TAFIM - Technical Architecture Framework for Information Management a
TAFIM released reference model for enterprise architecture by and for the United States
Department of Defense.
Clinger-Cohen Act passed  Clinger-Cohen Act - the Information Technology Management Reform Act is a
TAFIM retired United States federal law, designed to improve the way the federal government
acquires, uses and disposes IT.
FEAF 1.2 released
 FEAF - a federal enterprise architecture framework is the U.S. reference
FEA replaces FEAF enterprise architecture of a federal government.
TOGAF EE 8.0 released
 FEA - the enterprise architecture of the Federal government of the United States,
FEA mostly complete the U.S. "Federal Enterprise Architecture“.
TOGAF 9.1  TOGAF - the Open Group Architecture Framework is a framework for enterprise
architecture that provides an approach for designing, planning, implementing, and
governing an enterprise information technology architecture.
1987 1994 1996 1998 1999 2002 2003 2003 2011

8
What is the key difference
(Zachman vs Togaf)?
Framework Description What it does When to use

TOGAF Leading EA development tool for step-by- Creates an outline for rapid and iterative As a guide for clear-cut architecture
step architecture implementation architecture development implementation and governance

Zachman Set of management rules presented in a Defines relationships between different To describe independent element without
form of a 36-cell table perspectives and rules losing the holistic view of a system

9
Zachman framework
Data Function (How?) Network (Where?) People (Who?) Time Motivation (Why?)
(What?) (When?)

Objectives / Scope List of things important List of processes the List of locations where List of organizational List of business events / List of business goals /
to the business business performs the business operates units cycles strategies

Business Model Entity relationship Business process model Logistics network (nodes Organization chart, with Business master Business plan
diagram (Semantic (physical data flow and links) roles; skill sets; security schedule
model) diagram) issues.

Information System Physical Data model Essential Data flow Distributed system Human interface Dependency Business rule model
Model diagram; application architecture architecture diagram(processing
architecture structure)

Technology Model Data architecture; map System design: structure System architecture User interface; security "Control flow" diagram Business rule design
to legacy data chart, pseudo-code (hardware, software design (control structure)
types)

Detailed Data design, physical Detailed Program Design Network architecture Screens, security Timing definitions Rule specification in
Representation storage design architecture program logic

Function System Converted data Executable programs Communications Trained people Business events Enforced rules
facilities

10
TOGAF standard

11
Definitions to know
 Enterprise – the highest level (typically) of description of an organization and typically covers all missions and functions. An enterprise will often span
multiple organizations.
 Architecture - the fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the pri nciples of its
design and evolution.
 Architecture Framework - a conceptual structure used to plan, develop, implement, govern, and sustain an architecture.
 Architecture Model - a representation of a subject of interest.
 Information Technology (IT) - the lifecycle management of information and related technology used by an organization.
 Modelling – a technique through construction of models which enables a subject to be represented in a form that enables
reasoning, insight, and clarity concerning the essence of the subject matter.
 Baseline Architecture - is the “as is” or “current” architecture; includes architecture assets from all architecture domains.
 Target Architecture – architecture, which provides the details of a future state of an architecture being developed for an organization.
 TAFIM - Technical Architecture Framework for Information Management a reference model for enterprise architecture by and for the United States
Department of Defense.

12
References
 De Haes, S., & Van Grembergen, W. (2015). Enterprise Governance of IT, Alignment and Value. In Enterprise Governance of
Information Technology (pp. 1-10). Springer, Cham.
 Albert L. Lederer. Joseph M. Katz Graduate School of. Business. University of Pittsburgh. Pittsburgh, PA 15260 . (IBM, 1975;
Lederer and Putnam, 1986)
 Marc Lankhorst (2013) Enterprise Architecture at Work: Modelling, Communication and Analysis p. 23
 Business Systems Planning and Business Information Control Study: A comparisment. In: IBM Systems Journal, vol 21, no 3,
1982. p. 31-53.
 Sowa, J.F. & J.A. Zachman, 1992, and Inmon, W.H, J.A. Zachman, & J.G. Geiger, 1997. University of Omaha
 The TOGAF® Standard, Version 9.2 Overview (1995-2019) Retrieved from: https://www.opengroup.org/togaf

12
Thank you for your attention!