It includes the verification of designs.

It states that modules are tested against user requirements.

It specifies the test techniques to be used.

It only models the testing phase.

When the specified number of faults are found.

When the test completion criteria are met.

When all high and medium priority tests are complete.

When all statements have been executed.

Features to be tested

Incident reports

Risks

Schedule

Statement testing

Path testing

Data flow testing

State transition testing

find as many faults as possible.

test high risk areas.

obtain good test coverage.

test whatever is easiest to test.

encapsulation

inheritance

polymorphism

both b and c

cycles in the program

errors in the program

independent logic paths in the program

statements in the program

behavioral testing

black-box testing

grey-box testing

white-box testing

Function points

External Interface Files

Internal Logical Files

Feature points

50-50

40-60

60-40

Depend on the criticality of the application

Cause effect graph

Orthogonal array testing

State transition

Decision table

VTM

DL

BA

SPONSOR

VTM

DL

BA

SPONSOR

Before FPQ

After FPQ

Before HLE

After HLE

Boundary value analysis

Equivalence Partioning

State transition

Cause effect graph

3124

4312

3412

1342

FPA

SWAG

DELPHI

Production standards

True

False

Yes

No

NIL

NiL

Yes

No

__

NIL