Haramaya University: College of Computing and Informatics Department of Computer Science

HARAMAYA UNIVERSITY
COLLEGE OF COMPUTING AND INFORMATICS
DEPARTMENT OF COMPUTER SCIENCE
Project title: Cafeteria Management System of Haramaya University
Group member name Id no section

HAMZA ADEM 1556/10 “B”
TUNIZA HASSEN 1581/10 >>
MURAD ADEM 1572/10 >>
DECHAS KASIM 1540/10 “A”
1|Page
Abstraction
Cafeteria management system is computerized system that help to manage their cafteria dairy
process ,such as order ,reservation ,redemption and etc. The entire system consists of back
end and front end, which back end was an offline application and front end was a web site
.the offline application allow cafteria to manage the cafteria information and managing the
dairy process such as seat admition and order. And the system allow cafteria to manage their
meal menu and promotion .And all updated meal menu and promotion will be show on the
web page automatically up on the completion of updating .
Cafeteria management System is developed by using Microsoft office 2016.The offline

application is developed by using HTML with CSS.
The current cafeteria is currently working by using manual way which fully paperwork ,
which consist a lot of man power and time in managing the record and dairy process. And
human mistake is unavoidable while the workload is increasing . Therefore they request for
the developing of cafteria management system ,which making their dairy process form
paperwork into automate system. Cafteria management System other than replace their
manual dairy work such as enter order ,make reservation and payment ,also including new
function such as online reservation and ordering , online meal and promotion viewing ,report
generating and reservation notification.
With the developing of cafteria management system, it increase the efficiency of cafteria and
improves the service ,automate system process able reduce dairy work error, also save time
and also cost in long term.
2|Page
Abstraction.................................................................................................................................2
Acknowledgement......................................................................................................................5
Abreviations list.........................................................................................................................6
Chapter one................................................................................................................................7
1.Introduction.............................................................................................................................7
1.1 Background of the organization.......................................................................................7
1.2. Statement of the problem....................................................................................................7
1.3 Objectives.........................................................................................................................8
1.3.1 General objectives.........................................................................................................8
1.3.2 Specific Objectives....................................................................................................9
1.4 scope of the project and limitation...................................................................................9
1.4.1 scope of the project...................................................................................................9
1.4.2 Limitations..............................................................................................................11
1.5 Significance of the study...............................................................................................11
Chapter Two.............................................................................................................................12
2. Requirements Elicitation......................................................................................................12
2.1 overview of existing system...........................................................................................12
2.2 Overview of Proposed System......................................................................................14
2.3 Functional Requirement.................................................................................................14
2.4 Non-functional Requirement........................................................................................15
2.6 constraint and assumption............................................................................................18
2.6.1 Assumption.............................................................................................................18
2.6.2 Constraints...............................................................................................................19
CHAPTER THEE ...................................................................................................................19
3.System modeling...................................................................................................................19
3.1 Use case Diagram and description.................................................................................19
3.1.1 Use Case View........................................................................................................19
3.2 Sequence diagram..........................................................................................................22
3.3 Activity Diagram............................................................................................................28
3|Page
3.4 class diagram..................................................................................................................32
3.5 state diagram..................................................................................................................33
Chapter four ...........................................................................................................................35
4. System Design......................................................................................................................35
4.1 Design Constraints.........................................................................................................35
4.2 Hardware and Software environment............................................................................35
4.3 system architecture.........................................................................................................36
Chapter five..............................................................................................................................37
5.1 system Implementation.................................................................................................38
5.2 tools................................................................................................................................48
5.3 Testing Methods.............................................................................................................48
CHAPTER SIX ......................................................................................................................51
6.1 Conclusion......................................................................................................................51
6.2 Recommendation............................................................................................................52
7.Reference...............................................................................................................................53
4|Page
Figure: 1 the architectural structure of the cafeteria management system.
Figure: 2 use case diagram.
Figure: 3 sequence diagram that show how cafeteria manager login to the system.
Figure: 4 sequence diagram of how the student take Id’s barcode.
Figure: 5 Ssequence diagram show how the manager give special food user Id for student
Figure: 6 sequence diagram that show how student punished.
Figure: 7 sequence diagram that show how the worker punished
Figure :8 Activity diagram for registration
Figure: 9 Activity diagram for account creation or barcode account.
Figure: 10 level 1 of activity diagram data flow
Figure: 11 level 2 data flow diagram
Figure: 12 class diagram
Figure:13 login state diagram
Figure: 14 scanning ID’s barcode state diagram

figure: 15 process enter barcode
Figure : 16 system of barcode model
Table: 1 description of actor’s
Acknowledgement
First of all, I would like to express our special thanks to Almighty Allah who helped me a lot
in all our work and also I wish express our sincere gratitude to our project supervisor, Mr
Gadisa A.
5|Page
I would like to take this chance to thanks my friend and senior which giving me a hand while
I am facing the problem on debugging the system, and thanks to their experience and idea
contribution on the logic of code in our system.
Abreviations list
HTML :- hypertext markup language
HU:- Haramaya University
CMS: Cafteria Management System
CMSHU:Cafeteria Management System of Haramaya University.
Php:-hypertext preprocessor
Js:-javascript.
RAM:- Random acess memory
6|Page
Chapter one
1.Introduction
This project describes the existing system, players in the existing system general work flow
of HU Cafeteria management system. In the university cafeteria management system is one
of the organization system which provides food for university students. It is belongs to under
the collage of university. We collect the information about the system through interview,
observation and document analysis. This system has three main components which are
Administrative, staff and employees.
The problem student ordering mechanism is very difficult and time losing manner. To
overcome this problem, we discussed with administrative and staff. our project is to develop
computer based cafeteria system for Haramaya university.
1.1 Background of the organization

