Canteen Ordering System for Unilever

Simplilearn CBAP Certification

Project 1

Project Submission by:

Ameen Ahmad
On
27th April 2024

1|Page
Contents
 Project Overview and Objectives......................................................................................3
Company Overview......................................................................................................3
Project Overview..........................................................................................................3
Project Objectives........................................................................................................4
 Business Analysis Core Concept Model ………………………………………………………………………5
Need............................................................................................................................ 6
Change......................................................................................................................... 6
Context........................................................................................................................ 6
Stakeholders................................................................................................................ 7
Value............................................................................................................................ 7
Solution........................................................................................................................ 7
 Requirement Classification Schema….……………………………………………………………….…….8,9
 Project Tasks………………………………….….…………………………………………………………….…….…10
Task 1: Stakeholders List.............................................................................................11
Task 2: Problem Statement.........................................................................................12
Task 3: Objectives of Proposed System......................................................................12
Task 4: Current and Future Process for Canteen Ordering System........................13,14
Task 5: Context Diagram for Scope of the Canteen Ordering System.........................15
Task 6: Main Features of Proposed System................................................................16
Task 7: In-Scope and Out-of-Scope Requirements............................................17,18,19
Task 8: Activity Diagram of the System.......................................................................20
Task 9: ER Diagram of the System...............................................................................21
Task 10: Functional and Non-Functional Requirements.............................................22
Task 11: Wireframes.........................................................................................23,24,25

2|Page
Project Overview and Objectives

Company Overview
Unilever is a British-Dutch Multi-National FMCG company, headquartered in London, England.
Unilever is one of the oldest FMCG companies and its products are available in approximately 190
countries.

Project Overview
In its UK offices, Unilever has around 1500 employees all of which are spread across 12 floors. They
had 2 canteens to cater to these 1500 employees. Most employees would prefer to take their
lunch between 12 noon to 1PM. Each canteen could seat around 150 employees at a time.

To alleviate overcrowding of the canteens, reduce costs and improve service to employees,
management has embarked in a project to create an automated system that will allow employees
to self-serve and order their lunch for eating at their work stations. Furthermore, employees have
complained that many of their favorite food items were not available by the time their lunch hour
arrived. An automated ordering system will track which foods that are most popular and help meet
the higher demand. At the same time, less food will be wasted due to poor sales.

Given one hour of lunch time, management has calculated that those employees spent 10 minutes
traveling to and from the canteen to their desks. Between 30-35 minutes were spent waiting in a
queue to choose and buy their food and only 10-15 minutes remaining to actually eat the food.

3|Page
Project Objectives

The project aims to create the following:

 The major Business Objective is to reduce canteen food wastage by a minimum

of 30% within 6 months following first release.
Scale: Value of food thrown away each month by examining the canteen
inventory Previous - 25% wasted
Must plan for: Less than 15%
 Next Objective is to reduce canteen operating costs by 15% within 12 months,
following initial release.
 Moreover, management also wants to 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.

4|Page
 1. Business Analysis Core Concept Model as per BABOK
Business Analysis Core Concept Model™ (BACCM™): defines a conceptual framework for
the business analysis profession.

Figure 1. Business Analysis Core Concept Model as per BABOK

For proposed canteen ordering system, detailed analysis pertain to below aspects will have
to be done.
 Need to come up with new system
 Change required in to satisfy the need
 Solution to be delivered in response of change and need
 Stakeholders impacted by the solution delivered in response of change and need
 Value to the stakeholder for the solution delivered
 Context of payments horizon in which the solution will be delivered
enhancing the value of the application to the stakeholders.

5|Page
 1.1. BACCM for Canteen ordering system
Need Problem or opportunity
 There are two canteens serving 1500 employees. Between 12:00 and 1:00PM the canteens
are overcrowded Employees waste too much time selecting their food, waiting on queue to
pay and traveling to and from the canteen and not enough time to eat, Canteen wastes too
much food for orders that are not made.

 Employees do not find most popular items when they arrive. Employees have requested
an automated system to order the food and have it delivered to their workstations.
Canteen Management needs real-time information to control cost.

