HARAMAYA UNIVERSITY

CALLEGE OF COMPUTING AND INFORMATICS

DEPARTMENT OF COMUTER SCIENCE
Title : HARAMAYA UNIVERSITY STUDENT CAFETERIA MANAGEMENT SYSTEM
Prepared by :
NAME ID NO.
1.ABDULAKI MUSTEFA …………………………………..1938/14
2.FIKADU TAMIRU…………………………………………2933/14
3. YARED ADISU……………………………………………1819/14

Submitted to Mr. Asedo Sh.

Haramaya , Ethiopia

8 July, 2023
TABLE CONTENTS

Contents
CHAPTER ONE ............................................................................................................................................... 1
1.1 Introduction .............................................................................................................................1
1.2 Background ..............................................................................................................................1
1.3 literature review ......................................................................................................................1
1.4 Statement of Problems .............................................................................................................2
1.5 Objective ..................................................................................................................................2
1.5.1 General Objectives of the Project ............................................................................................. 2
1.6 Methodology ............................................................................................................................3
1.5.1 Data collection method .............................................................................................................. 3
1.7 Feasibility study.......................................................................................................................4
1.8 Scope, Limitation and Constraint of the Project .........................................................................4
1.8.1 Scope of the project .................................................................................................................... 4
1.8.2 Limitation of The Project .......................................................................................................... 4
1.8.3 Constraint Of The Project ........................................................................................................ 5
Chapter Two .................................................................................................................................................. 6
2.1 Database design .......................................................................................................................6
2.2 Entity And Attributes of HU Cafeteria System ......................................................................7
2.1.1 Functional dependencies and normalization ......................................................................... 10
2.1.2 PHYSICAL DESIGN ................................................................................................................ 11
2.1.3 Implementation And Result of Query ........................................................................... 13
Chapter Three.............................................................................................................................................. 17
3.1 Conclusion ............................................................................................................................. 17
3.2 Recommendation ................................................................................................................... 17
References ........................................................................................................................................... 17

i|Page
TABLE OF FIGURES
FIGURE 1 : ER DIAGRAM ............................................................................ 8
FIGURE 2 : RELATIONAL SCHEMA ................................................................... 9

ii | P a g e
TABLE OF TABLE
TABLE 1 : CAFETERIA TABLE ..................................................11
TABLE 2 : EMPLOYEE TABLE ..................................................11
TABLE 3 : STUDENT TABLE ....................................................12
TABLE 4 : KITCHEN TABLE .....................................................12
TABLE 5 : FOOD TABLE .........................................................12
TABLE 6 : LIST OF ALL MALE ....................................................13
TABLE 7 : DELETE FROM STUDENT ...........................................14
TABLE 8 : ADD COLUMN........................................................14
TABLE 9 : DROP COLUMN ......................................................14
TABLE 10 : SELECT FEMALE....................................................15
TABLE 11 : CREATED EMPLOYEE TABLE .....................................15
TABLE 12 : UPDATE EMPLOYEE SALARY ....................................15
TABLE 13 : RENAME COLUMN ................................................16
TABLE 14 : SELECT MANAGER ................................................16
TABLE 15 : SELECT ALL EMPLOYEE ...........................................16
TABLE 16 : INSERT INTO TABLE ............................................... 16

iii | P a g e
CHAPTER ONE
1.1 Introduction
Designing and implementing a database system is an essential task for any business or organization
that needs to store and manage large amounts of data. In the context of a cafeteria management
system, a well-designed database can help streamline operations, improve efficiency, and enhance
the overall student experience. The first step in creating a database system is to design an Entity-
Relationship (ER) diagram, which is a graphical representation of the entities, relationships, and
attributes that make up the system. The ER diagram serves as a blueprint for the database schema,
and it helps ensure that the database is organized in a logical and efficient manner.

Once the ER diagram is complete, the next step is to create a database diagram, which is a visual
representation of the database schema. The database diagram shows the tables, columns,
relationships, and constraints that make up the database, and it helps ensure that the database is
properly structured and optimized for performance.

