DEBRE MARKOS UNIVERSITY

FACULITY OF TECHNOLOGY
DEPARTMENT OF INFORMATON
TECHNOLOGY
TITLE:-INDIVIDUAL PROJECT OF DMU CAFTERIA

Chapter one

Page 1
Introduction-----------------------------------------------------------------------5
1. Background of the organization---------------------------------------------5
1.1. General objective of the background------------------------------------6
1.2. Specific objective of the background-----------------------------------7
1.3. Tasks undertaken by the organization----------------------------------8
2. Statements of the problem----------------------------------------------------8
3. Objective of the project-------------------------------------------------------9
3.1. General objectives---------------------------------------------------------9
3.2. Specific objectives--------------------------------------------------------9
4. Significance of the system----------------------------------------------------9
5. Scope of the project------------------------------------------------------------10
6. Methodology--------------------------------------------------------------------11
6.1. System development methodology---------------------------------------11
6.2. Programming and database tools-----------------------------------------11
6.3. Data collection methodology---------------------------------------------11
7. Feasibility analysis------------------------------------------------------------11
7.1. Economic feasibility-------------------------------------------------------12
7.1.1. Cost--------------------------------------------------------------------12
7.1.2. Benefit-----------------------------------------------------------------12
7.2. Technical feasibility-------------------------------------------------------13
7.3. Operational feasibility-----------------------------------------------------13
8. Work break down structure---------------------------------------------------13

Chapter two
2. Business area analysis and requirements-------------------------------------14
Page 2
2.1. Definition business area analysis--------------------------------------------14
2.1.1. Study of the activity---------------------------------------------------------14
2.1.2. Problems of the current system--------------------------------------------15
2.1.3. Forms and reports currently used------------------------------------------16
2.1.4. Users of the existing system------------------------------------------------17
2.1.5. Business rule identification-------------------------------------------------17
2.1.6. Use case diagram-------------------------------------------------------------18
2.1.7. Essential use case description-----------------------------------------------19
2.2. Requirements definition--------------------------------------------------------19
2.2.1. Functional requirement-------------------------------------------------------20
2.2.2. Non-functional requirements-------------------------------------------------20
2.2.3. Essential user interface prototyping------------------------------------------21
Chapter three
3. Object oriented design--------------------------------------------------------------22
3.1. Systems use case-----------------------------------------------------------------22
3.2. User interface identification----------------------------------------------------23
3.3. Business rule identification-----------------------------------------------------23
3.4. Actor identification--------------------------------------------------------------24
3.5. Use case identification----------------------------------------------------------24
3.6. Use case description-------------------------------------------------------------25
3.7. Designing the system use case diagram---------------------------------------29
3.8. Sequence diagramming----------------------------------------------------------30
3.9. Activity diagrams-----------------------------------------------------------------33
3.10. Class diagram--------------------------------------------------------------------41

3.10.1. Description of class diagram--------------------------------------------43

3.11. User interface prototyping-----------------------------------------------------44

Chapter four
4. Conclusion and recommendation-------------------------------------------------46
Page 3
4.1. Conclusion-------------------------------------------------------------------------46
4.2. Recommendation------------------------------------------------------------------46
References------------------------------------------------------------------------------47
Appendix--------------------------------------------------------------------------------47

CHAPTER ONE
Page 4
 INTRODUCTION
Debre markos campus student’s cafeteria system is giving service for its
students manually. It has its own problem with managing the café, the students and
estimating the budget daily, weekly, monthly, yearly. Regarding to management,
workers stand in front of the get’s and receives the meal card of the student then
mark or tick on it.
But this process is too much lengthy and inaccurate. There are two cafés in the
university. The first café has six gets therefore six workers are marking student
meal card and the second café has five gets therefore five workers are marking
student meal card. But they could not manage them properly because of the
number of students which is very lot. Therefore other solution should be invented.
This is computerized café system. This system also helps to make the budget
calculation simple and accurate. And moreover the system has database, so that a
lots of works are done. Generally, the system simplifies the total work of the
cafeteria system.
1. Background of the organization
Debre Marko’s University is one of the thirteen Universities which were
established by the federal democratic republic government of Ethiopia. Its
foundation stone was laid in 1997 E.C/.2005. The university is located two
kilometers east from the central square of the town. It is laid out on 100 hectares. It
is found in north western part of Ethiopia at Debre Marko’s town.
The town is located 300 K.M North West of Addis Ababa and 256 K.ms South of
Bahir Dar (the capital of Amhara National Regional state). Its altitude is 2400ms
above sea level and it has a comfortable weather condition.

