<< 1 >>
Rating: 
Summary: Aging gracefully with lots of life left - not for SW testing
Review: This book represents a pivot point in Perry's prolific published works that date from 1981. What makes it pivotal is the fact that this book synthesizes his approach to IS quality assurance from a production support viewpoint and his future work which focuses on software testing.Although over 11 years old the QA approach contained in this book is still valid. To get at the gems, though, you have to overlook a few things. For example, terminology common in the mainframe data center of past decades sounds quaint even to those of us who came from that environment. Also, the code examples used to illustrate quality problems are sure to confuse the younger generation of C++ and Java developers and test professionals who probably never heard of PL/I and only vaguely know about FORTRAN. What I like about this book and the reason why I think it's still an important reference is the fact that application quality from an enterprise perspective is addressed. This goes beyond testing and release processes, as well as beyond project issues surrounding applications delivery and SQA. The focus is on production and maintenance, although testing, SQA and project metrics are addressed. In addition to the focus, the book contains checklists, questionnaires and sample forms that can be updated to reflect modern computing environments - and you may be surprised to find that much of this 'ancient' material requires very little modification. Another aspect of this book that I like is the material on software maintenance, which seems to be a lost art, although it's as important now as it ever was. Don't let the age of this book deter you if you're interested in quality assurance from a production support point of view. If you are seeking a book on software testing this will not be useful (I recommend Systematic Software Testing by Rick D. Craig and Stefan P. Jaskiel for that) or SQA metrics (any of Robert B. Grady's books are great starting places). The best recommendation I can give is that this book has served me well in over a decade of consulting, and it probably will for years to come. However, it shouldn't be your only reference either.
Rating:
Summary: Aging gracefully with lots of life left - not for SW testing
Review: This book represents a pivot point in Perry's prolific published works that date from 1981. What makes it pivotal is the fact that this book synthesizes his approach to IS quality assurance from a production support viewpoint and his future work which focuses on software testing. Although over 11 years old the QA approach contained in this book is still valid. To get at the gems, though, you have to overlook a few things. For example, terminology common in the mainframe data center of past decades sounds quaint even to those of us who came from that environment. Also, the code examples used to illustrate quality problems are sure to confuse the younger generation of C++ and Java developers and test professionals who probably never heard of PL/I and only vaguely know about FORTRAN. What I like about this book and the reason why I think it's still an important reference is the fact that application quality from an enterprise perspective is addressed. This goes beyond testing and release processes, as well as beyond project issues surrounding applications delivery and SQA. The focus is on production and maintenance, although testing, SQA and project metrics are addressed. In addition to the focus, the book contains checklists, questionnaires and sample forms that can be updated to reflect modern computing environments - and you may be surprised to find that much of this 'ancient' material requires very little modification. Another aspect of this book that I like is the material on software maintenance, which seems to be a lost art, although it's as important now as it ever was. Don't let the age of this book deter you if you're interested in quality assurance from a production support point of view. If you are seeking a book on software testing this will not be useful (I recommend Systematic Software Testing by Rick D. Craig and Stefan P. Jaskiel for that) or SQA metrics (any of Robert B. Grady's books are great starting places). The best recommendation I can give is that this book has served me well in over a decade of consulting, and it probably will for years to come. However, it shouldn't be your only reference either.
Rating: 
Summary: Good for starting a new quality assurance department
Review: This book would be very useful for those implementing QA groups in their companies. The book displays a deep understanding of the issues involved in that. The sample QA plan, manual, and its forms and charts can be very useful. Unfortunately, some of the material, such as the checklists, is pretty dated. The book takes a fairly scientific approach to QA, and that may appeal to some, but not others. The book doesn't follow the IS0 9000-3 model, per se. Finally, the book assumes the reader works in an internal corporate IT department rather than one which serves outside clients. The book is still very useful, nonetheless.
Rating:
Summary: Good for starting a new quality assurance department
Review: This book would be very useful for those implementing QA groups in their companies. The book displays a deep understanding of the issues involved in that. The sample QA plan, manual, and its forms and charts can be very useful. Unfortunately, some of the material, such as the checklists, is pretty dated. The book takes a fairly scientific approach to QA, and that may appeal to some, but not others. The book doesn't follow the IS0 9000-3 model, per se. Finally, the book assumes the reader works in an internal corporate IT department rather than one which serves outside clients. The book is still very useful, nonetheless.
<< 1 >>
| 
