on software quality - chapter 2
Post on 15-Apr-2017
225 Views
Preview:
TRANSCRIPT
Software Quality Assurance
Chapter II: Basics and Definitions
Christian Soltenborn
FG Database and Information Systems
SQA – 2011 University of Paderborn - Gregor Engels 2
Overview
What is software?
What is quality?
Views of quality
Why does the classical approach to QA not apply?
Basics and Definitions
SQA – 2011 University of Paderborn - Gregor Engels 3
Basic Terminology
Software is:
Computer programs, procedures, and possibly associated
documentation and data pertaining to the operation of a
computer system.
[IEEE_Std_610.12-1990]
What is Software?
SQA – 2011 University of Paderborn - Gregor Engels 4
IEEE
SQA – 2011 University of Paderborn - Gregor Engels 5
IEEE Standards Association
SQA – 2011 University of Paderborn - Gregor Engels 6
SQA – 2011 University of Paderborn - Gregor Engels 7
SQA – 2011 University of Paderborn - Gregor Engels 8
SQA – 2011 University of Paderborn - Gregor Engels 9
Software Quality - IEEE
Software quality is:
(1) The degree to which a system, component, or
process meets specified requirements.
(2) The degree to which a system, component, or
process meets customer or user needs or
expectations.
[IEEE_Std_610.12-1990]
SQA – 2011 University of Paderborn - Gregor Engels 10
Software Quality – More Definitions
Software quality is :
„The ability to satisfy stated or implied needs“ [ISO 8402]
„A product or service free of deficiencies“ [American Society for Quality]
„Conformance to explicitly stated functional and performance
requirements, explicitly documented development standards, and
implicit characteristics that are expected of all professionally
developed software.” [Roger Pressman]
„Fitness for use“ [Joseph M. Juran]
„Degree to which a set of inherent characteristics fulfills
requirements“ [ISO 9001]
SQA – 2011 University of Paderborn - Gregor Engels 11
SQA – 2011 University of Paderborn - Gregor Engels 14
Overview
What is software?
What is quality?
Views of quality
Why does the classical approach to QA not apply?
Basics and Definitions
SQA – 2011 University of Paderborn - Gregor Engels 15
Basic Terminology
The view of quality can differ upon:
The user
The context
The product alternatives
The stage of the lifecycle
[…]
What is quality of a product?
SQA – 2011 University of Paderborn - Gregor Engels 16
Different views of quality
Product view: the quality of a product is measurable in
an objective manner
User view: quality is fitness for use
Manufacturing view: quality is higher if product is
easier to produce
Value-based view (Economic): quality is a function of
costs and benefits
SQA – 2011 University of Paderborn - Gregor Engels 17
Overview
What is software?
What is quality?
Views of quality,
product quality,
…
Why does the classical approach to QA not apply?
Basics and Definitions
SQA – 2011 University of Paderborn - Gregor Engels 19
Why does the classical approach to QA not apply?
Requirements:
define complete set of external quality characteristics
complete set of internal quality characteristics and a detailed and complete set of requirements and specifications
Design:
design that satisfies the requirements and specifications
design for reliability (wear out)
design for manufacturability
design for maintainability (e.g., self-diagnosis)
Manufacturing:
statistical production process control with acceptance sampling
focal area of quality assurance!
Operation: collect failure data for continuous improvement and predictions
(intelligent maintenance)
Classical approach (from hardware design)
SQA – 2011 University of Paderborn - Gregor Engels 20
Why does the classical approach to QA not apply?
Invisibility of the product
Limited opportunities to detect defects (“bugs”)
Often new demanding functionality has to be realized
Often software has to realize extraordinary high
complexity
[D. Galin, Software Quality Assurance: From theory to implementation.
Harlow, England: Pearson Addison Wesley, 2004.]
What is special about software?
SQA – 2011 University of Paderborn - Gregor Engels 21
Why does the classical approach to QA not apply?
Requirements:
Completeness is hard to achieve (complexity, development process)
Design:
design for reliability only in special cases
design for manufacturability is not required
focal area of software quality assurance!
Manufacturing Implementation:
limited success with statistical process control (metrics)
Operation:
fixing bugs found
SQA – 2011 University of Paderborn - Gregor Engels 22
Quality Models
Old-fashioned methods for quality assurance don’t work
with software
The general definitions of software quality are not
sufficient in practice
Thus, a standardized quality model is needed!
Current Standard Quality Model:
ISO/IEC 9126-1: Software Engineering – Product Quality, Part 1:
Quality Model, 2001
SQA – 2011 University of Paderborn - Gregor Engels 23
Now: Quality Standards!
top related