Minimal time and effort, new system is available immediately

If the new system fails, the old systems runs a backup

All features are fully trialled

Allows people to get used to the new system

Running two systems is costly in terms of time and money

If the new system fails, there is no fall back

Only a small part of the organisation suffers

Training of staff can be done in stages

The new system is stopped and new system is started

The new system is started, but the old system is kept running alongside it

The new system is piloted with a small subset of the organisation

The new system is introduced in phases

If the new system fails, there is no fall back for that part of the system

Running two systems is costly in terms of time and money

Only part of the data will be at the destination

The rules that are set up by programmers can be different

Incompatible file formats

Incomplete data transfers

Validation rules

All of the above

It ensures that the system works as expected

It reduces productivity

It increases end user dissatisfaction

It is not important

Alpha testing is performed by internal employees, beta testing by clients

Alpha testing is performed at client location, beta testing at developer's site

Alpha testing is less important than beta testing

There is no difference

A black-box without knowing its internals

A white-box with full knowledge of its internals

A system that is not tested

An outdated software