Carwash Management System

UNIVERSITY OF TOURISM TECHNOLOGY AND BUSINESS STUDIES
P.O. Box 350, Kigali - Rwanda

Tel: +250-788 306692, +250-788306203
Email: info@utb.ac.rw
www.utb.ac.rw
FACULITY OF APPLIED SCIENCES AND TECHNOLOGY
DEPARTEMENT OF BUSINESS INFORMATION TECHNOLOGY
RESEARCH TITLE:
CAR WASH MANAGEMENT INFORMATION SYSTEM
Case study: CAR WASH KICUKIRO
Submitted by: Francine MUKABAYIZERE
Registration Number: 01602/12
Under the guidance and Supervision of Mr. KUNDAN Kumar
A Dissertation submitted to:
The Department of Business Information Technology in partial fulfillment of the

requirement for the award of Bachelor‟s Degree in Business Information Technology
Year of submission: 2017

DECLARATION
I, MUKABAYIZERE Francine declare that the content of this final project entitled “CAR
WASH MANAGEMENT INFORMATION SYSTEM “is my original work intended to serve
as part of the fulfillment of the requirements for the award of a Bachelor degree in Business
Information Technology. I hereby confirm that to the best of my knowledge, this work is original
and has never been presented elsewhere for any academic qualification. I also declare that it has
not been previously and concurrently submitted for any other degree or award at University of
Tourism Technology and Business Studies. Any contribution made to the research by others is
explicitly acknowledged in the report
Name of Student: MUKABAYIZERE Francine
Kigali on, /…. / 2016
Signature of Student …………………………..
i
APPROVAL
This is to certify that the Project work entitled “CAR WASH MANAGEMENT
INFORMATION SYSTEM” Submitted by MUKABAYIZERE Francine, University of
Tourism Technology and Business Studies, in partial fulfillment of the requirement for the award
of the degree in Business Information Technology is a record of work carried out by her under
my guidance.
Supervisor: KUNDAN Kumar
Signature …………………………..
Kigali on, …. /…. / 2016
ii
DEDICATION
This research is dedicated
To Almighty God,
To my beloved Family,
To my Brothers and Sisters,
To all my Friends and Colleagues at UTB,
iii
ACKNOWLEDGEMENT
First and for most I would like to express my deepest gratitude to almighty God for his constant
love, care and companionship. Grateful acknowledgement is made to the following persons and
organizations for their contribution to the success of this work.
My special recognition goes to Dr. MBANZABUGABO Jean Baptiste the head of BIT
department and all academic staff specifically BIT department Lecturers for their kindness,
commitment and good manners provided to us an open environment allowing our learning to be
well-organized and successful.
I express my sincere gratitude to KUNDAN Kumar and Madame Lucy CHEP for having
accepted to supervise this project despite their enormous responsibilities. Their guidance and a
great and valuable of support they provided to me contributed to the successful completion of
this work.
My sincere gratitude goes to the staff of KICUKIRO CAR WASH for having co-operated with
me and provided me needed information to the achievement of goals of this work.
I once again expand my gratitude to my beloved family and friends for their contribution to my
studies and for having taken care of what I could not take care of during the past four years due
to my studies
Lastly but not least, many thanks to all friends who have contributed economically, socially and
morally to this achievement and that are not listed individually. Your contribution was highly
appreciated.
May the Almighty God bless you all!!!
MUKABAYIZERE Francine
iv
LIST OF ABBREVIATIONS
CSS: Cascading Style Sheets
DB: Database
DBMS: Database management system
ERD: Entity Relationship Diagram
GUI: Graphic User Interface
HTML: Hyper Text Markup Language
ICA: International Carwash Association

ICT: Information Communication Technology
IT: Information Technology
MIS: Management information system
PHP: Hypertext preprocessor
RDBMS: Relational Database Management System

SDLC: Software Development life cycle
SDM: Software Development Methodology

SQL: Structured Query Language
SQL: Structured Query Language

UTB: University of Tourism, Technology and Business Studies
WAMP: Window Apache MySQL PHP

WWW: World Wide Web
XML: Extensible Markup Language
v
Table of Contents
DECLARATION ............................................................................................................................. i
APPROVAL ................................................................................................................................... ii
DEDICATION ............................................................................................................................... iii
ACKNOWLEDGEMENT ............................................................................................................. iv
LIST OF ABBREVIATIONS ......................................................................................................... v
ABSTRACT .................................................................................................................................. xii
CHAP 1: INTRODUCTION AND BACKGROUND TO THE STUDY ...................................... 1
1.0 Introduction ...................................................................................................................... 1
1.1 BACKGROUND TO THE STUDY ..................................................................................... 1
1.2 PROBLEM STATEMENT ................................................................................................. 2
1.3 Objective of the study ........................................................................................................... 3
1.3. 1 General objective............................................................................................................... 3
1.3.2 Specific objectives.............................................................................................................. 3
1.4 Research questions ................................................................................................................ 3
1.5 Significance of the study ....................................................................................................... 3
1.5.1 Personal interest ................................................................................................................. 3
1.5.2 To Kicukiro car wash ......................................................................................................... 3
1.5.3 Social interest ..................................................................................................................... 4
1.6 Scope of study ....................................................................................................................... 4
1.6.1 Geographical scope......................................................................................................... 4
1.6.2 Time scope ......................................................................................................................... 4
1.6.3 Content scope ..................................................................................................................... 4
1.7 Limitation .............................................................................................................................. 4
1.8 Platform ................................................................................................................................. 5
vi
1.8.1 Hardware requirement ........................................................................................................ 5
CHAPTER TWO: REVIEW OF THE RELATED LITERATURE ............................................... 6
2.0 Introduction ........................................................................................................................... 6
2.1 Definition of key terms and concept ..................................................................................... 6
2.2 Management System ............................................................................................................. 6
2.2.1 Purpose and benefits of a management system .................................................................. 7
2.3 Information technology (IT).................................................................................................. 7
2.4 Information system ................................................................................................................ 7
2.5 Data ....................................................................................................................................... 8
2.6 Database management system ............................................................................................... 8
2.8 Related literature................................................................................................................ 8
Summary ......................................................................................................................................... 9
CHAPTER THREE: RESEARCH METHODOLOGY ............................................................... 10
3.1 Research Design .................................................................................................................. 10
3.2 Population and Selection of the Sample .......................................................................... 10
3.2.1 Population ..................................................................................................................... 10
3.2.2 Selection of the sample ................................................................................................. 11
3.2.3 Tools for data collection/ Instrumentation.................................................................... 12
3.3 Collection of data ................................................................................................................ 13
3.4 Analysis of data ................................................................................................................... 13
3.5 Validity and Reliability ....................................................................................................... 13
3.5.1 Reliability ..................................................................................................................... 13
3.5.2 Validity. ........................................................................................................................ 14
3.6 Ethical Considerations......................................................................................................... 15
CHAPTER FOUR: SYSTEM ANALYSIS AND DESIGN ......................................................... 16
vii
4.0 Introduction ......................................................................................................................... 16
4.1 Data analysis and presentation ............................................................................................ 16
4.1.1 Analysis result of 12 questionnaires for customers ...................................................... 16
4.1. 2 analysis result of 25 questionnaires for Employees..................................................... 21
4.2 Interpretation of findings/results ......................................................................................... 24
Summary ....................................................................................................................................... 25
4.3 Description of the existing system ...................................................................................... 25
4.3.1 Weaknesses of the existing system ............................................................................... 26
4.3.2 Strengths of the existing system ................................................................................... 26
4. 4 Description of the proposed system ................................................................................... 26
4.4.1 Advantages of the new system ................................................................................ 27
4.4.2 Modules of the new system .......................................................................................... 27
4.4.3 System Configuration and Technology (platform) ....................................................... 28
4.5 Illustration of New system ............................................................................................. 29
4.5.1 Software/System Development Model ......................................................................... 29
4.5.2 Data Flow Diagram ...................................................................................................... 31
4.5.3Use Case Diagram ......................................................................................................... 34
4.5.4 Normalization ............................................................................................................... 35
4.5.4.1 Data Normalization Rules ............................................................................................. 36
4.5.5 Database System ........................................................................................................... 38
4.5.6 Entity Relationship Diagram ........................................................................................ 42
4.5.7 Entity Relation Diagram of the carwash management information system ................. 44
4.6 Architecture design of the new System ........................................................................... 45
CHAPTER FIVE: IMPLEMENTATION, CODING AND TESTING ........................................ 46
5.1 Implementation and coding ................................................................................................. 46
viii
5.1.1 Introduction .................................................................................................................. 46
5.1.2 Description of implementation Tools and technology ................................................. 46
5.1.3 Screen Shots and Source Codes.................................................................................... 48
5.2Testing .................................................................................................................................. 65
5.2.1Introduction ................................................................................................................... 66
5.2.2 Objective of Testing ................................................................................................ 66
5.2.3 Unit testing outputs ....................................................................................................... 66
5.2.4 Validation Testing outputs......................................................................................... 66
5.2.5 Integration Testing Outputs .......................................................................................... 67
5.2.6 Functional and system testing Results .......................................................................... 67
5.2.7 Acceptance Testing Reports ......................................................................................... 68
Conclusions and recommendations ........................................................................................... 68
6.0 Introduction .................................................................................................................. 68
6.1.Conclusion (s) .................................................................................................................... 69
6.2 Recommendations ............................................................................................................... 69
6.3 Future Researchers ........................................................................................................... 69
REFERENCE ................................................................................................................................ 70
APPENDICES .............................................................................................................................. 73
ix
LIST OF TABLE
Table 1: Population and sample .................................................................................................... 12