Page 5
After the completion of some buildings of the first phase of the construction (4
G+1 buildings of classrooms, 1 dining room, 12 G+2 dormitories, 2 G+1 libraries,2
cafeteria and 3 lecture halls), the university admitted the first 760 regular students
in February 1999 E.C/2007.
In the cafeteria the students are in the compound with the permitted course
registered they will have a food service in the cafeteria. The cafeteria service given
to students doesn't include extension students.
1.1. General objective of the organization
 To produce competent and innovative professionals.
 To provide community and consultancy service that contribute to the
national development objectives.
 To carry out problem solving research at local and national levels.
 With strong support of the government, great commitment and effort
from its staff, and support of different institutions, Debre Markos
University aspires to be one of the best universities in Africa that
contributes to the sustainable development of the nation.

Page 6
1.2. Specific objective of the organization
The student’s cafeteria in Debre Markos University is able to prepare foods
to all students three times in a day. without repeating so in order to make this
they should have to have to plan and their plan is as the table follows:-
Day of week Breakfast Lunch Dinner
Monday Bread with a cup Bread ,half injera Injera with
of tea with sherowote sherowote
Tuesday Bread with cook Bread ,half injera Injera with cook of
with a cup of tea with potato cook meet
Wednesday Bread with a cup Bread ,half injera Injera with
of tea with vegateble sherowote
Thursday Bread with a cup Bread ,half injera Injera with cook of
of tea with kiki meet
Friday Bread with a cup Bread ,half injera Injera with
of tea with kiki sherowote
Saturday Injera firfir with a Bread ,half injera Injera with cook of
cup of tea with kiki meet
Sunday Bread,ruzz with a Bread ,half Injera with
cup of tea injera with cook of
kiki meet

1.3. Tasks undertaken by the organization

Page 7
  By comprising with the students cafeteria’s committee they will
prepare by the money which is ready for them.
 In this time the student’s cafeteria about 5150 students are getting all
breakfast, lunch and dinner.
 By counting the number of students who goes to break they increase
the quality of the food by the profits.
 They complete the number of leaders in both shifts.

2. Statements of the problem

Currently the services that are given in our café are handled manually. And the
Number Of students who is getting service that is (breakfast, lunch and dinner) is
Increase every year. So to know (estimate) the cost for the ingredient per day,
week, Month and year become very difficult as our café handled it’s every day
activity manually.
Having the above problem, I am going to solve this by making it a computerized
System. This means, there is no need of “marking” on the students meal card as
there is a bar code reader which can read and store student’s ID number to the
database.
The system checks and make it impossible or easily identify the students who
are not member of the café and those who are trying to eat more than once at the
given meal period and also for those students who are trying to cheat. The other
main advantage of our system is after obtaining the number of students who got
service for(breakfast, lunch and dinner)can be easily calculated and generate very
clear report of each and every student meal cost and budget.

Page 8
On the other hand a manager could register student’s information in the data base
permanently. It uses for backup system and easily retrieve students information
when ever needed. It is also possible updating and deleting student’s information
from the data base. Generally, the advantage of this system is to give enough
information to the user.
3. Objective of the project
3.1. General objective
The objective of the proposed system is that to control illegal users (students)
of the café such as dismissal students, students who try to eat more than once at
one meal period and simplify the method of calculating the budget daily, weekly,
monthly and yearly. The system also minimizes the cost to be drafted for meal card
every year.
3.2. Specific objectives
 To generate a report, to minimize workers load and number and to speed up
