CHUKA UNIVERSITY

FACULTY OF SCIENCE, ENGINEERING AND TECHNOLOGY

DEPARTMENT OF COMPUTER SCIENCE

UNIT CODE: COSC 482

UNIT NAME: COMPUTER SYSTEM PROJECT 1

PROJECT TITLE: Car Wash Management System

NAME: Kiprono Weldon Kipchirchir

REG NUMBER: EB1/42971/19
SUPERVISOR: MR. Kevin Gogo

SUBMITTED BY KIPRONO WELDON TO CHUKA UNIVERSITY, IN PARTIAL

FULFILMENT OF THE REQUIREMENTS FOR THE DEGREE OF BACHELOR OF
SCIENCE (COMPUTER SCIENCE)

DATE OF SUBMISSION
31/10/2022

i
Table of Contents
PROJECT TITLE: Car Wash Management System..................................................................i
CHAPTER 1: INTRODUCTION................................................................................................1
1.0 INTRODUCTION...................................................................................................................1
1.1 BACKGROUND STUDY.......................................................................................................1
1.2 PROBLEM STATEMENT......................................................................................................1
1.3 PROPOSED SOLUTION.......................................................................................................2
1.3.1 AIM OF THE PROJECT..........................................................................................................2
1.3.2 OBJECTIVES............................................................................................................................2
1.4 SIGNIFICANCE OF THE PROJECT..................................................................................2
1.5 SCOPE AND LIMITATION OF THE STUDY...................................................................3
CHAPTER TWO: LITERATURE REVIEW.............................................................................4
2.0 Introduction..............................................................................................................................4
2.1 Literature Review....................................................................................................................4
2.2 CONCLUSION.......................................................................................................................5
CHAPTER THREE: METHODOLOGY...................................................................................7
3.0 Research methodology/Research design used......................................................................7
3.1 Data collection methods used..................................................................................................7
3.1.0. Observation...............................................................................................................................7
3.1.1. Questionnaires..........................................................................................................................7
3.1.2. Interviews.................................................................................................................................7
3.2 SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC).....................................................8
3.3 REQUIREMENT DEFINITION............................................................................................8
3.3.1 SYSTEM DESIGN....................................................................................................................9
3.3.2 IMPLEMENTATION................................................................................................................9
3.3.3 INTEGRATION AND TESTING.............................................................................................9
3.3.4 DEPLOYMENT OF THE SYSTEM.........................................................................................9
3.3.5 MAINTENANCE......................................................................................................................9
CHAPTER 4 : RESOURCES REQUIRED/BUDGET............................................................10
CHAPTER 5: TIME PLAN........................................................................................................11

ii
Table of Figures
Figure 1: waterfall model...........................................................................................................................8
Figure 2: context diagram........................................................................................................................16
Figure 3: admin use case..........................................................................................................................17
Figure 4: farmer use case.........................................................................................................................17
Figure 5: data flow diagram.....................................................................................................................18
Figure 6: sequence diagram.....................................................................................................................19
Figure 7: flowchart...................................................................................................................................20
Figure 8: Home screen.............................................................................................................................21
Figure 9: Admin dashboard......................................................................................................................21
Figure 10: info screen..............................................................................................................................21
Figure 11: user screen..............................................................................................................................21
Figure 12: cloud firestore model..............................................................................................................22
Figure 13: design validation.....................................................................................................................23
Figure 14: login UI code..........................................................................................................................25
Figure 15: login interface.........................................................................................................................25
Figure 16: sign in code.............................................................................................................................26
Figure 17: sign in interface......................................................................................................................26
Figure 18: pets interface code..................................................................................................................27
Figure 19: pets interface...........................................................................................................................27
Figure 20: admin ui code.........................................................................................................................28
Figure 21: admin ui..................................................................................................................................28
Figure 22: product ui code.......................................................................................................................29
Figure 23: product ui................................................................................................................................29
Figure 24: notification ui..........................................................................................................................30
Figure 25: transaction ui..........................................................................................................................30
Figure 26: data update ui..........................................................................................................................31
Figure 27: data update code.....................................................................................................................31

iii
 CHAPTER 1: INTRODUCTION
1.0 INTRODUCTION
Every farmer must be accountable for their progress of the farm products through the use the
current technologies and eliminate the use of legacy systems. This chapter focuses on the
background of the study, stating the problem, proposing the solution to the problem states its aim
and objectives and gives the scope and limitation of the problem.

1.1 BACKGROUND STUDY