Haramaya University is one of the oldest Universities in our country. It was established in
1945E.C as other universities of the country, Haramaya University has the golden goal of
producing qualified personal as per the dire need of the country. These professionals are
expected to faster the long run socio economic development needs of the country in general
and the community of Afar region in particular. Because of this, the university has the clear
vision of being one of the leading academic and research institution of the country through
creating an Oasis of teaching learning process and the mission of creating qualified personal
and per the dire need of the country. Along with the above, the University has clearly stated
strategic goals and institutional guidelines which promote the core purpose which are the
reason why the institution is established. Thus are academic, Research and community
engagement. However, the starting year of Haramaya University its formal education was in
1945E.C.
1.2. Statement of the problem

Currently the services that are given in HU student’s café are handled manually.
However, the Number of students who are getting the service (breakfast, lunch and
dinner) is increasing from time to time as the university is growing fast and intake
capacity. So managing manpower as well as the cost for the ingredient per day, week,
7|Page
Month and year become very difficult as it handles it’s every day activity manually.
With the above problems and others, we are going to solve this by converting the
manual system in to a computerized System. This means, a computerized store
controlling system, computerized service way of students and there is no need
of “marking or ticking” on the student’s meal card as there is a database that contain
student’s ID number which can identified by a bar code reader.
Generally, the existing system works as follow: -

 The current system of cafeteria is not computerized.
 HU cafeteria manager manages all activities in manual form,
 These can take much time, manpower effort and many losses of money for
printing papers every semester.
 Great confusion are generated related to the transactional issues from the managerial
point of view ,like total amount of food items served.
 Manual record keeping trends of the expenses and income generate computational
errors.
 Manual file require large storage space, like to list to give meal card to student.
 Security is limited to physical controls.
 There is no billing system.
 There is no sterilely checking ways to get cafe once or more ,
 They cannot take a timely order and provide a timely service.
1.3 Objectives
1.3.1 General objectives

The general objective of the project is to develop computer based Cafeteria management
system in Haramaya University.
1.3.2 Specific Objectives
In order to achieve the general objective of this project, the following specific objectives will
be include.
 To prepare reports in simple way,
 To minimize time and energy during the process of service schedule, applicant
registration for meal card,
 To update data easily,
 To keep secure the organization’s data,
8|Page
 To automate ticking system,
 To generate reliable and timely reports to the stake holder’s
 To access any kind of information related to the system on time and at easy
 To manage bulky information related to students and employees
 To handle proper usability of cafeteria by avoiding any kind of theft
 To improve data availability,
 To timely generate available items in stock
 To searching complaints by the handling grievance office which are responsible for
the appropriate task.
 To enhance the effectiveness and efficiency of our cafeteria system.
 To evaluating the performance of the current system and setting solution.
 To reduce the re-admition process.
 To reduce wastage of time.
 To change meal system into barcode enable.
 To generate efficient report.
1.4 scope of the project and limitation

1.4.1 scope of the project
Our projects aim is to develop the system that makes the students of this university much
more served on their Cafe and gives the coordinator of the cafeteria assistance on easy task
which makes them do their daily activities in a much more efficient manner. And also
our project is limited to the management of cafeteria management system of Haramaya
University.
The activity of the manager of the cafeteria is the general managerial work done by the
managers. These activities are managing the resources that are needed for the cafeteria for
giving services to the students. The manager is responsible for giving meal card for student;
control whether services of foods and water ready on time, control whether the students are
managed properly while they are getting service, take a corrective action when the student
make unethical work and manage other worker of the cafeteria.
It is also responsible for the management of material that can play a great role to give the
service to the cafeteria. Those materials are cups, plate, that can student use directly and
many other material that can used indirectly by the student.
9|Page
The automization of the ticking system is the subsystem of the cafeteria management
system that can focus on the managing of the student while they are getting the food services
from the cafeteria.
 The proposed system keeps in mind the problems of the current system as stated
earlier.
 Registering and displaying detail information about employees and students,
 Allow employees of the cafeteria and the administrator to login with their
own password,
 Customers can send feedback to the system.
 The work in the organization will be well planned and organized. The data will be
stored properly in data stores, which will help in retrieval of information fast as
well as its storage.
 Food serving and food preparation, both of which are handled by the cafeteria
employees
 By keeping track of which quality and quantities of different food items for
students
 Placements of employees
 Scheduling system of cafeteria to student.
 Solving problems occurred among employees and students
 Manages time when food provides for students
 There will be harmonious of work.
 Enable smooth and secure operations.
 Eliminate possible manipulation by unauthorized person.
 Increase processing speed.
1.4.2 Limitations
o Cafeteria is its only used by the students.
o Cafeteria is exclude the teachers .
o Non-cafe student is not used Cafeteria .
o Home delivery is not allowed.
o It is accessed only by English language.
o We cannot get food without restricted time.
10 | P a g e
1.5 Significance of the study
The significance of this project could be applied in Haramaya University and at the
end of the completion of this project, cafeteria manager of our university will get a benefit
like:-
 Information accessing is easy and fast.

 Minimize the time that it takes to achieve a specific operation.
 Reduce the manpower required during the management activity and ticking
process.
 Reduce time and energy during the process like urgent case shift of service
schedule, applicant registration for meal card.
 Easy to handle student record after they start using the cafeteria services
Chapter Two
2. Requirements Elicitation
2.1 overview of existing system
The current system mainly depends on manual work. The activities and tasks are held and
focused on paper based depend operation, means managing students and students
11 | P a g e
information, stock control, employees and the ticking system are done manually. As a
result of the manual management system reporting writing, searching file, updating file,
and registering is difficult. So that, no reliable management because of the number of
students. The relationships between the manager and employees the case of idea
sharing is depend on meeting or needs third party/representative in which information
unreliable Or duplication of printed paper for each employee problems which leads to
extravagance. In addition, these there are a problems on the general activities of the
management for example, there is wastage of time manpower, loss files and documents,
and space wastage are the over view of the existing system in short.
The structure of existing the cafeteria management system