the working system.
 To give enough information to the user (the manager) and operator and also
to fore cast the budget of next month with clear report.

4. Significance of the system

 To minimize work load of workers.
 The system displays a well formatted output as a form of report (report
generate).
 Announce students Food Menu (breakfast, lunch, dinner) for each day.
 For budget calculation.
 Minimizing the cost for printing meal card every year for all senior students.
 To generate a clear report.
Page 9
 5. Scope of the project
The scope of the system is up to their exists power. If there is no power the
system fails. Student’s information accessed directly from the database. The
student who has not a database record did not support by the system. This system
works only when we have a barcode reader access. The manager has a know how
the database works (know how about database). The manager can register, update
and delete student’s information but, both manager and operator can calculate Net
salary of the employee’s and view results. It supports student who has a database
record .The student who has not a database record did not support by the system.
Due to this having a database record is the primary condition to be the user of café.
The scope is Up to this. If the students information is not exist in the database the
system does not support it (the interaction between barcode reader and the
computer).

Page 10
 6. Methodology
6.1. System development methodology
For the success of the project, I will use PHP (Pre Hypertext Process).I chooses
this technique because, it is easy and clear technique.
6.2. Programming and database tools
 Front –End : html and PHP

Because:
 Allows data base integration with wide variety of
application

 Back-End: MY SQL.

Others: Microsoft word (2007) and UML software (for the diagrams).
6.3. Data collection methodology
Document Analysis (supplementary method)
 I try to discover all written documents about the organizational areas
relevant to the project, Such as Organizational Structure of the cafeteria
system, Different forms used on the current system.
7. Feasibility Analysis
A feasibility analysis is an evaluation of a proposal designed to determine the
difficulty in carrying out a designated task. Generally, a feasibility study precedes
technical development and project implementation.

Page 11
7.1. Economic feasibility
Economic analysis is the most frequently used method for evaluating the
effectiveness of a new system. Commonly known as cost / benefit analysis.
University Administration must accurately weigh the cost versus benefits before
taking an action. Cost and benefits can be categorized into the following
categories. Basically it is an analysis of the costs to be incurred in the system and
benefits derivable out of the system. The costs can be divided into two types:
1. Development costs
2. Operating costs Resource feasibility
This involves questions such as how much time is available to build the new
Cafeteria, when it can be built, whether it interferes with normal College
operations, type and amount of resources required.
7.1.1. Cost
Material Cost/Birr
pen 6.00
flash 270.00
paper 30.00
copy 10.00
Total 316.00
7.1.2. Benefit
After finalizing these project you have to incurs the spread of ICT in government
organization and also this new system by reduced the number of workers and easy
to control the cafeteria system will give services for students at short period of
time, workers we have to generate reports simply, easy to get information, Creates
Job satisfaction to the managers and students will be allowed to interact with the
system.

Page 12
7.2. Technical feasibility
 In order to satisfy this requirement the design should be simple and all the
different interfaces should follow a standard template. There will be the
possibility of changing manual to computerize.
 The system I will develop is easily understandable by the user of this
system.
7.3. Operational feasibility
The product will be operating in windows environment. Also it will be compatible
with the IE 6.0. Most of the features will be compatible with the Mozilla Firefox &
Opera 7.0 or higher version. The only requirement to use this online product would
be the internet connection.

8. Work break down structure

 Time table
No_ Task Time duration
1 Proposal writing submitting 24/7/04 - 08/8/04

2 Analysis documentation 09/8/04 - 29/8/04

submission

3 Design phase documentation 30/8/04 - 13/09/04

submission
4 Implementation 14/9/04 - 30/9/04

5 presentation 1/10/04 - 05/10/04

Page 13
 CHAPTER TWO

BUSINESS AREA ANALYSIS AND REQUIREMENTS

2. DEFINITION BUSINESS AREA ANALYSIS

Business area analysis is a process of collecting factual data, understand the
processes involved, identifying problems and recommending feasible
suggestions for improving the system functioning. This involves studying the
business processes, gathering operational data, understand the information flow,
and evolving solutions for overcoming the weaknesses of the system so as to
achieve the organizational goals. System Analysis also includes subdividing of
complex process involving the entire system, identification of data store and
manual processes.

