CANTEEN ORDERING

SYSTEM
DONE BY:
HARSHITA
Table of Contents
1.Introduction
•Business Analysis Core Concept Model (BACCM)
•Requirements Classification Schema (RCS)
2.Stakeholders - RACI Chart
3.Problem Statement - Fishbone Diagram
4.Business Objectives - Mind Mapping
5.As-is and future process map (Flowcharts)
6.Scope of the Canteen Ordering System (Context Diagram)
7.Features
8.In-scope and Out-of-scope Requirements
9.Activity Diagram
10. ER Diagram
11. Business Requirements (Functional and Non-functional
Requirements)
12. Wireframes
 1.1 Business Analysis Core Concept Model (BACCM)
The need is to have an online canteen ordering system which can reduce the food wastage, operating
Need costs, manpower and increase employee’s work time.

The change is to automate the current canteen system to an online meal ordering system.
Change
The solution is to develop an online canteen ordering system in Java, that will allow the canteen users to
Solution order their meals and get it delivered to their workspace.

The context leading to change is that company has to cater 1500 employees during the lunch time (12-
Context 1pm). This causes huge rush in the canteen and leads to waste of employee’s time waiting for seat.

The value add with new system are:

External stakeholders:
•Supplier
•Project Manager
•Implementation SME
•Operational IT team
•Testers
Internal stakeholders:
Stakeholder •Inventory manager
•Chef
•Canteen manager
•Employees
•Meal deliverer
•Payroll team
Business Analyst
1.2 Requirements Classification Schema (RCS)
•
Business requirements : To automate the canteen ordering system by developing an online food ordering portal for the company that can
increase efficiency and save time and manpower.
• Reduce canteen food wastage by a minimum of 30% within 6 months following first release.
• Reduce canteen operating costs by 15% within 12 months, following initial release.
• Increase average effective work time by 30 minutes per employee per day, within 3 months.
• By making the ordering process automated and by delivering the food to the user's workstation, the canteen will be able to
operate with lesser manpower.
•

Stakeholder requirements : The key stakeholders are employees, canteen manager, meal deliverer, payroll manager.
• Employees : The users will be able to login and order food online through the system. The food will be delivered at their
workspaces and the amount of the meal will be deducted from their monthly salary.
• Canteen Manager : The canteen manager should be able to view the orders, take the inventory of all the orders and get them
cooked by the chef. The manager should be able to request a delivery to the employees’ workstation.
• Meal delivery person : After successful delivery of the meal the delivery boy should be able to close the online customer order.
• Payroll team : The team needs to calculate the total number of dishes ordered by each employee. and shall deduct money from
the employee’s salary.
•
Solution requirements :
• Functional requirements : An online web portal or mobile application is required to be developed to automate canteen food
delivery system. The system will be created and maintained on Java as it requires very little maintenance to be done on the
code.
• Non - functional requirements : This canteen ordering system is required to support a volume of 1500 employees ordering, so
the web pages should be light and render fast. The system should be scalable, self-explanatory and user-friendly.
•
Transition requirements : The users of the system should be trained enough to use it efficiently. A helpdesk team can be arranged to assist
in case any errors or problems are faced by the users while using the system.
 RACI CHART
Responsible Accountable
Stakeholders Consulted (C) Informed (I)
(R) (A)

Supplier R

Project Manager A

Implementation SME C

Operational IT team C

Testers R

Inventory manager R

Chef R

Canteen manager R

Employees I

Meal deliverer R

Payroll team I

Business Analyst R
FISH BONE DIAGRAM
Identify objectives of the new Canteen Ordering System
1.
Reduce canteen food wastage by a minimum of 30% within 6 months
following first release. The value of food thrown away each month by
examining the canteen inventory:
Previous - 25% wasted
Must plan for: Less than 15%
2.
Reduce canteen operating costs by 15% within 12 months, following initial
release.
3.
Increase average effective work time by 30 minutes per employee per day,
within 3 months.
4.
By making the ordering process automated and by delivering the food to
the user's workstation, the canteen will be able to operate with lesser
manpower.
AS IN PROCESS
FUTURE PROCESS
 Main features that need to be developed
Below are the main features of the system which needs to be developed:
1.Employee registration and login on the system
2.After successful login, employee should be able to see the updated food menu with all the dishes
3.The lunch orders cannot be made after 11 am, so that the chef has sufficient time to prepare the lunch for all the
employees
4.Employee can place the lunch order and confirm after adding all the desired food items into their cart
5.Once the order is confirmed, employee cannot modify or cancel the order
6.The canteen manager (order processor) views all the order an d assign them to chef for the preparation
7.The packed order will be assigned to the meal deliverer for the delivery to employee’s workstation
8.After the food is delivered, the meal deliverer will mark the order as closed
9.After completion of the order, the employees will be asked to fill the feedback form for their order
10.There will be no payment gateway so the bill amount will be deducted from the employee’s monthly salary by the
payroll team
In-scope requirements: Out-of-scope requirements:
•Employee registration / Login screen •Food vendor management
•Menu page •Food supplies out of stock notification
•Meal ordering screen (No order allowed after 11 am) •Chef and cook management
•Order confirmation screen •Chef and meal delivery person pay details
•Payment summary
•Order status page
•Meal delivery details
•Close delivered order by meal delivery person
•Monthly payroll adjustment
•Feedback submission
•Sales report for canteen management
SWIM LANE DIAGRAM
ER DIAGRAM
•Functional requirements : The canteen management system (CMS) have the
following functional requirements :
•Online web or mobile application
•Signup / Login screen to verify employee’s details (Only Unilever employees should be
allowed to sign up with their employee ID)
•Menu for food selection
•Food ordering not allowed post 11 am
•Food order and payment summary
•Order tracking feature
•Payroll management system
•Meal delivery person details
•Feedback submission
•
Non - functional requirements : CMS have the following non - functional
requirements :
•Usability : User friendly system and self-explanatory screens
•Scalability : Able to serve 1500 users of the office
•Performance : System should be light and render fas