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
Permasalahan
• Redundansi dan inkonsistensi data pada
perusahaan yang terdiri atas banyak unit-unit(
fungsi )
• Permasalahan manajemen untuk memperoleh
dukungan dan komitmen di semu tingkat untuk
proyek-proyek yang berjangka waktu lama
• Sistem yang ada tidak 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 diantara
komponennya yang meningkatkan kemudahan :
– Portabilitas aplikasi
– Upgrade komponen
– Pertukaran 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 tanpa
business plan yang terdokumentasi?
Dari mana memulai?
• Terdapat beberapa arsitektur TI yang berhasil
• Apakah harus reinvent the wheel?
Tahapan EA – Enterprise wide view
• Visi dan Tujuan
• Baseline – As Is
• Target – To Be
• Analisis gap dan identifikasi kesempatan
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 sangat
kompleks
• EA menggambarkan versi sederhana kompleksitas
untuk analisis, komunikasi dan opersional
• Frameworks dapat menyederhanakan
kompleksitas entitas dan relasinya di sebuah
enterprise
• Perhatikan semua bidang untuk dipertimbangkan
dalam scope EA
• Mengapa mengulang pekerjaan yang telah
dilakukan?
Manfaat Framework
• Proses, Proses, Proses
– Proses sebelum framework sebelum tool
• Anda harus berpikir masak semua aspek EA
untuk Enterprise anda – Jangan diserahkan ke
framework
• Tujuan dan Sasaran harus mengarahkan APA
yang anda lakukan
• Enterprise Architecture masih merupakan
sebuah seni daripada keilmuan dan
membutuhkan 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 menyediakan
struktur logis EA deliverables yang akan dibuat dan saling
berhubungan satu dengan yang lain
• Maksud EA Framework: Menyediakan konteks yang
disederhanakan untuk scope dan struktur enterprise dan
komponen-komponennya
• Contoh : Zachman Framework for Enterprise Architecture,
Karakteristik Umum Framework
• Komprehensif
• Visual
• Penyerdehanaan domain
• Merepresentasikan pekerjaan yang tidak
perlu diulang tapi sebagai titik awal untuk
mengadaptasikan konsep/model yang
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
• Konsensus industri
• Technology- and tool-neutral
• 8 tahun dalam pengembangan terus menerus
• Terbukti dalam praktek
• Tersedia di :
http://www.opengroup.org/public/arch
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 Foundation
Architecture
• 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 dengan
taksonomi detail dari
servis-servis
– mendefinisikan
batasan dari setiap
kategori servis
• Mendefinisikan
kemampuan
sistem(“kualitas”),
misalnya.:
– Internasionalisasi
– Keamanan
– Manajemen
Foundation Architecture:
Technical Reference Model (TRM)
Qualities
Qualities
Network Services
Operating System Services
Da
ta
Man
ag
em
en
t
Loc
ation
&
Dir
ec
tor
y
Infrastructure
Applications
Business
Applications
Da
ta
In
ter
ch
an
ge
In
tern
ational
O
p
er
ations
User
In
terf
ac
e
Tr
an
sact
io
n
P
roce
ss
ing
Sy
st
em
&
N
etw
or
k
Man
ag
em
en
t
Sec
u
rity
So
ftw
ar
e
En
gin
ee
ring
Gr
ap
h
ic
s
&
Im
ag
e
Communication Infrastructure
Application Programming Interface
Communications Infrastructure Interface
Qualitie
s
Qualitie
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
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
Zachman Framework[1]
Based on work by
John A. Zachman
VA Enterprise
Architecture
DATA
What
FUNCTION
How
NETWORK
Where
PEOPLE
Who
TIME
When
MOTIVATION
Why
DATA
What
FUNCTION
How
NETWORK
Where
PEOPLE
Who
TIME
When
MOTIVATION
Why
SCOPE
(CONTEXTUAL)
Planner
ENTERPRISE
MODEL
(CONCEPTU AL)
Owner
SYSTEM MODEL
(LOGICAL)
Designer
TECHNOLOGY
MODEL
(PHYSICAL)
Builder
DETAILED
REPRESENTATIONS
(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONING
ENTERPRISE
SCOPE
(CONTEXTUAL)
Planner
ENTERPRISE
MODEL
(CONCEPTU AL)
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 ModelEnt = 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
DATA
What
FUNCTION
How
NETWORK
Where
PEOPLE
Who
TIME
When
MOTIVATION
Why
DATA
What
FUNCTION
How
NETWORK
Where
PEOPLE
Who
TIME
When
MOTIVATION
Why
SCOPE
(CONTEXTUAL)
Planner
ENTERPRISE
MODEL
(CONCEPTU AL)
Owner
SYSTEM MODEL
(LOGICAL)
Designer
TECHNOLOGY
MODEL
(PHYSICAL)
Builder
DETAILED
REPRESENTATIONS
(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONING
ENTERPRISE
SCOPE
(CONTEXTUAL)
Planner
ENTERPRISE
MODEL
(CONCEPTU AL)
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 ModelEnt = 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 =