The major objectives of systems analysis are to find answers for each business
process: What is being done How is it being done, who is doing it, When is he
doing it, Why is it being done and How can it be improved? It is more of a
thinking process and involves the creative skills of the System Analysis. It
attempts to give birth to a new efficient system that satisfies the current needs
of the user and has scope for future growth within the organizational
constraints. The result of this process is a logical system design. Systems
analysis is an iterative process that continues until a preferred and acceptable
solution emerges.

2.1.1. STUDY OF THE ACTIVITIES

Within this system the system designer does the activities that are absolutely
functional to the entire system. These include:-
 Students registration
 Resource sharing among students

Page 14
  Payment implementation doing by the students

2.1.2. PROBLEMS OF THE CURRENT SYSTEM

The problems of the current system are describes using PIECES framework. This
framework is used to identify the problems within an existing information system.
Therefore the problems indicated are dealing only with the existing manual system.
Performance
 Response time

The response time to a given task in the current working system is significantly
long due to the time taken to get the accurate information of students and different
organizational data takes much time.

Information

 Outputs
 The manual system generates only identification and giving meal card
for students any other information output is done manually.
 Inputs

 Information is not accurately captured, contains errors.

 Stored Data

 information is not secure

 information is not well organized

Economically

 Cost

Page 15
  The System doesn’t take that much cost. But since a budget is set by
the universities once, if price changes occur the system may be pushed
to cut some of its functionalities.
 Profits
 The Existing system is not aimed at producing profits.

Control (and Security)

 Too little security or control

 Input data is not adequately edited
 Data privacy regulations or guidelines are being (or can be) violated.
Efficiency (resource wise)
 Students, foods and other’s waste time.

 Information is redundantly generated.

Service
 The system is inflexible to new or exceptional situations
 The system is inflexible to change
 The system is not coordinated with other systems (stand alone system)

2.1.3. FORMS AND REPORTS CURRENTLY USED

There are different forms and reports used by the finance to control the
budget. Among the forms and reports used around the budget control, most of
them are manual. And still some of the forms are used in both Amharic and
English.

Forms
Name
ID NO.

Page 16
Department
Year
Date
Fig 2.1 forms

2.1.4. USERS OF THE EXISTING SYSTEM

Students come to the café and they give their meal card to the thicker and she/he
marks on student’s meal card which is time taking, exhausting and has no
accuracy. Because student may not enter without marking on their meal card in to
the cafe. Therefore they can eat again and again. This leads to collapse budget of
the students. Not only this but also students who come late may not get their
breakfast or lunch or dinner which may force students to terminate classes.
2.1.5. BUSINESS RULE IDENTIFICATION
Business rules are statements about the enterprise’s way of doing business. They
reflect business rules. Organizations have rules in order to: satisfy the business
objectives, make good use of resource, and conform to general business
conventions.

Business rules become requirements, that is, they may be implemented in

Software as a means of requirement of this software system.
 One photographs required to get a new meal card.
 To renew meal card one photograph is needed
 The requester should fill the obligation form and prepare one photograph if
he/she lost a meal card.
 Requires a renewed meal card with full information

Page 17
2.1.6. USE-CASE DIAGRAMS

Communicate with
University manager

Student dean

Manager

Manage cafeteria

v.manager

Search properties

Renew meal card

Thicker
Thick on meal card
Student

Page 18
Have meal card
Have dinner
2.1.7. ESSENTIAL USE-CASE DESCRIPTION
Actors
1. Student:-student is a legal user it uses in the cafeteria.
2. Manager:-manager is a person who manages the whole activity of the
cafeteria system.
3. Operator: - operator is a controller who controls to whether a student is
marked in the meal card by the thicker or not manages in the cafeteria
system.
4. Thicker: - thicker is a person it ticks in the meal card of the student daily.
2.2. REQUIREMENTS DEFINITION
In the cafeteria I need different types of requirements. Such as barcode reader,
database, computer and some related tools. And the barcode reader recognizes
student’s barcode and transfer to the system or computer. I also use database to
store student’s information permanently and temporarily. There is a relationship
between the database and the PHP (HTML) source code.
Hardware and software requirement
I use the following Hardware and Software requirements. The hard ware parts
are barcode, barcode reader, computer parts. And the soft ware parts are Mysql
that is used to create the databases and tables which are used to store, retrieves,

