Presentasi sedang didownload. Silahkan tunggu

Presentasi sedang didownload. Silahkan tunggu

REKAYASA PERANGKAT LUNAK :: PROGDI SISTEM INFORMASI :: 2010.

Presentasi serupa


Presentasi berjudul: "REKAYASA PERANGKAT LUNAK :: PROGDI SISTEM INFORMASI :: 2010."— Transcript presentasi:

1 REKAYASA PERANGKAT LUNAK :: PROGDI SISTEM INFORMASI :: 2010

2 Tujuan 1. Mahasiswa memahami produk dan proses dalam rekayasa perangkat lunak. 2. Mahasiswa memahami dasar-dasar manajemen proyek perangkat lunak. 3. Mahasiswa memahami metode rekayasa perangkat lunak konvensional.

3 Topik Perkuliahan 1. Produk RPL 2. Proses RPL 3. Konsep Manajemen Proyek - 4. Proses dan Metrik Proyek Perangkat Lunak – Faisal TS 5. Perencanaan Proyek Perangkat Lunak - Johan 6. Manajemen dan Analisa Resiko - Novtori 7. Penjadwalan dan Penelusuran Proyek - Akbar 8. Jaminan Kualitas Perangkat Lunak – Wahyu AD 9. Manajemen Konfigurasi Perangkat Lunak - Ronny 10. Analisa Sistem - Tannia 11. Desain Perangkat Lunak - Rizal 12. Pengujian Perangkat Lunak - Ibnu

4 Penilaian 60 % UTS, UAS 60 % UTS, UAS 30 % Tugas, Quiz 30 % Tugas, Quiz 10 % Kehadiran 10 % Kehadiran NOTE: NOTE: Toleransi keterlambatan 30 menit. Toleransi keterlambatan 30 menit. Pakaian bebas rapi sopan. Pakaian bebas rapi sopan. Ijin tidak masuk maksimal 1 pekan setelahnya. Ijin tidak masuk maksimal 1 pekan setelahnya. Minimal 75% kehadiran untuk ikut ujian. Minimal 75% kehadiran untuk ikut ujian.

5 Tugas Kelompok 1. Setiap pertemuan diawali dengan paparan kelompok yang bertugas hari itu. 2. Jumlah file paparan antara 10 – 15 slide. 3. Waktu paparan maksimal 30 menit. 4. Baca dan coba pahami dulu materi yang akan dipaparkan. 5. Tanya jawab maksimal 30 menit. 6. Setiap anggota kelompok berhak menyampaikan pendapat.

6 What to Do? Buat 10 kelompok tiap kelompok terdiri dari 4-5 orang. Tulis NPM dan nama anggotanya. Buat 10 kelompok tiap kelompok terdiri dari 4-5 orang. Tulis NPM dan nama anggotanya. Tugas masing-masing kelompok adalah membuat resume sebuah bab pertemuan 3-12 dari buku referensi. Tugas masing-masing kelompok adalah membuat resume sebuah bab pertemuan 3-12 dari buku referensi. Resume ditulis dalam bahasa Indonesia dilengkapi dengan file untuk presentasi. Resume di-print di kertas A4, spasi 1.5, margin , font TNR 12 minimal 10 halaman. Resume dikumpulkan pada saat paparan. Resume ditulis dalam bahasa Indonesia dilengkapi dengan file untuk presentasi. Resume di-print di kertas A4, spasi 1.5, margin , font TNR 12 minimal 10 halaman. Resume dikumpulkan pada saat paparan. Presentasi kelompok dilakukan sesuai dengan jadwal pertemuan kuliah. Presentasi kelompok dilakukan sesuai dengan jadwal pertemuan kuliah.

7 What is S/W Engineering?

8 SWEBOK IEEE

9

10 SOFTWARE PRODUCT PERTEMUAN #1

11 Computer Software What is it? What is it? Who does it? Who does it? Why is it important? Why is it important? What are the steps? What are the steps? What is the work product? What is the work product? How do I ensure that I’ve done it right? How do I ensure that I’ve done it right?

12 What is it? Computer software is the product that software engineers design and build. It encompasses programs that execute within a computer of any size and architecture, documents that encompass hard-copy and virtual forms, and data that combine numbers and text but also includes representations of pictorial, video, and audio information.

13 Who does it? Software engineers build it, and virtually everyone in the industrialized world uses it either directly or indirectly.

