Pada bagian pertama ini, menjelaskan tentang : gambaran umum perangkat lunak, Perkembangan Perangkat lunak, Karakteristik, Krisis perangkat lunak, Mitos Perangkat lunak, dan Advice-advice pada perangkat lunak

1. ANDY RACHMAN

2. TUJUAN BAB 1
• Mahasiswa memahami tentang Perangkat
Lunak.
• Mahasiswa memahami Karakteristik Perangkat
Lunak dan Perangkat Lunak Aplikasi
• Mahasiswa memahami Mitos Perangkat Lunak
• Mahasiswa mengetahui Krisis Perangkat Lunak
• Mahasiswa mengetahui tentang Proses
Perangkat Lunak

3. MATERI

4. INTRODUCTION
LAPISAN
PERANGKAT
LUNAK
LAPISAN
PERANGKAT
LUNAK
LAPISAN
PERANGKAT
KERAS
LAPISAN
PERANGKAT
KERAS
SISTEM
KOMPUTER
SISTEM
KOMPUTER

5. INTRODUCTION
PENGENALAN SISTEM OPERASI
HARDWARE
OPERATING SYSTEM
APPLICATION

6. INTRODUCTION

7. THE EVOLVE ROLE of SOFTWAREROLEofSOFTWARE
PRODUCT
VEHICLE for delivering Product

8. THE EVOLVE ROLE of SOFTWARE
• Ada beberapa hal yang sering muncul pada
dunia industri sehubungan dengan
pengembangan perangkat lunak :
• Why does it take so long to get software finished?
• Why are development costs so high?
• Why can't we find all the errors before we give the
software to customers?
• Why do we continue to have difficulty in measuring
progress as software is being developed?

9. SOFTWARE CHARACTERISTIC
Software is
developed or
engineered, it is
not
manufactured in
the classical
sense.
Software is
developed or
engineered, it is
not
manufactured in
the classical
sense.
Software doesn't
"wear out."
Software doesn't
"wear out."
Although the
industry is moving
toward
component-based
assembly, most
software
continues to be
custom built
Although the
industry is moving
toward
component-based
assembly, most
software
continues to be
custom built

10. SOFTWARE CHARACTERISTIC

11. HARDWARE CHARACTERISTIC

12. SOFTWARE CHARACTERISTIC
• A software component should
be designed and implemented
so that it can be reused in
many different programs

13. SOFTWARE : CRISIS ON THE HORIZON
• SOFTWARE CRISIS :
• ASSOCIATED with SOFTWARE DEVELOPMENT
• The difficulty of writing useful and efficient computer
programs in the required time.
• The software crisis was due to the rapid increases in
computer power and the complexity of the problems
that could be tackled.
• The causes of the software crisis were linked to the
overall complexity of hardware and the software
development process

14. SOFTWARE : CRISIS ON THE HORIZON
• The crisis manifested itself in several ways:
• Projects running over-budget
• Projects running over-time
• Software was very inefficient
• Software was of low quality
• Software often did not meet requirements
• Projects were unmanageable and code difficult to
maintain
• Software was never delivered

15. SOFTWARE MYTHS
CUSTOMER
MYTHS
PRACTITIONER’s
MYTHS
SOFTWARE MYTHS
(MITOS PERANGKAT LUNAK)
SOFTWARE MYTHS
(MITOS PERANGKAT LUNAK)
MANAGEMENT
MYTHS

16. SOFTWARE MYTHS
• Buku Panduan (Standard Book) :
– Dengan buku ini dianggap oleh seorang
manager sudah dapat menggantikan
sebuah perangkat lunak.
• Have New Development tools:
– Dengan tools yang baru dan dapat dibeli,
seorang manager berfikir bahwa sudah
cukup untuk menghandle sebuah
perusahaan
• Mongolian Horde Concept:
– Perusahaan dapat dengan mudah
mendapatkan programmer kapanpun
dibutuhkan.
MANAGEMENT
MYTHS

17. SOFTWARE MYTHS
• General Statement of Objective is
Sufficient to begin writing programs:
– Sebuah perusahaan berpandangan bahwa
dengan memiliki detail data tujuan cukup
digunakan untuk membuat sebuah program.
• Project requirements continually change,
but Change can be easily accommodate
because software is Flexible.
– Industri beranggapan dengan adanya software
yang baru akan dapat mengkomodasi
perubahan, padahal perubahan sistem akan
berdampak pada segala sesuatunya, mulai dari
biaya, effort dan lain-lain.
CUSTOMER
MYTHS

18. SOFTWARE MYTHS
PRACTITIONER’s
MYTHS
• Once we write the program and get it to work, our
job is done.
– Anggapan praktisi bahwa sekali sebuah program
dibuat maka pekerjaan dah selesai
• Until I get the program "running" I have no way of
assessing its quality.
– Sekali sebuah program berjalan, maka tidak perlu
lagi mengevaluasi kualitasnya.
• The only deliverable work product for a successful
project is the working.
– Penilaian sebuah Produk adalah jika sebuah project
sudah berjalan (running well/release)
• Software engineering will make us create
voluminous and unnecessary documentation and
will invariably slow us down.
– Software enginering bukan membuat dokumentasi
tetapi dengan software enginering akan didapatkan
suatu produk yan g berkualitas

20. REFERENSI
• Roger S. Pressman, Software Engineering – A
Practitioner’s Approach 5th Edition, 2001,
McGraw-Hill.
• https://en.wikipedia.org/wiki/Software_crisis
• http://users.csc.calpoly.edu/~jdalbey/205/Lec
tures/myths.html