You are on page 1of 15

2.

Process
2.1 Software Development Life Cycle
2.2 Software Effort Estimation

2.1 Software Development Life


Cycle

2.1.1 Planning

When Do Software Projects Begin?


When someone sees an opportunity to c
reate business value from using informat
ion technology
Then he or she creates a system request
Feasibility analysis is used to aid in the
decision of whether or not to proceed w
ith the project
4

Software Development Life Cycle (SDLC)

Planning
Implementati
on

Design
5

Analysis

(Dennis, 2012)

Software Development Life Cycle (S


DLC)
1. Planning: Why build the system?

System request, feasibility analysis

2. Analysis:

Who, what, when, where will the system be?


Requirement gathering, business process modeling

3. Design:

How will the system work?


Program design, user interface design, data design

4. Implementation:

System construction and delivery


System construction, testing, documentation and insta
llation
6

1. Planning System Request


Elemen

Deskripsi

Contoh

Business
Need

The businessrelated reason for


initiating the
software
development
project

Increase sales
Improve market share
Improve access to information
Improve customer service
Decrease product defects
Streamline supply acquisition processes

Business
Requirem
ents

The business
capabilities that
software will
provide

Provide onIine access to information


Capture customer demographic
information
Include product search capabilities
Produce management reports
Include online user support

Business
Value

The benefits that


the software will
create for the
organization

3% increase in sales
% increase in market share
10% operational cost reduction
$200,000 cost savings from decreased
supply costs
$150,000 savings from removal of

System Request Case Study


Menu Utama
1.
Melihat Saldo
2.
Mentransfer Uang
3.
Mengambil Uang
4.
Logout

Kotak Uang

Kotak Kartu
Kotak
Kuitansi

System Request Online ATM System


Project
Sponsor:
Business
Need:

Margaret Mooney, Vice President of Marketing


Project ini dibuat dengan tujuan untuk mendapatkan
pelanggan baru yang menggunakan Internet dam
memberikan layanan yang lebih baik ke pelanggan
yang ada melalui layanan berbasis Internet

Business Requirements:

Dengan menggunakan Online ATM System, pelanggan dapat


melakukan seluruh transaksi perbankan. Fitur utama yang ada
pada sistem ini adalah:
1.Pengecekan Saldo
2.Pengiriman Uang
3.Transaksi Pembayaran Tagihan
Business Value:

Keuntungan Intangible:
- Meningkatkan layanan ke pelanggan
- Mengurangi komplen dari pelanggan
Keuntungan Tangible:
- $750,000 transaksi keuangan dari pelangan baru
10
- $1,875,000 transaksi keuangan
dari pelanggan lama

Latihan Studi Kasus


Buat Business need, System Request dan bu
siness value dari ide perangkat lunak untuk P
KM karsa cipta.
Ada kesempatan untuk memperbaiki ide jika
diperlukan
Jika anda punya 10 ide, maka kesepuluhnya
dibuatkan business need, system request dan
business value
Dikumpulkan di tulisan kertas A4, paling lam
bat hari Jumat, 30 September 2016 jam 11.
00
11

Reference (Foundation)
Ian Sommerville, Software Engineering 10th Edition, Ad
dison-Wesley, 2015
Roger S. Pressman, Software Engineering: A Practitione
rs Approach 8th Edition, McGraw-Hill, 2014
P. Bourque and R.E. Fairley, eds., Guide to the Software
Engineering Body of Knowledge Version 3.0, IEEE Com
puter Society, 2014
Albert Endres dan Dieter Rombach, A Handbook of Soft
ware and Systems Engineering, Pearson Education Limi
ted, 2003
Yingxu Wang, Software Engineering Foundations: A Sof
tware Science Perspective, Auerbach Publications, Tayl
or & Francis Group, 2008

Reference (Process)
Alan Dennis et al, Systems Analysis and Design with
UML 4th Edition, John Wiley and Sons, 2012
Dan Pilone and Russ Miles, Head First Software Devel
opment, OReilly Media, 2008
Barclay and Savage, Object-Oriented Design with UM
L and Java, Elsevier, 2004
Kenneth E. Kendall and Julie E Kendall, Systems Analy
sis and Design 8th Edition, Prentice Hall, 2010
Hassan Gomaa, Software Modeling and Design: UML,
Use Cases, Patterns, and Software Architectures, Cam
bridge University Press, 2011
Layna Fischer (edt.), BPMN 2.0 Handbook Second Edi
tion, Future Strategies, 2012

Reference (Quality)
Daniel Galin, Software Quality Assurance, Ad
dison-Wesley, 2004
Kshirasagar Naik and Priyadarshi Tripathy, S
oftware Testing and Quality Assurance, John
Wiley & Sons, Inc., 2008
Jeff Tian, Software Quality Engineering, John
Wiley & Sons, Inc., 2005
G. Gordon Schulmeyer, Handbook of Softwar
e Quality Assurance Fourth Edition, Artech H
ouse, 2008

Reference (Research)
Christian W. Dawson, Project in Computing and Informatio
n System a Student Guide 2nd Edition, Addison-Wesley, 20
09
Mikael Berndtsson, Jrgen Hansson, Bjrn Olsson, Bjrn Lu
ndell, Thesis Projects - A Guide for Students in Computer S
cience and Information System 2nd Edition, Springer-Verla
g London Limited, 2008
Mary Shaw, Writing Good Software Engineering Research P
apers, Proceedings of the 25th International Conference on
Software Engineering, 2003
C. Wohlin, P. Runeson, M. Host, M. C. Ohlsson, B. Regnell, a
nd A. Wesslen, Experimentation in Software Engineering, Sp
ringer, 2012
P. Runeson, M. Host, A. Rainer, and B. Regnell, Case Study
Research in Software Engineering: Guiidelines and Example
s, John Wiley & Sons, Inc., 2012
15