Review product manual ** Advanced review - Familiar with relevant knowledge of software applications This is very good, and it is easy to think about customers - study existing standards and norms. Software testers should do, not definition, but "inspection" is set with the right standard, there is no omissions. Such as: company usage and agreed; industry requirements; national standards; graphical user interfaces; hardware and network standards - review and testing similar software similar software helps develop test conditions and test methods, may also expose potential problems. ** Level Test - Property Checklist (8) ~ Complete. complete? Do you include all content alone? ~ Accurate. Is the scheme correct? with a clear purpose? ~ Accurate, not vague, clear. Easy to understand and understand? ~ Consistent. Is the function description contradictory? Is there any conflict? ~ Idle. Is the function statement necessary? Information redundancy? Is the customer request? ~ Reasonable. Is it possible for existing human, labor and resources? ~ The code is not related. Define the product instead of design, architecture or code! ~ Test. Do you provide enough test information? - Note checklist ~ Always, every, all, no, never. For such absolute or affirmatively determined narratives, it should be designed for a trying case. ~ Of course, therefore, obvious, obvious, inevitable. These scales sector to accept the assumption. Be careful in the circle. ~ Some, sometimes, often, usually, often, most, almost, too blurred. "Sometimes" function cannot be tested. ~ Wait, such, so on, in such push, the function list ends with such words cannot be tested. Function list must be absolute, explained. Can't deliberate. ~ Good, rapid, cheap, efficient, stable, these are uncertain, not test. Further indication must be further indicated. ~ Processted, rejected, neglected, eliminated, these statements may hide the functionality that needs to be explained ~ If ... then ... (no otherwise). Think about what happens? "
