Introduction

Cafeteria is a type of food service location in which there is little or no waiting staff table service
which is started in 2003. a university student café location is also referred to as a dining hall .
Cafeterias are different from other in this project an attempt is made to design a computer system
for the woldia café that makes the management of recording student details for food usage much
easier. The objective of this software is to maintain the details of students, waiters and manager.
Through this system we provide facility of postpaid accounts for students . It has the features like
adding, viewing, editing of students , waiters and manager details. The Software powered by
student assures clear and efficient services to the university. This easy-to-operate system helps to
access and modify student details, provides efficient facility. The software is designed to provide
Reliable and error free information. Anyone having an account with the system can have access
to cafe by logging into the client machine using a given username and password. Students can
login only if they have sufficient identification card. Otherwise they will not to access the café
service at the administrator side. To ensure enhanced security student account creation, editing,
etc are available only at the administrator side. On successful login the user can load browser and
can have access to café service. The login time displayed on the login screen may help the
students manage their

Background about WDU cafeteria system

Student cafeteria is one of the services given in woldia university that has been started its
service in 2004E.C. In 2006E.C the university has established second campus in mersa and
agricultural students were taken to there. This leads the cafeteria system to have two café. I.e.
main campus and Mersa campus. Now at the time the WDU main campus has giving its
service for around 9000 students and on the other side Merssa campus gives service for 800
students. Many Campuses are using one card system such as ASTU, JMU and other
technology Universities in our country that have got successful result or benefit from the
system. Taking those campuses as an example the system will give more benefit for the
users’ especially after it will be advanced to one card system.

Statement of the problem

Through the time, the number of students in WDU is increasing. For this reason, it is difficult
to manage cafeteria system manually as efficiently as possible and to give an efficient service
for the students on time. So the main problem is how the system can give an effective service
up on time for the students and drawback the workload of the staff workers. It is difficult to
generate report, improper budget sharing, difficult to reject students with re-admission,
dismissal cases and students leaving campus for apprenticeship. When budget is not shared
 equally, food shortage will happen; and this in-turn leads to students’ riot This self-service
fast food café will be equipped with a user-friendly touch screen card reader, and software
for completing the process at the backend. For this system there will be a system
administrator who will have the rights to enter the menu with their current prevailing prices.
He/she can enter anytime in the system by a secured system password to change the menu
contents by adding or deleting an item. Now when the students enters to the cafe, he will
place his order with the help of the touch screen using the intuitive graphical user interface.
He/she will select from the food options according to his/her choice and the system will
display the payment amount he has to make once he has finished with his order. He will have
the option of paying the bill by cash, debit card or a credit card. The user will slide his card
and the system will check for the validity of the card and the payment will be made. A
receipt will be printed containing the order number and the order will be sent in the kitchen
for processing.

Objectives
General Objective
The general objective of this project is to develop online cafeteria management system for WDU.

Specific Objective
There are some specific activities to achieve the general objective; these are: Developing a
database that will store the users and students detail information.
 By analyzing and designing the system using UML language.  Create a separate
account for Administrator and students.
 Preparing view menu that students will sign in to the system and view or see what
menu will be prepared for the breakfast, lunch and dinner.
 Differentiate Non café students, special and café usage accounts.
 Develop attractive interface to navigate through the system for the users.
Scope of the project
 Study the effects of new system on order processing time,
 Study the effects of new system on waiting time for student,
 Understand the café load at peak times,
 A better user interface design to give high student QoE,
 Keeping the café management system up‐to‐date and
Limitation of the project
 It is known that cafeteria management system needs integration of both the hardware and
software applications.
 Hence, this project will only focus on the software development part (i.e. register new
students, Check whether students eaten or not, view no of students taken/not their meal,
inactivate and activate enrolling students, search student’s file, generate report and other
student related activities) and doesn’t include the hardware part due to financial cost.
 The main limitation of this project was time for preparing, writing the document and
financial cost for including hardware part, printing, binding the whole document.

significant of the project

 This will minimize the number of employees at the back of the counter.
 The system will help to reduce the cost of labor.
 The system will be less probable to make mistake, since it?s a machine.
 This will avoid long queues at the counter due to the speed of execution and number of
optimum screens to accommodate the maximum throughput.
 The system will be available 24 hours for 365 days, because the machine is not going to
take any sick or vacation leave.
 Easy to search students profile or information.
 Each student uses their budget properly.
 It will be easy to separate readmission and dismissal students based up on the academic
status.
 Data will be accurately securable for the users.
 It will be easy to have detail information of the Non café from that of the café usage.
 Also it will be easy to have detail information about the special cases students and it will
