NAME: JEDIDAH NJERI WAIRIUKO

INDEX NO: 3411020080

SUPERVISOR: MR. KAMWENGU

INSTITUTE: JEREMIAH NYAGAH NATIONAL POLYTECHNIC

SUBMITTED TO: KNEC FOR AWARD OF DIPLOMA IN INFORMATION

COMMUNICATION TECHNOLOGY

DATE OF SUBMISSION: 2024

DECLARATION
I Jedidah Njeri Wairiuko declare that the project entitled Waypalace carwash
system is my own original work that has never been submitted in any KNEC
examination for any particular award.

NAME OF PRESENTER: JEDIDAH NJERI WAIRIUKO

SIGNATURE:
DATE:

NAME OF SUPERVISOR: Mr. JOHN KAMWENGU

SIGNATURE:
DATE:
DEDICATION
I wish to dedicate this project to my family : that is my guardians and also my
motivating friends and teachers for their continued support and encouragement
throughout the project work and research.

I won’t forget my concerned classmates who gave me technical assistance in

ensuring that the project was a success.
ACKNOWLEDGEMENT
I thank Almighty God for giving me the strength and wisdom to come up with this
project and make it successful. I also wish to express my sincere gratitude to my
friends for their assistance and encouragement and making it possible.

I would also to appreciate my supervisor Mr. John Kamwengu for the guidance
throughout the entire system development period.
ABSTRACT
Most carwash systems are manual which is time consuming. Hence being manual
may limit the clients who are willing to receive the services. This project proposes
the development and implementation of an advanced automated carwash
system, leveraging and cutting-edge technology to enhance efficiency and
customer sastification.

The conventional carwash involves long wait times which in this proposal system
helps the clients through the following services that the system entails that is
booking, carwash, garage, parking and café services.

To further elevation the customer, experience the system will integrate with a
user-friendly mobile application in the near future. Customers can schedule wash
appointments, track the progress in real time and receive notifications upon
completion. Payment processing will also be integrated in the system for
transactions experience. The problem of the system that it is quite expensive to
maintain, it requires literate personnel for those applying through the website
thus, to solve this they will training sessions and personnel for conducive
understanding of the system.
Thus, all related data that the carwash will access the system will be located in
accessible, secure environments and ensure they are great services. Apart from
carwash it will services such as parking, garage and café services that the system
in home and admin page will be showing the report of the daily activities held.

In summary, the automated carwash system proposal aims to revolutionize the

car- cleaning industry by introducing efficient, precision and user convivence.
Through the advanced technologies this system strives to set new standards in
the carwash experience while contributing to sustainable and eco-friendly
practices and expansion of the bus
Contents
CHAPTER ONE..............................................................................................................................................8
1.0 Introduction....................................................................................................................................8
1.1What is the problem.......................................................................................................................8
1.3 Justification of the project.........................................................................................................9
1.4 Objective of the system.........................................................................................................9
CHAPTER TWO...........................................................................................................................................11
LITERATURE REVIEW..............................................................................................................................11
2.0 Introduction.................................................................................................................................11
2.1 Problem recorded....................................................................................................................11
2.2 Solution................................................................................................................................11
CHAPTER THREE........................................................................................................................................12
METHODOLOGY.....................................................................................................................................12
3.0 Introduction.................................................................................................................................12
3.1 Requirement specifications.....................................................................................................12
3.2 System Design..........................................................................................................................13
3.3 Full system Data flow Diagram of Waypalace Carwash System...........................................13
3.4 Program Design....................................................................................................................14
3.5 System Test Plan..................................................................................................................17
3.7 System Roll Out Implementation.........................................................................................18
CHAPTER FOUR..........................................................................................................................................24
EXPECTED OUTPUTS AND IMPACTS...........................................................................................................24
4.1 EXPECTED IMPACT...........................................................................................................................25
CHAPTER FIVE............................................................................................................................................25
CONCLUSIONS AND RECOMMENDATIONS............................................................................................25
5.1 Reduction in strictness in the time deadliness.............................................................................25
5.2 Provisions of project finances to the students.........................................................................26
5.3 Compelling some institutions to pave way for the students to develop..................................26
5.4 Future Development............................................................................................................26
CHAPTER ONE
1.0 Introduction
This project WAYPALACE CARWASH SYSTEM is a solution to the real time situation
in managing the clients waiting time, in easier and convenient way. The
administrator is able to view all the client’s database. The basic structure of the
system is that it contains services that not only the carwash but also online
booking, garage, parking and café services.