14 Why is it important? Because it affects nearly every aspect of our lives and has become pervasive in our commerce, our culture, and our everyday activities.

15 What are the steps? You build computer software like you build any successful product, by applying a process that leads to a high-quality result that meets the needs of the people who will use the product. You apply a software engineering approach.

16 What is the work product? From the point of view of a software engineer, the work product is the programs, documents, and data that are computer software. But from the user’s viewpoint, the work product is the resultant information that somehow makes the user’s world better.

17 How do I ensure that I’ve done it right? Read the remainder of this book, select those ideas applicable to the software that you build, and apply them to your work.

18 THE EVOLVING ROLE OF SOFTWARE Today, software takes on a dual role. It is a product and, at the same time, the vehicle for delivering a product. Software delivers the most important product of our time—information. Software transforms personal data (e.g., an individual’s financial transactions) so that the data can be more useful in a local context; it manages business information to enhance competitiveness; it provides a gateway to worldwide information networks (e.g., Internet) and provides the means for acquiring information in all of its forms.

19 Continue… The role of computer software has undergone significant change over a time span of little more than 50 years. Dramatic improvements in hardware performance influence computer based system. The lone programmer of an earlier era has been replaced by a team of software specialists.

20 Software Software is (1) instructions (computer programs) that when executed provide desired function and performance, (2) data structures that enable the programs to adequately manipulate information, and (3) documents that describe the operation and use of the programs.

21 Software Characteristics Software is developed or engineered, it is not manufactured in the classical sense Software doesn't “wear out”. But it does deteriorate! Although the industry is moving toward component-based assembly, most software continues to be custom built.

22 Software Application system software system software real-time software real-time software business software business software engineering/ scientific software engineering/ scientific software embedded software embedded software PC software PC software AI software AI software webApps (Web applications) webApps (Web applications)

23 Some of Software Myths Myth: We already have a book that's full of standards and procedures for building software, won't that provide my people with everything they need to know? Reality: The book of standards may very well exist, but is it used? Are software practitioners aware of its existence? Does it reflect modern software engineering practice? Is it complete? Is it streamlined to improve time to delivery while still maintaining a focus on quality? In many cases, the answer to all of these questions is "no.“

24 Continue… Myth: My people have state-of-the-art software development tools, after all, we buy them the newest computers. Reality: It takes much more than the latest model mainframe, workstation, or PC to do high- quality software development. Computer-aided software engineering (CASE) tools are more important than hardware for achieving good quality and productivity, yet the majority of software developers still do not use them effectively.

25 Continue… Myth: A general statement of objectives is sufficient to begin writing programs—we can fill in the details later. Reality: A poor up-front definition is the major cause of failed software efforts. A formal and detailed description of the information domain, function, behavior, performance, interfaces, design constraints, and validation criteria is essential. These characteristics can be determined only after thorough communication between customer and developer.

26 Continue… Myth: Project requirements continually change, but change can be easily accommodated because software is flexible. Reality: It is true that software requirements change, but the impact of change varies with the time at which it is introduced.

27 Impact of Change

28 Another… Myth: Once we write the program and get it to work, our job is done. Reality: Someone said that "the sooner you begin 'writing code', the longer it'll take you to get done." Industry data indicate that between 60 and 80 percent of all effort expended on software will be expended after it is delivered to the customer for the first time.

29 Continue… Myth: The only deliverable work product for a successful project is the working program. Reality: A working program is only one part of a software configuration that includes many elements. Documentation provides a foundation for successful engineering and, more important, guidance for software support.

30 Continue… Myth: Until I get the program "running" I have no way of assessing its quality. Reality: One of the most effective software quality assurance mechanisms can be applied from the inception of a project. Software reviews are a "quality filter" that have been found to be more effective than testing for finding certain classes of software defects.

31 SUMMARY Software has become the key element in the evolution of computer-based systems and products. Over the past 50 years, software has evolved from a specialized problem solving and information analysis tool to an industry in itself. But early “programming” culture and history have created a set of problems that persist today. Software has become the limiting factor in the continuing evolution of computer-based systems. Software is composed of programs, data, and documents. Each of these items comprises a configuration that is created as part of the software engineering process. The intent of software engineering is to provide a framework for building software with higher quality.


Download ppt "REKAYASA PERANGKAT LUNAK :: PROGDI SISTEM INFORMASI :: 2010."

Presentasi serupa


Iklan oleh Google