1.2 Background
Haramaya university student cafeteria was established with the establishment of the university in
1952 by Emperor H\Sillasie . The cafeteria started giving its service with the_one hundred
employees for students for the first time. Now, though still the system is not digitalized the
cafeteria is at giving the services and the number of employees are increasing day to day and still
the cafeteria has some problems.

1.3 literature review

The literature review for this project would involve looking at existing research and literature
related to database design and management systems, especially in the context of cafeteria
management systems. This would include studies and articles that discuss the benefits of using
database management systems for cafeteria management, as well as any limitations or challenges
that might arise.

One important aspect to consider in the literature review would be the current system of the
organization. This would involve looking at how the organization currently manages its cafeteria
data, including any limitations or challenges with the current system. It would also involve looking
at any existing literature or research on cafeteria management systems, including best practices
and successful implementations.

1|Page
Another important aspect to consider would be the design and implementation of the database
system for each activity of the entities of the system. This would involve looking at existing
literature and research on database design, including ER diagrams, database tables, and the
different activities involved in building a flexible and dynamic database system.

The literature review would also need to address how to insert column, update attribute, drop
column, delete attribute, select and alter column of database. This would involve looking at
existing literature and research on database management systems, including SQL queries and other
programming languages used in database management.

1.4 Statement of Problems

Haramaya university Meal Service Management System currently has so many problems, because
the system is manually operating. Those problems are :-

 Time consuming and costly by giving the meal card to the student which can take much
time money and need many labor force.
 Boring: - Ticking the students’ meal card while they are entering the cafeteria to get food
services
 Re-printing when the students lost their meal card .
 Problem of information distribution .
 Problems of information redundancy .
 Punishment of the student when the students miss keeping the order of marching to eat
food.
 Loss of data and meal card of students due to lack of an automate system.
 Inaccuracy of information:- due to fault occurred during food item distribution to each
cafeteria .
 Error during reporting and Problems occur concerning special case and readmitted
students.

1.5 Objective
1.5.1 General Objectives of the Project
The main objective of this project is to develop and design a secure student cafeteria database
record system . By changing the manual part of the handling system in to well design and
Sophisticated computerized database system and by overcoming the drawback of the current

2|Page
working system of the organization , we are going to develop database management system and
comprehensive ER diagram for the simplification of the difficulties occurred in cafeteria
management system.

1.5.2 Specific Objectives of the Project

The specific objective of the project is to improve the service around the system and improve the
work process of the cafeteria information management by loosely coupling highly cohesiveness
of the internal work and minimize the labor work by designing advanced database management
system. By allowing students to get fastest and better service and any useful information without
complexity and also to make all things in recorded and transfer them in to the upcoming
generation.

1.6 Methodology
A system development methodology refers to the framework that is used to structure, plan, and
control the process of developing an information system.

1.5.1 Data collection method

The methods we used to collect data are:-

Interview: This is one of data collection method that enables to gather information from the
organization directly in the form of asking question and getting answers for those questions. So,
we have used this method to gather information by asking the head and staff of cafeteria
management system some basic questions. The questions we asked through interview are: -

 The establishment year of the cafeteria management system and the cafeteria itself.
 By how many employees it started giving services
 How the service was going on and in what manner the service was being given
 what are the problems of the cafeteria management system
 what is your method of handling data (manual approach or database based) and
 How many subsystem are there under student cafeteria management system.
 What are the relationship between the workers which is useful to construct ER diagram.
Observation: This is also another data collecting method. In fact we have also used this
observation method to gather data. This method enables us observing and understanding
how the cafeteria management system is being done.

3|Page
1.7 Feasibility study
Feasibility refers to the practicality and suitability of the proposed database solution.

1. Economic feasibility: Developing a database can be costly in terms of time, money, and
resources. the benefits of the database, such as improved efficiency and productivity, outweigh
the costs of its development and maintenance.

2. Operational feasibility: The success of the database project will depend on the needs of the
users and is practical and usable within the organization's existing business processes and
workflows

3. Legal and ethical feasibility: database complies with legal and ethical standards, such as data
privacy regulations and intellectual property rights.

1.8 Scope, Limitation and Constraint of the Project

1.8.1 Scope of the project
The scope of our project is to recording students’ cafeteria management system information in the
computerized way and design database table ,database ER diagram and to know:-
 The current system of the organization.
 How identify current cafeteria data record system limitation .
 How we solve the problem by using database management system.
 How to design and implement database system of each activity of the entities of the
