TOGAF 9 Fundamental Romi Satria Wahono [email protected] 081586220090.
-
Upload
emily-waters -
Category
Documents
-
view
239 -
download
5
Transcript of TOGAF 9 Fundamental Romi Satria Wahono [email protected] 081586220090.
2
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 ScienceSaitama 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
3
Textbooks
4
Course Outline1. Introduction2. Basic Concepts3. Core Concepts4. Key Terminology5. ADM Introduction6. UML Introduction7. TOGAF Case Study
5
PreTest1. 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
6
1. Introduction
7
1.1 What and Why Enterprise Architecture
8
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
9
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)
10
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 inter-relationships, and the principles and guidelines governing their design and evolution over time
11
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)
12
13
14
15
16
17
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)?
30
Why do I Need an Enterprise Architecture (EA)?
The purpose of enterprise architecture isto optimize across the enterprise:
Fragmented Legacy of Processes
Integrated Environment
(that is responsive to change and supportive of the delivery of the business strategy)
31
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?)
32
The Advantages of Good EAAdvantages Description
A more efficient business operation
• Lower business operation costs• More agile organization• Business capabilities shared across the organization• Lower change management costs• More flexible workforce• Improved business productivity
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 and exchange of system components
33
The Advantages of Good EAAdvantages 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
• The ability to secure more economic capabilities
34
Enterprise Architecture LayerArchitecture 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
35
36
1.2 What and Why Enterprise Architecture Framework?
37
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
38
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
39
1.3 Major Enterprise Architecture Framework
40
History of EA Framework
41
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
42
Zachman Framework
43
TOGAF
44
FEA
45
1.4 EA Comparison
Read Article: Sessions - A Comparison of the Top Four EA Methodologies - 2007
46
Comparison Parameters1. 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
47
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
48
EA Comparison
(Roger Sessions, A Comparison of the Top Four EA Methodologies, 2007)
49
Hybrid Enterprise Architecture
50
1.5 Enterprise Architecture Tools
Read Article: Short - Gartner Assessment EA Tool - 2011
51
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)
52
Comparison Parameters
1. Repository or Metamodel2. Modeling3. Decision Analysis4. Presentation5. Administration6. Configurability7. Frameworks and Standards8. Usability
(Julie Short and Chriss Wilson, Gartner Assessment of EA Tool Capabilities, Gartner Research, 2011)
53
planningIT (alphabet.com)
54
SAMU (altollgroup.eu)
55
Abacus (avolution.com.au)
56
Architect (bizzdesign.com)
57
Corporate Modeler (casewise.com)
58
Envision VIP (future-tech.com)
59
Rational System Architect (ibm.com)
60
Mega Suite (mega.com)
61
ProVision (metastorm.com)
62
MooD (tsorg.com)
63
ARIS (softwareag.com)
64
Enterprise Architect (sparxsystems.com)
65
1.6 Enterprise Architecture Competency
66
Key Competencies to Create an Enterprise Architecture
1. Enterprise Architecture Framework2. Enterprise Architecture Tools3. Business Strategy and Organization Analysis
Business Model Canvas4. Business Process Model and Notation (BPMN)5. Data Modeling6. Unified Modeling Language (UML)7. Infrastructure and Network Design
67
Percetakan
Penerbit dan Distributor Buku
PearsonVue
Prometrics
Kryterion Online
Food Court
SoftwareDevelopment
CertificationExamination
TrainingCenter
Kurikulum Internasional dan Customizable dengan Kebutuhan
Ruang Kelas Nyaman dan Posisi di Tengah
Kota Jakarta
International Authorized Training and Testing
Center
Biaya Infrastruktur
Honor Pengajar
Gaji Pegawai Biaya Marketing
Pegawai
Online Market
Brand IlmuKomputer.Com
Brand Romi Satria Wahono
PenjualanJasa Training
Instant Messaging(YM, WA, Line, BBM)
Social Media(Kaskus, Facebook, Twitter)
Staff IT
LembagaPemerintahan
Peserta UjianSertifikasi
Lembaga Pendidikan
Perusahaan Swasta
Offline: Kegiatan Workshop dan Training
Online: Social Media Participation, Situs Brainmatics.Com
Brainmatics.Com
PenjualanProduk Software
Biaya Operasional
MahasiswaPengajar dengan
Kompetensi Terpadu Akademisi dan Industri
Business Model Canvas
TeleponKurikulum
Key Partners Key Activities
Pengembangan Software dengan
Metodologi Standard Internasional
ValuePropositions
Key Resources
CustomerRelationships
Channels
CustomerSegments
Revenue StreamsCost Structure
Dosen
PT Brainmatics Cipta Informatika
69
UML
Actor A
Use Case 1
Use Case 2
Actor B
user : Clerk
mainWnd : MainWnd
fileMgr : FileMgr
repository : Repositorydocument : Document
gFile : GrpFile
9: sortByName ( )
L1: Doc view request ( )
2: fetchDoc( )
5: readDoc ( )
7: readFile ( )
3: create ( )
6: fillDocument ( )
4: create ( )
8: fillFile ( )
Window95
¹®¼ °ü¸® Ŭ¶óÀ̾ðÆ®.EXE
WindowsNT
¹®¼ °ü¸® ¿£Áø.EXE
WindowsNT
Windows95
Solaris
ÀÀ¿ë¼ ¹ö.EXE
AlphaUNIX
IBM Mainframe
µ¥ÀÌÅ º̧£À̽º¼ ¹ö
Windows95
¹®¼ °ü¸® ¾ÖÇǿDocument
FileManager
GraphicFile
File
Repository DocumentList
FileList
user
mainWnd fileMgr : FileMgr
repositorydocument : Document
gFile
1: Doc view request ( )
2: fetchDoc( )
3: create ( )
4: create ( )
5: readDoc ( )
6: fillDocument ( )
7: readFile ( )
8: fillFile ( )
9: sortByName ( )
ƯÁ¤¹®¼ ¿¡ ´ëÇÑ º ±̧â ¦̧ »ç¿ëÀÚ°¡ ¿äûÇÑ´Ù.
È ÀÏ°ü¸®ÀÚ´Â Àоî¿Â ¹®¼ ÀÇ Á¤º¸̧ ¦ ÇØ´ç ¹®¼
°´Ã¼¿¡ ¼³Á¤À» ¿äûÇÑ´Ù.
È ̧é °´Ã¼´Â ÀоîµéÀÎ °´Ã¼µé¿¡ ´ëÇØ À̸§º°·Î
Á¤·ÄÀ» ½ÃÄÑ È ̧é¿¡ º ¿̧©ÁØ´Ù. Forward and
Reverse Engineering
TargetSystem
Openning
Writing
ReadingClosing
add file [ numberOffile==MAX ] / flag OFF
add file
close file
close fileUse Case 3
Use-CaseDiagram Class Diagram
Collaboration Diagram
Sequence Diagram
Component Diagram
StatechartDiagram
GrpFile
read( )open( )create( )fillFile( )
rep
Repository
name : char * = 0
readDoc( )readFile( )
(from Persistence)
FileMgr
fetchDoc( )sortByName( )
DocumentList
add( )delete( )
Document
name : intdocid : intnumField : int
get( )open( )close( )read( )sortFileList( )create( )fillDocument( )
fList
1
FileList
add( )delete( )
1
File
read( )
read() fill the code..
Deployment Diagram
70
BPMN
71
Data Modeling class DM - Sistem ATM
Login
«column»*PK idLogin: INTEGER pin: INTEGER
«PK»+ PK_Login(INTEGER)
Account
«column»*PK id: INTEGER nama: VARCHAR(50) alamat: VARCHAR(50) pekerjaan: VARCHAR(50) FK idLogin: INTEGER FK idBalance: INTEGER FK idTransaksi: INTEGER
«FK»+ FK_idBalance(INTEGER)+ FK_idLogin(INTEGER)+ FK_idTransaksi(INTEGER)
«PK»+ PK_Account(INTEGER)
Balance
«column»*PK idBalance: INTEGER saldo: INTEGER
«PK»+ PK_Balance(INTEGER)
Transaksi
«column»*PK idTransaksi: INTEGER tgl: DATE jenis: VARCHAR(50)
«PK»+ PK_Transaksi(INTEGER)
+idTransaksi
+PK_Transaksi
+idBalance +PK_Balance+idLogin+PK_Login
72
Test Yourself Questions
Which one of the following best describes why you need a framework for enterprise architecture?
A. Architecture design is complexB. Using a framework can speed up the processC. Using a framework ensures more complete
coverageD. A framework provides a set of tools and a
common vocabularyE. All of these
73
Test Yourself Questions
Which of the following are the architecture domains that are commonly accepted subsets of an overall enterprise architecture?
A. Application, Business, Data, TechnologyB. Capability, Segment, StrategicC. Context, Definition, Governance, TransformationD. Definition, Realization, Transition, Vision
74
Test Yourself Questions
Which one of the following best describes an enterprise architecture?
A. An architecture of a commercial organizationB. An architecture that consists of more than one
subsidiary companyC. An architecture that crosses multiple systems, and
multiple functional groups within the enterpriseD. The highest level of architecture that can be
achieved in a given organization
75
References
1. Rachel Harrison, Study Guide TOGAF® 9 Foundation 2nd Edition, The Open Group, 2011
2. Rachel Harrison, Study Guide TOGAF® 9 Certified 2nd Edition, The Open Group, 2011
3. Open Group Standard, TOGAF® Version 9.1 (G116), The Open Group, 2011
4. Open Group Standard, TOGAF® Version 9.1 – A Pocket Guide (G117), The Open Group, 2011
5. Daniel Minoli, Enterprise Architecture A to Z: Frameworks, Business Process Modeling, SOA, and Infrastructure Technology, Taylor & Francis, 2008
6. Jon Holt and Simon Perry, Modelling Enterprise Architectures, The Institution of Engineering and Technology, 2010
7. Alan Dennis et al, Systems Analysis and Design with UML 4th Edition, John Wiley and Sons, 2013