Table 2 Respondent‟s Demographic Data Classified by Gender .................................................. 16
Table 3 Respondents‟ Demographic Data Classified by Age ....................................................... 17
Table 4 Respondents‟ Demographic Data Classified by Marital Status ....................................... 17
Table 5 Respondents‟ Demographic Data Classified by Education ............................................. 17
Table 6 Respondents‟ Demographic Data Classified by nationality ............................................ 18
Table 7 Respondent‟s Using Car Wash Service Behavior Pattern Classified by Frequency in
Using Car Wash Service ............................................................................................................... 18
Table 8 Respondents‟ Using Car Wash Service Behavior Pattern Classified by their appreciation
on using Kicukiro Car Wash Service ............................................................................................ 19
Table 9 Respondents‟ Using Car Wash Service Behavior Pattern Classified by fairness of the
price............................................................................................................................................... 19
Table 10 Respondents‟ Using Car Wash Service Behavior Pattern Classified by their choice
about the car wash ......................................................................................................................... 20
Table 11 Respondents „using Car Wash Service Behavior Pattern Classified by their views about
using a computerized system. ....................................................................................................... 20
Table 12 Respondents‟ Using Car Wash Service Behavior Pattern Classified by Expectation
from Using Car Wash Service ...................................................................................................... 21
Table 13 Frequency table .............................................................................................................. 21
Table 14 Gender of respondents ................................................................................................... 22
Table 15 Age of respondents ........................................................................................................ 22
Table 16 Education backgrounds of respondents ......................................................................... 22
Table 17 Nationality .................................................................................................................... 23
Table 18 Marital status................................................................................................................. 23
Table 19 Working experience ....................................................................................................... 23
Table 20 Time of service delivery ............................................................................................... 24
Table 21 View of respondents about using a computerized system ............................................. 24
Table 22: Normalization rules ...................................................................................................... 36
x
LIST OF FIGURES
Figure 1: Waterfall model ............................................................................................................. 30

Figure 2: Context diagram or level 0 ............................................................................................ 33
Figure 3: DFD level 1 for the manager ......................................................................................... 33
Figure 4: DFD level 1 for the customer ........................................................................................ 34
Figure 5: DFD Level 2 of proposed system .................................................................................. 34
Figure 6Use case diagram ............................................................................................................. 35
Figure 7: ERD ............................................................................................................................... 44
Figure 8: Database of the proposed system ................................................................................. 45
Figure 9: Login interface of Car wash MIS .................................................................................. 48
Figure 10: Print bill ....................................................................................................................... 53
Figure 11: Fee payment form ........................................................................................................ 58
Figure 12: Add new customer ....................................................................................................... 67
Figure 13: Customer registration .................................................................................................. 68
xi
ABSTRACT
Kicukiro car wash is facing a problem of poor management and the sharing of information with
its customers. All activities and services advancement reports in KICUKIRO CAR WASH are
done manually; and this causes a waste of time and outperformance of the car wash. The
purpose of this work is to design and implement a web based application which will help this car
wash to manage all problems relating to the communication between customers, employees and
car wash staff. This application offers the ability of communicating with customers and car wash
management quickly. It also offers the owner of car wash the ability to view all activity processes
done by managers on daily basis through bill reports. For the development of this project two
methodologies will be used: the research methodology and the software engineering
methodology. Research methodology consists of interviewing and reviewing and the literature
necessary to carry out this study. The population of this study is 60 including 40 employees of the
carwash and 20 customers. Employees are many compared to customers because most of time
customers are used to leave their car to the car wash to pick them back when they have been
cleaned, this was the main challenge to the researcher because to find customers present to the
car wash was not easy. A waterfall model in software development will be used to develop this
application and with this model, the whole process of software development is divided into
separate process phases and those phases are developed one after another. After the
implementation of this application called Car wash Management Information System, will be
tested and verified to check if it can solve a lot of problems faced by KICUKIRO CAR WASH
relating to the manual system.
Key Words: car wash, sms notification, report
xii
CHAP 1: INTRODUCTION AND BACKGROUND TO THE STUDY
1.0 Introduction
This chapter provides an overview and basic information on the whole project, a detailed
description of the study and the methodology used to achieve goals are presented in order to
present the scene of the study. It has been divided into different sections such as the background
to the study where researcher describes the details of KICUKIRO CAR WASH, problem
statement where is shown the whole problem, objectives of the study, research questions, scope
of the study, significance of the study and the platform with the system configuration.
In many institutions in Africa and particularly in Rwanda, there is a lack of well-designed
computerized systems that could offer better services to people.
With the proliferation of Information technology in all aspects of our life, computer application
becomes more useful to provide efficiency and effectiveness to meet the objective. The
researcher tend to develop an application which is being used for delivering service and sharing
content, communication between customers, workers and outside the world, creation and
delivery of presentations and offers, research, administrative support and customer record to
improve the carwash working environment.
1.1 BACKGROUND TO THE STUDY

KICUKIRO CAR WASH is a private company which is located in KICUKIRO District,
KICUKIRO Sector in KICUKIRO Cell opposite side of IPRC Kigali in 40 meters from
Sonatube.
This car wash has started working in 2000 with 15 workers known as washers and it keeps on
improving whereby currently they have 38 workers and 2 managers one for the morning shift
and another for the evening shift and both of them are the ones to coordinate all activities of the
company and manages employees in order to achieve company objectives.
Commercial vehicle washes presents a two-opportunity for the water conservation based both
upon differences in construction and upon operator preferences. Commercial carwashes are
categorized as either convey, in-bay automatic or self-serve, and includes those carwashes that
are available for public use at stand-alone facilities where we locate hand carwash. This was
confirmed by John Koeller (October, 2006).
1
Hand car wash system usually washes cars by using water and soap. For Kicukiro carwash, their
daily activity and all activities and information are managed manually. The communication
between customers and employees in car wash is not effective because customers are not notified
when their car are ready to be delivered. The reason why the researcher has thought of
establishing an automated information management system which will help managers to
communicate with their customers and inform employees about their daily concern activities and
assign duties accordingly. This adds more advantages comparing to manual system as the car
wash will easily communicate with its customers and improve performance.
1.2 PROBLEM STATEMENT

The hand car wash its department of giving service to customers is still using a manual system to
manage information of car wash business. Due to a large number of customers nowadays, this
department faces numerous problems when capturing, storing, securing, and retrieving
information related to car wash business and to communicate to customers seem to be a big
challenge.
When a customer comes to the car wash, the negotiation is made between the car‟s owner and
the preferred washer and this takes time because each and every one wants to be selected. The
way of recording received customers is currently made by recording customers using a pen and a
note book; this is a manual operation which can generate a loss of information easily. One
employee can have more than one car while others haven‟t any and this seems to be inefficient
among employees and can cause their customers to wait for long. Because washers are the one
to make negotiation with customers, they sometimes look at their interest where they can provide
poor service to customers for them to gain more per day this can cause the customer to do not be
back to the same carwash because the service was not attractive.
The payment of fees is not done effectively because customers pay washers then the washers will
pay on their own the manager based on the car model washed and the service provided because
they can either provide exterior wash or internal wash . This must be a problem when the
manager is distracted and do not be aware of all washers information.
2
1.3 Objective of the study
1.3. 1 General objective
The main objective of this project is developing and implementing a software application which
will manage the customer as well as employee profiles, and keep track of wash record of each
customer as well as to support and simplify the process of communication and information
sharing in Kicukiro car wash.
1.3.2 Specific objectives
i. To develop an application that will allow distributing and sharing of information of the
car wash by notifying customers to come and take their car as quick as possible.
ii. To develop an application that manages the records of car wash activities
iii. To generate report
1.4 Research questions
a. How the system will notify customer about the delivery of the car?
b. Which system will be able to manage the car wash activity records?
c. How the system will generate report?
1.5 Significance of the study
1.5.1 Personal interest

This project will help the researcher to apply the knowledge acquired during academic study into
practice and to improve knowledge and skills.
The study will also be helpful to the researcher to fulfill academic requirements for getting award
of Bachelor‟s degree in business information technology.
1.5.2 To Kicukiro car wash
This project will help the company through to increase quick communication between the
administration and customers, whereby customers will be able to have current information and
read get better services. This project will help Kicukiro car wash customers to minimize time
consuming for requested services, and promoting the use of information Technology in the
country.
3
1.5.3 Social interest
This project will be a guideline for other researchers and it will become one of the books in UTB
library. In additional, the result of this research will be benefit for companies, investors or
entrepreneurs who are interested in establishing car wash business in Rwanda.
1.6 Scope of study

This scope was limited to the creation and development of the proposed application software.
This software works as a standalone system and helps the car wash employees and customers to
communicate and manage their data.
1.6.1 Geographical scope

Due to the limited time and financial means, the study will be conducted in KICUKIRO Car
Wash Company located in Rwanda, Kigali City, Kicukiro District.
1.6.2 Time scope
This research started by May 2016 and end with submission of the final report of this research in
December 2016.
1.6.3 Content scope
The application will base on the communication in between the car wash administrations,
employees and customers; how is it possible to share information and better management of the
car wash.
1.7 Limitation
Within data collection, one obstacles which may occurs during this process is unavailability of
persons involves in giving required information which may cause delay in completion of this
project on time but this will be overcame by consulting the car wash many times so that
information can be more reliable.
4
1.8 Platform
1.8.1 Hardware requirement
Processor: Windows 7 and above
RAM capacity: 4GB
Storage capacity: 500 GB
Drives: 52xCD drive
1.8.2 Software requirement
Operating system: client operating system
Front End: PHP
Back End: MySQL
Web server: Apache 5.0
Scripting language: HTML, Java script
Tools: Notepad++
5
CHAPTER TWO: REVIEW OF THE RELATED LITERATURE
2.0 Introduction
This chapter provides the literature review that is related to the project development and is
intended to provide a brief description about technical terms and concepts that are being used
during development of the project .It reviews about the existence of others systems. The sources
are merely taken from books, articles, journals and also sources from internet.
2.1 Definition of key terms and concept
1. Self-service Wash: A wash where the customer performs all the labor.
Generally, the customer drives into a bay and washes the car by means of high pressure hose and
a foaming brush (“Car wash glossary”, n.d).
2. Full-service Wash: A conveyorized or tunnel wash that provides a complete wash,
vacuuming and drying, usually by hand (“Car wash glossary”, n.d).
3. Exterior wash: Car wash service that includes only a cleaning of the outside of the car. Often
this refers to a traditional style where customers are greeted by a person, where no detailing
services are offered.
4. Flex service washing: Is the combination of Express Exterior and Full Service, attracting a
broad customer base due to range of pricing. Typically customers stay in the car during the wash.
Express customers directly exit the wash, whereas full service customers pull into an aftercare
area, exit the vehicle, and wait while attendants vacuum the car, clean the windows, and perform
any other service.
5. ICA - International Carwash Association: Industry association that supports its members
and promotes the professional car care industry by collecting and disseminating information.
2.2 Management System