system.
 How to insert column , update attribute, drop column , delete attribute, select and alter
column of database.
 How to build flexible and dynamic database system are also one of the scope of the project.

1.8.2 Limitation of The Project

Our project is limited to :-
Design database table.
Design ER diagram.
Show retrieval and update procedure in database.

4|Page
1.8.3 Constraint Of The Project
due to the :-
 shortage of time .
 lack of adequate information.
 others mini projects.
 Lack of enough paper.
 Lack of good platform for designing.
The following activities will not be included in our project.
o Automating the system
o Making ticking system barcode enabled.

5|Page
Chapter Two
2.1 Database design

Database design is the process of creating a structured and organized database system that can
efficiently store, manage, and retrieve data. The design process involves identifying the data that
needs to be stored, organizing it into logical groups, and defining the relationships between the
different data entities.

A well-designed database system should be able to handle large amounts of data, while ensuring
data integrity and accuracy. The database design process involves several key steps, including:

1. Requirements analysis: Identifying the data that needs to be stored, and the relationships
between the data entities.

2. Conceptual design: Creating an Entity-Relationship (ER) diagram, which is a graphical

representation of the entities, relationships, and attributes that make up the system.

3. Logical design: Translating the ER diagram into a database schema, which is a set of tables,
columns, and constraints that define the structure of the database.

4. Physical design: Implementing the database schema using a database management system
(DBMS), and optimizing the database for performance.

5. Testing and maintenance: Testing the database system to ensure that it meets the service
requirements, and maintaining the database to ensure that it continues to meet the changing needs
of the organization.

In the context of a database, the following terms are commonly used:

 Entity: A thing, object, or concept that is represented in the database and has attributes that
describe its properties. For example, in a cafeteria management system, entities might
include food items, student, tickers, cooks, and suppliers.
 Primary key: A unique identifier for an entity instance that is used to distinguish it from
other instances of the same entity. The primary key can be composed of one or more
attributes of the entity. For example, in a food item entity, the primary key might be the
item ID.

6|Page
  Entity instance: A single occurrence or representation of an entity in the database. For
example, a specific food item with its attributes would be an instance of the food item
entity.
 Foreign key: An attribute in one entity that refers to the primary key of another entity. It is
used to establish a relationship between the two entities. For example, in a cafeteria
management system, the food item entity might have a foreign key that refers to the
supplier entity's primary key.
 Relationship: A connection or association between two or more entities in the database.
Relationships can be one-to-one, one-to-many, or many-to-many. For example, in a
cafeteria management system, there might be a relationship between the food item entity
and the supplier entity, where one supplier can supply many food items.
 Weak entity: An entity that does not have a unique identifier on its own and depends on
another entity to be identified. A weak entity always has a relationship with a strong entity.
For example, in a cafeteria management system, a food order entity might be a weak entity
that depends on the student entity to be identified.

2.2 Entity And Attributes of HU Cafeteria System

Employee entity: This entity would represent the workers who are employed in the cafeteria, such as
cafeteria head, managers ,tickers, cooks, and maintenance workers. The attributes of this entity might
include employee ID, name, contact information, job title, and address.

Student entity: This entity would represent the customers who are using the cafeteria services, specifically
the students who attend the university. The attributes of this entity might include student ID, name, contact
information, gender, program of study, and year.

Food entity: This entity would represent the items that are available for student in the cafeteria, such as
meals, snacks, and beverages. The attributes of this entity might include item ID, name, description,
category (e.g. entrees, sides, drinks), price, allergens, ingredients, nutritional information, and availability.

Cafeteria entity: This entity would represent the physical space and infrastructure that is used to provide
cafeteria services to customers. The attributes of this entity might include cafeteria ID, name, location,
seating capacity, hours of operation, and layout.

Kitchen entity: This entity would represent the space and equipment used for food preparation in the
cafeteria. The attributes of this entity might include kitchen ID, name, location, equipment inventory, and
staff information.

7|Page
THE ENTITY RELATIONSHIP DIAGRAM IS SHOWN AS FOLLOWS