In February 2021, Kenya exported coffee in the value of approximately 216 billion Kenyan
Shillings which is equivalent to $19.9 US dollars. From this statistic it clearly shows that many
coffee farmers in Kericho County are now shifting their focus into the production of coffee to
meet there daily needs as a source of income. The numbers of coffee plantations are increasing
annually as well as the branches of coffee factories. Several measures are carried out in this
organization to ensure that their achievements as a society will always grow positively.
However, despite the measures put in place by these organizations to cater for farmer’s interest
and satisfactions several challenges are encountered in each and every year. Farmers just buy
seedlings and plant them without taking into account the type of variety suitable for their area.
Even though factory board members conduct educational cinemas concerning measures of taking
care of their crops, most farmers don’t either attend the meetings or information doesn’t reach
them on time. The net weight of weight at the collection center some farmers like to be kept
private and confidential however, records of coffee factories in Kericho County are processed
manually on a paper sheet. These files can easily be accessed and an individual can alter them for
their personal gain. If against these old file system of storing data is misplaced or stolen, then the
data cannot be retrieved. With the advancement in technology our daily routine daily activities
we use our mobile phones in things like carried out transactions and sending and receiving
information thus saving us on time and money. The coffee mobile application will offer
accessibility and convenient to many farmers as well as complement the current data processing
methods and sending of notification messages to farmers.

1.2 PROBLEM STATEMENT

The methods of keep records are done manually by use paper where duplicate data may be
entered. If the paper files are misplaced no retrieval of data can be made and there is also a very
high chance of it being corrupted by unauthorized personnel. The farmers can receive important
updates from the coffee member board for instance when meeting are called few people who got
the message will attend because this information is passed through posters and if lucky some are
informed by their colleagues. Farmers do not have enough knowledge needed in taking care of
their coffee crops from diseases and favorable weather conditions for their crops. Farmers find it

1
difficult to keep the records to evaluate their performance since they have to sum up their total
kilograms from the receipt given when their coffee is weighed.

1.3 PROPOSED SOLUTION

The proposed mobile application will be able to provide better storage of records mechanism. All
the information passed by the factory committee will reach members in the appropriate time.
Farmers will be in a position to purchase farm equipment through their mobile phones. All the
educative measures involving improving the quality of coffee will be available to farmers at all
times whenever needed. The old system way of storing the farmers’ records will be access and
stored in a database system. Farmers will visualize the progress of their produce. Application
software will provide improved security mechanism against unauthorized access of the data.

1.3.1 AIM OF THE PROJECT

The aim of this study is to develop mobile application software which enables farmers in keeping
their records and all their services will be digitized instead of manual based systems. The
administrator will enter farmer’s details which are then stored in a secure database.
1.3.2 OBJECTIVES
1. To enable farmers register for the coffee society membership.
2. To enable users view their cumulative net weight
3. To learn about coffee controls and diseases affecting coffee
4. Purchase farm inputs through the mobile phone

1.4 SIGNIFICANCE OF THE PROJECT

1. The application software shall generate timely notifications
2. In case of the computer crush data backup and data setup allows data recovery
3. The application will be able to maintain and assures the consistency, accuracy and
reliability of data
4. Application software will be secured. This is obtained by use of password encryption to
protect data against unauthorized access or corruption to ensure data integrity
5. Since the current system data entry is done manually by use of paper it is slower hence
the proposed system will record and update data in a real time

2
1.5 SCOPE AND LIMITATION OF THE STUDY
The application software is built in such a way that it should suits for all type of coffee
factories in the future. So for that reason every effort is taken to implement this project in the
organizations and then on successful implementation will target other coffee factories. Coffee
factory application software project’s codes and scripts will download free. This software
application is useful for coffee farmers for managing daily activities e.g. keeping their
records with ease, purchasing farm inputs and receiving notifications from the factory stuffs.
This study will be conducted on four of these areas in Kericho County; Kimologit, Siret,
Lesirwo and Kokwet coffee factory where coffee is carried out and actively participated 85
percent between August – December 2021. The project will be limited to farmers to farmers
who have access to smart phones and with capability to operate them.

3
 CHAPTER TWO: LITERATURE REVIEW