Head of cafeteria
Assistant chief
12 | P a g e
Worker leader Head ticker Resource Operator
leaders leaders
Shift leader Guard Tickers

Laundry Boiler
operators operators
Junior shift
Store men Injera house Bread

leader store
controller
Cook Dish Food
washer prepare
Dough Injera
makers prepare
Fixed asset Consumabl Vegetable

store men e store men store men
Figure: 1 the architectural structure of the cafeteria management

system
2.2 Overview of Proposed System

The system is proposed to computerize the working environment of the existing system
and to overcome the problem regarded with manual work and to benefits the
community of the cafe in common.
The following list are the overview of the proposed system: -

 Saves time which is spent on searching the records by hand,
13 | P a g e
 Reduce space that occupied by manual document,
 Helps, admin to have an easy access and control over the system,
 Helps to reliable information among the community of the café,
 Helps to registering, searching, updating and to keep all the file in safe way,
 Generate report,
 Online feedback between the community of the café.
2.3 Functional Requirement

Functional requirements are mandatory requirements that must be incorporated in any system
and also where it is discussed with CMS keeping in mind operational issue faced by their
team and where generalized to make it work for any other set up without additional effort or
customization, as example we take student, admin and waiter.
 Meal module
This module allow cafeteria to manage their menu , function include edit ,
delete,add ,by using offline application .photo is allowed to upload . Update menu list
in the offline application will update the menu list on the web page as well .Add
member of cafeteria is able to view all update meal menu at their web page .
 Promotion module
This module allow cafeteria to combine the existing meal to become a promotion
menu , function include edit , delete, add ,by using offline application .photo is
allowed to upload . Update menu list in the offline application will update the menu
list on the web page as well .Add member of cafeteria is able to view all update meal
menu at their web page .
 Table reservation module
This module allows seat reservation to be made, either by staff or customer . Staff can
customer to reserve seat via the offline application ,or customer could reserve in cafeteria
web page after register as member.
 Order module
14 | P a g e
This module allows order to make . order make is allowed to edit as long as the
payment haven’t being made .meal ordering are allowed by member after reservation
had been make offline.
 Report module
This module allow the cafeteria to generate and view report. The reports included are
order Report and reservation report.
 Seat admission module
This module allow cafeteria to monitor the current seat situation of the cafe. which
table , or how many table are available or not available. And each table will be bound
to one order and one member once occupied.
2.4 Non-functional Requirement

 Product Requirement
▪ Efficient Requirement
The overall response of the system is satisfies ,system will response to user action within
few second. The modification of meal and promotion information will be updated directly on
web page.
▪ Reliability Requirement
That’s no system errors so far from system testing , therefore ,the system is reliable . all
information modified or uploaded by user didn’t lead to any conflict or error.
▪ Portability Requirement
The system is able to run on different platform as long as operating system in installed.
▪ Usability Requirement
The system is design as simple as possible without removing any requires function . every
single function could be complete in one form to avoid user confusion . add every up on
every completion of action , proper message will be shown to inform user .
 Organization Requirement
15 | P a g e
 Deliver requirement
 Order is only allowed upon the completion of reservation
 Only member is allowed to reservation.
 External requirement
 Legislative requirement
The system is developed with the scope of law and regulations .user and staff information in
the system will not disclose to any unrelated person.
 Ethical requirement
The offline application is designed according to the need of cafeteria staff requirement, and
the web application is designed manner where every general public user able to adapt, since
public user able to register and make reservation and order via web application.
2.5 The requirement of the proposed system

Barcode Generator. Once you have your product names, you can begin creating your
barcodes. While you can download barcode fonts, online generators can be easier. All you have
to do is enter in your code and download your barcode for printing.
Label Printer. If your home or office already has a working printer, you're all set – most
standard inkjet and laser models can print barcodes. If you're in the market for one, evaluate
your options.
Desktop printers work great for small batches whereas dedicated label printers are ideal for
larger operations.
Barcode reader
A barcode reader (or barcode scanner) is an optical scanner that can read
printed barcodes, decode the data contained in the barcode and send the data to a computer.
Like a flatbed scanner, it consists of a light source, a lens and a light sensor translating for
optical impulses into electrical signals. Additionally, nearly all barcode readers
contain decoder circuitry that can analyze the barcode's image data provided by the sensor
and sending the barcode's content to the scanner's output port.
16 | P a g e
Bar coding Software. You need a system that will interpret your product codes and
translate them back to you. While programs like Microsoft Excel might be great for cataloging,
they aren't ideal for other processes like inventory management.
Barcode Scanners. The software doesn't work without the hardware. You'll need to invest in at
least one barcode scanner to read your barcodes and communicate with your program.
Database server:
Creating a Database
First of all, we should create a database using any DBMS like Oracle, SQL Server or Ms
Access etc. For this article, we have chosen SQL Server 2000 for creating the database.
We have created a table named barcodes in the database with three columns in it. First
column, bid is acting as a Numeric Primary Key and Table Identity Column as well. It means
that bid column will automatically generate it's primary key (unique) values and we don't
have to enter any unique values in it by ourselves. Other two columns, code text and
symbology are of varchar type, which means that these columns can store variable length of
characters.
Saving Barcode Details to Database
Now, we have to create an application that generates a specific barcode image according to
user inputs. We have used Bar Code Control in our windows application to generate barcode
image. Bar Code Control has Code Text and Symbology Type properties through which we
can access Code text and Symbology of the barcode generated by Bar Code Control. So, all
we have to do, is to Open a database connection using Sql Connection and insert the Code
text and Symbology of the barcode into the barcodes table by calling Execute Non Query
method of Sql Command.
2.6 constraint and assumption

