CENTER NAME: RIFTVALLEY TECHNICAL TRAINING INSTITUTE

DEPARTMENT OF INFORMATION AND COMMUNICATION TECHNOLOGY

COURSE CODE: 2920

COURSE NAME: DIPLOMA IN INFORMATION COMMMUNICATION TECHNOGY
PROJECT TITLE

PRESENED BY:

ROTICH IAN KIBET

INDEX NO: 5342010204

PRESENTED TO:
The Kenya National Examination Council (KNEC), In Partial Fulfilment Required for The
Award of Diploma in Information and Communication Technology.

SUPERVISOR: MR. KITUZI GRAHAM MILLA

SERIES: NOVEMBER 2022

DATE OF SUBMISSION: 20TH JUNE 2022

Declaration

I hereby declare that to the best of my knowledge no part of this work has ever been submitted for the
award of any qualification of Diploma in Information Communication and Technology.

Student
Name: ROTICH IAN KIBET
Date: 20TH JUNE 2022

Sign: …………………………………………………………………………………

Supervisor
MR. KITUZI GRAHAM MILLA
Date: ………………………………………………………………………………

Sign: …………………………………………………………………………………

ii
Dedication
To my beloved parents, brothers and sisters who has always supported me financially and
emotionally as I endeavored to achieve my goals as a student. May God bless them abundantly.

iii
Acknowledgment

I give thanks to the almighty God for giving me all strength and courage to enable me to
successfully carry on with this project. I would like also to thank my parents for their support,
not forgetting my supervisor who gave guidance and entire of IT center through provision of
resources that offered aid to my project.

iv
 ABSTRACT

Pig production is one of the fastest growing livestock sectors in Kenya and this trend is expected
to continue over the coming years. Majority of the population in central Kenya rear pigs as an
integral part of their livelihood. There is a growing demand for pork and pig products all over
Kenya some of which is met from the imports from other countries this is due to the low
production in the country due to the use of the poor traditional management methods. These
methods have made it difficult for farmers to manage feeds, prepare measures for both planned
and unplanned veterinary health care, breeding of good breeding boars and detection and
prevention of diseases in the farms. The initial studies and research have all concluded that the
traditional methods of management have proved to be ineffective and expensive and thus a raised
a need for a different approach to management of these farms if production is to be increased,
risks reduced significantly and profit margins increased abundantly. The proposed system allows
the farm managers or since it is very easy to use, the farmers, to tackle all these challenges and
maximize their production with the ease of management especially with the growing numbers of
the pigs in a farm. The evaluation of the study shows that the Pig Farm Management System
(PFMS) is very feasible in Kenyan settings as more citizens are now appreciating farming as an
alternative for raising their livelihood and the government is in support of the farming sector so
there is now more market to the pig products than ever before and it is expected to grow even
further.

v
Contents
DECLARATION...........................................................................................................................................................II

DEDICATION..............................................................................................................................................................III

ACKNOWLEDGMENT..............................................................................................................................................IV

CHAPTER ONE.............................................................................................................................................................1

BACKGROUND INFORMATION...........................................................................................................................1

STATEMENT OF THE PROBLEM..........................................................................................................................2

AIMS AND OBJECTIVES........................................................................................................................................2

SIGNIFICANCE OF THE STUDY...........................................................................................................................2

SCOPE AND LIMITATIONS...................................................................................................................................3

CHAPTER TWO............................................................................................................................................................4

LITERATURE REVIEW...........................................................................................................................................4

INTRODUCTION......................................................................................................................................................4

FINDINGS AND SUMMARY..................................................................................................................................5

ANALYSIS OF THE PROPOSED SYSTEM...........................................................................................................5

CONCLUSION..........................................................................................................................................................6

CHAPTER THREE........................................................................................................................................................7

SYSTEM ANALYSIS AND METHODOLOGY......................................................................................................7

ANALYSIS OF THE EXISTING SYSTEM.............................................................................................................8

REQUIREMENT DEFINITIONS..............................................................................................................................8

METHODS OF INFORMATION GATHERING.....................................................................................................8

OBSERVATION........................................................................................................................................................8

INTERVIEWS............................................................................................................................................................8

LITERATURE REVIEW...........................................................................................................................................9

SYSTEM DESIGN.....................................................................................................................................................9

