MANAGEMENT INFORMATION SYSTEMS
Chapter 8
Chapter 8: System Implementation
8.1 Learning Outcomes
After complete this lesson, you would be able to:

Know the various testing and its purposes.

Discuss the purposes of system conversion.

Why do we need to give training to the users.

Explain the types of documentation in the software development.
8.2 Introduction

At the conclusion of system design, SA prepared a system design
specification that contains the complete design for the new
information system.

Now, in the system implementation phase, the system design
specification serves as a blueprint for constructing the new system.

The IS department will plan, develop, document, integrate and test
all the new programs and code modules.

If the design is based on a commercial software package, IS staff
members can add custom features by using the application’s builtin development tools or by creating additional programs and
modules.
8.3 Application Development

A new system requires planning, construction and testing.

Programs and modules musts be designed, coded, tested and
documented.

After developing the programs and code modules, SA and
programmers perform the link testing of modules, system testing
and complete all documentation.
8.3.1 Coding

Coding is the process of turning program logic into specific
instructions that can be executed by the computer system.

Small programs usually are coded by a single programmer,
whereas larger programs are divided into modules that can be
assigned to different individuals or groups.

Each IS department has its own standards for programming
languages and coding.

A strong trend exists toward using report writers, screen
generators, program generators, fourth-generation languages and
other CASE tools that produce code directly from program design
specifications.
SYSTEM IMPLEMENTATION
Page 1 of 10
MANAGEMENT INFORMATION SYSTEMS
Chapter 8
8.4 Testing The Application

After coding, a programmer must test the program to be sure that it
functions correctly.

The programmer’s first step is to compile the program using a
language compiler.

This process detects syntax errors, which are language grammar
errors.

The programmer corrects the error until obtaining a clean
compilation, which indicates that the program code can be
executed properly.

Next, the programmer desk checks the program. Desk checking is
the process of reviewing the program code to spot logic errors,
which produce incorrect results.

This process can be performed by the person who wrote the
program or by other programmers.

Many organizations require a more formal type of desk checking
called a structured walkthrough or code review.

The objective of structured walkthrough is to identify errors,
maintain IS standards and verify that the program meets all
requirements as set forth in the system design specifications.

There exists to be some major types of testing:
Unit testing
 The testing of an individual program or module is called unit
testing.
 The objective is to identify and eliminate execution errors that
cause the program to terminate abnormally and logic errors
that might have been missed during desk checking.
 Test data should contain both correct data and erroneous data
and should test all possible situations that the program must
handle.
 For example, for a field that allows a range of values, the test
data should contain minimum values, maximum values and
values outside the acceptable range.
Link testing
 Testing two or more programs that depend on each other is
called link testing, string testing, series testing or integration
testing.
 Only by performing link test can be sure that the programs
work together properly
SYSTEM IMPLEMENTATION
Page 2 of 10
MANAGEMENT INFORMATION SYSTEMS

Chapter 8
It will also ensure that the job streams are correct. A job
stream is a series of statements that control program, files, and
devices that must work together properly.
Top-Down Incremental Testing

Start the testing with the president module.

It will complete the testing from one phase before going to
the next phase.

Each module tested will also be re-tested in the next round.
Thus, each time we will increase the number of module
being tested by one.

Both the top-down approaches test the upper-level interfaces
repeatedly.
Bottom-Up Incremental Testing

Begins with the bottommost module.

It works out its way up the structure chart.

Bottom-up approach tests the lower-lever
repeatedly.
interface
Sandwich Incremental Testing

The combination of top-down and bottom-up approach.

A team of member will perform the top-down testing, while
another team of member will perform the bottom-up testing.

Both teams will meet somewhere in the middle.
System Testing / Acceptance Tests

After completion of link testing, one must run a series of
system tests that involve the entire information system.

A system test includes all typical processing situations.

During a system test, user enters data, including of live data,
perform queries, and print reports to simulate actual
operating conditions.

Major objectives of system testing are:  Perform a final test of all programs.
 Ensure that the IS 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.
SYSTEM IMPLEMENTATION
Page 3 of 10
MANAGEMENT INFORMATION SYSTEMS
Chapter 8
 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.
