We are confused about the two Key areas:Static test techniques and Evaluation. And we can't tell the difference between them.
The description about the two areas we got from "summary TPI UK v1.2_tcm6-32137.pdf" is followed.
As we understand that the two areas is the same, both of them are related to inspection the intermediate products without running programs. We also study the check points to get more info, but we haven't got the key point till now.
We confused that what's the real difference between them. And if there are more examples, maybe we can understand well.
Anybody can help me out?
Static test techniques :
Not everything can and should be tested dynamically, that is, by running
programs. Inspection of products without running programs, or the
evaluation of measures which must lead to a certain quality level, is called
static tests. Checklists are very useful for this.
Evaluation means inspecting intermediate products such as the
requirements and the functional design. The importance of evaluation is
that the defects are found at a much earlier stage in the development
process than with testing. This makes the rework costs much lower. Also,
evaluation can be set up more easily because there is no need to run
programs or to set up an environment etc..
I'm not big fan of TPI, so perhaps anyone experienced with it may comment, though my vision is this: evaluation in TPI is high-level, generic ceremony. You may do static testing and then Evaluate the results of the Static Testing (together with other findings) to make conclusions about quality. You are supposed to mostly find process defects during evaluation (i.e. discrepancy between requirements and design; inconsistency between strategy and actual test coverage, etc.). Statics testing is supposed to find product defects instead: missing exception handling, ambiguous requirements, etc.)
?:the art of a constructive conflict perceived as a destructive diagnose.