SYSTEM DESIGN...................................................................................................................................................10

THE DATABASE....................................................................................................................................................10

NEW.........................................................................................................................................................................11

LOGIN FORM.........................................................................................................................................................12

vi
 BREED.....................................................................................................................................................................12

PIGS.........................................................................................................................................................................12

QUARANTINE........................................................................................................................................................13

THE FORMS............................................................................................................................................................14

THE SUMMARY PANEL.......................................................................................................................................14

USER INTERFACE DESIGN.................................................................................................................................14

HELP SYSTEM DESIGN........................................................................................................................................14

TESTING DESIGN......................................................................................................................................................15

TESTING.................................................................................................................................................................15

PHASES...................................................................................................................................................................15

CASE DIAGRAM....................................................................................................................................................16

DATABASE TEST..................................................................................................................................................17

INQUIRY SYSTEM................................................................................................................................................17

DISPLAY SYSTEM................................................................................................................................................18

REQUIREMENTS TRACEABILITY.....................................................................................................................18

USING THE BACK-END.......................................................................................................................................19

MANAGING ADMIN.............................................................................................................................................20

PIG CATEGORY AND BREED TYPE..................................................................................................................20

MANAGE THE PIGS..............................................................................................................................................21

ADMIN LOGIN MENU..........................................................................................................................................22

TESTING SCHEDULE............................................................................................................................................22

RECORDING PROCEDURES................................................................................................................................23

HARDWARE AND SOFTWARE REQUIREMENTS...........................................................................................23

HARDWARE REQUIREMENTS...........................................................................................................................24

SOFTWARE REQUIREMENTS.............................................................................................................................24

CHAPTER FOUR.........................................................................................................................................................24

PROJECT TIME SCHEDULE.....................................................................................................................................24

TABLE FOR THE ACTIVITIES OF THE PROPOSED SYSTEM........................................................................25

GANNT CHART......................................................................................................................................................26

vii
 ADVANTAGES OF GANTT CHARTS.................................................................................................................26

DISADVANTAGES OF GANTT CHART.............................................................................................................26

GANT CHART FOR THE DEVELOPMENT OF LEARNER AID SYSTEM......................................................27

FUTURE RECOMMENDATIONS.........................................................................................................................28

PERSONAL REFLECTION....................................................................................................................................28

ACQUIRING PROGRAMMING SKILLS..............................................................................................................28

CONCLUDING REMARKS...................................................................................................................................29

REFERENCES.............................................................................................................................................................30

BIBLIOGRAPHY.........................................................................................................................................................30

APPENDICES:.............................................................................................................................................................31

DASHBOARD CODE.............................................................................................................................................31

viii
CHAPTER ONE
BACKGROUND INFORMATION

In Kenya over the years’ animal and farm production are sustainable source of income and
source of food. Hence people have a vast number of breeding of animals this includes pig
farming which is growing annually.

The pig production is one of the fastest growing livestock sectors in Kenya and this trend is
expected to continue over the coming years. Majority of the population in central Kenya rear
pigs as an integral part of their livelihood. There is a growing demand for pork and pig products
all over Kenya some of which is met from the imports from other countries this is due to the low
production in the country due to the use of the poor traditional management methods. These
methods have made it difficult for farmers to manage feeds, prepare measures for both planned
and unplanned veterinary health care, breeding of good breeding boars and detection and
prevention of diseases in the farms.

The initial studies and research have all concluded that the traditional methods of management
have proved to be ineffective and expensive and thus a raised a need for a different approach to
management of these farms if production is to be increased, risks reduced significantly and profit
margins increased abundantly. The proposed system allows the farm managers or since it is very
easy to use, the farmers, to tackle all these challenges and maximize their production with the
ease of management especially with the growing numbers of the pigs in a farm.

The evaluation of the study shows that the Pig Farm Management System (PFMS) is very
feasible in Kenyan settings as more citizens are now appreciating farming as an alternative for
raising their livelihood and the government is in support of the farming sector so there is now
more market to the pig products than ever before and it is expected to grow even further.
 STATEMENT OF THE PROBLEM

The following problems have been addressed from the study conducted:

1. Pest and diseases attacking the animal

2. Lack of proper maintenance of the animals.
3. Unemployment of many individuals and inefficient production.
4. Lack of skills and knowledge in the Pig Farming sector.

