Identify any unresolved
incidents.
??? Evaluate each test item including its limitations based on the test results and the item level pass/
fail criteria. Add an estimate of failure risk.
??? Summary of activities and methods. Summarize:
Test Documents 157
??“ The test approaches taken including usability and the tools used
??“ The major testing activities and events
??“ The resource consumption data, for example, total staffing level, total machine time, and total
elapsed time used for each of the major testing activities (see section A.7 in Appendix A)
8.14 Usability Test Summary
As section 8.13, but add:
??? Metrics overview based on the usability metrication occurring so far. Structure this in terms of
the questions the metrics are attempting to answer. If you are comparing products or versions
you can add a comparison overview here too. Kiviat (Aka ???radar???) diagrams can be useful here
(Figure 8.26).
??? Bug (or root) cause analysis is one in which the causes of each bug are listed in order of severity.
Note that the severity can be determined from the table in Appendix C. In particular if a human
factors (HF) bug can be shown to have occurred regularly (for example if more than 30% of the
users experience it), the column entitled ???Fails regularly??? can be employed. The causes are of
three kinds:
??“ Functional (X doesn??™t work)
??“ Non-functional (the system is too slow and the user times-out with boredom)
??“ Human: The way information is presented, perhaps the feedback pattern employed is ???wrong,???
inhumane, or otherwise psychologically unwise.
Pages:
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343