Page 19
delete and update information. I prefer mysql because it easily to function out, fast
to run and is easily dawn load it. I also use PHP this software is used to create user
interfaces, generate PHP source codes and connect with mysql.
The reason why I choose PHP tools is that because PHP is very power full and we
can easily create user interfaces. And also its sources code is free to access.

2.2.1. FUNCTIONAL REQIRMENTS

The goal of the System (DMU students’ café system) is to solve the problem of
Mark on students meal card manually which is a tedious work for employees and
Calculating cost analysis of students who use café of DMU campus. Knowing the
number of students who are currently using the café is very important: such as
daily, weekly, monthly and yearly with their consuming Budgets. A manager or
concerned body can take immediate and appropriate Action in accordance with the
budget. End users or students have no need of meal card to the ticker instead they
show their barcode to the bar code Reader to eat their breakfast, lunch or dinner.
For the manager or operator, it is advantageous to take measurement up on illegal
students who are trying to eat again and for those students who are dismissed but
still use the café.
The system works in the following way:-
The manager stores all students’ information in the database by giving necessary
information for each student. A student barcode number is automatically
generating .During mealing each student must reads their barcode number to the
machine (barcode reader). If the read barcode (students mealing id) matches with
previously stored in the database she/he can eat. In the other way if a student try to
eat more than once at a specific mealing period( at breakfast , lunch and dinner) the
system should take an appropriate action by showing light or by giving sound.

2.2.2. NON-FUNCTIONAL REQUIRMENTS

Security

Page 20
For the following operations only the manager has full authority.
1. To store students information in the database by randomly generating
(mealing id) for every student.
2. To cancel students information from the database.
Reliability
When we need to calculate budget we have accurate and readable data.
Readability
We have well formatted output when we retrieve information from the database.
2.2.3. ESSENTIAL USER INTERFACE PROTOTYPING

An essential user interface prototype is a low-fidelity model, of the user interface

for the system. It represents the general idea behind the user interface, but not the
exact details. Essential user interface prototypes represent user interface
requirements in a technology requirement. An essential user interface prototype is
effectively the initial state-the beginning point-of the prototype for the system. So,
now I don’t need to use technology-based prototyping tool in order to understand
and solve the problem.

Photo
ስም
Name…….

የመ.ቁጥር
ID NO…….

ዲፓርትመንት
Department

ዓመት
Year…….
Page 21
 የተሰጠበት ቀን
Date…….

Fig 2.2 User interface prototyping

የተማሪዎች ዲን
Student’s Dean

CHAPTER THREE
3. OBJECT ORINTED DESIGN

Object-oriented design is the process of planning a system of interacting objects

for the purpose of solving a software problem. It is one approach to design. The
software design is the discipline of defining the objects and their interactions to
solve a problem that was identified and documented during the objects problem.
What follows is a description of the class-based subset of object-oriented design,
which does not include object prototype-based approaches where objects are not
typically obtained by instancing classes but by cloning other (prototype) objects.

3.1. Systems use case

Use case diagram conclude that manager manages the whole cafeteria system
and she/he also controls operators. The barcode reader is response to the system.
The bar code readers after reading students bar code number, then send the
recognized data to the system. Student shows his student bar code to the machine
or bare code reader. Only the manager is full authorization on the system or he
must have a user account for himself.

