This is discussed further in section 17.6.3.
This will lead you into some reasoning about Very Wonderful Psychological theories by your
HF advisor. Good. Luck.
Providing this kind of feedback gives management a unique view of the user experience
which mere anecdotes lack. Write it so that they can take decisions on it. Don??™t include
recommendations (that??™s the HF advisor??™s job), but make them implicit.
??? Weaknesses. There are probably areas you feel you should have tested differently or more rigorously
or you perhaps would have proceeded differently with a Usability Test Candidate (UTC).
Here is the place to own up, if only to yourself.
FIGURE 8.26 Kiviat diagram of task/bug status per release
Edit ?¬?le
Undo
correction
Reopen ?¬?le
Save ?¬?le Manual code
Change
password
Autocode
Drop 1
Drop 2
Drop 3
Drop 4
Drop 5
Create ?¬?le Delete ?¬?le
25
20
15
10
5
158 Manage Software Testing
8.15 Acceptance Certificate (Figure 8.27)
Use this when formal customer acceptance or certification tests are required. Have it completed and
checked by the project manager (or nominee), and offered to the Customer for signature. Keep the
original in the project records.
All references indicated should be provided or marked Not Applicable.
8.16 Security Risk Analysis Report
Here is a typical table of contents of a security risk analysis report. This report would be used as the
basis for implementing and thereafter testing a set of security measures.
Pages:
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344