One definition of management is „the guidance and control of action‟ and a system is defined as
a „set of components interconnected for a purpose‟. So you could argue that a management
system is a „set of components interconnected for the guidance and control of action‟. This
suggests that the interconnection has been planned for a reason, and that the purpose would not
be achieved without the interconnection. In other words, the separate components would not
independently achieve the same result by Richmond, B. (1994).
6
In some small organizations, there may not be an official system, just “our way of doing things,”
this is mostly kept in the heads of the staff. But the larger the organization, the more likely that
procedures need to be recorded to ensure everyone is clear on who does what. This process of
systemizing how things are done is known as a management system
Over the year, computer systems have became more established and sophisticated (account and
payroll were among the first functions affected), and the automation of many parts of relevant
processes has introduced an automatic control over many of the tasks. (Senge, Peter, 1990)
2.2.1 Purpose and benefits of a management system

A management system should be a mean to:
 Achieve business objectives
 Increase understanding of current operations and the likely impact of change
 Communicate knowledge
 Demonstrate compliance(with the requirements of the Turnbull report, S arbanes-
Oxley, sector-specific and international standards etc)
 Establish best practice
 Ensure consistency
 Set priorities
 Change behavior
2.3 Information technology (IT)
(Wainrght.et al.1993,)define information technology as a broad one encompassing all forms of
technologies involved in capturing, manipulating, communicating and using data i.e. data
transformed into information.
(Henry C. Lucas .2001, p.11) stated that information technology refers to all forms of technology
applied to processing, storing and transmitting information in electronic form.
2.4 Information system
Information system (IS) is the study of complementary networks of hardware and software that
people and organizations use to collect, filters, and process, create and distribute data.
Some authors make a clear distinction between information systems, computer systems and
business processes. Information system typically include ICT component but are not purely
7
concerned with ICT, focusing instead on the end use of information technology. Shaikh IS1060
2013
Information systems are also different from business process. Information systems help to
control the performance of business process. (Lindsay, John (2000). Information Systems
fundamentals and Issues. Kingston University, School of Information Systems)
2.5 Data
Data refers to the raw facts including numbers, words that are processed on a computer and later
transformed into structured ordered information quoted.
In computing, data is information that has been translated into a form that is more convenient to
move or process.
2.6 Database management system
A database management system (DBMS) is a collection of programs that enables you to store,
modify, and extract information from a database.
2.7 MANAGEMENT INFORMATION SYSTEMS (MIS)
A management information system is an information system that uses the data collected by the
transaction processing system and uses this data to create reports in a way that managers can use
it to make routine business decisions in response to problems. Some of the reports that this
information system creates are summary, exception and ad hoc reports. All this is done to
increase the efficiency of managerial activity (New Jersey, 2004)
MIS can be defined as “A system to convert data from internal and external sources into
information and to communicate that information, in an appropriate form, to managers at all
levels in all functions to enable them to make timely and effective decisions for planning,
directing and controlling the activities for which they are responsible”
2.8 Related literature

Jahangir (2005) states that based on the significant role that information plays in choice of
decision to be made, organizations must ensure that they have a good management information
system. As a notable general observation, a good MIS ensures good decision making just in the
same way bad MIS propel the making of bad decisions.UStudy.in (2010) supports the above
observation by saying that “The quality of managerial decision-making depends directly on the
8
quality of available information” and the managers should therefore cultivate an environment
that encourages the growth and viable sprouting of quality information. Essentially, before
deciding on which MIS strategy to use, it is vital to ensure that the choice made is fully
compatible with your current system. This will not only help in avoiding erratic choices but it
will also save you the time and money that would have been otherwise wasted by that person
(Rhodes, 2010; Jahangir, 2005). In addition to that, it is not worthy for the MIS strategy or tool
used to be in line with the decisions that are to be made. In other words, there should be a
connecting point between the decision to be made and the MIS to be used by individual or
corporate business owners (Jarboe, 2005). As a key consideration, Management Information
Systems is a highly complex and delicate arena that calls a lot of caution to be taken by its
managers. It is for this reason that it is recommendable for organizations to ensure that they
carefully select the individuals who are placed to control the systems. The more cautious and
professional a person is, the better the person gets an assurance of positive prospects of in MIS
with regards to decision making and other related areas of business (Lingham, 2006).
Bee, R.,Bee, F., 1999. Managing information and statistic. Trowbridge: Cromwell Press. Lucy,
T., 1997. Management Information System. London.
Summary
A management system aimed at smooth functioning through standard practices. It will generally
include detailed information on topics such as organizing the car wash company setting and
implementing corporate policies, establishing accounting, monitoring and quality control
procedures.
9
CHAPTER THREE: RESEARCH METHODOLOGY
3.0 Introduction
In order to examine the need of using information technology in car wash service in Kigali, a
study is designed to be a descriptive case research design using qualitative and quantitative
research techniques to collect data from the car owners who are frequently consuming
KICUKIRO Car wash services and live in Kigali, and employees who serve them. The
researcher analyzes data variables using percentage, frequency, and SPSS to analyze data and
answer research questions.
The purpose of this study is to develop application software that will improve the good working
environment in carwash industry by supporting the management and communication in car wash
sector.
3.1 Research Design

This study will employ a descriptive case research design using qualitative and
quantitative research techniques. This research design has been selected because it is
difficult for the researcher in this kind of study to manipulate the independent variables.
Rather, the variables will be taken as they occur in their natural setting.
Descriptive research is particularly in social and educational context where the
independent variable cannot be manipulated by the researcher (Musabyemariya, 2002).
3.2 Population and Selection of the Sample
3.2.1 Population
Polit and Hunger (1999) refer to the population as an aggregate or totality of all the
objects, subjects or members that conform to a set of specifications.
During the research of the study, the researcher made ahead cohort of approximately 20
customers per day.
For the sample size calculation the researcher has considered the 20 customers to join 40
employees to form the population of 60 participants which have affected the sample group
participated in this study.
10
3.2.2 Selection of the sample
Before investigation of the study, the researcher used a sample selected from car wash
employees of Kicukiro car wash, the reason that asking all employees requires a big need
of time. For selecting sample members from a population of 60 formed by 20 customers
and 40 employees of Kicukiro car wash, we used simple random sampling method so that
all members have the same possibility of belonging to the sample. This helped us also to
avoid selection error which takes place if any of the elements of the population has a
higher probability of being selected than the rest.
The sample group participated in this study will be calculated by using YAMANE equation
(Yamane, 1967) as follows;
�
n=
1+�(� 2 )
Where,
n = the sample size

N = the size of population
e= the error percentage points.
N= 60
e = 10% = 0.1
From equation, the sample size can be calculated as follows;
60
n= =37.5 ≃ 37 Respondents
1+60×0.12
After the calculation the researcher got the sample size of 37 respondents including 12
customers and 25 customers.
11
Table1: Population of the study
3.2.3 Tools for data collection/ Instrumentation

Respondents Population Sample size
Employees of the car wash 40 25

Customers of the car wash 20 12
Total 60 37
Table 1: Population and sample
The data was used both primary and secondary source of data in both qualitative and quantitative
methods for the purposes of data triangulation.
Indeed, the self administered questionnaire and interview were used to collect quantitative
data from customers and employees and those quantitative data have helped to produce
inferential statistics while the interview was used to collect qualitative data from the
manager of Kicukiro car wash and this helped in providing narrative statements which
have been a common base for reaching conclusion.
3.2.3.1 Information gathering techniques

Information gathering refer to the means by which the researcher solicits information
from responds or from other sources that relevant to the study problem. The researcher
used the following techniques to gather the required information: observation,
questionnaires and the documentation techniques.
3.2.3.2 Interview techniques

The interview used as a strategy of collecting data; researcher used purposive sampling to
select non-random fashion to get information needed from the respondents. Interview
method of collecting data involves the presentation of oral verbal and reply in terms of
the oral verbal response this method can be used through personal interview and if
possible through telephone interview.
3.2.3.3 Questionnaire techniques

A set of questionnaires for obtaining statistically useful was obtained certain from individual.
The researcher used this method to gather first-hand information from the respondents.
12
3.2.3.4 Observation method
Through observation, the researcher were able to observe the existing operations of the system
and how it did its current activities that were taking more time on the ground.
3.3 Collection of data

Primary data were the main source of information for this paper and were collected
through questionnaire to the customers and employees. Both quantitative and qualitative
information were collected. Key informant questionnaire were held with customers and
employees who had understanding on different between manually system and system
electronically.
Secondary information for the study was obtained from published printed documents and
unpublished documents and reports from different sources like online report provided by
international car wash association and staff of car wash especially the manager.
3.4 Analysis of data

