DR
Karakteristik Hardware
Infant mortality
Failure rate
Wear out
Time
Karakteristik Software
Failure rate
Actual Curve
Change
Idealized Curve
Time
Mengapa
Rekayasa Perangkat Lunak Diperlukan ?
SOFTWARE
COST
HARDWARE COST
Source : Electronic design, Jan 1981
Biaya perangkat lunak cenderung meningkat dan melebihi biaya perangkat keras
Requirement Design
Analysis
Code
Development
Test
Acceptance Operation
Test
Perbaikan kesalahan pada tahap analisa memerlukan biaya 2 satuan. Perbaikan untuk
kesalahan yang sama pada tahap operasi memelukan biaya 200 satuan
Very
Common
Fairly
Common
Not Very
Common
Very
Rate
Never
Occurs
Dontt
Know
21.2
29.2
25.7
9.7
6.2
3.0
30.1
31.9
25.7
8.0
1.8
2.7
8.8
34.5
35.4
13.3
6.2
1.8
3.6
16.1
57.1
20.5
2.7
5.3
37.2
38.1
11.5
4.4
3.5
14.2
62.8
15.0
6.2
1.8
CAUSE
Agency estimated its own state of progress when it let the contract
Incorrect agency management action, such as using inapporapriate
contract
Agency failed to specify requirement adequtely
Agency overcommited it selt
agency failed to manage during execution, including executive
changes
Agency failed to adequately inspect and test
1
X
2
X
3
X
Case Number
4 5 6 7
X
X
X
X
8
X
X
X
X
X
X
49%
49
43%
43
Pemeliharaan
Pengembangan
Lain-lain
8%
8
Sub karakteristik
Adaptability, Installability
MODEL
Code and Fix
System Development Life Cycle (SDLC)
Prototyping
Spiral
CASE (Computer Aided Software
Engineering)
KRITERIA TRANSISI :
Dokumentasi.
CATATAN :
Sering dikenal sebagai Document Driven Software
Process
Merupakan perbaikan dari code and fix, dan sampai saat
ini merupakan salah satu proses perangkat lunak yang
paling banyak digunakan.
PROTOTYPING
TAHAPAN: Identifikasi kebutuhan awal, prototyping, penggunaan dan
evaluasi prototipe (feedback),Revisi Prototyping ( Iterasi 1n),
Penerimaan/Persetujuan End User, Implementasi Sistem, Operasionalisasi
dan Pemeliharaan
KRITERIA TRANSISI :
CODE (PROGRAM)
CATATAN :
Sering dikenal sebagai Code Driven Software Process
Merupakan salah satu proses perangkat lunak yang mulai banyak
digunakan saat ini.
Banyak memanfaatkan 4GL dan Application Generator.
Dibandingkan dengan SDLC :
* Produktivitas lebih baik
* Kelengkapan fungsi dari sistem kurang baik
* Keterpaduan (integrasi) sistem kurang baik
Alternatif
MEMBUAT SEBUAH
PROTOTYPE
REVISI PROTOTYPE
CONTOH MODEL
(PROTOTYPE)
MENGGUNAKAN DAN
MENGEVALUASI
PROTOTYPE
SISTEM YANG
DISERAHKAN
Implementasi
Setuju
Tidak
Specifications Complete
Objectives
Full Release
February
March
Beta 3
April
Stabilize
Beta 4
Beta 5
May
Beta 6
June
July
Agustus
7
User
Approval
2
Rapid Analysis
5
Functions
1
Projek Plan
3
Database
Creation
9
Tuning
4
Menus
10
Operation & Maintenance
(Sumber : J.L. Connel, L.B. Shafer, Structured Rapid Prototyping, Prentice Hall, 1989)
Team. A few end users and IS developers form a team to develop a business
application
CATATAN :
Sering dikenal sebagai : Risk Driven Software
Process
Untuk pengembangan proyek yang berskala besar,
dengan memperhatikan pengaruh resiko dilihat dari
segi finansial maupun keamanan (jiwa manusia).
Kombinasi SDLC, Prototyping dan Risk Analysis.
MODEL SPIRAL
tahap-tahapnya :
Determine
Objectives
Alternatives
Constraints
Cumulative Cost
Progress through steps
Evaluate alternative
Identity resolve risk
Risk
analysis
Risk
analysis
Commitment
Review
Partition
Spiral Model
Prototype
Risk
analysis
Prototype
Risk
analysis
Prototype
Operasional
Prototype
Develop, verify
next - level product
Planning
Toolset
Case Workstation
The Analysis Toolset
focuses on correctly
capturing detailed business
requirements early in
development process
Analysis
Toolset
Case
Design
Toolset
Code
Generation
Toolset
Database
Generation
Toolset
System
Interface
Work Station
Repositories
Information
Integrator
Workstation repositories
and a server repository
document information
about systems being
developed or in use
The Code
Generation
Toolset
produces
program
code based
on system
specification
The Database
Generation
Toolset
generates
information
needed for
data storage
and access
The System
Interface
provides for
file transfers
and query
resporting
Control
What controls needed to
protect against accidental
loss or damage ?
is there a needed to control
access to data us by the
application ?
Input
What data are available,
in what form
Processing
What operations on the inputs
are needed to produce the
desired output ?
What software can most
effectively support those
operations ?
Storage
Does the application use
previously stored data ?
Does it create data that must
be stored for future use by this
or other applications ?
END USER
DEVELOPMENT
Output
What information is needed
by end users and in what
form should the output be
presented ?
PENGEMBANGAN
BERBAGAI
ALTERNATIF
SOLUSI
PEMILIHAN
SOLUSI TERBAIK
DISAIN
SOLUSI TERBAIK
IMPLEMENTASI
SOLUSI
Inve
e
t
a
g
s ti
al
An
SIKLUS
PENGEMBANGAN
SISTEM INFORMASI
(SDLC)
Desi
gn
y ze
in ta
Ma
in
t
Implemen
SIKLUS
PENGEMBANGAN
SISTEM INFORMASI
Memahami
Permasalahan dan
Peluang
Sistem
Systems Investigation
Product
Feasibillity
Study
Systems Analysis
Product
Functional
Requirements
(SDLC)
Pengembangan
Solusi
Sistem Informasi
Implementasi
Solusi
Sistem Informasi
Systems Design
Product
System
Specifications
Systems Implementation
Product
Operational
systems
Systems Maintenance
Product
Improved system
INVESTIGASI SISTEM
PRODUK: TUJUAN, RUANG LINGKUP DAN PERUMUSAN MASALAH
TOOLS: MATRIK KOMPONEN SISTEM INFORMASI DLLNYA.
Organizational Feasibility
Economic Feasibility
Technical Feasibility
Cost savings
Increased revenue
Decreased investment
Increased profits
Operational Feasibility
TAHAPAN ANALISIS
PRODUK: FUNCTIONAL REQUIREMENTS
Open-ended
interviews
Open-ended
interviews
On-site, in-context
observations
Data
Analysis
Form Systems
Development Team
User videotape
library and database
video
transcripts
site maps
mock-ups
Verify findings
with users
Codevelopment
Design solutions embodied in
sketches, mock-ups, simulations
Design workshops with users
Final
System
Design
Tahapan Disain
User
UserInterface
Interface
Design
Design
Data
Data
Design
Design
Process
Process
Design
Design
Progam and
Procedure design
TAHAPAN
IMPLEMENTASI
Implementation
Activities
Acquisition of
Hardware,
Software,
and Services
Software
Development
or
Modification
End User
Training
System
Documentation
Conversion
Parallel
Pilot
Phased
Plunge
12-44
TAHAPAN IMPLEMENTASI
Evaluate and acquire new hardware and software. Hardware includes computer
systems, POS terminals, and telecommunications processors and network facilities.
Software includes network management programs and POS transaction processing
packages.
Develop computer programs or make any necessary modifications to software
packages that are acquired.
Prepare training materials and documentation on how to operate the new POS
system for managers and salespeople.
Educate and train managers, salespeople, and information systems personnel to
operate the new system.
Test the system and make corrections until it operates properly
Convert to the new system on a phased store-by-store basis to minimize disruption.
Use the first store converted as a pilot installation to help with testing and training.
Perform a postimplementation audit within 30 days of each store's conversion to
determine if the new POS systems are achieving their expected advantages.
12-46
KONVERSI SISTEM
DIRECT CUT OVER
( IMMEDIATE CUT
OVER)
PHASED IN CUT
OVER
PARALELL CUT
OVER
PILOT PROJECT
(Plunge)
12-48
Post-Implementation Activities
System Maintenance
Corrective: fix bugs and logical errors
Adaptive: add new functionality
Perfective: improve performance
Preventive: reduce chances of failure