2.0 Introduction
Kenyan coffee is grown on an estimated total area of 115,570ha in 32 counties out of a total of
47 counties in the country. The country has a dual production system with about 3,000 large
estates and over 700,000 smallholder growers. Introduced in the end of the 1800s by the colonial
government, coffee already played a crucial role in the economy of the country by the time of its
independence in 1963. The sole type of coffee produced in the country is Arabica, which is
planted during the rainy season from April to October with two harvest periods (from April to
June and from October to December). Coffee is grown without shade and the average yield is
estimated at 302kg/ha for smallholder farms and 556kg/ha for estate farms. The annual average
production is below 900,000 bags. After harvest, farmers deliver their cherries to their primary
societies for processing. The time frame until farmers are paid is largely dependent on the
efficiency of the marketing agents and the availability of buyers. Cooperative societies are
required by law to pay farmers at least 80% of the total upon delivery of their cherries. However,
cherry repayment rates differ from region to region, ranging from 84.6% to 10.2%.

2.1 Literature Review

According to the International Organization for Standardization (ISO) (2000), Quality is
described as "the ability of a set of inherent characteristics of a product, system or process to
fulfill requirement of customers and other interested parties". These inherent characteristics can
also be called "attributes. For coffee, the definition of quality and the attributes considered have
probably evolved through the centuries. But nowadays, this definition varies along the
production-to-consumer chain (Leroy et al., 2006). At the farmer level, coffee quality is a
combination of production level, price and easiness of culture; at the exporter or importer level,
coffee quality is linked to bean size, lack of defects and regularity of provision, tonnage
available, physical characteristics and price; at the roaster level, coffee quality depends on
moisture content, stability of the characteristics, origin, price, biochemical compounds and
organoleptic quality (Leroy etal., 2006). It should be noted that each consumer market or country
may define its own organoleptic qualities; at the consumer level: coffee quality deals with price,
taste and flavor, effects on health and alertness, geographical origin, environmental and
sociological aspects (ISO, 2000). More specifically, ISO (2004a) defined a standard for green
coffee quality (ISO 9116 standard) as, it requires several pieces of information, like the
geographical and botanic origins of the coffee, the harvest year, the moisture content, the total
defects, the proportion of insect-damaged beans and the bean size. These ISO standards define
methods of measurements for several of these qualities such as, defects, moisture content, bean
size, some chemical compounds and preparation of samples to perform cup tasting. According to
the definition of quality and standards authority of Ethiopia (QSAE) (2000) a quality is
4
conformance with requirements or fitness for use in which the parties involved in the industry
(customer, processor, supplier, etc) should agree on the requirements and the requirements
should be clear to all stake holders involved in the process. On the other hand, Coffee quality
control and auction Center was established with a key objective of maintaining coffee quality
control, which in turn facilitates the coffee marketing system to be standard based, and for the
betterment or proper functioning of the long coffee supply chain of Ethiopia (Endale, 2008).
Mulugeta (1999) reported that access to credit, farm size, supplementary inputs, technical and
institutional support like the extension service determine the adoption of technologies.
Furthermore, Negussieet al. (2008) reported adoption of improved varieties, literacy, visit and
proximity to research center positively influenced farmers’ perception. Many evidences show
that female households have less access to improved technologies, credit and extension service
(Ellis and Mudhara, 1995). On the other hand, male-headed households have better access for
information than female households that helps for adoption of improved agricultural
technologies. According to the findings of Negussieet al. (2008), only 26% of the female-headed
households had access to improved coffee varieties as compared to 88% for the male-headed and
87% of the male respondents ever used fertilizer as compared to 55% for females in survey made
in Gomma woreda.
The International Coffee Organization (ICO, 2001) implemented a Coffee Quality Improvement
Program (CQIP) with recommendation to exporting countries. It is not recommended to export
coffee with the characteristics having foreign material of non-coffee origin; foreign materials of
non-bean origin, such as pieces of parchment or husk; abnormal beans for shape regularity or
integrity; abnormal beans for visual appearance, such as black beans; abnormal beans for taste of
the cup after proper roasting and brewing. Bean size, which is usually determined by screening,
is of particular importance to roasters since bean of the same size would be expected to roast
uniformly. In addition, these size and shape differences of coffee beans were influenced by
botanical variety and environmental growth circumstances (Sivetz and Dosrosiier, 1979;
EAFCA, 2008)

2.2 CONCLUSION
Kenyan coffee quality become deteriorates from time to time. As many researches indicated that
this deterioration is because of soil and climatic factors, genetic factors, pre harvest practices,
harvesting method and timing, post-harvest process, storage and social fa-tor. The environment
has a strong influence on coffee quality (Altitude, daily temperature fluctuations, amount and
distribution of rainfall and the physical and chemical characteristics of the soil) are very
important factors. Soil also has its own role in quality of coffee. An excess of nitrogen increases
the caffeine content, resulting in a more bitter taste of the brew. High concentration of calcium
(>0.11%) and potassium (>1.75%) in the beans is associated with a bitter and “hard” taste.
nitrogen and phosphorous negatively correlated with coffee quality. In addition, calcium
negatively correlated with the quality of coffee. Soil pH was noted to indirectly associate with
the character and acidity of coffee. In pre harvest processes use of decomposed coffee husk,