2.6.1 Assumption
 The cafeteria is open for breakfast, lunch, and dinner for Haramaya University are
expected to be on site.
 As our assumption is cafeteria management system in haramaya university based on
the service provider and producer, must be satisfy the user ,that are student. it must be
17 | P a g e
improved in the time management ,for instance breakfast time, lunch, dinner and
schedule of food based student want .
 As assumption we states in our project in case controlling system of student
that means ,meal card system that currently use in cafe must remove by computer
system control.
 For example, you have assumed that some particular equipment will be made
available to you whenever you need it. However, the equipment is not provided when
the time comes.
 Assumptions play an essential role in developing a risk management plan. Therefore,
as a project manager, you must collect and identify as many assumptions as you can.
2.6.2 Constraints
Cafeteria management system is a management system that is designed to improve
accuracy and to enhance facility and efficiency to the students. It is a computer
based system which helps the users to improve inventory management, time, and effort.
 The limitation of this cafeteria is we can not service in any time .that means its has
restricted time.
 Constraints are used to limit the type of data that can go into a table
 Its give service to only the students and cafeteria employer’s.
CHAPTER THEE
3. System modeling
 System modeling is the process of developing abstract models of a system,
with each model presenting a different view or perspective of that system.
3.1 Use case Diagram and description

 use case is a description of a system’s behavior as it responds to a request that
originates from outside of that system. It describes "who" can do "what" with the
18 | P a g e
system in question and A use case can be taken as a simple scenario that describes
what a user expects from a system.
3.1.1 Use Case View
The use-case approach requires the analyst to determine all the potential actors involved in a
system. Actors are external to the system and make use of it. An actor is typically a person,
but may be a third-party organization or another computer system. We model actors, not
individuals.
An actor makes use of a system in different ways. Each of these ways is known as a use-case.
Use-case is “a behaviorally related sequence of transactions (performed by a user/actor) in a
dialogue with the system”. A use-case may involve a number of actors, just as an individual
actor may make use of several use-cases. We represent use-case diagrammatically by ovals
and actors by stick men.
In our system we have three actors. Those are:
1. managers
2. tickers and
3. students
The cafeteria managers have many interactions within the systems. Among this the major
one is seeing the report of the student and the workers. By looking this report when he see
unethical student or worker which break the principles of the cafeteria management system
for the first time he can advise them. If the worker or student can do the same thing for the
second time, for the purpose of correcting them he can punish them by using the principles of
the cafeteria.
Another actor of the cafeteria management system is the tickers. His/her responsibility in
the existing system is to control and tick the meal card of the student while they come to use
the food service from cafeteria. After this system is implemented the role of the ticker can be
controlling the student, ready the system to use for student and reporting the student that can
done unethical work when the system is not get student’s Id’s barcode.
Students are the most benefited and the mean actor of this system. They can get their Id’s
barcode easily.
After getting the Id’s barcode one’s they can use it while the entire life of their university.
Even if the Id’s barcode will be lost from them regaining their Id’s barcode is not difficult to
them since the system reduce this activity.
19 | P a g e
More Description of actors
An actor represents anything that needs to interact with the system to exchange
Actor Name Cafeteria managers
Use case:  Reporting the servicing capacity cafeteria to the

student to the office of register
 Register the student to give id’s that have barcode
 Control the students while they getting the services
Actor Name Tickers
Use case:  Supervise the students while they are entering the
cafeteria
 reporting the unethical students

Actor Name Students
Use case:  Check their id’s barcode
 Enter the cafeteria hall
 Get the food services
information. An actor is a user, a role, which could be an external system as well as a person.
An actor initiates the system activity, a use case, for the purpose of completing the some
business task.
Table :1 of actors and their descriptions
20 | P a g e
Figure: 2 use case diagram.
21 | P a g e
3.2 Sequence diagram
Sequence diagrams are used to depict graphically how objects interact with each other via
messages in the execution of a use case or operation. Sequence diagrams highlight more the
temporal aspect, by showing invocation and responses along a (vertical) timeline and by
explicitly showing the activation time of objects. Sequence diagrams show how objects
communicate with each other in terms of a temporal sequence of messages. The time flow is
the most visible aspect in these diagrams, as messages are sequenced according to a vertical
timeline and also the lifespan of objects associated to those messages is reported. They
illustrate how the messages are sent and received between objects and in what sequence.
Our system design needs many sequence diagrams to simplify the development the
system throughout this project. Among those sequence diagrams the most needed in our
project is illustrated below
22 | P a g e
Figure: 3 sequence diagram that show how cafeteria manager login to
the system
23 | P a g e
Figure: 4 sequence diagram of how the student take Id’s barcode
24 | P a g e
Figure: 5 Sequence diagram show how the manager give special food
user Id for student
25 | P a g e
Figure: 6 sequence diagram that show how student punished
26 | P a g e
Figure: 7 sequence diagram that show how the worker punished
27 | P a g e
3.3 Activity Diagram
Illustration of the dynamic nature of a system modelling is essential to control the flow
of activity to activity. An activity means that the representation of an operation on some
class in the system that results in change with in the state of the system.
Figure :8 Activity diagram for registration

