EA-Lecture 3 EA Methods and Frameworks.ppt

Enterprise Architecture
EA Methods
EA Methods
and
and
Frameworks
Frameworks
EA: Lecture 3
TOGAF
21
e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
Builder
SCOPE
(CONTEXTUAL)
MODEL
(CONCEPTUAL)
ENTERPRISE
Designer
SYSTEM
MODEL
(LOGICAL)
TECHNOLOGY
MODEL
(PHYSICAL)
DETAILED
REPRESEN-
TATIONS
(OUT-OF-
CONTEXT)
Sub-
Contractor
FUNCTIONING
ENTERPRISE
DATA FUNCTION NETW ORK
e.g. Data Definition
Ent = Field
Reln = Address
e.g. Physical Data Model
Ent = Segment/Table/etc.
Reln = Pointer/Key/etc.
e.g. Logical Data Model
Ent = Data Entity
Reln = Data Relationship
e.g. Semantic Model
Ent = Business Entity
Reln = Business Relationship
List of Things Important
to the Business
ENTITY = Class of
Business Thing
List of Processes the
Business Performs
Function = Class of
Business Process
e.g. Application Architecture
I/O = User Views
Proc .= Application Function
e.g. System Design
I/O = Data Elements/Sets
Proc.= Computer F unction
e.g. Program
I/O = Control Block
Proc.= Language Stmt
e.g. FUNCTION
e.g. Business Process Model
Proc. = Business Process
I/O = Business Resources
List of Locations in which
the Business Operates
Node = Major Business
Location
e.g. Business Logistics
System
Node = Business Location
Link = Business Linkage
e.g. Distributed System
Node = I/S Function
(Processor, Storage, etc)
Link = Line Characteristics
e.g. Technology Architecture
Node = Hardware/System
Software
Link = Line Specifications
e.g. Network Architecture
Node = A ddresses
Link = Protocols
e.g. NETWORK
Architecture
Planner
Owner
Builder
ENTERPRISE
MODEL
(CONCEPTUAL)
Designer
SYSTEM
MODEL
(LOGICAL)
TECHNOLOGY
MODEL
(PHYSICAL)
DETAILED
REPRESEN-
TATIONS
(OUT- OF
CONTEXT)
Sub-
Contractor
FUNCTIONING
MOTIVATION
TIME
PEOPLE
e.g. Rule Specification
End = Sub-condition
Means = Step
e.g. Rule Design
End = Condition
Means = Action
e.g., Business Rule Model
End = Structural Assertion
Means =Action Assertion
End = Business Objective
Means = Business Strategy
List of Business Goals/Strat
Ends/Means=Major Bus. Goal/
Critical Success Factor
List of Events Significant
Time = Major Business Event
e.g. Processing Structure
Cycle = Processing Cycle
Time = System Event
e.g. Control Structure
Cycle = Component Cycle
Time = Execute
e.g. Timing Definition
Cycle = Machine Cycle
Time = Interrupt
e.g. SCHEDULE
e.g. Master Schedule
Time = Business Event
Cycle = Business Cycle
List of Organizations
People = Major Organizations
e.g. Work Flow Model
People = Organization Unit
Work = Work Product
e.g. Human Interface
People = Role
Work = Deliverable
e.g. Presentation Architecture
People = User
Work = Screen Format
e.g. Security Architecture
People = Identity
Work = Job
e.g. ORGANIZA
T ION
Planner
Owner
to the Business
Important to the Business
What How Where Who When Why
John A. Zachman, Zachman International (810) 231-0531
SCOPE
(CONTEXTUAL)
Architecture
e.g. STRATEGY
ENTERPRISE
e.g. Business Plan
TM

• Frameworks structure architecture description
techniques by identifying and relating different
architectural viewpoints and the modeling techniques
associated with them.
• Some frameworks are closely connected to a specific
modeling language or set of languages.
EA: Lecture 4 3

• Most architecture frameworks are quite precise in
establishing what elements should be part of an
enterprise architecture.
• To ensure the quality of the enterprise architecture
during its life cycle the adoption of a certain
framework is not sufficient.
EA: Lecture 4 4

