1 / 32

Bug Tracking Database (2) Pertemuan 7

Bug Tracking Database (2) Pertemuan 7. Matakuliah : M0232/Testing dan Implementasi Tahun : 2008. TIK. Mahasiswa dapat menggunakan Bug Tracking Database sebagai alat bantu pengujian. (C3) TIK-23

aysel
Download Presentation

Bug Tracking Database (2) Pertemuan 7

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Bug Tracking Database (2)Pertemuan 7 Matakuliah : M0232/Testing dan Implementasi Tahun : 2008

  2. TIK • Mahasiswa dapat menggunakan Bug Tracking Database sebagai alat bantu pengujian. (C3) TIK-23 • Mahasiswa dapat menghasilkan laporan pengujian dengan baik dalam berbagai macam bentuk grafik. (C3) TIK-24 2

  3. Breakdown the subsystem For DataRocket Case Study, eg: Mainboard Video SCSI Network telecommunication Other hardware BIOS Other software For SpeedyWriter Case Study, eg: User Interface Tools File Edit Engine Install/config Docs/Packaging What the Bug Relates To: Subsystem, Configuration, and Quality Risks

  4. Where the Bug Came From: Resolution and Root Cause

  5. Bug Taxonomy • Functional • Specification • Function • Test • System • Internal Interface • Hardware Devices • Operating System • Software Architecture • Resource Management • Process • Arithmetic • Initialization • Control or Sequence • Static Logic • Other

  6. Bug Taxonomy • Data • Type • Structure • Initial Value • Other • Code • Documentation • Standards • Other • Duplicate • NAP • Bad Unit • RCN • Unknown

  7. How Long Was the Bug Around? • 8 phases of projects • Requirements • Design • Implementation • Component Test • Integration Test • System test • Acceptance Test • Post Release

  8. The Finalized Bug Tracking Database

  9. The Finalized Bug Tracking Database

  10. A complete Bug entry Form

  11. RPN (Risk Priority Numbers) • Prioritas dan Serverity tidak selalu sejalan. Dalam sistem testing mungin ditemukan suatu bug yang memiliki severity 5 tetapi ber-prioritas 1. • RPN = Priority x Serverity • RPN dapat bernilai 1 sampai dengan 25. • Bug yang paling berbahaya memiliki RPN=1

  12. Pengelolaan Bugs Life Cycle

  13. Bug State

  14. Bug State (2)

  15. Tampilan Layar untuk Memasukkan Bug • Bug ID: nomor urut bug. • Date Opened: tanggal pelaporan bug. • Project Name: nama proyek. • Tester: nama teknisi • Severity • Priority: prioritas ; & RPN • Summary, Steps to Reproduce, Isolation

  16. Tampilan Layar untuk Memasukkan Bug(lanjutan) • State (text) • Owner (text): penanggung jawab. • Estimate fix (date): perkiraan bug teratasi. • Status / LOG (memo) • Subsystem: area/komponen yang akan terpengaruh oleh bug. • Configuration: konfigurasi sistem yang mengakibatkan bug. • Close date: tanggal saat bug terselesaikan. • Resolution: penjelasan singkat bagaimana bug diatasi/diperbaiki. • Root Cause: akar penyebab terjadinya kesalahan (developer atau test engineer).

  17. Pelacakan Perubahan Status

  18. Informasi Tentang Bug

  19. Bug Analysis Chart • Generate Bug Analysis Charts • excellent for communicating with management • The information-rich chart provides answers to a number of questions. • Are you ready to ship the product? • Have you finished fixing bugs? • Is the bug management process working? • How do milestones in the project relate to inflection points, changes in the slope of the opened or closed curves?

  20. Opened / Closed Charts

  21. Opened / Closed Charts

  22. Endless Bug Discovery

  23. The Nightmare of ignored Bugs

  24. The Nightmare of Mismanaged Bugs

  25. A Root Cause Breakdown

  26. A Closure Period Chart

  27. A Subsystem Breakdown

  28. Politics and Misuse of Bug Data • Don't Fail to Build Trust • Don't Be a Backseat Driver • Don't Make Individuals Look Bad

More Related