Figure 1: ER DIAGRAM

8|Page
 Figure 2 : Relational schema

9|Page
 2.1.1 Functional dependencies and normalization

Normalize student table int 2 NF

Tabele 1 student

S_id_no S_fname S_lname S_department

Table 2 department
S_department C_number

Normalize student table int 3 NF

Tabele 1 student

S_id_no S_fname S_lname S_department

Table 2 department

S_department

Table 3 cafeteria

S_department C_number

10 | P a g e
2.1.2 PHYSICAL DESIGN
2.1.1.1 PHYSICAL DESIGN OF ALL TABLES

Table 1 : Cafeteria Table

Table 2 : Employee Table

11 | P a g e
Table 3 : Student Table

Table 4 : Kitchen Table

Table 5 : Food Table

12 | P a g e
2.1.3 Implementation And Result of Query

1. create database for Haramaya university student cafeteria management system

create database HU_cafeteria_management_system

2. create table for student

use HU_cafeteria_management_system
create table student ( s_fname varchar (50),s_lname varchar (50),s_id int
primary key,
s_department varchar (50),s_gender int,s_year)

3. List name of all male students with their respective attributes

SELECT s_FNAME,s_LNAME,department,age,year,s_id_no,GENDER FROM student
WHERE GENDER='Male'
Table 6: list of all male

13 | P a g e
 4. Delete student whose ID NO=129
delete from student where s_id_no=129
after delete the table looks

Table 7 : delete from student

5. Add column UID to student table

alter table student
add S_UID int
Table 8 : add column

6. Drop the column S_UID

alter table student
drop column S_UID
Table 9 : drop column

7. List the name and Id_no of female students

SELECT s_FNAME,s_LNAME,s_id_no,GENDER FROM student WHERE
GENDER='female'

14 | P a g e
Table 10 : select female

8. Create table for employee

Create table employee (e_fname varchar(50),e_lname

varchar(50),e_id_no int primary key,e_GENDER ,varchar(30)e_job_type
varchar(50),
e_job_type varchar(50),e_region varchar(50),e_woreda varchar(50))

Table 11: created employee table

9. Update employee salary where E_id_no is 3637

update employee set salary=3200 where e_id_no= 3637
Table 12 : update employee salary

10. Rename the column woreda to district

15 | P a g e
sp_rename 'employee.woreda','District','column'
Table 13 : rename column

11. List all employees from Oromia whose job type is manager
Select e_fname, e_lname, e_id_no ,salary,e_gender,age,phone_no ,region
from employee where e_job_type= 'manager'
Table 14: select manager

12. List all emloyees with their respective salary,gender and job type
Select e_fname, e_lname,e_job_type,Ssalary,e_gender from employee
Table 15 : select all employee

13. insert values into table

insert into student
values('Tola','Ahmad',265,'IT',23,253725)
Table 16 : insert into table

16 | P a g e
Chapter Three

3.1 Conclusion
The Haramaya University student cafeteria management system project was successfully completed,
including the design of a database, drawing of an ER diagram, and implementation of the database. The
project demonstrated a comprehensive understanding of the importance of different roles in a cafeteria
management system. The feasibility analysis conducted as part of the project indicated that the project
was technically feasible, economically viable, operationally practical, legally and ethically sound, and time
feasible. The database design phase involved creating an efficient and effective database structure that
would facilitate the management of student cafeteria operations. The ER diagram drawing phase involved
creating a visual representation of the database structure, which helped to identify the relationships
between different data entities and optimize the database design. The implementation phase involved
coding and testing the database, ensuring that it was functional and met all the requirements of the
project. Overall, the project demonstrated a systematic approach to problem-solving and a commitment
to achieving the project goals.

3.2 Recommendation
The Haramaya University student cafeteria management system would benefit from automating
its system. Automating the system would help to reduce errors, increase efficiency, and improve
the overall management of the cafeteria. Additionally, the implementation of an inventory
management system would help to ensure that the cafeteria always has enough stock to meet
demand, while minimizing waste. Overall, automating the cafeteria system would be a significant
improvement and would help to streamline operations, reduce costs, and enhance the overall
student experience.

References
hospital_project _I prepared by IS student

17 | P a g e