The researcher analyzes data variables using SPSS program to compute for the results. The
outputs of the program have been presented in Chapter five and the result of respondents would
be presented as follows;
Descriptive statistics will be used with demographic variables. The researcher will take collected
data to analyze by using Frequency, Percentage and then present the results in form of tabulation.
3.5 Validity and Reliability
3.5.1 Reliability
According to Joppe (2000), Reliability is defined as “The extent to which results are consistent
over time and an accurate representation of the total population under study is referred to as
reliability and if the results of a study can be reproduced under a similar methodology, then the
research instrument is considered to be reliable.”
According to classical test theory, any score obtained by a measuring instrument (the observed
score) is composed of both the “true” score, which is unknown, and “error” in the measurement
process. The true score is essentially the score that a person would have received if the
13
measurement were perfectly accurate. The process of developing and validating an instrument is
in large part focused on reducing error in the measurement process. There are different means of
estimating the reliability of any measure. Ac-cording to Crocker and Algina (1986), the test
developer has a responsibility to “identify the sources of measurement error that would be most
detrimental to useful score interpretation and design a reliability study that permits such errors to
occur so that their effects can be assessed.”Pretesting or pilot testing an instrument allows for the
identification of such sources. Refinement of the instrument then focuses on minimizing
measurement error. Reliability estimates are used to evaluate (1) the stability of measures
administered at different times to the same individuals or using the same standard (test–retest
reliability) or (2) the equivalence of sets of items from the same test (internal consistency) or of
different observers scoring a behavior or event using the same instrument (interrater reliability).
Reliability coefficients range from 0.00 to 1.00, with higher coefficients indicating higher levels
of reliability.
3.5.2 Validity.
Validity is often defined as the extent to which an instrument measures what it purports to
measure. Validity requires that an instrument is reliable, but an instrument can be reliable
without being valid. For example, a scale that is incorrectly calibrated may yield exactly the
same, albeit inaccurate, weight values. While we speak of the validity of a test or instrument,
validity is not a property of the test itself. Instead, validity is the extent to which the
interpretations of the results of a test are warranted, which depends on the test‟s intended use
(i.e., measurement of the underlying construct). Validity evidence is built over time, with
validations occurring in a variety of populations. Comprehensive literature reviews on
measurement approaches are therefore critical in guiding the selection of measures and
measurement instruments.
Construct validity: This type of validity is a judgment based on the accumulation of evidence
from numerous studies using a specific measuring instrument. Evaluation of construct validity
requires examining the relationship of the measure being evaluated with variables known to be
related or theoretically related to the construct measured by the instrument. For example, a
measure of quality of life would be expected to result in lower scores for chronically ill patients
than for healthy college students. Correlations that fit the expected pattern contribute evidence of
14
construct validity. All evidence of validity, including content- and criterion-related validity,
contributes to the evidence of construct validity.
Content validity: This type of validity addresses how well the items developed to operationalize
a construct provide an adequate and representative sample of all the items that might measure the
construct of interest. Because there is no statistical test to determine whether a measure
adequately covers a content area or adequately represents a construct, content validity usually
depends on the judgment of experts in the field. Criterion related validity. This type of validity
provides evidence about how well scores on the new measure correlate with other measures of
the same construct or very similar underlying constructs that theoretically should be related. It is
crucial that these criterion measures are valid themselves. The concept of validity is described by
a wide range of terms in qualitative studies. This concept is not a single, fixed or universal
concept, but “rather a contingent construct, inescapably grounded in the processes and intentions
of particular research methodologies and projects”(Winter, 2000, p.1). Although some qualitative
researchers have argued that the term validity is not applicable to qualitative research, but at the
same time, they have realized the need for some kind of qualifying check or measure for their
research.
3.6 Ethical Considerations
The purpose of this module is to introduce and discuss ethical issues that should be considered
when designing and conducting a research project. Ethical considerations in research are critical.
Ethics are the norms or standards for conduct that distinguish between acceptable and
unacceptable behaviors. For the case of Kicukiro Car Wash, the researcher made it clear to them
that the information get will not be disclosed as well as the names of institutions and respondents
involved in the study. Before carrying out this study, the researcher made a request of
permission to start from UTB authorities and therefore, responses gained from respondents will
be treated with total confidentiality and will be for the academic propose only.
15
CHAPTER FOUR: SYSTEM ANALYSIS AND DESIGN
4.0 Introduction
This chapter covers the system analysis which describes the process that focuses on the analysis
of the existing system, requirement specification, and the overall architecture of the new system.
In addition system analysis helps the researcher in understanding and identifying the user and
system requirements of the proposed system as well as how to design and model the proposed
system in order to come up with a working solution.
4.1 Data analysis and presentation

This chapter presents the data analyzed based on the 37 questionnaires composed by 12
questionnaires for customers 25 questionnaires for employees separately. The obtained data were
input in computer and have been analyzed using SPSS16.0 software to compute for the results.
Starting by the customers „side, the results were classified into three sections including
demographic data of respondents, using car wash service behavior pattern, and decision making
on using car wash service in Kigali. In the last of this chapter, the researcher will discuss about
financial analysis, people management and competitive analysis that the researcher believes that
it might be useful for entrepreneurs who are interested in this business.
4.1.1 Analysis result of 12 questionnaires for customers

a. Demographic Characteristics of Respondents
Base on part 1 of the questionnaire, the personal information of the sampling group of the study
is demographic characteristics as summarized in the following figures.
Table 2 Respondent’s Demographic Data Classified by Gender
Source: Primary data analyzed with SPSS16
The results from Table 1 illustrated that the majority of respondents are male
16
Table 3 Respondents’ Demographic Data Classified by Age

The results from Table 2 illustrated that the majority of respondents have between 31 and 40
years old.
Table 4 Respondents’ Demographic Data Classified by Marital Status

The results from Table 3 revealed that up to 75 % of respondents are single while the remaining
25% are married.
Table 5 Respondents’ Demographic Data Classified by Education
17
The results from Table 4 showed that the majority of respondents have a Bachelor degree and a
Secondary certificate respectively at 41.7 percent level, while the remaining percent have the
Vocation training and primary certificate respectively at 8.3%.
Table 6 Respondents’ Demographic Data Classified by nationality
The results from Table 5 showed that up to 100% of respondents are Rwandan by nationality.
b. Using Car Wash Service Behavior Pattern of Respondents

Base on part 2 of the questionnaire, using car wash service behavior pattern of the sampling
group of the study is using car wash basing on service delivery and service frequencies,
appreciation of the provided service and lastly the fairness of price.
Table 7 Respondent’s Using Car Wash Service Behavior Pattern Classified by Frequency
in Using Car Wash Service

The results from Table 6 illustrated that most of respondents who use car wash service regularly
always use the service once in a week and more than once a week respectively.
18
Table 8 Respondents’ Using Car Wash Service Behavior Pattern Classified by their
appreciation on using Kicukiro Car Wash Service

The results from Table 7 illustrated that most of respondents who use car wash service regularly
always appreciate the service they are given.
Table 9 Respondents’ Using Car Wash Service Behavior Pattern Classified by fairness of
the price.

The results from Table 8 illustrated that most of respondents who use car wash service find the
price of service fair.
c. Decision Making on Using Car Wash Service in Kigali

The results from part 3 of the questionnaire, the decision making on using car wash service in
Kigali of the sampling group of the study could be analyzed, concluded, and illustrated in the
following figures.
19
Table 10 Respondents’ Using Car Wash Service Behavior Pattern Classified by their choice
about the car wash

The results from Table 9 revealed that most of respondents who use car wash service regularly
stated that they always give their first priority when they are choosing to be membership with car
wash service operators to location.
Table 11 Respondents ‘using Car Wash Service Behavior Pattern Classified by their views
about using a computerized system.

The results from the table 10 showed that the majority of respondents really appreciate the use of
a computerized system in Kicukiro car wash to improve their performance.
20
Table 12 Respondents’ Using Car Wash Service Behavior Pattern Classified by
Expectation from Using Car Wash Service

The results from Table 11 revealed that up to 50 % of respondents who use car wash service
regularly stated that they would like the management of car wash to advice their employee and
then the remaining is all about proper time range and selling car care products respectively.
4.1. 2 analysis result of 25 questionnaires for Employees.

Table 13 Frequency table
Source: Primary data analyzed with SPSS16.0

Data in table 1 reveals that up to 100% of respondents have validated their answers.
This shows that this project caught much attention, and the respondents have thought more
about the challenges of current system of customer care service given by the manager.
And this have motivated the researcher to think about the designing and developing the
new system.
21
Table 14 Gender of respondents

Data in table 2 also reveals that there were male respondents at 96% then 4% female.
Table 15 Age of respondents
Primary data analyzed with SPSS16

The result from the table 3 reveals that up to 60% of respondents are less than 30 years old.
Table 16 Education backgrounds of respondents

The result from the table 4 reveals that the majority of respondents have a primary
certificate at 60 percent level and a Secondary certificate at 32 percent while the
remaining 8 percent have done vocational training.
22
Table 17 Nationality

Data in the table 5 reveals that 92% of respondents are Rwandan by nationality.
Table 18 Marital status

The result from the table 6 reveals that 64% of respondents are single while the remaining
36% are married.
Table 19 Working experience

The result from the table 7 reveals that 48% of respondents have between 2-4 years of
experience while 36% have less than 1 year of experience and then the remaining 16%
have over 5 years of experience.
23
Table 20 Time of service delivery

The result from the table 8 shows that most of respondents deliver the service to their
customer between 30 minutes and 1 hour.
Table 21 View of respondents about using a computerized system

The result from the table 9 shows that most of respondents appreciate the use of a
computerized system at 92 %.
4.2 Interpretation of findings/results
Structured survey questionnaires were distributed to the car owners who live in Kigali area for a
face-to-face interview. The descriptive statistics for data analysis are frequency and percentage.
The samples are 12 people who are currently own a car and live in Kigali and 25 current
employees of the car wash.
The results of the study illustrated that the majority of respondents are male at 100% level on
the side of customers and 96% on employee side are also male, on the customer side, 58.3
percent have age between 31 and 40 years while 60% of respondents at employee‟s side have
24
less than 30 years old. Up to 75 percent of respondent‟s customers are married while 36 percent
respondent‟s employees are single and most of them are Rwandan by nationality because only
8% of employees are not Rwandan by nationality. The result from the table b.1 illustrated that
regular customers frequently use the car wash more than once a week and once in week
respectively at 41.7%, where the result from table b.2 proved that up to 91.7% appreciate the
service they get even thought the price is not totally fair basically they choose the carwash
according to the location. Finally the respondent customers expect from the management of the
car wash to advice their employees at 50% and to improve their proper time range as well as to
sell their car care product and according to table c.2 and table 4.1.2.9 it is shown that the new
system is needed at the highest portion.
Summary
Car wash service should charge the reasonable price, have good and friendly employees and do
not waste the customers‟ time. Car wash service should have a delivery service. It should have a
pick-up service at the customers‟ place in order to attract customers who have no time.
Furthermore, it will be a perfect service for people who go to car wash service sites and it turned
out that the sites cannot serve their demands because of full capacity. Car wash service should be
very careful about the copy of car key because some customers choose not to use the service as
they do not trust employees. They are afraid that employees would take their car key and make a
copy of it. To maximize all this improvement we will motivate it by introducing information
technology tools as it have been expressed by the result of the research so that the company can
reach to the positive change that they tend to achieve. Car wash service should have guarantee
policies not only the quality of the wash matters but also the safety and properties inside the car.
4.3 Description of the existing system

The existing system that was been used at Kicukiro Car Wash to communicate with their
customers during the service delivery and share information with their employees showed that it
was totally done manually, where the manager of the car wash records the whole process of
offered wash services using a pen and a piece of paper and even all company‟ transactions are
recorded the same way using a piece of paper and a pen for each and every day and this can be
damaged very easily. Customers to communicate with car wash employees was also an
25
arrangement of the concerns which is also hard because in case one among the employees and
customer isn‟t on the network it is a problem because the customer is the one to take his/her time
to go and take back his/her car. In addition to that employees are the one to allocate themselves
to work where one employee can have more than one cars while others are free.
4.3.1 Weaknesses of the existing system

 The system was found to be a bad management, time consuming, resource consuming.
 Furthermore, the researcher founds that there was a lot of paper work involved in the
