Canteen Ordering System for Unilever

Simplilearn Project for CBAP

Project 1 ||Submitted By : Mahant Chowdapur ||

AUG 2021 Cohort 2

Table of Contents

1. Introduction
2. Company Background
3. Business Analysis Core Concept Model
4. Requirements Classification Schema
5. Identification of Stakeholders
6. Problem Statement
7. Business Objectives
8. As –is and Future Process Map
9. Scope of the Canteen Ordering System using Context Diagram
10. In Scope & Out of Scope Requirements
11. Activity Diagram
12. ER Diagram
13. Use of Wireframes

1. Introduction

Established over 100 years, Unilever is one of the world’s largest consumer goods companies.
It is known for their great brands, a global footprint and belief in doing the business the right
way.
Company have 149,000 people across the world. Company have over 400 brand names in
over 190 countries. Unilever is a global company with global Purpose.

2. Company Background

Unilever is a British-Dutch MNC FMCG company, headquartered in London, England. Unilever

is one of the oldest FMCG companies, and its products are available in around 190 countries.
In its UK offices, Unilever had around 1500 employees which were spread across 12 floors.
They had 2 canteens to cater to these 1500 employees. Each canteen could seat around 150
employees at a time. 
Business Analysis Core Concept Model (BACCM)

Need The need is to have an online Canteen ordering system for the employees which could save
considerable time of the employees, getting the food items they prefer, food wastage to be
reduced and in turn will reduce the cost

Change To automate the ordering system by making it online so that Canteen user gets to order meals
online to get their choice of food.
Solution The screens should be self-explanatory and very user friendly they want meals to be delivered
to their work station at a specified time and date. Java tools can be used
Context  1500 Employees
 2 canteens -Canteen space was designed only for 150 employees at a time which
resulted in waiting time of 30-35 mins
 Huge rush in the canteen during lunch hours resulting in employees wasting a lot of
time waiting for tables to be vacant.
 No payment gateway

Value  A system would have 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 their quality of work life and their productivity
 The food wastage will be reduced
 This will reduce the cost

Stakeholders External Stakeholders

 Domain Subject Matter Expert
 Tester
 Operational Support(IT)
 Implementation Subject Matter Expert
 Project Manager
Internal Stakeholders Business Analyst
 Canteen Manager
 Employee/Customer
 Chef
 Inventory Manager
 Payroll System
 Deliverer (delivery boy)
Requirements Classification Schema

1. Business Requirements
 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

2.Stakeholder Requirements

Customer The employee shall open the web page of the canteen ordering system, with the
updated menu and the list of all dishes available along with their prices.
Canteen The canteen manager also known as order processor should be able to view the
Manager 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 There shall be a meal deliverer (delivery boy) who shall deliver the lunch to the
employee's desk. After delivering the lunch, this delivery boy shall close the online
customer order
Payroll At the end of the month the payroll system shall calculate the total number of
System dishes ordered by each employee. The payroll system shall deduct money  from the
employee’s salary
Management No. of employees using the system, looking for the most popular dishes, satisfaction
of employees based on feedback, sales for each day, total monthly earnings and
order forecasting.

3. Solution Requirements

Functional Requirements

 User Registration and Login

 Upto date Menu for the day
 Order to be placed before the mentioned timings
 Create and edit the order before check out
 Delivery to the employee work station
 After delivery, the deliverer shall close the online customer order.
 Customer should be able to submit the feedback
 Generation of reports for management regarding the utilization of the canteen order system,
reduction in operational costs

Non Functional Requirements

 Scalability & Performance: Scalable for 1500 employees at a time

 Availability: System to be light and fast
 Usability: User friendly and self-explanatory
 Maintainability: Software in Java
 4. Transition Requirements
 Training to the employees and canteen staff
 Ease of use
 Data to be recorded securely and accessible
 Satisfaction of the employees on using the new Canteen order system

Project Tasks: 
1. Identifying stakeholders – Create a list of stakeholders (as taught in Business Analysis
Planning and Monitoring Knowledge Area)
2. Identify the problem statement in this system.
3. Identify objectives of the new Canteen Ordering System.
4. Create as-is and future process map (using flowcharts). You can use any of the popular tools
in the market like Microsoft Visio, Lucid Chart, Creately, Pidoco, or Balsamiq
5. As a Business Analyst working on this project, find out the scope of the Canteen Ordering
System. To find the scope you can use the case diagram (UML) or context diagram for the
same.
6. Write down the main features that need to be developed.
7. Write the in-scope and out-of-scope items for this software.
8. Draw an activity diagram for the system.
9. Draw an ER diagram of the system.
10. Write out the business requirements, both the functional and nonfunctional requirements. 
11. Draw wireframes or mock screens for any two of the features namely Menu Creation and any
other feature as deemed fit by the student. (Use the technique prototyping or wire framing
that is taught in the Training). You can use any of the wireframing tools like Microsoft
PowerPoint, Microsoft Word, Balsamiq, Sketch, Adobe XD, Adobe Illustrator, Figma, UXPin,
InVision Studio, InVision Freehand, or Moqups.

