Professional Writing Service http://StudyHub.vip/AMBO-UNIVERSITY-WOLISO-CAMPUS-FACAULTY- 👈

1. compiled by IT 2nd yea Page i
AMBO UNIVERSITY WOLISO CAMPUS
FACAULTY OF BUSINESS AND ECONOMICS
MINI PROJECT ON CAFE MANAGEMENT SYSTEM
DEPARTMENT: - INFORMATION TECHNOLOGY
TITLE: CAFE MANAGEMENT SYSTEM
GROUP 6
Name of student.................................................................................IDNUMBER
1) 1.TOFIK ABDELLA...........................................................IT-RW-029/08
2) 2.YUSUF SUFI HAJI..........................................................IT-RW-039/08
3) 3.AYANA ADMASSU..................................................IT-RW-003/08
4) 4.LETA BEDESA................................................................IT-RW-015/08
5) 5.GADISE KEBEDE...........................................................IT-RW-009/08
6) 6.MUMMED HASEN.....................................................IT-RW-017/08
SUBMITTED TO INSTRUCTOR KASSAHUN.M
submitted date :may 18/2017

2. compiled by IT 2nd yea Page ii

3. i
Table of Contents
AKNOWELEDGEMENT ii
ABSTRACTS.................................................................................................................................................... ii
CHAPTER ONE (1) .................................................................................................................................- 1 -
SYSTEM DESCRIPTION........................................................................................................................- 1 -
1.1 Introduction.......................................................................................................................................- 1 -
1.1 Back ground of AUWC student cafe management system - 1 -
1.2 Description of the existing system - 1 -
1.2.1 Player in existing system: - 2 -
1.3.2 Major function of existing system - 2 -
1.3 Statement of problem - 2 -
1.4 Objective of project.......................................................................................................................- 3 -
1.5 General objective: .........................................................................................................................- 3 -
1.5.1 Specific objective:.....................................................................................................................- 3 -
1.6 Methodology and tools of the project ...........................................................................................- 4 -
1.7.1. Data gathering methodology...........................................................................................................- 4 -
1.8. scopes of our project and limitation..............................................................................................- 4 -
1.8.1. Scope of our project..................................................................................................................- 4 -
1.8.2. Limitation of our project...........................................................................................................- 4 -
Benefits and beneficiaries of the project...................................................................................................- 5 -
1.9. Benefits of the project...................................................................................................................- 5 -
1.10. Beneficiaries of the project .......................................................................................................- 5 -
1.14. Project schedule...............................................................................................................................- 6 -
CHAPTER TWO (2).................................................................................................................................- 6 -
2. REQUIREMENT ANALYSIS .........................................................................................................- 6 -
2.1.1 Functional requirements analysis..............................................................................................- 7 -
2.1.2 Non-functional requirement analysis........................................................................................- 7 -
2.2. Resource requirement analysis...........................................................................................................- 8 -
Software requirement - 8 -
2.3. overview of current system ..............................................................................................................- 9 -
2.1.4 Proposed system: .............................................................................................................................- 9 -
Over view of proposed system - 9 -
CHAPTER TH REE - 10 -

4. compiled by IT 2nd yea Page ii
SYSYTEM MODELING - 10 -
3.1 Conceptual modeling ........................................................................................................................- 10 -
3.2 Entity relation diagram(ER) - 10 -
3.2 DATA FLOW DIAGRAM - 12 -
3.3 Logical modeling - 13 -
FD (funcattion dependance)....................................................................................................................- 14 -
3.3.1 NORMALIZATION - 14 -
3.3.2 Second normalization - 16 -
3.3.3.Third normalization .......................................................................................................................- 17 -
3.4 Recommendation.............................................................................................................................- 17 -
AKNOWELEDGEMENT
The generous corporation of many people has a contribution for the success and completion of this project.
Our special gratitude to our advisor instructor MR KASAHUN for his commitment and constructive
comments that he gave us for the success of this project. We are also very grateful all our group member for
their cooperation, for their participation and for their moral support. And also we would like to thank the
employees of Ambo university woliso campus’s café for their contribution for the success of this project.
Finally we would like to thanks to Ambo university Woliso campus and its employees who support us for the
completion of our project.
ABSTRACTS
This project was developed to solve the problem related to café management system of Ambo university
Woliso campus. This café management system is primary using manual for café management system.
The café management system can use two systems. This is manual and automated system. Manual café
management system is system attending signing system .this system is the systems that use the more: human
power, time and resources and can’t provide employee service module.
Automated system is a system that saves human power, resource and time and also provides self service for
employees. This automated system is more efficient than manual one.
Since automated system is use electronic devise for ticking the meal card of student when they want to get
café it uses less time tick and check for the meal card barcodes and it replace the ticker and employees that

