If you are responsible for designing, implementing, or managing a quality software program, this updated edition of the Practical Guide to Software Quality Management now identifies 10 major components that make up a solid program in line with ISO 9001 quality management precepts. Thoroughly revised and with new chapters on software safety and software risk management, this comprehensive primer provides you with the starting points for a standardized documentation system, and analyzes each individual program component separately, addressing in detail its specific role and overall importance to the system. This is the only volume to offer a broad overview of software quality management for non-experts and experts alike. It is written in clear, easy-to-understand language and contains a complete glossary that demystifies technical terms, abbreviations, and acronyms. Useful appendices contain example and "starting point" documentation outlines. Moreover, every chapter features an extensive list of authoritative references directing you to the latest technical details on a variety of software quality management issues.
Review By: Arvind Pal Singh 09/16/2005Judging by the title of the book, "A Practical Guide to Software Quality Management" gives the impression that it is about standard quality practices for a software project. However this detailed study gives much food for thought and action. The book's structure is based on the importance attached to each particular aspect of a software project, be it reviews, defect analysis, configuration management, or otherwise.
The subject of quality management is addressed by giving timely and appropriate examples. Although different organizations follow diverse terminology or approaches in the many phases of a software project, a reader can still learn how to work toward improving software quality, while performing different roles during a project. This book also emphasizes the importance of different people in various phases taking care of quality. The author also offers ways to improve it through best practices. I like the simple writing style, and appreciate Horch's’ eloquence. The examples offered in appendices make a great quick reference.
This multi-faceted book deals with avenues to improve software quality, and cannot be categorized solely under QA/Testing, for that is only a part of the complete software project. People who want to learn the inside processes of a software project, without getting into finer details, will find this book profitable.
The collection of different standards regarding the software lifecycle, documentation, naming, and user development is a great effort. Information offered by standards of IEEE, ISO, DoD, AS, ISO, NRC, and IEC are presented with outlines of the numerous types of documents involved. These offer a good deal of purpose in a software project from the viewpoint of quality management.
"A Practical Guide to Software Quality Management" deals with myriad aspects of a software project, so that a quality standard can be maintained. The book is an excellent primer for software project personnel. Systems analysts, quality managers, testers, and QA personnel will appreciate the way the author has made the contents useful, in an interesting, standards-oriented approach.