All of the above
A table containing rules for combinations of inputs to two fields on a screen
A table containing rules for interfaces between components.
A table containing rules for mortgage applications.
A table containing rules for chess.
Test design specification
Test case specification
Test procedure specification
Which of the following statements about the relationship between statement coverage and decision coverage is correct?
100% statement coverage is achieved if decision coverage is greater than 90%.
100% decision coverage always means 100% statement coverage.
100% statement coverage always means 100% decision coverage.
Defects could cause a downstream effect
Defects will cause downstream damage; the scope and impact of the defect is beyond the document under inspection.
Defects are not likely to cause downstream damage
Explicitly plan and track review activities
Continuously improve process and tools
Pick things that really count
All of them
The number of decisions in a program.
It provides an indication of the amount of testing necessary to practically avoid defects.
Identify high risk, complex areas.
All of them
Static Analysis is for early detection of defects ;
Static Analysis is for identification of defects not easily found in dynamic testing;
Static Analysis provides early warning about suspicious aspects of the code, design or requirements;
All of them
Gives quality information about the code without executing it.
Checks expected results against actual results.
Can detect memory leaks.
Gives information about what code has and has not been exercised.
Inspections are led by a trained moderator, whereas technical reviews are not necessarily.
Technical reviews are led by a trained leader, inspections are not.
In a walkthrough, the author does not attend
Participants for a walkthrough always need to be thoroughly trained
Faults in the requirements
Too few comments
Instructions are executed.
The data items are accessed and modified by the code.
data is organised, independent of the program.
With examining how well the system does something, rather than what it does.
With what the system does, its features or functions.
Less procedural and less formalized
Less procedural and more formalized
More procedural and less formalized
use the internal structure of the software to derive test cases.
Use functional aspects of software to derive test cases.
Use non-functional aspects of software to derive test cases.
a design document
A requirement specification document
A high level document