CANTEEN ORDER SYSTEM

for

A SIMPLILEARN PROJECT FOR CBAP

SUBMITTED BY: NAVA TIMSINA
 Table of content

1. Company introduction
2. Background
3. Business Analysis core concept model
4. Requirement classification schema
5. Stakeholders RACI model
6. Root cause analysis
7. Current state process map
8. Future state process map
9. Out of scope context diagram
10. Knowledge areas under consideration for the project
11. In scope and out of scope requirement for the software
12. Entity relationship diagram
13. Mock screen
COMPANY INTRODUCTION:
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.

BACKGROUND:
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.
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. 
There is a huge rush in the canteen during lunch hours resulting in employees wasting a lot of time
waiting for tables to be vacant. 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.

BUSINESS ANALYSIS CORE CONCEPT MODEL (BACCM)

The conceptual framework of business analysis has been captured as outlined in the BABOK
guide.
 

Figure 1. Business Analysis Core Concept Model as per BABOK

The business analysis core concept model for the canteen order system is presented as under:

CORE CONCEPTS DEFINITION

Change  Switching from an existing manual ordering system to an online

canteen order system that will facilitate food delivery to the
employees in their workstation.

Need  Huge rush in canteen resulting in increase in queue time and decrease
in effective work time of employees.
 Employees not getting the food they prefer resulting in food
wastages.
 Increased production cost for the canteen management

Solution  Design and implement an IT project that enables the organization to

have its own online canteen order system which is integrated with the
payroll system and that facilitates the food delivery to the employees
on time.
 The existing system will also run parallelly until everyone will be
able/willing to use the new online system.
 Setup a delivery system so that the food is delivered on time and
without mix-up errors.

Stakeholders  Business Analyst

 Project Manager
 Domain SME-
 Implementation SME- IT department head
 Tester
 Operation SME
 End user- employees
 Chef/ canteen manager/delivery boy/ Menu manager
 Accounts department Head/ HR Head
 Inventory suppliers
 Regulators

Value  Increased effective worktime and increased productivity.

 Satisfied Employees
 Reduced Food wastages and reduced canteen operating cost.
 Efficient canteen management
 Record of employee eating habits.

Context  Huge number of employees i.e., 1500 working at the headquarter.

 Long waiting time in queue to get food.
 Attraction of employees toward online food ordering system
 No payment gateways.
 Access to smartphones/computers and access to internet/intranet
REQUIREMENT CLASSIFICATION SCHEMA

Business  Reduce Canteen food wastage by min 30% within 6 months of first
Requirements* release. Value of food thrown away each month must be reduced from
25% to 15%
 Reduce canteen operation cost by 15% within 12 months.
 Increase average effective work time by 30 minutes per employee per
day within 3 months.
 To reduce the manpower in the canteen.
 Improve Employees Satisfaction

Stakeholders  A system that would permit a canteen user to order meals online, and
Requirements food to be delivered to their work location at a specified time and date.
 Updated menu
 Able to customize the food order.
 A canteen order system that can be integrated with the payroll system.
 A system that does not allow ordering the food after 11 am
 A system wherein the canteen management can easily track the orders
for further processing it on time.
 Easy Report generation

Solution Functional Requirements

Requirements  User registration
 Viewing the menu
 Making online orders before 11 am
 Being able to make edits in the orders before checking out.
 Enrolment in salary payment deduction
 Arranging to-go boxes and other logistics for delivery of food.
 Easy User Interface / user friendly system
 Giving Feedback online
 The software should have three users with customized buttons as per
their specific requirements: for Employees to place the order and give
feedback, for Canteen Management staffs to process the order and get it
delivered and for IT department for maintenance of the software issues
and to generate the reports for submission to the management.
 Use of Java Platform

Non-Functional Requirements
 Ensure Internet Accessibility to all employees.
 Ensure Device Accessibility to all employees.
 Increased Server capacity and Increased bandwidth to ensure smooth
user experience.

Transition  Train the users to use the system.

Requirements  Motivate more users by offering food schemes.
 Provide training to the canteen staffs for smooth transition.
STAKEHOLDERS:
The different level of involvement of the stakeholders in the project has been described using RACI
model as under:

ROLE NAME ROLE

Business Analyst A, Z R,A
Project Manager B A
Domain SME- C C
Implementation SME- IT department head D, Y, X R
Tester E, P, Q R
Operation SME F, R R
Head Chef G, M C
Canteen manager H, N C
Delivery boy I, O, R C
Menu manager J, S C
Accounts department Head/ HR Head K C
Inventory suppliers L I
Regulators - I
Sponsor - A
Employees - I
*R=Responsible, A= Accountable, C= Consulted, I= Informed

THE ROOT CAUSE ANALYSIS:

The problem statement can be represented with the help of fishbone diagram. It gives a deeper
understanding of cause and effect of the problem.

People Process

increasing number wait in queue.

of employees Counter sale only
same lunch timing walk in food service

long queue. Decreased effective

work time/ food
wastages.
Only two canteens Running out of required items
Limited seating area

Long queue no food choice

Low sales
Environment Material

Fig : Fishbone Diagram (Ishikawa Diagram)

CURRENT STATE OF CANTEEN ORDER SYSTEM:
The present state of canteen order system has been shown in the process flow diagram as under:

