This book, on the TMAP process (for testing software) was written in
Dutch and translated, directly, into English. It's very difficult to
read and not worth the price. The TMAP process does not begin to
compare to the RUP process. (I say that even though I have written a
book on Software Quality Assurance "Best Practices" due for release
later this year, 2008). This book should have been edited by an expert
content editor. Had it been edited, it would have ended up being 240
pages long instead of its current 752 pages.
Here's an example of wasted, meaningless verbiage, right out of the
book: "The process of the acceptance and systems tests consists of a
number of different activities." Huh?!?
I believe that anything worthwhile in this book is not new but
taken from the IBM SDLC processes that go all the way back to the 60s
(when I worked for IBM). There's nothing new in the TMAP book, you can
find all the same information, in a better readability format!, in
William E. Perry's book, published in 1991, "A Standard for Testing
Application Software."
The fact that Rex Black wrote a foreword to the TMAP book only
reaffirms my opinion about Rex Black (egotistic, money-grubber, poor
writer of 'quality' books). The fact that Mr. Salvador, CEO of Sogeti
wrote a foreword, well, Sogeti OWNS TMAP now, so 'go figgur' who just
wanted to see his name in print. This book proves the value of the
1970s bumper sticker "QUESTION AUTHORITY." You might call this a
'vanity press' book, since it is Sogeti / Cap Gemini's 'sales
promotion' for their 'qa processes'.
There are many, much better SQA books out there. Take a look at the
lists provided by other SQA people on this site. My favorite SQA book
(aside from my own book) is "Quality Essentials" by Jack B. Revelle. It
is a 'cookbook' of sorts, a great reference material.
As for really learning SQA, hopefully you find your way into a
company that has at its SQA helm, a focused QA Process/test expert who
knows how to mentor and help you learn how to THINK and ANALYZE,
someone like ME, for example. There are a lot of good senior QA people,
now in leadership roles, who have an experientially acquired
understanding of SQA in all its phases and permutations. Be thankful if
you work for such a person! If you do not, google 'rational, RUP' and
learn the IBM RUP processes. They are solid.
댓글 영역