Documents
or code which are exchanged, for example, between program feature groups A and B, and on which group B
relies as some description of what group A does, must be configuration-managed.
Test Documents 155
??? bug details: add details under the following headings if the formality of the project or the
complexity of the bug merits it
??“ summary: summarize the bug. Identify the item(s) involved indicating their version/revision
level (supply references to the test-procedure specification, test-case specification, and test log)
??“ description: describe the incident in which the bug was evident, avoiding redundancy with
other test documents; include the following: inputs, steps taken (describe step-by-step) expected
results, actual results, anomalies (showing the moment the bug is first evident), date and time,
procedure step, (if any) environment (if not obvious), attempts to repeat, testers, the names of
any observers
??“ related activities and observations that may help to isolate and correct the cause of the bug,
for example describe any test-case executions that might have a bearing on this particular bug
and any variations from the published test procedure
??“ effect: indicate what effect this bug will have on the user, the user??™s business, test plans, testdesign
specifications, test-procedure specifications, or test-case specifications, such that the
severity of the bug is evident
??? signature of the observer
??? function of the observer ??” the group within which the observer works or the responsibility held
at the time the problem was observed
??? date on which the observation was made (optionally the time, too)
Pass the observation to the project manager to decide what action is to be taken.
Pages:
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340