Transcript A Comparative Survey of Enterprise Architecture Frameworks

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
Pr
a
B
c P es Best
rac P
ract ices
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
Organization own
32%
Other
6%
Zachman Framework
18%
FEAF, US Federal
Enterprise Architecture
Framework
6%
TOGAF, the Open Group
Architecture Framework
9%
All Others except the Financial & Insurance Industry
CIMOSA (Computer
Integrated Manufacturing
Organization own
Open Systems
22%
Architecture) framework
6%
Other
7%
IAF, Cap Gemini Ernst &
Zachman Framework
FEAF, US Young's
Federal - Integrated
19%
Enterprise
Architecture
TOGAF, the Open Group
Architecture Framework
None
Framework
7% Architecture Framework
4%
4%
7%
Financial & Insurance Industry
PERA (Purdue
CIMOSA (Computer
TEAF, US Treasury
EnterpriseIntegrated
ReferenceManufacturing
Enterprise Architecture
Architecture) Framework
Open Systems Framework.
3%
Architecture) framework 4%
Source: EA Survey 2003, © Copyright: IFEAD
7%
ISO/IEC 14252 (IEEE
Std 1003.0) Guide to the
Zachman
POSIX Open System
Framework
Environment
17%
3%
C4ISR, US Defense
IAF, Cap Gemini Ernst &
Architecture Framework
Young's - Integrated
6%
Architecture Framework
7%
PERA (Purdue
Enterprise Reference
TAFIM, US Defense
Organization own
Architecture) Framework TEAF, US Treasury Technical Architecture
83%
Enterprise Architecture
4%
Framework for
Framework.
Information
Management
Source: EA Survey 2003, © Copyright: IFEAD
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
C4ISR, US Defense
Architecture Framework
7%
ISO/IEC 14252 (IEEE
Std 1003.0) Guide to the
POSIX Open System
Environment
4%
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
DoD AF
2003
references
JTA
references
ISO/IEC
14252
influenced
influenced
TAFIM
C4ISR
1999
references
DoD TRM
PERA
supported by
TOGAF
1995
adopted by
influenced
TOGAF
2002
influenced
influenced
Zachman
1987
influenced
influenced
EAP
1992
influenced
UVA Model
1994
IAF v1
1996
influenced
1995
Zachman
2003
influenced
influenced
influenced
IAF v3 EE
2001
influenced
1990
SAGA
FEAF
2003
supported by
TISAF
1997
influenced
TEAF
2000
FEAF
1999
influenced
1985
CIMOSA
Supported by
2000
Http://www.enterprise-architecture.info
© 2004, Institute For Enterprise Architecture Developments / Capgemini - All Rights Reserved
Page 7
E2AF
2003
XAF
2003
2005
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
InformationInformationSystems
TechnologyTechnologyInfrastructure
Systems Goals, Drivers and Concepts
Technology Goals, Drivers and Concepts
Abstraction Levels
Why?
Characteristics:
• Positioning Framework
• History in Enterprise
Planning
• Separation of Concerns
• Categorizing Aspects
• Limited Acceptance
• Proprietary
• Holistic Perspective.
• Communication Tool
Vision / Strategy
Business / Technology
Drivers
Scope
Contextual Level
What?
Goals & Objectives
Requirements
Conceptual Level
How?
Logical Representation
Business Goals, Drivers and Concepts
• Corporate Strategic Plans
• Business Drivers
• Guiding Principles
• Scope of the Change
• Environmental Dynamics, e.g. Laws
• Business Goals & Objectives, KPI’s
Activities the Business Performs
• Information Policy
• System Development policy
• Locations in which the Business Operates
• Responsibilities & Competencies
• Integration Policy
• Technology Infrastructure policy
• Confidentiality of Information
• Dependencies of others
• Activities in Scope
With what?
• Guiding Principles
End = Information Situation
End = To-Be Information-System Situation
Level of Business Collaboration
Level of Information Interaction
Level of Interoperability
• Project Goals & Objectives
• Business Requirements
• Functional Requirements
• Non-Functional Requirements
• Business Relationships
• Quality of Services
• Budget of Change
• Information Relations
• Stakeholders / Win-Win Conditions
• Information Characteristics
• As-Is Information Systems Environment
• Functional Requirements
• Non-Functional Requirements
• Information-Systems Behaviour
• As-Is Infrastructure
• TI Principles
• Functional Requirements
• Non-Functional Requirements
• Quality of Services
End = Business Purpose
Link = Business System Connection
Node = Business System Environment
Type of Business Collaboration
Type of Information Interaction
Type of Interoperability
Type of Inter-Connection
• MDA Platform-Independent Modelling (PIM)
• Business functionality and behavior
• Value Net Position
• Information Processes
• Information Objects & Relations
• Information Interaction
• Information Flow Characteristics
• Business Culture
• Information Resources
• Business Commitment
• Information Locations
Standards = MDA Development
Standards
• Organisation Structure
• Business Area Structure
• Role Players / Actors
• Many Middleware Technologies
• Shared & Pluggable Services
End = Information Behaviour
Solutions of Business Collaboration
Solutions of Information Interaction
Solutions for Interoperability
• Business Functions structure and relations
• Business Objects
Characteristics = Time, Availability, Security,
Maintainability, etc.
• Technology Standards
• Infrastructure Profile
• Hardware Systems Profile
• Communication Profile
• Security Profile
• Governance Profile
Viewpoint = Business Perspective
End = Business Behaviour
Entities = Classes, Attributes &
Associations
End = PIM
Viewpoint = Human Perspective
• Type of Information Exchange
•Formal / Informal
• Grouping of Information Objects
• Grouping of Information Resources
• Type of Triggers / Events
Positioning = Allocation of Services
Interaction = Concepts of Layering
Solutions of Inter-Connection
• MDA Platform-Specific Modelling (PSM)
• Technology Overview
• Map PSM to application interfaces, code, GUI
descriptors, SQL queries, etc.
• Solutions & Products for Inter-Connection
Viewpoints = Characteristics of a View
• Formats of Communication
End = Business Outcome
Priority = Dependency of Information
Relation = Information Flow
End = Information Outcome
Structure = Spectrum of Styles
Quality = Component Characteristics
End = PSM
• Security Integration
Node = Hardware + System
Software, etc.
Connectivity = Middleware /
Messaging, etc.
End = Structure of Relations,
Products + Specifications
Granularity of Change
Impact of Change
Timeframe of Change
Timeframe of Change
• Business Resources
• Grouping of Information
Types
• Business Case
• Business Case
• Business Case
• Business Case
• Transformation Roadmap
• Information Systems Roadmap
• Make or Buy Decision
• Transformation Plan
• Priority Plan
• Security Plan
• Implementation Roadmap
• Priority Setting
• Budget Plan
• Governance Plan
• Tools for Development / Implementation
e.g. Business Process Redesign or Outsourcing
End = Business Transformation
e.g. Information Roadmap
e.g. Design of Application & Components
Interface = Type of Information Exchange
End = Activities to be supported by ICT
Security
• IS Alignment Impact
• Governance Plan
Selection = Set of ICT Supported Objects
• Security Impact
Transformational Level
Level of Inter-Connection
Policy = Business Purpose
Domains = Functional Areas
I/O = Business Resources
End = Information Resources
• Quality of Services
Characteristics = Time, Flexibility, Availability,
Security, Maintainability, etc.
• Technology Possibilities
Organisational Impact
• Guiding Principles
Node = Major Business Location
• Abstraction & Precision of Data
• Quality of Services
Characteristics = Time, Availability, Security,
Maintainability, etc.
Structure = Interfaces
• Business Benefits
When?
• TI Portfolio
Activities = Generic or Specific
Activities = Critical / Overhead
• Business Knowledge
Physical Level
• Responsibility of TI
• Application portfolio
Viewpoints = Competition, Value Net, etc.
• Business Tasks / Activities
Solution Representation
• Business - Technology Enablers
• Responsibility of IS
Ends/Means = As-Is / To-Be Business Situation
• Business Rules
Logical Level
• Business - Technology Enablers
Priority = Dependencies
End = Roadmap for realization
/
e.g. Blue Print of Technology Implementation
Portfolio of Products and Components.
Catalogues of used Standards
End = Roadmap for implementation
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
Business
Organization
Model
Organization Model
Systems
Systems
ConceptualModel
Model
Conceptual
Software
SoftwareModel
Component
Component Model
Information Flow
Node
Flow
Node
Connectivity
Model InformationDiagram
Connectivity Model
Systems
Systems
Logical
Model
Logical
Model
Integration Model
Diagram
System
System
PhysicalPhysical
Model Model
Implementation
Implementation
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
Aspect Areas
Why?
Value Net Relations
Cooperating /
Collaborating Elements
Contextual Level
Environmental Level
Business Goals, Drivers and Concepts
Business
Conceptual Level
Level of Business Collaboration
• Enterprise Priority Plan
• Stakeholders / Win-Win Conditions
• Business Culture
• Quality of Services
Characteristics = Time, Flexibility,
Availability, Security, Maintainability, etc.
• Business Commitment
• Collaborative Business Goals & Objectives
• Business Resources
• Business Knowledge
• Business Benefits
• Business Rules
• Technology Possibilities
End = Business Outcome / Business Solutions
End = Enterprise Business Transformation
Level of Information Interaction
Type of Information Interaction
Solutions of Information Interaction
Impact of Change
• Extended Information Exchange Services
• Extended Information Ownership
• Ownership of Information
• Parties Information Confidentiality
• Internal / External Dependencies
• Extended Dependencies
• Quality of Services
• Information Relations
• Internal / External Activities in Scope
• Activities out of Scope
• Information Characteristics
• Functional Requirements
• Non-Functional Requirements
• Information Tasks / Activities
• Information Objects & Relations
• Information Interaction
• Information Flow Characteristics
• Information Resources
• Information Locations
• Grouping of Information Resources
• Type of Triggers / Events
• Grouping of
Information Types
• Business Case
• Information Systems Roadmap
• Security Plan
Selection = Set of ICT Supported Objects
End = Ext. Enterprise Information Exchange
Viewpoint = Interaction Perspective
End = Information Behaviour
Priority = Dependency of Information
Relation = Information Flow
End = Information Solutions Sets
Interface = Type of Information Exchange
End = Activities to be supported by ICT
Extended Enterprise Interoperability
Level of Interoperability
Type of Interoperability
Solutions for Interoperability
Timeframe of Change
• Product-Independent Reference Solution
(PIRS)
• IS Functions & behaviour
Standards = IS Interoperability Standards
End = PIRS
• Product-Specific Reference Solution (PSRS)
• Map PSRM to Product Solutions and
options, etc.
• Interface Solutions
• Implementation of Quality of Services
• Refinement Technical Reference Model
Viewpoints = Selection of a Product Solutions
Structure = Spectrum of Styles & Solutions sets
Quality = Solution Interface Characteristics
End = PSRS
Priority = Dependencies
End = Roadmap for realization
Type of Inter-Connection
Solutions of Inter-Connection
Timeframe of Change
Information = Generic or Specific
End = Information Situation
Systems Goals, Drivers and Concepts
Information = Critical / Overhead
• System Development policy
• Enterprise Interoperability Standards
• As-Is Information Systems Environment
• Enterprise Interoperability Policy
• Enterprise Interoperability Governance
• Functional Requirements
• Business - Technology Enablers
• Enterprise Interoperability Quality of
Services (e.g. Security)
• Non-Functional Requirements
• Choice of Middleware Technologies
• Information-Systems Behaviour
• Shared & Pluggable IS Services / Solution sets
• Enterprise Interface portfolio
End = To-Be Interoperability Definitions
• Abstraction & Precision of Data
• Quality of Services
Characteristics = Time, Availability,
Security, Maintainability, etc.
Structure = Interfaces
Technology Goals, Drivers and Concepts
Extended Enterprise Inter-Connection
Level of Inter-Connection
• Locations in which the Business Operates
• Enterprise Inter-Connection Standards
• Enterprise Technology Infrastructure policy
• Enterprise Inter-Connection Governance
• Enterprise TI Portfolio
• Type of Information Exchange
•Formal / Informal
• Grouping of Information Objects
Policy = Business Purpose
Domains = Functional Areas
I/O = Business Resources
End = Information Resources
Activities = Generic or Specific
Activities = Critical / Overhead
• Enterprise Business - Technology Enablers
• Enterprise Governance Plan
Viewpoint = Business Perspective
End = Business Behaviour
• Responsibilities & Competencies
• Enterprise Responsibility of TI
• Enterprise Budget Plan
e.g. Business Process Redesign or Outsourcing
End = Business Purpose
• Enterprise Information Policy
• Enterprise Guiding Principles
Granularity of Change
• Enterprise Transformation Roadmap
• Environmental Dynamics, e.g. Laws
• Enterprise Application portfolio
Solutions of Business Collaboration
• Budget of Change
• Scope of Collaboration
• Enterprise Responsibility of IS
Transformational Level
• Enterprise Business Case
• Law & Regulations
Extended Enterprise Information Exchange
Physical Level
• Business Objects
• Business Relationships
Ends/Means = As-Is / To-Be Collaborative
Environment
Type of Business Collaboration
Enterprise Impact
• Business Tasks / Activities
• Collaboration Contracts, Service Levels
Viewpoints = Competition, Value Net, etc.
Logical Level
Solution
Representation
• Business Functions structure and relations
• Extended Guiding Principles
Viewpoint = Collaborative Value, etc.
Logical Representation
When?
• Business Area Structure
• Role Players / Actors
• Value Net Position
• Program Goals & Objectives
• Business Requirements
• Business Goals & Objectives, KPI’s
With what?
How?
• Organisation Structure
• Collaborative Value Parties
• Scope of the Collaborative value
End = As-Is / To-Be Information-System
landscape
Technology Infrastructure
Goals & Objectives
Requirements
• Extended Business Drivers
Activities the Business Performs
Information –
Systems
Extended Enterprise Value Net
What?
• Corporate Strategic Plans
Ends/Means = As-Is / To-Be Business Situation
Information
With Who?
Vision / Strategy
Business / Technology
Drivers
Scope
• Enterprise Collaboration Principles
• Enterprise Inter-Connection Quality
of Services (e.g. Security)
• Enterprise Inter-Connection portfolio
• Enterprise Guiding Principles
• Enterprise Inter-Connection Principles
Node = Major Enterprise Business Location
End = To-Be Inter-Connection Definitions
Characteristics:
• Interface Definitions & Standards
• Official & De-facto IS Standards
• Implementation Roadmap
• Tools for Development / Implementation
• Governance Plan
• Security Impact
e.g. Design of Application & Components
• History in (Extended) Enterprise
Frameworks
• Focusing on Collaboration
• Separation of Concerns
• Broad Acceptance
• Neutral / Open
• Complete Holistic Perspective.
• Communication Tool
• Enterprise Technology Standards
• Technology Overview
• Enterprise Infrastructure Profile
• Solutions & Products for Inter-Connection
• Functional Requirements
• Enterprise Hardware Systems Profile
• Non-Functional Requirements
• Enterprise Communication Profile
• Quality of Services
• Enterprise Security Profile
Link = Enterprise Business System Connection
Node = Enterprise Business System Environm.
• Business Case
• Make or Buy Decision
• Positioning Framework
• As-Is Enterprise Infrastructure
• TI Principles
Characteristics = Time, Availability, Security,
Maintainability, etc.
e.g. Information Roadmap
• Enterprise Governance Profile
• Technical Reference Model & Standards
Positioning = Allocation of IT Services ~ TRM
Interaction = Concepts of Service Layering
Http://www.enterprise-architecture.info
© 2004, Institute For Enterprise Architecture Developments / Capgemini - All Rights Reserved
Page 11
• Formats of Communication
• Security Integration
• Refinement Technical Reference Model
• Business Case
• Enterprise Transformation Plan
• Enterprise Priority Setting
• Enterprise IS Alignment Impact
Node = Hardware + System Software, etc.
Connectivity = Middleware / Messaging, etc.
e.g. Blue Print of Technology Implementation
End = Structure of Relations, Products +
Specifications
Catalogues of used Standards
End = Roadmap for Enterprise Implementation
Portfolio of Products and Components.
Computer Integrated Manufacturing Open Systems Architecture (CIMOSA)
Enterprise
Activity
•Information
•Constraints
Structure
•Function
•Material
•Resource
•Rules
•Organisation
User
Input
Function Information resource Organisation
CM-OSA Reference
Architecture
Requirements
Generic Building Blocks
Function Information resource Organisation
CIMOSA
Design
Enterprise
System
Requirements
Enterprise
System
Constraints
Characteristics:
• Process Framework
Partial Models
Function Information resource Organisation
• History in Manufacturing
• Focusing on Views
• Definition of Models
• Limited Acceptance
• 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
Implementation
System
Components
Component
Catalogue
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)
• 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)
Component-Based Architecture
Business & Performance-Driven Approach
Performance Reference Model (PRM)
• 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
Who and Why
Enabler
Information
Organisational
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
So, the Question is: Do You Create or Choose your
Enterprise Architecture Framework
ISBN 1-4120-1607-X
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