Task 1 : Identifying Stakeholders – Create a List of Stakeholders

RACI MATRIX

1. Responsible : the persons who will be performing the work on the task
2. Accountable : the person who is ultimately held accountable fr successful completion
of the task and is the decision maker. Only one stakeholder receives this assignment
3. Consulted : the stakeholder or stakeholder group who will be asked to provide an
opinion or information about the task. This assignment is often provided to the subject
matter experts (SMEs)
4. Informed : a stakeholder or stakeholder group that is kept up to date on the task and
notified of its outcome

Task 1.1: RACI MATRIX

Stakeholders Responsible Accountable Consulted Informed

 Supplier R
Tester R
Operational C
support(IT)
Implementation C
SME
Project A
Manager
Canteen R
Manager
Employees I
Chef R
Inventory R
Manager
Payroll System I
Deliverer R
Business R
Analyst

Task 2 : Identifying the Problem Statement in the current Ordering System

In its UK offices, Unilever had around 1500 employees which were spread across 12 floors. They had 2
canteens to cater to these 1500 employees. Each canteen could seat around 150 employees at a
time. 
Most employees would prefer to take their lunch between 12 noon to 1 pm. This led to a huge rush in
the canteen during lunch hours resulting in employees wasting a lot of time waiting for tables to be
vacant. 
Management calculated that it took around 60 minutes for employees to go and come back from
lunch. Almost 30-35 minutes were wasted in waiting in a queue to collect their food and get a table to
sit and eat. However, the time spent eating was barely 10-15 minutes. The remaining 10 minutes
were spent reaching and coming back from the canteen using the elevators. 
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.
Many employees have requested a system that would permit a canteen user to order meals online, to
be delivered to their work location at a specified time and date.

The above problem/Root Cause Analysis is represented by Fishbone diagram as below

Task 3 : Objectives of the New Canteen Ordering System

1. Reduce Canteen food wastage by a minimum of 30% within 6 months following first release
a. Previous – 25% wasted
b. 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

Task 4 : As – is and Future Process Map

4.1 As – is Process Map of the Current State

4.2 : Future Process Map for the System

 Task 5 : Scope of the Canteen Ordering System of Unilever can be known by the
Context Digram Shown below

Task 6 : Main Features that need to be developed

1. Employee Registration and Login on the system

2. Canteen manager Updates and displays list of the daily menu
3. Users can select dishes and create order, they should be able to edit the items before check
out
4. User will not be able to edit the order after the confirmation of the order on the system
5. The canteen manager views the orders and assign to Chef for the preparation
6. Request delivery by canteen manger to employee workstation
7. After delivering the lunch the delivery boy shall close the order online
8. Users must be able to submit the feedback
9. The payroll system shall calculate the total number of dishes ordered by each employee. The
payroll system shall deduct money from the employee’s salary. 
10. Generation of the reports and submission of the same to the Management
Task 7 : In-scope and out-of-scope items for this software

In-scope requirements:

 Employee registration / Login screen

 Menu page
 Meal ordering screen
 Order confirmation screen
 Order status page
 Meal delivery details
 Close delivered order by meal deliverer
 Monthly payroll adjustment
 Feedback submission
 Sales report for canteen management system

Out-of-scope requirements:

 Food vendor management

 Food supplies out of stock notification
 Chef and cook management
 Chef and meal delivery person pay details
Task 8 : Activity diagram for the System
 Task 9 : ER diagram of the System

Task 10 : Functional Business Requirements & Non-Functional Business Requirements

Functional Business Requirements

 User Registration and Login

 Upto date Menu for the day
 Order to be placed before the mentioned timings
 Create and edit the order before check out
 Delivery to the employee work station
 After delivery, the deliverer shall close the online customer order.
 Customer should be able to submit the feedback
 Generation of reports for management regarding the utilization of the canteen order system,
reduction in operational costs
Non Functional Business Requirements

 Scalability & Performance: Scalable for 1500 employees at a time

 Availability: System to be light and fast
 Usability: User friendly and self-explanatory
 Maintainability: Software in Java

Task 11.1 : Wireframes for the Unilever Canteen Ordering System

Task 11.2 : Wireframes for the Unilever Canteen Ordering System