AIMS AND OBJECTIVES

The Pig Farm Management System described in this document has been designed to fill a
specific niche in the pig farming to help the farmers control, market, and to create equipped
structures in the sector in having custom software designed specifically for them. The system,
which is highly customizable, allows the farmers to easily manage the site content, most
importantly the management of the markets and the pigs, themselves through a very intuitive
graphical interface.

The website, which is the only component seen by the pig farmers, is then built dynamically
based on the current state of the system, so any changes made are reflected in real time. Visitors
to the site, once registered, are able to monitor the pigs in a farm, this is by helping identify the
young from the old, the new, the sick and those ready for the market also to provide timely
reports on the progress of the farm whether daily, weekly, monthly or yearly through the farm
management reports and to promptly retrieved and displayed in an easily readable format for
efficient processing.

2
 SIGNIFICANCE OF THE STUDY

The purpose of this document is to provide in-depth descriptions of design and implementation
details of the system, as well as descriptions of all available functionality and plans for evolution.
In addition, user manuals and trouble-shooting tips have been included for all three components
to give the reader a clear idea of intended typical use cases for the system.

The site greatly lightens the load on the user end, as the entire process of navigation is
automated. Once you open the homepage, it is placed into the database and then retrieved, in
pretty much real-time, by an admin on the farm website end. Within this website, there is display
of the types of pigs and their breeds, care and maintenance of piglets, breeding management,
feeding management, housing, disease and healthcare and other management practices, in a
concise and easy to read manner.

SCOPE AND LIMITATIONS

The Website is based on the requirements needed to be run in the Country. However this site
won’t cover all parts of the country since it is mainly build for pig farms and hence not everyone
has access to the internet.
The following are the limitations:

1. Internet: It might require constant supply of internet connection

2. Time: It is time consuming due to addition of it.
3. Electricity: It requires constant supply of electricity to function.

3
CHAPTER TWO
LITERATURE REVIEW

INTRODUCTION

In the ancient days’ computers weren’t existence the processing data were done manually. But
when computer was introduced, the society became liveliest than before. Every institution,
organization, homes, offices changes from their old manual methods of data processing to a
computerized one. One could clearly see that the computer system is so much demand by people
because of its characteristics which includes:

1. Speed of processing data

2. Accuracy
3. Capacity
4. Storage speed
5. Reliability
6. Flexibility
In some developing countries like ours (KENYA) the computer came into existence in
the 1970’s and was sued by few organizations that could afford to define the system but in the alt
70’s and early 80’s more public/private organization started using the system. A clear

4
investigation shows that computer is the heart-beat of most business. Almost every organization
has one or two computer in order to improve their services.

By the way what is the system called computer all about? The computer system has been
defined by many in different ways. Collins (1988) comprehensive directive of computing
defines a computer as a machine that receives stores and process data quickly according to a
stored program.

Findings and summary

The respondents were categorized into several factors, such as type, age, breed, income.

Breed

Large White The most raised pig breed in Kenya. Landrace White breed, elongated and lean
conformation with hanging ears and short legs. Duroc Resistant, rustic and adaptable breed.
Pertain It is a not very prolific breed and has low growth, but produces very tasty lean meat and
gives good hams. Berkshire It has black fur with some white or white mottled spots. Hampshire
and Vietnamese Pot-bellied and many more breeds.

Income

In Kenya from 1 pig, you can get a net profit of ksh1000 – 5000 after half a year of farming
depending on how the farm sell the pig’s meat. 1 Kilogram pork is usually sold for ksh500 –
600. Most often the price is around Ksh500 per Kilogram. After butchering and processing
market pig yield about 55% (+/- 10%) meat.

Analysis of the Proposed System

The Life Cycle Assessment method was used to analyses and compare the environmental
impacts of three systems of pig farming management: pig farming with pig
manure fertilization; pig farming using a manure treatment and a filtration method
involving the production of mineral-organic fertilizers from manure; and pig farming in

5
which 50% of the manure produced per y was used as fertilizer, and the other 50% was used
in the treatment and filtration method.

Conclusion