1.1What is the problem

Existing system is manual that has led to;
 Wastage of time.
 Complexity of calculations.
 Calculation.
The fact that the system is manual the developer is developing an online system
that will led to tracking of vehicles in real time and more so to save time.
Exposure
Developer during research discovered that the clients and staff aren’t exposure to
the chemicals and services offered. This project will be solving the problem by
displaying all the services offered in the system website that will make it easy for
the members involved to understand whatever is required with ease.
Calculation
At the end of the day it for the better services and efficient prices for the system
activities to work effectively in the business sector. The system with solve the
issue of complex calculations since they will be an online payment to generate the
calculations and generate the receipt required after the services.
1.3 Justification of the project
Why choose the carwash system? In Kenya most carwash system are manual
where the booking happens according to the number of the vehicles that require
the services. In most cases the services offered in the carwash are the washing
services.

Thus, the system is to expand the system with more services like online booking,
garage, parking and café stalls. In conclusion, the system is easy, efficient for the
clients and work system saves on the real time.

1.4 Objective of the system

The main objective is to solve the long awaits since the system in most cases is
manual, by enhancing an online system will reduce time wastage where the
income will at large and the increase of the clients in the WAYPALACE CARWASH.

Another objective is to enhance an effective payment system that will help in

taking the database of the client’s vehicles and the services in the day to day
routine and solve the issue of complex calculations.

1.5 Scope of the project

The project scope typically is both the functional and non-functional scope
operations to meet the customer’s needs.
The function scope is:
 Admin interface
 Clients interface
 User interface
 Payment interface
 Services interface
The non-functional is:
Performance
This is the saving of tome and handling of multiple vehicles concurrently.
Reliability
The consistency of the operations working in the system.
Scalability
The ability to expand services and add new features and maintaining compliance
with environmental and safety standards.

1.6 Benefits of the system

1. Time efficiency: Due to online booking and the website is online will help in
saving time and the system to run smoothly.
2. Convenience: Available at various locations, often 24/7.
3. Environmental friendliness: Many users eco-friendly and easy for the
members to use.
4. Easier on calculation since the payments are online generated together
with the receipt.
5. Preservation: Through maintenance help to preserve the data of the system
well and secure.
6. Value retention: Keeps the vehicle looking new and preserving it resale
value and also wins the client’s urge for more services from the system.
7. Data analysis: In the data stastics will be able to range the types of client’s
vehicles, the gender data and the services offered.
8. Computerization: The system itself it’s a modern system that will align with
the day to day activities.

CHAPTER TWO
LITERATURE REVIEW
2.0 Introduction
The system was designed after a thorough investigation on carwash systems
compared to many other carwashes according to local research 98% of the them
are manually operated. Thus, enabling the work in the firm to run smoothly.

2.1 Problem recorded

After a well investigation the following problems were identified during the
research that is being conducted.
i. Time wastage since there is no online booking and online websites
among the many carwash system.
ii. Errors in the calculation.
iii. Customer wait time: Customers may experience longer waiting time
especially during the peak hours or days.
iv. Labor intensity: Manual system can lead to fatigue and reduced
productivity over time.
v. Limitations of other services.
vi. Repetition of entry of data.
vii. Maintenance of the system is costly.
2.2 Solution
The above problems were recorded and the developer came up with
a structure on how the system is going to solve the above problem.
The developer designed the WAYPALACE CARWASH SYSTEM which
will reduce the above problems when used and utilized properly.

CHAPTER THREE
METHODOLOGY
3.0 Introduction
Its important to fulfill the planning of the implementation phase. This can only be
done if proper methodology is selected. Methodology is important to make sure
the project life cycle activities are being carried without shortcuts. Methodology
helps the system developer to take one step at a time words accomplishing the
full system. The following section discusses the choice of methodology towards
the implementation of Waypalace carwash system.

3.1 Requirement specifications

