Enterprise Architecture linking to Chess and Lego games , and main capabilities of EA framework , concentrating on Togaf as common Enterprise architecture framework.
8. Enterprise Definition
Enterprise
Any collection of organizations that has a common set of goals
Large corporations may comprise multiple enterprises.
Extended Enterprise
comprises the partners, suppliers, and customers, as well as internal
business units.
Enterprise Can Be
▷Single department
▷ Chain of geographically distant organizations
linked together by common ownership.
▷Government Agency
▷Whole Corporation
▷Division of a corporation
9. Architecture Definition
Definition 2
Structure of components, their inter-relationships, and principles and
guidelines governing their design and evolution over time
Definition 1
Formal Description or Detailed plan Of system at component level
to guide its implementation
10. Enterprise Architecture Definition
Conceptual blueprint
Defines the structure and operation of an organization
EA Intent to determine how to achieve current and future
objectives of organization
Mapping Business into IT
The organizing logic for business processes and IT
infrastructure reflecting integration and standardization
requirements of firm’s operating model.
Share same purpose with SOA
12. Chess & EA Analogy
Chess shares same concerns with situation in Enterprise Architecture
Making and implementing a design decision in the organization
is suggested as an analogy to making a ‘move’ in chess.
complexity unpredictability
13. Chess Tips & EA
Tip #1 : Chess Move
Chess players generally do not make a move with an ‘end state’ in mind.
Chess players work from the current state and think of moves that
strengthen their position
✓ Enterprise Architects should do the same ,
Do not focus on the unpredictable future too much,
Focus on making the best changes
(improving your position) now
14. Chess Tips & EA
Tip #2 : Tactical rules
Tactical rules in chess are not predictive but descriptive ( Competitive advantage )
Following the rule does not by definition lead to good moves.
A good chess player Does not follow the rules , The rules are embedded in his skills
without being exactly visible during play
✓ Same is true for design rules in Enterprise Architecture
Good architecture shows the rules,
BUT that doesn’t mean that following
the rules leads to good architecture
15. Chess Tips & EA
Tip #3 : Sometimes a pawn is decisive
Sometimes, the fact that lowly pawn is just one square move forward may open or close
up entire scenario
Some cases may even determine the differences between winning or loosing.
In Chess , You can’t ignore details , you must pay attention to the relevant ones.
✓ Same is true in Enterprise Architecture
Some details are relevant and ignoring that leads
to project dramas as well.
The road to landscape hell ( & project fail) is based on
grand-over simplified design (irrelevant details)
16. Chess Tips & EA
Tip #4 : The Chess Player
Master chess players don’t calculate much deeper than good amateurs
What master chess players have is ‘a superior estimation’ of
where the good moves are likely to be.
✓ The same is true for enterprise architects
Enterprise Architects need to have a good estimation,
what next improvement (move) need to
take place (change)
Which is why applying the logical structure of
frameworks does not really help all that much.
17. Chess & EA
Chess is actually very simple, the
field is just 64 squares, there are
only 6 types of piece, the current
position can be perfectly known,
players neatly take turns
In real organizations the ‘board’ is
huge, the squares overlap,
the rest of the board changes while
you are ‘making a move’
(implementing a change),
many players all act simultaneously
on that same board, and the
strategic goals are complex, vague
and even contradictory compared
to chess (checkmate!).
Enterprise Architecture is the Chess Game from Hell.
19. EA & Lego Tips
Tip #1 : Lego box is a store for all building blocks
✓ The same is true for enterprise architecture
should have clearly structure Architecture repository ,
that contains all assets (Architecture BB , Solutions BB)
20. EA & Lego Tips
Tip #2 : Reusable building blocks
✓ The same is true for enterprise architecture
A building block is re-usable and replaceable, and well specified.
Same concepts with SOA
21. 2 Core Concepts
▷What & How Concepts
▷Architecture Framework Structure
▷Architecture Domain
▷Architecture Frameworks
▷Togaf Standard
22. What & How Concepts
Building Blocks
(WHAT)
Differentiators
(HOW)
Process (HOW)
Function (WHAT)
▷How can I do something ?
▷Differentiators point of views
▷ Eg : How I Make Coffee ?
▷Identify what you have ?
▷Basic unit from which something is built up.
▷What Building blocks you have ?
▷Eg : What I Have to Make Coffee ?
Everything about architecture relates to these concepts
23. Architecture Framework Definition
Foundational Structure used for
developing range of different
architectures
Common Vocabulary
And set of tools
Recommended standards
& compliant products
Method for designing Enterprise
Target state ( building blocks)
24. Why do I need a framework for enterprise architecture ?
Future Growth
Allow respond to future needs of business
(Responsive to change)
Simplify & Speedup
Architecture Development
Complete Coverage
Ensure coverage of desired solution
25. Architecture Framework Structure
Metamodel
Consume
B.B
Add
B.B
Architecture Model
Method
Categorization System
Architecture Model
To Build
▷The way to do architecture
▷Cycle for develop architecture work
▷Lego Box for your building blocks
▷Classify your building blocks
▷Consider Stakeholders Concerns
▷Cover Stakeholder views and viewpoints
Metamodel
▷How, with what you described architecture structure
▷Start point to do EA in your enterprise
26. Architecture Domains
Technology Architecture
Software and Hardware capabilities
IT infrastructure, middleware,
Networks, communications,
Processing, and standards.
Business Architecture
Business strategy
Governance
Organization
business processes.
People
Application Architecture
Application blueprint
Applications Interaction
Relation to business processes
Data Architecture
Logical data assets
Physical data assets
Data management.
27. Why we need Enterprise Architecture ?
Optimize Across Enterprise
[fragmented – legacy processes
into integrated environment ]
that is Responsive To Change
Support Delivery of
Business Strategy
[ Business Alignment]
Management and exploitation
of information through IT
Achieving Competitive Advantage
Providing a Strategic Context for IT in
response to constantly change of
business needs
30. What is Togaf Standard ?
Tool Applying Enterprise Architecture
assist in acceptance, production, use, and maintenance of EA
Iterative process model
ADM method is heart of Togaf to build EA that meet business needs.
Supported by best practices and a re-usable architectural assets.
Architecture Framework
Togaf standard is architecture framework that can be use in
conjunction with other frameworks
31. What is Togaf Standard ?
▷Togaf developed and maintained by the open group architecture forum
▷The original development of TOGAF Version 1 in 1995
▷Togaf was based on the Technical Architecture Framework for Information
Management (TAFIM), developed by the US Department of Defense (DoD).
▷The DoD gave The Open Group explicit permission and encouragement to
create TOGAF by building on the TAFIM
33. Togaf & Other Frameworks
▷TOGAF is a generic framework and it is expected that the architect will adapt
and build on the TOGAF to create an organization-specific framework
▷The generic TOGAF deliverables may be replaced or extended by deliverables
defined in any other relevant framework E.g.: ITIL, CMMI, COBIT, PRINCE2,
PMBOK, etc.
▷TOGAF also complements other frameworks that are aimed at specific
vertical business domains, specific horizontal technology areas
(such as security or manageability), or specific application areas
(such as e-Commerce)
35. What does Togaf Standard contains ?
Part I : Introduction
1 High-level introduction to the key concepts of enterprise architecture
2 Contains definitions of terms , Togaf certification path
36. What does Togaf Standard contains ?
Part II : Architecture Development Method (ADM)
1 Step-by-step approach to developing an enterprise architecture
2
Provide architecture development phases in a cycle
[overall process template for architecture development activity]
3 Cross-phase summaries that cover requirements management.
4
Narrative of each architecture phase
[objectives, approach, inputs, steps, and outputs]
37. Part III : ADM Guidelines and techniques
1
Guidelines address adapting the ADM to deal with a number of usage
scenarios
(e.g,. the use for iteration) also specific specialty architectures ( such as security)
2
Techniques support specific tasks within the ADM
(such as defining principles, business scenarios, gap analysis , etc.)
Part III : Architecture Content Framework
1
Detailed model of architectural work products, including deliverables,
artifacts within deliverables and Architecture Building Blocks (ABBs)
What does Togaf Standard contains ?
38. Part V : Enterprise Continuum & Tools
1 Model for structuring a virtual repository
2
Methods for classifying architecture and solution artifacts
[ foundation – common systems – industry - organization specific]
Part VI : TOGAF Reference Models
1
TRM : TOGAF Technical Reference Model
[Generic services architecture to provide foundation to build specific
architecture]
2 III-RM : Integrated Information Infrastructure Reference Model
[Based on the TOGAF Foundation Architecture]
What does Togaf Standard contains ?
39. Part VII : Architecture Capability Framework
1
Set of resources, guidelines, templates, responsibilities ,background
information, etc.
2 Help the architect establish an architecture practice within an organization
What does Togaf Standard contains ?
40. 4 EA Game Store
( Continuum , Repository)
▷Categorization system
▷Architecture Repository
43. Categorization system
Arch.
Cont.
Solu.
Cont.
Foundation
Architecture
CommonSys.
Architecture
Industry
Architecture
Org.specific
Architecture
Generic Specific
Lego Box ( Enterprise Continuum)
Foundation Architecture
Generic components, inter-relationships, principles, and
guidelines that provide a foundation on which more
specific architectures can be built
Common Systems Architecture
Use services in Foundation Architecture to create an architecture
useful for building common Solutions (high reusable)
across a wide number of relevant domains.
Industry Architecture
Integration of common systems components with
industry-specific components (certain vertical industries)
Organization Specific Architecture
Describe and guide the final deployment of solution
components for a particular enterprise
B
D
A
T
B
D
A
T
Metamodel
48. SOA Reference Model
▷SOA is architecture style for
Enterprise Architecture
▷Related to BDAT Architecture Domains
Business Service
Data Service
Application Service
Infrastructure Service
49. Architecture Partitioning
▷ Allows for direction setting at an executive level.
Strategic Architecture
Segment Architecture
▷ Allows for direction setting and the development of
effective architecture roadmaps at a program or
portfolio level.
Capability Architecture
▷ Development of effective architecture
roadmaps realizing capability increments.
51. Architecture Repository
Standard Information Base (SIB)
Architecture Metamodel
Architecture Capability
Architecture Landscape
Describes the organizationally tailored application of an architecture framework,
including a metamodel for architecture content
Defines the parameters, structures, and processes that support governance of
the Architecture Repository
Architectural representation of assets deployed within the operating enterprise at a
particular point in time , for specific partition (Strategic , segment , capability)
Captures the standards with which new architectures must comply, which may
include industry standards, selected products and services from suppliers, or
shared services already deployed within the organization
52. Architecture Repository
Solutions Landscape
Reference Library
Governance Log
Architecture Requirements Repository
Provides guidelines, templates, patterns, and other forms of reference material that can be
leveraged in order to accelerate the creation of new architectures for the enterprise
Provide a record of governance activity across the enterprise
Provides a view of all authorized architecture requirements which have been agreed
with the Architecture Board
Presents an architectural representation of the SBBs supporting the Architecture
Landscape which have been planned or deployed by the enterprise
53. Architecture Landscape
Stakeholder LeaveArchitecture Landscape
▷Architecture models over time ( years)
▷EA as strategic enabler , help business decisions
▷Enterprise planning space where EA can add true value
Business intelligence – Business Analytics
Architecture
Model 1
Architecture
Model 2
Architecture
Model 3 Capability
Strategic
Segmente
d
In Y 2000
Revenue
40M$
In Y 2001
Revenue
50M$
In Y 2002
Revenue
20M$
Why enterprise lose revenue ?
55. Architecture Development Method ( ADM)
▷Add and Consume B.B
▷Can Apply Iterations ( ADM Guidelines)
▷Can apply on different levels of details (Segmentation)
▷Repeatable process for developing Architectures
▷Include Establish Architecture Framework , develop Architecture
content , Transitioning , govern realization of architectures
▷Iterative Cycle of Continuous architecture definition
▷Transform enterprise in response to business goals and
opportunities
ADM focus Points
56. ADM Phases
Preliminary Phase
Determine the Architecture Capability
▷Review the organizational context
▷Identify the established frameworks, methods, and processes
that intersect with architecture capability
▷Establish Capability Maturity target
Establish Architecture Capability
▷Establish Organizational Model for EA
▷Establish the detailed process for Architecture Governance
▷Define architecture principles
▷Select & implement tools to support Architecture Capability
57. ADM Phases
Phase A : Architecture Vision
▷Develop Vision of the capabilities and business value to be
delivered for [iteration , partitioning ]
▷Define scope , identify stakeholders , obtain approvals
Prelim
VisionVision
Vision
Phase Phase Phase
58. ADM Phases
Phase B : Business Architecture
▷Develop target business architecture that describes how the
enterprise needs to operate to achieve the business goals,
respond to strategic drivers
▷Identify candidate Architecture Roadmap components , based
on gaps between target and baseline business architecture
59. ADM Phases
Phase C : Information System Architecture
▷Develop target Application/Data architecture , that enables the Business
Architecture and the Architecture Vision, to address stakeholder concerns
▷Identify candidate Architecture Roadmap components ,
based on gaps between target and baseline
Application/Data architecture
60. ADM Phases
Phase D : Technology Architecture
▷Develop target Technology architecture that enables the Architecture Vision,
target business, data, and application building blocks to be delivered through
technology components and technology services , to address
stakeholder concerns.
▷Identify candidate Architecture Roadmap components , based
on gaps between target and baseline Technology architecture
61. ADM Phases
Phase E : Opportunities and solutions
▷identify major implementation projects group them into work packages
▷Start Establish implementation , migration plan
▷Solution Architect involved in this phase
62. ADM Phases
Phase F : Migration Planning
▷Detailed implementation and migration plan by PMO
▷Include [ cost , time , effort , resources ,
critical projects and align other projects
(strategic , segmented , capability)]
63. ADM Phases
Phase G : Implementation Governance
▷Handover your projects to be implemented by
[ internal dev team , vendor , outsource]
▷Compliance architecture to our business
[I Give you this / You deliver this / What is the gaps]
64. ADM Phases
Phase H : Architecture Change Management
▷Ensure that the architecture lifecycle is maintained
▷Ensure that the Architecture Governance Framework is
executed
▷Ensure that the Enterprise Architecture Capability
meets current requirements
65. 6 Architecture Content Framework
▷Content Metamodel
▷Views – Viewpoints
▷Build Your enterprise Reference Model
▷Artifacts, Deliverables, and Building Blocks
70. Architecture Model
Consume
B.B
Add
B.B
Architecture Model
To Build
▷The representation of a related set of concerns
( Issues , Risks , Assumptions , Constraints) of stakeholder
▷A view is what is seen from a viewpoint.
▷Anything that matter to stakeholders (How they see the world right)
▷Outcome of ADM , Pull B.B to build Architecture Model
▷Give view of you organization
▪ At different states
▪ Across different times
Views
Viewpoint
▷Definition of the perspective from which a view is taken.
72. Handler Stakeholder Concerns Stakeholder
Lego Box
Concerns Requirements
Architecture Model
Building Blocks
Model Model Model
View
Function (What)
Process(How) Viewpoint
74. How to build your enterprise reference model
Consume
B.B
Add
B.B
Architecture Model
To Build
▷Repeat ADM
▷Build Architecture Model and scale it
▷Contain all stakeholders views , concerns and viewpoints
across your organization
Reference
Model
Stakeholders
Views &
Viewpoints
85. Architecture Maturity Model
Isolated
I
Losing
L
Optimized
O
Fragmented
F
Level of Organization Integration Delivery
LevelofArchitectureThinking
Organization become tactical thinking
[project focus – solution focus]
F I Organization become Strategic thinking
I F
Maturity Low High
Losing No Delivery , No Arch. Thinking -
Isolated Business not well Delivered
Architecture don’t add value
Great Architecture Thinking
Fragmented No log term focus A lot of tactical projects focused
Optimized - Great Architecture Thinking
Organization solutions delivered well
86. EA gaps with SA & PMO
EA
Gap
Try to fill gaps without full information
SA
Failed Compliance review with architecture
DeliveryPMOEAProblem
Solution
+ Cost
+ Timeline
+ Quarter Measures
+ Strategy
Resistance
80 %
20 %
Architecture Iteration 1
Architecture Iteration 2
Architecture Iteration 3
Reduce Gap
Increase Maturity
Architecture
Governance
Measure organization Steps to reduce gap
Architecture Governance
87. EA Scope/Value Graph
Notes
Scope of EA
ValueofEA
EA = ITA
EA = EWITA
EA = BA + EWITA
EA = SA + BA + EWITA
A
B
Levels of Maturity ( EA Seen from Business View)
▷Each step between A-B ,
you will cycle in Maturity model
▷Move from point A-B
▷Most organizations in point A
▷True value of EA in point B
Enterprise Planning
▷Show true Value of EA
▷Help to take decisions
▪ Business Planning
▪ Business Analytics
▪ BI
▪ EA
▷We are not deliver building blocks
▷Architecture work not seen by business people
▷They need something help them to take decisions
91. Guidelines & Techniques
Guidelines and techniques
1
Guidelines address adapting the ADM to deal with a number of usage
scenarios
(e.g,. the use for iteration) also specific specialty architectures ( such as security)
2
Techniques support specific tasks within the ADM
(such as defining principles, business scenarios, gap analysis , CBP , etc.)
93. Iteration between ADM Cycles
Each iteration completes an ADM cycle at
a single level of Architecture Description.
This approach to the ADM uses Phase F
(Migration Planning) to initiate new more
detailed architecture development projects.
94. Iteration within an ADM Cycle
▷Architecture Capability Iteration
▷Architecture Development Iteration
▷Architecture Transition Iteration
▷Architecture Governance Iteration
97. ADM Iterations – Architecture Development Iteration
1. Define stakeholders view , viewpoints , concerns
2. Reference model if exist , Building blocks if exist
3. AS-IS architecture according to vision
4. TO-BE architecture
5. GAP analysis between AS-IS and TO-BE
Phase B – Phase C – Phase D
Above steps depends of Vision of iteration
Step may be not exist according to Vision
108. Togaf Certification for People Program
Togaf 9.1 Foundation
▷Foundation Concepts and core Concepts of Togaf Framework
▷Learning objective towards achieving TOGAF 9 Certified
▷40 multiple-choice questions
Togaf 9.1 Certified
▷Analyze and apply this knowledge of Foundation concepts.
▷Apply Togaf into more practical scenarios
▷8 complex scenario questions
109. Togaf Foundation Certification Process
▷Basic Concepts (3 questions)
▷Core Concepts (3 questions)
▷Introduction to the ADM (3 questions)
▷ADM Phases (9 questions)
▷ADM Guidelines and Techniques (6 questions)
▷The Enterprise Continuum and Tools (4 questions)
▷Building Blocks (2 questions)
▷ADM Deliverables (2 questions)
▷Architecture Views, Viewpoints, and Stakeholders (2 questions)
▷Architecture Governance (4 questions)
▷TOGAF Reference Models (2 questions)
110. Togaf Certified Certification Process
▷ADM Phases: Project Establishment (Phases Preliminary, A, Requirements
Management)
▷ADM Phases: Architecture Definition (Phases B, C, D)
▷ADM Phases: Transition Planning (Phases E and F)
▷ADM Phases: Governance (Phases G and H)
▷Adapting the ADM
▷Architecture Content Framework
▷TOGAF Reference Models
▷Architecture Capability Framework
The eight scenarios are drawn from the following major topic areas:
Question Point System
▷5 Point – best answer
▷3 Point – 2nd best answer
▷1 Point – 3rd best answer
▷0 Point - distracter