5. compiled by IT 2nd yea Page iii
serves around the place of standing student while it works with checking hidden codes and alarming on an
error take placed.
This system is also effective than manual café management since the system uses less time and easily access
able for the user.

6. compiled by IT 2nd yea Page - 1 -
CHAPTER ONE (1)
SYSTEM DESCRIPTION
1.1 Introduction
Ambo university Woliso campus café management system was constructed to support serves for student of
campus and employees who works in it .Ambo university Woliso campus café management system was
built in compound of Ambo university the branch of Woliso that found in Woliso town that are found
almost 114 KM distance from Addis Ababa town
Café management system of Ambo university woliso campus was started working in 2001 etc.
This project regarding of this campus to improve the problem faced the student cafe management. It contain
three chapter
Ambo university woliso campus is one of the largest organizations located in central part of Ethiopia in
south west part of direction of Addis Ababa. It is one of branches of Ambo University and found in woliso
town which of the capital city of south West Zone of Oromia region. It is 64Km from main campus.
Ambo university woliso campus located a distance of 114km from capital city of Ethiopia (Addis Ababa).
It was established in May 2001 E.C collage standard and developed into campus in 2001 E.C by the
government of Ethiopia by 24 teacher and three permanent worker as well as 60 contract workers and it was
named as Ambo University woliso campus
1.1 Back ground of AUWC student cafe management system
Ambo University woliso Campus student cafe management system has own their historical developments.
It has one largest building that have three rooms or section which is used for different purpose
Out of these room one for kitchen, two rooms for student service not only for student service but also
Used as hall at the time of meeting etc.
1.2 Description of the existing system
The existing system of AUWC student cafe management system perform different task. The most popular
task performed in the system.

7. compiled by IT 2nd yea Page - 2 -
 Thicker for student meal card
 Generating report
 And different kind of meal card are prepared
 Cost sharing
1.2.1 Player in existing system:
Players are a participant in the system, or a person who get benefit from the system, by acting different
tasks in the system. The main players of café management system are:
 Student
 Manager
 Ticker
 Student service
1.3.2 Major function of existing system
Major function of woliso campus student café management system is preparing meal card every year.
Ticking meal card of students every time when students want to eat food
Preparing cost sharing fill form every semester and storing it as the document.
1.3 Statement of problem
This is used to identify and understand the problem of existing system or current system.
Some activity such as ticking meal card and controlling the sequence of students and prevent student from
two time eating id done manually.
The manual system has the following problems.
Time consuming: since it is a manual system each activities are done by human power each activity
consumes time .for example when employee or tickers wants to tick meal card of one student it needs to
open all pages to search the current pages that he wants to thick, while all this activities are need times it
consume the time and take more time than the automated system.
The security problem: while all students should have to wait until the meal card of student in front of him is
ticked by the ticker the student in the behind may disturb when he compete with the student in front of him
toward the ticker therefore the security of café may be disrupted with this

8. compiled by IT 2nd yea Page - 3 -
Ticking meal card is not easy: for ticking the meal card the thicker must have open all pages of
meal card to search the current page that he want to thick on it therefore ticking meal card is not an
easy task.
Updating the manual meal card is not an easy task: In every year the manual meal card is expired
and it needs to take anew meal card every year if it is a manual updating is not a difficult matter
while it is renewed or updated by the machine thicker easily. While the manual meal card is need a
new photo every year there can be extravagance of photo every year, if t s automated while your
name and tour photo are encoded one time it is not need always a new photo.
Expenditure of the resources: while it’s a manual system t needs an employees at least it needs two
employees since this employees are take a salaries ‘every month ,this means the café system
management may pay salaries large number of money in one year .There is a probably to create
errors: while the system is manual there is a probability to create errors when the ticker is ticking
meal card .on the manual meal card there is a three section. It is option box (check box)there is a
probability to make error during ticking time
1.4 Objective of project
Our objective is to change manual ticking meal card to automatic ticking through machine.
1.5 General objective:
Our main function of our project is ticking meal card by the machine and generate report every year
automatically. Also our new machine is going to register all information go with café. Like: registering all
days every time when student uses a machine to tick a meal card.
1.5.1 Specific objective:
o Saving time
o Ticking meal card manually
o Generating report every time automatically
o Saving human resource by using machine
o Registering the day of tick
o Saving money paid for …………………etc.

