Chapter 11& 12 – Managing Systems

Implementation & Maintenance

2
• Each program must be tested to make sure it
functions correctly
• Desk checking
• Groups of three to five IT staff members
participate in code review
• Objective is to have a peer group identify
errors, apply quality standards, and verify
that the program meets the requirements
of the system design specification

4
FIGURE 11-22 The first step in testing is unit testing, followed by integration testing, and then
system testing

5
• 1. Unit Testing
• The testing of an individual program or module
• Programs that interact with other programs and files are tested
individually, before they are integrated into the system
• Objective is to identify and eliminate execution errors that could
cause the program to terminate abnormally, and logic errors that
could have been missed during desk checking
• Someone other than the programmer who wrote the program
usually creates the test data and reviews the results
• Test data should contain both correct data and erroneous data
and should test all possible situations that could occur

• 2. Integration Testing
• Testing two or more programs that depend on each other to make
sure that the programs work together properly

6
• 3. System Testing
• Perform a final test of all programs
• Verify that the system will handle valid and invalid data
properly
• Ensure that the IT staff has the documentation and
instructions needed to operate the system properly and that
backup and restart capabilities of the system are adequate
• Demonstrate that users can interact with the system
successfully
• Verify that all system components are integrated properly
and that actual processing situations will be handled
correctly
• Confirm that the information system can handle predicted
volumes of data in a timely and efficient manner

7
• System Documentation
• Describes the system’s functions and how they are
implemented
• Includes data dictionary entries, data flow diagrams,
object models, screen layouts, source documents,
and the systems request that initiated the project
• Operations Documentation
• Operations documentation contains all the
information needed for processing and distributing
online and printed output
• User Documentation
• Consists of instructions and information to users who
will interact with the system and includes user
manuals, Help screens, and tutorials
9
• After system testing is complete, you present
the results to management
• You should describe the test results, update
the status of all required documentation, and
summarize input from users who participated
in system testing
• You also must provide detailed time
schedules, cost estimates, and staffing
requirements for making the system fully
operational

12
• Prepare a separate operational environment
and test environment
• Provide training for users, managers, and IT
staff
• Perform data conversion and system
changeover
• Carry out a post-implementation evaluation
of the system
• Present a final report to management

13
Access to the operational environment is limited to
users and must strictly be controlled
FIGURE 11-28 The test environment versus the operational environment.
Notice that access to the test environment is limited to IT staff,
while the access to the operational environment is restricted to users

15
• Training Plan
• Essential to provide the right training for the right
people at the right time
• The first step is to identify who should receive
training and what training is needed
- Users
- Managers
- IT Staff
• Look carefully at the organization, how the system
will support business operations, and who will be
involved or affected

16
FIGURE 11-30 Examples
of training topics for three
different groups. Users,
managers, and IT staff
members have different
training needs

17
• Vendor Training
• If the system includes the purchase of software or hardware, then
vendor-supplied training is one of the features you should include
in the RFPs (requests for proposal) and RFQs (requests for
quotation) that you send to potential vendors
• Webinars, Podcasts, and Tutorials
• Many vendors offer Web-based training options, including
Webinars, podcasts, and tutorials
• A Webinar (web and seminar) is an Internet-based training
session that provides an interactive experience
• A pre-recorded Webinar can be delivered as a Webcast – a
one-way transmission, whenever a user wants support
• Outside Training
• Many training consultants, institutes, and firms are available that
provide either standardized or customized training packages

18
• ONLINE TRAINING
• Regardless of the
instructional method,
training lessons should
include step-by-step
instructions for using
the features of the
information system
• Training materials
should resemble actual
screens, and tasks
should be typical of a
user’s daily work — the
more realistic, the
better
FIGURE 11-33 A sample lesson
in an online tutorial

20
 System changeover is the process of putting
the new information system online and
retiring the old system
 Changeover can be rapid or slow, depending
on the method
 The four changeover methods are:
◦ 1. Direct cutover
◦ 2. Parallel operation
◦ 3. Pilot operation
◦ 4. Phased operation

26
FIGURE 11-37 The four system changeover methods

 1. Direct Cutover
◦ Causes the changeover
from the old system to
the new system to occur
immediately when the
new system becomes
operational
◦ Usually is the least
expensive changeover
method because the IT
group has to operate
and maintain only one
system at a time
27
FIGURE 11-37 The four system changeover methods

 2. Parallel Operation
◦ Requires that both the
old and the new
information systems
operate fully for a
specified period
◦ Obvious advantage of
parallel operation is
lower risk
◦ Company can use the
old system as a backup
◦ Most costly changeover
method
28
FIGURE 11-37 The four system changeover methods
 3. Pilot Operation
◦ Combines direct cutover
and parallel operation to
reduce risks and costs
◦ Implementing the
complete new system at a
selected location of the
company
◦ The old system continues
to operate for the entire
organization, including
the pilot site
◦ Restricting the
implementation to a pilot
site reduces the risk of
system failure
◦ Less expensive than a
parallel operation for the
entire company 29
FIGURE 11-37 The four system changeover methods
 4. Phased Operation
◦ Implement the new system in
stages, or modules
◦ Combines direct cutover and
parallel operation to reduce
risks and costs
◦ In phase operation, it give a
part of the system to all users,
while in pilot operation it
provides the entire system but
to only some users
◦ Risk of errors or failures is
limited to the implemented
module only
◦ Less expensive than full
parallel operation because you
have to work with only one
part of the system at a time 30
◦ The SDLC model usually
includes five steps
 I) Systems Planning
 II) Systems Analysis
 III) Systems Design
 IV) Systems Implementation
 V) Systems Security and
Support

36
◦ Maintenance tasks
 Corrective Maintenance- fix errors and problems
 Adaptive Maintenance- provide enhancements
 Perfective Maintenance- improves system’s
efficiency &reliability
 Preventive Maintenance- avoids future problems

37
 The systems implementation phase consists of
application development, testing, installation,
evaluation of the new system, provide training and
maintenance.
 Systems support and security covers the entire period
from the implementation of an information system
until the system no longer is used.
 Corrective, Adaptive, Perfective and Preventive are
types of system maintenance

43