The document discusses 6 common myths about software development. The first myth is that existing manual systems can simply be converted into software. However, more than half of software projects fail or run over budget and time. Building quality software is challenging and requires strong analysis, design, and project management skills. The second myth is that software quality is determined by the technologies used, but quality is really about meeting requirements and user needs regardless of technology. The third myth is that coding ability is the most important developer skill, but software development involves many phases beyond just coding, such as planning, analysis, design, and testing.
The document discusses 6 common myths about software development. The first myth is that existing manual systems can simply be converted into software. However, more than half of software projects fail or run over budget and time. Building quality software is challenging and requires strong analysis, design, and project management skills. The second myth is that software quality is determined by the technologies used, but quality is really about meeting requirements and user needs regardless of technology. The third myth is that coding ability is the most important developer skill, but software development involves many phases beyond just coding, such as planning, analysis, design, and testing.
The document discusses 6 common myths about software development. The first myth is that existing manual systems can simply be converted into software. However, more than half of software projects fail or run over budget and time. Building quality software is challenging and requires strong analysis, design, and project management skills. The second myth is that software quality is determined by the technologies used, but quality is really about meeting requirements and user needs regardless of technology. The third myth is that coding ability is the most important developer skill, but software development involves many phases beyond just coding, such as planning, analysis, design, and testing.
The document discusses 6 common myths about software development. The first myth is that existing manual systems can simply be converted into software. However, more than half of software projects fail or run over budget and time. Building quality software is challenging and requires strong analysis, design, and project management skills. The second myth is that software quality is determined by the technologies used, but quality is really about meeting requirements and user needs regardless of technology. The third myth is that coding ability is the most important developer skill, but software development involves many phases beyond just coding, such as planning, analysis, design, and testing.
SD Sompok Semarang (1987) SMPN 8 Semarang (1990) SMA Taruna Nusantara Magelang (1993) B.Eng, M.Eng and Ph.D in Software Engineering from Saitama University Japan (1994-2004) Universiti Teknikal Malaysia Melaka (2014) Research Interests: Software Engineering, Machine Learning Founder dan Koordinator IlmuKomputer.Com Peneliti LIPI (2004-2007) Founder dan CEO PT Brainmatics Cipta Informatika 2
Mengapa Pengembangan Software?
Software Di Sekitar Kita
Hampir semua peralatan elektronik digerakkan oleh software! Mobil, pesawat terbang, kapal laut, Telepon, bangunan, kota,
Semua disiplin ilmu menggunakan software!
Teknik dan sains (teknik sipil, teknik mesin, teknik geologi, ) Kedokteran, farmasi,
Hardware tidak berfungsi tanpa software di dalamnya
5 Best Jobs in the World
1. Software Engineer: $80,500 Average Pay and 46% 10 Year Growth
2. College Professor: $81,500 Average Pay and 31% 10 Year Growth
3. Financial Adviser: $122,500 Average Pay and 26% 10 Year Growth
4. Human Resources Manager:
$73,500 Average Pay and 23% 10 Year Growth
5. Physician Assistant: $75,000 Average Pay and 50% 10 Year Growth 5
The World's Billionaires
Rasio Jumlah Entrepreneur
12% 10%
10%
10%
8%
7%
6% 4%
4%
4%
2%
1%
0% Jepang
China
Singapura
Thailand 7
Malaysia
Indonesia
6 Mitos Kesalahan Pengembangan Software
MITOS 1 Cara yang Ada Sekarang Masih Manual, Karena Itu Akan Saya Buatkan Softwarenya!
Systems Development Projects Fail
More than half of all systems development projects Fail (42% - Standish Group, 53% - General Accounting Office)
Canceled before completion
System is never used once finished Doesn't provide the expected benefits
Most of the ones that don't fail:
Are delivered late Are over budget Don't provide the features promised 10
Recent Significant IT Failures
Company
Year
Outcome
Hudson Bay (Canada)
2005
Inventory system problems lead to $33.3
million loss
UK Inland Revenue
2004/5
$3.45 billion tax-credit overpayment caused
by software errors
Avis Europe PLC (UK)
2004
Enterprise resource planning (ERP) system
cancelled after $54.5 million spent
Ford Motor Co.
2004
Purchasing system abandoned after
deployment costing approximately $400 M
Hewlett-Packard Co.
2004
ERP system problems contribute to $160
million loss
AT&T Wireless
2004
Customer relations management (CRM)
system upgrade problems lead to $100M loss 11
Building software will always be hard.
There is inherently no silver bullet (Brooks, 1987)
The Challenges in Software Engineering
Good software: Should deliver the functionality and performance that the software users need Should be maintainable, dependable and usable (Sommerville, 2012)
14
Teori Dasar Komputasi
Manusia itu lambat tapi cerdas Komputer itu cepat tapi bodoh
Serahkan masalah kecepatan pada
komputer, dan prioritaskan urusan kecerdasan kepada manusia 15
Analisis Kembali Sistem di Sekitar Kita
Sistem Komputerisasi KTP Sistem e-KTP Sistem Pencatatan Pembersihan Toilet Sistem e-Learning di Universitas
Tidak Semua Sistem Bermanfaat dan Layak
Dikembangkan! 16
MITOS 2 Kualitas Software Dinilai dari Teknologi yang Digunakan
Sofware Quality? Software quality is (IEEE, 1991): 1. The degree to which a system, component, or process meets specified requirements 2. The degree to which a system, component, or process meets customer or user needs or expectations
Quality means conformance
to requirements (Crosby, 1979) 18
Software untuk Pesan Ojek (Go-Jek)
19
20
21
Kualitas Software? Teknologi bukan faktor terpenting dari kualitas software!
Keunikan ide adalah hal yang menentukan
kualitas software
22
MITOS 3 Kemampuan Terpenting bagi Developer adalah Kemampuan Coding
Systems Development Life Cycle (SDLC)
Planning
Implementation
Analysis
Design 24
Effort Distribution
25
Project Phases 1. Planning: Why build the system?
System request, feasibility analysis, project size
estimation
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
installation
26
Planning 1. Identifying business value (System Request) Lower costs Increase profits
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 - $1,875,000 transaksi keuangan dari pelanggan lama - $50,000 pengurangan biaya telepon untuk melayani pelanggan 28
Feasibility Analysis - Online ATM System
Margaret Mooney and Alec Adams created the following feasibility analysis for the Online ATM System Project.
1. Technical Feasibility The Online ATM System is feasible technically, although there is some risk. 1.1 Online ATM Systems risk regarding familiarity with the application is high
The Marketing Department has little experience with Internet-based marketing and sales The IT Department has strong knowledge of the companys existing ATM systems, however, it has not worked with Web-enabled ATM systems.
1.2 Online ATM Systems risk regarding familiarity with the technology is medium
The IT Department has relied on external consultants to develop its existing Web env. The IT Department has learned about Web technology by maintaining the corporate site
1.3 The project size is considered medium risk
The project team likely will include less than ten people Business user involvement will be required The project timeframe cannot exceed a year and it should be much shorter
1.4 The compatibility with existing technical infrastructure should be good
The current ATM System is a client-server system built using open standards. An interface with the Web should be possible Retail bank already place and maintain orders electronically An Internet infrastructure already is in place at retail bank and at the corporate headquarters 29
2. Economic Feasibility A costbenefit analysis was performed. A conservative approach shows that the Online ATM System has a good chance of adding to the bottom line of the company significantly. Return on Investment (ROI) over 3 years: 229 percent Break-even point (BEP) occurs: after 1.7 years Total benefit after three years: $3.5 million
3. Organizational Feasibility From an organizational perspective, this project has low risk. The objective of the system, which is to increase sales, is aligned well with the senior managements goal of increasing sales for the company. The move to the Internet also aligns with Marketings goal to become more savvy in Internet marketing and sales. The project has a project champion, Margaret Mooney, Vice President of Marketing. Margaret is well positioned to sponsor this project and to educate the rest of the senior management team when necessary. Much of senior management is aware of and supports the initiative. 30
Increased sales from new customers
Increased sales from existing customers Reduction in customer complaint calls Total Benefits: PV of Benefits: PV of All Benefits: Labor: Analysis, Design and Implementation Consultant Fees Office Space and Equipment Software and Hardware Total Development Costs: Labor: Webmaster Labor: Network Technician Labor: Computer Operations Labor: Business Manager Labor: Assistant Manager Labor: 3 Staff Software upgrades and licenses Hardware upgrades User training Communications charges Marketing expenses Total Operational Costs: Total Costs: PV of Costs: PV of all Costs: Total Project Costs Less Benefits: Yearly NPV: Cumulative NPV: Return on Investment (ROI): Break-even Point (BEP):
(BEP in Year 2 = [2,094,731 1,415,119] / 2,094,731 = 0.32)
Software Development Artifacts
1. Planning
System Proposal
1.1 System Request
1.2 Feasibility Analysis
2. Analysis 2.1 Use Case Diagram 2.2 Activity Diagram 2.3 Sequence Diagram
System Specification
3. Design 3.1 Class Diagram 3.2 Deployment Diagram 3.3 User Interface Design 3.4 Data Model
4. Implementation
New Software
4.1 Program Code
4.2 Testing Plan 4.3 Documentation 32
Kemampuan Coding? Penting! Tapi lebih penting lagi kemampuan membaca kebutuhan riil masyarakat dan kemampuan analisis kelayakan dari software yang kita kembangkan
33
MITOS 4 Kalau Project Software Molor, Tinggal Tambah Pengembang Saja!
Hukum Penambahan Pengembang
Adding manpower to a late project makes it later (Brook, 1975) Just because a woman can make a baby in nine months, it does not follow that nine women can make a baby in one month
35
Anekdot di Pengembangan Software
Project Manager is a person who thinks nine women can deliver a baby in one month Developer is a person who thinks it will take 18 months to deliver a baby Client is the one who doesn't know why he wants a baby Marketing Manager is a person who thinks he can deliver a baby even if no man and woman are available Tester is a person who always tells his wife that this is not the right baby Human Resource is a person who thinks that a donkey can deliver a human baby if given 9 months 36
MITOS 5 Software yang Saya Buat ini Mirip dengan Software yang Ada
Kejar Ceruk Pasar Baru
Don't Reinvent The Wheel! Lakukan komparasi terhadap aplikasi sejenis, lihat dimana ada gap dan ceruk pasar yang belum tergarap Jangan pernah membuat software yang sama saja dengan yang ada saat ini Buat aplikasi untuk segmen pasar baru dan diprediksi besar 38
MITOS 6 Pengembangan Software Saya Lakukan Hanya untuk Mencari Nafkah, Sebenarnya Saya Tidak Menyukainya
Satu hal yang membuat
saya tetap bertahan adalah bahwa saya mencintai apa yang saya lakukan... (Steve Jobs)
Saya tidak keberatan dengan
5 tahun dan 5126 kegagalan saya dalam membuat penyedot debu dual cyclone tanpa kantung... (James Dyson)
Kesalahan terbesar saya
adalah mencoba membuat alat pancing, padahal saya tidak suka memancing dan tidak pernah pergi memancing... (Eli Harari)
Lakukan Yang Kita Cintai, dan Cintai
Yang Kita Lakukan Para inovator selalu bekerja dan menikmati kesuksesannya pada bidang yang mereka memang benar-benar mencintai
43
6 Mitos Pengembangan Software
Mitos 1: Cara Sekarang Manual, Perlu Dibuatkan Software Mitos 6: Saya Tidak Suka Mengembangkan Software
Mitos 2: Kualitas Software Dinilai dari Teknologi Yang Digunakan