Fig: As-Is Process Flow Diagram for the present canteen ordering system
FUTURE STATE PROCESS MAP:
Swimlane has been used to show the future state of the canteen order system

Fig: Future State Process Map

OUT OF SCOPE OF THE CANTEEN ORDER SYSTEM:
Context diagram has been used to show the out of scope of the online order system:

Fig: Out-of scope context diagram for the online order system
KNOWLEDGE AREAS USED:
Knowledge Areas Tasks

Business Analysis Planning and  Plan business Analysis Approach

Monitoring  Plan Stakeholders Engagement
 Plan business Analysis information
Management
Elicitation and collaboration  Prepare for Elicitation.
 Conduct Elicitation
 Confirm Elicitation
 Communicate Business Analysis Information
 Manage Stakeholder Collaboration
Requirement Life Cycle  Trace Requirements
Management  Maintain Requirements
 Prioritize Requirements
 Access Requirement changes
 Approve Requirements
Strategy Analysis  Analyze Current State
 Define Future State
 Access Risks
 Define Change Strategy

Requirements Analysis and  Specify and Model Requirements

Design Definition  Verify Requirements
 Validate Requirements
 Define Requirement Architecture
 Define Design Options
 Analyze Potential Value and Recommend
Solution
Solution Evaluation  Measure Solutiion Performance
 Analyze Performance Measures
 Access Solution Limitations
 Assess Enterprise Limitations
 Recommend Actions to Increase solution
value
IN-SCOPE AND OUT OF SCOPE REQUIREMENT FOR THE SOFTWARE

In-Scope Requirements
Functional Requirements
Menu Selection
1 Employee will access Canteen Ordering System main page via URL
2 The web page should have list of all the dishes available in the canteen for the day along with its prices.
3 To order, employee will have to log in with User selected ID and Password

4 If employee has not set up a profile, 'Initial Registration' sup-application will launch

5 Place order button in the web page will be active until 11:00AM - Message 'Ordering Time Expired'
will appear in Main Page - All customer logins will be blocked until menu is updated
6 System will perform security check against saved Password from initial registration or updated
Password
7 If Password is Forgotten, system will initialize 'Reset Password' Routine - (see Initial 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

1 Main page will have Shopping Cart Icon on Upper right corner to Check-Out

2 Shopping Cart will display a list of all item selected by the user along with activated 'Like' icon 

3 User will be able to click activated 'Like' icon to deactivate it and remove any item from tray

4 Message 'Item Removed from Tray' will appear

5 User will have the ability to 'Continue Shopping' or 'Confirm Order'

6 If 'Confirm Order' is pressed, message will appear that Customer will not be able to make changes or
Cancel the order
7 Canteen will include applicable sales tax and display window with the list of items and Total and total
amount due to customer

Initial Registration
1 First-time Customers will need to create a profile in the system

2 Customer will enter Employee ID, First Name, Last Name, Work Phone, Cell Phone (optional),
work-email
3 System will require customer create a unique password with standard rules - (1 or 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
4 If customer forgets the password, initial page should have 'Forgot Password' link that will send an
automated email to reset the password. Customer profile will be updated with new password

Canteen Manager Requirement

1 First-time Customers will need to create a profile in the system

2 Customer will enter Employee ID, First Name, Last Name, Work Phone, Cell Phone (optional),
work-email
3 System will require customer create a unique password with standard rules - (1 or 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
4 If customer forgets the password, initial page should have 'Forgot Password' link that will send an
automated email to reset the password. Customer profile will be updated with new password
5 First-time Customers will need to create a profile in the system

6 Customer will enter Employee ID, First Name, Last Name, Work Phone, Cell Phone (optional),
work-email

System Requirement

1 Application will be written in Java for easy maintenance

2 Canteen Manager will need a new server or standalone computer to track orders, data storage and
create reports
3 System will auto-create daily reports to track sales, how many employees use the system, access
satisfaction reports from customers and report on the most popular dishes
4 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
5 Delivery Agent will receive orders from Canteen Manager as these are completed

6 System will compile all daily information

7 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
1 Breakfast items are not included in Canteen Ordering System
2 Refund to Customers in the event an order is never received
3 Electronic 'received' confirmation recording the time of receipt of 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
7 Real-time notification of 'Order Status' in customer profile (in 'My Orders' section)
8 Delivery to any other place besides work station
9 To streamline daily work, Canteen Manager should be able to update menu for the entire week (i.e.
upon closing of canteen on Friday)
10 Mobile text message option when order is complete or received
11 Optional Inclusion of dietary preferences from Customer (i.e. vegan, low-cal, gluten-free, etc.)
12 Optional Inclusion of food allergies
13 Inclusion of automated emails with the day's menu and suggestions (depending on dietary
preferences)
14 Web Page must be accessible via mobile or Tablet device

ENTITY RELATIONSHIP DIAGRAM:

Fig: ER Diagram
MOCKUP SCREEN :
www.unilever.com/canteen

CANTEEN ORDER SYSTEM

USER ID

PASSWORD

Login Cancel login

Do you have an account? Sign up.

www.unilever.com/canteen

CANTEEN ORDER SYSTEM

User Registration

Full Name Cabin No

Employee ID Mobile

Floor No Work Phone

Passwort

Reconfirm Submit