The bidder’s test policy should enforce that incident management fully conforms to IEEE 1044.

The bidder’s project strategy shows that the data content of all the test environments conforms to EU standards.

The bidder’s test plan shows that the application will be delivered for acceptance in six months time.

The bidder’s project test plan depicts a phased implementation with later delivery dates to be confirmed and states that test deliverables will be developed using IEEE 829 as a guide.

Create an estimate based on the function point analysis technique and test point analysis

Create an estimate based on the complexity of the code

Create an estimate based on the credentials of the successful bidder

Create an estimate based on a percentage of the development effort

The expectation is that development testing is not adequate.

Exit criteria are used to decide on when to stop testing.

Entry and exit criteria are a principal way for getting adequate resources.

Using entry and exit criteria will prevent software that is not or poorly tested from going to the next test level.

a

b

c

d

e

f

Test environment more complex

Define expectation for tasks and deliverables

Clear channels of communications

Possibly different cultures

Testing of non-functional requirements

Audit trail from requirements to test cases

Applying test automation

In the delivered application, one of the countries, as specified in the requirements, has not been correctly implemented.

The application takes too long to process a request for additional cover.

The test cases do not cover the key requirements.

The successful bidder may not deliver all the required functionality on time.

Code cannot be released into production until independent testing is complete.

Testing is isolated from development.

Independent testers find different defects and are unbiased.

Developers do not have to take as much responsibility for quality.

By providing training in the payroll domain

By providing a workshop on test design techniques

By providing specific training on the systems being tested

By providing training on reviewing requirements

Developer and independent testing will overlap and waste resources.

Developers loose the sense of responsibility and independent testers may become a bottleneck.

Independent testers need extra education and always cost more.

Independent testers will become a bottleneck and introduce problems in incident management.

Has there been sufficient comparison of tools?

What are the problems we are trying to address?

Do we have a set of tool requirements to validate the tool against?

How will the implementation be organized?

Which project will be selected to perform the tool pilot?

Is customized training available?

How will the change process be managed?