5
pruning practice, shade, control of common diseases and weeds etc. has important role in quality
of coffee. Almost all Ethiopian coffee farmers do not use fertilizers except on commercial farms.
But decomposed coffee husk at a rate of 10-ton ha-1 (4 kg tree-1 on dry weight basis) was found
to be superior in terms of yield performance of coffee trees. Pruning practice has its own role in
the quality of coffee. Shade also improved the appearance of green and roasted coffee beans as
well as the acidity and body of the brew. In the other hand the Pests and diseases attacks and
weed is found to be a serious problem which reduces the productivity and quality of coffee in
most area. Maturity also has a strong influence on coffee quality. Overripe cherries and under rip
cherries are not recommended for harvesting.

6
 CHAPTER THREE: METHODOLOGY
3.0 Research methodology/Research design used.
This Chapter introduces techniques, methods and strategies used in the research. The research
design is defined with the scope and the limitations of the design. This section also looks into the
analysis of methods that are used in the research. The most suitable design and data collection
are also highlighted.
This research uses a hybrid data collection method mixing both qualitative and quantitative
methods. Quantitative research is basically measurement of quantity/amount involving
generation of data in quantitative form which is subjected to quantitative analysis. The research
mainly uses an inferential quantitative research method because of the sample population.
The research design is both analytical and applied research methods. The research uses already
available facts and information from coffee factory hence an analytical research. The research
aims at solving the information gap in the coffee farmers by providing data collection application
software for effectively collecting the information. The research design method therefore is
action or applied.

3.1 Data collection methods used.

3.1.0. Observation
This is a method that provides first-hand information about the real problems encountered by the
coffee farmers as they take their coffee to the factories. Observations will be conducted in these
locations in Kericho County; Siret, Lesirwo, Kokwet and Kimologit to identify the poor record
keeping, accountability issues and other related problems.

3.1.1. Questionnaires
For this method, open ended questionnaire questions will be used to determine the coffee
farmer’s perception and organization’s perception on the proposed coffee application software.
The study captured the attitude knowledge, and practice of the farmer as undergo all the
activities.
For the prototype testing stage of this project, questionnaires were used in a survey on the use of
the coffee application software to improve organizations’ participation with the aim of
establishing the system that is computerized to enable farmer and coffee factories improve their
records and services, in order to digitize their work. This will help them in solving their problems
through the use of the developed prototype solutions.

3.1.2. Interviews
Interview is used to gather some information regarding coffee application software. This method
allows the researcher to gather the data from the individual or group who are generally the
current organizations or users of the existing system or potential users of the proposed system.
The farmers or organizations can respond positively or negatively since the proposed software

7
has an impact and differences in some way. Interviews will be conducted with the organizations,
farmers and with the public to find facts, verify facts, clarify facts, generate interest and identify
ideas and opinions. A set of interview questions will be prepared to ask the interviewee to
respond to a series of questions.
The interview is divided into open and closed-ended questions so that sufficient information can
be gathered.

3.2 SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)

A life cycle is the sequence in which a project specifies, prototypes, designs, implements, tests,
and maintains a piece of software. Explicit recognition of a life cycle encourages development
teams to address development issues at the appropriate time.
Waterfall model will be used in the design of the proposed coffee mobile application. Waterfall
model in an SDLC framework which illustrates the software development process in a linear
sequential flow, this means that any phase in the development process begins only if the previous
phase is complete. In this waterfall model, the phases do not overlap.

Figure 1: waterfall model

3.3 REQUIREMENT DEFINITION

The first phase in the waterfall model and it involves understanding what services are required
from coffee application together with its operational constraints.

8
3.3.1 SYSTEM DESIGN
The requirement specifications from the first phase are studied in this phase and system design is
prepared. System design helps in specifying hardware and system requirements and also helps in
defining overall application architecture. Design activities carried out here involves the use of
sequence diagrams, class diagrams and context diagrams.

