Metrics are only useful if they
answer a question. I have tried to put all the basic questions in and give you worked examples to
show how to get the answers. I??™ve put in the equations to show the basis, but where things have
got complex I have put some of the equations in Excel spreadsheet format.
??? Appendix A contains
examples
of reports and plans as well as case studies.
??? Appendix B contains
checklists
with questions you need answers to in more detail. Although this
book is not concerned with reviews, inspections, or audits, these may prove useful in either.
??? Appendix C contains approaches to
categorizing bugs
.
??? Appendix D lists
tools
.
???
References
, a
glossary
, and the
index
are located at the back of the book.
Managing testing is like managing a battle. Part of the time you need to fight the battle and part of the
time you need to be above the battle, thinking. Thinking above the battle requires that you ask questions.
If you don??™t ask the right questions, you will never get the answers. The answers must help you and the
test team
do
something. At the back of my head I hear the voice of an awkward Highland-Scottish project
manager asking, ???
Aye, but what does it buy me?
???
It??™s a good question and this is an answer.
Assumptions
This book has been written with a number of assumptions:
??? That software is best developed according to a plan which respects a life-cycle.
Pages:
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77