Download - Enterprise Architecture
-
Enterprise Architecture
-
Arsitektur TI di Perusahaan
Beberapa didesain
dan beberapa
seperlunya
-
Latar Belakang
Bisnis : keuntungan, perubahan, struktur, proses bisnis yang kompleks
CIO : melndukung proses bisnis, added value
Manajemen Data : Dimana data saya? Apa artinya? Apakah nilainya konsisten?
Jaringan : desain jaringan, SLA, bottlenecks, upgrade
SOLUSI?
-
Permasalahan
Redundansi dan inkonsistensi data padaperusahaan yang terdiri atas banyak unit-unit( fungsi )
Permasalahan manajemen untuk memperolehdukungan dan komitmen di semu tingkat untukproyek-proyek yang berjangka waktu lama
Sistem yang ada tidak berhubungan
Proyek-proyek yang ada tidak saling berhubungan
-
Apa itu arsitektur?
tergantung scope menentukan batasan
Seluruh perusahaan
Divisi dalam sebuah perusahaan
Lebih luas : supplier, perusahaan, kustomer
Architecture
Prinsip-prinsip tata kelola, aturan, pedoman, standar, pemetaan, model, aset-aset TI, proses bisnis
-
Arsitektur TI yang baik akan
Memenuhi kebutuhan perusahaan Menyesuaikan perubahan sesuai dengan kecepatan pasar Dipahami dan didukung oleh manajemen senior Secara jelas mendefinisikan struktur sistem existing Menyediakan perencanaan, roadmap dan strategi migrasi untuk
pengembangan( pembelian? ) di masa depan Memanajemen proyek ke dalam proyek-proyek lainnya sehingga
konsisten, milestone dapt terukur dan dikomunikasikan secara efektif Optimal jika dilaksanakan dalam scope enterprise( lebih luas ) akan
mengurangi redundansi dan kompleksitas dari interface diantarakomponennya yang meningkatkan kemudahan : Portabilitas aplikasi Upgrade komponen Pertukaran komponen Pengembangan dan pemeliharaan komponen
-
Mana rencana anda?
Kemampuan lebih untuk merespon permintaan baru Nilai bisnis lebih dari operasi TI Kemampuan lebih untuk mengenalkan teknologi baru Pengadaan yang lebih cepat, lebih sederhana dan lebih
murah
Dapatkah sebuah bisnis sukses tanpabusiness plan yang terdokumentasi?
Dapatkah IT sukses tanpa arsitektur yang terdokumentasi?
-
Dari mana memulai?
Terdapat beberapa arsitektur TI yang berhasil
Apakah harus reinvent the wheel?
Referensi apa yang tersedia?
-
Tahapan EA Enterprise wide view
Visi dan Tujuan
Baseline As Is
Target To Be
Analisis gap dan identifikasi kesempatan
Prioritas, rencana migrasi dan implementasi
-
Jadi.
Kebutuhan TI untuk merubah budaya
Enterprise Architecture adalah :
Cross project
Cross function
Technology neutral
Proyek berada dalam kerangka arsitektur, tidak berdiri sendiri
-
Kenapa Framework Enterprise
Sebuah enterprise adalah entitas yang sangatkompleks
EA menggambarkan versi sederhana kompleksitasuntuk analisis, komunikasi dan opersional
Frameworks dapat menyederhanakankompleksitas entitas dan relasinya di sebuahenterprise
Perhatikan semua bidang untuk dipertimbangkandalam scope EA
Mengapa mengulang pekerjaan yang telahdilakukan?
-
Manfaat Framework
Proses, Proses, Proses Proses sebelum framework sebelum tool
Anda harus berpikir masak semua aspek EA untuk Enterprise anda Jangan diserahkan keframework
Tujuan dan Sasaran harus mengarahkan APA yang anda lakukan
Enterprise Architecture masih merupakansebuah seni daripada keilmuan danmembutuhkan kreativitas
-
Definisi Framework
Kamus: n. 1) A structure for supporting or enclosing something else, especially a skeletal support used as the basis for something being constructed; 2) a simplified description of a complex entity or process (syn.: model)
Konteks EA: sebuah model atau outline yang menyediakanstruktur logis EA deliverables yang akan dibuat dan salingberhubungan satu dengan yang lain
Maksud EA Framework: Menyediakan konteks yang disederhanakan untuk scope dan struktur enterprise dankomponen-komponennya
Contoh : Zachman Framework for Enterprise Architecture, TOGAF, DODAF, MODAF, FEAF
-
Karakteristik Umum Framework
Komprehensif
Visual
Penyerdehanaan domain
Merepresentasikan pekerjaan yang tidak perlu diulang tapi sebagai titik awal untuk mengadaptasikan konsep/model yang representatif untuk enterprise tertentu
-
Asal TOGAF dan Motivasi
Inisiatif kustomer :
User requirement formal pada 1994
Tema-tema utama :
Single, unifying Architectural Framework untuk industri TI
Sebuah framework untuk mengembangkan arsitektur untuk memenuhi kebutuhan bisnis tertentu
Bukan arsitektur one-size-fits-all
-
Konsensus industri
Technology- and tool-neutral
8 tahun dalam pengembangan terus menerus
Terbukti dalam praktek
Tersedia di : http://www.opengroup.org/public/arch
TOGAF Sekarang
-
Struktur dan Komponen TOGAF
Building Blocks Information Base
(architecture building blocks -future)
Standards Information Base
(standards)
Technical Reference Model
(services taxonomy)
Architecture Development Method
Resource Base
Target Architectures
TOGAF FoundationArchitecture
Architecture Development Method
Foundation Architecture
Resource Base
-
Architecture Development Method (ADM)
Open, metode-metode konsensus industri untuk arsitektur TI
Quick-start foundation
Praktis, pedoman berdasar pengalaman
Membutuhkan validasi terus menerus terhadap kebutuhan
-
Berhubungan dengantaksonomi detail dariservis-servis mendefinisikan
batasan dari setiapkategori servis
Mendefinisikankemampuansistem(kualitas), misalnya.: Internasionalisasi Keamanan Manajemen
Foundation Architecture:Technical Reference Model (TRM)
Qualities
Qualities
Network Services
Operating System ServicesD
ata Man
agemen
t
Locatio
n &
Directo
ry
InfrastructureApplications
BusinessApplications
Data In
terchan
ge
Intern
ation
al Op
eration
s
User In
terface
Transactio
n P
rocessin
g
System &
Netw
ork M
anagem
ent
Security
Softw
are Engin
eering
Grap
hics &
Image
Communication Infrastructure
Application Programming Interface
Communications Infrastructure Interface
Qu
alit
ies Qu
alities
-
Foundation Architecture:Standards Information Base (SIB)
Sebuah basisdata standar industri yang bersifat terbuka
Kumpulan lengkap standar Open Group yang telah disahkan
Isi ditentukan oleh proses konsensus Open Group
Diatur sesuai TOGAF Technical Reference Model taxonomy
Secara reguler diupdate
Tersedia di web
http://www.db.opengroup.org/sib.htm
Pintu gerbang untuk banyak sumber lainnya
-
Resource Base
Resource tersedia dalam menerapkan TOGAF Architecture Development Method; misalnya ADML
Architecture Compliance Reviews
Architecture Principles
Architecture Views
Business Scenarios (metode requiremen)
Case Studies
Strategi IT Governance
-
Zachman Framework[1]
Based on work by
John A. Zachman
VA Enterprise
Architecture
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
SCOPE
(CONTEXTUAL)
Planner
ENTERPRISE
MODEL
(CONCEPTUAL)
Owner
SYSTEM MODEL
(LOGICAL)
Designer
TECHNOLOGY
MODEL
(PHYSICAL)
Builder
DETAILED
REPRESENTATIONS
(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONING
ENTERPRISE
SCOPE
(CONTEXTUAL)
Planner
ENTERPRISE
MODEL
(CONCEPTUAL)
Owner
SYSTEM MODEL
(LOGICAL)
Designer
TECHNOLOGY
MODEL
(PHYSICAL)
Builder
DETAILED
REPRESENTATIONS
(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONING
ENTERPRISE
Things Important
to the Business
Entity = Class of
Business Thing
Processes
Performed
Function = Class of
Business Process
Semantic Model
Ent = Business Entity
Rel = Business Relationship
Business Process
Model
Proc = Business Process
I/O = Business Resources
Business Logistics
System
Node = Business Location
Link = Business Linkage
Work Flow Model
People = Organization Unit
Work = Work Product
Master Schedule
Time = Business Event
Cycle = Business Cycle
Business Plan
End = Business Objectiv e
Means = Business Strategy
Important
Organizations
People = Major
Organizations
Business
locations
Node = Major
Business Locations
Ev ents Significant
to the Business
Time = Major
Business Event
Business Goals
and Strategy
Ends/Means =
Major Business Goals
Logical Data
Model
Ent = Data Entity
Rel = Data Relationship
Application
Architecture
Proc = Application Function
I/O = User Views
Distributed System
Architecture
Node = IS Function
Link = Line Characteristics
Human Interface
Architecture
People = Role
Work = Deliv erable
Processing
Structure
Time = System Event
Cycle = Processing Cycle
Business Rule
Model
End = Structural Assertion
Means = Action Assertion
Physical Data
Model
Ent = Segment/Table
Rel = Pointer/Key
System
Design
Proc = Computer Function
I/O = Data Elements/Sets
Technology
Architecture
Node = Hardware/Softw are
Link = Line Specifications
Presentation
Architecture
People = User
Work = Screen Format
Control
Structure
Time = Ex ecute
Cycle = Component Cycle
Rule
Design
End = Condition
Means = Action
Data
Definition
Ent = Field
Rel = Address
Program
Proc = Language Statement
I/O = Control Block
Netw ork
Architecture
Node = Addresses
Link = Protocols
Security
Architecture
People = Identity
Work = Job
Timing
Definition
Time = Interrupt
Cycle = Machine Cycle
Rule
Design
End = Sub-Condition
Means = Step
Data
Ent =
Rel =
Function
Proc =
I/O =
Netw ork
Node =
Link =
Organization
People =
Work =
Schedule
Time =
Cycle =
Strategy
End =
Means =
Based on work by
John A. Zachman
VA Enterprise
Architecture
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
SCOPE
(CONTEXTUAL)
Planner
ENTERPRISE
MODEL
(CONCEPTUAL)
Owner
SYSTEM MODEL
(LOGICAL)
Designer
TECHNOLOGY
MODEL
(PHYSICAL)
Builder
DETAILED
REPRESENTATIONS
(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONING
ENTERPRISE
SCOPE
(CONTEXTUAL)
Planner
ENTERPRISE
MODEL
(CONCEPTUAL)
Owner
SYSTEM MODEL
(LOGICAL)
Designer
TECHNOLOGY
MODEL
(PHYSICAL)
Builder
DETAILED
REPRESENTATIONS
(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONING
ENTERPRISE
Things Important
to the Business
Entity = Class of
Business Thing
Processes
Performed
Function = Class of
Business Process
Semantic Model
Ent = Business Entity
Rel = Business Relationship
Business Process
Model
Proc = Business Process
I/O = Business Resources
Business Logistics
System
Node = Business Location
Link = Business Linkage
Work Flow Model
People = Organization Unit
Work = Work Product
Master Schedule
Time = Business Event
Cycle = Business Cycle
Business Plan
End = Business Objectiv e
Means = Business Strategy
Important
Organizations
People = Major
Organizations
Business
locations
Node = Major
Business Locations
Ev ents Significant
to the Business
Time = Major
Business Event
Business Goals
and Strategy
Ends/Means =
Major Business Goals
Logical Data
Model
Ent = Data Entity
Rel = Data Relationship
Application
Architecture
Proc = Application Function
I/O = User Views
Distributed System
Architecture
Node = IS Function
Link = Line Characteristics
Human Interface
Architecture
People = Role
Work = Deliv erable
Processing
Structure
Time = System Event
Cycle = Processing Cycle
Business Rule
Model
End = Structural Assertion
Means = Action Assertion
Physical Data
Model
Ent = Segment/Table
Rel = Pointer/Key
System
Design
Proc = Computer Function
I/O = Data Elements/Sets
Technology
Architecture
Node = Hardware/Softw are
Link = Line Specifications
Presentation
Architecture
People = User
Work = Screen Format
Control
Structure
Time = Ex ecute
Cycle = Component Cycle
Rule
Design
End = Condition
Means = Action
Data
Definition
Ent = Field
Rel = Address
Program
Proc = Language Statement
I/O = Control Block
Netw ork
Architecture
Node = Addresses
Link = Protocols
Security
Architecture
People = Identity
Work = Job
Timing
Definition
Time = Interrupt
Cycle = Machine Cycle
Rule
Design
End = Sub-Condition
Means = Step
Data
Ent =
Rel =
Function
Proc =
I/O =
Netw ork
Node =
Link =
Organization
People =
Work =
Schedule
Time =
Cycle =
Strategy
End =
Means =
-
Zachman Framework[2]
-
October 23, 2009A Tutorial on the Zachman Enterprise
Architecture Framework24
Zachman Framework
Baris 1 ScopeExternal Requirements dan Drivers
Business Function Modeling
Baris 2 Enterprise ModelBusiness Process Models
Baris 3 System ModelLogical Models
Requirements Definition
Baris 4 Technology ModelPhysical Models
Solution Definition dan Development
Baris 5 As BuiltAs Built
Deployment
Baris 6 Functioning EnterpriseFunctioning Enterprise
Evaluation
1
2
3
4
5
6
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
-
October 23, 2009A Tutorial on the Zachman Enterprise
Architecture Framework25
Aturan-aturan Framework
Aturan 1:
Kolom-kolom tidak berurutan
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
Aturan 2:
Setiap kolom mempunyai model sederhana
Aturan 3:
Basic model untuk setiap kolom unik
Aturan 4:
Setiap baris merepresentasikan view berbeda
Aturan 5:
Setiap sel unik
Aturan 6:
Kombinasi sel-sel dalam saru baris membentuk
deskripsi lengkap dari view tersebut
Basic Model = Entities dan Relationships
EntityRelationshipEntity
-
Memilih sebuah Framework
Apa yang anda ingin kerjakan/selesaikan?
Di industri/usaha apa anda bergerak?
Apakah anda pemerintah daerah/pusat?
Level kompetensi apakah yang sumber daya EA anda punyai?
Apakah batasan dari usaha EA anda?
Framework apakah yang biasa digunakan oleh organisasi anda?
-
Referensi
A Tutorial on the Zachman Enterprise Architecture Framework, Slide from Department of Veterans Affairs, USA
The Open Group, The Open Group Architecture Framework (TOGAF) Version 7, http://www.opengroup.org
Luther, Dorothy, Enterprise Architecture, 4 September 2006
Westbrock, Tim, Do Frameworks Really Matter?, EAdirections, 2007