This section defines the minimum hardware and software needed in order for the
system to run as intended.
Hardware requirements
The Waypalace carwash system, system requires computerized devices for the
system to run effectively and hard copy material for the staffs to understand and
have a valid information on the types of equipment and chemicals for use. And
also, for the after-sell services for the clients who support the Waypalace system.

Software requirements
The system is intended to be compatible with any browser, secure and friendly
system that will be able to access the services easily and conveniently.

3.2 System Design

This section demonstrates how data flows in the whole system. The data flow is
shown information of dataflow diagram for both programmers and non-
programmers to able to understand how the program runs theoretically through
representation in for of practical diagrams.

3.3 Full system Data flow Diagram of Waypalace Carwash System

Home Admin

Sign off Sign off

This flow chart demonstrates how data flow in the whole Waypalace system that
is for both programmers and non-programmers.

3.4 Program Design

In this sub chapter we are going to look at the flow charts drawn representing few
parts of the WAYPALACE CARWASH SYSTEM. With this representation one is able
to picture how the user will be interacting with the system.

The developer decides to present 3 different flow charts of 3 user types in the
Waypalace system which are;
 Admin page
 Client page
 Payment page
FLOW CHART OF ADMIN ACCOUNT

ADMIN

ADD

SIGN OFF
LOG IN

FLOW CHART OF USER PAGE

USER PAGE

ENTER DATA

CONFIRM IF
TRUE

PAYMENT
 FLOW CHART OF PAYMENT PAGE

PAYMENT

3.5 System Test Plan

ENTER DATA

CONFIRM IF
TRUE

DOWNLOAD
VERIFY PAYMENT RECEIPT
In this title the developer tests the system and see how it is running. The
developer tries to be sure that all modules of the system are running as it is
intended to in the actual world; that is whether the system functionality input
output recording and processing of data is running smoothly.
The developer tests the system in 3 different phases that is;
a) Unit testing
b) Module testing
c) System testing
UNIT TESTING

In this unit testing the developer tests different parts of the pages on its own
and confirms the pages that they are working correctly and confirm each page.

MODULE TESTING

The developer tests various modules in the system, the developer tests and asses
each module to ensure that it produces correct input and the user is entering the
correct input.

SYSTEM TESTING
The whole system was evaluated, verified and validated to detect whether the
system is working the way it is intended to that the input and output generated is
the way that is intended thus it passes the test ,it is observed and concluded its
working in a satisfactory manner.

3.6 Change Over Method

After a lot of consideration, the developer opts to use the direct change over way
of implementing the system. The new system is to be implemented on a
particular day and time, the developer decide that the system will be
implemented overtime and the manual system will no longer be in use.
Developer considers the method because of the cost and the direct changeover is
cheaper than the parallel method and also reduce the long and tiring que that had
been experiencing before the implementation of the new system.

3.7 System Roll Out Implementation

WAYPALACE CARWASH SYSTEM is highly secured that is only authorized by two
personnel who will be able to interact with the system database. The security OF
the system will be secured by ensuring that the user will only be redirected to
their pages and the roles.
The developer has only authorized the receptionist and admin to be able to view
the client’s information. The following measure is being put into place to ensure
confidentiality of the client’s information.
i. The will be checking the access level of the clients as they log into the
system.
ii. The system database and server will be secured with a strong password
only accessible by the system admin.
iii. The system data will be regularly backed up to ensure that any data can be
retrieved back in case of any data loss.
 3.8 User Manual
Home Page
This is the first page that the user will see after searching the name of the web
and it also contain more about WAYPALACE and the user will choose whether to
register or login.

LOGIN PAGE
On this section after registration the client will be redirected to the login page
where it is the main page. It contains selection of the user type that is Admin and
Receptionist .The last part is inserting their credentials and they will be redirected
to the pages respectively if the password is incorrect the receptionist will be able
to access the system
CLIENT PAGE WHEN LOGGED IN
ABOUT CLIENT PAGE WHEN YOU PROCEED TO PAYMENT
ABOUT CLIENT PAGE WHEN A RECEIPT IS DOWNLOADED
 CHAPTER FOUR
EXPECTED OUTPUTS AND IMPACTS
4.0 Expected Results
These requirements are those that enable the system to operate. These
requirements focus mainly on what the system should do. They include:
 Users have to signup to gain access to the system services.
 Users on the home page should be able to see services offered by the
