Académique Documents
Professionnel Documents
Culture Documents
Testin
g
Chapter 1
Objectives
End Goals
Coverage
Overview of Topics
Introduction
The Software Crisis
16%
53%
31%
Successful
Cancelled
Challenged
(Delayed/Exceed
Budget)
Introduction
The Software Crisis
60%
50%
53%
46%
40%
53%
44%
40%
30% 31%
20%
49%
51%
34%
33%
27%
28%
26%
29%
28%
23%
16%
32%
24%
15%
Succeeded
Failed
Challenged
18%
10%
0%
1994
1996
1998
2000
2002
2004
2009
*Standish Chaos Report listed
by year
One solution
A Comprehensive Testing Approach
22.2B can be
saved by applying
a comprehensive
testing approach
$$
$
Practical
Technical
Creative
Critical
ACTIVITY
The Kings Challenge
TEST
DRIVE
Validate affordability
Validate attractiveness
Validate usefulness
Break the car?
Improve the cars
design?
Validate comfort
Validate performance
TRY Performance
Testing
Work different
features of the car by
actually driving the car
EXAMINE Static
Testing
Observe, read, review
without actually
driving the car
BASIS = Requirements
Document
Performance Testing
work different
features of the car in
the prototypes
Functional and
Structural Testing
work different features
of the car models, mockups, and manufactured
subassemblies
What if you cant test it all? What if you run out of time?
Prioritize the outstanding defects, and prioritize features that
are most important
Review test results and determine clusters or trends to allocate
resources better
Development Axiom
Testing is not abrakadabra for quality
Return on Investment
Benefit from the Investment
Revenue or profit
Cost associated with testing, testing basically reduces the total
profit of the final product
Customers
Loss of customers due to poor quality
Litigation
An unhappy customer can do a company as much financial
damage as an injured customer
The Myth
Quality can be tested into a software product at the end of the
development cycle
NOTE: Quality in this context means software that exhibits zero
defects when used by the customer
Lessons
You cant take too many shortcuts when developing software
You will pay for testing now or later, but the cost of testing is
unavoidable. Testing now is always less expensive than testing
later.
1950 1960
reactive
debugging
many
corrections and
refinements to
software
1960 - 1970
Captain Grace
Murray Hopper
found first
bug
1970 - 1980
captured best
software
development
practices,
repeatable level of
software reliability
The Y2K
Sword of
Damocles
1990 ->
Skill classifications
Entry level skills
Intermediate level skills
Advanced skills
Skill classifications
Entry level skills
Intermediate level skills
Advanced skills
Testin
Overview of
END
Module Updates
Document Version Details
Versio
n
Date Updated
1.0
7/30/2011
Changes/Details
Created document
Author
Engr. K. Fajardo
This document must not be used for other purposes outside the USC
Department of Computer Engineering without permission.