• The relations between the different types of
domains, views, or layers of the architecture must
remain clear, and any change should be carried
through methodically in all of them.
• For this purpose, a number of methods are
available, which assist architects through all phases
of the life cycle of architectures.
EA: Lecture 4 5

1. Enterprise Architecture Methods
• An architecture method is a structured collection of
techniques and process steps for creating and
maintaining an enterprise architecture.
• Methods typically specify:
• the various phases of an architecture’s life cycle,
• what deliverables should be produced at each stage, and
• how they are verified or tested.
• The following methods for architecture
development are worth mentioning:
EA: Lecture 4 6

1. Although meant for software development, the
Rational Unified Process (RUP) (Jacobson et al.
1999) is of interest here, as it defines an iterative
process, as opposed to the classical waterfall
process, that realizes software by adding
functionality to the architecture at each increment.
An extension towards enterprise IT architecture is
given by McGovern et al. (2004) in the form of the
Enterprise Unified Process.
EA: Lecture 4 7

2. The UN/CEFACT Modeling Methodology
(UMM) is an incremental business process and
information model construction methodology. The
scope is intentionally restricted to business
operations, omitting technology-specific aspects.
The Business Collaboration Framework (BCF), is a
specialization of the UMM aimed at defining an
enterprise’s external information exchanges and
their underlying business activities.
EA: Lecture 4 8

3. The four phase/twenty-step methodology to
establish an EA program and implement the six EA
documentation elements of EA3 Cube Framework
provided by Scott A. Bernard . It contains four
phases Phase I:EA Program Establishment, Phase
II:EA Framework and Tool Selection, Phase III:
Documentation of the EA and Phase IV: Use and
Maintain the EA
EA: Lecture 4 9

4. The TOGAF Architecture Development Method
(ADM), developed by The Open Group, provides a
detailed and well-described phasing for developing
an IT architecture. The current version of TOGAF
(The Open Group 2011) provides a framework and
development method for developing enterprise
architectures.
EA: Lecture 4 10

5. The Chief Information Officers Council has created
The Federal Enterprise Architecture Framework
(FEAF) accompanied by a practical and useful
manual for developing enterprise architecture for
governmental organizations (CIO Council 2004).
Other initiatives of the US government include the
Federal Enterprise Architecture (FEA) of the
Federal Enterprise Architecture Program
Management Office (FEAPMO 2004) and the
Treasury Architecture Development Process by the
Department of the Treasury (US Treasury 2004).
EA: Lecture 4 11

• Various consulting companies have developed their
own architecture methods and frameworks.
• Examples include Sogeti’s DYA, Capgemini’s IAF,
IBM’s Enterprise Architecture method, and
Microsoft’s Motion.
EA: Lecture 4 12

Types of EA Frameworks
• EA frameworks can be categorized into the
following types:
1. Consortia-developed frameworks
2. Defense industry frameworks
3. Government frameworks
4. Open-source frameworks
5. Proprietary frameworks
EA: Lecture 4 13

Consortia-developed frameworks
• ARCON : A Reference Architecture for Collaborative
Networks – not focused on a single enterprise but
rather on networks of enterprises
• GERAM : Generalized Enterprise Reference
Architecture and Methodology
• RM-ODP : the Reference Model of Open Distributed
Processing
• ISO/IEC 10746: defines an enterprise architecture
framework for structuring the specifications of open
distributed systems.
EA: Lecture 4 14

Consortia-developed frameworks
• IDEAS Group :a four-nation effort to develop a
common ontology for architecture interoperability
• ISO 19439: Framework for enterprise modeling
• TOGAF : The Open Group Architecture Framework –
a widely used framework including an architectural
Development Method and standards for describing
various types of architecture.
EA: Lecture 4 15

Defense industry frameworks
• AGATE : the France DGAArchitecture Framework
• DNDAF : the DND/CF Architecture Framework
(CAN)
• DoDAF : the US Department of Defense Architecture
Framework
• MODAF : the UK Ministry of Defence Architecture
Framework
• NAF : the NATO Architecture Framework
EA: Lecture 4 16