be fair for all students to being a special case usage by only fulfilling the rule of form
having a reason.
 It will be easy to post if there is a problem with in the café to shift the time back.
 It will save time and resource like papers filling to be Non café.
 Easy to generate a report daily, weekly or monthly

Methodology and tools

Methods
method of data collection
Throughout the work of this project, we use different methods for collecting information as well
as gathering data. Those are:
Interview:
we have gone to the WDU cafeteria administrator’s office and interviewed him.
Discussion:
this is one of the technique in which we have seated together and discussed on the project how
we can perform the system.
Observation:
assessing and analyzing the overall system has been carried out by observing the current working
systemize we have gone to WDU cafeteria office and search (seen) how their system works. And
we have conducted physical observation to see how data are handled and information of
customers is kept in the system.
Referring documents:
for the purpose of how customers can be served and what type in addition to this we have
searched more data from internet.

Development Tools
 MS office 2022
 Window11 pro
 Hard drive .
Implementation tools
There are some tools that we have used for developing the system. These are:-
 HTML: for describing web pages and interface application.
 JavaScript: designed to add interactivity to HTML through validation.
 CSS: we have used it add style to html elements for decoration and attractively.
 PHP: we used it as a server script because of it run on different platform like windows,
and on other servers like Xampp , Apache server.
 MY SQL server: for developing database of the system.
FEASIBILITY STUDY

During system analysis, the feasibility study of the new system is to be carried out. This is to
ensure that new system is not a burden to the campus. This study can be categorized into three
types. They are:
  ECONOMIC FEASIBILITY STUDY
This study is carried out to check the economic impact that the system will have on the campus.
The amount of fund that the campus can pour into the research and development of system is
limited, the expenditures must be justified. Thus the developed system was well within the
budget and this was achieved because most of the technologies used are freely available. Only
customized products had to be purchased.
 TECHNICAL FEASIBILITY STUDY
This study is carried out to check the technical facility, that is, the technical requirements of the
system. Any system developed must not have a high demand on the available technical
resources. This developed system has modest technical requirements, as only minimal or null
changes are required for implementing this system.
 SOCIAL FEASIBILITY STUDY
This aspect of study is to check the level of acceptance of the system by the user. This includes
the process of training the system but must accept it as a necessity. The levels of acceptance by
the users solely depend on the methods that are employed to educate the user about the system
and make him familiar with it. His level of confidence must be raised so that he is also able to
make some constructive criticism, which is welcomed, as he is the final user of the system.

System requirement
 The concept of cafe management system to be developed is to reduce manual efforts in
the café ordering system.
 It is important that such system is deployed in a real environment and hence the
requirements are not abstract and are collected from the real setup.

Functional requirements

Functional requirement is a description of activities and services a system must provide

and exactly what the system must do. These requirements describe the interactions
between the system and its environment independent of its implementation. The
environment includes the user and any other external system with which the system
interacts. Any system has its own users as a main role player. Therefore, it is crucial to
meet the users need. So the new system provides (include) the following service:
 Register students.
 Search student’s data.
  Check student’s eaten / not.
 View student who have eat his/her meal.
 Deactivate students.
 Activate students.
 View daily menus.
 Registers special case students.
 Registers Non café usage
 Create account.
 Change account.
 Generate a report monthly or yearly

student
o The student who would use the café management system is the most important.
o The student should be attached to a seat from where he/she should be able to
access the café management system.
o Once the system is accessible to the student, he/she can switch the language of
his/her choice on any page.
o The student can access the entire menu and can choose one or more food/drink
items of his/her choice with a restriction.
o The student can order the selected items
o The student have an option to cancel the order within a specific time.
o The student can see ordered items when the order is placed.
o The student gets notifications on the status change of the order.
o order in process to keep him updated on the status.
o The student can call the waiter by using the application.
Admin
 The admin manages the mobile application maintainability after the deployment.
 control or edit the role of an other actors in the system .
 The admin can add, delete or edit the menu items.
 The admin can edit the users and their roles in the system.
 Order status and the order processing time can be monitored for efficiency and
performance of the waiters.
 The Admin update cafe layout depending on weather and special occasions in the
system .
Non- functional requirements of the new system
A non-functional requirement describes user-visible aspects of the system that are not directly
related with the functional behavior of the system. They are concerned with security,
performance like speed, usability, maintainability, reliability, modifiability, efficiency,
portability (across operating systems), testability, and understandability. So we try to present the
non-functional requirements of the system as follow: Performance like:
Efficient