3.3.2 IMPLEMENTATION
With inputs from system design, the system is first developed in small programs called units,
which are integrated into the next phase. Each unit is developed and tested for its functionality
which is referred as unit testing.
1. Programming tools
a) Ide
the ide used is android studio together with visual studio code Visual Studio Code comes
equipped with a huge plugin system and functionalities. Flutter plugin should be installed
when VS is used.
b) Dart

Dart is completely open source with a clean license. Dart is programming language used to code
Flutter app.
c) Flutter
User Interface toolkit used to craft apps for mobile from a single codebase.
2. Database
a) Cloud Firestore. Flexible, scalable NOSQL cloud database to store and sync data.

3.3.3 INTEGRATION AND TESTING

All the units developed in the implementation phase are integrated into the system into a system
after testing each unit. The software designed, needs to go through constant software testing to
find out if there are any flaws or errors. Testing is done so that the client does not face any
problem during the installation of the software.

3.3.4 DEPLOYMENT OF THE SYSTEM

Once the functional and non-functional testing is done, the product is deployed in the customer
environment or released into the market.

3.3.5 MAINTENANCE
This step occurs after installation, and involves making modification to the system or the
individual component to alter attributes or improve performance. These modifications arise due
to change requests initiated by the customer, or defects uncovered during live use of the system.
The client is provided with regular maintenance and support for the developed software.

9
CHAPTER 4: RESOURCES REQUIRED/BUDGET
The following is the estimated cost for which the finding is required. This includes all expenses
that will be incurred and inclusive of the implementation cost. It also includes all indirect cost
that allows the project to bear a portion of the administrative cost of the day-to-day operations.

ITEM DESCRIPTION COST(KSH)

1 laptop 30,000

Traveling expenses 1,000

Stationary and printing 500

Data Bundles 3,000

Total 37,000

Budgets table

Project Resources

1. Windows
2. Xampp
3. Visual Studio Code
4. Browser

10
 CHAPTER 5: TIME PLAN
Time duration 12 -19 20 – 26 - 29 - 1-2 3-4 5-25 26 21 27- 01 15
Sep 25 28 31 Oct Oct Oct Oct- Nov 28 Jan Mar
Sept Sept Sept 20 Nov – -
Nov 15 05
Mar Apr
Background of
the
study ,problem
statement draft
Proposed
solution, aims of
the objectives
and significance
of the project
analysis
Literature review
and research of
the industry
Methodology
deliberation and
drafting
Budget draft,
analysis and
preparation
Proposal
consolidation
and submission
System analysis

11
and requirements
specification
System Design

Submission of
project document
Oral presentation

Coding (System
implementation)
Testing and
maintenance
Time Plan.

REFERENCES (APA REFERENCING SYSTEM)

1. CRF (1999), Strategies to enhance coffee production in Kenya. Coffee Research

Foundation (CRF), technical committee report, Ruiru, 109p.
2. Karanja, A.M. (2002a), Liberalisation and smallholder agricultural development. A case
study of coffee farms in Kenya. Ph.D. thesis, Wageningen University. ISBN 90-5808-
603-8
3. Mugenda M. O. and Mugenda A. (1999), Research Methods: Qualitative and Quantitative
Approaches, African Centre for Technology Studies, Nairobi, Kenya. Mugenda, O.M. and
Mugenda, A.G. (2003), Research Methods, Quantitative & Qualitative Approaches, Acts
Press, Nairobi
4. Nigatu, T. (2009). Qualitative Data Analysis. Ethiopia: African Medical & Research
Foundation.
5. Omae, M. O., Langat, P. K., & Ndung’u, E. N. (2015). Mobile Subscription, Penetration
and Coverage Trends in Kenya’s Telecommunication Sector. International Journal of
Advanced Research in Artificial Intelligence, Vol. 4, No.1.

6. Ostapowicz, K., Ziółkowska, E., Kaim, D., & Kozak, J. (2011). Knowledge transfer
between science and practice for sustainable development. Mountain.TRIP project.
7. Shawish, A., & Salama, M. (2014). Cloud Computing: Paradigms and Technologies.
Springer-Verlag Berlin Heidelberg.
8. Sidhu, N. (2015). The Secret Sauce to Great Mobile Apps. Retrieved from Reality Check:
http://www.softwareag.com/blog/reality_check/index.php/soa-what/the-secret-sauce-to-
great-mobile-apps/

12
9. Prodolliet, J. 2004. Coffee Quality Assurance: Current Tools and Perspectives. In:
20thInternational Scientific Colloquium on Coffee. Bangalore. pp. 120-145
10. Mylopoulos, J. (2004). Information Systems Analysis and Design. Toronto:
University of Toronto

13