Download as pdf or txt
Download as pdf or txt
You are on page 1of 28

Perancangan Sistem Informasi (TIN61652)

8
Arsitektur
Sistem Informasi
Dene Herwanto, ST., MT.

Program Studi Teknik Industri


Fakultas Teknik - UNSIKA
Semester Ganjil Tahun Akademik 2021/2022
Berbagai Definisi Arsitektur Sistem Informasi

 Disebut juga arsitektur teknologi informasi, arsitektur


sistem informasi, infrastruktur teknologi informasi
 Pemetaan atau rencana kebutuhan-kebutuhan informasi di
dalam suatu organisasi (Turban, McLean, Wetherbe, 1999)
 Bentuk khusus yang menggunakan teknologi informasi
dalam organisasi untuk mencapai tujuan-tujuan atau
fungsi-fungsi yang telah dipilih (Laudon & Laudon, 1998)
 Desain sistem komputer secara keseluruhan (termasuk
sistem jaringan) untuk memenuhi kebutuhan-kebutuhan
organisasi yang spesifik (Zwass, 1998)
Tujuan Arsitektur Sistem Informasi

 Sebagai penuntun bagi operasi sekarang atau


menjadi cetak-biru (blueprint) untuk arahan di
masa mendatang
 Agar bagian teknologi informasi memenuhi
kebutuhan bisnis strategis organisasi
Contoh Arsitektur Sistem Informasi
Framework Arsitektur Sistem Informasi
Alasan lain pengembangan arsitektur
sistem informasi

 Shared understanding
 Way to communicate the future
 Help make decisions (e.g., which projects to
select)
 Communicate to vendors
 Way to find opportunities to integrate
Tipe Arsitektur Sistem Informasi

[1] Centralized Information Systems Architecture


 Mainframes dictated IS architecture be
centralized
[2] Decentralized Information Systems Architecture

[3] Distributed Information Systems


[1] Centralized Information Systems
Architecture
Mainframes Dictated IS Architecture be Centralized
 Advantages
 High degree of control
 Easy to maintain hardware, software,
procedure, and operation standards
 Easy control of access to information
 Disadvantages
 Inflexible
 Lack of customization
[1] Centralized Information Systems
Architecture

Figure: In centralized IS architecture, information resources are maintained on


one or several large computers that are centrally controlled.
[2] Decentralized Information Systems
Architecture
 Allows departments and remote sites
independence in organizing and using their IS
 Local IS department establishes infrastructure
 Disadvantages
 Difficult to share applications and data among
units
 Expensive to maintain and service different
systems
[2] Decentralized Information Systems
Architecture

Figure: In decentralized IS architecture, workers at different sites and departments (A, B, C)


use information resources that are dedicated to their site or department.
[3] Distributed Information Systems

 Each unit selects and implements its own


system.
 Remote units can share resources through
communication lines.
 Many organizations changing to distributed
architecture.
 Increased reliability and affordability of data
communication and PC technology
[3] Distributed Information Systems

Figure: In distributed IS architecture, workers use the information resources


of their own site or department, but can also use the resources of other
sites or departments through communication lines
Centralized vs Decentralized IS trade-offs

Figure: Centralized vs. decentralized IS trade-offs


Manajemen Sistem Informasi

Centralized vs. Decentralized ISs: Advantages


and Disadvantages
 Advantages of Centralized IS Management
 Standardized hardware and software
 Easier training
 Encouragement of common reporting systems
 Effective planning of shared systems
 Easier strategic planning
 Efficient use of IS personnel
 Accommodation of tight control by top
management
Manajemen Sistem Informasi – lanjutan

Figure: Centralized management of ISs


Manajemen Sistem Informasi – lanjutan

 Advantages of Decentralized IS Management


 Better fit of ISs to business needs
 Timely responsiveness of IS units to business
demands
 Encouragement of end user application
development
 More innovative use of ISs
 Support for delegation of authority
Manajemen Sistem Informasi – lanjutan

Figure: Decentralized management of ISs (in fully decentralized


management, the central IS unit would not exist)
Trends in Information Systems Organization

 Discarding Big Iron (mainframe computers)


 Switch to PCs brings distributed IS
architecture benefits
 Some companies keep mainframe for
processing power
 Reengineering with Information Technology
 Effort for breakthrough gains through radical
business process and system changes
 Almost always leads to integrating IT in all
processes
Organizing the IS Staff

 Central IS Organization
 Corporate IS team serves all units
 IS Director oversees departments within IS
 System development and maintenance
 Information center
 Communications
 Data administration
 Research and development
 Involved in virtually every aspect of IT
 Steering committee oversees IS services
Organizing the IS Staff

Figure: An example of an IS unit’s organization with centrally managed ISs


Organizing the IS Staff

 Functional IS Organization
 Each unit fulfills IS needs independently.
 Each business unit has one or several IS
professionals who report to the unit manager.
 Funds come from unit budget.
 Small central unit can coordinate IS for
departments that need help.
Organizing the IS Staff

Figure: An example of IS personnel locations in an organization


with functionally managed ISs
Organizing the IS Staff

 The Best of Both Approaches


 Many companies use elements of both central
and functional IS management.
 Regardless of IS management, implementation
depends on position of highest IS officer.
 Reports to VP: IS provides technical solutions
 Reports to CEO: IS more involved in strategic
planning
Challenges for IS Managers and
Line Managers

 Line Managers’ Expectations of an IS Unit


 Broad understanding of business activities
 Prompt response to information needs
 Clear explanation of what technology can and
can’t do
 Candid explanations of what IS can and can’t do
 Honest budgeting
 Single point of contact
Challenges for IS Managers and
Line Managers

 IS Manager Expectations of Line Managers


 Projected list of basic IS needs
 Clear explanation of business processes that
need support once an IS manager is asked to
develop a new system
 What features the business manager wants in
the new system once general automation
process is set
The Information Center

 Coordination and Control


 Hardware and software purchases
 Application development
 Development and use of databases by end
users
 Support
 Training and response to requests for help
 Help desk: Troubleshoot on demand
Sekian...
Terimakasih...

You might also like