A Comparative Survey of

Enterprise Architecture
Frameworks

Jaap Schekkerman, B.Sc.

President of the Institute For Enterprise Architecture

Developments (IFEAD)

Thought Leader Business Technology Strategy &

Enterprise Architecture, Capgemini

Http://www.enterprise-architecture.info
© 2004, Institute For Enterprise Architecture Developments / Capgemini - All Rights Reserved
Page 1
Agenda

• About the speaker

• EA Survey 2003 Results – EA Framework Usage
• EA Frameworks Comparison
• Conclusion

Http://www.enterprise-architecture.info
© 2004, Institute For Enterprise Architecture Developments / Capgemini - All Rights Reserved
Page 2
 Speaker Qualifications - Jaap Schekkerman

Author / Co-Author of several Architecture books & publications

• Founder & President of the Institute For Enterprise Architecture Developments, The Netherlands.

• Thought Leader Business Technology Strategy & Enterprise Architecture, Capgemini, The Netherlands.

• Professional Associations:
– Advisory board member of the Federal Enterprise Architecture Certification Institute, USA.
– Co-Founder & Alliance member of the Global Enterprise Architecture Organisation, New Zealand.
– Member of the 'MANYWORLDS' knowledge network of Business Thought Leaders, USA.
– Member of the IEEE 1471 (Recommended Practice for Architectural Description) working group, USA.
– Member of the World Wide Institute of Software Architects (WWISA), USA.
– Member of the Netherlands Society of Information Architects (GIA), NL.
– Member of the SWEBOK (Software Engineering Body of Knowledge) working group of the University of Québec, Montréal.

For more info about my books & publications, visit: http://www.enterprise-architecture.info

Http://www.enterprise-architecture.info
© 2004, Institute For Enterprise Architecture Developments / Capgemini - All Rights Reserved
Page 3
Combining EA Research & Best Practices

Be s
Pra Be s t
c Pra ct ice
s

Http://www.enterprise-architecture.info
© 2004, Institute For Enterprise Architecture Developments / Capgemini - All Rights Reserved
Page 4
Survey Question: What kind of EA Frameworks are you using?

All Industries / Governments

Zachman Framework FEAF, US Federal
Other 18% Enterprise Architecture
Organization own 6%
Framework
32% TOGAF, the Open Group
6%
Architecture Framework
9%
All Others except the Financial & Insurance Industry
IAF, Cap Gemini Ernst &
Zachman Framework FEAF, US Young's
Federal - Integrated
CIMOSA (Computer 19%
Integrated Manufacturing None Enterprise Architecture TOGAF, the Open Group
Architecture Framework
Organization own Other Framework
Open Systems 4% 7% Architecture Framework
22% 7% 4% 7%
Architecture) framework
6%
Financial & Insurance Industry C4ISR, US Defense
IAF, Cap Gemini Ernst &
Architecture Framework
Young's - Integrated
PERA (Purdue CIMOSA (Computer ISO/IEC 14252 (IEEE 6% Architecture Framework
TEAF, US Treasury
EnterpriseIntegrated
ReferenceManufacturing Std 1003.0) Guide to the
Zachman 7%
Enterprise Architecture
Architecture) Framework Open Systems Framework. POSIX Open System
Framework
3%Architecture) framework 4% 17% Environment C4ISR, US Defense
Source: EA Survey 2003, © Copyright: IFEAD
7% 3% Architecture Framework
7%
PERA (Purdue
Enterprise Reference TAFIM, US Defense ISO/IEC 14252 (IEEE
Organization own Architecture) Framework TEAF, US Treasury Technical Architecture Std 1003.0) Guide to the
83% 4% Enterprise Architecture Framework for POSIX Open System
Framework. Information Management Environment
Source: EA Survey 2003, © Copyright: IFEAD
4% 4% 4%
Source: EA Survey 2003, © Copyright: IFEAD

Http://www.enterprise-architecture.info
© 2004, Institute For Enterprise Architecture Developments / Capgemini - All Rights Reserved
Page 5
Enterprise Architecture Frameworks & the Holistic Perspective