Change
Transformation

 Company will alleviate overcrowding by delivering lunches to employees at their

workstations.

 Management will build a Canteen Ordering System that will allow employees to order
from daily menu for delivery to workstation.

 Canteen Administrator will receive reports of most popular dishes and a monthly report of
total sales leading to more efficient tracking and operations.

Context Influential Circumstances

 The proposed system will enable employees of Unilever to place their order online and
ensure timely delivery at their workstations.

 It will further help them to choose the lunch of their choice.

 This will reduce the wait time, increase productivity and reduce the manpower requirement
in Canteen.

Stakeholder Group or Individual impacted by the change

6|Page
 External Stakeholders: Sponsors, Suppliers, Unilever Employees, Management, Canteen
Manager, Chef, Menu Manager, Payroll Manager, Meal Deliverer.

 Internal Stakeholder: Development Manager, Project Manager, Implementation SME,

Developers, Testers, Operational Support, Business Analyst.

Value
Its worth, importance and usefulness to stakeholders within a context
 The proposed system will reduce canteen food wastage, increase average effective work
time and require lesser manpower in canteen.

Solution
Way of satisfying needs in a context

 Management will implement a web-based application that will allow employees with
ability to order and have the food delivered to workstation. Application will also track
most popular orders, streamline payment reducing operation costs.

Figure 2. BACCM Model for Canteen Ordering System

2. Requirement Classification Schema

7|Page
Requirements are described by following classification schema:

1. Business Requirements: These are statements of goals, objectives, and outcomes that
describe why a change has been initiated. They can apply to the whole of an
enterprise, a business area, or a specific initiative.

2. Stakeholder Requirements: It describe the needs of stakeholders that must be met to

achieve the business requirements. They may serve as a bridge between business and
solution requirements.

3. Solution Requirements: It describe the capabilities and qualities of a solution that

meets the stakeholder requirements. They provide the appropriate level of detail to
allow for the development and implementation of the solution. Solution requirements
can be divided into two sub-categories: Functional requirements & Non-functional
requirements or quality of service requirements

4. Transition Requirements: It describe the capabilities that the solution must have and
the conditions the solution must meet to facilitate transition from the current state to
the future state, but which are not needed once the change is complete

8|Page
 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.

Transition Requirements Stakeholder requirements

Proposed System will have the
entire process of accepting orders
online. The currency of the users
placing the order should be
conveniently handled.
At any point of time, if the
system collapses then handling
the lunch orders offline should be
thought through.
Employees: Users will be able to
place their orders online & can
expect delivery at their workstation.
The payment for their orders will be
deducted from their salary on
monthly basis.
Canteen Manager: The manager will
have to view the orders and plan and
deliver the lunch order to employees’
workstation. He/She will also have to
keep the menu

Solution requirements
The feature should be scalable.
The proposed system should be user
friendly, self-explanatory.

Figure 3. Requirement Classification Schema for Canteen

Ordering System

9|Page
Project Tasks
Task No. Project Tasks

1. Identifying stakeholders – Create a list of stakeholders

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)

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
5. 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

Draw wireframes or mock screens for any two of the features namely Menu Creation and
11. any other feature as deemed fit by the student.

10 | P a g e
 6. Task 1: Stakeholders List
Keep Satisfied Manage Closely Monitor Keep Informed
Sponsor Development Manager Supplier Developer
Canteen Manager Project Manager Menu Manager Tester
Unilever Employees Implementation SME Payroll Manager Operational Support
Management Chefs

Stakeholder Matrix

11 | P a g e
7. Task 2: Problem Statement
 There are two canteens serving 1500 employees. Between 12:00 and
1:00PM the canteens are overcrowded.
 Employees waste too much time selecting their food, waiting on
queue to pay, and traveling to and from the canteen and not
enough time to eat.
 Canteen wastes too much food for orders that are not made.
 Employees do not find most popular items when they arrive.
 Employees have requested an automated system to order the food
and have it delivered to their workstations.
 Canteen Management needs real-time information to control costs

8. Task 3: Objectives of the proposed system

 Reduce canteen food wastage by a minimum of 30% within 6
