Kualitas Perangkat Lunak (lanjutan)Pertemuan 3

Matakuliah : M0232/Testing dan ImplementasiTahun : 2008

Bina Nusantara

TIK• Mahasiswa akan dapat menjelaskan dua macam

metoda yang dapat digunakan untuk melakukan penilaian dan analisa terhadap resiko kualitas. (C2) TIK-10

• Mahasiswa dapat menerangkan pengelompokan tahap-tahap proses pelaksanaan pengujian. (C2) TIK-11

• Mahasiswa dapat menyebutkan faktor-faktor yang harus diperhatikan untuk mengestimasi sumber daya dan anggaran yang diperlukan. (C1) TIK-12

• Mahasiswa dapat menjelaskan relasi antara jadwal, sumber daya, anggaran, dan faktor kualitas dalam perencanaan pengujian. (C2) TIK-13

Bina Nusantara

Penilaian dan Analisa Resiko Kualitas

Bina Nusantara

Resiko Kualitas• Bug/Kesalahan yang mungkin terjadi disebut sebagai

resiko kualitas (quality risk).

• Gejala yang ditimbulkan oleh bug yang dapat dirasakan disebut mode kesalahan (failure mode).

• Ada dua metode yang dapat digunakan untuk melakukan penilaian dan analisa terhadap resiko kualitas: (1) Metoda Informal; dan (2) Metoda Formal.

Bina Nusantara

Informal Risks Analysis Techniques• Goals: Address as many of quality risks as

possible, developing tests in an order consistent with customer priorities.

• Breaking down the test process into the classic phases of component testing, integration testing and system testing

Bina Nusantara

Component Testing• States• Transactions• Code Coverage• Data Flow Coverage• Functionality• User Interface• Mechanical Life• Signal Quality

Bina Nusantara

Integration Testing• Component or subsystem interface• Functionality• Capacity and volume• Error / Disaster Handling and recovery• Data Quality• Performance• User Interface

Bina Nusantara

System and Acceptance Testing• Functionality• User Interface• Operations• Capacity and Volume• Reliability, Availability, and

stability• Error/disaster handling and

recovery• Stress• Performance• Date and Time Handling• Localization• Network and Distributed

environments

• Configuration option and compatibility

• Standard compliance• Security• Environment• Power Input, consumption and

output• Shock, vibration and drop• Installation, cut-over, setup and

initial configuration• Documentation and Packaging• Maintainability• Alpha, beta and other live tests

Bina Nusantara

Failure Mode and Effect Analysis• A Formal Method for Understanding Quality Risks• FMEA is a technique for understanding and

prioritizing possible failure modes (or quality risks) in system functions, features, attributes, behaviors, components and interfaces

Bina Nusantara

Bina Nusantara

3. What you can test?

Jadwal, Sumber Daya, dan Anggran(Schedule, Resources, and Budget)

Bina Nusantara

Schedule, Resource, Budget

Bina Nusantara

Tahap-tahap Proses Pelaksanaan Pengujian

• Perencanaan• Konfigurasi• Pengembangan• Pelaksanaan

Bina Nusantara

Penerapan: Fitting a Test Schedule into the Project

Bina Nusantara

Perkiraan Sumber Daya dan Anggaran• Staf• Alat Bantu Pengujian (Test Tools)• Fasilitas dan Pendukung• Sistem Pengujian• Laboratorium Eksternal

Bina Nusantara

Computer User's Bill of Rights1. The user is always right2. The user has the right to easily install and uninstall software and

hardware systems without negative consequences3. The user has the right to a system that performs exactly as promised4. The user has the right to easy-to-use instructions for understanding

and utilizing a system to achieve desired goals and recover efficiently and gracefully from problem situations

5. The user has the right to be in control of the system and to be able to get the system to respond to a request for attention

6. The user has the right to a system that provides clear, understandable, and accurate information regarding the task it is performing and the progress toward completion

7. The user has the right to be clearly informed about all system requirements for successfully using software or hardware

8. The user has the right to know the limits of the system's capabilities9. The user has the right to communicate with the technology provider

and receive a thoughtful and helpful response when raising concerns10.The user should be the master of software and hardware technology,

not vice versa. Products should be natural and intuitive to use.