Bug Tracking Database (2) Pertemuan 7

Presentasi berjudul: "Bug Tracking Database (2) Pertemuan 7"— Transcript presentasi:

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

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 Bina Nusantara

3 What the Bug Relates To: Subsystem, Configuration, and Quality Risks
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 Bina Nusantara

4 Where the Bug Came From: Resolution and Root Cause
Bina Nusantara

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

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

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

8 The Finalized Bug Tracking Database
Bina Nusantara

9 The Finalized Bug Tracking Database
Bina Nusantara

10 A complete Bug entry Form
Bina Nusantara

11 Bina Nusantara

12 Bina Nusantara

13 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 Bina Nusantara

14 Pengelolaan Bugs Life Cycle
Bina Nusantara

15 Bug State Bina Nusantara

16 Bug State (2) Bina Nusantara

17 Bina Nusantara

18 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 Bina Nusantara

19 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). Bina Nusantara

20 Pelacakan Perubahan Status
Bina Nusantara

21 Informasi Tentang Bug Bina Nusantara

22 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? Bina Nusantara

23 Opened / Closed Charts Bina Nusantara

24 Opened / Closed Charts Bina Nusantara

25 Endless Bug Discovery Bina Nusantara

26 The Nightmare of ignored Bugs
Bina Nusantara

27 The Nightmare of Mismanaged Bugs
Bina Nusantara

28 A Root Cause Breakdown Bina Nusantara

29 A Closure Period Chart Bina Nusantara

30 A Subsystem Breakdown Bina Nusantara

31 Politics and Misuse of Bug Data
Don't Fail to Build Trust Don't Be a Backseat Driver Don't Make Individuals Look Bad Bina Nusantara

32