months following first release.
Scale: Value of food thrown away each month by examining the
canteen inventory
Previous - 25% wasted
Must plan for: Less than 15%
 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.

12 | P a g e
 9. Task 4: Current and Future Process for Canteen
Ordering System

CURRENT SYSTEM

Takes the food

Eat the food (15
Employee with limited
choices mins)

Walks to
Head back to
Canteen (10 Places Order
mins) Work

Waits in the
Food
Queue (30 - 35 WorkStation
mins) Token/Payment

Figure 5. Current State of the Canteen Ordering Process

 From the above flow, it’s clear that to have lunch for 15 mins, employees spend closely
around one hour

13 | P a g e
FUTURE STATE

Figure 6. Future State of the Canteen Ordering Process

14 | P a g e
 10. Task 5: Context Diagram for Scope of the Canteen
Ordering System.

Scope Model
Scope models define the nature of one or more limits or boundaries and place elements inside or
outside those boundaries.

15 | P a g e
11. Task 6: Main features of the proposed system
Below are the features of the system:
1. The employee shall open the web page of the Canteen Ordering System. He/she
shall be presented with an up-to-date menu for the day. It will have a list of all the
dishes available in the canteen for the day along with its prices.

2. The lunch order can be placed by employees latest by 11 am. After 11 am the
system shall not allow the users to place orders for lunch items so that the chefs
have sufficient time to cook the ordered dishes. There should be a Menu Manager
(a canteen employee) who shall create the menu and update the menu.

3. The users can select the lunch dishes they would like to eat and create an order.
They should be able to edit the items they want to order any time before checking
out. Once the order is confirmed and the user has checked out, they should NOT be
able to cancel or edit the order.

4. The canteen manager also known as order processor 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. This canteen
manager should also be able to request a delivery to the employees’
workstation.

5. 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.

6. If a customer does not like any food item or is not happy with the delivery
system by the canteen, they should be able to submit feedback.

7. There is no payment gateway for the same so the payment for dishes ordered
shall be deducted from employee’s salary. Hence, the employees need to enroll
for salary payment deduction. The payroll system will handle payroll deductions.
At the end of the month 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.

8. Management would like the following reports:

a. Which dishes are the most popular?
b. How many employees are using the system?
c. Satisfaction of the employees on using the system. This should be tracked
based on feedback submitted by the employees.
d. Sales for each day?
e. Total monthly earnings?

16 | P a g e
 f. Order forecasting.

9. Task 7: In-Scope and Out-of-Scope Requirements

In-Scope Requirements

In-Scope Requirements
Functional Requirements

Menu Selection
1) Employee will access Canteen Ordering System main page via URL
2) Employee should be able to view the day's menu without having to log in
3) To order, employee will have to log in with User selected ID and Password
If employee has not set up a profile, 'Initial Registration' sup-application will launch
4) (see Initial Registration section for detailed requirements)
Web page will be active until 11:00 AM - Message 'Ordering Time Expired' will
5) appear in Main Page - All customer logins will be blocked until menu is updated
System will perform security check against saved Password from initial registration
6) or updated Password
If Password is Forgotten, system will initialize 'Reset Password' Routine - (see Initial
7) Registration for detailed requirements)
8) When reaching main page, User will select items from Daily Menu

9) Menu will be separated into 'Snacks', 'Main Dishes', 'Drinks', 'Desserts'

10
) Menu will have Photograph, Description and Price for each menu
11
) Each item will have 'Like' icon next to the price
12 User will click on 'Like' Icon for each item selected and message 'Item in Tray' will
) appear

Check-out
13
) Main page will have Shopping Cart Icon on Upper right corner to Check-Out
14 Shopping Cart will display a list of all item selected by the user along with activated
) 'Like' icon
15 User will be able to click activated 'Like' icon to deactivate it and remove any item
) from tray
16
) Message 'Item Removed from Tray' will appear
17
) User will have the ability to 'Continue Shopping' or 'Confirm Order'

17 | P a g e
18 If 'Confirm Order' is pressed, message will appear that Customer will not be able to
) make changes or Cancel the order
19 Canteen will include applicable sales tax and display window with the list of items
) and Total and total amount due to customer

