A.Usage of a more traditional software development lifecycle

B.Using a reference model, e.g. TMMi

C.Process ownership and experienced moderators who drive the inspection process.

D.Alignment with software process improvement

E.Training of those involved

F.The availability of stands and processes

G.Management support

A.Using action words to describe the actions to be taken, the test data.

B.Being based on Equivalence Partitioning testing techniques.

C.Separating out the test data inputs and using a generic script that can read the test data and perform the same test steps with different data.

D.Scaling to support large numbers of users.

A.The test schedule

B.Test performance indicators

C.The test design techniques to be used

D.Test training needs for the project resources

E.The entry and exit criteria for each test phase

A.This can serve as a way to build their confidence in the system

B.They have the ability to also focus on invalid test cases

C.They are a cheap resource

D.They have good testing skills

A.Static analysis tools can be used before code is written.

B.Static analysis tools find defects earlier in the life cycle.

C.Static analysis tools are particularly effective for regression testing.

D.Static analysis tools test that the delivered code meets business requirements.