Trends
•Holistic Architecture: By 2006, 20% of Global 2000
organizations will integrate holistic enterprise architecture,
enterprise program management, enterprise strategy/planning,
and IT portfolio management into a common set of IT
management processes under the auspices of the CIO’s office.
Ten percent will operate these integrated management
disciplines outside the IT organization.

•Value of Integrated Architecture: By 2007, 50% of Global

2000 enterprises will move beyond a pure technology
architecture focus to include enterprise business architecture,
enterprise information architecture, and enterprise solution
architecture. Architecture teams that fail to move beyond the
technical focus will come under increasing pressure to
demonstrate business value.

Source: META GROUP RESEARCH ~ EA TRENDS 2004 – 2005.

So, EA Frameworks has to support the

holistic perspective……… and more..

Http://www.enterprise-architecture.info
© 2004, Institute For Enterprise Architecture Developments / Capgemini - All Rights Reserved
Page 6
Enterprise Architecture Frameworks History

references DoD AF
JTA
2003

references
ISO/IEC CIMOSA
Supported by
14252 C4ISR
DoD TRM references
influenced 1999
influenced PERA
supported by influenced
TOGAF TOGAF
TAFIM adopted by 1995 influenced 2002
SAGA
influenced
Zachman Zachman
1987 2003
TEAF
influenced influenced 2000

EAP FEAF FEAF

influenced
1992 1999 2003
influenced
influenced supported by

influenced
TISAF influenced
E2AF
1997 2003
influenced

UVA Model IAF v1 IAF v3 EE XAF

influenced
1994 1996 2001 2003
influenced

1985 1990 1995 2000 2005

Http://www.enterprise-architecture.info
© 2004, Institute For Enterprise Architecture Developments / Capgemini - All Rights Reserved
Page 7
 Enterprise Architecture Framework (Zachman)

Characteristics:
• Positioning Framework
• Categorizing Deliverables
• Limited usefulness EA
• History in Manufacturing
• Broad Acceptance
• Limited Holistic Perspect.
• Planning Tool

Http://www.enterprise-architecture.info
© 2004, Institute For Enterprise Architecture Developments / Capgemini - All Rights Reserved
Page 8
Integrated Architecture Framework (Capgemini)
Aspect Areas

Business Information Information-

Information- Technology-
Technology-
Systems Infrastructure
Abstraction Levels
Business Goals, Drivers and Concepts Activities the Business Performs Systems Goals, Drivers and Concepts Technology Goals, Drivers and Concepts
Why? • Corporate Strategic Plans • Information Policy • System Development policy • Locations in which the Business Operates
• Responsibilities & Competencies
Vision / Strategy • Business Drivers
• Confidentiality of Information
• Integration Policy • Technology Infrastructure policy
• Guiding Principles • Business - Technology Enablers • Business - Technology Enablers
Business / Technology • Scope of the Change
• Dependencies of others
• Responsibility of IS • Responsibility of TI
Drivers • Activities in Scope

Characteristics:
• Environmental Dynamics, e.g. Laws • Application portfolio • TI Portfolio

Scope • Business Goals & Objectives, KPI’s

Activities = Generic or Specific • Guiding Principles • Guiding Principles
Viewpoints = Competition, Value Net, etc.
Contextual Level Ends/Means = As-Is / To-Be Business Situation
Activities = Critical / Overhead
End = Information Situation End = To-Be Information-System Situation Node = Major Business Location

• Positioning Framework Level of Business Collaboration Level of Information Interaction Level of Interoperability Level of Inter-Connection
What?
• History in Enterprise
• Project Goals & Objectives • As-Is Information Systems Environment • As-Is Infrastructure
• Functional Requirements
• Business Requirements • Non-Functional Requirements • Functional Requirements • TI Principles
• Functional Requirements
Goals & Objectives • Business Relationships • Quality of Services • Non-Functional Requirements
• Non-Functional Requirements

