Customer Reviews

Software Quality Assurance: From Theory to Implementation

5 star:		(1)
4 star:		(2)
3 star:		(1)
2 star:		(1)
1 star:		(1)

 

 

Although written as a college text (the publisher also has instructor manual, syllabus and discussion guidelines, and test material), this book sufficiently reflects real world SQA to be used by working practitioners. My review focus is on the latter use.

Chapters that will be of interest to real world SQA include Chapter 3. Software Quality Factors (excellent foundation for a metrics initiative), Chapter 5. Contract Review (checklists for proposal and contract review are excellent), Chapters 7 (Integrating Quality Activities in the Project Life Cycle - especially the model for SQA defect removal effectiveness and cost) and 8 (Reviews, which includes supporting templates), and Chapter 11. Assuring The Quality of Software Maintenance, which is an often overlooked aspect of SQA.

Note that this book has been written to support ISO 9001 and contains chapters that are specifically slanted towards that approach. Included are chapters on document and configuration control, auditing, and attaining ISO 9001 certification. The author also provides solid information on ISO/IEC Quality Assurance standards, IEEE/ANSI Standards, and MIL-STD-498, as well as on common assessment approaches (CMM and SPICE).

As a textbook the coverage of every facet of SQA from why and what, to testing, metrics and its role in organizations and projects are thoroughly covered. The fact that the material is up-to-date and truly reflects the real world makes this one of the better texts for college level courses because it does prepare students for roles as practitioners.

Galin explains why software is usually far harder to test than hardware. The latter usually only has a few modes of operation, thousands at most. While the combinatorics of any nontrivial software package can easily produce millions of modes. Also, hardware defects (like parts missing) are often easy to detect by visual inspection. While software is often inherently opaque. It might have a corrupted or missing module that might not be found until the customer tries to use it. This is exacerbated by bugs being found essentially mostly in development and testing. And not in manufacturing. This latter step is trivial is software, but is the key step in hardware.

His book then goes over the main types of Software Quality Assurance models. These might already be familiar to you. The Waterfall model, which forms the basis of most SQA standards. But for small software projects, you might be able to use the Prototyping model, which can be faster. If you have a complex project, then maybe try the Spiral model. Here the spiral is a useful metaphor that indicates a hopeful convergence of the project at the centre of a Spiral chart.

Then there is the Object Oriented model. Which takes its inspiration from the rise of OO languages like C++ and Java. As you build up a library of classes, then the more useful this model becomes, at the project level.

Each of the above models is concisely explained. The entire book has this flavour. With a continual emphasis on metrics, as these are crucial to permitting an objective assessment of your project. In some ways, without taking sides as to which model you might adopt, the book seems to suggest that doing the metrics may be at least as important. So that you get some tangible idea of how your project is progressing.

It is also nice to see that he gives no mention of Extreme Programming. This is a dead end that was briefly popular amongst some developers, until its disadvantages became apparent.

The book is structured somewhat like a textbook, with questions at the end of each chapter. Certainly useful in focusing your attention. But its usage as an actual text in a university course seems unlikely. Not due to any failing in the book. But simply that computer science departments rarely teach this topic in any detail. Mostly left to industry.

i got no major issues with the content of the book, just another read on this topic. nothing special. my main source of disdain however, lies in the fact that amazon sent me what clearly looked like a heavily used book.
i dont like that.

I had to purchase this book for a class I was taking. Only read 6 chapters, which is what we were required to read, and I found the book to just be way too jam packed with information. Packed so much to the point where I found it troublesome to retain it all. It's just constant terms and knowledge and more terms, much of which isn't important, just being thrown at you in an unorganized way. I don't know, maybe it was just being overwhelmed with information that made it seem unorganized.

This book needs someone to go through it and take from it what students REALLY need to know, which I'm sure it's all there, and make a new book out of it. The book would probably be half the size of this book...

My review title represents well the impression I had reading this book. I read this book in a Software Engineering course context. It was complementary to our theory and examples.

While some chapters are really well built and organized with good templates, examples and metrics, some other are almost useless and explain obvious theory.

The book is hard to read because its boring most of the time and the text doesn't flow as well as its chapters. Also, examples and templates do not exist in every chapter and there is often a lack of explanations. Over 26 chapters, around 10 or 12 seem relevant for me because some are covered too much briefly to be useful. Or simply that there are better sources for the same topics in other books, for example software life cycle, software testing, configuration management and tools related.

I would recommend this book for someone who has no basis on SQA, as an introduction to it. It could be useful as a reference or either a reminder for guidelines and checklists when you are implementing a SQA process.

But if you already know strong basis, you won't learn a lot of things in that book.

Up front, this is one of the most dry and boring techical texts that I have ever read. Reading the book is as interesting as reading your insurance policy. I had (as part of a class that I was taking) to read the book cover to cover and can definitely say that this was a hard experience. The book uses very few examples and for the most part, they are useless. They do not carry a point nor explain any of the material they cover. The material is arranges in a confused way and does not flow from one chapter to another, nor does the structure of the chapters make any sense.
The reason I give this book 2 stars is that is does cover the various areas that SQA is concerned with. Going over the table of contents would give you enough information to look somewhere else for a better text.