Pig farming throughout the world is going through significant changes. Public concern about
negative environmental effects of pig farming, as well as ethical issues such as animal welfare
and medicine use, are gaining importance. In order to cope with these developments, changes
in farm set up and management have to be considered, as they may result in an increase of cost
price. However, pig farmers must also provide their families with adequate income in
the long run and due to recent developments the income of pig farmers decreased in the last
decade. Therefore, the aspects of costs and revenues caused by changes in farming systems
and management have to be included in the decision before the changes are implemented.

The Animal Sciences Group, part of the Wageningen University and Research Centers, The
Netherlands is working on new farming systems, where environmental goals are realized,
animal welfare is secured and farmers get a profitable income. In order to combine these
aspects and calculate the expected technical and economic results of new systems, a
multidisciplinary model is designed: the so-called “Pig Farm Manager”. In this paper, this
model will be presented, including a case where a standard sow farm is compared with a high-
health-farm.

6
CHAPTER THREE
SYSTEM ANALYSIS AND METHODOLOGY

This basically deals with the way of data collection. This research work was conducted through
careful identification and selection of data that contains reliable information about the farm
structure.

Kenya Agriculture and Research Institute (KARI) was selected as a source of data for both
primary and secondary type of data. The research obtained the primary sources of data after
frequent visitations and interviews to the different departments of agriculture division. The
secondary data were collected from views and finding of some previously researched work and
comprehensive review of literature on the subject matters contained in textbooks, journals,
libraries, magazine, newspapers and internet. There are fact finding techniques employed during
the research work. A computer system can be seen as a collection of interrelated and
interdependent hardware and software component working together in a regular relation to
achieve a specific objective or goal.

Hardware is the computer component that can be seen and handled, while software are programs
designed by a programmer on manufacturer and use in the computer system with their associated
documentation if parallel therefore, system analysis can be defined as the study of system by
examining its parts and their relationship in order to recommend the specified business
requirement for the techniques used in obtaining data which is to be used in the course of the
project. This particular aspect of data which is been elaborated would include:

o the various methods of facts findings techniques

o Their merit and demerits.

7
o Amidst the various methods, one would be adopted and the reason for adoption would be
clearly stated.
After investigating the old system, a new system is proposed. It is here that the management
analyse situations that could trigger or set an action or process in motion, a change of the old
system which includes, what to do, how to do it, when to do it, to enhance the performance of the
system.

Analysis of the Existing System

System design is the process of defining the architecture, components, modules, interfaces, and
data for a system to satisfy specified requirements through system modelling. The design of the
system is not user friendly.
In other words, system design consists of design activities that produce system specifications
satisfying the functional requirements that were developed in the system analysis process.
System design specifies how the system will accomplish. System design is the structural
implementation of the system analysis.

REQUIREMENT DEFINITIONS

Preliminary investigation plays an important role in developing a satisfactory requirement. Its’ as

a result of thorough investigation of how the current or the existing system works using the facts
gathered at the preliminary investigation that leads to focusing on the possibility of replacing the
existing site or improving upon the existing sites. This task involves information gathering.

Methods of Information Gathering

Collection of fact is the act of getting and gathering information from various sources in order to
be able to compose the project. Data used for designing of the system were gathered through
several means. Therefore, the method used in the design and collections of information from
various sources are as follows:

8
Observation

This data collection method was specifically designed to collect data from all the farms that were
available within the Trans-Nzoia County.

Interviews

This is one of the primary ways of gathering information about the information system project.
This is done by asking questions but not the leading ones which would to the conclusion. Ask
them on the challenge of the new system. During interviewing, you gather facts, opinions, and
speculations and observe body language, emotions, and other signs of what people want and how
they access current system.

Interview technique has the following advantages:

 Researcher can know how people are interpreting questions

 Able to ask for more detail when needed
 Provide detailed data

Literature Review

This involved reading a lot of literature about the development of similar systems and their
operations. It also involved doing research on the internet and also visiting the library to read
about such systems to be able to understand their working. This helped to give more insight on
how similar systems had been developed previously and their various components and this
consequently will ease the development process.

 Collecting and analyzing existing materials on the project topic, written by different
expert.
 Studying the present system in detail and the organizational style.
 Knowing and understanding the input and output processes of the existing system.
 Primary data: This source has to do with the text book contacted for the development
of this project.

9
SYSTEM DESIGN

Therefore, system design could be seen as the specification of construction of a technical