Overview of Program Testing
Sys te m
Te s t
Unit Test
Program 1
Link
Te s t
Unit Test
Program 2
Link
Te s t
Unit Test
Program 4
Unit Test
Program 3
Unit Test
Program 5
Link
Te s t
Unit Test
Program 6
8.5 Documentation

Documentation is essential for successful system operation and
maintenance.

Accurate documentation helps a programmer who needs to carry
out a future program change and makes maintenance easier, faster
and less expensive.

Documentation explains the system and helps people interact with
it.

Documentation could include paper-based and computer-based
(embedded training such as context sensitive help) as well.

For modern information system, the documentation includes the
on-line help, which is designed as a part of the system interface.

Documentation can be further divided into two major types:
- System documentation
 Records detailed information about a system’s design
specifications, its internal workings and its functionality.
 Internal documentation: part of the program source code or is
generated at compile time.
SYSTEM IMPLEMENTATION
Page 4 of 10
MANAGEMENT INFORMATION SYSTEMS
Chapter 8
 External documentation: the outcome of all of the structured
diagramming techniques, such as data flow, entity-relationship
techniques, etc.
- User documentation
 Written or other visual information about an application system,
how it works, and how to use it.
 Two target audiences: the new employee who knows nothing
about the system, and the experienced employee who uses the
documentation only for occasional reference.
 In user documentation, we need to give instructions for both
manual and computerized procedures, explaining normal
conditions, such as exactly how to bring up a particular screen,
as well as conceivable error conditions.
 User documentation includes the following:
 Systems overview that clearly describes all major system
features, capabilities, and limitations.—user manual
 Source document content, preparation, processing, and
samples.
 Menu and data entry screen options, contents, and
processing instructions.
 Reports that are produced regularly or available at the user’s
request, including samples.
 Security and audit trail information.
 Procedures for requesting changes and reporting problems.
 Frequently asked questions (FAQs)
 Explanation of how to get help
8.6 Installation And Evaluation

The next steps in system implementation are the installation and
evaluation of the information system.

Task being performed in installation and evaluation are: - Prepare an operational environment and install the new system.
- Provide training
- Perform system changeover
- Carry out post implementation evaluation of the information
system
8.6.1 Site Preparations

Issues to be considered are: - Vendor specifications
- Operating and environment requirements
SYSTEM IMPLEMENTATION
Page 5 of 10
MANAGEMENT INFORMATION SYSTEMS
Chapter 8
 Air-conditioning, power, floor-load units, fire protection,
communication wiring.
- Space requirements
 Equipment layout, service areas and storage, management
offices, library, etc.
- Security requirements
 Fire protection, system security, access to computer room.
8.7 Training

No system can be successful without proper training

Consideration of training plan should start early in the system
development.

At the creation of documentation, one should think of how to use
the material in the training sessions.

It is essential to provide the right training to the right people at the
right time.

All people who have primary or secondary use of the system must
be trained.

This includes everyone from data-entry personnel to those who will
use output to make decisions without personally using a computer.

The amount of training requires depend on how much someone’s
job will change because of the new system.

Analyst must ensure that users of different skill levels and job
interests are separated.

Different individual will have different knowledge, education level,
working responsibilities, and many other factors that will be
needed to take into consideration.

Possible training source:
- Vendors
 Large vendors often provide off-site, one- or two-day training
on their equipment for free.
 These include lecture and hand-on training in a focused
environment (a place decided by the vendor where all the
equipment has been prepared for the trainee to practically use
on).
 This type of training is focused on the products that the
vendors developed therefore scope is rather limited and not
custom suit to your company internal environment.
SYSTEM IMPLEMENTATION
Page 6 of 10
MANAGEMENT INFORMATION SYSTEMS
Chapter 8
- In-House system analyst(trainer)
 In-house system analyst knows the organization’s personnel
and the system very well since he has involved from the
beginning of the development of the system.
 Thus, analyst could provide good training for the respective
users.
 Guidelines should keep in the mind when system analyst
developing a training program:
 Train people in groups, with separate training programs for
distinct groups.
 Select the most effective place to conduct the training.
 Provide for learning by hearing, seeing, and doing.
 Prepare effective training material, including interactive
tutorials.
- External paid trainers (Outside training resources)
 Some organization employ external paid trainers who have
broad experience in teaching people how to use a variety of
computers.
 However, the limitation is that, the external paid trainers may
