Professional Documents
Culture Documents
Lecture 1
Introduction to Software Quality Engineering
Muhammad Fawad
Lecturer
COMSATS Institute of Information Technology
Sessional # 2 15%
Quizzes 5%
Assignments 5%
Presentations/Projects 15%
• Reference Book:
“Software Quality Assurance From Theory to Implementation
by Daniel Galin
available in soft form
Can earn you a punishment from getting zero in the cheated stuff to awarding an F
grade in the whole course to expulsion from university based on the severity of the act.
A student marked as a cheater twice in assignments will get ZERO in all assignments.
• It is recommended that:
– Be attentive in the class.
– In the first possible free time, do a ‘few problems’ related to
the topic(s) covered in class.
– If you are able to do it, it means you got the point; if not, at
least you know what you do not know. Ask the teacher in the
next class.
– At the weekend, sum up all the week’s study.
• Patriot-Scud
(rounding error, 1991)
• Usability problems
– Producers (Internal)
• Fulfil their contractual commitments to produce product conforming to
product specification.
• “good enough" for the cost
• functionality & correctness via V&V
• cost: managers
• service related: maintainability
• interfacing units: interoperability
• Adaptation of ISO-9126:
• customized for companies
– e.g., IBM's CUPRIMDS.
36
36 COMSATS Institute of Information Technology, Attock Muhammad Fawad
Focus on Correctness 2/2
37
37 COMSATS Institute of Information Technology, Attock Muhammad Fawad
Correctness & Defects: Definitions
38
38 COMSATS Institute of Information Technology, Attock Muhammad Fawad
Correctness & Defects: Definitions
• Defect:
– Generally refers to some problem, either with external behavior or
with internal characteristics
– error/fault/failure are collectively referred to as defects
• Bug/debug:
– not good terms, avoid
– Instead use defect detection & removal
39
39 COMSATS Institute of Information Technology, Attock Muhammad Fawad
Defect and Quality
41
41 COMSATS Institute of Information Technology, Attock Muhammad Fawad
Error, Fault, Failure: Relation
42
42 COMSATS Institute of Information Technology, Attock Muhammad Fawad
Error, Fault, Failure: Relation
43
43 COMSATS Institute of Information Technology, Attock Muhammad Fawad
Nine Causes of Software Errors
(Galin)
• Faulty requirements definition.
• Client-developer communication failures.
• Deliberate deviations from software requirements.
• Logical design errors.
• Coding errors.
• Non-compliance with documentation and coding
instructions.
• Shortcomings of the testing process.
• User interface and procedure errors.
• Documentation errors.
Phase % of defects
Requirements 56
Design 27
Code 7
Other 10