computer based solution for the business requirement identified in as system analysis or system
design in the evaluation of solution and the specification of a detailed computer base solution.
This is called the physical design. The goal of this stage of system design to build a technical
blue print of how the proposed procedure being brought into a workable state. The purpose of
this designing state is the develop specification for each of the components of the system.
(hardware, software, procedure, people) the feasibility study stage, investigation, analysis, etc
services as input to the design processor, system design can be further directed into two namely.

(1) Logical design: this lays down the component of the system and the relationship to each
other as they would appear to the user of defines the input the output as well as the processing
functions to be performed, business procedures, models and control.
(2) Physical design: this is the process of translating the abstract logical model into the
specification technical design for the new system. It provides the actual specification for
software physical database, input and output media, manual procedure and specific control. This
proposed system is carefully constructed data flow diagrams.
SYSTEM DESIGN

The Database

The structure contains the database of the pig farm management system which contains the total
number of columns and rows. It has five structural databases which is: -
1. New
2. Admin
3. Breed
4. Pigs
5. Quarantine

10
New

It shows the new itemn that is entailled in the website newly entailed information.

11
Login Form

The login form is standard for a form of this type. It provides text fields for username and
password, which the user must enter before signing in. This form also gives the option for a user
to register for the site if they have not yet done so.

Breed

It shows the type of breeding pigs.

12
Pigs

The type and info of pigs.

Quarantine

The quarantine form, which is dynamically generated based on selections from the main menu.

13
The Forms

There are three types of forms in the menu management system - breed Forms, Category Forms,
and type Forms. The three forms are all similar, allowing the user to add, edit, and remove
information relevant to the selected item. Where they differ is in the specific fields that the user
is able to edit. After changes to any of the forms are saved, the necessary records in the database
are updated.

The summary panel

The summary panel, located on the left side of the screen, displays a list of all currently active
business, along with their type being sold and newly acquired. By changing the selected item in
this list, the user is able to control the contents of the panel.

User Interface Design

The user interface design principles can be broken into two groups. The interface in the web
application is designed to limit free form user input, using mostly drop down menus, radio
buttons and check boxes. This is done for two reasons – to simplify the ordering process as much
as possible, and to limit SQL injection attempts. Free form input is necessary in the menu

14
management component, however, as all of the values must be user supplied. The interface for
this component contains traditional forms comprised of text fields and corresponding labels,
along with save and discard buttons for each form.

Help System Design

Due to the form-based nature of the applications, the design of the help systems will be minimal.
In both the desktop and web applications, it will be accessed from the application’s main menu
and will open in a new window. Modelled after the typical help system design, it will be both
searchable and include a navigation tree highlighting common topics. There will be a help page
for each form type, describing the significance of each field on the page.

Testing Design
Testing

Phases

The structure of the system can be divided into three main logical components, plus the database,
which is invisible to the end user. Each of these components must be tested individually, and the
approaches which will be used for each component are described in the following sections.

Ordering
Customer Database Order Retrieval
System

Menu
Management

Type of the pig and weight

Employee

15
 Case Diagram

Home
<
<
Add Admin

Upd admin

Delete

Add breed
<<include all>> Login to the
System
Delete
sold

Admin Edit types

Add breed

Edit ctgr

16
 Delete ctgry

Exit

Log out

Database Test

Testing of the database component is very straightforward, and has actually already been mostly
completed. The database was the first component designed and before beginning work on any of
the applications, I wrote all of the SQL statements I expected to need and executed them directly,
essentially isolating the database, using the MySQL client. By doing this I was able to reveal,
and promptly fix a large percentage of the errors within the database itself.

Inquiry system

Testing of the inquiry system will be the most strenuous, as it is the component that will see the
highest frequency of use and will be exposed to the most users, which leads to a higher potential
of failure. Testing here will be divided into two phases. During normal use case testing I will
execute all of the functions available through the web interface using a broad spectrum of
reasonable values that a user would be expected to input. In addition to simply observing the in-
application effects, I will also be monitoring and inspecting the QUERY requests and responses
(using XAMMP) to make sure that everything is sent and received correctly.

In phase two I will perform exceptional use case testing, where I will artificially generate cases
that shouldn’t arise, but possibly could, and monitor how the system handles these cases. These
cases fall into one of two categories – when the mistake happens in the browser and the server
has to deal with it, or the other way around. I have tried to place appropriate checks on all values

