The approach

Software Quality Models Structures

Of Quality

What is Quality?

Drazen Milicic Quality

Attributes
Software Quality Models

Gurus

What is quality? What do the gurus say?

„ ISO 9000 – Quality management system
… 1994: The totality of characteristics of an entity that bear on its „ Two dominant overall „ Joseph M. Juran
ability to satisfy stated and implied needs. views on software „ Walter A. Shewhart
… 2000: degree to which a set of inherent characteristics (i.e. quality: „ Philip B. Crosby
distinguishing feature) fulfils requirements (i.e. need or 1. Conformance and degree
expectation that is stated, generally implied or obligatory) of satisfaction to an in „ W. Edwards Deming
„ IEEE STD beforehand defined „ Armand V. Feigenbaum
specification.
… 1061:1993 (Software quality metrics methodology) - The degree 2. The products or services „ Kaoru Ishikawa
to which software possesses a desired combination of attributes. capability to meet
… 610.12:1990 (Glossary of Software Engineering Terminology) customer expectations –
The degree to which a system, component, or process meets explicitly stated or not
specified requirements.

Philip B. Crosby I W. Edwards Deming II

„ Quality is a subjectively identified differently by
each individual and institution.
„ As this is not useful in software engineering
quality must be defined as “conformance to
requirements”
„ Nonconformance to requirements is the absence
of quality, quality problems become
nonconformance problems, and quality becomes
definable
„ Translating future needs of the user into
measurable characteristics
„ Constantly changing based on “real world”
- competitors, solutions, technology, price
„ Quality can be defined only in terms of the
agent.

1
Armand V. Feigenbaum II Kaoru Ishikawa II
„ Quality is based upon the customer’s actual „ Quality defined according to standards (ISO,
experience with the product or service, IEEE etc.) contain shortcomings, does not reflect
constantly changing customer needs
measured against his or her requirements
„ Narrowly interpreted, quality means quality of
… stated or unstated products.
… conscious or merely sensed „ Broadly interpreted, quality means quality of
… technically operational product, service, information, processes, people,
… entirely subjective
systems etc. etc.
… always representing a moving target
„ Quality must be defined comprehensively and
dynamically.

Joseph M. Juran I Walter A. Shewhart II

„ Quality can be: „ Quality from two perspectives:
… Those product features which meet the need of … An objective reality independent of the
customers and thereby provide product satisfaction.
existence of the customer
… Freedom from deficiencies.
… The subjective perspective dependent on
„ Quality in terms of satisfying customer
individual thoughts, feelings or senses as a
expectations or specifications is not usable as it
result of the objective reality.
is very hard to achieve.
„ Quality is fitness for use

Gurus vs. Models Software Quality Models

„ How well does the models actually meet
the definition of quality as described by the
gurus?

2
McCall’s Quality Model McCall’s Quality Model

Boehm’s Quality Model McCall vs. Boehm

FURPS(+) / Robert Grady Dromey's Quality Model

„ Functionality – which may include feature sets, capabilities and security
„ Usability - which may include human factors, aesthetics, consistency in the
user interface, online and context-sensitive help, wizards and agents, user
documentation, and training materials
„ Reliability - which may include frequency and severity of failure,
recoverability, predictability, accuracy, and mean time between failure
(MTBF)
„ Performance - imposes conditions on functional requirements such as
speed, efficiency, availability, accuracy, throughput, response time,
recovery time, and resource usage
„ Supportability - which may include testability, extensibility, adaptability,
maintainability, compatibility, configurability, serviceability, installability,
localizability (internationalization)
„ + - Design constraints, implementation requirements, interface requirements
and physical requirements.

3
ISO 9000:2000 ISO 9126
„ Quality management ISO 9126: Software
principles: Product Evaluation:
… Customer focus Quality
… Leadership Characteristics and
… Involvement of people Guidelines for their
… Process approach Use
… System approach to
management
… Continual improvement
… Factual approach to
discussion making
… Mutually beneficial
supplier relationships

ISO 9126 CMM

ISO 9126: Software
Product Evaluation:
Quality
Characteristics and
Guidelines for their
Use

CMM P-CMM
Level Focus Key Process Area
Process Change Management
Level 5 – Optimizing
Continuous improvement Technology Change Management
level
Defect Prevention
Level 4 – Managed Software Quality Management
Product and process quality
level Quantitative Process Management
Organization Process Focus
Organization Process Definition
Peer Reviews
Level 3 – Defined level Engineering process Training Program
Intergroup Coordination
Software Product Engineering
Integrated Software Management
Requirements Management
Software Project Planning
Level 2 – Repeatable Software Project Tracking and Oversight
Project management
level Software Subcontract Management
Software Quality Assurance
Software Configuration Management
Level 1 – Initial level Heroes No KPAs at this time

4
CMMI
Excellence models
„ Common excellence models:
… Malcolm Baldrige National Quality Award
… European Quality Award
… Utmärkelsen Svensk Kvalitet
„ The excellence models contain criteria (within
leadership, process and technology) that enable
comparative evaluation of organizational performance.
„ Assessment criteria in excellence models provide a
basis for an organization to compare its performance
with the performance of other organizations.
CMMI
Quality - Gurus vs. Models
„ How well does the models actually meet the
definition of quality as described by the gurus?
„ From: According to specification.
„ To: Customer satisfaction.
„ Q = Deliverables / Expectations
„ Quality models focus on control of deliverables