Summary of Presentation of January 27, 1999

	We covered pages 493 - 494 in the textbook.  
we started with Tom Gilb's software testing strategic issues.
These are:
1.  Product requirements must be testable;
2.  Testing objectives must be explicit and measurable;
3.  We must understand the motivations, skills, and expected product uses by
each class of potential users;
4.  testing should use a rapid cycle of one to two weeks and be 
repeated every four to nine weeks;
5.  Software should be robust and self-testing;
6.  Technical reviews are an effective and cost-effective prelude to 
unit testing;
7.  The test strategy and test set should undergo formal, technical 
reviews;
8.  We should never be satisfied with our testing strategy, but should use
metrics to evaluate and improve it.