1
Sobah Abbas Petersen
Adjunct Associate [email protected]
TDT4252Modelling of Information Systems
Advanced Course
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
2
This Lecture• Enterprise Architectures continued: TOGAF, Gartner, FEA
– Based on lecture slides from Spring 2010, by Harald Rønneberg.
• Requiered Reading: – A15: Roger Sessions, A Comparison of the Top Four Enterprise-Architecture
Methodologies, White Paper, ObjectWatch Inc. May 2007.
• Additional reading:– The Open Group Architecture Framework (TOGAF) – The continuing Story, Chris Greenslade,
2002. (http://www.enterprise-architecture.info/Images/Documents/Togaf%20seminar.pdf)– Federal Enterprise Architecture Framework, Version 1.1, September 1999,
(http://www.cio.gov/documents/fedarch1.pdf)– http://en.wikipedia.org/wiki/Federal_Enterprise_Architecture– Cisco Systems, 2009. Federal Enterprise Architecture (FEA) and Network Services, White Paper,
pages 1-6. (http://www.cisco.com/en/US/solutions/collateral/ns340/ns414/ns859/C11-542359-00_FEAnetsol.pdf)
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
3
What is Enterprise Architecture –recap
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
4
EA Bridges Strategy and Implementation
The bridge between strategy & implementation
Business architectureInformation architectureSolution architectureTechnology architecture
Business StrategyBusiness driversBusiness goalsBusiness policyTrend analysis
ImplementationBusiness processesApplication systemsTech infrastructureOrganizational structure
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
5
Alignment
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Common understanding!
6
Zachman’s EA Framework - recap
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
2 1e .g . D AT A
E N T E R P R IS E A R C H IT E C T U R E - A F R A M E W O R K
B u ilder
S C O P E(C O N T E X T U A L)
M O D E L(C O N C E P T U A L)
E N T E R P R IS E
D esigner
S Y S T E MM O D E L(LO G IC A L)
T E C H N O LO G YM O D E L(P H Y S IC A L)
D E T A ILE DR E P R E S E N - T AT IO N S(O U T -O F - C O N T E X T )
Sub-C on tra cto r
F U N C T IO N IN GE N T E R P R IS E
D AT A F U N C T IO N N E T W O R K
e.g . D a ta D e fin it ion
E n t = F ie ldR e ln = A d d ress
e .g . P h ys ica l D a ta M o d e l
E n t = S e g m e n t/Ta b le /e tc .R e ln = P o in te r /K e y /e tc .
e .g . L o g ica l D a ta M o de l
E n t = D a ta E n tityR e ln = D a ta R e la tio n sh ip
e .g . S e m a n tic M o d e l
E n t = B u s in ess E n tityR e ln = B u sin e ss R e la tio nsh ip
L is t o f T h in g s Im p o rta n tto th e B us in e ss
E N T IT Y = C la ss o fB u s ine ss Th ing
L is t o f P ro ce sse s th eB u s in e ss P e rfo rm s
F unc tion = C la ss o fB u s in e ss P roce ss
e .g . A p p lica tion A rch ite c tu re
I/O = U se r V ie w sP ro c .= A p p lica tio n F u n c tio n
e .g . S ys te m D e sig n
I/O = D a ta E le m e n ts /S e tsP ro c.= C om p u te r F u n c tio n
e .g . P ro g ra m
I/O = C o n tro l B lo ckP ro c .= L a n g u a ge S tm t
e .g . F U N C T IO N
e .g . B u s in e ss P ro ce ss M o d e l
P ro c. = B u s in e ss P ro ce ssI/O = B us in e ss R e so u rces
L is t o f Lo c atio n s in w h ich th e B us ine s s O p e ra tes
N o de = M a jor B u s ines sLo ca tio n
e .g . B us in e ss Lo g is tics S ys te m
N o d e = B u s in e ss L o ca tionL ink = B u s in ess L in ka g e
e .g . D is tr ib u te d S yste m
N o d e = I/S F u n c tio n(P ro ce sso r, S to ra g e , e tc )L in k = L in e C h ara c te r is t ic s
e .g . Tech n o log y A rch ite ctu re
N o d e = H a rd w are /S ys te mS o ftw a re
L ink = L in e S p ec if ic a tions
e .g . N e tw o rk A rch ite c tu re
N o d e = A d d re sse sL in k = P ro toco ls
e .g . N E T W O R K
A rch ite c tu re
P lanner
O w ner
B uilde r
E N T E R P R IS EM O D E L
(C O N C E P T U A L)
D esigner
S Y S T E MM O D E L
(LO G IC A L)
T E C H N O LO G YM O D E L
(P H Y S IC A L)
D E T A ILE DR E P R E S E N -
T AT IO N S (O U T -O F
C O N T E X T )
Sub-C on trac to r
F U N C T IO N IN G
M O T IV AT IO NT IM EP E O P LE
e .g . R u le S p e c if ica tio n
E nd = Su b-co n d itio nM e a n s = S te p
e .g . R u le D e s ig n
E n d = C on d itio nM e a ns = A c tio n
e .g ., B u s ine ss R u le M o d e l
E n d = S truc tura l A ss ertio nM e a n s = Ac tio n A sse r tio n
E n d = B u s ine ss O b je c tiveM ea n s = B u s in e ss S tra teg y
L is t o f B u s in e ss G oa ls /S tra t
E nds /M ea n s= M a jo r B u s . G o a l/C rit ica l S u cce ss F a cto r
L is t o f E ve n ts S ig n if ica n t
T im e = M a jo r B u s in es s E v en t
e .g . P ro ce ss ing S tru c tu re
C yc le = P ro ce ssin g C yc leT im e = S yste m E v en t
e .g . C o n tro l S tru c tu re
C ycle = C om p o n e n t C yc leT im e = E xe cu te
e .g . T im in g D e fin itio n
C yc le = M a ch in e C ycleT im e = In te rru p t
e .g . S C H ED U L E
e.g . M a s te r S ch e d u le
T im e = B us ine s s E ve n tC ycle = B u s in e ss C yc le
L is t o f O rg an iza tio ns
P eo p le = M a jo r O rga nizatio n s
e.g . W o rk F lo w M ode l
P e op le = O rga nizatio n U n itW o rk = W o rk P ro d u c t
e .g . H um a n In te rfa ce
P e op le = R o leW o rk = D e live ra b le
e .g . P re se n ta tion A rch itec ture
P e op le = U s erW o rk = S c ree n F orm ate .g . S e cu rity A rch ite ctu re
P e o ple = Id en tityW ork = J ob
e .g . O R G A N IZ AT IO N
P lanner
O w ner
to th e B u s ines sIm po rtan t to th e B us ine s s
W ha t H ow W here W ho W hen W hy
Joh n A . Z achm an , Z ach m an In te rn ation a l (810 ) 2 3 1 -05 31
S C O P E(C O N T E X T U A L)
A rch itec tu re
e .g . S T R AT E G YE N T E R P R IS E
e .g . B u sin e ss P la n
T M
View
Aspects
Viewpoints
7
Example case: MEM-EA• Internal conflicts between the
technical and and the business side.– Business side saw IT as reducing business
agility.– IT side saw the business side as making
impossible demands. Crisis!
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Irma, CIO
Cath, CEO
Bret, Business Manager
8
TOGAF
• The Open Group Architecture Framework
• The Open Group Forums – cooperation between vendors and users, where a variety of common interests are explored, one of which is architecture.
• Earlier versions of TOGAF available since 1995.
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
9
Enterprise Architecture
• An architecture– A formal description of a system, or
a detailed plan of the system at component level to guide its implementation.
– The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time.
TOGAF
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
10
The Position of IT Architects
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
11
TOGAF – consists of
• An Architectural Development Method (ADM)
• Foundation Architecture– A Technical Reference Model (TRM)
– A Standards Information Base (SIB)
– Building Blocks Information (BBIB)
• Resource Base contains advice on:– Architecture views, IT Governance, Business scenarios, Architecture
patterns, etc.
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Greenslade, 2000-2002
12
TOGAF
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
13
TOGAF – Framework or Process?
• TOGAF describes itself as a Framework. But the most important part of it is the Architectural Development Method (ADM):– ADM is a recipe for creating architecture.
• TOGAF is an architectural process (Roger Sessions).
• It complements Zachman’s Framework: – Zachman tell you how to categorise artifacts; TOGAF provides a
process for creating them.
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
14
TOGAF’s Enterprise Architecture
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Describes theprocesses thebusiness uses to meet its goals.
Describes howspecificapplications aredesigned and howthey interact witheach other.
Describes how the enterprise datastores are organised and accessed.
Describes the hardware and software infrastructure that supports applications and their interactions.
15
TOGAF Enterprise Continuum (1)
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
•TOGAF views the Enterprise Architecture as a
continuum of architectures, ranging from the highly
generic to the highly specific.
•It views the process of creating a specific enterprise
architecture as moving from the generic to the specific.
•TOGAF’s ADM provides a process for driving this
movement from the generic to the specific.
16
TOGAF Enterprise Continuum (2)
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
17
• Foundation Architectures:– Most generic, architectural principles that can be used by any IT
organisation.
• Common System Architectures:– architectural principles that may be found in many types of
enterprises.
• Industry Architectures:– architectural principles that are specific across many enterprises that
are in the same domain.
• Organisational Architectures:– Architectures that are specific to a given enterprise.
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
TOGAF Enterprise Continuum and ADM
Generic
Specific
18 TOGAF – Components of Foundation Architecture
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
19
TRM – Technical Reference Model
• Any TRM has two main components:1. A taxonomy, which defines terminology, and provides a
coherent description of the components and conceptual structure of an information system.
2. An associated TRM graphic, which provides a visual representation of the taxonomy, as an aid to understanding.
• The objective of the TOGAF TRM is to provide a widely accepted core taxonomy, and an appropriate visual representation of that taxonomy.
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
20
Architecture Development Cycle -ADM
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
21
ADM - Framework and Principles
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Define architecture principles that drive technological architectures and document those.
Choose framework and customise.
Request for Architecture Work
Framework and
Principles
Irma, CIO
Teri, TOGAF
Consultant
Bret, Business Manager
22
ADM - Architecture Vision
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Define the scope of the architecture project
Define high level business requirements
Statement of architecture work/architectural vision, to be approved by Stakeholders
A Architecture
Vision
23
ADM – Business Architecture
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Detailed baseline and target business architecture and full analysis of the gaps between them.
The objective is to define and describe the product and/or service strategy, and the organizational, functional, process, information, and geographic aspects of the business environment.
BBusiness
Architecture
Teri, TOGAF
Consultant
Bret, Business Manager
24
ADM: Informations Systems Architecture – Data & Applications
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
CInformation
System Architecture
Applications Architecture
Data Architecture
Management
The objective is to define the major types and source of data necessary to support the business. It is NOT about database design. The goal is to define the data entities relevant to the enterprise.
Teri, TOGAF
Consultant
Irma, CIO
Target information and application architecture.
25
ADM: Technical Architecture
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
DTechnology Architecture
Management
The objective is to define the technology and technical services that will form the basis of the following implementation work.
Teri, TOGAF
Consultant
Irma, CIO
Complete technical architecture: the infrastructure necesary to support the proposed new architecture.
26
ADM: Opportunities and Solutions
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
The first phase directly concerned with implementation
How to close the gaps?
Identify implementation projects
EOpportunities and Solutions
ManagementFocus on projects that will deliver short term payoffs, e.g. the organisational pain points such as difficulties in completing regional /warehouse specialisation and unreliability in data sharing.
27
Prioritize between implementation projects
i.e. project portfolio management Cost and benefit analysis Risk assessment
ADM: Migration Planning
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
FMigration Planning
Management
28
ADM: Implementation Governance
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Architectural contract. Ensure compliance with the
defined architecture. Implementation
specifications – acceptance criteria.
GImplementation
Governance Management Architectural specifications for the implementation projects.
29
ADM: Architectural Change Management
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Handle architecture change requests
Suggest new architecture projectsH
Architecture Change
Management
Management
30
ADM: Requirements Management
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Handling new and changing requirements from architecture projects, IT projects, change projects, operations, etc.
Requirements Management
Ready to start the phase again. One of the goals of the first cycle
should be information transfer so that Teri's consultancy services are required less in the next cycle.
31
TOGAF - benefits
+ TOGAF is flexible about the architecture that is generated – ”architecture agnostic” or vendor neutral.
+ Comprehensive process, from business requirements to applications to infrastructure.
• The final architecture may be good, bad or indifferent.÷ TOGAF merely describes how to generate enterprise
architecture, not necessarily how to generate a good one!
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
32
TOGAF and MED-EA
• The final architecture may be good or bad.
• It merely describes how to generate an architecture, not
necessarily a good one!
• A good architecture will depend on the experience of
the MedAMore staff and Teri, thOGAF consultant.
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
33
Gartner
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
• A planning discipline for the enterprise that goes beyond technology choices:– Driven by the strategic intent of the enterprise– Holistic in breadth– Designed to create a future-state “road map”– Provides flexibility and adaptability for changing business, information, and
solution needs => change enabler– A bridge between strategy and implementation
Architecture ImplementationStrategy
34
EA Bridges Strategy and Implementation
The bridge between strategy & implementation
Business architectureInformation architectureSolution architectureTechnology architecture
Business StrategyBusiness driversBusiness goalsBusiness policyTrend analysis
ImplementationBusiness processesApplication systemsTech infrastructureOrganizational structure
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
35
From Strategy to Implementation
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
• Planning and Strategy– Focused on integration of business
and IT planning• Enterprise Architecture
– Goal is to provide the road map for the enterprise
• Program Management– Primary agent for implementing
enterprise transformation
EnterprisePlanning
and Strategy
Enterprise Program
Management
EnterpriseArchitecture
36
Gartner
• The Gartner EA methodology is a ”practice” – Sessions.• It is an ongoing process of creating, maintaining, and
especially, leveraging an enterprise architecture that gives the enterprise its vitality.
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
37
Gartner • EA is about creating a
common understanding.• Bringing together 3
constituents: business owners, information specialists and technology imolementers.
• If we can unify these behind a common vision that drives the business value success!
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Business Owners
Informationspecialist
TechnologyImplementers
Common understanding
38
Gartner
• Enterprise Architecture must start where an organisation is going, not where it is focussed on destination.
• Recommends that an organisation begins by telling the story of where its strategic direction is heading and what the business drivers are to which it’s responding.
Goal: everybody understands and shares a single vision.
• As soon as an organisation has a single vision, the implications on the business, technical, information and solution architectures can be considered.
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
x
x
39
Gartner Enterprise Architecture Method
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
The two major facets of the Gartner EA method are: • Gartner Enterprise Architecture Process Model
Environmental TrendsBusiness Strategy
Closing the Gap
Future State Architecture
Current State Architecture
Governing & Managing
Org
aniz
e Ar
chite
ctur
e Ef
fort
ArchitectingDevelop
RequirementsDevelop
PrinciplesDevelopModels
Documenting
• Gartner Enterprise Architecture Framework
40
Gartner’s 4 Architectural Viewpoints
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Three primary viewpoints:– Business Architecture– Information Architecture– Technology Architecture
One meta-architectureviewpoint
– Solution Architecture
Solution Architecture Framework
– A framework for creating Solution Architectures
41
Gartner’s 4 Architectural Viewpoints
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Business Architecture– Defines and describes the current- and future- state models of business activities
(processes, assets and organization structure)Information Architecture
– Defines and describes the current- and future- state models of the information value chain, key information artifacts (concepts), information flows
Technology Architecture– Defines and describes the current- and future- state models of the infrastructure and
technology platforms required for the solution architecture and which enables rapid engineering, solutions development and technical innovation
Solution Architecture– Combining and reconciling (integration) the loosely coupled and often conflicting
viewpoints of the primary stakeholders into a unified architecture– Having divided to conquer, we must reunite to rule– SA is a consistent architectural description of a specific enterprise solution– An intersection of viewpoints
42
Gartner Enterprise Architecture Process Model
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Environmental Trends
Business Strategy
Closing the Gap
Future State Architecture
Current State Architecture
Governing & Managing
Org
aniz
e A
rchi
tect
ure
Effo
rt
ArchitectingDevelop
RequirementsDevelop
PrinciplesDevelopModels
Documenting
43
Organise Architecture Effort
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Environmental Trends
Business Strategy
Closing the Gap
Future State Architecture
Current State Architecture
Governing & Managing
Org
aniz
e A
rchi
tect
ure
Effo
rt
ArchitectingDevelop
RequirementsDevelop
PrinciplesDevelopModels
Documenting
44
Organise Architecture Effort - Activities
• State the goals• Scoping• Buy-in and commitment• Stakeholder analysis• Set time box• Establish EA team
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
45
Develop Requirements
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Environmental Trends
Business Strategy
Closing the Gap
Future State Architecture
Current State Architecture
Governing & Managing
Org
aniz
e A
rchi
tect
ure
Effo
rt
ArchitectingDevelop
RequirementsDevelop
PrinciplesDevelopModels
Documenting
46
CRV - from strategy to business requirements
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Greg, Gartner
Consultant
Cath, CEO
• Greg asks Cath to specify her visions in business (not technical terms).
• The visions are prioritised. • Cath decides the highest priority is "MedAMore will
reduce its purchasing costs by 10% by consolidating all regional purchasing into a central system".
CRV = Common Requirements Vision
47
What is CRV?
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
• A process for capturing, discussing and documenting a shared common view of the strategic requirements driving the enterprise: Position on the impact of
environmental trends to the enterprise Set of enterprise business strategies Set of common strategic
requirements derived from enterprise business strategies
The CRV document is an articulation of what will drive the enterprise’s future state
EnvironmentalTrends
EnterpriseBusiness
Strategies
BusinessChange
Requirements
BusinessInformation
Requirements
InformationTechnology
Requirements
BusinessSolutions
Requirements
48
Develop Models
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Environmental Trends
Business Strategy
Closing the Gap
Future State Architecture
Current State Architecture
Governing & Managing
Org
aniz
e A
rchi
tect
ure
Effo
rt
ArchitectingDevelop
RequirementsDevelop
PrinciplesDevelopModels
Documenting
49
Gartner’s 4 Architectural Viewpoints (1)
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Business Architecture– Defines and describes the future- state models of business
activities (processes, assets and organization structure)
Information Architecture– Defines and describes the future- state models of the
information value chain, key information artifacts (concepts), information flows
Technology Architecture– Defines and describes the future- state models of the
infrastructure and technology platforms required for the solution architecture and which enables rapid engineering, solutions development and technical innovation
Bret, BusinessManager
Greg, Gartner
Consultant
Irma, CIOGreg, Gartner
Consultant
50
Gartner’s 4 Architectural Viewpoints (2)
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Solution Architecture– Combining and reconciling (integration) the loosely coupled and often
conflicting viewpoints of the primary stakeholders into a unified architecture– Having divided to conquer, we must reunite to rule– SA is a consistent architectural description of a specific enterprise solution– An intersection of viewpoints.
51
Current state and the gap
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Environmental Trends
Business Strategy
Closing the Gap
Future State Architecture
Current State Architecture
Governing & Managing
Org
aniz
e A
rchi
tect
ure
Effo
rt
ArchitectingDevelop
RequirementsDevelop
PrinciplesDevelopModels
Documenting
52
Governing and Managing
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Environmental Trends
Business Strategy
Closing the Gap
Future State Architecture
Current State Architecture
Governing & Managing
Org
aniz
e A
rchi
tect
ure
Effo
rt
ArchitectingDevelop
RequirementsDevelop
PrinciplesDevelopModels
Documenting
53
Gartner- benefits
+ Process completeness – the methodology fully guides you through a step-by-step process for creating EA.
+ Practical guidance.+ Business focus.+ Provides a methodology that can support governance.÷ Does not provide a complete taxonomy.÷ Not much information available about it.
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
54
What is FEAF?
• FEAF (Federal Enterprise Architecture Framework) provides an organised structure and a collection of common terms by which Federal segments can integrate their respective architectures into the FEA (Federal Enterprise Architecture).
• FEA is a strategic information asset base that defines the business, information necessary to operate the business, technology necessary to support the business operations and transitional processes for implementing new technologies in response to the changing needs of the business.
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
55
Why FEAF?
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
56
Value of FEAF
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
57
FEAF Components (1)
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
External stimuli or change agents for the enterprise architecture.
Refer to all standards (some of which may be mandatory), guidelines and best practices.
Defines the ”as-is” enterprise architecture. Consists of 2 parts: current business and design architectures (i.e. data, applications and technology).
Defines the ”to-be” enterprise architecture. Consists of 2 parts: current business and design architectures (i.e. data, applications and technology).
58
FEAF Components (2)
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Consists of focused architecture efforts on major cross-cutting business areas and program areas.
Guides the development of the target architecture and consists of a vision, principles, goals and objectives.
Supports the migration from the current to the target architecture. This includes migration planning, investment planning, engineering change control, etc.
Defines the business and design models that compromise the segments of the enterprise descriptions.
59
FEAF - Segments
• FEAF allows critical parts of the overall Federal Enterprise, called architectural segments, to be developed individually, while integrating these segments into the larger Enterprise Architecture.
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
60
FEA – Federal Enterprise Architecture• FEA is the latest attempt by the US federal government
to unite its agencies and functions in a single common and ubiquitous enterprise architecture.
• FEA is the most complete methodology. It has a:– A comprehensive taxonomy, like Zachman’s framework.– An architectural process, like TOGAF.
• FEA can be viewed as either a methodology for creating an enterprise architecture or the result of applying that process to a particular enterprise.
• FEA includes everything necessary for building an enterprise architecture.
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
61
FEA – Reference Models
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
•The goal of the reference models is to provide standardised terms and
definitions for the domain of enterprise architecture and thereby
facilitate collaboration and sharing across the federal government.
•It’s all about establishing a common language.
•Collectively, the reference models comprise a framework for describing
important elements of the FEA in a common and consistent way.
62
FEA – Reference Models
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
FEA consists of 5 reference models:
63
FEA – Reference Models: descriptions• Business Reference Model (BRM):
– Gives a business view of the various business functions.
• Service Components Reference Model (CRM):– Gives a more IT view of systems that can support business
functionality.
• Technical Reference Model (TRM):– Defines the various technologies and standards that can be used in
building ITsystems.
• Data Reference Model (DRM):– Defines standard ways of describing data.
• Performance Reference Model (PRM):– Defines standard ways of describing the value delivered by enterprise
architecture.
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
64
FEA – Segment architecture approach• FEA perspective on EA: an enterprise is built of
segments.• A segment is a major line-of-business functionality,
such as human resources.• Although segments function at the political level (the
agency), they are defined at the enterprise level (government).
• Segments are defined globally to facilitate reuse across the the different enterrpises.
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
65
FEA – Segment Map
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Segments (vertical columns): spans a single organisation, used by multiple segments.
Enterprise Services: have a scope across the entire enterprise.
66
FEA Process (1)
• FEA Process is primarily focussed on creating a segment architecture for a subset of the overall enterprise.
• Segment architecture development process:– Step 1: Architectural analysis.– Step 2: Architectural definition.– Step 3: Investment and funding strategy.– Step 4: Program management plan and execute projects.
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
67
FEA Process, Level I
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
High level
68
FEA Process – Level II
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
More detail – the business and design pieces of the architecture and how they are related.
69
FEA Process – Level III
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Expand the design pieces of the framework to show the 3 design architectures: data, application and technology.
70
FEA Process – Level IV• Identifies the kinds of models that describe the business architecture and
the three design architectures ( data, applications and technology).• It also defines Enterprise Architecture Planning (EAP).• EAP focuses on defining what data, applications and technology
architectures are appropriate for and support the overall enterprise.
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
EAP
71
EAP and Zachman
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
72
FEA Models
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
How the models (according to Zachman’s framework) relate to FEA.
73
Discussion and example case
• FEA and FEAF were originally designed for the federal US government.
• Can FEA be applied to private enterprises?
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Cath, CEO Fred, FEA Consultant
74
FEA and MAM-EA• Build enthusiasm for MAM-EA.• Build a governance structure – FEA Project Management Office
(PMO).• Create reference models (PRM, BRM, TRM, DRM, SRM) that can
be used by all the organisations across MedAMore.• Create a desription of a reference architecture as it applies to
MedAMore.• Test drive the segment architecture process.• Analyse and prioritise the segments.• Enterprise Architecture program assessment.• Restart process with a new segment.
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Fred, FEA Consultant
75
Comparing EA Approaches
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
76 How can we choose an EA methodology?• Go through the criteria for comparing and evaluating EA
methodologies, that are important for your organisation.• Rate the methodologies.
What you may find out is that you need a blended approach, in which you create your own enterprise architecture, taking parts of different methodologies that provide the highest value for your specific needs.
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
77
Discussions
• Several different EA Methodologies, quite different from one another.
• Some of the methodologies complement one another, e.g. Zachman framework provides a taxonomy while TOGAF provides a process.
• Enterprise architecture is a path, not a destination.• Main goal: to bring alignment to the business side and
the technology side.
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
x
x
78
Summary
• We have looked at several Enterprise Architecture methodologies: Zachman, TOGAF, Gartner and FEA.
• We have compared them by using a case study.
• Can we similarities and differences between EA and Enterprise Modelling as we have discussed in this course?
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
79
What next?
• Term paper presentations:– 29 March 2012, 0815-1100hrs, MA21
TDT4252, Spring 2012Lecture 15 – Enterprise Architecture, TOGAF, Gartner, FEA
Top Related