Professional Documents
Culture Documents
and
Software Quality
Assurance
(an overview)
Learning Outcomes
Introduction
Teacher
Class
Subject
Name
Course outline
Books
Project
Assignments
Quality - Definitions
Definition- IEEE
Kinds of Quality
Quality of Design
Quality of Conformance
Quality Challenges
Requirements
Design
Source code
User manuals/training material
Bad fixes or mistakes made during repairs
Flawed test cases used by the application
10
11
Present
Quality
is
the
responsibility
of
blue
collar workers and direct
labor employees working
on the product
Quality defects should
be hidden from the
customers
and
management
Quality problem lead to
blame,
faulty
justifications and excuses
Quality
is
everyone's
responsibility,
including
white-collar workers, the
indirect labor force and the
over head staf
Defects
should
be
highlighted and brought to
the surface for corrective
action
Quality problems lead to
co-operative solutions
12
continued
Past
Corrections-to-quality
problems
should
be
accompanied
with
minimum
documentation
Increased
quality
will
increase project costs
Quality
is
internally
focused
Quality will not occur
without close supervision
of people
Quality
occurs
during
project execution
Present
Documentation
is
essential
for
lessons
learnt so that mistakes
are not repeated
Improved quality saves
money
and
increases
business
Quality is customer focused
People want to produce
quality products
Quality
occurs
at
project
initiation and must be planned
for within the project
13
14
Software Quality
in
Business Context
15
Quality Control
16
Quality Assurance
17
QA
Correction
(Reactive)
Preventive
(Proactive)
Product
Process
Confidence to
Producer
Confidence to
Customer
Line Function
Staf Function
Find Defects
Prevent Defects
18
QA
Walkthrough
Defining Processes
Testing
Quality Audit
Inspection
Selection of Tools
Checkpoint review
Training
19
SQA Function
20
References
Chapter 1
1.1, 1.2
1.3 (1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.3.6)
1.4, 1.5
1.7 (1.7.1, 1.7.2, 1.7.3, 1.7.4, 1.7.5)
21