Page 532 -

Chapter 13 Building Information Systems 531

FIGURE 13.5 A SAMPLE TEST PLAN TO TEST A RECORD CHANGE

When developing a test plan, it is imperative to include the various conditions to be tested, the
requirements for each condition tested, and the expected results. Test plans require input from both
end users and information systems specialists.

The direct cutover strategy replaces the old system entirely with the new
system on an appointed day. It is a very risky approach that can potentially be
more costly than running two systems in parallel if serious problems with the
new system are found. There is no other system to fall back on. Dislocations,
disruptions, and the cost of corrections may be enormous.
The pilot study strategy introduces the new system to only a limited area
of the organization, such as a single department or operating unit. When this
pilot version is complete and working smoothly, it is installed throughout the
rest of the organization, either simultaneously or in stages.
The phased approach strategy introduces the new system in stages, either
by functions or by organizational units. If, for example, the system is introduced
by function, a new payroll system might begin with hourly workers who are
paid weekly, followed six months later by adding salaried employees (who are
paid monthly) to the system. If the system is introduced by organizational unit,
corporate headquarters might be converted first, followed by outlying operating
units four months later.
Moving from an old system to a new one requires that end users be trained to
use the new system. Detailed documentation showing how the system works
from both a technical and end-user standpoint is finalized during conversion
time for use in training and everyday operations. Lack of proper training and
documentation contributes to system failure, so this portion of the systems
development process is very important.

Production and Maintenance
After the new system is installed and conversion is complete, the system is
said to be in production. During this stage, the system will be reviewed by
both users and technical specialists to determine how well it has met its orig-
inal objectives and to decide whether any revisions or modifications are in
order. In some instances, a formal postimplementation audit document is

MIS_13_Ch_13 global.indd 531 1/17/2013 2:31:22 PM