Activity Diagram for Creating an account:
This is unique registration form other than registering employee and students, these
means the that action is only done by manager of the CMSHU
28 | P a g e
Figure: 9 Activity diagram for account creation or barcode account.
29 | P a g e
Cafeteria
Management
System of
Haramaya
University
Figure: 10 level 1 of activity diagram data flow.
30 | P a g e
Cafeteria
Management of
Haramaya
University
Figure: 11 level 2 data flow diagram
31 | P a g e
3.4 class diagram
Class diagrams are used to represent objects can be having name, attributes and
properties of an objects. Here under are the system classes that we identified,
Figure: 12 class diagram
32 | P a g e
3.5 state diagram
The basic idea state diagram is to define a machine that has a number of states (hence
the term finite state machine). The machine receives events from the outside world,
and each event can cause the machine to move from one state to another. These
diagrams therefore identify what events can occur in a system, and what effect they
can have on the object. Diagrams of this type can provide a good sense of the events
that can occur in a system and the effect they have on the object.
Login to
CMSHU system
Figure:13 login state diagram
33 | P a g e
Figure: 14 scanning ID’s barcode state diagram
34 | P a g e
Chapter four
4. System Design
4.1 Design Constraints
System design is the process of defining the architecture, components, modules, interfaces,
and data for a system to satisfy specified requirements through system modelling. One could
see it as the application of systems theory to produce development. The design of this system
will be user friendly. It shall be designed in such a way that employees will be able to
navigate easily through the information supplied on the system. 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.
4.2 Hardware and Software environment
Hardware environment:-
• A minimum hard disk space of 20 Gigabytes (GB)
• RAM size of 1GB
• Pentium 4 dual processor CPU
• A VGA colour monitor
• Mouse
• Keyboard 4.5
Software environment
 Windows operating system such as Windows 2000, windows XP, Windows Vista,
Windows7, Visual basic 6.0 software.
 WAMP server
 MySQL:- for database
 PHP:- for implementation language
 Js:- To program the behavior of web pages.
 HTML:- to develop client side web page
35 | P a g e
4.3 system architecture
figure: 15 process enter barcode

Architecture of proposed system:
Barcode scanners consist of three different parts including the illumination system,
the sensor, and the decoder. In general, a barcode scanner “scans” the black and white
elements of a barcode by illuminating the code with a red light, which is then
converted into matching text. More specifically, the sensor in the barcode scanner
detects the reflected light from the illumination system (the red light) and generates an
analog signal that is sent to the decoder. The decoder interprets that signal, validates
the barcode using the check digit, and coverts it into text.
36 | P a g e
 Bar code scanner used to scan the student card which contains
the student identification number. The twelve digits then send
to the attendance system and it will remain displaying student
record for 5 second before change to the state to accept
another student card number.
Each recorded data will be send to the database which developed using database
processing application. Structured query language (SQL) used to query
data to produce various kind of student attendance report.
37 | P a g e
Figure : 16 system of barcode model
38 | P a g e
Chapter five
5.1 system Implementation
The implementation document helps users on how to work with the design system. It acts
as a user manual and to gate further information about the system. And it helps user’s not
to be confused with the system. It includes sample forms and some selected fragment
code. It gives the users a brief over view of the design system. And its objective is to change
what we did in the design Phased to machine readable form by writing code using PHP and
java script to all modules. The system contains many forms that are connected to the data
base in each individual form also combined in one module in order to work the system as
whole.
The code that implement our system is as follow:-
Sample code for login page

<?php session_start();
unset($_SESSION['id']);
?>
<! DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<Head>
<Title>Library Management System</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
<meta http-equiv="Content-Style-Type" content="text/css" />
<script src="css/ac_activex.js" type="text/javascript"></script>
<script src="js/valid.js" type="text/javascript"></script>
<link href="css/template_css.css" rel="stylesheet" type="text/css"/>
<link href="css/css.css" rel="stylesheet" type="text/css"/>
<link rel="stylesheet" media="screen"type="text/css" href="css/formstyles.css"/>
<script type="text/javascript" src="js/jquery.js"></script>
</head>
<body id="bd" class="auto fs3" bgcolor="#88CCCC">
<div id="ja-wrapper">
<div id="ja-wrapper-inner">
39 | P a g e

<div id="ja-headerwrap">
<div id="ja-header" class="clearfix">
<h1><img src="images/logolibrary.jpg"width="100%" height="130" alt="Library
Management System"align="top" /> </h1>
</div>
</div>


<div id='cssmenu'>
<ul><li class='has-sub'><a href='firstlogin.php' target="iframe1"><span>Home
</span></a>
<ul><li class='last'><a href='university_info.html'
target="iframe1"><span>HU_Back_Ground</span></a></li>
<liclass='last'><a href='library_info.html'
target="iframe1"><span>Library_Information</span></a></li>
</ul> <li class='has-sub'><a href='#'><span>Help</span></a>
<ul> <li><a href='recovery.php'target="iframe1"><span>Forget your
Password?</span></a></li> </ul>
</li> </ul></div>
<div id="ja-containerwrap">
<div id="ja-container" class="clearfix">

<div id="ja-mainbody">
<div id="ja-contentwrap">
<div id="ja-content">
<div id="ja-pathway"></div>
<iframe name="iframe1" width="700" height="480" src="firstlogin.php"
scrolling="auto" frameborder="0"></iframe>
</div>
</div>

<div id="ja-rightcol">
<div id="ja-rightcol-inner">
40 | P a g e
<div class="module">
<h3>Time:</h3>
<script src="css/time.js" language="javascript"
type="text/javascript"></script>
<body onLoad=" yourClock()",
onUnload=" stopClock(); return true">
<form name="the_clock"><table width="60%"
border="0" cellpadding="0" cellspacing="0" bgcolor="#ABCDEF">
<tr align="center"><td>System
Time: <input type="text" name="the_time" size="10"
style="padding-bottom:5px;" align =
"top"></a></td></tr>
<tr align="left"><td><br/><br
/></td></tr><br/>
</table>
</form>
<br /><br />
<h3> Calendar</h3>
<script src="css/calander.js" language="javascript"
type="text/javascript"></script><br/><br/>
</div>
</div>
</div>
<! -- END: RIGHT COLUMN -->
</div>
<! -- END: CONTENT -->
<! -- BEGIN: LEFT COLUMN -->
<div id="ja-leftcol"><div class="moduletable">
<h3><font style size=5> Login Form</font></h3>
<form action="login.php" method="post" name="contact_form"class="contact_form">
<table> <tr><td><label>Username:</label></td></tr>
<tr><td><input type="text" name="username" placeholder="username"
required />
<span id="username" class="error" ></span></td></tr>
41 | P a g e
<tr><td><label>Password:</label><td></tr>
<tr><td><input type="password" name="password"placeholder="..........." required />
<span id="password" class="error" ></span></td></tr>
<tr><td><button class="submit" type="submit">Login</button></td></tr>
</table>
</form>
</div>
</div><br/>

