Pengembangan Sistem

Didik Dwi P didik@um.ac.id

Tujuan Memahami konsep dasar, tahapan, siklus hidup, dan metodologi pengembangan sistem (systems development).

Topik Bahasan Pengembangan sistem (systems development) Systems Development Life Cycle (SDLC) Pendekatan dan metodologi pengembangan sistem

Pengembangan Sistem Systems development creating or altering systems. Background:

Problems
Urgensi sistem

Opportunities
Capture market opportunities Enhance productivity Improve qualityof services

Directives
Kebijakan, peraturan, dll

SDLC SDLC phase that encompasses the planning, analysis, design, and implementation phases of the system life cycle (McLeod). SDLC process of creating or altering systems, and the models and methodologies that people use to develop these systems. SDLC provides overall framework for managing system development process (Hedrington).

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, and programming

All projects use some variation of SDLC

SDLC - Karakteristik Systems development project

Planned 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 project

Successful development project:

Provides a detailed plan to follow Organized (tasks and activities) Produces reliable, robust, and efficient system

Tahapan SDLC (Hedrington) Project planning: initiate, ensure feasibility, plan schedule, obtain approval for project Analysis: understand business needs and processing requirements Design: define solution system based on requirements and analysis decisions Implementation: construction, testing, user training, and installation of new system Support: keep system running and improve

Tahapan SDLC

Tahapan SDLC
Sumber Alter (1992) Tahapan-tahapan dalam SDLC Inisiasi, pengembangan, implementasi, dan operasi dan perawatan

Fabbri dan Schwab Studi kelayakan, rencana awal, analisis sistem, desain (1992) sistem, dan implementasi sistem Hoffer, George, dan Identifikasi dan seleksi proyek, inisiasi dan perencanaan proyek, analisis, perancangan logis, Valacich (1998) perancangan fisik, implementasi, dan perawatan McLeod (1998) Perencanaan, analisis, perancangan, implementasi

Laudon & Laudon Definisi proyek, studi sistem, desain, (1998) pemrograman, instalasi, dan pascainstalasi

10

SDLC and problem-solving Similar to problem-solving approach Organization recognizes problem (Project Planning) Project team investigates, understands problem and solution requirements (Analysis) Solution is specified in detail (Design) System that solves problem built and installed (Implementation) System used, maintained, and enhanced to continue to provide intended benefits (Support)

11

Tahap Perencanaan Set objectives Define business problem and scope Produce detailed project schedule Confirm project feasibility
Economic, organizational, technical, resource, and schedule

Identify constraints

12

Tahap Analisis Gather information to learn problem domain Define system requirements Build prototypes for discovery of requirements Prioritize requirements Generate and evaluate alternatives Review recommendations with management

13

Tahap Desain Design and integrate the network Design the application architecture Design the user interfaces Design the system interfaces Design and integrate the database Prototype for design details Design and integrate system controls

14

Tahap Implementasi Construct software components Verify and test Convert data Train users and document the system Install the system

15

Tahap Dukungan Maintain system

Small patches, repairs, and updates

Enhance system
Small upgrades or enhancements to expand system capabilities

Support users
Help desk and/or support team

16

Pendekatan Pengembangan Sistem Waterfall Evolusioner Spiral* Unified Process*

* Current trends in development

17

Model Waterfall

18

Fase model Waterfall Analisa dan definisi kebutuhan Desain sistem dan software Implementasi dan unit testing Integrasi dan testing sistem Operasi dan maintenance

19

Permasalahan model Waterfall Kekurangan utama dari model waterfall adalah kesulitan untuk mengakomodasi perubahan setelah proses berjalan Tidak fleksibel dalam pembagian proyek ke dalam tingkat yang berbeda Sulit untuk merespon perubahan kebutuhan konsumen Sehingga model ini hanya cocok jika kebutuhan sudah dimengerti dengan baik

20

Pengembangan Evolusioner

21

Pengembangan Evolusioner Permasalahan

Tidak ada visibilitas proses Sistem biasanya tidak terstruktur dengan baik Kemampuan khusus (misalnya bahasa untuk prototipe cepat) kemungkinan diperlukan

Aplikasi
Untuk sistem interaktif berukuran kecil atau medium Untuk bagian dari sistem besar (misalnya user interface) Untuk sistem dengan daur hidup pendek

22

Spiral

23

Unified Process (UP)

24

Metodologi Recommended way of doing something (McLeod) Comprehensive guidelines to follow for completing every SDLC activity (Hedrington) Kesatuan metode-metode, prosedur-prosedur, konsepkonsep pekerjaan, aturan-aturan dan postulat-postulat yang digunakan oleh suatu ilmu pengetahuan, seni atau disiplin lainnya (Jogiyanto). Collection of models, tools, and techniques.

25

Model Representation of an important aspect of real world, but not same as real thing Abstraction used to separate out aspect Diagrams and charts Project planning and budgeting aids

26

Model

27

Tools and Techniques Tools

Software support that helps create models or other required project components Range from simple drawing programs to complex CASE tools

Techniques
Collection of guidelines that help analyst complete system development activity or task Can be step-by-step instructions or just general advice

28

Tools

29

Techniques

30

Relasi Komponen Metodologi

31

Metodologi Pengembangan Sistem Functional decomposition methodologies

Dekomposisi sistem ke subsistem.

Data-oriented methodologies
Memfokuskan karakteristik data Jenis: data flow dan data structure

Prescriptive methodologies

32