Software Proses
Tugas-tugas pekerjaan
project milestones
Hasil pekerjaan PL dan penyelesaian
Poin-poin jaminan kualitas
Proyek PL
Manajemen Kualitas PL
User Satisfaction =
Kesesuaian produk +
kualitas baik +
selesai sesuai dengan budget dan jadwal
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
Tujuan:
10
Perbedaan QC / QA
GOALS
Standards
Standards
SATISFIED
NEEDS
METHODS
Standards
PERFORMANCE
12
Verifikasi:
Validasi:
Budaya kualitas:
Dedikasi kpada kepuasan customer
penekanan pada perbaikan yang berkelanjutan
Komunikasi dan kerja tim
Memberdayakan anggota tim
Komitmen dengan managemen tim
14
CONTROL
CONTROL
INFORMATION
SOFTWARE
DEVELOPER
SOFTWARE
QUALITY FUNCTION
15
=<4%
=< 3%
=< 1%
16
CHALLENGE
TASKS
Review
Applications
W
hentoabort aproject
Executivemanagement ignorance
User ignorance
Audit requirements
Provide
Technical
Advice
Changingtechnology
Useof consultants
Abilitytokeepcurrent technically
Complexityof systems
Knowcurrent technology
Act asinternal consultant
Act astechnical consultant
Knowmanysystems
Reviewand
Builda
Quality
Environment
Howtoevaluatesoftwareproducts
Buildaqualityenvironment
Evaluatesoftwareproducts
Counsel management
Develop
Standards
and
Guidelines
Fewsystemsandprogrammingstandards
Professionalism
Helpset standards
Evaluate qualityof work
Analyse
Development
Errors
Knowtypeof problems
Knowcost of problems
Knowmagnitudeof problems
Quantifyproblems
Identifyproblems
Determinecost of problems
18
Walkthrough
Software Inspection
Technical Review
20
21
Software Inspections
Without Inspection
No. of Employees
Requirements
Planning
Design
With Inspection
Coding
Testing
Time
22
Inspection Process
Planning
Follow-up
Overview
Individual
Preparation
Rework
Inspection
Meeting
23
Feedback
Rework
Analysis
Feedback
Operation 2
Analysis
Feed forward
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
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
Data faults
Inspection check
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
required?
Exception
Have all possible error conditions been taken
into
management faults
account?
Inspection che
31
Technical Reviews
Technically Qualified Team
Evaluates
Suitability for
the intended
use?
Software Product
Rework/Follow-up
Review Report
Action Item List
34
Typical Goals
Typical Attributes
Walkthroughs
Minimal overhead
Developer training
Quick turnaround
Little/no preparation
Informal process
No measurement
Not FTR!
Technical
Reviews
Requirements elicitation
Ambiguity resolution
Training
Formal process
Author presentation
Wide range of discussion
Inspections
Formal process
Checklists
Measurements
Verify phase
Referensi