This document presents a proposal for a Cafeteria Management System (CMS) for Sanothimi campus. The system would allow for menu management, ordering interfaces, and bill printing. It aims to increase efficiency and save time and money compared to the current non-computerized system. The proposal outlines the objectives, limitations, waterfall development methodology, data models, and timeline. The system would be a desktop application to manage food ordering and billing without home delivery capabilities. It is intended to reduce paperwork and provide efficient services to students and staff.

1. Proposal Defense
By:
Suresh
Chaudhary
Third
Semester
Sanothimi
Campus,Bhaktapur
1

2. Title of Project:
Cafeteria Management System in
Sanothimi campus(CMS)
This software can be called in any of the following
names:
 Canteen management system
 Hotel management system
 Restaurant management system
2

3. Background and Introduction
 Cafeteria management especially manages the
menu items, gives interface to the orderings,
expenditure report .
 User to manage the item and manage the
category of food too.
 This project also gives the interface for the bill
printing purpose in instant time.
 It is designed to increase operational efficiency,
saving our money and time, maximizing profit and
provide more security.
 It is designed to avoid paper work.
3

4. Statement of problem
 The current system of cafeteria is not
computerized.
 There is no billing system.
 They cannot take a timely order and provide a
timely service. due to lack of Staff and waiter.
4

5. Objective
The Project Objective are:
 Develop a desktop application, which can easily
& effectively manage ordering and billing of food
items.
 Reduce paperwork.
Limitation
 Home delivery service is not allowed.
 It is only provide the service of student and
teacher.
5

6. Software Development Methodology
Waterfall Model
 Sequential model, Classical model.
 This model is simple and easy to understand and
use.
 It is easy to manage due to the rigidity of the
model – each phase has specific deliverables and
a review process.
 In this model phases are processed and
completed one at a time. Phases do not overlap.
 Waterfall model works well for smaller projects
where requirements are very well understood.
6

7. For this Project, I have used the ‘Waterfall’
methodology because of
 User well understands software requirement.
 Requirements are very well documented, clear
and fixed.
 Technology is understood and is not dynamic.
 Product definition is stable.
 The project is short.
 There are no ambiguous requirements.
7

8. Data Dictionary
Field Type PrimaryKey Default
UserId int32 yes
UserCode varchar(11) No
RoleId int32 No
Password varchar(50) No
UserDesc Varchar(max) No
Table
Name:UserTable
8

9. Table Name:-RoleTable
Field Type Primary key Default
RoleId int32 yes
RoleCode varchar(54) No
RoleName Varchar(50) No
RoleDesc Text No
9

10. Table Name:-OrderTable
Field Type Primary key Default
OrderId int32 yes
CostumerName varchar(100) No
Field Type Primary key Default
CategoryId int32 Yes
CategoryCode varchar(11) No
CategoryName varchar(100) No
CategoryDesc Text No
Table Name:-CategoryTable
10

11. Process and Data Modeling
Flow Chart
11

12. ER-Diagram
Username
Admin
Creates
User
Creates
UserCode
password
userId
Role
RoleId
RoleCode
RoleDesc
RoleName
Category
CategoryId
CategoryCode
CategoryName CategoryDesc
belongs Food
FoodId FoodCode CategoryId
FoodName
Price
FoodDescription
Generates Bill
FoodOrderId
OrderId
FoodName
SalesDate
Cost
Rate
Quantity
12

13. Context-Diagram
13

14. Project Timeline (Gantt chart)
ID TaskName Start Finish Duration
Aug2015
7 8 9 10 16 1813 1512 171411
1 .4w8/10/20158/7/2015Feasibility
2 .3w8/12/20158/11/2015Analysis
3 .3w8/13/20158/12/2015Design
4 .2w8/14/20158/14/2015Coding
5 .2w8/17/20158/17/2015Testing
6 .2w8/18/20158/18/2015Implementation
7 2.2w8/21/20158/7/2015Documentation
19 20 21
14

15. Delimitation
15
 It is not Web based application.
Expected Output
 To make a computerized system and making an
efficient and user friendly desktop application for
the fast transaction and services to the students
and staffs of the college.

16. References
 R. Thomas, G. Semecko, H. Morarji, G. Mohay, “Core
Software Engineering Subjects: A Case Study (’86-
94’), in Proceedings of the Software Education
Conference 1994 IEEE,1995
 S.Tockey, “Recommended Skills and Knowledge for
Software Engineers ”, in Proceeding of the Twelfth
Conference on Engineering Education and Training,
IEEE 1999
ONLINE RESOURCES
 http://www.w3schools.com
 http://www.tutorialspoint.com/
 http://www.lynda.com
16

17. Thank You
17