Software Quality Models and

Philosophies
 • Rida Sheikh
• Ramsha Bakht
Group members
• Rabia Noreen
• Rahab Anum
The purpose is to provide an overview to different quality models.
 What is quality?

• Conformance to specification
• Meeting customer needs
Quality Management Philosophies
 Quality according to Crosby

• Quality is defined as conformance to requirements not as

goodness or elegance.
• The performance standard must be Zero Defects. i.e. doing it right
the first time.
• The measurement of quality is the cost of quality. Investments
should be made in training and other supporting activities to
eliminate errors and recover the costs of waste.
Quality according to Deming
Customer satisfaction and the management processes.
1. Create constancy of purpose for improvement of product and service
2. Adopt the new philosophy
3. Cease dependence on mass inspection
4. End awarding business on price
5. Improve constantly and forever the system of production and service
6. Institute training
7. Institute leadership
8. Drive out fear
9. Break down barriers between departments
10. Eliminate slogans, exhortations and numerical targets
11. Eliminate numerical quotas or work standards
12. Remove barriers to taking pride in workmanship
13. Institute a vigorous programme of education
14. Take action to accomplish the transformation:
 Quality according to Feigenbaum

• Meeting customer needs

• Satisfying the customer in both actual and expected needs.
Quality according to Ishikawa
• Ishikawa’s perspective on quality is a “meeting customer needs”
definition as he strongly couples the level of quality to every changing
customer expectations.
• Quality is a dynamic concept as the needs, the requirements and the
expectations of a customer continuously change.
• Ishikawa also includes price as an attribute on quality
 Quality according to Juran

Juran defines quality as “Fitness for use”.

Juran trilogy elements are:
• Quality Planning
• Quality Control
• Quality Improvement
 Quality according to Shewhart

• Conformance to specification
• Meeting customer needs
Quality models
McCall’s Quality
Model (1977)

Three major perspectives for defining

and identifying the quality of a software
product:
• Product revision (includes
maintainability)
• Product transition (all about
portability)
• Product operations (all about
correctness of the system)
Boehm’s Quality Model
(1978)
• Boehm addresses the contemporary
shortcomings of models that
automatically and quantitatively evaluate
the quality of software.
• The model is structured around high level
characteristics and intermediate level
characteristics.
Characteristics of Boehm’s Model

High level characteristics Intermediate level characteristics

• As-is utility: How well (easily, reliably, • Portability
efficiently) can I use it as-is? • Reliability
• Maintainability: How easy is it to • Efficiency
understand, modify and retest?
• Usability
• Portability: Can I still use it if I change
my environment? • Testability
• Understandability
• Flexibility