IntroToTesting

IntroToTesting - Introduction to Software Quality Assurance...

Info iconThis preview shows pages 1–6. Sign up to view the full content.

View Full Document Right Arrow Icon
Introduction to Software Quality Sources: Code Complete, 2 nd Ed., Steve McConnell Software Engineering, 5 th Ed., Roger Pressman Testing Computer Software, 2 nd Ed., Cem Kaner, et. Al.
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Software Quality Assurance The purpose of SQA is to find and report defects AND succeed in getting them fixed What is a software defect? Defintion #1: There is a mismatch between the program and its requirements specification This definition is fine if a requirements specification exists and is complete and correct (not always true) Definition #2: The program does not do what its end user reasonably expects it to do This definition always applies, even when there's no specification
Background image of page 2
Software Quality Assurance Categories of Defects Functional defects The program’s features don’t work as they should User Interface defects Usability problems Performance defects Too slow, Uses too much memory/disk space/bandwidth/etc. Error Handling defects Failure to anticipate and handle possible errors, or deal with them in a reasonable way Security defects Attackers can compromise the system and access sensitive data or other resources
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Software Quality Assurance Categories of Defects Load defects Can't handle many concurrent users, can't handle large data sets Configuration defects Doesn't work on the required hardware/OS/browser configurations Race conditions Behavior depends on the interleaving of concurrent activities Documentation defects User manuals or online help isn't clear, complete, well-organized
Background image of page 4
Software Quality Assurance The longer defects remain in the system, the more expensive they become The cost of a defect grows dramatically the longer it remains in the system What is the cost of a defect in the requirements specification if it’s found found during requirements phase? during implementation?
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 6
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 03/02/2012 for the course C S 340 taught by Professor Woodfield,s during the Winter '08 term at BYU.

Page1 / 16

IntroToTesting - Introduction to Software Quality Assurance...

This preview shows document pages 1 - 6. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online