Waypalace system.
 Administrator can be able to reach the database.
 Admin is the only person capable of adding a client.
 Users authentication is by the use of passwords.
The system has only one database, the Admin is the super administrator
and has more privileges than the other users.
 The system is expected to accept 3 user types that is:
i. Administrator
ii. Client
iii. Receptionist
iv. Local user (It’s not a must for him/her to sign in)
 The categories of users allowed to access the data in the system.
The categories of users allowed to access the data in the system
 Administrator
The super admin is responsible for making changes to the database while the
other members are only allowed to perform other services.

4.1 EXPECTED IMPACT

WAYPALACE CARWASH SYSTEM will bring great impact. These impacts are;
 a) The system should be able to save a lot of time compared to the manual
system.
b) Privacy and confidentiality: client’s data will be more secure than the
manual system.
c) Paperwork: it is thrown away since when the receipt is downloaded it can
be sent in form of a pdf to the use.
d) Documentation: The system will be documented and pdf manuals will be
available for users when the system goes live.
e) Recover-ability: The system will be regularly backed up so that it can be
recovered in case data is lost for some reason.
f) Design constraints: The software will be developed with the (my sql
workbench 8.0) database back end.
g) The system will only allow the super admin to change data on the database
and not any other user.

CHAPTER FIVE
CONCLUSIONS AND RECOMMENDATIONS
5.0 Recommendations.
In order to reverse the risk and the problems involved in the project and realized
improvements in succeeding development, l would like to make the following
recommendations.
5.1 Reduction in strictness in the time deadliness.
Since some of the issues in this system cover new concept l would recommend
that the students to be allowed to begin the project development at a quite early
time to build up on their ideas and to complete early and meet the set deadlines
by the requirements.
5.2 Provisions of project finances to the students.
Due to the fact that some of the students are unable to meet the required data
and requirements capture l would recommend that some special finances be
provided to act as the support for the students who have fees difficulties in the
developments and research process.
 5.3 Compelling some institutions to pave way for the students to develop.
Some institutions have been a major bottleneck in the developments of the
project and high level institutes should compel them to release and loosen the
restrictions they have over their intellectual property such as API (Application
Programming Interface)

5.4 Future Development

I would like to say that Waypalace carwash system didn’t capture everything that
would be required and therefore, recommend for future improvements on the
following;
 A feature to allow the admin to message clients within the system.
 A feature to enable clients give feedback and suggestions.
 A system to introduce robotics works to reduce manual works among the
members.

5.5 Conclusion
It is clear that the existing system it’s a manual system. This system is a bit
expensive to the clients compared to the manual system.

The problem associated with current system will be addressed with the new
proposed system. The whole design of the proposed system is a clear automation
of the current system at WAYPALACE CARWASH SYSTEM, where the problems
associated with the manual system are well addressed by the design. And the
system also has a developed graphical user interface. Despite, of the few
challenges in the implementation process.
Taking this project all through have been a wonderful experience for me and for
practical knowledge that l acquired, this would not have materialized. This is a
very important part of my course and has helped me to understand the concept
behind a number of web scripting language as well as familiarize the market
expectations of the course at large.

APPENDIX 1
Cost and Material estimates
ITEM QUANTITY
Internet Research 1GB@20 50 HOURS 1000
Printing 50 PAGES @15 2 COPIES 1500
Binding 50 PER DAY 100
Burning disk 50 50
Token to tutor 1 1000
TOTAL 3650

APPENDIX 2
COST LISTINGS
Home Page
<html>

<head>
<title>WAYPALACE CARWASH PROJECT PROPOSAL</title>
<link rel="stylesheet" href="home.css">
<link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/font-
awesome/4.7.0/css/font-awesome.min.css">
</head>

<body>
<div class="menu-bar">
<ul>
 <li class="active"><a href="#"><i class="fa fa-
