Professional Documents
Culture Documents
Manajemen Kualitas Sistem Informasi
Manajemen Kualitas Sistem Informasi
Informasi
Referensi
Buku Utama:
1. Daniel Galin, Software Quality ASsurance, From theory to
implementation,Pearson, Adisson Wesley, 2004
2. G.Gordon S., James I.Mc Manus, “Handbook of software quality
assurance”, 3rd ed, Prentice Hall, NEW JERSEY
3. Software Engineering : A Practtioner’s Approach, 2001 Oleh :
Roger S Pressman, PhD
Buku Tambahan:
W.E.Perry “Quality Assurance for Information Systems”,QED Information
Sciences,Inc,1991
Main Problems Addressed
Deliver software system that...
does what it is supposed to do.
does the things correctly.
show/demonstrate/prove it (“does").
Major difficulties for the above:
Size: MLOC products common
Complexity
Environmental stress/constraints
Flexibility/adaptability expected
“no silver bullet", but...
SQE (software quality engineering) helps
Major SQE activities
Scope and content hierarchy
System Implementation
6
PEOPLE’S QUALITY EXPECTATIONS
1. quality planning;
2. execution of selected QA or software validation and
verification activities;
3. measurement and analysis to provide convincing evidence
to demonstrate software quality to all parties involved.
Quality ?
The American Heritage Dictionary defines quality as “a
characteristic or attribute of something.”
Dalam PL :
Kualitas desain : karakteristik yang ditetapkan
Kualitas konformasi : tingkat dimana spesifikasi desain terus diikuti
selama pembuatan
Dalam SW development :
Kualitas desain mencakup syarat, spesifikasi dan desain sistem
Quality: views and attributes
FAKTOR KUALITAS PERANGKAT LUNAK
11
McCall’s Triangle of Quality
Maintainability Portability
Flexibility Reusability
Testability Interoperability
PRODUCT OPERATION
Correctness Usability Efficiency
Reliability Integrity
12
FAKTOR KUALITAS … (McCall)
13
SQA/Jaminan Kualitas Sistem
14
SQA (lanj.)
SQA dimulai dgn sekumpulan alat & metode teknis yg membantu analis utk
mendapatkan spesifikasi yg berkualitas tinggi & bagi perancang utk
merancang dg kualitas tinggi
Setelah spesifikasi & desain dibuat, ditetapkan kualitasnya dg melakukan
review teknis formal.
Pengujian per. Lunak mengkombinasikan langkah2 strategi dg metode
rancangan test-case yg dpt menjamin pendeteksian kesalahan secara efektif.
Jika terdapat standar yg formal, berarti harus dapat dijamin bahwa standar
tsb diikuti.
15
SQA (lanj.)
16
REVIEW PERANGKAT LUNAK
17
PERTEMUAN PADA REVIEW TEKNIS FORMAL
Batasannya
Antara 3 & 5 orang yg terlibat : pemimpin review, pereview & produsen
Persiapan sebelumnya tidak lebih 2 jam kerja per orang
Lama pertemuan review minimal 2 jam
Fokus : produk, komponen program (spesifikasi kebutuhan,
perancangan modul detail, listing koding utk setiap modul
Akhir review, harus diputuskan
Menerima produk tanpa modifikasi
Menolak produk krn kesalahan yg fatal
Menerima produk dg kesalahan yg kecil dan harus diperbaiki
18
PENDOKUMENTASIAN PADA REVIEW TEKNIS FORMAL
19
PEDOMAN REVIEW TEKNIS FORMAL
20
resource
Software Engineering By RogerPressman
PROGRAM S2 UNIVERSITAS GUNADARMA
Software Quality Engineering : Testing, Quality Assurance, and
Quantiable Improvement by Je Tian