03012022 Pengantar Disampaikan oleh Dian Saadillah Maylawati Sumber

03/01/2022 (Pengantar) Disampaikan oleh: Dian Sa’adillah Maylawati Sumber: Roger S. Pressman; Software Engineering: A Practitioner's Approach (7 th. Ed. ); Mc Graw-Hill, 2010 RPL/UINBandung/Sem. IV/20152016 Rekayasa Perangkat Lunak 1

RPL/UINBandung/Sem. IV/20152016 System Engineering 2 03/01/2022

RPL/UINBandung/Sem. IV/20152016 Big Pict. Of System Eng. 3 03/01/2022

4 RPL/UINBandung/Sem. IV/20152016 03/01/2022

RPL/UINBandung/Sem. IV/20152016 Product Engineering 5 03/01/2022

6 RPL/UINBandung/Sem. IV/20152016 03/01/2022

RPL/UINBandung/Sem. IV/20152016 Software Engineering 7 03/01/2022

03/01/2022 Apa itu Perangkat Lunak? Definisi: (Computer programs, procedures, and possibly associated documentation and data pertaining to the operation of a computer system) (IEEE Standard Glossary of Software Engineering Terminology, 1990) RPL/UINBandung/Sem. IV/20152016 Program komputer, prosedur, dan dokumentasi serta data yang terkait dengan operasi sistem komputer 8

03/01/2022 • P/L dirancang dan dibangun oleh S/W Engineers • Software engineers have a moral obligation to build reliable software that does no harm to other people. • Software engineers view computer software, as being made up of the programs, documents, and data required to design and build the system. • Software users are only concerned with whether or not software products meet their expectations and make their tasks easier to complete. RPL/UINBandung/Sem. IV/20152016 Apa itu P/L ? 9

03/01/2022 • Produk yang unik • Tidak akan rusak • Tidak dapat ‘dilihat’ • Fleksibel sehingga mudah (? ) dimodifikasi • Kompleksitasnya terus bertambah • Terhubung dengan perangkat keras (hardware) RPL/UINBandung/Sem. IV/20152016 Karakteristik P/L 10

03/01/2022 • P/L sistem • P/L real-time • P/L bisnis • P/L engineering dan scientific • P/L embedded • P/L aplikasi (perkantoran) • P/L berbasis web • P/L dengan kecerdasan buatan RPL/UINBandung/Sem. IV/20152016 Jenis P/L 11

03/01/2022 Software Problems Software used, but criticized or dropped Software used after modifications 19% 3% Software paid for but never delivered 29, 7% Software delivered and used as it is Software delivered but never used 47% 1982: Nine DOD contracts amounting to $6. 8 million (source: GAO, quoted in CMU/SEI-93 -EM-8) RPL/UINBandung/Sem. IV/20152016 2% 12

03/01/2022 Software Problems (2) Testing Specification Distribution of effort: what happens Specification Design Encoding Testing Design Encoding Maintenance RPL/UINBandung/Sem. IV/20152016 Distribution of effort : what is believed 13

03/01/2022 Software Problems (3) Failure Rate "Infant Mortality" "Wear Out" Change Ideal FAILURE CURVE FOR HARDWARE Time FAILURE CURVE FOR SOFTWARE * Software Engineering, Module 1, Richard Conn, University of Cincinnati, May 1993 RPL/UINBandung/Sem. IV/20152016 Actual 14

03/01/2022 Rekayasa P/L • Aplikasi pendekatan yang sistematik, disiplin, terukur terhadap proses pembangunan P/L, operasi P/L, dan perawatan P/L • Mencakup: proses, teknik pengelolaan, metode teknis, dan penggunaan alat bantu RPL/UINBandung/Sem. IV/20152016 (Software engineering is the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software) 15

03/01/2022 Teknologi Berlapis - Rekayasa P/L Alat Bantu Proses Berfokus pada kualitas RPL/UINBandung/Sem. IV/20152016 Metode 16

• Untuk mendapatkan P/L yang benar dan untuk membuat P/L dengan benar • Kompleksitas P/L dapat ditinjau dari: Domain masalah Ukuran data: Digital dan Non Digital Solusi: Algoritma Lokasi • P/L harus benar (correct): Berdasarkan business rule Sejalan dengan segala sesuatu dan semua pihak yang terkait • Pembangunan P/L harus dikelola dengan baik untuk memelihara kebenarannya (correctness) 03/01/2022 RPL/UINBandung/Sem. IV/20152016 Kenapa perlu RPL ? 17

• Ada tanggung-jawab lain, selain tanggun—jawab yang bersifat teknis • S/W engineers harus jujur dan bertanggung-jawab agar disebut profesional • Perilaku yang etis lebih dari sekedar patuh terhadap hukum yang berlaku * Software Engineering 7 th ed, Ian Sommerville 03/01/2022 RPL/UINBandung/Sem. IV/20152016 Tanggung-jawab Profesi dan Etika 18

03/01/2022 • Dikembangkan oleh komunitas profesional di US • Seorang SW engineer harus menanda-tangani kode etik ini agar bisa bergabung dengan komunitas ini • Berisi 8 prinsip * Software Engineering 7 th ed, Ian Sommerville RPL/UINBandung/Sem. IV/20152016 ACM/IEEE Code of Ethics 19

03/01/2022 Code of ethics - principles • PUBLIC Software engineers shall act consistently with the public interest CLIENT AND EMPLOYER Software engineers shall act in a manner that is in the best interests of their client and employer consistent with the public interest • PRODUCT Software engineers shall ensure that their products and related modifications meet the highest professional standards possible * Software Engineering 7 th ed, Ian Sommerville RPL/UINBandung/Sem. IV/20152016 • 20

03/01/2022 Code of ethics - principles • JUDGMENT Software engineers shall maintain integrity and independence in their professional judgment MANAGEMENT Software engineering managers and leaders shall subscribe to and promote an ethical approach to the management of software development and maintenance • PROFESSION Software engineers shall advance the integrity and reputation of the profession consistent with the public interest * Software Engineering 7 th ed, Ian Sommerville RPL/UINBandung/Sem. IV/20152016 • 21

03/01/2022 Code of ethics - principles • COLLEAGUES Software engineers shall be fair to and supportive of their colleagues SELF Software engineers shall participate in lifelong learning regarding the practice of their profession and shall promote an ethical approach to the practice of the profession * Software Engineering 7 th ed, Ian Sommerville RPL/UINBandung/Sem. IV/20152016 • 22