</div></div>

<div id="ja-footerwrap">
<div id="ja-footer">
<div id="ja-sublogo"></div>
<p id="ja-bottomline">
<table width="100%" border="0" cellspacing="0">
<tr><td width="80%" align="center" bgcolor="#555555">Copyright ©
2012 reserved <i>library management system the case of Haramaya University</i>.
</td></tr>
</table>
</p>
<div id="ja-cert"></div>
</div>
</div>

</div>
</div>
</body>
42 | P a g e
Code for manage interface
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>HU Online Library Management System</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<script src="css/ac_activex.js" type="text/javascript"></script>
<link href="css/template_css.css" rel="stylesheet" type="text/css" />
<link href="css/css.css" rel="stylesheet" type="text/css" />
<script type="text/javascript" src="js/jquery.js"></script>
</head>
<body id="bd" class="auto fs3">

<div id="ja-wrapper">
<div id="ja-wrapper-inner">

<div id="ja-headerwrap">
<div id="ja-header" class="clearfix">
<h1><img src="images/logolibrary.jpg"width="100%" height="130"
alt="####"align="top" />
</h1>
</div></div>
<div id='cssmenu'>
<ul> <li class='active'><a href='comm2.php'
target="iframe1"><span>Home</span></a></li>
<li class="has-sub"><a href="#"><span>Registeration</span></a>
<ul> <li class='last'><a href='registerBok.php' target="iframe1"><span>Book
Register</span></a></li>
<li class='last'><a href='registerStudent.php'target="iframe1"><span>Student
<li class='last'><a href='RegForCreateBook.php'target="iframe1"><span>CreateBook for
43 | P a g e
</ul>
</li>
<li class='has-sub'><a href='#'><span>Booked Item</span></a>
<ul>
<li class='last'><a href='add_book.php' target="iframe1"><span>Add
Book/Download</span></a></li>
<li class='last'><a href='view_book.php'
target="iframe1"><span>View Book/Download</span></a></li>
<li class='last'><a href='add_category.php'
target="iframe1"><span>Add Book Category</span></a></li>
<li class='last'><a href='view_catagory.php'
target="iframe1"><span>category_details</span></a></li>
<li class='last'><a href="jornalconn.php"
target="iframe1"><span>v jornalview Book Available</span></a></li>
<li class='last'><a href="property.php"
target="iframe1"><span>propAdmin</span></a></li>
</ul>
</li>
<li class="has-sub"><a href="#"><span>Daily_Update_control</span></a>
<ul>
<li class='last'><a href='daily.php'target="iframe1"><span>Add_Book</span></a></li>
<li class='last'><a href='bookcalcul.php'target="iframe1"><span>view
availability</span></a></li>
<li class='last'><a href='addoxford.php'target="iframe1"><span>Add</span></a></li>
</ul></li>
<li class="has-sub"><a href="#"><span>Update</span></a>
<ul> <li class='last'><a href='updateBook.php'target="iframe1"><span>Update
Book</span></a></li>
<li class='last'><a href='updateStudInfo.php' target="iframe1"><span>Update
Student</span></a></li>
</ul></li>
<li class="has-sub"><a href="#"><span>Delete</span></a>
<ul><li class='last'><a href='deleteStudent.php' target="iframe1"><span>Delete
44 | P a g e
<li class='last'><a href='deleteSpecialTheif.php' target="iframe1"><span>Delete Student
Theif</span></a></li>
<li class='last'><a href='deletenews.php' target="iframe1"><span>Delete
News</span></a></li>
<li class='last'><a href='deStudChe.php'target="iframe1"><span>Delete Cheating
</ul></li>
<li class='has-sub'><a href='#'><span>News</span></a>
<ul>
<li><a href='new.php'target="iframe1"><span>Post news</span></a></li>
</ul> </li>
<li class='has-sub'><a href='#'><span>Feedback</span></a>
<ul>
<li ><a href='commentsearch.php' target="iframe1"><span>Read
comment</span></a>
</ul>
</li>
</ul>
</div>
<br/>
<div id="ja-containerwrap">
<div id="ja-container" class="clearfix">

<div id="ja-mainbody">
<div id="ja-contentwrap">
<div id="ja-content">
<iframe name="iframe1" width="700" height="455" src="comm2.php"
scrolling="auto" frameborder="0"></iframe>
</div> </div>

<div id="ja-rightcol">
<div id="ja-rightcol-inner">
<div class="module">
45 | P a g e
<a href=logout.php><font
color=green>          &
nbsp;
Logout </font></a> <br/></h3>
<script src="css/time.js" language="javascript" type="text/javascript"></script>
<body onLoad="yourClock()", onUnload="stopClock(); return true">
<form name="the_clock">
<table width="60%" border="0" cellpadding="0" cellspacing="0">
<tr align="center"><td><a class="mainlevel">
System Time:  <input type="text"
name="the_time" size="10"style="padding-bottom:5px;" align = "top"></a></td></tr>
<tr align="left"><td><br/></td></tr><br/>
</table>
</form>
<br/><br/>
<h3>     Calendar</h3>
<script src="css/calander.js" language="javascript"
type="text/javascript"></script>
<br/><br/>
</div> </div>
</div></div>