Planning
• Budget of Change • Information Relations
• Information-Systems Behaviour
Requirements • Stakeholders / Win-Win Conditions • Information Characteristics
• Abstraction & Precision of Data
• Quality of Services
• Quality of Services Characteristics = Time, Availability, Security,
Policy = Business Purpose • Quality of Services
Characteristics = Time, Flexibility, Availability, Maintainability, etc.

• Separation of Concerns
Domains = Functional Areas Characteristics = Time, Availability, Security,
Security, Maintainability, etc.
Conceptual Level End = Business Purpose
I/O = Business Resources
End = Information Resources
Maintainability, etc.
Structure = Interfaces
Link = Business System Connection
Node = Business System Environment

• Categorizing Aspects How?

Type of Business Collaboration
• Organisation Structure
Type of Information Interaction
• Information Processes
Type of Interoperability
• MDA Platform-Independent Modelling (PIM)
• Business functionality and behavior
Type of Inter-Connection
• Technology Standards

• Limited Acceptance
• Business Area Structure • Information Objects & Relations • Infrastructure Profile
• Information Interaction • Many Middleware Technologies
• Role Players / Actors
Logical Representation • Value Net Position • Information Flow Characteristics • Shared & Pluggable Services
• Hardware Systems Profile
• Communication Profile
• Business Culture • Information Resources Standards = MDA Development

• Proprietary
Standards • Security Profile
• Business Commitment • Information Locations
• Governance Profile
• Business Rules
Entities = Classes, Attributes &

Logical Level Viewpoint = Business Perspective Viewpoint = Human Perspective Associations Positioning = Allocation of Services

• Holistic Perspective.
End = Business Behaviour End = Information Behaviour End = PIM Interaction = Concepts of Layering

Solutions of Business Collaboration Solutions of Information Interaction Solutions for Interoperability Solutions of Inter-Connection

• Communication Tool With what? • Business Functions structure and relations

• Business Tasks / Activities
• Type of Information Exchange
•Formal / Informal
• Grouping of Information Objects
• MDA Platform-Specific Modelling (PSM)
• Map PSM to application interfaces, code, GUI
descriptors, SQL queries, etc.
• Technology Overview
• Solutions & Products for Inter-Connection

Solution Representation • Business Objects • Grouping of Information Resources

Viewpoints = Characteristics of a View
• Formats of Communication
• Security Integration
• Business Resources • Type of Triggers / Events
Node = Hardware + System
• Business Knowledge • Grouping of Information
Software, etc.
• Business Benefits Types
Connectivity = Middleware /
Priority = Dependency of Information Structure = Spectrum of Styles Messaging, etc.
• Technology Possibilities
Physical Level End = Business Outcome
Relation = Information Flow
End = Information Outcome
Quality = Component Characteristics
End = PSM
End = Structure of Relations,
Products + Specifications

Granularity of Change Impact of Change Timeframe of Change Timeframe of Change

When? • Business Case • Business Case • Business Case • Business Case
• Transformation Roadmap • Information Systems Roadmap • Make or Buy Decision • Transformation Plan
• Priority Setting
Organisational Impact • Priority Plan
• Budget Plan
• Security Plan • Implementation Roadmap
• Tools for Development / Implementation • IS Alignment Impact
• Governance Plan Selection = Set of ICT Supported Objects • Governance Plan
• Security Impact e.g. Blue Print of Technology Implementation
e.g. Business Process Redesign or Outsourcing e.g. Information Roadmap e.g. Design of Application & Components Portfolio of Products and Components.
Interface = Type of Information Exchange
Transformational Level End = Business Transformation End = Activities to be supported by ICT
Priority = Dependencies
End = Roadmap for realization
Catalogues of used Standards
End = Roadmap for implementation

Security / Governance
Architecture ViewPoints

Http://www.enterprise-architecture.info
© 2004, Institute For Enterprise Architecture Developments / Capgemini - All Rights Reserved
Page 9
NATO Architecture Framework / C4ISR / DoDAF

Business Node Information Flow

