Note any variations
from the current item requirements and designs. A variant of this note may be put on installation CDs.
Specify the names and titles of all persons who should approve this transmittal. Provide space for the
signatures and dates.
5 An anomalous event is not necessarily a bug. It might be caused by some test environmental issue. Some are
foreseeable and can thus be specified in advance such as power failures.
Test Documents 153
8.10.1 Transmitted Items
Identify:
??? The item(s) being transmitted, including their version/revision level
??? The item documents and the test plan relating to the transmitted item(s)
??? The people responsible for the transmitted item(s)
??? The purpose of the release (new feature content, bug fixes, emergency release to the field, for
internal use only, etc.)
8.10.2 Feature Content
List the features of the software. This may be difficult if the item is a single unit (copy the header), but
will be simple when the item represents some release. Identify the features that differ from the last version
of the release. Define any restrictions on its use associated with the release.
8.10.3 Location
Identify the media and location of the item(s) being transmitted. Indicate how media are labeled or
identified. List each file, ordered by media.
8.10.4 Status
Identify:
??? The status of the item(s) being transmitted (draft | reviewed | reviewed and approved | unit-tested
| system-tested | released)
??? Any deviations from the item documents, from previous transmittals of these item(s), and from
the test plan
??? The bug reports which are expected to be resolved by the transmitted item(s)
??? Any pending modifications to item documents which may affect the item(s) listed in the transmittal
report
8.
Pages:
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337