Building Quality Into Software: A Guide to Manage Quality in Software Development and Use [Illustrated] [Paperback]

Horst P. Richter (Author)

Product Details

• Paperback: 260 pages
• Publisher: 1st Book Library; illustrated edition edition (July 20, 2000)
• Language: English
• ISBN-10: 1587210347
• ISBN-13: 978-1587210341
• Product Dimensions: 11.1 x 8.3 x 0.6 inches
• Shipping Weight: 1.5 pounds (View shipping rates and policies)
• Average Customer Review: 5.0 out of 5 stars  See all reviews (1 customer review)
• Amazon Best Sellers Rank: #2,572,538 in Books (See Top 100 in Books)

Customer Reviews

Most Helpful Customer Reviews

5.0 out of 5 stars Holistic view of SW quality from the project perspective, August 23, 2002

By 

Mike Tarrani "www.tarrani.com" (Deltona, FL USA) - See all my reviews
(COMMUNITY FORUM 04)    (REAL NAME)   

This review is from: Building Quality Into Software: A Guide to Manage Quality in Software Development and Use (Paperback)

This book captures the essence of SQA and shows how to not only integrate it into software development project management, but how to take a wide view by including the production and support milestone in the development life cycle.

For project managers the advice given on cost and risk management is invaluable. More importantly, the book shows project managers how to effectively integrate quality metrics into the project plan to measure more than cost and schedule attainment.

Software quality practitioners will gain a project-oriented view of SQA, which encompasses not only quality metrics, but qualification and certification criteria for the software being delivered. This aspect of the book is also invaluable to the testing team, which has a different role than the SQA function.

Developers and development managers will gain an understanding of requirements traceability and, as importantly, security considerations, that need to be incorporated into the build phase of the life cycle.

Overall, this book is invaluable because it portrays the quality function as a team effort, and this theme is interwoven throughout the book. The author does an excellent job of tying together the viewpoints of the disparate team functions in a development project into a single focus on attaining quality as a team objective. I found the illustrations, tables and checklists especially valuable, and the holistic approach given in this book to be a refreshing change from similar books that focus on a much narrower view (i.e., development, architecture, QA, etc.).

I strongly recommend that this easy-to-read book be used as a key reference by all members of large project teams before initiating complex projects. It will literally have everyone reading from the same page and will show all stakeholders how to bring about quality within their unique domains and as members of a much larger team.