9. compiled by IT 2nd yea Page - 4 -
1.6 Methodology and tools of the project
Methodology is the process of gathering, analyzing, implementing and coding the requirement. In this
document we want to mansion only methodology of gathering and analyzing
1.7.1. Data gathering methodology
Methodology is approaches for solving problem by using different techniques those techniques are:
Interview: it is used to collect data detail about the current system. By going the organization and ask them
about the café management system
Interview is used to;
 Allow us to clarify question unlike the quaternaries, in interviewing we can ask additional question
 Allow the informant to respond in any manner
Document reviewing: this thing we cannot easily understand by using interviewing, we must review
documents to elaborate the system to collect data.
Observation: we use the interview to check the date gathered by interview and also to understand more
about the system, we will use this tool by
 Time sampling; the project member will go to the organization two times in the week based on
work load of the employees.
 Event sampling; project member also will understand the current system problem of the system
without time limit.
Brain storming
Brain storming is the general idea that the project members have agreed after detail discussion about the
problem.
1.8.scopes of our project and limitation
1.8.1. Scope of our project
The scope of our project to make a system, a system that record the time and attendance of the users and
ticking the meal card of student automatically.
1.8.2. Limitation of our project
Limitation of this project is the area which project cannot focus as its scope.

10. compiled by IT 2nd yea Page - 5 -
 Calculation of cost sharing of food
 Specifying the food time
 Scheduling
Benefits and beneficiaries of the project
1.9.Benefits of the project
Benefit of this project is reducing the time consumed over all the performance process café management
system of Ambo university woliso campus and keeping quality among other facilities
A). tangible benefits; this project will saves resources appropriately like
 Reducing over load of works on each employee
 Increase the performance efficiency of café system
 Consuming of time while employee working on their respected tasks.
 Expense of money for different material like meal card.
B). intangible benefits
 Because of the system can be expandable other function can be added
 Café system of Ambo university uses new technology to manage system
 Project cost; the cost which is expensed to complete the project. This is categorized into tangible
and intangible cost
a)Tangible cost; a cost that can be calculated accurately
The money which café management system of ambo university pay for the new system
 Time and device
b).intangible cost; is one that cannot be measured directly
 Error handling
 Efficiency of the system.
1.10.Beneficiaries of the project.
For café management system of ambo university woliso campus

11. compiled by IT 2nd yea Page - 6 -
 Save the payment of money
 Easy manage resources
For employees
 For the system is very speedy they save their times
For the student
 Students can easily use the system without consuming of time.
For system developer
 Develop the skill of the designers’
 Give satisfaction of the designer
 Generate income for the designer
For other researcher
Use it as a reference material during the research.
1.14. Project schedule
CHAPTER TWO (2)
2. REQUIREMENT ANALYSIS
Requirement analysis is general property related with activity and tasks of the proposed system.
no Activity duration start End
2 Proposal 3 days 12/06/2017 30/06/2017
4 Designing 4 days 12/08/2017 13/08/2017
7 Documentation 8 days 01/09/2017 09/09/2017

12. compiled by IT 2nd yea Page - 7 -
Requirement is a condition or capability proposed by a software or system component in order to solve a
real world problem
so as we recognized in our project requirement that existed in our project is look like these:-
 To reduce problem of existing system
 To increase effective time management
 To increase resource management
 Increasing performance of the work by machine
 Increasing efficiency ways of ticking student meal card
 Generally to put the whole system under a single machine that reduce human effort, time
and resource management
2.1.1 Functional requirements analysis
Functional requirement is behavior of the system that support user goals, task or activities
It is the function s or service of the system
These functional requirement capture the intended behavior of the system this behavior may be expressed as
service, tasks or function the system is required to perform these are listed below:
 The expected machine or software aimed to search and accept student meal card and display
report to server
 The main point expected from our machine or software is the capability to tick and check student
meal card
 The system reflect the result of ticking student meal card by showing different color or sound
 As to be the software can minimize ticker role in the ways ticker can simply control system
 The system record information of the meal card and generate report to server to whether the user
use twice or not
2.1.2 Non-functional requirement analysis
Non-functional requirement deal with behavioral property that the system must have
Non-functional requirement is constraint and quality of the system
It is how well the system provides service for the user these include:-

13. compiled by IT 2nd yea Page - 8 -
 Performance
 Speed
 Reliability
 Maintainability
 Cost
 Security
 Organizational menu
2.2. Resource requirement analysis
There are two types of resource requirement analysis those are:-
 Software
 Hardware
Hardware requirement analysis
 Monitor
 Keyboard
 Processor
 mouse
Software requirement
Activity Tools
Documentation Ms word
To Design Microsoft office visio 2017
Table1. Software requirement tool

