8 A Test Plan Walkthrough
It is VERY easy to be ambiguous, or to have misunderstandings.
NOTE any assumptions.
CHECK with others, especially USERS

Top Down (Stepwise Decompostion) often helpful
Cluster, depending on applicaton, but at least:
input
computations
output
(requirements for each cluster/section/object)

use cases (and variants)
(boundary values; illegal input, etc)
happy path versus alternative paths versus failure paths
specify tests, test data, acceptable results
	edge cases and corner cases
Be aware that program requirements can be modified;
	named constants
	generalizable code
How much effort is needed for any specific requirement?

For temperature, below absolute zero is not a possible value.
But for every day use, how significant is that?
For grades, negative values are inappropriate.

Tradeoff: be very specific  about the test plan
or trust the tester more

How about non-functional requirements?
E,g, speed
How do you know which circumstances might violate the constraint?
[See also 'real time systems' e.g. in Operating Systems]