</div>


<div id="ja-leftcol">
<div class="moduletable">
<h3>Administrator Activity</h3>
<tr align="left"><td><a class="mainlevel" >
<a href='searchBook.php'target="iframe1"><span><font size="3"
color="#0000FF">Book_Info.</span></a><td/></tr>
<a href='search.php'target="iframe1"><span><font size="3"
46 | P a g e
color="#0000FF">Book_Info.</span></a><td/></tr>
<a href='reportsearch.php'target="iframe1" ><span><font size="3"
color="#0000FF">Book Report</span></a><td/></tr>
<a href='' target="iframe1"><span><font size="3"
color="#0000FF">Search ISBN</span></a><td/></tr>
<tr align="left"><td><a class="mainlevel"
></span></a><td/></tr></font>
</table></div>

<div class="moduletable">
<h3>some pictures</h3>
<div id="content">
<div class="container_16 clearfix">
<div id="featured"> <div class="grid_12">
<div id="slides">
<img class="framed"
SRC="images/featured/library.jpg" alt="Slide 1" width="200" height="150"/>
<img class="framed"
SRC="images/featured/cci.png" alt="Slide 1" width="200" height="150"/>
<img class="framed"
SRC="images/featured/coa.jpg" alt="Slide 1" width="200" height="150"/>
<img class="framed"
SRC="images/featured/library2.jpg" alt="Slide 1" width="200" height="150"/>
<img class="framed"
SRC="images/featured/gc.jpg" alt="Slide 1" width="200" height="150"/>
<img class="framed"
<img class="framed"
<img class="framed"
SRC="images/featured/Lab.jpg" alt="Slide 1" width="200" height="150"/>
47 | P a g e
<img class="framed"
SRC="images/featured/documt11.jpg" alt="Slide 1" width="200" height="150"/>
<img class="framed"
SRC="images/featured/docment5.jpg" alt="Slide 1" width="200" height="150"/>
<div id="slidepager"></div>
</div>
</div>
<div class="clear"></div>
</div>
<div class="grid_4"></div>
</div>
</table>
</div>
</div><br/>

</div></div>

<div id="ja-footerwrap">
<div id="ja-footer">
<div id="ja-sublogo"></div>
<p id="ja-bottomline">
<table width="100%" border="0" cellspacing="0"><tr><td width="80%"
align="center">
Copyright © 2012 Haramaya University.
Developers: Hamza, Tuniza, Murad
</td></tr>
</table> </p>
<div id="ja-cert"></div>
</div></div>

</div></div>
</body>
</html>
48 | P a g e
5.2 tools
The tools that used in our project is:-
 Hardware
 Software
5.3 Testing Methods
Unit testing:
Unit testing involves the design of test cases that validate that the internal program logic is
functioning properly, and that program inputs produce valid outputs. All decision branches
and internal code flow should be validated. It is the testing of individual software units of the
application . It is done after the completion of an individual unit before integration. This is a
structural testing, that relies on knowledge of its construction and is invasive. Unit tests
perform basic tests at component level and test a specific business process, application,
and/or system configuration. Unit tests ensure that each unique path of a business process
performs accurately to the documented specifications and contains clearly defined inputs and
expected results.
Integration testing:
Integration tests are designed to test integrated software components to determine if

they actually run as one program. Testing is event driven and is more concerned with the
basic outcome of screens or fields. Integration tests demonstrate that although the
components were individually satisfaction, as shown by successfully unit testing, the
combination of components is correct and consistent. Integration testing is specifically aimed
at exposing the problems that arise from the combination of components.
Functional test:
Functional tests provide systematic demonstrations that functions tested are available as
specified by the business and technical requirements, system documentation, and user
manuals.
49 | P a g e
Functional testing is centered on the following items:
Valid Input : identified classes of valid input must be accepted.
Invalid Input : identified classes of invalid input must be rejected.
Functions : identified functions must be exercised.
Output : identified classes of application outputs must be exercised.
Systems/Procedures: interfacing systems or procedures must be invoked.
Organization and preparation of functional tests is focused on requirements, key functions,

or special test cases. In addition, systematic coverage pertaining to identify Business process
flows; data fields, predefined processes, and successive processes must be considered for
testing. Before functional testing is complete, additional tests are identified and the effective
value of current tests is determined.
System Test:
System testing ensures that the entire integrated software system meets requirements. It
tests a configuration to ensure known and predictable results. An example of system testing is
the configuration oriented system integration test. System testing is based on process
descriptions and flows, emphasizing pre-driven process links and integration points.
White Box Testing:

White Box Testing is a testing in which in which the software tester has knowledge of
the inner workings, structure and language of the software, or at least its purpose. It is
purpose. It is used to test areas that cannot be reached from a black box level.
Black Box Testing:

Black Box Testing is testing the software without any knowledge of the inner workings,
structure or language of the module being tested. Black box tests, as most other kinds of tests,
must be written from a definitive source document, such as specification or requirements
document, such as specification or requirements document. It is a testing in which the
software under test is treated, as a black box .you cannot “see” into it. The test provides
inputs and responds to outputs without considering how the software works.
50 | P a g e
Testing By Requirements
Correctness: Our system is functioning exactly it is supposed to the ticker as well as the cafeteria
mangers are able to retrieve information or fill required forms with complete accuracy and
consistence.
Reliability: The system must be available. It performs its consistency and complete accuracy. So
one can rely on it not to miss data and form
Security: The manager and other users of the system have their own user name and password so
that nobody who is unauthorized user can enter and modify data.
Test strategy and approach
Field testing will be performed manually and functional tests will be written in detail.
Test objectives
 All field entries must work properly.
 Pages must be activated from the identified link.
 The entry screen, messages and responses must not be delayed.

