Chapter Five:

Implementation

5.1 Introduction
Introduce the chapter.
The implementation phase consists of
developing, testing and deploying the system.
 New system installation pre-requisites, System
customization to meet customer needs or general-
purpose system

5.2 System Software Specifications

(platforms, packages, libraries,
Specifications etc.)
 Hardware Specifications (CPU, RAM,
camera, routers, switches, cables, etc.)
System testing is a process of executing a
program with the sole intention of looking for its
faults
5.3 System
Testing
Define testing objectives

Give screenshots of test results

obtained
 Verification (Compare performance with the
existing system performance)

Verification &
Validation
Validation (put screen shots showing that the system validates data upon
entry)
Testing Methodologies
• It is the process of introducing a new system
into an organisation. 5.4 Installation •
Involves the following processes: and
Conversion • System training (state the training
needs and who should be trained on what)
• Training schedules/plans (Give the schedule)
• System installation and User Acceptance
• Conversion Methods (discuss the conversion methods and
recommend one for the system)
Direct changeover
• A direct changeover occurs when an old
system is completely replaced with a new
system at a given moment and the new system
is put into use
Parallel
change over
• Parallel changeover is when
the new system is used with
the old system simultaneously
for some time. This type of
changeover is done to
mitigate the risk of system
failure.
 Pilot change
• This method of changeover is when the
new system is used in a department
before it is implemented in the whole
organisation. After the system has been
used successfully in that department it is
then installed in every department of
the organisation

Phased
changeover
• It is also known as gradual
changeover as the units of
the new system are
implemented one after the
other. This method is when
the old system works with the new system. The new system is installed bit by bit
until full installation is reached.
 (Quality testing and assurance.
5.5 System Different maintenance strategies)
Maintenance • Adaptive maintenance
• Corrective maintenance
• Preventive maintenance
• Perfective maintenance
 Analyse your system in terms:
5.6 Performance Throughput,
Analysis Speed,
Services,
Security.
• It is impossible to design and develop a

5.7 system that is so perfect that no one needs to improve it.

Recommendation • This should address two things: firstly, new for

Future areas of investigation prompted by
Development developments in this project, and secondly
parts of the current work which were not
completed due to time constraints and/or
problems encountered.
• Outline at least three future developments that needs to be done to the system.
 Describe the degree to which the
results support the original
5.8Conclusions objectives laid out for the project
(partially or fully achieved, or
exceeded; The principal outcomes of
your research project; what the
project suggested, revealed or
indicated)
• END