1&2 are true and 3 is false.

1,2&3 are true.

1 is true, 2&3 are false.

1&2 are false, 3 is true.

Risks involved

Contractual requirements

Legal requirements

Test data

Test management

Test design

Test planning

Test execution

Find faults

Improve quality

Check user friendliness

Improve software accuracy

Correctness

Usability

Viability

Reusability

Incidents should always be investigated and resolved.

Incidents occur when expected and actual results differ.

Incidents can be analyzed to assist in test process improvement

An incident can be raised against documentation

Usability testing.

Statement Coverage.

Dataflow testing.

Cause-effect graphing.

It is easy to execute.

It is designed to detect faults if present.

The expected outcome is specified before execution.

It is unlikely to delay progress.

An appropriate way of deriving system tests.

Only used if good requirements are not available.

Only used when good requirements are available.

The most appropriate way of deriving system tests.

IEEE 802.11

ISO 9001

BS 7925-1

BS 7925-2

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.

Functions not to be tested.

Environmental requirements.

Analysis of Specifications.

Entry and Exit criteria.

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.

Estimating test duration.

Incident Management.

Configuration Management.

De-bugging.

Metrics from previous similar projects.

Discussions with the development team.

Time allocated for regression testing.

Both A & B.

Compiling code is not a form of static analysis.

Static analysis need not be performed before imperative code is executed.

Static analysis can find faults that are hard to find with

Extensive statistic analysis will not be needed if white- Box testing is to be performed.

Testing whether a known software fault been fixed.

Executing a large number of different tests.

Testing whether modifications have introduced adverse side effects.

Using a test automation tool.

This is an acceptable risk of a multi-user system.

Insufficient functional testing has been performed.

This indicates an important non-functional requirement was not specified and tested.

It is not possible to test against such events prior to release.

Testing the system when combined with other systems.

Testing a sub-system using stubs and drivers.

Testing a system with a large number of users.

Combing software components and testing them in one go.

How rapidly data is transferred through a program.

The rate of change of data values as a program executes.

The use of data on paths through the code.

The intrinsic complexity of the code.