Government frameworks
• ESAAF : European Space Agency Architectural Framework, a
framework for European space-based Systems of Systems
• GEA : Government Enterprise Architecture, common
framework legislated for use by departments of the Queensland
Government
• FDIC Enterprise Architecture Framework
• FEAF : Federal Enterprise Architecture Framework, a
framework produced in 1999 by the US Federal CIO
Council for use within the US Government (not to be confused
with the 2002 Federal Enterprise Architecture (FEA) guidance
on categorizing and grouping IT investments, issued by the US
Federal Office of Management and Budget
EA: Lecture 4 17

Government frameworks
• NORA : Nederlandse Overheid Referentie
Architectuur , a reference framework from the Dutch
Government E-overheid NORA
• NIST Enterprise Architecture Model
• TEAF : Treasury Enterprise Architecture Framework,
a framework for treasury, published by the US
Department of Treasuryin July 2000
EA: Lecture 4 18

Open-source frameworks
• MEGAF : is an infrastructure for realizing architecture
frameworks that conform to the definition of architecture
framework provided in ISO/IEC/IEEE 42010.
• Praxeme, an open enterprise methodology, contains an
enterprise architecture framework called the Enterprise System
Topology (EST)
• TRAK : a general systems-oriented framework based on
MODAF1.2 and released under GPL/GFDL.
• SABSA is an open framework and methodology for Enterprise
Security Architecture and Service Management, that is risk
based and focuses on integrating security into business and IT
management.
EA: Lecture 4 19

Proprietary frameworks
• ASSIMPLER Framework – an architecture framework,
based on the work of Mandar Vanarse at Wipro in 2002
• AM : Avancier Methods Processes and documentation
advice for enterprise and solution architects, supported
by training and certification.
• BRM : Build-Run-Manage Framework, an architecture
framework created by Sanjeev "Sunny" Mishra during
his early days at IBM in 2000.
• IAF : Capgemini Integrated Arcitecture Framework,
from Capgemini company in 1993
EA: Lecture 4 20

• Dragon1 : An open Visual Enterprise Architecture Method
recently recognized by The Open Group as Architecture
Framework
• DYA framework developed by Sogeti since 2004.
• Dynamic Enterprise Enterprise architecture concept based
on Web 2.0 technology
• Extended Enterprise architecture Framework from Institute
For Enterprise Architecture Developments in 2003
• EACOE Framework : an Enterprise Architecture
framework, as an elaboration of the work of John Zachman
EA: Lecture 4 21

• IFW : IBM Information Framework, conceived by
Roger Evernden in 1996
• PEAF : Pragmatic Enterprise Architecture
Framework, part of Pragmatic Family of Frameworks
developed by Kevin Lee Smith, Pragmatic EA, from
2008
• Purdue Enterprise Reference Architecture developed
by Theodore J. Williams at the Purdue University early
1990s.
EA: Lecture 4 22

• SAP Enterprise Architecture Framework
• SOMF : Service-Oriented Modeling Framework based
on the work of Michael Bell
• SAM : Solution Architecting Mechanism, A coherent
architecture framework consisting of a set of integral
modules.
• Zachman Framework, an architecture framework,
based on the work of John Zachman at IBM in the
1980s
EA: Lecture 4 23

2. The Zachman Framework
• In 1987, John Zachman introduced the first and best-
known enterprise architecture framework (Zachman
1987), although back then it was called ‘Framework
for Information Systems Architecture’.
• The framework as it applies to enterprises is simply
a logical structure for classifying and organizing the
descriptive representations of an enterprise that are
significant to the management of the enterprise as
well as to the development of the enterprise’s
systems.
EA: Lecture 4 24

• The framework in its most simple form depicts the
design artefacts that constitute the intersection
between the roles in the design process: that is,
owner, designer, and builder; and the product
abstractions: that is, what (material) it is made of,
how (process) it works and where (geometry) the
components are relative to one another.
EA: Lecture 4 26

• Empirically, in the older disciplines, some other
‘artefacts’ were observable that were being used for
scoping and for implementation purposes.
• These roles are somewhat arbitrarily labeled planner
and subcontractor and are included in the
framework graphic that is commonly exhibited.
EA: Lecture 4 27

• From the very inception of the framework, some
other product abstractions were known to exist
because it was obvious that in addition to what, how,
and where, a complete description would necessarily
have to include the remaining primitive
interrogatives: who, when and why.
• These three additional interrogatives would be
manifest as three additional columns of models that,
in the case of enterprises, would depict: who does
what work, when do things happen, and why are
various choices made?
EA: Lecture 4 28

• Advantages of the Zachman framework are that it is easy to
understand, it addresses the enterprise as a whole, it is defined
independently of tools or methodologies, and any issues can
be mapped against it to understand where they fit.
• An important drawback is the large number of cells, which is
an obstacle for the practical applicability of the framework.
• Also, the relations between the different cells are not that well
specified.
• Not with standing these drawbacks, Zachman is to be credited
with providing the first comprehensive framework for
enterprise architecture, and his work is still widely used.
EA: Lecture 4 29

EA: Lecture 4 31
The Zachman Framework

The Spewak EA Planning Method (1992)
EA: Lecture 4 32

The EA³ Cube Framework (2004)
provided by Scott A. Bernard
EA: Lecture 4 33

EA: Lecture 4 34
Level EA Components EA Artifacts
Goals and Initiatives x Strategic Plan
x E-Commerce/E-Government Plan
x Strategic Plan (S-1)
x SWOT Analysis (S-2)
x Concept of Operations Scenario (S-3)
x Concept of Operations Diagram (S-4)
x Balanced Scorecard™ (S-5)
Products & Services x Business Services
x Business Products
x IT Capital Planning Portfolio
x Business Plan (B-1)
x Node Connectivity Diagram (B-2)
x Swim Lane Process Diagram (B-3)
x Business Process/Service Model (B-4)
x Business Process/Product Matrix (B-5)
x Use Case Narrative and Diagram (B-7)
x Investment Business Case (B-8)
Data and Information x Knowledge Warehouses
x Information Systems
x Databases
x Knowledge Management Plan (D-1)
x Information Exchange Matrix (D-2)
x Object State-Transition Diagram (D-3)
x Object Event Sequence Diagram (D-4)
x Logical Data Model (D-5)
x Physical Data Model (D-6)
x Activity/Entity (CRUD) Matrix (D-7)
x Data Dictionary/Object Library (D-8)

Systems and
Applications
x Software Applications
x Web Services
x Service Bus and Middleware
x Enterprise Resource Planning (ERP ) Solutions
x Operating Systems
x System Interface Diagram (SA-1)
x System Communication Diagram (SA-2)
x System Interface Matrix (SA-3)
x System Data Flow Diagram (SA-4)
x System/Operations Matrix (SA-5)
x Systems Data Exchange Matrix (SA06)
x System Performance Matrix (SA-7)
x System Evolution Diagram (SA-8)
x Web Application Diagram (SA-9)
Network &
Infrastructure
x Data Networks
x Telecommunications Networks
x Video Networks
x Mobile Networks
x Cable and Wireless Backbones
x Security Solutions
x Buildings and Server Rooms
x Equipment
x Network Connectivity Diagram (NI-1)
x Network Inventory (NI-2)
x Capital Equipment Inventory (NI-3)
x Building Blueprints (NI-4)
x Network Center Diagram (NI-5)
x Cable Plant Diagram (NI-6)
x Rack Elevation Diagram (NI-7)
EA: Lecture 4 35

Security x Security and Privacy Plan (SP-1)
x Security Solutions Description (SP-2)
x System Accreditation Document (SP-3)
x Continuity Of Operations Plan (SP-4)
x Disaster Recovery Procedures (SP-5)
Standards x Technical Standards Profile (ST-1)
x Technology Forecast (ST-2)
Workforce Skills x Workforce Plan (W-1)
x Organization Chart (W-2)
x Knowledge and Skills Profile (W-3)
EA: Lecture 4 36

EA-Lecture 3 EA Methods and Frameworks.ppt

More Related Content

Similar to EA-Lecture 3 EA Methods and Frameworks.ppt (20)

Recently uploaded (20)

EA-Lecture 3 EA Methods and Frameworks.ppt

Editor's Notes