Page 22
3.2. User interface identification
Use cases Items Used by
U1 Student shows BC student
U2 Manager Manages Café Manager/system
System
U3 System generates report system
U4 Operator Views Report operator
U5 BCR Reads StBC BCR
U6 System Give Action System
U7 Logon manager
U8 Logoff manager
U9 Makes Registration Manager/student
U10 Cancel Registration Manager/student
U11 Search Manager/operator
Fig 3.1.User interface
3.3. Business rule identification
Business rules are statements about the enterprise’s way of doing business. They
reflect business rules. Organizations have rules in order to: satisfy the business
objectives, make good use of resource, and conform to general business
conventions.
Business rules become requirements, that is, they may be implemented in
Software as a means of requirement of this software system.

Page 23
  The manager opens the login form.

 After login you see the adding, deleteing, search and reports of the student
and as well as the employee net salary form.

 If a student adding to the database we add it and you can work any other
work that means delete, search, and you can see reports.

 At the end the barcode reader machine that works if a student does not eat
you can send a message called ok! Get in and if a student come again to eat
you can send a message called don’t get twice.
3.4. Actor identification
Actors
1. Student:-student is a legal user who insert his/her ID to the machine when
he/she enters to the café.
2. Manager:-manager is a person who manages the whole activity of the
cafeteria system.
3. Operator: - operator is a controller who controls to whether a student
touches to the BCR to his BC or not and manages the system.
4. BCR: - It is a machine that recognizes students BC and sends to the system.
5. System: - It is a combination of hardware and software that takes an action
and calculates the Net salary of the employees.
3.5. Use case identification
Use case lists
U1. Student Shows BC: - student shows his/her BC to the BCR.
U2. Manager Manages Café System: - manager manages the cafe system by
observing the café activities and views reports from the system and takes an
appropriate action.

Page 24
U3. System generates report: - System calculates the Net salary of the employee
by referring the input from the database.
U4.Oprator Views Report: - Operator retrieves information from the database and
views appropriate information and report to the manager if needed.
U5.BCR Reads StBC: - BCR recognize students BC and transmit to the system.
U6.System Give Action:-After receiving from BCR the system checks if the BC is
matches with the stored one and take an appropriate action.
U7. Logon: manager logs on to the system using his user name and current
Password.
U8. Logoff: a user logs off from the system.
U9. Makes Registration: a manager registers students information in the database
permanently using their stBC as a unique key.
U10. Cancel Registration: a manager cancels student’s information from the
database whenever it is necessary. (E.g. If a student is completely dismissed, the
manager must cancel his information from the Cafeteria database.)
U11. Search: both the manager and operators are search and retrieve students
information from the database.

3.6. Use case description

U1. Student shows BC
Precondition Logon (U7)
1. Student enter in the cafeteria
2. Student show his /her BC to the BCR
3. The BCR recognize his / her BC
4. Entered U6

Page 25
 Post condition:-the BCR gives an action, If do not feed he/she says get in
and If feed it says do not get twice.

U2. Manager Manages cafeteria system

Precondition
1. Manager reserves student’s information and give unique BC for every
student.
2. View reports from the database and accept from operator.
3. Cancel and update student’s information.
4. Take an appropriate decision.
Post condition:-gives an action that means when one student deisms from the
university it cancel from the database.
U3.System Generate Net salary
Precondition
1. Accept input from user
2. performs appropriate calculation based on the input
3. Display in well formatted way.
Post condition:-It calculates appropriate (exactly) the net salary of the
employee.
U4.Oprator Views Result:-
Precondition
1. Operator chooses a menu (button) which contains different information.
2. Click on the chosen menu / button and view appropriate information. That is
the system display information.
Page 26
 3. Report information to the manager if he / she can make his / her own
decision.
Post condition:-It reports full information to the manager of the database.

U5. BCR Reads BC:

Precondition
1. The machine (BCR) must connect to the system (Computer).
2. BCR recognize each student BC.
3. Sends data to the system.
Post condition:-send information to the system.

U6.System Gives Action:

Precondition
1. Accept data from BCR.
2. Take an appropriate action.
Post condition: - It gives an action message.

U7. Logon
Precondition
1. Enter Password and user name.
2. If the Password and User Name is valid display home page.
Post condition:-If the password and user name not valid it sends message it’s
called please enter the correct user name and password.