home"></i>Home</a></li>
<li><a href="#"><i class="fa fa-user"></i>About us</a>
<div class="sub-menu-1">
<ul>
<li><a href="#">Mission</a></li>
<li><a href="#">vision</a></li>
<li><a href="#">Team</a></li>
</ul>
</div>
</li>
<li><a href="#"><i class="fa fa-clone"></i>Autoservices</a>
<div class="sub-menu-1">
<ul>
<li><a href="#">Carwash</a></li>
<li class="hover-me"><a href="#">Parking</a><i class="fa
fa-angle-right"></i>
<div class="sub-menu-2">
<ul>
<li><a href="#">Ticket insurance</a>
<li><a href="#">Vehicle parking</a>
</ul>
</div>
</li>
<li class="hover-me"><a href="#">Garage</a><i class="fa
fa-angle-right"></i>
<div class="sub-menu-2">
<ul>
<li><a href="#">Repairs</a>
</ul>
</div>
</li>
<li><a href="#">cafe stalls</a></li>
<li class="hover me"><a href="#">Playzone</a><i
class="fa fa-angle-right"></i>
<div class="sub-menu-2">
<ul>
<li><a href="#">Gaming</a>
<li><a href="#">Playground</a>
<li><a href="#">Pool</a>
</ul>
</div>
</li>
</ul>
</div>
 </li>
<li><a href="#"><i class="fa fa-users"></i>clients</a></li>
<li><a href="#"><i class="fa fa-inr"></i>Pricing</a></li>
<li><a href="#"><i class="fa fa-phone"></i>Contacts</a></li>
</ul>
</div>
</body>

</html>

Login page
<?php
session_start();

// Set the timezone

date_default_timezone_set('Africa/Nairobi');

// Include the database connection

include '../php/connect.php';

// Check if the request method is POST

if ($_SERVER["REQUEST_METHOD"] == "POST") {
// Get the email and password from the POST data
$email = $_POST['email'];
$pass = $_POST['pass'];

// Check if the user exists in the users table

$sql = "SELECT nationalID, userType, pass FROM users WHERE email = ?";
$stmt = $connection->prepare($sql);
if (!$stmt) {
die("Error in SQL query: " . $connection->error);
}
$stmt->bind_param("s", $email);
$stmt->execute();
$result = $stmt->get_result();

if ($result->num_rows == 1) {
// User exists in users table
$user = $result->fetch_assoc();

// Verify password
if (password_verify($pass, $user['pass'])) {
 // Password is correct
$nationalID = $user['nationalID'];
$usertype = $user['userType'];

// Save login attempt to logs table

saveToLogs($connection, $email, $nationalID, $usertype);

// Store user session data

$_SESSION['email'] = $email;
$_SESSION['nationalID'] = $nationalID;
$_SESSION['usertype'] = $usertype;

// Redirect based on user type

redirectToPage($usertype);
}
} else {
// Check if the user exists in the enroll table
$sql = "SELECT nationalID FROM enroll WHERE email = ?";
$stmt = $connection->prepare($sql);
if (!$stmt) {
die("Error in SQL query: " . $connection->error);
}
$stmt->bind_param("s", $email);
$stmt->execute();
$result = $stmt->get_result();

if ($result->num_rows == 1) {
// User exists in enroll table
$user = $result->fetch_assoc();
$nationalID = $user['nationalID'];

// Save login attempt to logs table

saveToLogs($connection, $email, $nationalID, 'client');

// Store user session data

$_SESSION['email'] = $email;
$_SESSION['nationalID'] = $nationalID;
$_SESSION['usertype'] = 'client';

// Redirect to the client page

redirectToPage('client');
} else {
// User not found
redirectToErrorPage("Invalid credentials");
}
 }
}

// Function to save login attempt to logs table

function saveToLogs($connection, $email, $nationalID, $usertype) {
$login_time = date('Y-m-d H:i:s');
$login_date = date('Y-m-d');

$sql = "INSERT INTO logs (nationalID, email, login_time, login_date,

usertype) VALUES (?, ?, ?, ?, ?)";
$stmt = $connection->prepare($sql);
if (!$stmt) {
die("Error in SQL query: " . $connection->error);
}
$stmt->bind_param("sssss", $nationalID, $email, $login_time, $login_date,
$usertype);
$stmt->execute();
$stmt->close();
}

// Function to redirect to appropriate page based on user type

function redirectToPage($usertype) {
switch ($usertype) {
case 'Admin':
header("Location: ../html/admin.php");
break;
case 'Receptionist':
header("Location: ../html/receptionist.php");
break;
case 'client':
header("Location: ../html/clientpage.php");
break;
default:
// Redirect to error page for unknown user types

header("Location: ../html/clientpage.php");
break;
}
exit();
}

