Software System Testing and Quality Assurance (Van Nostrand Reinhold Electrical/computer Science and Engineering Series) [Hardcover]

Boris Beizer (Author)

Product Details

• Hardcover: 358 pages
• Publisher: Van Nostrand Reinhold (March 1984)
• Language: English
• ISBN-10: 1850328218
• ISBN-13: 978-1850328216
• Product Dimensions: 9.5 x 6.5 x 1.2 inches
• Shipping Weight: 1.5 pounds
• Average Customer Review: 5.0 out of 5 stars  See all reviews (2 customer reviews)
• Amazon Best Sellers Rank: #2,823,658 in Books (See Top 100 in Books)

More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

Most Helpful Customer Reviews

14 of 15 people found the following review helpful:

5.0 out of 5 stars This is a bible for software system testing, April 20, 1998

By 

[e-mail] (Taiwan) - See all my reviews

This review is from: Software System Testing and Quality Assurance (Van Nostrand Reinhold Electrical/computer Science and Engineering Series) (Hardcover)

I've read this book to build up my software testing knowledge base while I was working for Logitech,CA. Though these're many new tools and papers coming in these years , I 'll still love to recommend this book as an entry book in this field(even this book is out of print).

3 of 3 people found the following review helpful:

5.0 out of 5 stars A developer's best friend, June 14, 2002

By 

M. Woolsey (Fairfax, VA United States) - See all my reviews
(REAL NAME)   

This review is from: Software System Testing and Quality Assurance (Van Nostrand Reinhold Electrical/computer Science and Engineering Series) (Hardcover)

I bought this book almost 20 years ago with some skepticism. The title made it sound like it was another book for Dilbert's boss.

But this is a great book. It offers readable insights into why tests are performed, and what tests are appropriate at major phases in a software product. And it doesn't oversell the developer's ability -- **nor the tester's**. A little excerpt to illustrate the balance this book strikes:

"If the programmer just produces a working routine without prood and documentation and all but the primary goals are ignored, its quality cannot be measured and management is impossible. Conversely, if the subsidiary and auxiliary goals dominate, management and quality assurance may seem satisfied, but there's little or no working code to evaluate and manage! You can't burden programmers with filling out thousands of forms -- you can try, but it won't work."