U8.LogOOf
Page 27
Preconditions: None.
1. User elects to log off.
2. System ends current session.
Post conditions: user is logged off.

U9: make registration:

Preconditions:
1. Manager gets s students full information to register.
2. Set the primary key of student information (e.g. stID)
3. Fill student’s data into the database properly.
Post condition: Any requested Reservations have been made.

U10. Cancel reservation:

Preconditions: None.
1. Manager selects a Reservation.
2. Manager selects to cancel the Reservation.
3. Manager confirms that they wish to cancel the Reservation.
Post condition:-it deletes from all of the system.
3.7. Designing the system use case diagram
The Use case diagram is used to identify the primary elements and processes that
form the system. The primary elements are termed as "actors" and the processes
are called "use cases." The Use case diagram shows which actors interact with each
use case. A use case diagram captures the functional aspects of a system. More
specifically, it captures the business processes carried out in the system. As you
discuss the functionality and processes of the system, you discover significant

Page 28
characteristics of the system that you model in the use case diagram. Use case
diagrams have important use. Use case diagrams define the requirements of the
system being modeled and hence are used to write test scripts for the modeled
system.

Insert BC NO
Reads BC NO

Student
Login
Give action

View result Logoff

Manager Search
Calculate net
Salary

Delete student

Add student

Manage cafe

System

Operator

Fig 3.1.Use-case diagram

Page 29
3.8. Sequence diagramming
A sequence diagram is a kind of interaction diagram that shows how processes
operate with one another and in what order. It is a construct of a Message
Sequence Chart. A sequence diagram shows object interactions arranged in time
sequence.
Sequence Diagram for Registration

MANAGER ACTIVITY Login Page Form page

Validate User Name Password

Open login Page

Login

User Name Password Display Information

Page 30
MANAGER ACTIVITY Login Page Form page

Invalid User Name Password

Open login Page

login

User Name Password Display failed Information

Fig3.2 sequence diagram of login

Student Adding Page Form page

Insert student
Chose register button

Submit

Display inserting student

Fig3.3 sequence diagram of inserting student

Page 31
Student Delete Page Form page

delete the student

Chose delete button

Submit

Display deleted

Fig3.4 sequence diagram of deleting student

Student Search Page Form page

Searches the student

Chose search button

Submit

Display search student

Fig3.5 sequence diagram of searching student

Page 32
Note:-The sequence diagram of employee is like the above student diagram.

Bar code reader

Insert barcode
No
BCR reads stBCNO

Studen
t

Name
Get in to cafe Count no of students ()

Out from the cafe

Close ()

Fig3.6 sequence diagram of Barcode Reader

3.9. Activity diagrams

Activity diagrams are graphical representations of workflows of stepwise
activities and actions with support for choice, iteration and concurrency. Activity
diagrams can be used to describe the business and operational step-by-step
workflows of components in a system. An activity diagram shows the overall flow
of control.

Page 33
 Enter user name and password
Select type of user
Click on login button
Invalid

Valid

System displays student form

Insert in to the form

Invalid

Valid

System displays inserted student

Fig 3.7 Activity diagram of inserting students

Page 34
 enter user name and password
select type of user
click on login button
Invalid

Valid

system displays student form

click delete button

Invalid

Valid

system displays deleted

Fig 3.8 Activity diagram of deleting students

Page 35
 Enter user name and password
Select type of user
Click on login button
Invalid

Valid

System displays student form

Click search button

Invalid

Valid

system displays searched student

Fig 3.9 Activity diagram of searching students

Page 36
 Enter user name and password
Select type of user
Click on login button
invalid

Valid

System displays student form

Click report button

Invalid

Valid

System displays views reported

student

Fig 3.10 Activity diagram of reporting students

Page 37
 Student Enter into Café
(U1)

Student shows BCNo to BCR

BCR recognize student’s BCNo

Send an action to the System

Page 38
 Reserve Students Information
by giving BCNo

Cancel & Update View Reports from the

Student Information Database

Make Decision

Accept input from

User (U3)

Performs Calculation

Give well formatted report

