Solution for Problem Statement 1 – Hospitability Industry

STAKEHOLDERS

ACTOR What he can do on the Software Created

Employee  Should be able to order the dishes he wants to eat.
 Should be able to register for payroll deduction.
 Should be able to submit feedback

Canteen  Can create, modify or delete menu items.

Manager  should be able to request a delivery to the employees’
workstation
 should be able to view the orders placed by the employees.
 He shall take an inventory of all the dishes ordered by different
users and get them cooked by the chef.

Delivery Boy  shall deliver the lunch to employee’s desk.

 After delivering the lunch this delivery boy shall close the
online customer order.

Payroll  The payroll system will handle payroll deductions

system  The payroll system shall deduct money from the employee’s
salary.

Management  Shall generate reports of canteen ordering system usage.

PROBLEM DEFINITION AND SOLUTION

 A lot of time is wasted by employees on going to the canteen to eat lunch.

 Employees don’t always get their choice of food they want because the Canteen runs out
of certain items.
 The canteen wastes a significant quantity of food by throwing away what is not
purchased.

Advantages and Objectives

Advantages of Canteen Ordering System:

  A system would save considerable time to those employees who use the service.
 It would increase the chance of them getting the food items they prefer.
 This would improve both their quality of work life and their productivity.
 The food wastage will be reduced.

Objectives:

 Reduce Canteen food wastage by a minimum of 30% within 6 months following 1st
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 users
workstation, the canteen will be able to operate with lesser man power.

EXISTING SYSTEM

 There is no existing system as the business set up is new. Not choosing an automated
system may be very time consuming, complex, manual, requires more manpower, leads
to a lot of time wastage, thus it is not at all cost effective. So, after doing the feasibility
study it was decided to create an automated canteen ordering system.

PROPOSED SYSTEM

The proposed system is a software system for tracking day to day management of the
lunch orderinf. The proposed system has the following advantages:

 User friendly interface

 Fast access to database
 Search Facility
 Report generation
SCOPE using Use Case Diagram (UML)

SCOPE using Context Diagram

IN SCOPE

 Login – The users of the system Waiter/Manager/CEO will be able to login using their
employee IDs & passwords.
 Creating Menu – The Manager will be able to add new menu items.
 Modify Menu – The Manager will be able to modify the price of any item existing in the
menu.
 Delete Menu – The Manager will be able to delete any existing menu items under the
selected category.
 Taking Orders – The Manager; will be able to track orders of employees
 Generate Bills – The system will be able to generate the bill of the lunch order placed by
employee.
 Fetching Reports – The CEO will be able to extract different types of reports based on
the requirements specified.
 A log out feature will be added so that the canteen employee/Manager/employees using
the system can log out once they are done with their work.
 Delivery boy should be able to close delivery order upon delivering.

OUT OF SCOPE

 Payment via cash, debit card, mobile wallets, credit cards is currently out of scope.
 Delivery of food within the same campus.
 Any demand for training to new or existing user after two weeks.
 Any maintenance request after two months of system rollout.
ACITIVITY DIAGRAM FOR THE SOFTWARE
ER DIAGRAM FOR THE SOFTWARE
CREATE MENU –
The user Manager will be able to create a new menu item.

Pre-Condition: The user with designation Manager can only access the create menu option.

Trigger: The user needs to add a menu item to the restaurant menu.

Basic Flow: The user can create new menu item.

1. The user will click on the menu tab present on the home page.
2. A page with 3 links (Create Menu/Modify Menu/Delete Menu) will be displayed.
3. The user clicks on Create Menu link.
4. A new page as below opens.
5. The user selects category from the drop-down list.
6. The user enters item description.
7. The user enters price for the menu item.
8. The item code auto populates.
9. The user clicks on Save.
10. New menu item created.

Exception Flow: The user enters an already existing item description.

Branch Point: Basic Flow, Step 9

1. System throws an error message stating that the item exists.

2. The user clicks ok.
3. The page clears all the textboxes & returns to the previous page.

Data Elements:

Field Name Field Type Data Type Mandatory Editable Remarks

Drop Down
Item Category List Text Y Y Predefined 5 categories
Item Description Textbox Alphanumeric Y Y
Item Price Textbox Numeric Y Y
System should auto
Item Code Textbox Alphanumeric Y N populate
Business Requirements:

Business Objective – 1:
Reduce Canteen food wastage by a minimum of 30% within 6 months following 1st release.
Scale: Value of food thrown away each month by examining the Canteen Inventory

 Previous - 25% wasted

 Must plan for: Less than 15%

Business Objective – 2:
Reduce Canteen operating costs by 15% within 12 months, following initial release.

Business Objective - 3:
Increase average effective work time by 30 minutes per employee per day, within 3 months.

Business Objective - 4:
By making the ordering process automated and by delivering the food to users workstation, the
canteen will be able to operate with lesser man power.

FUNCTIONAL REQUIREMENTS

1. Menu creation
2. Menu deletion
3. Menu editing / updation by menu manager
4. Order creation by employee
5. Order confirmation
6. View orders by order processor
7. Meal delivery closure in the system
8. Feedback submission by emplyees
9. Payroll deduction facility to be offered to users
10. Payroll deduction calculations
11. Following Report generation
 Which dishes are most popular?
 How many employees are using the system?
 Satisfaction of the employees on using the system. This should be tracked on basis of
feedback submitted by the employees.
 Sales for each day
 Total monthly earnings.
 Order forecasting i.e. predict which items are ordered at what time of the day.
NON-FUNCTIONAL REQUIREMENTS

System Requirement:

Scalability and performance: this canteen ordering system is required to support a

volume of 1500 employees ordering. Webpages should be light and render fast.

Usability:

The screens should be self-explanatory and very user friendly. Management would not
want employees not ordering from the system as they cannot understand the screens
and data fields on screen. The users should not find the system cumbersome.

Environments
We are going to be creating and maintaining the program in Java. We chose Java because it will
not change much over time and if we make it well, there will be very little maintenance to be
done on the code.