TOGAF 9 Fundamental
Romi Satria Wahono
romi@romisatriawahono.net
http://romisatriawahono.net
081586220090
Romi Satria Wahono
•
•
•
•
•
•
•
•
SD Sompok Semarang (1987)
SMPN 8 Semarang (1990)
SMA Taruna Nusantara Magelang (1993)
B.Eng, M.Eng and Dr.Eng (on-leave)
Department of Computer Science
Saitama University, Japan (1994-2004)
Research Interests: Software Engineering and
Intelligent Systems
Founder IlmuKomputer.Com
LIPI Researcher (2004-2007)
Founder and CEO PT Brainmatics Cipta Informatika
2
Textbooks
3
Course Outline
1.
2.
3.
4.
5.
6.
7.
Introduction
Basic Concepts
Core Concepts
Key Terminology
ADM Introduction
UML Introduction
TOGAF Case Study
4
PreTest
1. Apa tugas atau pekerjaan utama anda saat ini?
2. Apa itu enterprise architecture dan mengapa kita harus
menggunakannya?
3. Apa itu enterprise architecture framework dan mengapa
kita harus menggunakannya?
4. Modelkan business process dari requirement di bawah
dengan use case diagram dan activity diagram/bpmn!
SISTEM ELIBRARY
• Sistem elibrary memungkinkan pengguna untuk melakukan
registrasi dan login
• Setelah menjadi member, pengguna dapat memodifikasi profile,
serta mencari dan mendownload koleksi buku elibrary
• Admin sistem elibrary melakukan approval terhadap registrasi
dan menampilkan laporan aktifitas pengguna secara individual
maupun total
5
1. Introduction
6
1.1 What and Why Enterprise
Architecture
7
What is an Enterprise?
• A collection of organizations that share a
common set of goals, such as a government
agency, part of a corporation, or a
corporation in its entirety
• Large corporations may comprise multiple
enterprises
• An “extended enterprise” can include
partners, suppliers, and customers
8
What is Architecture?
• The organizational structure of a system or
component
(IEEE Standard 610, Standard Computer Dictionary: A Compilation of
IEEE Standard Computer Glossaries)
• The fundamental organization of a system
embodied in its components, their relationships
to each other, and to the environment, and the
principles guiding its design and evolution
(IEEE Standard 1471, IEEE Recommended Practice for Architectural
Description of Software-Intensive Systems)
9
What is Architecture?
1. A formal description of a system, or a
detailed plan of the system at a component
level to guide its implementation
2. The structure of components, their interrelationships, and the principles and
guidelines governing their design and
evolution over time
10
What is Enterprise Architecture?
The organizing logic for business processes and IT
infrastructure reflecting the integration and
standardization requirements of the firm’s
operating model
(MIT Center for Information Systems Research)
A conceptual blueprint that defines the
structure and operation of an organization.
The intent of an enterprise architecture is to
determine how an organization can most
effectively achieve its current and future
objectives
(SearchCIO.com)
11
12
13
14
15
16
17
Why do I Need an Enterprise
Architecture (EA)?
18
Why do I Need an Enterprise
Architecture (EA)?
19
Why do I Need an Enterprise
Architecture (EA)?
20
Why do I Need an Enterprise
Architecture (EA)?
21
Why do I Need an Enterprise
Architecture (EA)?
22
Why do I Need an Enterprise
Architecture (EA)?
23
Why do I Need an Enterprise
Architecture (EA)?
24
Why do I Need an Enterprise
Architecture (EA)?
25
Why do I Need an Enterprise
Architecture (EA)?
26
Why do I Need an Enterprise
Architecture (EA)?
27
Why do I Need an Enterprise
Architecture (EA)?
28
Why do I Need an Enterprise
Architecture (EA)?
29
Why do I Need an Enterprise
Architecture (EA)?
The purpose of enterprise architecture is
to optimize across the enterprise:
Fragmented Legacy of Processes
Integrated Environment
(that is responsive to change and supportive of the
delivery of the business strategy)
30
Why do I Need an Enterprise
Architecture (EA)?
Ultimately, the benefits of enterprise
architecture derive from the better
planning, earlier visibility, and more
informed designs that result when it is
introduced
(Read Article: Simon Townson, Why Does Enterprise Architecture Matter?)
31
The Advantages of Good EA
Advantages
Description
A more efficient
business
operation
•
•
•
•
•
•
A more efficient
IT operation
• Lower software development, support, and
maintenance costs
• Increased portability of applications
• Improved interoperability and easier system and
network management
• Improved ability to address critical enterprise-wide
issues like security
• Easier upgrade 32and exchange of system components
Lower business operation costs
More agile organization
Business capabilities shared across the organization
Lower change management costs
More flexible workforce
Improved business productivity
The Advantages of Good EA
Advantages
Description
Better return on
existing
investment,
reduced risk for
future
investment
• Reduced complexity in the business and IT
• Maximum return on investment in existing business
and IT infrastructure
• The flexibility to make, buy, or out-source business
and IT solutions
• Reduced risk overall in new investments and their
cost of ownership
Faster, simpler,
and cheaper
procurement
• Buying decisions are simpler, because the
information governing procurement is readily
available in a coherent plan
• Maximizing procurement speed and flexibility
without sacrificing architectural coherence
• The ability to procure heterogeneous, multi-vendor
open systems
33
• The ability to secure
more economic capabilities
Enterprise Architecture Layer
Architecture Type
Description
Business
Architecture
The business strategy, governance, organization, and
key business processes
Data Architecture
The structure of an organization's logical and
physical data assets and data management
resources
Application
Architecture
A blueprint for the individual applications to be
deployed, their interactions, and their relationships
to the core business processes of the organization
Technology
Architecture
The logical software and hardware capabilities that
are required to support the deployment of business,
data, and application services. This includes IT
infrastructure, middleware, networks,
communications,
processing, and standards
34
35
1.2 What and Why Enterprise
Architecture Framework?
36
What is an Architecture Framework?
A foundational structure, or set of structures,
which can be used for developing a broad range
of different architectures:
• Describe a method for designing a target state of the
enterprise in terms of a set of building blocks, and for
showing how the building blocks fit together
• Contain a set of tools and provide a common
vocabulary
• Include a list of recommended standards and compliant
products that can be used to implement the building
blocks
37
Why do We Need a Framework for
Enterprise Architecture?
• Using an architecture framework will speed
up and simplify architecture development
• Ensure more complete coverage of the
designed solution
• Make certain that the architecture selected
allows for future growth in response to the
needs of the business
38
1.3 Major Enterprise Architecture
Framework
39
History of EA Framework
40
Major EA Framework
1. The Zachman Framework for Enterprise Architectures
• Although self-described as a framework, is actually more
accurately defined as a taxonomy
2. The Open Group Architectural Framework (TOGAF)
• Although called a framework, is actually more accurately
defined as a process
3. The Federal Enterprise Architecture(FEA)
• Can be viewed as either an implemented enterprise
architecture or a proscriptive methodology for creating an
enterprise architecture
4. The Gartner Methodology
• Can be best described as an enterprise architectural practice
41
Zachman Framework
42
TOGAF
43
FEA
44
1.4 EA Comparison
Read Article: Sessions - A Comparison of the Top Four EA
Methodologies - 2007
45
Comparison Parameters
1.
Taxonomy completeness: how well you can use the methodology to
classify the various architectural artifacts (Zachman)
2.
Process completeness: how fully the methodology guides you through
a step-by-step process for creating an enterprise architecture (TOGAF)
3.
Reference-model guidance: how useful the methodology is in helping
you build a relevant set of reference models (FEA)
4.
Practice guidance: how much the methodology helps you assimilate
the mindset of enterprise architecture into your organization (Gartner)
5.
Maturity model: how much guidance the methodology gives you in
assessing the effectiveness and maturity of different organizations
within your enterprise in using enterprise architecture
6.
Business focus: whether the methodology will focus on using
technology to drive business value, in which business value is
specifically defined as either reduced expenses and/or increased
income
46
Comparison Parameters
7.
Governance guidance: how much help the methodology will
be in understanding and creating an effective governance
model for enterprise architecture
8. Partitioning guidance: how well the methodology will guide
you into effective autonomous partitions of the enterprise,
which is an important approach to managing complexity
9. Prescriptive catalog: how well the methodology guides you in
setting up a catalogue of architectural assets that can be
reused in future activities
10. Vendor neutrality: how likely you are to get locked-in to a
specific consulting organization by adopting this methodology.
A high rating here indicates low vendor lock-in
11. Information availability: the amount and quality of free or
inexpensive information about this methodology
12. Time to value: the length of time you will likely be using this
methodology before you start using it to build solutions that
deliver high business value
47
EA Comparison
(Roger Sessions, A Comparison of the Top Four EA Methodologies, 2007)
48
Hybrid Enterprise Architecture
49
1.5 Enterprise Architecture Tools
Read Article: Short - Gartner Assessment EA Tool - 2011
50
EA Tools
•
•
•
•
•
•
•
•
•
•
•
•
planningIT (alphabet.com)
SAMU (altollgroup.eu)
Abacus (avolution.com.au)
Architect (bizzdesign.com)
Corporate Modeler (casewise.com)
Envision VIP (future-tech.com)
Rational System Architect (ibm.com)
Mega Suite (mega.com)
ProVision (metastorm.com)
MooD (tsorg.com)
ARIS (softwareag.com)
Enterprise Architect (sparxsystems.com)
51
Comparison Parameters
1.
2.
3.
4.
5.
6.
7.
8.
Repository or Metamodel
Modeling
Decision Analysis
Presentation
Administration
Configurability
Frameworks and Standards
Usability
(Julie Short and Chriss Wilson, Gartner Assessment of EA Tool Capabilities, Gartner Research, 2011)
52
planningIT (alphabet.com)
53
SAMU (altollgroup.eu)
54
Abacus (avolution.com.au)
55
Architect (bizzdesign.com)
56
Corporate Modeler (casewise.com)
57
Envision VIP (future-tech.com)
58
Rational System Architect (ibm.com)
59
Mega Suite (mega.com)
60
ProVision (metastorm.com)
61
MooD (tsorg.com)
62
ARIS (softwareag.com)
63
Enterprise Architect (sparxsystems.com)
64
1.6 Enterprise Architecture
Competency
65
Key Competencies to Create an
Enterprise Architecture
1. Enterprise Architecture Framework
2. Enterprise Architecture Tools
3. Business Strategy and Organization Analysis 
Business Model Canvas
4. Business Process Model and Notation (BPMN)
5. Data Modeling
6. Unified Modeling Language (UML)
7. Infrastructure and Network Design
66
67
Business Model Canvas
PT Brainmatics Cipta Informatika
Key Activities
Key Partners
Software
Development
Pearson
Vue
Kryterion
Online
Prometrics
Training
Center
Certification
Examination
Brand IlmuKomputer.Com
International Authorized
Training and Testing
Center
Pengembangan
Software dengan
Metodologi Standard
Internasional
Peserta Ujian
Sertifikasi
Lembaga
Pendidikan
Telepon
Brainmatics.Com
Lembaga
Pemerintahan
Instant Messaging
(YM, WA, Line, BBM)
Social Media
(Kaskus, Facebook, Twitter)
Biaya
Operasional
Penjualan
Jasa Training
Gaji Pegawai
Mahasiswa
Revenue Streams
Cost Structure
Honor Pengajar
Staff IT
Channels
Email
Online Market
Food
Court
Offline: Kegiatan
Workshop dan Training
Online: Social Media
Participation, Situs
Brainmatics.Com
Kurikulum
Brand Romi Satria Wahono
Customer
Segments
Dosen
Ruang Kelas Nyaman
dan Posisi di Tengah
Kota Jakarta
Pegawai
Penerbit dan
Distributor Buku
Kurikulum Internasional
dan Customizable
dengan Kebutuhan
Pengajar dengan
Kompetensi Terpadu
Akademisi dan Industri
Key Resources
Percetakan
Customer
Relationships
Value
Propositions
Biaya
Infrastruktur
Biaya Marketing
Penjualan
Produk Software
Perusahaan
Swasta
UML
Use-Case
Diagram
Statechart
Diagram
Class Diagram
add file
DocumentList
Use Case 1
FileMgr
Actor A
Actor B
Document
add( )
delete( )
fetchDoc( )
sortByName( )
name : int
docid : int
numField : int
get( )
open( )
close( )
read( )
sortFileList( )
create( )
fillDocument( )
Use Case 2
FileList
fList
add( )
delete( )
Writing
add file [ numberOffile==MAX ] /
flag OFF
read() fill the
code..
Openning
close file
1
Use Case 3
close file
Reading
Closing
rep
Repository
(from Persistence)
File
read( )
GrpFile
name : char * = 0
readDoc( )
readFile( )
Collaboration
Diagram
read( )
open( )
create( )
fillFile( )
9: sortByName ( )
Repository
mainWnd : MainWnd
1: Doc view request ( )
DocumentList
Deployment
Diagram
Windows95
Window95
FileManager
Windows95
L
2: fetchDoc( )
Document
gFile : GrpFile
4: create ( )
¹®¼°ü¸®
Ŭ¶óÀ̾ðÆ®.EXE
¹®¼°ü¸® ¾ÖÇø´
Windows
NT
8: fillFile ( )
user : Clerk
Solaris
fileMgr : FileMgr
¹®¼°ü¸® ¿£Áø.EXE
GraphicFile
3: create ( )
Alpha
UNIX
ÀÀ¿ë¼¹ö.EXE
6: fillDocument ( )
File
FileList
Windows
NT
IBM
Mainframe
7: readFile ( )
5: readDoc ( )
document : Document
repository : Repository
µ¥ÀÌŸº£À̽º¼¹ö
mainWnd
fileMgr :
FileMgr
user
ƯÁ¤¹®¼¿¡ ´ëÇÑ º¸±â¸¦
»ç¿ëÀÚ°¡ ¿äûÇÑ´Ù.
document :
Document
1: Doc view request ( )
2: fetchDoc( )
gFile
repository
Component
Diagram
Target
System
3: create ( )
4: create ( )
5: readDoc ( )
ÈÀÏ°ü¸®ÀÚ´Â Àоî¿Â
¹®¼ÀÇ Á¤º¸¸¦ ÇØ´ç ¹®¼
°´Ã¼¿¡ ¼³Á¤À» ¿äûÇÑ´Ù.
6: fillDocument ( )
7: readFile ( )
8: fillFile ( )
È¸é °´Ã¼´Â ÀоîµéÀÎ
°´Ã¼µé¿¡ ´ëÇØ À̸§º°·Î
Á¤·ÄÀ» ½ÃÄÑ È¸é¿¡
º¸¿©ÁØ´Ù.
Forward and
Reverse
Engineering
9: sortByName ( )
Sequence
Diagram
69
BPMN
70
Data Modeling
71
Test Yourself Questions
Which one of the following best describes why you
need a framework for enterprise architecture?
A. Architecture design is complex
B. Using a framework can speed up the process
C. Using a framework ensures more complete
coverage
D. A framework provides a set of tools and a
common vocabulary
E. All of these
72
Test Yourself Questions
Which of the following are the architecture domains
that are commonly accepted subsets of an overall
enterprise architecture?
A.
B.
C.
D.
Application, Business, Data, Technology
Capability, Segment, Strategic
Context, Definition, Governance, Transformation
Definition, Realization, Transition, Vision
73
Test Yourself Questions
Which one of the following best describes an
enterprise architecture?
A. An architecture of a commercial organization
B. An architecture that consists of more than one
subsidiary company
C. An architecture that crosses multiple systems,
and multiple functional groups within the
enterprise
D. The highest level of architecture that can be
achieved in a given organization
74
References
1.
2.
3.
4.
5.
6.
7.
Rachel Harrison, Study Guide TOGAF® 9 Foundation 2nd Edition,
The Open Group, 2011
Rachel Harrison, Study Guide TOGAF® 9 Certified 2nd Edition,
The Open Group, 2011
Open Group Standard, TOGAF® Version 9.1 (G116), The Open
Group, 2011
Open Group Standard, TOGAF® Version 9.1 – A Pocket Guide
(G117), The Open Group, 2011
Daniel Minoli, Enterprise Architecture A to Z: Frameworks,
Business Process Modeling, SOA, and Infrastructure
Technology, Taylor & Francis, 2008
Jon Holt and Simon Perry, Modelling Enterprise Architectures,
The Institution of Engineering and Technology, 2010
Alan Dennis et al, Systems Analysis and Design with UML 4th
Edition, John Wiley and Sons, 2013
75