Page 39
 Choose menu (U4)

Click on the Chosen Button

System Display Information

Must be connect to the System (U5)

BCR recognize Student’s BCNo

Send Data to The system

Page 40
 Accept Data from BCR (U6)

Is Student BC Equals the Stored Data?

No

Yes

Send Messages
Is More Than One?
No

You Try to Eat Illegally Allow

Fig 3.11 Activity diagram of Barcode Reader

3.10. Class diagram

Class diagram is a type of static structure diagram that describes the structure of a
system by showing the system's classes, their attributes, operations (or methods),
and the relationships among the classes.

Page 41
 1…*

Operator
+doCalculation():floa
t
+viewresult() :String
+Search():String

controls

1…*

3.10.1. Description of class diagram

Page 42
 1. Meal period: - is a class which has three sub classes. Any student who is a
café user and a member of DMU can eat his breakfast at breakfast period,
lunch at lunch period and his dinner at dinner period. A student cannot eat
more than once at each meal period for one day. At each meal period there
is a method called get Count () which returns the number of student at each
meal period. Firstly Number of students set to zero and when the BCD
reads stBD Number of students increment by one. This enables as how
many students eat at that meal period.
2. Employee: - is a class which contains manager and operators. A manager is
an employee who manages the cafeteria system. The following operations
are performed by him.
a) Register students information: - only the manager can register
student’s information.
b) Cancel Students reservation: - to cancel student’s information also
the manager has full authorization. Because it needs security. For
example if a student is academically dismissed, his information also
delete (cancel) from the cafeteria database. Therefore in this case
only the manager can delete his information.
c) Do calculation ():- the manager can calculate the budget from the
meal period which is control by the operator.
3. Operator:-Is an employee who controls the meal period. And he knows
how many students eat at that meal period.
4. Student: - The only task for students is showing his/her stBCNo to the
BCR and eats (if she/he is legal).

3.11. User interface prototyping

Page 43
Page 44
 CHAPTER FOUR
4. CONCULUSION AND RECOMMENDATION
4.1. CONCLUSIONS
From the findings derived from the survey process, I concluded that 80%
students indicated that they had no experience with the cafeteria services. 70 %
indicated that they are considering cafeteria solution. Furthermore, 51% of them
are willing to have computer based solution, 85% indicated that they prefer
to purchase the hardware and pay very little or no fees for other services.
This project is developed by using Design Research methodology and applying
object oriented design technique for analyzing and designing the prototype. Design
Research emphasizes on the knowledge generation inherited in the method. The
use case diagram is a visualization of a use-case analysis been applied. This project
also implement sequence diagram to display the overall flow of control in an object
oriented program. Thus, the second objective to design the cafeteria computer-
based reservation/management system is achieved.
From the findings that derived from the survey process, I concluded that cafeteria
computer-based reservation/management is confidently reliable and easy to use.
Page 45
Concurrently, the study found that the system has a multiplier effect to the
management services development.
To make this system more interactive and keep the pace of the technology of it, all
Stakeholder in the cafeteria system should understand the utility and implement the
system as the strategic point in order to improve the student’s cafeteria business,
develop the number of loyal manager and expand the design to get a higher quality
in services.
Computer-based reservation/management system is a valuable means to guide
manager to reserve all services or facilities offered by the cafeteria areas. The third
objective to develop the prototype of computer-based reservation/management
system is achieved.
The present study was determining the computer-based reservation/management
system.PHP programming and mySQL server are needed to construct this
dynamically computer based system.
4.2. Recommendation
To make this computer-based cafeteria system with more interactive and keep
rapidity with the technology of the all the cafeteria system. In the house rental area
should understand the utility and implement the system. As the strategic point in
order to improve their profit, develop the number of loyal managers and expand
the design to get a higher quality in services.

Appendixes
BC=Barcode

Page 46
BCR=Barcode Rader
STBC=Student barcode
U=Use case
STID=Student ID
DMU=Debre Markos University

References
1. www.dmu.edu.et (the website of DMU).
2. Manager of the cafeteria.

Page 47