lec 1 - overview of stqa

7/31/2019 Lec 1 - Overview of STQA

1/18

Software Testing and QualityAssurance

Lecture 1: Overview of SoftwareTesting and Quality Assurance

Produced by VTT on Dec 14th 2011


2/18

Overview 2

Outline

Course program and materials Workstation for students

Goals of the course

Testing vs. Quality Assurance (QA) Why a software has bugs?

History evolution of software testing (ST)

vs. career perspectives Cost of failure vs. defect correction cost


3/18

Overview 3

Course program

At university: Lectures: 19 hours

Practices: 26 hours (require attending 100%)

At home: 60 hours for reading materialsbefore class is taken

Examination: 4-9 hours Theory test: 20-40 seconds (15%)

Practice test: 3-7 hours


4/18

Overview 4

Materials for ref.

Dorothy Graham, Erik van Veenendaal, Isabel Evans and Rex Black,Foundations of Software Testing: ISTQB Certification: 2nd Edition,Cengage Learning EMEA, 2008

Gerald D. Everett and Jr. Raymond McLeod, Software Testing: Testingacross the Entire Software Development Life Cycle, Wiley-Intnerscience,A John Wiley & Sons, Inc., Publication, 2007

Glenford J. Myers, The Art of Software Testing: 2nd Edition, John Wiley& Sons, Inc., Publication, 2004

Ieff Tian, Software Quality Enginnering: Testing, Quality Assurance, andQuatifiable Improvement, Wiley-Intnerscience, A John Wiley & Sons, Inc.,

Publication, 2005 Nick Jenkins, A Software Testing Primer: An Introduction to Software

Testing, 2008


5/18

Overview 5

Additional materials

L Bnh Cng, Kim Th V Bo m Cht Lng Phn Mm, HBch Khoa, 202p, 2011

L Th Thu Hng and Nguyn Th Thu Hin, Kim Th Phn Mm, HS Phm K Thut Hng Yn, 128p, 2010

L Bnh Cng, Kim Th V Bo m Cht Lng Ph

n Mm, HBch Khoa, 202p, 2011

L Th Thu Hng and Nguyn Th Thu Hin, Kim Th Phn Mm, HS Phm K Thut Hng Yn, 128p, 2010

Websites: http://www.vietnamesetestingboard.org
http://www.vietnamesetestingboard.org/http://www.vietnamesetestingboard.org/


6/18

Overview 6

Workstation for students


7/18

Overview 7

Workstation for students (cont)

Download

http://travt/bmt/SE312/Materials

http://travt/bmt/SE312/Lectures

Upload

http://travt/bmt/SE312/DropOffLibrary

http://travt/bmt/SE312/Proposals
http://travt/bmt/SE312/Materialshttp://travt/bmt/SE312/Lectureshttp://travt/bmt/SE312/DropOffLibraryhttp://travt/bmt/SE312/Proposalshttp://travt/bmt/SE312/Proposalshttp://travt/bmt/SE312/DropOffLibraryhttp://travt/bmt/SE312/Lectureshttp://travt/bmt/SE312/Materials


8/18

Overview 8

Workstation for students (cont)

Take tests

http://travt/bmt/SE312/Quick Test

Access info: User: se312sv

Pass: bmtSE312
http://travt/bmt/SE312/Quick%20testhttp://travt/bmt/SE312/Quick%20test


9/18

Overview 9

Goals of this course

Provide knowledge and skills for thosewho want to do:

software testing software quality assurance


10/18

Overview 10

Quality Assurance

Testing vs. Quality Assurance

Testing

Scope & Content


11/18

Overview 11

Software Testing and Quality Assurance is notjust finding software bugs, but also the process

of checking andverifyinga software which hasmet bothrequirementsandexpectationsofcustomers for products, helps reduce adjustment

costs and development time

Definition


12/18

Overview 12

Why software has bugs?

Software complexity

Programming errors

Changing requirements Time pressures

Poorly documented code

Software development tools


13/18

Overview 13

Historical evolution of ST

1950s-1960s: no formal development ortesting processes

1960s-1970s: many corrections & refinements

yield very stable & reliable software Customers began to expect software to be highly reliable &

stable over extended periods of time

Developers began to examine the development processes

1970s-1980s: successful in capturing the bestdevelopment practices


14/18

Overview 14

Historical evolution of ST

1990s: testing became recognized Reichheld Jr. & Sasser, 1990: quality control

shifting from zero defect in products to zerodefection of customers

Y2K: software testing activities has beenconsidered as the savior of the 21st century

Billions of dollars were spent mitigating thepossible business disasters caused bysoftware development activities.


15/18

Overview 15

Perspective of software testing

2001: software failures cost of USeconomy ~ $59.5B/ year.

$22.2B of annual losses could be eliminated by

software testing

Testing activities: ~ 30-50% time ofdeveloping software

Career opportunities


16/18

Overview 16

Cost of Failure

Example: Ford Pinto,1971, an error of gas tankwhich causes an explosion when Pinto is rear-ended in a collision

Ford assigned $25,000 to human life lost in a car fire.

Estimated ~$2.20/car from faulty gas tank litigation Ford calculated the cost of retrofitting every Pinto with a

gas tank bracket to be $8.59-11.59/car

the best ROI decision: refrain from retrofitting and payall faulty gas tank lawsuits

Wrongly death lawsuit settlements cost Ford a loss of $5M-10M

An incensed jury hits Ford with a $128M settlement


17/18


18/18

Overview 18

Next lecture ?

lec 1 - overview of stqa

Documents