Scribd
Upload
59 views2 pages

Enterprise Architecture Concepts

Enterprise architecture is the craft of creating a master plan or blueprint of an enterprise. Historically, IT initiatives were tactical and led to cluttered systems with spaghetti relationships and redundancies. This resulted in "hairball architectures". Enterprise architecture emerged as a mechanism to handle the complexity of IT implementations and now focuses on architecting the whole enterprise rather than just IT components. Key developments included early work at IBM in the 1960s, the US Department of Defense coining the term "Technological Architecture Framework for Information Management" in the 1980s, and the National Institute of Standards and Technology first publishing an enterprise architecture model in 1989.

Uploaded by

Dannver Jay Lagramada
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
59 views2 pages

Enterprise Architecture Concepts

Enterprise architecture is the craft of creating a master plan or blueprint of an enterprise. Historically, IT initiatives were tactical and led to cluttered systems with spaghetti relationships and redundancies. This resulted in "hairball architectures". Enterprise architecture emerged as a mechanism to handle the complexity of IT implementations and now focuses on architecting the whole enterprise rather than just IT components. Key developments included early work at IBM in the 1960s, the US Department of Defense coining the term "Technological Architecture Framework for Information Management" in the 1980s, and the National Institute of Standards and Technology first publishing an enterprise architecture model in 1989.

Uploaded by

Dannver Jay Lagramada
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

`ENTERPRISE ▪ Technical or solutions architect (Focus on IT

implementation)
• Single organization, business unit
• Collection of organizations collaboration in ▪ Project/ program manager (Program Manager:
long term, strategic planning, Project Manager:
value stream
Short term, Tactic Planning- small, specific
• It covers a broad spectrum of organizational action to finish the project)
entities ▪ Enterprise architect
ARCHITECT
HISTORICAL PERSPECTIVE
Root word: Architect

French: Architecté EA FACETS


o EA limited to enterprise IT architecture
Greek: Arkhitekton o EA is enterprise-wide solutions
architecture
Archi/Arkhi – chief | Tekton – builder o EA as a tool for business IT alignment
o EA as a discipline for architecting
= “Master Builder” business capabilities and functions

• Architecture is a master of builders


• Architecture is a crafts of master builder HISTORICAL VIEW

ENTERPRISE ARCHITECTURE - It initiatives and spending have been historically


tactical and operationally directed at solving an
- Craft of creating a master plan or blueprint of immediate problem
an enterprise - This attitude to It systems resulted in a clutter
Modern Definition: Well defined approach to align of technology implementations:
business goals and IT infrastructure o Spaghetti relationships
o High level of redundancies
o System cross purpose with each other
ENTERPRISES ARE COMPLEX ADAPTIVE SYSTEM Result: HAIRBALL ARCHITECTURE
• Architects are engaged usually when the
enterprise is already functional.
1960s – Early work by Duane P. Walker (IBM)
(Implement ng Architecture method)
WHY DO WE NEED EA?
1970s & early 1980s- Further developed by IBM BSP
THEN (Business System Planning)
• It emerged as a mechanism to handle the ▪ Dewey – resigned in IBM – he developed a
complexity of IT system implementations. methodology called BSP (Business System
Planning)
NOW
1987- John Zackman –published a book “A framework
• The role of EA transformed to address the
for IS architecture and TAFIM”
architecture of the whole enterprise rather than
just the IT components ▪ Department of Defense (DOD) Invented TAFIM
(Technological Architecture Framework for
Information Management)– introduced by DISA
CAREER PATH
(Defense Information System Agency)
▪ Developer, system administrator, system or 1989- NIST (National Institute of Standard and
business analyst
Technology) publishes EA model the 1st time.
Late 1980s – Roger Evernden – came from Westpac, he
introduces the Information framework (IFW)– initiate
Westpac CS90 – Core System

▪ Westpac CS90 prototype for enterprise


architecture

1996- Clinger-Cohen Act (men behind: Congressman


William Clinger and Senator William Cohen)

• Clinger-Cohen Act compose of 2 Act


o Information Technology Management
Reform Act
o Federal Acquisition Reform Act

2006- Jeanne Ross publishes her work for EA.

Vinton G. Cerf “Vint Cerf” - Father of the internet

ABBREVIATIONS

EA – Enterprise Architecture

IBM – International Business Machines Corporation

BSP – Business System Planning

TAFIM - Technological Architecture Framework for


Information Management

DOD – Department of Defense

DISA - Defense Information System Agency

NIST - National Institute of Standard and Technology

IFW - Information framework

You might also like