Software Proses
3
Manajemen Kualitas PL
Kesesuaian produk +
kualitas baik +
4
Terminologi Proses Kualitas
Tujuan Kualitas :
Mencapai dan menopang kualitas produk/layanan
untuk memenuhi kebutuhan customer
Memberikan jaminan ke manajemen bahwa
kualitas telah dicapai dan dipelihara
Memberikan jaminan ke customer bahwa kualitas
telah tercapai
Kebijakan Kualitas
Sasaran dan arah kualitas keseluruhan dari sebuah
organisasi terkait dengan kualitas yang secara
formal dinyatakan oleh top manajemen
6
Terminologi Proses Kualitas
7
Terminologi Proses Kualitas
8
Terminologi Proses Kualitas
9
Terminologi Proses Kualitas
10
Terminologi Proses Kualitas
Perbedaan QC / QA
QC – bekerja dengan produk
Mengukur produk berdasarkan standard
Mengenali kerusakan/cacat
Sebatas pada melihat produk
QA – bekerja dengan proses
Sebuah fungsi yang mengatur kualitas
setup QC
Menggunakan hasil QC untuk mengevaluasi dan
meningkatkan proses yang menghasilkan produk
11
Terminologi Proses Kualitas
EVALUATION OBJECTIVES
of a
GOALS
SOFTWARE QUALITY FUNCTION
Standards Standards
SATISFIED
NEEDS
METHODS PERFORMANCE
Standards
12
Terminologi Proses Kualitas
MANAGEMENT
CONTROL CONTROL
INFORMATION
SOFTWARE SOFTWARE
DEVELOPER
QUALITY FUNCTION
15
Ukuran Tim Software Quality
=>4% SAMPLE OF 135 ORGANISATIONS (1983)
=<4%
Software Quality Staff / Development Staff
=< 3%
=< 1%
Review
Applications
Provide
T echnical Advice
Review
and Build a
Quality Environment
Develop Standards
and Guidelines
Analyse Development Errors
17
Tugas Tim Software Quality
ROLE CHALLENGE TASKS
18
Peran Utama Tim Software Quality
Peran utama Tim SQ adalah Review Applications.
19
Apa itu Software Review?
20
Tiga Tipe Software Review
21
Software Inspections
Without Inspection
No. of Employees
With Inspection
Requirements
Planning Design Coding
Testing
Time
22
Inspection Process
Planning
Follow-up
Overview
Individual Rework
Preparation
Inspection
Meeting
23
Software Inspection Overview
Operation 1 I
Error
feedback Analysis
Operation 1 I Operation 2
25
Prosedur Inspeksi
Program yg akan diinspeksi diserahkan kpd team
inspeksi
Kode dan dokumen terkait didistribusikan dlm tahap
peninjauan saat mendeskripsikan apa yg menjadi tujuan
program
Harus berlangsung relatif singkat (tidak lebih dari 2 jam)
Tim tidak boleh menyarankan bgm cacat harus
diperbaiki
Setelah inspeksi, program diubah oleh pembuatnya utk
membetulkan masalah yg ditemukan
Inspeksi ulang tidak mutlak harus dilakukan
Team Inspeksi
Tim paling sedikit terdiri dari 4 orang
Pembuat program adalah org yg bertanggung jawab
menghasilkan program yg akan di inspeksi
Inspector adalah orang yg menemukan error, hal-hal
yg tidak terdeteksi dan ketidak konsistenan pd
program
Reader (pembaca) adalah oarng yg menguraikan
program dgn kata-katanya sendiri dlm rapat inspeksi
Moderator adalah org yg menangani proses &
memfasilitasi inspeksi
Inspection checklists
(daftar error)
Untuk memandu kegiatan inspeksi
Tergantung bahasa pemrograman yang
digunakan
Contoh : inisialisasi, penamaan constanta,
Examples: Initialisation, Constant naming, loop
termination, dll.
Fault class Inspection check
Data faults Are all program variables initialised before their values
are used?
Have all constants been named?
Should the lower bound of arrays be 0, 1, or something
else?
Should the upper bound of arrays be equal to the size of
the array or Size -1?
If character strings are used, is a delimiter explicitly
assigned?
Control faults For each conditional statement, is the condition correct?
Is each loop certain to terminate?
Are compound statements correctly bracketed?
In case statements, are all possible cases accounted for?
Input/output faults Are all input variables used?
Are all output variables assigned a value before they are
output?
Interface faults Do all function and procedure calls have the correct
number of parameters?
Do formal and actual parameter types match?
Are the parameters in the right order?
If components access shared memory, do they have the
same model of the shared memory structure?
Storage management If a linked structure is modified, have all links been
faults correctly reassigned?
If dynamic storage is used, has space been allocated
correctly?
Is space explicitly de-allocated after it is no longer
Exception
required?
Have all possible error conditions been taken into
Inspection che
management faults account?
Pengukuran Proses Inspeksi
500 statement/jam selama peninjauan
31
Synchronous Review Process
Asynchronous Review Process
Technical Reviews
Suitability for
the intended
use?
Software Product
Rework/Follow-up
•Review Report
•Action Item List
34
Families of Review Methods
Method Family Typical Goals Typical Attributes
Walkthroughs Minimal overhead Little/no preparation
Developer training Informal process
Quick turnaround No measurement
Not FTR!
Technical Requirements elicitation Formal process
Reviews Ambiguity resolution Author presentation
Training Wide range of discussion
Inspections Detect and remove all Formal process
defects efficiently and Checklists
effectively Measurements
Verify phase
Source: Johnson, P. M. (1996). Introduction to formal technical reviews.
Referensi
36