SCHOOL OF TECHNOLOGY

BACHELORS IN INFORMATION TECHNOLOGY

UNIT: PROJECT PROGRAMMING
TITLE: CUSTOMER SEGMENTATION SYSTEM
IMPLIMENTATION
NAME: JOSHUA ODHIAMBO MERCY
REG NO: 18/06471
SUPERVISOR: MR JUSTUS MUTIA.
Email:1806471@students.kcau.ac.ke

THIS PROJECT PROPOSAL ISSUBMITTED IN

PARTIAL FULFILMENT OF THE REQUIREMENTS
OF THE AWARD OF BACHELORS IN
INFORMATION TECHNOLOGY IN KCA
UNIVERSITY
 Table of Contents

IMPLEMENTATION

INTRODUCTION

PURPOSE

OUTCOME

IMPLEMENTATION STRATEGY

VALIDATION OF PARALLEL CHANGEOVER

 DECLARATION

I declare that this project is of my own ideas, work and effort.

It hasn’t been presented by any other person before and has been created and developed
by my own time and efforts.

Name: JOSHUA ODHIAMBO MERCY

Signature: Date:

This proposal has been submitted for examination purposes to my project supervisor for
approval

Supervisor: Dr. Justus Mutia

Signature: Date:
IMPLEMENTATION
INTRODUCTION
This document hails from a means of facilitating the installation and delivery of
the entire system to the organization. The implementation stage is supposed to
unravel the addressed concerns raised by the user which is to encounter the
user’s requirement specification.
PURPOSE
The purpose of the implementation strategy is to ensure:

 The intended project outcomes are achieved prior to the project closure.

 The final stages of the project are fared in an agreeable manner.

 The use of the project’s output is interconnected to the project planned

results.

 The success of the project’s output is assessed and corrective action taken

if required.

OUTCOME
The projected results of this implementation strategy are as follows:
 A minimum disruption to the organization and client’s daily routine.
 A quicker execution of client’s needs and various practices.
 A smooth changeover to welcome the new system.
IMPLEMENTATION STRATEGY

The implementation strategy chosen for the Customer Segmentation is a

parallel changeover. Which will allow a steady analysis and comparison of two
systems running simultaneously, thus enabling the end-users to learn more
and more of the new system and consequently be ready to change to a new
system.
The existing system can act as a backup to the new system until both the end-
users and the developer are entirely satisfied with the performance and
integrity of the new system. Parallel changeover will bring out more meaning
to automation and end user will be able to value a fully computerized system
compared to the present manual system.

VALIDATION OF PARALLEL CHANGEOVER

 It becomes easy for users to learn the new system because they work
with it and at the same time are working with the old system.
 It becomes easier for the new system to be accepted as the users have
in mind that the old system is not being faced out immediately.
 It is the most preferred form of changeover strategy since it offers
security to the users this ensures that the user will always have
confidence that if the old system does not work, they can always rely
on the new system.
 It helps in comparing the performance of the new system in
comparison to the old system.
 It becomes easy to debug the new system and not affect the normal
running of the business because they always have the old system.