Software RX: Secrets of Engineering Quality Software [Paperback]

Rodney C. Wilson (Author)

Book Description

Publication Date: November 2, 1996 | ISBN-10: 0134726634 | ISBN-13: 978-0134726632 | Edition: 1

In one neat package, this book brings together information on every aspect of developing quality software.Introduces a phased approach for delivering software quality. Presents the role of reviews and design specifications in optimizing quality. Discusses best quality practices for object-oriented development. Discusses prototypes and acceptance testing. Includes a detailed checklist of best practices.For software engineers, software project managers, designers, and technical software marketing managers.

Editorial Reviews

From the Publisher

Learn to achieve high customer satisfaction through a blend of the best technology and the best communication. In one neat package, this book brings together the best information on every aspect of developing quality software. Software Rx introduces a practical, phased approach for delivering software quality. Walk step-by-step through the entire process of improving software quality within a development organization. Understand the role of reviews and design specifications in optimizing quality. Learn best quality practices designed specifically for object-oriented development environments. Make sure prototyping and acceptance-testing practices deliver the feedback necessary to improve both current and future products. Software Rx's detailed checklist of best practices alone is worth the price of the book. This is the complete, practical quality guide for anyone responsible for producing world-class software.

From the Back Cover

In one neat package, this book brings together information on every aspect of developing quality software.Introduces a phased approach for delivering software quality. Presents the role of reviews and design specifications in optimizing quality. Discusses best quality practices for object-oriented development. Discusses prototypes and acceptance testing. Includes a detailed checklist of best practices.For software engineers, software project managers, designers, and technical software marketing managers.

Product Details

• Paperback: 192 pages
• Publisher: Prentice Hall; 1 edition (November 2, 1996)
• Language: English
• ISBN-10: 0134726634
• ISBN-13: 978-0134726632
• Product Dimensions: 9.3 x 7 x 0.6 inches
• Shipping Weight: 11.2 ounces (View shipping rates and policies)
• Average Customer Review: 1.0 out of 5 stars  See all reviews (1 customer review)
• Amazon Best Sellers Rank: #4,211,617 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

1 of 1 people found the following review helpful:

1.0 out of 5 stars Need to know about the software QA process? Look elswhere, September 18, 2002

By 

Richard C. Davis (Littleton, MA USA) - See all my reviews
(REAL NAME)   

This review is from: Software RX: Secrets of Engineering Quality Software (Paperback)

This is one of the worst technical book I have ever read, or I should say, ever made an attempt to read. While it may contain pertinent information about the software development/QA process, the author's writing style safely obscures it. His officious pronouncements about what constitutes good or bad practices, without supporting information in the near vicinity, is maddening. His odd style of writing construction, where practically every third sentence is followed by a parenthetical phrase that (presumably) is supposed to augment the preceding text, but in many cases either states something so obvious as to be insulting to the reader, or actually contradicts earlier definitions, makes reading it a real chore. This book appears to have somehow escaped the editorial review process and gone right to print.
The overall software development process as envisioned by the author, apparently takes place in some techno-bureaucratic fantasy land, where QA engineers, developers and tech writers are somehow interchangeable and should routinely "rotate jobs" to develop some empathy for the other fellow's position.
If you must read this book, read the conclusions at the end of each chapter, where space constraints dictate a refreshing brevity, and do read the appendices, which are really quite good. Finally, try to ignore the "marketingese" slogans "Best-Practices" and "Best-in-Breed", which of course convey no useful information, but seem to be used everywhere.