INFS 328
Systems Analysis and Design
Session 8 – Systems Implementation –
Part 1 – Systems Testing
Lecturer: Prof. Ellis Edwin Badu, Dept. of Information Studies
Contact Information: eebadu@[Link]
College of Education
School of Continuing and Distance Education
2017
Session Overview
After designing the system you are now ready to implement
the system. System implementation involves writing and
testing programs and procedures required by the approved
system design document; completing the user manuals both
for training purposes and for continued use during
operations; testing of the system and carrying out
installation effectively and efficiently.
Slide 2
Session Outline
The key topics to be covered in the session are as follows:
• System Testing
Slide 3
Topic One
SYSTEM TESTING
Slide 4
System Testing
Now that the software packages and in-house programmes
have been installed, you need to conduct a final test. All
software packages, custom built programmes, and any
existing programmes that comprise the new system must
be tested to ensure that they all work together.
The knowledge acquired will enable you to test your new
system on the computer, and also understand how to apply
effectively any of the implementation tests on a system.
Slide 5
System Testing
Testing the New Information System
This test usually involves analysts, owners, users, and
builders. The system analyst facilitates the completion of
the testing process. The systems analyst typically
communicates testing problems and issues with the project
team members.
Slide 6
System Testing
Testing the New Information System
The system owners and system users hold the ultimate
authority on whether or not a system is operating correctly.
System development team members of various specialties,
are involved in the systems testing. For example,
application programmes, database programmers, and
networking specialists may need to resolve problems
relating to their respective specialties during systems
testing.
Slide 7
System Testing
Several types of testing are done in the following sequence.
• Realistic tests – You present the system with a realistic
example of the environment in which the system is to
operate. This tests the system and the understanding and
training of users. It also gives the users confidence before
they take over the system.
Slide 8
System Testing
• Contrived tests – This test deals with as many unusual
and unexpected events as possible such as incorrect
codes, wrong amounts, inappropriate commands and so
on. The intention is to see how the system reacts and
whether all answerable anomalies have been centred for
in the system.
Slide 9
System Testing
• Volume tests – This test is about presenting the system
with a large volume of transactions to see how it reacts,
particularly in operating and response times
Slide 10
System Testing
• Acceptance testing is undertaken by users after all other
system testing is complete. It is designed to test the
complete system so that the users can see if the new
system is satisfactory. As the final system test, it is
probably the most important and elaborate. It is
performed by the users using realistic data over an
extended time period. It is an extensive test that
addresses three levels of acceptance testing – verification
testing, validation testing and audit testing.
Slide 11
System Testing
Levels of Acceptance Testing:
• verification testing - uses the system in a simulated
environment using simulated data. The simulated test is
sometimes called alpha testing. The simulated test is
primarily looking for errors and omissions regarding end-
user and design specification that were specified in the
design phase but not fulfilled during the development of
the system.
Slide 12
System Testing
Levels of Acceptance Testing:
• validation testing - runs the system in a live environment
using real data. This is sometimes called data testing.
During this validation, a number of items are tested:
Slide 13
System Testing
• systems performance – performance in terms of
response and processing times. If those are not
acceptable then the programs may have to be re-written
Slide 14
System Testing
• Peak workload processing performance – can the system
handle the workload during peak processing periods? If
not improved hardware and software may be needed to
increase efficiency
Slide 15
System Testing
• Human engineering test – is the system as easy to learn
and use as anticipated, if not it is inadequate
• Methods and procedures test – methods and procedures
must be tested and may have to be modified if they
prove awkward and inefficient
Slide 16
System Testing
• Backup and recovery testing – all back up and recovery
procedures should be tested. This should include
simulating a data loss disaster and testing the time
required to recover from the disaster
Slide 17
Questions
Individual Assignment:
What is systems acceptance test? When is this test
performed?
Forum Question
What are the three levels of acceptance testing? And what
is their importance in the implementation process.
Slide 18
References
• Checkland, P. (1999). System Thinking, System Practice. Chiches:
John Wiley.
• O’Brien, J. A. (2003). Introduction to Information Systems:
Essentials for E-Business Enterprise. Boston: Irwin
• O’Leary, I. and O’leary, T. I. (2004). Computing Today. Boston: Mc
Craw-Hill
• Rowley, J. (1990). The Basics of Systems Analysis and Design for
Information Managers. Ludin: Clive Bingley
• Whitten, J. et al (2000). Systems Analysis and Design Methods. 6th
ed., Boston: Mc Craw-Hill
Slide 19