Payment
20
) Payment will immediately be requested to Payroll
21 If Payroll does not have a record of employee (i.e. employee left company,
) terminated, new employee) message will appear that Employee is not registered
22
) Payment will be sent to Canteen and deducted from employee paycheck

Initial Registration
23
) First-time Customers will need to create a profile in the system
24 Customer will enter Employee ID, First Name, Last Name, Work Phone, Cell Phone
) (optional), work-email
System will require customer create a unique password with standard rules - (1 or
25 more Capital letter, 1 or more lower case letters, 1 or more number [0-90] and 1
) non-alphanumeric character). Password should not be longer than 12 characters
If customer forgets the password, initial page should have 'Forgot Password' link
26 that will send an automated email to reset the password. Customer profile will be
) updated with new password

Canteen Manager Requirements

Canteen Manager will have write-access to Menu for daily update. Canteen
27 Manager will be able to add, update and delete items in the menu including
) photographs, description and price
28
) Canteen Manager will have 'Administrator' capabilities for updating webpage
29
) System will require Canteen Manager to enter Employee ID and unique password
30
) Only one Administrator can be logged into the system at one time.
31 If more than one person is Canteen Manager (administrator) the system will display
) message that another user is Administrator at this time.
32 System Administrator should be able to override and close out any account
) accidentally left open

System Requirements
33
) Application will be written in Java for easy maintenance
34 Canteen Manager will need a new server or standalone computer to track orders,
) data storage and create reports

18 | P a g e
 System will auto-create daily reports to track sales, how many employees use the
35 system, access satisfaction reports from customers and report on the most popular
) dishes

36 Server will monitor in real-time all orders and send these to stations where the
) Canteen Manager will be able to dispatch them to the Chefs
37
) Delivery Agent will receive orders from Canteen Manager as these are completed
37
) System will compile all daily information
38 System will auto-create monthly reports to include monthly earnings and order
) forecasting based on what dishes are the most popular

Out-of-Scope Requirements

Out of Scope Requirements

1) Breakfast items are not included in Canteen Ordering System
2) Refund to Customers in the event an order is never received
Electronic 'received' confirmation recording the time of receipt of
3) order
4) Automated email to customer once order is complete
5) Automated email to customer when order is received

6) Include suggestions of what can be done better in Feedback

Real-time notification of 'Order Status' in customer profile (in 'My
7) Orders' section)

8) Delivery to any other place besides work station

To streamline daily work, Canteen Manager should be able to
update menu for the entire week (i.e. upon closing of canteen on
9) Friday)
10) Mobile text message option when order is complete or received
Optional Inclusion of dietary preferences from Customer (i.e.
11) vegan, low-cal, gluten-free, etc.)
12) Optional Inclusion of food allergies
Inclusion of automated emails with the day's menu and
13) suggestions (depending on dietary preferences)
14) Web Page must be accessible via mobile or Tablet device

19 | P a g e
10. Task 8: Activity Diagram of the System

Figure 7. Activity Diagram for the Canteen Ordering System

20 | P a g e
11. Task 9: ER diagram of the system

Figure 8. ER Diagram for Canteen Ordering System

Page | 21
12. Task 10: Functional and Non-Functional Requirements

Functional Requirements
1. Website will take lunch orders from employees until 11:00AM.
2. Site must be user-friendly with reliable connectivity.
3. Site calculate bill with no cash transaction at the time of purchase.
4. Website will have connectivity and collect funds from Payroll.
5. Site will track all order and deliver them in real-time to Canteen Management.
6. Site will compile all orders and perform analytics for reporting most popular dishes, total
daily sales, total monthly sales and forecast future sales of dishes.
7. Website will have a Feedback page for customers.

Non-Functional Requirements
1. Menu will be easy to read and categorize food by type
2. Website should be able to serve all 1500 employees in the building
3. Website shall increase employee work-life quality

Page | 22
13. Task 11: Wireframes

 Initial Landing Page

 Initial Customer Registration

Page | 23
 Menu Selection Page

 Main Dish Selection (Sample)

Page | 24
Check-Out Page

Page | 25