This documentation is normally in the form of a
Release note
(see Chapter 8).
??? The item itself, possibly held on disk in a special secure area and identified by a special filename.
??? Any item test results which demonstrate that the item has been tested to some level.
??? In the case of large items such as entire subsystems, the reports of configuration or function
reviews may be necessary.
??? The item tests should it have been necessary to change those as well.
??? A checklist which all parties can use to ensure and demonstrate their agreement, that all the
required actions have been executed.
The keys to success of item acceptance reviews are preparation and formality. The item acceptance process
as indicated by the checklist must have been previously agreed by all parties. If any part of the checklist
cannot be signed, it is the responsibility of the moderator either to reconvene the review (if the discrepancies
are too large) or to ensure that any minor changes are made and the necessary signatures obtained.
A pedantic participant can be worth their weight in gold during such reviews and when well prepared,
they can require seven minutes per item or a day per major subsystem.
7.2.2 Testing and Reviewing Changes
As a test manager you may have suffered from having changes made arbitrarily and without reference
to you. When the project realizes that untested changes are counter-productive, you will be involved in
their review and approval.
Pages:
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253