[.ca] Effective Methods for Software Testing, 2nd Edition (ISBN 047135418X)

From Amazon.com:
Aimed at the working test manager or test engineer, the second edition of William Perry's Effective Methods for Software Testing is one of the most rigorous guides to software testing available. This book provides the latest in standards for measuring how good your organization's commitment to software testing is and many ways to improve it. In all, with its numerous lists and practical step-by-step guide to testing, this book points the way toward more economical and effective software testing. This book's major strength is its meticulous 11-step guide to all aspects of today's software testing process--from initial analysis and test planning to testing software installation and looking at ways to improve the testing cycle the next time around. The book is filled with to-do lists that enumerate the resources and tasks required for each step with helpful hints for what to do, how to work with management, and how to staff and execute a test plan from start to finish. (There is a chapter devoted to each of the 11 steps.) The text also incorporates the latest in testing standards from the Quality Assurance Institute (QAI), and the author does a good job of integrating testing with today's iterative software methodologies. Another standout here is a look at software tools and how they can simplify the testing process. Of course, few software shops will be as rigorous in real life with the testing process outlined in this book, but there's little doubt that this exhaustive guide sets a high standard that test engineers can aim for. Written in a somewhat formal--yet clear--style, this book can certainly benefit any software testing engineer or manager. --Richard Dragan Topics covered: Software testing process fundamentals, Quality Assurance Institute (QAI) test quality assessment, software defects, Kiviatt charts, testing economics, methodologies and costs, test plans, risk analysis, structural and functional testing, dynamic and static testing, manual and automated testing, testing tools, stress testing, compliance testing, security testing, requirements testing, regression testing, 11-step software testing process, testing client/server, and Web-based systems.

Move Away from this Page:
The book is full of hypothesis. Till now nobody would have implemented all the checklists/templates/procedures mentioned in this book, in their real environment and I can bet on this. Checklists are needed if the task of review/testing is very critical and the organizational processes shall demand that. An attempt to define a checklist/template to make it global is real childishness. The definition of Verification and Validation itself is written wrong in this book. I dont know if these terms had such definitions during the past years. Summary: We are in 2003 now. If somebody wants to go back to 1970 then this book will be very useful for them. A wise decision for normal readers would be to move away from this page. Thanks.

not all that:
i find the book too advance to understand

a great book for the software organization trying to improve:
This is a very good book, despite what the other reviewers say. It is aimed at the professional software developer, consistent with good software engineering practices. Unfortunately, those who still work ad hoc in software development do not understand the value of formal processes and the resulting reduction of risk or increase in quality. This book assume that readers, and their organizations, have the required discipline to formalize their testing methods. One of the key principles in the book is that requirements must be validated and traced throughout the software life cycle - garbage in garbage out. Consider whether or not you would like to fly in a plane or have your bank account managed by software that has not been as rigorously tested as the author requires it to be.

Great Book:
I find the book extremely useful from the perspective of one who has had to test software and audit systems development. Though the book may appear pedantic to some, application of its principles can say companies mega bucks!

Fails the readability tests:
There are a few things to say in favour of this book: 1. It does walk through on how to approach testing in your organization (however, it is definitely oriented towards organizations with established testing principles). 2. It does give you some background information on software testing. Sadly, these are mainly explained in a textbook like manner, making them hard to digest. 3. It provides a thorough, detailed and tested methodology for software testing throughout the various life cycles. Yet again, due to the book's textbook like manners, I found it hard to actually implement the offered methodologies. Whatever positive attributes the book has to offer, they pale in comparison to the book's negative aspects: 1. Total unreadability: The book written in such a boring manner, you will find yourself reading every page thrice, and still lack the satisfaction of being able to quote the meaning of what you just read. 2. Lack structure: Paragraphs are thrown in one after the other; it's hard to decipher what leads where. 3. Repetitiveness: Items like "building the test plan" repeat themselves for no particular reason. 4. No examples: It's hard for the text to find any foundation in your mind when there are no examples to help the reader relate to. Given its monotonous descriptions, nothing could hinder the reader's efforts to understand and implement the book's ideas more than that. The final verdict: Look for another software testing book.