17
being sent back and forth so the system realizes something is wrong before going to the database
and potentially changing the state of the system, but it will very important to see if there is
anything I have not accounted for

Display System

Of all the components, testing of the display system will be the simplest. Since it is simply an
interface to display the results of database queries and has no potential to change the state of the
system, the only thing that really needs to be tested is how the system responds when a result set
is not in the form it is expecting. This will be done by intentionally corrupting the database and
analysing the response of the order retrieval system.

Requirements Traceability

In the requirements document, I specified the following functional requirements:

For the Pig Management System:

 Create an account.
 Manage their account.
 Log in to the system.
 Navigate the menu.
 Customize options for a selected item.
 Add an item to their current ordeal.
For the display System:

 Add a new/update/delete vendor to/from the menu.

 Add a new/update/delete sold pig to/from the menu.

 Add a new/update/delete deceased to/from the menu.

 Add a new/update/delete option for a consumed food item.

 Update price for a given pig and other item.

18
  Update default options for a newly bought or piglet.

 Update additional information (description, photo, etc.) for a given pig type.

For the Order Retrieval System:

 Retrieve new orders from the database.

 Display the orders in an easily readable, graphical way.

 Mark an order as having been processed and remove it from the list of active orders.

In order to assure thorough testing, I will have to generate cases in which each of these functions
is performed, not just with a single input value, but an example of each possible class of input.
This may seem tedious, but is absolutely necessary since the system is so heavily dependent on
user input and must respond appropriately to anything the user may do. The good news is that
because the system was design to contain only the absolutely necessary functionality, the testing
of the different functions should flow smoothly into one another.

Using the Back-end

When the system is first installed, it contains no menu information. Therefore, the first step in
using the system is to add admin information. Start by launching the admin site URL.
Managing Admin

By clicking add admin button to add a new admin, then supply the name of the admin and click
“Save”. This adds the new admin user. If there will be multiple admins using the system, they
will be able to identify as new admin name will be displayed.

19
 Pig Category and breed type

Represents the pig type and the breed, you can add the new breed or delete move to the next
page, they will only click on the add category button as shown below.

20
 Manage the pigs

To edit pig details, select the pig you wish to modify and click on the Update button. From this
screen you can now modify the prices and default options for the selected item. Repeat this
process for all items you have added. Also the arrival date, the gender the pig weight and those
that have been quarantined.

21
 ADMIN LOGIN MENU

Figure above, shows the admin login area of the application. After a successful login supplying
the correct username and password, it opens into another page where the activities of the admin
module and pupil module are fully stipulated. The admin controls all the major activities of this
application.

Testing Schedule

Throughout all of the design and development phases, I have been performing unit tests on each
component, assuring that it works properly before introducing it into the rest of the system.. I
will begin by putting the system through its normal paces as a normal user would be expected to.
I will test the entire functionality of the system, but will do so following the normal logical flow,
and only providing reasonable values for user input.

22
Once I am happy with how the system performs for normal use cases, I will move on to testing
the exceptional use cases. These are the use cases that would never be encountered by the
average user, but, whether through confusion or malice, may come up. Two examples would be
adding hundreds of items to an order or attempting to supply an SQL statement as a login
credential.

In the final phase of testing, I will carry out stress and performance testing. In this phase, I will
bombard the system with an increasing number of HTTP requests and then measure response
times and see at what point things begin to break down.

Recording Procedures

The recording procedures I will use can be divided into two categories. For the use case testing,
the tests will be designed in a “Pass/Fail” manner, making recording the results very simple.
Each time a series of tests is run, the results will be recorded in a spreadsheet, where each
outcome can be identified by the name of the test case along with the execution date and time.

For the stress and performance testing, the procedure will be similar. However, since these tests
involve numerical results rather than simply “Pass/Fail”, I will be able to not only record the
results, but to also perform analysis (both numerically and graphically) on them to get a better
idea exactly what the numbers mean.

Hardware and Software Requirements

The testing to be performed will require no special hardware, but some specially designed
software may be used, particularly when performing stress testing. I plan on writing and utilizing
a multi-threaded PHP program to bombard the system with an increasing number of SQL
requests and then measure response times and see at what point things begin to break down.