// Function to redirect to error page with specified error message

function redirectToErrorPage($error) {
header("Location: ../html/error.php?error=" . urlencode($error));
exit();
}

// Close the database connection

$connection->close();

User Registration
<?php
$servername = "localhost";
$username = "root";
$password = "@Jedidah1";
$database = "carwash";

// Create connection
$conn = new mysqli($servername, $username, $password, $database);

// Check connection
if ($conn->connect_error) {
die("Connection failed: " . $conn->connect_error);
}

// Check if form data is submitted

if ($_SERVER["REQUEST_METHOD"] == "POST") {
$fname = $_POST['fname'];
$mname = $_POST['mname'];
$lname = $_POST['lname'];
$nationalID = $_POST['nationalID'];
$p_no = $_POST['p_no'];
$usertype = $_POST['usertype'];
$email = $_POST['email'];
$pass = $_POST['pass'];

//Password Encryption
$hashed_password = password_hash($pass, PASSWORD_DEFAULT);

$sql = "INSERT INTO users (fname, mname, lname, nationalID, p_no, usertype,
email, pass) VALUES (?, ?, ?, ?, ?, ?, ?, ?)";

//Checking Whether user is registered

$check_duplicate = "SELECT * FROM users WHERE email = ? OR nationalID = ?";
$stmt_check = $conn->prepare($check_duplicate);
$stmt_check->bind_param("ss", $email, $nationalID);
$stmt_check->execute();
$result = $stmt_check->get_result();
 if ($result->num_rows > 0) {
echo "<div id='overlay' style='position: fixed; top: 0; left: 0; width:
100%; height: 100%; background-color: rgba(0,0,0,0.5); z-index: 999; display:
flex; justify-content: center; align-items: center;'>
<div style='background-color: white; padding: 20px; border-radius: 10px;
text-align: center;'>
<h2 style='color: red;'>National ID and Email Already Registered !
</h2>
<button class='login100-form-bgbtn' style='color: white; width:
100px; height: 30px; font-weight: bolder; border-radius: 30px; border: none;
cursor: pointer; background: #a64bf4; background: -o-linear-gradient(right,
#21d4fd, #b721ff, #21d4fd, #b721ff); background: -moz-linear-gradient(right,
#21d4fd, #b721ff, #21d4fd, #b721ff); background: linear-gradient(right, #21d4fd,
#b721ff, #21d4fd, #b721ff);'onclick=\"window.location.href =
'../html/adduser.php';\">OK</button>
</div>
</div>";
exit;
}

// Prepare and bind parameters

$stmt = $conn->prepare($sql);
if ($stmt === false) {
die("Error: " . $conn->error);
}

$stmt->bind_param("ssssssss", $fname, $mname, $lname, $nationalID, $p_no,

$usertype, $email, $hashed_password);

// Execute the statement

if ($stmt->execute()) {
echo "<div id='overlay' style='position: fixed; top: 0; left: 0; width:
100%; height: 100%; background-color: rgba(0,0,0,0.5); z-index: 999; display:
flex; justify-content: center; align-items: center;'>
<div style='background-color: white; padding: 20px; border-radius: 10px;
text-align: center;'>
<h2 style='color: green;'>User Registered Successfully</h2>
<button class='login100-form-bgbtn' style='color: white; width:
100px; height: 30px; font-weight: bolder; border-radius: 30px; border: none;
cursor: pointer; background: #a64bf4; background: -o-linear-gradient(right,
#21d4fd, #b721ff, #21d4fd, #b721ff); background: -moz-linear-gradient(right,
#21d4fd, #b721ff, #21d4fd, #b721ff); background: linear-gradient(right, #21d4fd,
#b721ff, #21d4fd, #b721ff);'onclick=\"window.location.href =
'../html/admin.php';\">OK</button>
 </div>
</div>";
} else {
echo "Error: " . $stmt->error;
}

$stmt->close();
$stmt_check->close();
} else {
echo "Form submission error!";
}

// Close connection
$conn->close();
?>

APPENDIX 4
References
 A friend full of stack development
 Online research tutorial point and java point