Features to be tested
 Verify that the entries are of the correct format
 No duplicate entries should be allowed
 All links should take the user to the correct page.

Test Results:
All the test cases mentioned above passed successfully. No defects encountered.
Acceptance Testing:
User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional
requirements.
Error Handling
In our system testing process we have tested the group of components (units) together to
evaluate or ensure their quality, performance and correctness. In addition to this we have
also tested the integration of all components or models system.
The integration testing and system testing are used to test whether the entered values are
valid or not. We have done this by providing error message when invalid input is entered.
51 | P a g e
CHAPTER SIX
6.1 Conclusion
Generally, in this project, we developed an automated CMSHU that facilitates various
activities taking place at the cafe. The CMSHU do different activities such as employee
registering, student registering, control store and daily meal, update and delete
information and also automatic ticking system.
We realize that the existing system is not capable of reducing errors and too backward to
work in a flexible manner. However, the newly developed system has dynamic features
of manipulating and managing data.
Furthermore, this document briefly describes the problems and the solutions we proposed
with the figures to visualize better and steps taken to solve the problem. In other words
this document introduces the technical details of the CMSHU.
In the first part of the technical design the major functions needed to develop CMSHU
are introduced. Later on, these major functions and their sub-functions are visualized with
the use case diagrams. In the second part, user interfaces are described in a detailed
manner with figures. Lastly, data modules and their relationships are discussed.
We believe from heartily that the existing problems of the cafe will be resolved and a
sustainable working environment will be created just by taking advantage of the newly
developed system.
To conclude, this document constitutes a base for the development of an CMSHU. In
addition, with implementing the new system will make the overall system more
convenient and give fast and reliable service for users which has continuous relation with
cafe.
Overall the implementation of this project was an excellent learning opportunity for us.
6.2 Recommendation
This paper will recommend specific steps to transform the elements of the CMSHU in
to a technologies. These steps, if taken, will result in better support to users while
expediting access to different information requirements and decreasing the workload of
the employees. These improvements will depend on the creation of an integrated software
development with one lead agent in charge of developing, maintaining, and growing the
architecture.
52 | P a g e
The Students Cafeteria Management System is immense and expanding. There should be
one centralized element responsible for design control and monitoring. It is imperative
that automation is properly reviewed and focused around the Core Task of managing.
There needs to be a plan for the entire system. This plan must be an active document that
grows with changes while anticipating future requirements.
The following paragraphs will provide specific recommendations
 Automation of Common Tasks: CMSHU management tasks were manual
procedures. Instead of multiple manual submissions of identical information,
automation solutions could significantly simplify these tasks with the use of
standardized applications within existing software solutions.
 Rapid Response: Students Cafeteria Management System Automation must
be responsive to the needs and requirements of the employees. The design must
be responsive enough to implement changes prior to requirements for users
The final recommendation is to establish effective, efficient and reliable
information management system for cafeteria manager as well as for all users of
this cafeteria.
7. Reference
 Systems Analysis and Design
 Software engineering 9th ed
Website
 www.hu.edu.et
 www.google.com
 www.info.com
 www.project.com.
 http: //www.softwareEnginering-3.com
53 | P a g e
54 | P a g e

Haramaya University: College of Computing and Informatics Department of Computer Science

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Haramaya University: College of Computing and Informatics Department of Computer Science

Uploaded by

Copyright:

Available Formats

HARAMAYA UNIVERSITY

COLLEGE OF COMPUTING AND INFORMATICS

DEPARTMENT OF COMPUTER SCIENCE

Project title: Cafeteria Management System of Haramaya University

Group member name Id no section

Cafeteria management System is developed by using Microsoft office 2016.The offline

Figure: 2 use case diagram.

Figure: 4 sequence diagram of how the student take Id’s barcode.

Figure: 6 sequence diagram that show how student punished.

Figure: 7 sequence diagram that show how the worker punished

Figure :8 Activity diagram for registration

Figure: 9 Activity diagram for account creation or barcode account.

Figure: 10 level 1 of activity diagram data flow

Figure: 11 level 2 data flow diagram

Figure: 12 class diagram

Figure:13 login state diagram

Figure: 14 scanning ID’s barcode state diagram

Table: 1 description of actor’s

HTML :- hypertext markup language

HU:- Haramaya University

CMS: Cafteria Management System

CMSHU:Cafeteria Management System of Haramaya University.

RAM:- Random acess memory

1.1 Background of the organization

1.2. Statement of the problem

Generally, the existing system works as follow: -

1.3.1 General objectives

1.4 scope of the project and limitation

 Information accessing is easy and fast.

The structure of existing the cafeteria management system

Shift leader Guard Tickers

Store men Injera house Bread

Fixed asset Consumabl Vegetable

Figure: 1 the architectural structure of the cafeteria management

2.2 Overview of Proposed System

The following list are the overview of the proposed system: -

2.3 Functional Requirement

 Table reservation module

2.4 Non-functional Requirement

2.5 The requirement of the proposed system

Saving Barcode Details to Database

2.6 constraint and assumption

3.1 Use case Diagram and description

Use case:  Reporting the servicing capacity cafeteria to the

 Register the student to give id’s that have barcode

 Control the students while they getting the services

Actor Name Tickers

 reporting the unethical students

Use case:  Check their id’s barcode

 Enter the cafeteria hall

 Get the food services

Table :1 of actors and their descriptions

Figure :8 Activity diagram for registration

Figure: 10 level 1 of activity diagram data flow.

Figure: 11 level 2 data flow diagram

Figure: 12 class diagram

Figure:13 login state diagram

4.2 Hardware and Software environment

figure: 15 process enter barcode

The code that implement our system is as follow:-

Sample code for login page

<body id="bd" class="auto fs3">

5.3 Testing Methods