work of communicating the announcements, which could easily be misplaced and
subjected to many factors like losing the records into papers.
 Some records could get lost or be misplaced
 You can‟t access your information wherever you are
 There is lack of communication
 Assignment of duties and responsibility is not effective
4.3.2 Strengths of the existing system

 The system could not be destroyed by an accidental power loss
 The system might be an operational if no power supply or computer failure
 The system was easy to use
 Hard copies were kept for referral purposes
4. 4 Description of the proposed system

The car wash management information system is application software which is designed to
improve clearance in carwash industry especially in Kicukiro car wash by providing easy
communication way between employees and customers, this application also will help the
management of the car wash company to record and generate report accordingly. This
application also will help the car wash administration to solve the management issue which is
frequent in this sector.
26
4.4.1 Advantages of the new system
With the car wash management information system services, you will enjoy the advantages
of:
 Individualized account management that can simultaneously check the payment
amount and the payer, and make quick and correct receipt.
 The new system will provide the security of information by verifying authentication of
each and every one who needs to access the system, and keep them from loss.
 The new system will be an application that will notify the customer to come and take the car
based on its scheduled time and finally generates the report accordingly.
 The system will provide a mean of registering each and every customer for membership
purposes.
4.4.2 Modules of the new system

1. Authentication module: This module is used to provide access to the appropriate car wash
staff member like administrative or the manager to access the application.
2. Management Module: This module allows the manager to control and manage car wash daily
activities
3. Notification module: This module is used for notifying customers to come and take back their
cars when they are ready.
4. Registration module: This module is used for the registration of new customers in Kicukiro
Car wash for membership purposes
5. Labor management module
Anticipate and control labor cost with the system. Because the labor is one of the highest daily
costs in car wash operations, the system will provide the powerful tools to manage employees
effectively.
27
4.4.3 System Configuration and Technology (platform)
4.4.3.1 Hardware requirements and specification

Table 1: Hardware tools
System Specification
Storage (Hard disk) 40 GB or above
Read access memory(RAM) 1GB or above
Processor speed (CPU) 1.4 GHZ or above
Processor Intel Pentium 4 or above
4.4.3.2 Software requirements and specification
Table 2: Software tool table
Software and technology Technology and Language specification
Operating system type 32 and 64 bit operating system
Operating system Windows 7 or other cross-platform
Browsers Opera, Google chrome, torch, Mozilla
Firefox, …
HTML, CSS,PHP,JSP Front-End Languages
MYSQL(WAMP) Back- end languages/ server
Sniping tool To take screenshot picture
Flowchart Software Click Charts Diagrams
28
4.5 Illustration of New system
4.5.1 Software/System Development Model

In the system development process, the researcher focuses on the activities directly related
to production of system for example water fall model and prototyping. The two models
were used during the development of the application.
Prototyping model is a system development method (SDM) in which a prototype (an

early approximation of a final system or product) is built, tested, and then reworked as
necessary until an acceptable prototype is finally achieved from which the complete
system or product can now be developed. This model works best in scenarios where not
all of the project requirements are known in detail ahead of time. It is an iterative, trial-
and-error process that takes place between the developers and the users.
4.5.1.1 Waterfall model

The waterfall model is a sequential development approach, in which development is seen
as flowing steadily downwards (like a waterfall) through the phases of requirements
analysis, design, implementation, testing (validation), integration, and maintenance. To
follow the waterfall model, one proceeds from one phase to the next in a purely sequential
manner. (Benington , 1983).
29
Figure 1: Waterfall model
System Requirement
Software Requirement
Analysis
Program design
Coding & Testing
Operations
4.5.1.2 Phases of water fall model

1. System requirements
 Identify, select and document functional, scheduling and financial requirements.
 Defines the purpose of the information system.
 The deliverable at the end of this stage is the feasibility study.
2. Software requirements
 Identify, select and document the software features necessary to satisfy the system
requirements.
 A deliverable at the end of this stage is the software requirements document.
 Another deliverable is the preliminary design specification.
3. Analysis
 Methodically work through the details of each requirement.
 Document inputs, outputs, processing and algorithms.
 Resolve problems, handle dependencies and develop plans to mitigate risks.
4. Program design
 Use programming techniques to design software and hardware within the
constraints and objectives set in the earlier stages.
 A deliverable at the end of this stage is the design specification
30
 Another deliverable is the test plan.
5. Coding
 Implement the program as designed in the earlier stages.
 The deliverable at the end of this stage is the software program.
6. Testing
 Test the software and record the results.
 A deliverable at the end of this stage is the updated test plan.
 Another deliverable is the updated design specification.
7. Operations
 The deliverable at the start of this stage is the operating manual.
 Deliver, install and configure the completed software.
 Provide maintenance and support of the software
4.5.1.3 Advantages of waterfall model

 It is easy to understand and implement.
 It reinforces good habits: define before design, design before code.
 Widely used and known
 Easy to manage due to the rigidity of the model each phase has specific deliverables
and a review process.
 Works well for smaller projects where requirements are very well understood.
4.5.2 Data Flow Diagram
4.5.2.1Context diagram
Is a representation of a user's interaction with the system and depicting the specifications
of all external users with the system? A context diagram can portray the different types of
external of a system and the various ways that they interact with the system. This type of
31
diagram is typically used in conjunction with the textual external users and will often be
accompanied by other types of diagrams as well.
Concepts
Actor: The actor of this system is someone who does an action

Flow: This is way of showing of system it should work from
4.5.2.2 Data Flow Diagrams symbols

There are four basic symbols used in data flow diagram: External entity, process, data
flow, and data store.
Entity
The external entity represents the actors outside the system that interacts with the system.
It is represented by the rectangle.
Process
Processes are work or actions performed on incoming data flows to produce outgoing data
flows. These show data transformation or change. Data coming into a process must be
"worked on" or transformed in some way.
Data Flow
Data flow represents the input (or output) of data to (or from) a process ("data in motion").
A DF is represented by a line, with arrowheads showing the direction of flow.
Data Stores
Data Stores are repository for data that are temporarily or permanently recorded within the
system. It is an "inventory" of data. Data store are represented by Narrow opened
rectangle as follows.
32
4.5.2.3 Data flow diagram (DFD)
Level 0 or Context diagram: This is leveled as 0 because it represents the system as a
single box. It has only the external entities sending and receiving data to and from the
system.
Figure 2: Context diagram or level 0
Figure 3: DFD level 1 for the manager
33
Figure 4: DFD level 1 for the customer
Figure 5: DFD Level 2 of proposed system
4.5.3Use Case Diagram

A use case is a methodology used in system analysis to identify, clarify, and organize
system requirements. The use case is made up of a set of possible sequences of
interactions between systems and users in a particular environment and related to a
particular goal
Kicukiro Car Wash Management Information System
34
Figure 6 Use case diagram
4.5.4 Normalization
Is the process of organizing data in a database where include creating tables and establishing
relationship between those tables according to rules designed both to protect the data and to
make the database more flexible by eliminating redundancy and inconsistent dependency.
35
Redundancy data wastes disk space and creates maintenance problems. If data that exist in more
than one place must be changed‟ the data must be changed in exactly the same way in all
location. An employee address change is much easier to implement if that data is stored only in
the employee tables and nowhere else in database.
4.5.4.1 Data Normalization Rules