Business
Organization Model Node
Connectivity Model InformationDiagram
Flow
Organization Model Connectivity Model Diagram

Systems
Systems Systems
Systems System
System PhysicalPhysical
Conceptual
ConceptualModel
Model Logical
LogicalModel
Model Model Model

Software Implementation
SoftwareModel
Component Integration Model Implementation
Model
Component Model Integration Model Model

Characteristics:
• Positioning Framework
• History in Defence
• Broad Defence Acceptance
• Neutral
• Limited Holistic Perspective.
• Process / Planning Tool

Http://www.enterprise-architecture.info
© 2004, Institute For Enterprise Architecture Developments / Capgemini - All Rights Reserved
Page 10
Extended Enterprise Architecture Framework (IFEAD)
Abstraction Levels
Why?
Vision / Strategy
Business / Technology
Drivers
Scope
Aspect Areas Contextual Level
Business Goals, Drivers and Concepts
• Corporate Strategic Plans
• Extended Business Drivers
• Extended Guiding Principles
Business • Scope of Collaboration
• Environmental Dynamics, e.g. Laws
• Business Goals & Objectives, KPI’s
Viewpoints = Competition, Value Net, etc.
Ends/Means = As-Is / To-Be Business Situation
Activities the Business Performs
• Enterprise Information Policy
• Responsibilities & Competencies
• Ownership of Information
Information
• Internal / External Dependencies
• Internal / External Activities in Scope
Activities = Generic or Specific
Activities = Critical / Overhead
End = Information Situation
Systems Goals, Drivers and Concepts
• System Development policy
• Enterprise Interoperability Policy
Information –
• Business - Technology Enablers
• Enterprise Responsibility of IS
Systems
• Enterprise Application portfolio
• Enterprise Guiding Principles
End = As-Is / To-Be Information-System
landscape
Technology Goals, Drivers and Concepts
• Locations in which the Business Operates
• Enterprise Technology Infrastructure policy
Technology - • Enterprise Business - Technology Enablers
Infrastructure
• Enterprise Responsibility of TI
• Enterprise TI Portfolio
• Enterprise Guiding Principles
Node = Major Enterprise Business Location
With Who?
Value Net Relations
Cooperating /
Collaborating Elements
Environmental Level
Extended Enterprise Value Net
• Collaborative Value Parties
• Scope of the Collaborative value
• Collaboration Contracts, Service Levels
• Law & Regulations
• Collaborative Business Goals & Objectives
Viewpoint = Collaborative Value, etc.
Ends/Means = As-Is / To-Be Collaborative
Environment
Extended Enterprise Information Exchange
• Extended Information Exchange Services
• Extended Information Ownership
• Parties Information Confidentiality
• Extended Dependencies
• Activities out of Scope
Information = Generic or Specific
Information = Critical / Overhead
End = Ext. Enterprise Information Exchange
Extended Enterprise Interoperability
• Enterprise Interoperability Standards
• Enterprise Interoperability Governance
• Enterprise Interoperability Quality of
Services (e.g. Security)
• Enterprise Interface portfolio
• Enterprise Collaboration Principles
End = To-Be Interoperability Definitions
Extended Enterprise Inter-Connection
• Enterprise Inter-Connection Standards
• Enterprise Inter-Connection Governance
• Enterprise Inter-Connection Quality
of Services (e.g. Security)
• Enterprise Inter-Connection portfolio
• Enterprise Inter-Connection Principles
End = To-Be Inter-Connection Definitions
Http://www.enterprise-architecture.info
© 2004, Institute For Enterprise Architecture Developments / Capgemini - All Rights Reserved
What? How? With what? When?
Goals & Objectives
Logical Representation Solution Enterprise Impact
Requirements
Representation
Conceptual Level Logical Level Physical Level Transformational Level
Level of Business Collaboration Type of Business Collaboration Solutions of Business Collaboration Granularity of Change
• Program Goals & Objectives • Organisation Structure • Business Functions structure and relations • Enterprise Business Case
• Business Requirements • Business Area Structure • Business Tasks / Activities • Enterprise Transformation Roadmap
• Business Relationships • Role Players / Actors • Business Objects • Enterprise Priority Plan
• Budget of Change
• Stakeholders / Win-Win Conditions
• Value Net Position
• Business Culture
• Business Resources
• Business Knowledge
• Enterprise Budget Plan
• Enterprise Governance Plan
• Quality of Services • Business Commitment
• Business Benefits e.g. Business Process Redesign or Outsourcing
Characteristics = Time, Flexibility, • Business Rules
• Technology Possibilities
Availability, Security, Maintainability, etc. Viewpoint = Business Perspective
End = Business Purpose End = Business Behaviour End = Business Outcome / Business Solutions End = Enterprise Business Transformation
Level of Information Interaction Type of Information Interaction Solutions of Information Interaction Impact of Change
• Information Tasks / Activities • Type of Information Exchange • Business Case
• Functional Requirements
•Formal / Informal • Information Systems Roadmap
• Non-Functional Requirements • Information Objects & Relations
• Grouping of Information Objects
• Quality of Services • Information Interaction • Security Plan
• Grouping of Information Resources
• Information Relations • Information Flow Characteristics
• Type of Triggers / Events
• Information Characteristics • Information Resources Selection = Set of ICT Supported Objects
• Grouping of
• Information Locations Information Types
Policy = Business Purpose e.g. Information Roadmap
Domains = Functional Areas Priority = Dependency of Information
I/O = Business Resources Viewpoint = Interaction Perspective Relation = Information Flow Interface = Type of Information Exchange
End = Information Resources End = Information Behaviour End = Information Solutions Sets End = Activities to be supported by ICT
Level of Interoperability Type of Interoperability Solutions for Interoperability Timeframe of Change
• As-Is Information Systems Environment • Product-Independent Reference Solution • Product-Specific Reference Solution (PSRS) • Business Case
(PIRS) • Map PSRM to Product Solutions and • Make or Buy Decision
• Functional Requirements
Characteristics:
• IS Functions & behaviour
options, etc.
• Non-Functional Requirements • Implementation Roadmap
• Choice of Middleware Technologies • Interface Solutions
• Tools for Development / Implementation
• Information-Systems Behaviour • Implementation of Quality of Services
• Shared & Pluggable IS Services / Solution sets • Governance Plan
• Refinement Technical Reference Model
• Abstraction & Precision of Data
• Positioning Framework
• Interface Definitions & Standards • Security Impact
• Quality of Services Viewpoints = Selection of a Product Solutions
• Official & De-facto IS Standards e.g. Design of Application & Components
Characteristics = Time, Availability, Structure = Spectrum of Styles & Solutions sets
Security, Maintainability, etc. Standards = IS Interoperability Standards Quality = Solution Interface Characteristics Priority = Dependencies
• History in (Extended) Enterprise
Structure = Interfaces End = PIRS End = PSRS End = Roadmap for realization
Frameworks
Level of Inter-Connection Type of Inter-Connection Solutions of Inter-Connection Timeframe of Change
• As-Is Enterprise Infrastructure • Enterprise Technology Standards • Technology Overview • Business Case
• TI Principles • Enterprise Infrastructure Profile • Solutions & Products for Inter-Connection • Enterprise Transformation Plan
• Functional Requirements
• Non-Functional Requirements
• Enterprise Hardware Systems Profile
• Enterprise Communication Profile • Focusing on Collaboration
• Formats of Communication
• Security Integration
• Enterprise Priority Setting
• Enterprise IS Alignment Impact
• Quality of Services • Enterprise Security Profile • Refinement Technical Reference Model
• Separation of Concerns
e.g. Blue Print of Technology Implementation
Characteristics = Time, Availability, Security, • Enterprise Governance Profile Node = Hardware + System Software, etc.
Maintainability, etc.
• Technical Reference Model & Standards Connectivity = Middleware / Messaging, etc. Portfolio of Products and Components.
Link = Enterprise Business System Connection Positioning = Allocation of IT Services ~ TRM End = Structure of Relations, Products + Catalogues of used Standards
• Broad Acceptance
Node = Enterprise Business System Environm. Interaction = Concepts of Service Layering Specifications End = Roadmap for Enterprise Implementation
• Neutral / Open
• Complete Holistic Perspective.
• Communication Tool
Page 11
Computer Integrated Manufacturing Open Systems Architecture
(CIMOSA)

