Siklus Pengembangan SI

PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition

Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.1 - 1

Siklus Hidup Siklus Hidup Pengembangan SIPengembangan SI



Key Ideas

Banyak sistem gagal dibuat karena analis mencoba membuat sistem yang bagus tanpa mengerti organisasi.Tujuan utama adalah menciptakan nilai bagi organisasi.



Key Ideas

systems analyst adalah orang kunci yang menganalisa kegiatan bisnis, mengidentifikasi peluang untuk pengembangan dan mendisain sistem informasi untuk mengimplementasi idenya. Sangat penting untuk mengerti dan membangun kemampuan melalui praktek agar berhasil dalam mendisain dan mengimplementasikan sistem informasi.



Atribut utama dalam Siklus Hidup

Proyek--Perubahan secara sistematis dalam setiap fase memiliki standar hasil.Menghasilkan proyek yang deliverablesMenggunakan deliverables dalam implementasiHasil yang nyata dalam SIMenggunakan gradual refinement



Fase Proyek

Planning (Mengapa membangun sistem? Bagaimana cara tim membangunnya?)Analysis (Siapa yang menggunakan sistem, apa yang akan dilakukan, dimana dan kapan sistem akan digunakan?)Design (Bagaimana sistem bekerja?)Implementation (System delivery)



A simple process for making lunch



Mengidentifikasi business valueMenganalisa feasibility (kelayakan)Membangun rencana kerjaMenyiapkan staf proyekMengontrol proyek dan terjun langsung dalam proyek

Planning



Analysis strategyMengumpulkan business requirementsRequirements definition use casesProcess modelingData modeling

Analysis



Design selectionArchitecture designInterface designData storage designProgram design

Design



ConstructionProgram buildingProgram and system testing

InstallationConversion strategyTraining planSupport plan

Implementation



Processes and Deliverables

Process Product

Planning

Analysis

Design

Implementation

System RequestFeasibility Analysis

Workplan

System Proposal

System Specification

New System and Maintenance Plan



SYSTEM DEVELOPMENT SYSTEM DEVELOPMENT METHODOLOGIESMETHODOLOGIES



What Is a Methodology?

A formalized approach to implementing the SDLC

A series of steps and deliverables

Methodology CategoriesProcess-

CenteredData-CenteredObject-

Oriented

Structured DesignRapid Application

DevelopmentAgile Development



Waterfall Development Methodology



Pros and Cons of the Waterfall Methodology

Pros Cons

Identifies systems requirements long before programming begins

Minimizes changes to requirements asproject progresses

Design must be specified on paper before programming begins

Long time between system proposal and delivery of new system



Parallel Development Methodology



Pros and Cons of Parallel Development Methodology

Pros Cons

Reduces Schedule Time

Less Chance ofRework

Still Uses PaperDocuments

Sub-projects May BeDifficult to Integrate



Rapid Application Development

Incorporate special techniques and tools:

CASE toolsJAD sessionsFourth generation/visualization programming languagesCode generators



Three RAD Categories

Phased developmentA series of versions developed sequentially

PrototypingSystem prototyping

Throw-away prototypingDesign prototyping



Phased Development Methodology

Insert Figure 1-4 here



Pros and Cons of Phased Development Methodology

Pros Cons

Users Get a SystemTo Use Quickly

Users Can IdentifyAdditional NeedsFor Later Versions

Users Work with aSystem that isIntentionally Incomplete



How Prototyping Works



Pros and Cons of Prototyping Methodology

Pros Cons

Users Interact withPrototype Very Quickly

Users Can IdentifyNeeded ChangesAnd Refine RealRequirements

Tendency to doSuperficial Analysis

Initial Design Decisions May

Be Poor



Throwaway Prototyping



Pros and Cons of Throwaway Prototyping Methodology

Pros Cons

Risks are Minimized

Important Issues areUnderstood Before the

Real System is Built

May Take LongerThan Prototyping



Agile Development: Extreme Programming



Pros and Cons of Agile Methodologies

Pros Cons

Fast Delivery of Results

Works Well in ProjectsWith Undefined or

Changing Requirements

Requires Discipline

Works Best in Small Projects

Requires MuchUser Input



Criteria for Selecting the Appropriate Methodology

Clear user requirementsFamiliarity with technologyComplexity of systemReliability of systemTime scheduleSchedule visibility



TEAM ROLES AND TEAM ROLES AND SKILLSSKILLS



Information Systems Roles

Business analystSystems analystInfrastructure analystChange management analystProject manager



SummaryThe Systems Development Lifecycle consists of four stages: Planning, Analysis, Design, and ImplementationThere are six major development methodologies: the waterfall method, the parallel development method, the phased development method, system prototyping, design prototyping, and agile development.There are five major team roles: business analyst, systems analyst, infrastructure analyst, change management analyst and project manager.



Copyright © 2003 John Wiley & Sons, Inc.

All rights reserved. Reproduction or translation of this work beyond that permitted in Section 117 of the 1976 United States Copyright Act without the express written permission of the copyright owner is unlawful. Request for further information should be addressed to the Permissions Department, John Wiley & Sons, Inc. The purchaser may make back-up copies for his/her own use only and not for redistribution or resale. The Publisher assumes no responsibility for errors, omissions, or damages, caused by the use of these programs or from the use of the information contained herein.

Siklus Pengembangan SI

Documents

Transcript of Siklus Pengembangan SI