14. compiled by IT 2nd yea Page - 9 -
2.3. overview of current system
Current system is an existing system that are working manually, all activity performing in the system like
ticking meal card, generating report, recording information, diagnosis information and many other works
are being working manually.
Practical activity in existing system
Many practical works in existing system that are in manual working are
 Ticking meal card: it is the ticker activity of existing café management system, it is every meal card
have to be ticked by ticker manually for each student.
 Generating report: an activity of generating report in café management system in server office, it
has to be recorded by worker of service office manually
2.1.4 Proposed system:
Over view of proposed system
A proposed system instead of existing system is changing manual ticking system to automated machine.
Practical works in proposed system: a proposed system is going to works with automated way that is every
meal card has to be ticked by machine that has automated to tick meal card
Which is every student have come to machine and insert their electronic meal card into automated machine
that prepared for ticking meal card, as soon as student insert meal card to machine the machine have to tick,
record or read bar code in the electronic meal card automatically.
Then the machine has to alert when it finished its works to get out meal card from the machine.
Recording information: this proposed machine has to have storage that store the student meal card
calculation like date, time name and ID number.
After that the manager and other workers that need information from machine in simple way they can get
full information from storage of proposed system.
That machine has to have an alert sound when some student try to repeal insert electronic meal card into
machine that call police.

15. compiled by IT 2nd yea Page - 10 -
CHAPTER TH REE
SYSYTEM MODELING
3.1 Conceptual modeling
In this concept, we focus on creating a logical data model. Although there are several ways to model data,
we will present one of the most commonly used techniques: entity relationship diagramming, a graphic
drawing technique developed by Peter Chen1 that shows all the data components of a business system.
Conceptual data model is the crucial or vital model that indicates the detail of process to show how the
process can process in internal of it. The common conceptual data model is entity relationship diagram
which is better to show internal of process.
3.2 Entity relation diagram(ER)
An entity relationship diagram (ERD) is a picture which shows the information that is created, stored, and
used by a business system.
The ERD also communicates high-level business rules. Business rules are constraints or guidelines that are
followed during the operation of the system.
3.2.1 Elements of an Entity Relationship Diagram
There are three basic elements in the data modeling language (entities, attributes, and relationships), each of
which is represented by a different graphic symbol. There are many different sets of symbols that can be
used on an ERD. No one set of symbols dominates industry easily better than another.
Entity: The entity is the basic building block for a data model. It is a person, place, event, or thing about
which data is collected—for example, an STUDENT, an MANAGER, and a TICKER. An entity is depicted
by a rectangle, and it is described by a singular noun spelled in capital letters. All entities have a name and
description of it called attribute or instance.
Attribute: An attribute is some type of information that is captured about an entity. For example,
NAME,ID NO ADDRESS,AGE are all attributes of an STUDENT. It is easy to come up with hundreds of
attributes for an entity), but only those that actually will be used by a business process should be included in
the model. Attributes are nouns that are listed within an entity.
Therefore Entity relationship diagram for our project contain the above things means entity with its attribute
and relation between them as below within full description of their relation

16. compiled by IT 2nd yea Page - 11 -

17. compiled by IT 2nd yea Page - 12 -
Fig 3.1 entity relationship diagram (ERD)
3.2 DATA FLOW DIAGRAM
Data flow diagram is another important diagram dynamic aspect of the system. Data flow diagram is
basically a flow chart to represent the flow form one activity to another activity
fig 3.2 shows data flow diagram

18. compiled by IT 2nd yea Page - 13 -
3.3 Logical modeling
Table of relatioship is show the entity and enntities attributtes in the databases, even though the table
relation for our project according entity relationship diagram has been drawed formulated as below.
Table for those attributies (stid no,name,address,phone no, sex,age,office no,E-mail,SSN. salary,) .Those
we have been mentioned attriribute for the database in thise case it should normalized, to normalize first it
could be fuctional dependant
STUDENT TABLE
ID FNAME LNAME AGE SEX PHONE_NO BDATE ADDRESS
105 Tofik abdella 21 M 936079102 1.9999E+004 Harar
TICKER TABLE
TID FNAME LNAME PHONE_NO ADDRESS SALARY
108 Tola Abdisa 92334567 harar 6000
FINANCE TABLE
SSN FNAME OFFICE_NO ADDRESS ACCOUNT_NO FAX
134 AUWCF 102 Woliso 2345678890 email.com
MANAGER TABLE
MGID FNAME LNAME OFFICE_NO EMAIL PHONE_NO SALARY
20 John Mickel 1 john@email.com 987657654 20000