not be able to custom-tailor their presentations enough to make
them meaningful to the users. This is because they do not
involve in the development.
- Other system users
 It is possible to have any of these trainers train a small group of
people from each functional area that will be using the new
information system.
 They in turn can then be used to train the remaining users.
This approach works well if the original trainees still have
access to materials and trainers as resources when they are
providing the training. Otherwise, it might fall into a trial-anderror situation rather than a structured one.
8.8 System Conversion

System changeover is the process of putting the new information
system into operation and retiring the old system.

Types of conversion:
- Direct changeover
 Conversion by direct changeover, which means on a specific
date, the old system is dropped and the new system is put into
use.
SYSTEM IMPLEMENTATION
Page 7 of 10
MANAGEMENT INFORMATION SYSTEMS
Chapter 8
 User must adapt to the new system. It is quite a risky approach.
It will be impossible to compare new results with the old
system.
 Direct changeover is least expensive changeover method
because the IS group has to operate and maintain only one
system at a time.
 Companies often choose the direct cut-over method for
implementing commercial software packages because these
applications involves less risk of total system failure.
- Parallel conversion
 Running the old system and the new system at the same time, in
parallel. Both systems run simultaneously for a specified period
of time.
 The results are examined, if the same results can be gained over
time, the new system is put into use, and the old one is stopped.
 The cost of running two systems at the same time is highly
expensive.
 Users might tend to use the old system more for they have been
familiar with.
 The most obvious advantage of parallel operation is lower risk.
If the new system does not work correctly, the old system can
be used as a backup until appropriate changes are made.
 Parallel operation is not practical if the old and new system are
incompatible technically, or if the operating environment cannot
support both systems.
- Pilot conversion
 With the pilot conversion, one implements the complete new
system a t a selected location of the company.
 For instance, a new sales reporting system might be
implemented in just one branch office. And this group that uses
the news system first is called the pilot site.
 During the pilot operation, the old system continues to operate
for the entire organization, including the pilot site.
 After the system proves successful at the pilot site, it is
implemented in the rest of the organization, usually using the
direct cut-over method.
 Pilot conversion reduces the risk of system failure, compared to
a direct changeover.
 Operating both systems for only the pilot site is less expensive
than a parallel operation for the entire company.
SYSTEM IMPLEMENTATION
Page 8 of 10
MANAGEMENT INFORMATION SYSTEMS
Chapter 8
- Phased conversion / Gradual conversion
 With a phased changeover, you implement the new system in
stages or modules.
 Instead of implementing a new manufacturing system all at
once.
 One advantage of phased changeover is that the risk of errors or
failures is limited to only the implemented module.
 Phased changeover is less expensive than full parallel operation
because you have to deal with only part of the system at a time.
RISK
DIRECT
High
PILOT
Medium
PHASED
PARALLEL
Low Relative risk and cost characteristics of the FOUR changeover methods
Low
Medium
High
COST
8.9 Post-Implementation Evaluation

Once the new system is operational, SA must perform the postimplementation evaluation.

A post-implementation evaluation assesses the overall quality of
the information system.

The evaluation verifies that the new system meets specific
requirements, complies with user objectives and achieves the
anticipated benefits.

By providing feedback to the development team, the evaluation
also helps improve IS development practice for future projects.
SYSTEM IMPLEMENTATION
Page 9 of 10
MANAGEMENT INFORMATION SYSTEMS



Chapter 8
A post-implementation evaluation should examine all aspects of
the development effort and the end product, the developed
information system.
The same fact-finding techniques use in system analysis can be
used in post-implementation evaluation.
A typical evaluation includes feedback for the following areas: - Accuracy, completeness and timeliness of information of
system output
- User satisfaction
- System reliability and maintainability
- Adequacy of system controls and security measures
- Hardware efficiency and platform performance
- Effectiveness of database implementation
- Performance of the IS team
- Completeness and quality of documentation
- Quality and effectiveness of training
- Accuracy of cost-benefit estimates and development schedules
Review Questions
1.
Explain the following testing:
a.
Unit testing
b.
Acceptance testing
2.
Discuss the purposes of system conversion.
3.
What are different types of documentation used in the software
development?
SYSTEM IMPLEMENTATION
Page 10 of 10