Table 22: Normalization rules
Level Rule
First normal
An entity type is in 1NF when it contains no repeating groups of data.
form (1NF)
Second normal An entity type is in 2NF when it is in 1NF and when all of its non-key
form (2NF) attributes are fully dependent on its primary key.
Third normal An entity type is in 3NF when it is in 2NF and when all of its attributes are
form (3NF) directly dependent on the primary key.
Scott W. Ambler 2004) (
Inconsistent dependency while it is intuitive for a user to look in the employee table for the
address of a particular employee. The employee salary is related to or dependent on the
employee and thus should be moved to the employee table. Inconsistent dependency can make
data difficult to access because the path to find the data may be broken.
There a few rules for database for database normalization. Each rule is called a “normal form.”If
the first rule is observed the data base is said to be in “first normal form. If in the first three rules
are observed the database is considered to be in “third normal form”. Although other levels of
normalization is possible third normal formal form is considered the highest level necessary for
most application
4.5.4.2 First normal form

 Create a separate table for each set of related data
 Eliminate repeating groups in individual tables
 Identify each set of related data with a primary key
 Do not use multiple fields in a single table to store similar data
36
Car Table
Car_id Plate_number Car_model Received_date Washer_id Wash_cost
4.5.4.3 Second normal form

Create separate tables for set of values that apply to multiple record relate these table with
foreign keys. Record should not depend on anything other than a table‟s primary key (a
compound key if necessary.
Car
Car id Plate number Car model
Washer
washe washer_nam washer_addres washer_status washer_dob washer_contact

_id e s
4.5.4.4 Third normal formal

Eliminate fields that do not depend on the key values in the record that are not part of that
record‟s key do not belong in the table in general anytime the content of a group of field may
apply to more than a single record in the table consider placing those field in a separate table.
Car
CarID Plate_number Car_model Received_date WasherID
Washer
washe_id washer_name washer_address carID washer_contact
37
4.5.5 Database System
A database system is described in a formal language supported by the database management

system (DBMS). In a relational database, the schema defines the tables, the fields in each table,
and the relationships between fields and tables.
A table: is a set of data elements (values) that is organized using a model of vertical columns
(which are identified by their name) and horizontal rows.
Primary key: sometimes called a unique key can uniquely identify each row in a table; a unique
key comprises a single column or a set of columns.
A foreign key: a foreign key is a field in a relational table that matches a candidate key of
another table. The foreign key can be used to cross-reference tables.
A relation: is defined as a set of tuples that have the same attributes. A tuple usually represents
an object and information about that object.
4.5.5.1 Database Schema
Figure: 7 Database schema
38
4.5.5.2 Data Dictionary Car wash Management Information System
A data dictionary is a collection of descriptions of the data objects or items in a data model for
the benefit of programmers and others who need to refer to them or the dictionary of data is at a
time the pillar of work and the result of research and analysis of data. It is just like a depicted
Picture of the entire work. This dictionary of data defines all categories of data or data types,
Brief the all essential information about the software is included.
It can be also an automated tool for collecting and organizing the detailed information about
system component, it also maintains, facilitate to document data element, record, system, files,
user and another system component. It will also have facilitated to cross -reference all system
components to each other.
Table 23 Customer_record
39
Table 24 Car
Table 25 Feepayement
40
Table 26 Payement doc
Table 27 users
Table 28 Paymentmode
41
Table 29 Washers
Source: phpMyAdmin
4.5.6 Entity Relationship Diagram

Entity relationship diagram is defined as a visual representation of different data using
convention that describe how these data are related to each other.
Entity relationship diagram have three basic elements
 Entity
 Attributes
 Relationship
1. Entity: It is a principal data object about which information is to be collected it can
also be called an object or a table.
In ER diagram an entity is represented by a rectangle and named using singular nouns.
2. Relationship: this represents an association between two or more objects. It

represented by diamond shapes and is labeled using verbs.
42
Type of relationship
 One-to-one: is implemented using single table by establishing relationship between

same types of columns in a table. In a one –to– one relationship, each row in one
database table is linked to 1 and only 1 other row in another table. In a one –to– one
relationship between Table A and Table B, each row in Table A is linked to another row
in Table B.
R is 1:1 B
A
 One-to-many: implemented using two tables with primary key and foreign key
relationship
In One –to– Many relationships, each row in the related to table can be related to many
rows in the relating table. This allows frequently used information to be saved only once
in a table and referenced many times in all other tables. In a One –to– Many relationships
between Table A and Table B, each row in Table A is linked to 0, 1 or many rows in
Table B.
R is 1: N
A B
 Many—many: implemented using a junction table. The key s from both the tables
form composite primary key of the junction table in a Many –to– Many relationships, one
or more rows in a table can be related to 0, 1 or many rows in another table. In a Many –
to– Many relationships between Table A and Table B, each row in Table A is linked to0, 1
or many rows in Table B and vice versa.
43
R
A B
R is M: N
3. Attribute: is a property or characteristic of an entity
Figure 7: Database squema
4.5.7 Entity Relation Diagram of the carwash management information system

Figure 7: ERD
Source: Click charts Diagram flowchart software
44
4.6 Architecture design of the new System
1.Definition
An architecture design is a technique, form or a stylistic representation that is used by
architects in classification of their work. They may include the various aspects of cultural
context and construction.
2. Database architecture
Figure 8: Architecture of the New System
The above diagram shows how the system is manipulated while processing the data and
how it is accessed users. Each part has got a way of accessing the data through software
application that is designed to solve the problem of the current system .A form is designed
in a way that you fill all data in the interface connected to the database where it is stored.
Each form has got its own specification depending on what the part deals with and what is
supposed to be don
45
CHAPTER FIVE: IMPLEMENTATION, CODING AND TESTING
5.1 Implementation and coding
5.1.1 Introduction
System implementation is a stage in system life cycle whereby a new system is developed,
installed and made ready for use. It is at this stage that all details and key point in the
requirement specification are implemented. System implementation therefore, is a very
essential stage in which its success determines to a great extent the success of the new
system. At this instance, after all is said and done the system is duly ready to be
implemented (Car wash Management Information System).
The system is implemented using the current system (manual system).The work is then
progressively transferred from the old system to the new system over a period of time.
This ensures that any problems in the new system can be resolved.
The structure phase does two things: builds and tests a functional system that fulfils design
requirements, and implements the interface between the new system and the existing
system. The researcher constructed the database, application programs, user and system
interfaces, and networks.
5.1.2 Description of implementation Tools and technology

CSS: CSS stands for Cascading Style Sheets and Styles define how to display HTML
elements. Styles were added to HTML to solve a problem. CSS is used to control the style
and layout of multiple Web pages all at once.
HTML: HTML stands for Hyper Text Markup Language, a markup language is a set of
markup tags. The tags describe document content. HTML documents contain HTML tags
and plain text and documents are also called web pages. (Ben Joan, 2011)
JavaScript: JavaScript is the programming language of the Web that is easy to learn. All
modern HTML pages are using JavaScript. It is the language for HTML, for the Web, for
computers, servers, laptops, tablets, smart phones, and more.
PHP: Hypertext Pre-processor is a widely used, general-purpose scripting language that

was originally designed for web development to produce dynamic web pages.
46
For this purpose, PHP code is embedded into the HTML source document and interpreted
by a web server with a PHP processor module, which generates the web page document,
(Mike Chapple , 2012).
MySQL: is an open source relational database management system (RDBMS) based on

Structured Query Language (SQL).
MySQL is a relational database management system that runs as a server providing multi-
user access to a number of databases. The MySQL development project has made its
source code available under the terms of the GNU General Public License, as well as
under a variety of proprietary agreements. MySQL is owned and sponsored by a single
for-profit firm, the Swedish company MySQL AB, now owned by Sun Microsystems, a
subsidiary of Oracle Corporation. Several high-traffic web sites (Flick, Face book,
Wikipedia, Google (Though not for searches), Nokia and YouTube) use MySQL for data
storage and logging of user data, all the enterprises must obtain a commercial license from
Oracle, Margaret Rouse (2013).
Notepad++: notepad is a page editor that makes it possible to define "languages", or more
precisely highlighting schemes. The original purpose of the feature is to enable proper
highlighting of files in a programming language for which an internal Scintilla lexer is not
available.
WAMP: Wamp Server refers to a software stack for the Microsoft Windows operating
system, created by Romain Bourdon and consisting of the Apache web server, OpenSSL
for SSL support, MySQL database and PHP programming language(Susan, 2012)).
Browser: is a software application for retrieving, presenting and traversing information

resources on the World Wide Web. An information resource is identified by a Uniform
Resource Identifier (URI/URL) and may be a web page, image, video or other piece of
content,(Spirit Works , 2009).
47
5.1.3 Screen Shots and Source Codes
Figure 9: Login interface of Car wash MIS
Login interface allows all users of system based on their function or role and shows how the user
can enter in the system using his/her name and given password.
Source: taken by using snipping tool
<?php
error_reporting(0);
session_start();
$userid=$_SESSION['valid_user'];
$type=$_SESSION['valid_type'];
?>
<!DOCTYPE html>
<html lang="en">
<head>
<title>Home</title>
<meta charset="utf-8">
<link rel="stylesheet" href="css/reset.css" type="text/css" media="all">
<link rel="stylesheet" href="css/layout.css" type="text/css" media="all">
<link rel="stylesheet" href="css/style.css" type="text/css" media="all">
<script type="text/javascript" src="js/jquery-1.6.js" ></script>
48
<script type="text/javascript" src="js/cufon-yui.js"></script>
<script type="text/javascript" src="js/cufon-replace.js"></script>
<script type="text/javascript" src="js/Didact_Gothic_400.font.js"></script>
<script type="text/javascript" src="js/Shanti_400.font.js"></script>
<script src="js/roundabout.js" type="text/javascript"></script>
<script src="js/roundabout_shapes.js" type="text/javascript"></script>
<script src="js/jquery.easing.1.2.js" type="text/javascript"></script>
<script type="text/javascript" src="js/script.js"></script>
</head>
<body id="page5">
<div id="header">
<marquee><p>We are happy to serve and satisfy all your needs
you mean so much to us!!!!
The service derivery is only in three hours</p></marquee>
</div>
<div class="body1">
<div class="main">

<header>
<div class="wrapper">
<nav>
<span class="date"><?php $d=date("D M d,Y"); echo $d;?></span>
</nav>
<span class="date"></span>
<nav>
<ul id="menu">
49
<li id="menu_active"><a><span><span>Welcome To KICUKIRO CAR Wash
Management Information System</span></span></a></li>
<li>
</ul>
</nav>
</div>
</header>
<div class="ic"></div>

<article id="content">
<section class="col2">
<figure class="left marg_right1"><img
src="images/ISPGlogo.JPG" alt=""></figure>
<h2 class="pad_bot1">User Identification - Login</h2>
<p class="pad_top1 pad_bot1">
<div>
<form id="ContactForm" method="post"
action="kiki.php">
<table>
<tr>
<td>Username:</td><td><div class="
bg"><input type="text" class="input" name="user" required /></div></td></tr>
<option> </option>
<?php
/*include"connect.php";
$sql=mysql_query("SELECT * FROM users",$con);
while($row=mysql_fetch_array($sql))
{
$a=$row['user_name'];
echo"<option>$a</option>";
50
}
mysql_close($con);*/
?>
<tr>
<td>Password:</td>
<td><div class="bg"><input
type="password" class="input" name="pw" required></div></td>
</tr>
<tr>
<td></td>
<td>.</td>
</tr>
<tr>
<td><input type="submit" value="Login"
class="button" name="submit"></td>
<td><input type="reset" value="Cancel"
class="button" name="submit"></td>
</tr>
</table>
</form>
<a href="account.php">Create account</a>
</div>
</section>
</article>
</div>
</div>
<div class="main">
<footer>© 2016- KICUKIRO CARWASH Management System Developed
BY MUKABAYIZERE Francine</footer>
51
</div>
<script type="text/javascript"> Cufon.now();</script>
<script type="text/javascript">
$(document).ready(function() {
$('#myRoundabout').roundabout({
shape: 'square',
minScale: 0.89, // tiny!
maxScale: 1, // tiny!
easing:'easeOutExpo',
clickToFocus:'true',
focusBearing:'0',
duration:800,
reflect:true
});
});
</script>
</body>
</html>
52
Figure 10: Print bill
At this stage, the print bill will help the manager to be able to know exactly the number of
received customers based on the bill printed.
Source: taken by using snipping tool
<?php
error_reporting(0);
session_start();
?>
if($type=="admin")
{
?>
<ul id="menu">
<li><a
href="customers.php"><span><span>customer</span></span></a></li>
53
<li><a
href="schedule.php"><span><span>About Fees</span></span></a></li>
<li id="menu_active" class="nav3"><a
href="documents.php"><span><span>Billing</span></span></a></li>
<li class="nav4"><a
href="reports.php"><span><span>Reports</span></span></a></li>
<li><a
href="administration.php"><span><span>Settings</span></span></a></li>
</ul>
<?php
}
else
{
?>
<ul id="menu">
<li><a
href="customer.php"><span><span>customers</span></span></a></li>
<li><a
href="schedule.php"><span><span>About Fees</span></span></a></li>
<li id="menu_active" class="nav3"><a
href="documents.php"><span><span>Billing</span></span></a></li>
</ul>
<?php
}
?>
</nav>
</div>
</header>
<div class="ic"></div>

<article id="content">
54
<h2>Billing</h2>
<?php
include "connect.php";
$total=mysql_query("SELECT COUNT(received_from) AS total
FROM payementdoc ORDER BY received_from ASC",$con);
$n=0;
$query=mysql_query("SELECT * FROM payementdoc ORDER
BY billid DESC");
echo"<h4>";
echo"<table>";
while($row=mysql_fetch_array($query))
{
$n=$n+1;
if($n<=13)
{
$id=$row['billid'];
echo"<tr>
<td>$row[billid]     </td>
<td>$row[received_from]</td>
<td>      $row[car_id]</td>
<td>      $row[amount_payed]</td>
<td>     $row[payment_description]</td>
<td>     $row[date_of_payment]</td>
<td>     $row[slipnumber]</td>
<td>     <a href=printbill.php?billid=$row[billid]
class='button' target='_blank'>Print</a></td>
</tr>";
}
}
55
echo"</table>";
echo"<h4>";
$a=$total%13;
$b=$total/13;
$bb=ceil($total/13);
if($a>0 && $a<13)
{
$c=$bb+1;
}
else
{
$c=$bb;
}
$i=1;
echo"<center><h5>Pages : ";
while($i<=$c)
{
if($i==1)
{
echo"<a href=next.php?page_id=".$i.">"."first"."-
</a>";
}
else
{
if($i==$c)
{
echo"<a href=next.php?page_id=".$i.">"."
last"."</a>";
}
else
{
56
echo"<a
href=next.php?page_id=".$i.">".$i."-</a>";
}
}
$i=$i+1;
}
echo"</h5></center>";
?>
</article>
</div>
</div>
<div class="main">
<footer>©2016 Car Wash Management Information System</footer>
</div>
</body>
</html>
57
Figure 11: Fee payment form
Source: data taken by using snipping tool
This form will be used by the administrator to record payement processes for customers
according to their arrival.
<?php
error_reporting(0);
session_start();
?>
<script src="../../../../ui/jquery.ui.widget.js"></script>
<script src="../../../../ui/jquery.ui.datepicker.js"></script>
<link rel="stylesheet" href="../../../demos.css">
<script>
$(function() {
58
$( "#datepicker" ).datepicker({
changeMonth: true,
changeYear: true
});
});
</script>
<script type="text/javascript" src="js/jquery-
1.6.1.min.js"></script>
ui-1.7.custom.min.js"></script>
search.js"></script>
<script src="js/jquery-1.7.1.min.js"></script>
<script src="js/script.js"></script>
</head>
<body id="page2">
<div class="body1">
<div class="main">
<header>
<nav>
<ul id="top_nav">
<li><a>Welcome : <?php echo
$userid;?></a></li>
<li><a
href="index.php">Disconnect</a></li>
</ul>
</nav>
<span class="date"><?php $d=date("D M d,Y"); echo
$d;?></span>
</div>
59
<nav>
<?php
if($type=="admin")
if(isset($_POST['feesubmit']))
{
$a=$_POST['cstmid'];
$b=$_POST['paymentdate'];
$c=$_POST['feetype'];
$d=$_POST['financialyear'];
$e=$_POST['feedescription'];
$f=$_POST['amountpayed'];
$g=$_POST['slipnumber'];
$h=$_POST['carid'];
$i=$_POST['userid'];
include"connect.php";
{
$query=mysql_query("INSERT INTO
feepayement(customer_id,paymentdate,feetype,financialyear,feedescription,amountpaid,sl
ipnumber,car_id,user_id) VALUES('$a','$b','$c','$d','$e','$f','$g','$h','$i')",$con)or
die("<h3>Problem with Insertion of Data:</h3>:".mysql_error());
if(!empty($query))
{
echo"<h3>payement recorded successfully !!!! </h3>";
}
else
{
60
echo"<h3>Operation failed !!!!!</h3>";
}
//mysql_close($con);
}
?>
<div class="dialog-pad">
<div id="dialog2" title="customer service Fee Information">
<h2> Service Fee payment Information.</h2>
<table width="358" border="0">
<tr>
<td width="167">Customer ID :</td>
<td width="181"><h4><?php echo $code;?></h4></td>
</tr>
<hr />
<tr>
<th width="50"><strong>Date</strong></th>
<th width="150"><strong>Fee Description</strong></th>
<th width="90"><strong>Fee Amount</strong></th>
</tr>
</table>
<hr />
<h2>Total Amount Payed is : <?php echo $total;?></h2> - <a href="print1.php?id=<?php
echo $id;?>&y=<?php echo $y;?>" class="btn style_2" target="_blank">Print</a>
<hr />
</div>
<button id="opener2" class="btn style_2">View Results</button>
</div>
61
<?php
}
?>
</section>
<section>
<table>
<tr valign="top">
<td valign="top">
<h3>
<form action="schedule.php" method="post" id="ContactForm" name="fee">
<tr>
<td>Customer ID:</td>
<td><div class="bg">
<select name="car_id">
<?php
$custom=mysql_query("SELECT * FROM customer_record");
while($fetch=mysql_fetch_object($custom))
{
echo "<option>".$fetch->customer_id."</option>";
}
?>
</select>
</div></td>
</tr>
<tr>
<tr>
62
<td>Payment date:</td>
<td><div class="bg"><input type="text" placeholder="enter date" class="input"
name="paymentdate" pattern="\d{4}-\d{1,2}-\d{1,2}" title="please match with this
format yyyy-mm-dd" class="tcal" required /></div></td>
</tr>
<td>Fee.Type:</td>
<select name="feetype">
<option>select</option>
<option>wash Fee</option>
<option>Engine wash fee</option>
<option>Maintenance fee</option>
</select></div></td>
</tr>
<tr>
<td>financial year:</td>
<td><div class="bg"><input type="text" class="input" name="financialyear"
title="please enter digit only" required /></div></td>
</tr>
<tr>
<td>feedescription:</td>
<td><div class="bg"><input type="text" class="input" name="feedescription" required
/></div></td>
</tr>
<tr>
<td>Amount paid:</td>
<input type="text" placeholder="enter your amount" class="input" name="amountpayed"
title="please enter digit only" required />
</div></td>
</tr>
63
<tr>
<td>Car ID:</td>
<?php
$car=mysql_query("SELECT * FROM cars");
while($fetch=mysql_fetch_object($car))
{
echo "<option>".$fetch->car_id."</option>";
}
?>
</select>
</div></td>
</tr>
<tr>
<td>User ID:</td>
<?php
$us=mysql_query("SELECT * FROM users");
while($fetch=mysql_fetch_object($us))
{
echo "<option>".$fetch->user_id."</option>";
}
64
?>
</select>
</div></td>
</tr>
<tr>
<td></td>
<td><input type="submit" name="feesubmit" value="Save Payement" class="button">
<input type="reset" name="" value="Cancel" class="button"></td>
</tr>
</table>
</form>
</h3>
</td>
<td>           </td
>
<td>
</td>
</tr>
</table>
</section>
</article>
</div>
</div>
<div class="main">
<footer>© 2016 - KICUKIRO CAR WASH Managent INFORMATION
System </footer>
</div>
</body>
</html>
5.2Testing
65
5.2.1Introduction
Software testing is a method of assessing the functionality of a software program. There are
many different types of software testing but the two main categories are dynamic testing and
static testing.
Dynamic testing is an assessment that is conducted while the program is executed; static testing,
on the other hand, is an examination of the program's code and associated documentation.
Dynamic and static methods are often used together.
5.2.2 Objective of Testing

The testing phase of the development is a continual process during the application stage. It
is important that testing is accepted during the development of a system because it
recognizes any mistakes and bugs within the system; either introduced during
establishment (such as wrongly written code) or design faults. It is also authoritative that
these errors and bugs are located during the testing phase prior to the system going live,
because there is the potential that users may exploit these bugs or users will get frustrated
with a system that is “broken “because it was not tested effectively. In addition to this
testing ensures that the implantation meets the requirements
5.2.3 Unit testing outputs

Unit testing is a testing done at the discrete level of program or module. Sometimes, it
refers to module testing. The purpose of unit testing is to identify and reduce execution
errors that cause the program to terminate unusually, and logic errors that could have been
missed during desk checking.
5.2.4 Validation Testing outputs

Validation control if the system gathers with the requirements and executes purpose for
which it is proposed and meet the user need and the organization‟s goals.
66
Figure 12: Add new customer
Source: snipping tool
5.2.5 Integration Testing Outputs
System integration testing (SIT) is a high-level software testing process in which testers verify
that all related systems maintain data integrity and can operate in coordination with other
systems in the same environment. The testing process ensures that all subcomponents are
integrated successfully to provide expected results.
5.2.6 Functional and system testing Results
Is needed to check if the user interface is easy to use and understand. After using this test, the
researcher has been able to confirm the functional of this system to be easy to use by the end
users. System testing is also a level of the software testing process where a complete, integrated
system/software is tested. The purpose of this test is to evaluate the system‟s compliance with the
specified requirements.
67
System Testing is performed after integration testing and before acceptance testing and it is
normally performed by independent testers who are not developers of the system and all
recommended that the developed system is in full compliance with the requirements.
5.2.7 Acceptance Testing Reports

Acceptance Testing (AT) is the last phase of the software testing process. During AT, the actual
software users test the software to make sure it can handle required tasks in real world scenarios
according to specifications.
Figure 13: Customer registration
Conclusions and recommendations

6.0 Introduction
The researcher presented the summary of the findings based on the respondent‟s views the
summary of the findings is presented in line with the objectives of the research.
This part also present conclusion gives the recommendations and suggests the Area(s) for
further research
68
6.1.Conclusion (s)
Regarding to the output of the CAR WASH MANAGEMENT INFORMATION SYSTEM now,
all the objectives have been achieved well considering to the way the system designed process
operations in a small bit of time than how they were done manually without forgetting many
difficulties seen as discussed in earlier chapters.
From this system, the printout message to the scientific environment where the researcher is
belonging is very relevant than before where the things like those this system processes were
seen as the magic but now it is remarkable that all the things done with intellectual contributions
and commitment are very advantageous to real time researchers as well as future researchers
while they are taken into considerations and in priorities for a living life of a scientific person
because there are most valuable things in today‟s business scene.
The researcher is grateful that the system will be able to serve its future purpose and meet
its objectives to the satisfaction of KICUKIRO CAR WASH.
6.2 Recommendations
-Head office
For implementing CAR WASH MANAGEMENT INFORMATION SYSTEM in National in

Kicukiro car wash, all employees must be committed to see that the system operates as the
intentions were set initially by the researcher to improve the working environment of the car
wash. It should however be noted that there is a need for training to the employees especially
those that have to use it on daily basis for example the car wash managers and administrators.
This is because the system involves aspect of new technology that may not be familiar to
everybody.
6.3 Future Researchers

The researcher recommends also the future researchers to develop additional functionality to
adopt all kind of users who need the access on CAR WASH MANAGEMENT INFORMATION
SYSTEM which supports multiple platform users to access the system on the move.
69
REFERENCE
Ahituv, N.&Neummann, Principles of information systems for management, S.(1982). Third
Edition, WCB CO, P 131, P 8. Allen, B., Heurtebise, A., & Turnbull, J.
(2010). Improving Information Access.
Awad, E. M , Business Management US, (1988). Retrieved October 2, 2010 from http://
Bahman, Management Information System: p.5 A. (1991). Concept, structure, and

applications. Califonia: The Benjamin Cummings,
Bee, R.,Bee, F., Managing information and statistic, 1999 Trowbridge
Cromwell Press. Lucy, T., Management Information System. 1997, London.
http://databases.about.com/od/specificproducts/a/whatisadatabase.htm, on 9st Sept;2013

http://goodhassan.wordpress.com/2010/02/02/what-is-internet/(visited on 11th May 2014)
http://www.answers.com/topic/database-management-system, on 11th, July, 201
http://www.fileheap.com/software-editplus-download-9198.html (visited on 11th May 2014)
http://www.programmersheaven.com/2/FAQ-JAVA-What-Is-JDK, on 12th, October, 2013
http://www.techterms.com/definition/css (visited on 14th May 2014)
Information from World wide web(www)
Jahangir, The significant role that information plays in choice of decision, (2005)
Jarboe, MIS strategy, (2005)
John Koeller , Water conservation, (October, 2006). Williams E. Drying Systems.
John Koeller, Water conservation, (October, 2006).
Joppe, Carwashing & Detailing 5, 1, (2000) , 2003. Validity and reliability (2000)
Joppe, Validity and Reliability, (2000), International Carwash Association Inc.
Lindsay, John , Information Systems Fundamentals and Issues, (2000). Kingston University,
School of Information Systems)
70
Lindsay, John, Information Systems fundamentals and Issues, (2000). Kingston University,
School of Information Systems.
Lingham, Positive prospects of MIS , (2006
New Jersey, Information System, ( 2004)
Plan deputy and defense and Armed forces support Ministry plan:” The management
information plan of Armed forces support Ministry plan”. The Report of Systems
Management and Informatics. p. 7.
Richmond, B., Systems Dynamics/Systems Thinking: Let‟s Just Get On With It. Sterling,
Scotland, (1994).
Senge, Peter , Essential of MIS, (1990)
Senge, Peter, International, Systems Dynamics Conference, (2011)
Systems thinking/system dynamics, Ricmond, BC, 1994
T. Cornford, M. Shaikh IS1060, Introduction to information systems, 2013 Undergraduate
Study Departament of Polymer Technology, Faculty of Chemistry, gdansk University of
Technology, narutowicza 11/12, 80-952-gdansk, PolandReceived: April 26, 2006, Accepted:
July 16, 2007
Trends in Modern Car Washing by H. Janik*, A. Kupiec utility costs? Professional

Wade, J., Systems Engineering, (2011). At the Crossroads of Complexity. In Kongsberg
Systems Engineering Event.
Winter, Ethical consideration, (p.1,2000)
www.busmanagement.com/article/Improvinginformation-access/.
71
APPENDICE
72
APPENDICES
Appendice 1: Questionnaire to the employees
Dear respondents,
I am a student from University of Tourism, Technology and Business Studies, currently carrying
out a research on the topic CAR WASH MANAGEMENT INFORMATION SYSTEM a case
study of Car Wash Kicukiro. The researcher would like to ensure you that the answers will only
be used for the study‟s purposes, and will be treated with high confidentiality.
Kindly, I request you to spare few minutes of your time and express your views on the question
below.
SECTION A: Profile of the respondent
1. What is your gender?
o Male
o Female
2. How old are you?
o Less than 30 years

o 31- 40 years
o 41- 50 years
o Over 50 years
3. What is your level of education?
o Primary Certificate
o Secondary Certificate
o Vocational training
o Bachelor degree
73
o Masters Degree
o PhD
4. What is your nationality?
o Rwandan
o Not Rwandan
5. What is your marital status?
o Single
o Married
B. Question relate to the topic
5. How long have you been working with Car Wash?
o Less than 1 year

o 2-4 years
o Over 5 years
6. When do you deliver the service required by the customers?
a. Within 30 minutes
b. Less than 30 minutes
c. Between 30 minutes and 1 hour
d. After 1 hour
7. What is your view if computerization was to be implemented at this company?
o Not appreciated
o Appreciated
Please support your answer
74
............................................................................................................................................................
....................................................................................................................................
INTERVIEW QUESTIONS TO THE MANAGER
1. How do you manage challenges that you face frequently in your working environment
like misunderstanding among employees?
................................................................................................................................................
2. What do you think about the use of technology in your business?
………………………………………………………………………………………………
3. As you record received customers on a daily basis, do you give bonus to those who are
permanent or you record them for your information only?
4. Please describe to us, how your day today work look
like…………………………………………………………………………………………
………………………………………………………………………
5. How do you communicate with your customers when their cars are ready to be
delivered?...............................................................................................................................
....................................................................................................................................
6. How do you categorize prices of your effort? Is it based on car model, or the price is the
same for all cars? Can you please give a little bit explanation about
it……………………………………………………………………………………………
…………………………………………………………………………………..
7. How do you track car model that have been received by employees? Do you use etickets
to mark them or just you record the car id?
…………………………………………………………………………………………….
8. How do you plan or schedule your daily activities? Do you have time table or you let
your employees arrange themselves?
………………………………………………………………………………………………
What is the uniqueness that makes you differ from other carwashes in this city? Qualified
employees? Or you do you advertisement in different ways?
………………………………………………………………………………………………
75
Appendice 2: Letter approved from Kicukiro Car wash
Appendice 3: Schedules
Months 1 2 3 4 5 6 7 8 9 10 11 12
Tasks
Documentation
Chapter one
&two
Chapter two
Chapter three
Chapter four
Chapter five
Submission of
draft
Submission of
final report
76
Appendice 4: Budget
77
Appendice 5: Schedules
Source: Data from Google Map
78
Appendice 6: Supervision tracking form
79

Carwash Management System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Carwash Management System

Uploaded by

Copyright:

Available Formats

UNIVERSITY OF TOURISM TECHNOLOGY AND BUSINESS STUDIES

P.O. Box 350, Kigali - Rwanda

FACULITY OF APPLIED SCIENCES AND TECHNOLOGY

DEPARTEMENT OF BUSINESS INFORMATION TECHNOLOGY

CAR WASH MANAGEMENT INFORMATION SYSTEM

Case study: CAR WASH KICUKIRO

Submitted by: Francine MUKABAYIZERE

Registration Number: 01602/12

Under the guidance and Supervision of Mr. KUNDAN Kumar

A Dissertation submitted to:

The Department of Business Information Technology in partial fulfillment of the

Year of submission: 2017

Name of Student: MUKABAYIZERE Francine

Kigali on, /…. / 2016

Signature of Student …………………………..

Supervisor: KUNDAN Kumar

Kigali on, …. /…. / 2016

To my Brothers and Sisters,

To all my Friends and Colleagues at UTB,

May the Almighty God bless you all!!!

CSS: Cascading Style Sheets

DBMS: Database management system

ERD: Entity Relationship Diagram

GUI: Graphic User Interface

HTML: Hyper Text Markup Language

ICA: International Carwash Association

IT: Information Technology

MIS: Management information system

PHP: Hypertext preprocessor

RDBMS: Relational Database Management System

SDM: Software Development Methodology

SQL: Structured Query Language

WAMP: Window Apache MySQL PHP

DEDICATION ............................................................................................................................... iii

LIST OF ABBREVIATIONS ......................................................................................................... v

ABSTRACT .................................................................................................................................. xii

CHAP 1: INTRODUCTION AND BACKGROUND TO THE STUDY ...................................... 1

1.0 Introduction ...................................................................................................................... 1

1.1 BACKGROUND TO THE STUDY ..................................................................................... 1

1.2 PROBLEM STATEMENT ................................................................................................. 2

1.3 Objective of the study ........................................................................................................... 3

1.3. 1 General objective............................................................................................................... 3

1.3.2 Specific objectives.............................................................................................................. 3

1.4 Research questions ................................................................................................................ 3

1.5 Significance of the study ....................................................................................................... 3

1.5.1 Personal interest ................................................................................................................. 3

1.5.2 To Kicukiro car wash ......................................................................................................... 3

1.5.3 Social interest ..................................................................................................................... 4

1.6 Scope of study ....................................................................................................................... 4

1.6.1 Geographical scope......................................................................................................... 4

1.6.2 Time scope ......................................................................................................................... 4

1.6.3 Content scope ..................................................................................................................... 4

1.7 Limitation .............................................................................................................................. 4

1.8 Platform ................................................................................................................................. 5

CHAPTER TWO: REVIEW OF THE RELATED LITERATURE ............................................... 6

2.0 Introduction ........................................................................................................................... 6

2.1 Definition of key terms and concept ..................................................................................... 6

2.2 Management System ............................................................................................................. 6

2.2.1 Purpose and benefits of a management system .................................................................. 7

2.3 Information technology (IT).................................................................................................. 7

2.4 Information system ................................................................................................................ 7

2.5 Data ....................................................................................................................................... 8

2.6 Database management system ............................................................................................... 8