PTI444.05.a - Pengembangan SI
Transcript of PTI444.05.a - Pengembangan SI
-
7/29/2019 PTI444.05.a - Pengembangan SI
1/32
Didik Dwi P
Pengembangan Sistem
-
7/29/2019 PTI444.05.a - Pengembangan SI
2/32
2
Tujuan
Memahami konsep dasar, tahapan, siklus hidup, danmetodologi pengembangan sistem (systemsdevelopment).
-
7/29/2019 PTI444.05.a - Pengembangan SI
3/32
3
Topik Bahasan
Pengembangan sistem (systems development)Systems Development Life Cycle (SDLC)
Pendekatan dan metodologi pengembangan sistem
-
7/29/2019 PTI444.05.a - Pengembangan SI
4/324
Pengembangan Sistem
Systems development creating or altering systems.Background:
Problems
Urgensi sistem
Opportunities
Capture market opportunities
Enhance productivity
Improve qualityof services
DirectivesKebijakan, peraturan, dll
-
7/29/2019 PTI444.05.a - Pengembangan SI
5/325
SDLC
SDLC phase that encompasses the planning,analysis, design, and implementation phases of thesystem life cycle (McLeod).
SDLC process of creating or altering systems, and
the models and methodologies that people use todevelop these systems.
SDLC provides overall framework for managingsystem development process (Hedrington).
-
7/29/2019 PTI444.05.a - Pengembangan SI
6/326
SDLC
Two main approaches to SDLC:Traditional approach: structured systems development
and information engineering
Object-oriented approach: object technologies requires
different approach to analysis, design, andprogramming
All projects use some variation of SDLC
-
7/29/2019 PTI444.05.a - Pengembangan SI
7/327
SDLC - Karakteristik
Systems development projectPlanned undertaking with fixed beginning and end
Produces desired result or product
Can be a large job of thousands of hours of effort or a
small one month projectSuccessful development project:
Provides a detailed plan to follow
Organized (tasks and activities)
Produces reliable, robust, and efficient system
-
7/29/2019 PTI444.05.a - Pengembangan SI
8/328
Tahapan SDLC (Hedrington)
Project planning: initiate, ensure feasibility, planschedule, obtain approval for project
Analysis: understand business needs and processingrequirements
Design: define solution system based on requirementsand analysis decisions
Implementation: construction, testing, user training, and
installation of new systemSupport: keep system running and improve
-
7/29/2019 PTI444.05.a - Pengembangan SI
9/32
9
Tahapan SDLC
-
7/29/2019 PTI444.05.a - Pengembangan SI
10/32
10
Tahapan SDLC
Definisi proyek, studi sistem, desain,
pemrograman, instalasi, dan pascainstalasi
Laudon & Laudon
(1998)
Perencanaan, analisis, perancangan, implementasiMcLeod (1998)
Identifikasi dan seleksi proyek, inisiasi dan
perencanaan proyek, analisis, perancangan logis,
perancangan fisik, implementasi, dan perawatan
Hoffer, George, dan
Valacich (1998)
Studi kelayakan, rencana awal, analisis sistem, desain
sistem, dan implementasi sistem
Fabbri dan Schwab
(1992)
Inisiasi, pengembangan, implementasi, dan operasi
dan perawatan
Alter (1992)Tahapan-tahapan dalam SDLCSumber
Definisi proyek, studi sistem, desain,
pemrograman, instalasi, dan pascainstalasi
Laudon & Laudon
(1998)
Perencanaan, analisis, perancangan, implementasiMcLeod (1998)
Identifikasi dan seleksi proyek, inisiasi dan
perencanaan proyek, analisis, perancangan logis,
perancangan fisik, implementasi, dan perawatan
Hoffer, George, dan
Valacich (1998)
Studi kelayakan, rencana awal, analisis sistem, desain
sistem, dan implementasi sistem
Fabbri dan Schwab
(1992)
Inisiasi, pengembangan, implementasi, dan operasi
dan perawatan
Alter (1992)Tahapan-tahapan dalam SDLCSumber
-
7/29/2019 PTI444.05.a - Pengembangan SI
11/32
11
SDLC and problem-solving
Similar to problem-solving approachOrganization recognizes problem (Project Planning)
Project team investigates, understands problem andsolution requirements (Analysis)
Solution is specified in detail (Design)
System that solves problem built and installed(Implementation)
System used, maintained, and enhanced to continue toprovide intended benefits (Support)
-
7/29/2019 PTI444.05.a - Pengembangan SI
12/32
12
Tahap Perencanaan
Set objectivesDefine business problem and scope
Produce detailed project schedule
Confirm project feasibilityEconomic, organizational, technical, resource, and
schedule
Identify constraints
-
7/29/2019 PTI444.05.a - Pengembangan SI
13/32
13
Tahap Analisis
Gather information to learnproblem domainDefine system requirements
Build prototypes for discovery of requirements
Prioritize requirementsGenerate and evaluate alternatives
Review recommendations with management
-
7/29/2019 PTI444.05.a - Pengembangan SI
14/32
14
Tahap Desain
Design and integrate the networkDesign the application architecture
Design the user interfaces
Design the system interfacesDesign and integrate the database
Prototype for design details
Design and integrate system controls
-
7/29/2019 PTI444.05.a - Pengembangan SI
15/32
15
Tahap Implementasi
Constructsoftware componentsVerify and test
Convert data
Train users and document the systemInstall the system
-
7/29/2019 PTI444.05.a - Pengembangan SI
16/32
16
Tahap Dukungan
Maintain systemSmall patches, repairs, and updates
Enhance system
Small upgrades or enhancements to expand system
capabilities
Support users
Help desk and/or support team
-
7/29/2019 PTI444.05.a - Pengembangan SI
17/32
17
Pendekatan Pengembangan Sistem
WaterfallEvolusioner
Spiral*
Unified Process*
* Current trends in development
-
7/29/2019 PTI444.05.a - Pengembangan SI
18/32
18
Model Waterfall
-
7/29/2019 PTI444.05.a - Pengembangan SI
19/32
19
Fase model Waterfall
Analisa dan definisi kebutuhanDesain sistem dan software
Implementasi dan unit testing
Integrasi dan testing sistemOperasi dan maintenance
-
7/29/2019 PTI444.05.a - Pengembangan SI
20/32
20
Permasalahan model Waterfall
Kekurangan utama dari model waterfall adalahkesulitan untuk mengakomodasi perubahan setelahproses berjalan
Tidak fleksibel dalam pembagian proyek ke dalam
tingkat yang berbedaSulit untuk merespon perubahan kebutuhan konsumen
Sehingga model ini hanya cocok jika kebutuhan sudahdimengerti dengan baik
-
7/29/2019 PTI444.05.a - Pengembangan SI
21/32
21
Pengembangan Evolusioner
-
7/29/2019 PTI444.05.a - Pengembangan SI
22/32
22
Pengembangan Evolusioner
PermasalahanTidak ada visibilitas proses
Sistem biasanya tidak terstruktur dengan baik
Kemampuan khusus (misalnya bahasa untuk prototipe
cepat) kemungkinan diperlukanAplikasi
Untuk sistem interaktif berukuran kecil atau medium
Untuk bagian dari sistem besar (misalnya user interface)
Untuk sistem dengan daur hidup pendek
-
7/29/2019 PTI444.05.a - Pengembangan SI
23/32
23
Spiral
-
7/29/2019 PTI444.05.a - Pengembangan SI
24/32
24
Unified Process (UP)
-
7/29/2019 PTI444.05.a - Pengembangan SI
25/32
25
Metodologi
Recommended way of doing something (McLeod)
Comprehensive guidelines to follow for completingevery SDLC activity (Hedrington)
Kesatuan metode-metode, prosedur-prosedur, konsep-
konsep pekerjaan, aturan-aturan dan postulat-postulatyang digunakan oleh suatu ilmu pengetahuan, seni ataudisiplin lainnya (Jogiyanto).
Collection ofmodels, tools, and techniques.
-
7/29/2019 PTI444.05.a - Pengembangan SI
26/32
26
Model
Representation of an important aspect of real world, butnot same as real thing
Abstraction used to separate out aspect
Diagrams and charts
Project planning and budgeting aids
-
7/29/2019 PTI444.05.a - Pengembangan SI
27/32
27
Model
-
7/29/2019 PTI444.05.a - Pengembangan SI
28/32
28
Tools and Techniques
Tools
Software support that helps create models or otherrequired project components
Range from simple drawing programs to complex CASEtools
Techniques
Collection of guidelines that help analyst completesystem development activity or task
Can be step-by-step instructions or just general advice
-
7/29/2019 PTI444.05.a - Pengembangan SI
29/32
29
Tools
-
7/29/2019 PTI444.05.a - Pengembangan SI
30/32
30
Techniques
-
7/29/2019 PTI444.05.a - Pengembangan SI
31/32
31
Relasi Komponen Metodologi
M d l i P b Si
-
7/29/2019 PTI444.05.a - Pengembangan SI
32/32
32
Metodologi Pengembangan Sistem
Functional decomposition methodologies
Dekomposisi sistem ke subsistem.
Data-oriented methodologies
Memfokuskan karakteristik data
Jenis: data flow dan data structure
Prescriptive methodologies