HARDWARE REQUIREMENTS

 A minimum hard disk space of 20 Gigabytes (GB)

23
  RAM size of 4GB

 processor CPU

 monitor

 Mouse

 Keyboard

 Router for stable internet connection.

SOFTWARE REQUIREMENTS

 Operating systems such as, windows 8, Linux OS and Windows 10.

CHAPTER FOUR.

PROJECT TIME SCHEDULE

Activity Duration

Preliminary Description 30 days

Project proposal 10 days

Literature Review 21 days

Project plan 10 days

Functional specification 20 days

Software Design 30 days

24
 Project coding 30days

Project Testing 10 days

User manual/Documentation Through out

Table for the activities of the proposed system

ACTIVITY NO. ACTIVITY TIME PRECEDENTS

(WEEKS)
A Preliminary Description 1 -
B Project proposal 2 A

C Literature Review 1 B

D Project plan 3 C

E Functional specification 1 D

F Software Design 4 E

G Project coding 8 F

H Project Testing 1 G

I User manual/Documentation Throughout

GANNT CHART

Adequate time has been allocated in order to come up with The Online Food Website and
because of the available expertise in developing it, the specified deadline is dimmed realistic.
The time frame is shown in the Gantt chart below.

25
 Advantages of Gantt charts

1. It creates a picture of complexity – complex ideas can be easily understood when

presented diagrammatically.
2. It organizes your thoughts- A big problem can be handled by dividing it in to component
parts
3. It helps you to set realistic time frames –the bars on the chart indicate in which period a
particular task will be completed. This can help you get things in perspective properly.
4. It is highly visible – a larger version of it can be placed where everyone can see.

Disadvantages of Gantt chart

1. The size of bars does not indicate the amount of work

2. Gantt Charts can be complex in big projects.
3. They need to be constantly updated.
4. Difficult to see on one piece of paper.

Gant Chart for the Development of Learner Aid System

Gant Chart

26
 ACTIVITY

JAN FEB MAR APRIL MAY

Preliminary description

Literature Review

Project proposal

Project plan

Functional specification

Software Design

Project coding

Project testing

Documentation

Future Recommendations

In addition to the unfinished requirements, there are other possibilities of further

improving the project. The respondent of user acceptance testing also suggest some
improvement ideas. The improvements may include:

• Overcoming the limitations.

27
 • Secured payment system with various payment methods.

• Presenting graphical floor plan for table management and reservation.

• Adding support for pigs’ order delivery tracking.

• Advanced inventory control with material storage and expiry information.

• Managing customer loyalty membership and discount voucher.

• Converting the system to progressive web application.

Personal Reflection

I have gained some experiences and developed skills through the project. I also became aware of
some aspects which needs improvements.

Acquiring Research Skills

The literature review chapter required reviewing lots of journal articles and research
papers. By reading and reviewing journal articles, I have gained some knowledge about
how to write a journal paper in a structured way and how a research is conducted. It also
improved my presentation skills. I also become aware of my lacking on researching which
should be improved to be a better researcher.
Acquiring Programming Skills

To develop the application, I have to learn HTML and Bootstrap. Learning PHP made my
concept clearer. I have also gained some experiences on problem solving skills, as
sometimes I had to brainstorm, search and think for two or three days to solve a piece of
code that was not working. Sometimes it comes out a silly problem. Along with this, I
was not good in developing user interface.

Concluding Remarks

This project is for developing a web application for restaurant. For developing the
application, a systematic approach has been taken into account. Extreme Programming

28
method of agile development has been applied to develop the system. Along with this,
CSS has been used for modelling processes and data. The application has been developed
using PHP framework.

The project successfully implemented a working complex prototype of an online food

ordering system. The implemented prototype software has been fully tested to
demonstrate the quality and performance of the system. This report also documented all
the relevant research details and decision-makings processes. In summary, the project has
satisfied its objectives and fulfilled its purpose. I hope, the site can meet most of the
requirements of restaurant online ordering.

REFERENCES

Bibliography.
Ben-Zahia, M. A. and Jaluta, I. (2014) ‘Criteria for selecting software development models’, in.
2014 Global Summit on Computer Information Technology (GSCIT), pp. 1–6. doi:
10.1109/GSCIT.2014.6970099.