Enterprise

Activity Structure

•Information •Function •Rules

•Constraints •Material •Organisation
•Resource

User
Input
Function Information resource Organisation Enterprise
CM-OSA Reference System
Architecture Requirements Requirements

Enterprise
Generic Building Blocks Function Information resource Organisation
System
CIMOSA Constraints
Design

Characteristics:
Partial Models Function Information resource Organisation
• Process Framework Component
Catalogue
• History in Manufacturing Implementation

• Focusing on Views
• Definition of Models
• Limited Acceptance System
Components
• European Initiative
• Limited Holistic Perspective
• Process Planning Tool

Http://www.enterprise-architecture.info
© 2004, Institute For Enterprise Architecture Developments / Capgemini - All Rights Reserved
Page 12
The Open Group Architecture Framework (TOGAF v8.x) Enterprise Edition

Characteristics:
• Enterprise Architecture
Development Methodology
• History in Defence
• Open Standard
• Neutral
• Broad Acceptance
• Holistic Perspective.
• Process / Planning Tool

Http://www.enterprise-architecture.info
© 2004, Institute For Enterprise Architecture Developments / Capgemini - All Rights Reserved
Page 13
 US - Federal Enterprise Architecture Framework (FEAF)

Federal
Federal Enterprise
Enterprise Architecture
Architecture (FEA)
(FEA)