19. compiled by IT 2nd yea Page - 14 -
EMPLOYEE TABLE
EMPID FNAME LNAME PHONE_NO SKILL ADDRESS SALARY
109 Wakjira fayyera 944567689 Deploma woliso 4000
SKILL TABLE
EMPID SKILL
107 DEGREE
FIg 3.2 relational table
FD (funcattion dependance)
stid name,age,address,phone no,bdate
Mgrid ,name,office no,phone no,E-mail,address,salary
ACCOUNT NO,SSN,name,address,office no,fax
tiid name,phone no,salary,address
empid name,phone no,address,age,skill
3.3.1 NORMALIZATION
First normalization
first normal form is defined in the definition of relation table it self.this rule defines that all the attribute in
the relation must have atomic domain

20. compiled by IT 2nd yea Page - 15 -
first normalization is the same to the funcational dependance that has been depicted, but the difference
between them is that first normalization a cell should contain atomic value, so it look like thise:
1NF
STUDENT TABLE
STD(stid name,age,address,phone no, sex,bdate)
ID FNAME LNAME AGE SEX PHONE_NO BDATE ADDRESS
105 Tofik Abdullah 21 M 936079102 1.9999E+004 Harare
MANAGER TABLE
MGR(Mgrid ,name,office no,phone no,E-mail,salary)
MGID FNAME LNAME OFFICE_NO EMAIL PHONE_NO SALARY
20 John Michel 1 john@email.com 987657654 20000
TICKER TABLE
TICKER(tiid name,phone no,salary,address)
TID FNAME LNAME PHONE_NO ADDRESS SALARY
108 Tula Abdias 92334567 Harare 6000
EMPLOYEE TABLE
EMP(empid name,phone no,address,salary,skill)
EMPID FNAME LNAME PHONE_NO SKILL ADDRESS SALARY
109 Wakjira fayyera 944567689 Deploma woliso 4000
FINANCE TABLE

21. compiled by IT 2nd yea Page - 16 -
FINANCE(SSN,name,address,office no,account no,fax)
SSN FNAME OFFICE_NO ADDRESS ACCOUNT_NO FAX
134 AUWCF 102 Woliso 2345678890 email.com
3.3.2 Second normalization
A relation in the second normal form if and only if it is in first normal form and all the non key attributes
are fully functional dependent on the key
In second normalization each attribute fully functionaly dependent on primary key, means that non key
attribute should be full functionaly dependent to primary, so the feature of second normalization is to full
fill this property. And also it should be first normalization to come with secod norm.
STUDENT(stid name,age,address,phone no,bdate)
stid->stname,bdate,age,address,phone no
MANAGER(Mgrid ,E-mail, name,office no,phone no,address,salary)
Mgrid,E-mail mgrname,office no,phone no, ,address,salary
Mgrid office no, address,Mgrname,salary
E-mail Address, phone no,
TICKER(tiid name,phone no,salary,address)
tiid tname,salary,phone no,address
EMP(empid name,phone no,address,age,skill)
empid name,phone no,address,skill,age
FINANCE(ACCOUNT NO,SSN,name,address,office no,fax)
Account no SSN Fname,mgrid,emid,office no,addresss
all the above four tables are in 2NF since they are in 1NF and there is no partial dependency in them.

22. compiled by IT 2nd yea Page - 17 -
3.3.3.Third normalization
A relation is Third normalization form if it is already in 2NF and every non-key column is non-transitively
dependent upon its primary key in the other word all non-key attributes are functionally dependent only
upon the primary key.
Third normalizaation is the part of normalization and crucial one because it minimize the redudance of the
of data in database. Third normalization is focus on the detect the transitive rule and it should be second
norm.
STUDENT(stid name,age,address,phone no,bdate)
MANAGER(Mgrid ,E-mail, name,office no,phone no,address,salary)
Mgrid Email,office no, address,Mgrname,salary
E-mail Address, phone no,
Mgrid name,office no,phone no,address,salary
TICKER(tiid name,phone no,salary,saddress)
tiid tname,salary,phone no,address
EMP(empid name,phone no,address,age,skill)
empid name,phone no,address,age
EMP(emp,skiil)
FINANCE(ACCOUNT NO,SSN,name,address,office no,fax)
account SSN,Name,Address,Office no,fax,
3.4 Recommendation
While doing this project we have faced different challenges. But by the help of many member of cafe and
our group member we are able to reach on this. So now we strongly recommend the Information
Technology department concerned one’s to appreciate their commitment to help the student who doubted
with any challenges. And also the school prepared nice resources so that to complete the project with not
much challenges. In this we would like to forward our deepest feeling
. the cafe organization has to support all students who want to develop this project.

23. compiled by IT 2nd yea Page - 18 -
THE END OF OUR PROJECT !!!
THANK YOU !!!!