29
Bhaumik, S. (2015) Bootstrap Essentials. Birmingham, UK: Packt Publishing. Bounnady, K. et al.
(2016) ‘Comparison the processing speed between PHP and [Link]’, in. 2016 13th
International Conference on Electrical Engineering/Electronics, Computer,
Telecommunications and Information Technology (ECTI-CON), pp. 1–5. doi:
10.1109/ECTICon.2016.7561484.

Cheong, S. N., Chiew, W. W. and Yap, W. J. (2010) ‘Design and development of Multi-touchable
E-restaurant Management System’, in. 2010 International Conference on Science and Social
Research (CSSR 2010), IEEE, pp. 680–685. doi:
10.1109/CSSR.2010.5773867.

Das, R. and Saikia, L. P. (2016) ‘Comparison of Procedural PHP with Codeigniter and Laravel
Framework’, International Journal of Current Trends in Engineering & Research, 2(6).

Dawson, C. W. (2009) Projects in Computing and Information Systems: A Student’s Guide. Addison-
Wesley.

Dennis, A., Wixom, B. H. and Roth, R. M. (2012) Systems Analysis and Design. 5th Editon. John wiley &
sons.

Dhore, V. B. et al. (2014) ‘Digital Table Booking and Food Ordering System Using Android
Application’, International Journal of Emerging Engineering Research and Technology, 2(7), pp.
76–81.

Dockins, K. (2016) Design Patterns in PHP and Laravel. Apress.

Gayatri, P. V., Chaitanya, J. K. and Harikrishna, K. (2014) ‘Developing an Intelligent e-
Restaurant with a Menu Recommender for Customer-Centric Service using Wi-Fi Technology’,
International Journal of Computer Applications, 101(16).

Gerchev, I. (2017) ‘The 5 Most Popular Frontend Frameworks Compared’, SitePoint, 17 May.
Available at: [Link]

Gilmore, W. J. (2015) Easy Laravel 5: A Hands On Introduction Using a Real-World Project.

Leanpub. Available at: [Link]

Google (2017) Lighthouse, Google Developers. Available at:

[Link]

30
Gould, H. (2016) Systems Analysis and Design. 1st Edition. BookBoon. Available at:
[Link]

APPENDICES:
Dashboard code

<?php include 'setting/[Link]'; ?>

<?php include 'theme/[Link]'; ?>

<?php include 'theme/[Link]'; ?>

<?php include '[Link]'; ?>

<!-- !PAGE CONTENT! -->

<div class="w3-main" style="margin-left:300px;margin-top:43px;">

<!-- Header -->

<header class="w3-container" style="padding-top:22px">

<h5><b><i class="fa fa-dashboard"></i> My Dashboard</b></h5>

</header>

<?php include 'inc/[Link]'; ?>

<div class="w3-container" style="padding-top:22px">

<div class="w3-row">

31
 <h2>Recent Pigs</h2>

<div class="table-responsive">

<table class="table table-hover" id="table">

<thead>

<tr>

<th>S/N</th>

<th>Pig No.</th>

<th>Breed</th>

<th>Weight</th>

<th>Gender</th>

<th>Arrived</th>

<th>Desc.</th>

</tr>

</thead>

<tbody>

<?php

$qpi = $db->query("SELECT * FROM pigs ORDER BY id");

$result = $qpi->fetchAll(PDO::FETCH_OBJ);

$c = $qpi->rowCount();

foreach ($result as $j) {

$pigname = $j->pigno;

32
 $b_id = $j->breed_id;

$weight = $j->weight;

$gender = $j->gender;

$remark = $j->remark;

$arr = $j->arrived;

$k = $db->query("SELECT * FROM breed WHERE id = '$b_id' ");

$ks = $k->fetchAll(PDO::FETCH_OBJ);

foreach ($ks as $r) {

$bname = $r->name;

?>

<tr>

<td>

<?php for ($i=1; $i <= $c ; $i++) {

echo $i;

} ?>

</td>

<td><?php echo $pigname; ?></td>

<td><?php echo $bname; ?></td>

<td><?php echo $weight; ?></td>

<td><?php echo $gender; ?></td>

<td><?php echo $arr; ?></td>

33
 <td><?php echo $remark; ?></td>

</tr>

<?php

?>

</tbody>

</table>

</div>

</div>

</div>

</div>

<?php include 'theme/[Link]'; ?>

34