Solid Software (Paperback)

~ (Author)
Key Phrases: software metrics, predicting effort, automated testing tools, New York, Upper Saddle River, Prentice Hall (more...)

Editorial Reviews

Product Description

For courses in Software Reliability, Software Testing and Verification, Software Requirements, Software Metrics, and Software Engineering--Advanced Solid Software presents realistic techniques for analyzing and improving the quality and robustness of any software system or software-intensive product. Solid Software isn't theoretical: it's a relentlessly practical decision maker's guide to making intelligent, responsible trade-offs that lead to the best software at the best cost. Solid Software draws upon dozens of real-world examples, based on the author's extensive experience as software quality consultants, and interviews with key software decision makers worldwide. Whether you're a developer, project manager, architect, executive, manager, or regulator, it's your single source for improving software quality in the real world.

From the Back Cover

The practical guide to evaluating and improving the quality of mission-critical software.

Large software systems will never be perfect, but decision makers need better ways to evaluate and enhance software quality—especially where software is mission critical or used in life-or-death environments. Solid Software presents realistic techniques for analyzing and improving the quality and robustness of any software system or software-intensive product.

Solid Software isn't theoretical: it's a relentlessly practical decision maker's guide to making intelligent, responsible trade-offs that lead to the best software at the best cost.

* Understand what levels of quality are reasonable to expect at every stage of the software life cycle, including development, deployment, and maintenance
* Discover the key "design leverage points" that lead to robust software
* Learn sophisticated new ways to predict software quality and assess systems in production
* Make the most of hazard analysis, testing, design analysis, reviews, static code analysis, and other techniques
* Choose the best tools—and use them more effectively

Solid Software draws upon dozens of real-world examples, based on the authors' extensive experience as software quality consultants, and interviews with key software decision makers worldwide. Whether you're a developer, project manager, architect, executive, manager, or regulator, it's your single source for improving software quality—in the real world.

See all Editorial Reviews

Product Details

• Paperback: 340 pages
• Publisher: Prentice Hall (July 2, 2001)
• Language: English
• ISBN-10: 0130912980
• ISBN-13: 978-0130912985
• Product Dimensions: 9.1 x 6.8 x 0.8 inches
• Shipping Weight: 1.2 pounds (View shipping rates and policies)
• Average Customer Review: 4.0 out of 5 stars  See all reviews (1 customer review)
• Amazon.com Sales Rank: #1,357,976 in Books (See Bestsellers in Books)

  Popular in this category: (What's this?)

  #57 in

  Books > Computers & Internet > Programming > Software Design, Testing & Engineering > Quality Control

Customer Reviews

Most Helpful Customer Reviews

7 of 7 people found the following review helpful:

4.0 out of 5 stars Solid Software, mushy in the middle, January 14, 2002

By	R. Dameron "been-there" (Longmont, CO United States) - See all my reviews (REAL NAME)

I teach software engineering at the University of Colorado. I have begun a 3 course graduate series and am using Solid Software as one of two texts in the first course, Software Engineering of Stand Alone Programs. (Subsequent courses cover multiprogramming and distributed systems.) I have found Solid Software to cover the right topics but not to the right level of detail for my purposes. It is hard to find a general book on software engineering that covers adequately enough development factors that contribute to robustness such as requirements and design reviews, static and dynamic testing, etc. I was pleased when I read through the table of contents and saw the 9 areas addressed by the book. However, it is written to, say, first level managers of programming teams, not to the programmers themselves. On many topics, there are excerpts from books or papers that give a high level "hit". The good news is that the reference list at the end of each chapter includes excellent references. I think it's fair to say that my students' (all with industry experience) reaction is that it's not quite detailed enough to really understand. They are not expecting a how-to guide but ... more than this level. But you *can* follow the reference trail to get to more substance. If you ARE a 1st level manager, wondering what more can be done, what is reasonable to ask for, then this may be a great book for you.