Performance Reference Model (PRM)

Business & Performance-Driven Approach

Component-Based Architecture
• Government-wide Performance Measures & Outcomes
• Line of Business-Specific Performance Measures & Outcomes

Business Reference Model (BRM)

• Lines of Business
• Agencies, Customers, Partners

Service Component Reference Model (SRM)

• Service Domains, Service Types, Components
• Access, Delivery Channels

Data Reference Model (DRM)

• Business-focused data standardization
• Cross-Agency Information Exchanges

Technical Reference Model (TRM)

• Technologies, Standards, Specifications
• Component Framework
Characteristics:
• Enterprise Architecture
Reference Framework
• History in Enterprise
Architecture Planning
• US-Gov Standard
• Broad US-Gov Acceptance
• Holistic Perspective.
• Planning &
Communication Tool

Http://www.enterprise-architecture.info
© 2004, Institute For Enterprise Architecture Developments / Capgemini - All Rights Reserved
Page 14
 US - Treasury Enterprise Architecture Framework (TEAF)

How, Where, and When

Functional

What, How Much, and

How Frequently Information

Who and Why Organisational

Enabler Infrastructure

Characteristics:
• Positioning Framework
• History in FEAF
• US-Treasury Standard
• Broad US-Treasury Acceptance
• Limited Holistic Perspective.
• Planning & Communication
Tool

Http://www.enterprise-architecture.info
© 2004, Institute For Enterprise Architecture Developments / Capgemini - All Rights Reserved
Page 15
Conclusion

• Most EA Frameworks have different evolutions

• Most EA Frameworks serve different Purposes

• Most EA Frameworks are different in Scope

• Most EA Frameworks are based on different Principles

• Most EA Frameworks have different Structures

• Most EA Frameworks are supported by different approaches

• Most EA Frameworks are different in compliancy with the

Clinger Cohen Act

ISBN 1-4120-1607-X
So, the Question is: Do You Create or Choose your
Enterprise Architecture Framework

http://www.enterprise-architecture.info or http://www.trafford.com/robots/03-1984.html or at the author

Http://www.enterprise-architecture.info
© 2004, Institute For Enterprise Architecture Developments / Capgemini - All Rights Reserved
Page 16