ITECH 7415: Masters Project

Group 7
6/18/2021
Project Title: Mobile Application for La Mono
Restaurant

Assessment task 3: Project Write- Up

Submitted to:
Dr Belal Md Chowdhury
Dr Zakiullah Khan

Submitted by:

Dhiraj Kumar Thakur 30378004

Bikash KC 30380267
Pradeep Thapa 30377119
Sagar Parajuli 30381175
 Table of Contents
Abstract.................................................................................................................................................4
Acknowledgement................................................................................................................................5
Statement of Ethics...............................................................................................................................6
Chapter 1. Introduction........................................................................................................................7
1.1 Project Introduction..............................................................................................................7
1.2 Project Organization.............................................................................................................7
1.3 Client Introduction................................................................................................................7
1.4 Development Process of Project...........................................................................................7
1.5 Major Deliverables................................................................................................................8
1.6 Product Features...................................................................................................................8
1.7 Project Scope.........................................................................................................................9
Chapter 2. Problem Statement.............................................................................................................9
2.1 Problem Definition......................................................................................................................9
2.2 client Requirement...................................................................................................................10
2.3 Users/ Stakeholders..................................................................................................................10
2.4 User Stories...............................................................................................................................11
Chapter 3. Project Objectives.............................................................................................................12
3.1 Project Objectives.....................................................................................................................12
3.2 Project Aim................................................................................................................................13
Chapter 4: Related Academic Commercial Research.........................................................................14
4.1 Literature Review......................................................................................................................14
4.1.1 Literature Review by Dhiraj...............................................................................................14
4.1.2 Literature Review by Dhiraj...............................................................................................15
4.1.3 Literature Review by Bikash..............................................................................................15
4.1.4 Literature Review by Bikash..............................................................................................16
4.1.5 Literature review by Bikash...............................................................................................17
4.1.6 Literature review by Pradeep............................................................................................18
4.1.7 Literature review by Pradeep............................................................................................19
4.1.8 Literature review by Sagar.................................................................................................19
4.2 Relevant Theories and Frameworks.........................................................................................20
4.2.1 As – IS Model......................................................................................................................20
4.2.2 To -be Model......................................................................................................................22
4.2.3 Wireframing.......................................................................................................................24
4.2.4 Research Methodology...............................................................................................26
 4.3 Data Collection Methods....................................................................................................28
4.3.1 Data Collection and analysis..............................................................................................29
4.3.2 Dashboard..........................................................................................................................31
Chapter 5: Project Approach..............................................................................................................33
5.1 Agile Development Approach...................................................................................................33
5.2 Product Design Approach.........................................................................................................33
5.2.1 Product Design...................................................................................................................33
5.2.2 Design Heuristic Model Approach.....................................................................................36
5.2.3 Balance Scorecard Model..................................................................................................37
5.2.4 Flow Analysis......................................................................................................................38
5.2.5 Root Cause Analysis...........................................................................................................39
5.2.6 GAP Analysis......................................................................................................................41
Chapter 6: Discussion of Product........................................................................................................44
6.1 Description of the product developed......................................................................................44
6.2 UML Diagram............................................................................................................................45
6.2.1 Use Case Diagram..............................................................................................................45
6.2.2 Class Diagram.....................................................................................................................47
6.2.3 Activity Diagram.................................................................................................................48
6.2.4 Sequence Diagram.............................................................................................................50
6.2.5 BPMN Diagram...................................................................................................................51
6.3 Tools and Methodology Used...................................................................................................51
6.4 Testing.......................................................................................................................................53
6.5 Technical Document..................................................................................................................54
6.5.1 User Manual.......................................................................................................................54
6.5.2 System Features for Mobile Application...........................................................................61
6.5.3 Developer Manual.............................................................................................................63
6.6 Result and Findings...................................................................................................................66
6.6.1 Results and Finding by Dhiraj............................................................................................66
6.6.2 Results and Finding by Sagar.............................................................................................66
6.6.3 Results and Finding by Pradeep.........................................................................................66
Chapter 7: Summary, Limitation, and Recommendation...................................................................67
7.1 Summary...................................................................................................................................67
7.2 Limitation..................................................................................................................................67
7.3 Recommendation......................................................................................................................68
7.4 YouTube Links for Individual Reflection...................................................................................68
7.5 List of Tasks...............................................................................................................................69
References..........................................................................................................................................70

Table of Figures
FIGURE 1: AS-IS MODEL.............................................................................................................. 21
FIGURE 2: TO-BE MODEL OF MOBILE APPLICATION............................................................................23
FIGURE 3: WIREFRAMING MODEL OF MOBILE APPLICATION................................................................25
FIGURE 4: TREND OF SALES IN WEEKDAYS........................................................................................30
FIGURE 5: TREND OF SALES IN WEEKENDS.......................................................................................31
FIGURE 6: DASHBOARD OF ONE WEEK'S SALES OF LA MONO..............................................................32
FIGURE 7:FLOWCHART FROM CUSTOMER'S VIEW.............................................................................39
FIGURE 8: FISHBONE/ ISHIKAWA DIAGRAM..................................................................................... 41
FIGURE 9: GAP ANALYSIS: USER STORIES ARE FILLED OR NOT.............................................................42
FIGURE 10: PROJECT GAP ANALYSIS..............................................................................................43
FIGURE 11:USE CASE DIAGRAM....................................................................................................45
FIGURE 12: CLASS DIAGRAM........................................................................................................ 47
FIGURE 13: ACTIVITY DIAGRAM FOR ADMIN....................................................................................48
FIGURE 14:ACTIVITY DIAGRAM FOR USER.......................................................................................49
FIGURE 15: SEQUENCE DIAGRAM FOR ADMIN................................................................................. 50
FIGURE 16: SEQUENCE DIAGRAM FOR USER....................................................................................50
FIGURE 17:BPMN DIAGRAM....................................................................................................... 51
FIGURE 18: DATABASE DESIGN..................................................................................................... 53
FIGURE 19: ACCEPTING TESTING................................................................................................... 54
FIGURE 20:APP LOGIN PAGE........................................................................................................ 55
FIGURE 21:SELECT GOOGLE ACCOUNT............................................................................................56
FIGURE 22:APP MENU PAGE........................................................................................................57
FIGURE 23:TABLE RESERVATION....................................................................................................59
FIGURE 24:USER SIGN OUT PAGE................................................................................................. 60
FIGURE 25:LOGIN PAGE FOR ADMIN..............................................................................................61
FIGURE 26:DASHBOARD PAGE...................................................................................................... 61
FIGURE 27:TABLE BOOKING PAGE................................................................................................. 62
FIGURE 28:FOOD ORDERING LIST VIEW..........................................................................................62
FIGURE 29:START ADMIN APP IN LOCAL HOST.................................................................................63
FIGURE 30:DATABASE AUTHENTICATION.........................................................................................64
Abstract
After the evolution of the technical world and emerging of new technology and
technical applications, customer demands, and expectations are high and the
old tradition of performing business has been changed. It is a challenge for the
organization to integrate technology’s changes according to their business
model and make changes in their strategies to pursue the customers’ needs
and demands. In the field of hospitality, Restaurant sector we can integrate
latest technologies for the convince of the customer to provide better facilities.
In this master project, we intend to develop a mobile application for customer
and web application for business (admin) which should provide better facilities
and help to resolve the problems arises before having this system. We focused
on the booking system for customers, add to cart functionality which avoids
the queue system and save times. Moreover, customers can make a
reservation for dine-in services, and they can add food to their cart, and they
can pick their food from the store. We had used a mixed research design which
is a combination of both qualitative and quantitative research methods. We
studied and analyzed various research papers, case studies, and articles that
had been done in the past in a similar field. We have applied Agile
methodology for the development of this project. This method makes parallel
development with the client’s goals and customer needs. This project reflects
the use of the mobile application and its impacts upon the business and its
customers. As a team, we continuously focused on how the project can be
completed with the available resources and limited time by maintaining the
budgets and quality of the product.
Acknowledgement

This project has been completed for ITECH 7415 – Master Project at the
Melbourne Institute of Technology (MIT), Federation University, Sydney. It is
our honor to complete this project on time.

We are very thankful to the MIT family for providing us such a magnificent
course coordinator Dr. Belal Md Chowdhury, tutor Dr. Zakiullah Khan, Project
Supervisor Dr. Rachid Hamadi who gave us proper guidance to complete our
project. They gave us their recommendations and opinions throughout the
semester during the workshop as well as lecture time and supervisor meeting
time which helps us to do the growth and write-up part of our project. The
valuable advice and assistance provided by them assisted us to keep our
momentum and track the development of the report as per the plan. The
guidelines from tutors, lecturers, and supervisors added as back support to
achieve our targeted goal.
We would like to convey our special thanks to our client Mr. John Azar for
giving his precious time and support for the successful competition of our
project.
Finally, we would like to thank every team member including our colleagues
who inspired and support us during the Project.

Sincerely,
Dhiraj Kumar Thakur (Scrum master)
Pradeep Thapa (Team Member)
Bikash KC (Team Member)
Sagar Parajuli (Team Member)
Statement of Ethics
This is one of the essential portions of our project. We believe in the guarantee
of security and self-esteem of the research accused. We confirm that our
analysis does not affect human conduct and sentiments. We follow necessary
precautions while we visit a client or while we went to campus during this
pandemic. Partakers of this project are not forced to take part in the
questionnaire, and they are given full rights to leave the project if they want.
We completely retain a tactical gap from the biasness and misusing data of
crucial information in our research. Partakers are given full authority to add
their thoughts as per their knowledge. We make use of referencing/APA
framework in the incident of using the possibility of various authors’ articles.
Chapter 1. Introduction

1.1 Project Introduction

The title of our project is Mobile Application for La Mono Restaurant. This
project delivers an effective service to their customer by providing different
types of services to their customers. The system we built involves
characteristics like the online add to cart function and pick up order
function. It also includes a table reservation booking function. Our project is
intended to be built using the scrum methodology, hence executing an
Agile project management framework. We are four members, our task is
systematically distributed into parts in combination with the client’s
necessity and is aimed to be provided within a period of 3 sprints, where
each member week is of 3 weeks. The major aim of this project is to
provide a cost-effective and useful application that will boost the efficiency
of the company by offering better services to the customers. 

1.2 Project Organization

Client Name: John Azar

Client email: john@lamono.com.au
Contact Number: (02) 9822 2239

1.3 Client Introduction

The La Mono Pvt Ltd is a Sydney-based private company, renowned Lebanese
Cuisine which provides services with good Lebanese authentic foods to their
customers. The company provides highly qualified and experienced personnel
in different departments.

1.4 Development Process of Project

 Based on Agile methodology we have categorized our whole
development phases in the following steps:
 First, we gather all the requirements in the presence of the Product
Owner, product manager, business team, stakeholder, and developing
 teams. It assists everybody to express their needs and envision their
relevant requirements.
 After that, the developing team will then create user stories, product
roadmap, process, and architect design which is presented with the
guidance of the product owner.
 After the formation of user stories, the team develops a Product
Backlog. Product Backlog is a catalog of all new features, bug fixes, and
any changes to existing system features, and tasks.
 After the competition of Product backlog, the project is in developing
phases, where different team member will do their tasks like designing,
data analyzing and coding.
 Retrospective Testing and review are done to make sure the team is not
falling behind in the development phases.
 When all 3 sprints are done, the product is released and uploaded.

1.5 Major Deliverables

 At the end of Sprint 1, Home Page, Login function, Data Collections are
completed.
 At the end of Sprint 2, Booking function, Different articles analyzed,
system architecture, As Is framework model are completed.
 At the end of Sprint 3, Add to cart functionality, to-be model, different
framework, and related research has completed.
 At the end of Sprint 3, Final Integration is done.
 At the end of the project, we will launch the mobile application.

1.6 Product Features

 The mobile application is developed for a customer to see the menu, for
a reservation the table for dine-in, add to cart functionality.
 The web application is developed for the admin panel, where the admin
can manipulate the menu items with prices and content.
 From web application, admin can control over booking system.
 It helps to book the table for dine-in.
1.7 Project Scope
 The web application which we developed will be used for managing the
booking system.
 The web application which we designed will be used for managing the
online order to provide faster service.
 The mobile application will be used to make reserve the table for dine-
in.
 The mobile application will be used to add food in their cart to pick up
from which customers do not have to wait and stand in a queue.
 To develop this project, no one has spent any money since this is just for
educational purposes. So instead of financial, each member spends their
time.

Chapter 2. Problem Statement

2.1 Problem Definition

La Mono is one of the renowned Lebanese cuisine restaurants in Sydney. It has
4 branches all over Sydney. It is old and popular in town, so it has a strong base
of customers. This restaurant has a website, and they have a menu on their
website. Every time it is not feasible to open a website to check details. People
always prefer an application to a website because the application is specific.
While we visit the store first time and talked with the client then he told us his
problem what he is facing. According to him, they have a proper website with
all menus, but they do not have any mobile application. When they collect
information from the customer then customer expressed their thought that if
they have a proper mobile application with booking facilities, ordering
functionalities then they would love to use. So, our client told us that their
website is just showing information about menus, except that it does not
provide any functionalities.
When we asked the client in more details about his needs then he told us if
possible then make a mobile application for a restaurant which has all the
basic features like different pages with the details of menus. He added that he
would love it if we can add register functionalities for the customer so they can
use their ID and account in the application. He added again that he wants a
table reservation system in an application through which customers can book
or reserve the table for dine-in service which will skip the queue system. He
also wants an add-to-cart functionality so a customer can order from the
application. Then we told them about difficulties we may faces while
implementing the payment process then he said if not possible then they will
be happy with pick up functionalities.

2.2 client Requirement

Accumulating requirements for a project is the major part; this phase helps us
to define the project scope and objectives. To achieve the client’s
requirements, it is very important to recognize the client engagements which
include their objectives, vision, and ambition for what they are dreaming to
accomplish. A product that was designed with the requisite requirements
process provides us with additional benefits; products with well-written
specifications have a lower likelihood of problems. If we find our fundamental
requirements at beginning of the project, then it will help us to get success in
our goal. So, some of the client’s requirements are as follows:
 Login function for admin to do different functionality.
 Register function for the customer to become a verified member via
google id.
 Table reservation facility for the customer to reserve the table for dine-
in.
 Customer can make an order from the application, and they can pick it
up from the store.
 Admin can promote their special foods or promote their special events
through applications.
2.3 Users/ Stakeholders

Company La Mono Pvt Ltd

Admin/staff
Employees La mono owner or Manager
Customers Old or new Customers

Every user has their own credential to use their account in the mobile
application.
2.4 User Stories

Requirement Conditions of Satisfaction Acceptance

Criteria

US1: As a product manager, I Log in to the application High

want the login page so that I can with unique credentials.
use my credentials to log in to go
through the system securely.

US2: As a product manager, I The information of High

want registered customers’ data customer who has
in the system to be safe. registered should be only
accessible by
authorized(admin).
US3: As a product manager, I Log in as product manager, High
want customer information so then check the booked
that I can contact them. order with customer
contact details.
US4: As a Product manager, I Admin can update High
want to update the information necessary information from
dynamically. the database dashboard
according to the needs.
US5: As a customer, I want a View as customer, before High
details ingredient of each items buying customer want to
which I will buy. know about the ingredients
because few customers
have allergies.
US6: As a product manager, I The dashboard in admin High
want the database of sales of section, it will have reports
company so that I can analyze the of sales.
trend.
US7: As a customer, I want the list I want all similar items in High
of similar categories of products one category so it will save
in one section so that I can buy time to search any product.
and search easily.

US8: As a customer, I want to get It will be good if I can see Medium

image of products also so I can the image of product which
know how they look like before I am going to buy.
buying it.

US9: As a customer, I want good The interface of application High

user interface for the mobile must be user friendly so
application that customer can use the
application easily.
US10: As a customer, I want clear View as customer, before Medium
details of products so that I can buying customer can
review before buying them. review items more
precisely.
US11: As a customer, I want to Customer can add food to High
book some table or food to pick their cart and pay at the
up so that when I reach the store counter when they pick up
I do not have to stand in queue. the food.
US12: As a product manager, I Customer can register their High
allow customer to register from account and become a
their google id. member via google id.
US13: As a product manager, I Admin can post about High
want to promote special events special offer or special
or special foods on special events events.
then I can do via admin
credential.
US14: As a product manager, I Admin can remove the food High
can remove some items for item from list if it is out of
certain period. stock.

Chapter 3. Project Objectives

3.1 Project Objectives

 The primary goal of this project's development is to deliver good

services to clients and product owners in the world of hospitality.
 Makes the easy for customers to order food and table services.
 Allow customers to see the details about the whole menus and
ingredients from the mobile application.
 Allow customers to reserve the table from home to skip the queue.
  Satisfy the customer by saving their time not to stand in a queue.
 Allow admin to update the menus of the store.
 Allow admin to see the sales trend and helps to make the decision for
future.

3.2 Project Aim

The primary goal of this project's development is to deliver good services to

clients and product owners in the world of hospitality. Other main aims are to
understand the customer expectations and requirements. This project is
developed for both webs as well as mobile applications. The mobile application
is for customers and the web application is for admin/business. There are
varieties of functionalities in both applications. Like in web applications, the
admin can handle all the menu items where they can edit the list or prices.
They can add any items for special events. They can see the trending sales
scale from where they can make a backup for the future. They can also check
the booking orders.
Similarly, in mobile application customer can view the whole menus of the
restaurant and they can add to their cart whatever they want to buy, and later
they can pay on the counter when they will pick it up from the store.
Customers can reserve the tables for dine-in from their homes.
Chapter 4: Related Academic Commercial Research

4.1 Literature Review

4.1.1 Literature Review by Dhiraj
Problem

Service providers with capacity limitations, such as telecommunications

companies, must increase revenues to survive. Time-based pricing has been
created by hotels and airlines. Overbooking, pricing, early discounts, and
restricted early sales (Shugan, 1999). In the restaurant business, Pricing
becomes a tough job because demand is directly dependents on service
quality. Like, when the demand is at a peak then long waiting times often
occur, and consequently, service quality may diminish. The Restaurant
managers can uplift the service quality by advancing sales of products.

Despite the difficulties that restaurant pricing strategies face, restaurateurs

have devised a variety of pricing incentives to move demand from peak to non-
peak hours: Price-sensitive consumers can be drawn to off-peak hours through
discounted menus, early-bird specials, and happy hours.[ CITATION Sus04 \l 16393 ]

Solution

When used in a restaurant environment, mobile information services can help

build a more efficient and effective communication and marketing platform
between restaurants and their customers. As a result, such a channel has the
potential to raise the sales of the business.
First, by providing customers with the information they need through mobile
applications, restaurant managers can increase revenue, the incentive to draw
more customers on time. Simultaneously, the restaurant could impress some
customers’ appetites by displaying visual images to consider dining out when
they had not previously intended to do so.
Second, mobile application marketing can help restaurants better handle their
demand. Restaurant managers may submit electronic coupons to customers'
cell phones to increase traffic during off-peak hours.
4.1.2 Literature Review by Dhiraj
The Portuguese consumer foodservice industry is seeing an increase in
technology use because of substantial changes in customer behavior and
business dynamics brought about by the accurate demand for mobile devices.
As a result, the current work method involved establishing a business plan to
capitalize on an identified potential in the modern foodservice scene.
Therefore, this article is categorized into three sections and each section is
addressing different objectives.[ CITATION Sof16 \l 1033 ]
 External Environment - providing key external insights that support the
opportunity.
 Strategy Formulation – defining a strategic decision.
 Action Plan – deciding on a profit implementation strategy.
External Environment analysis “focuses on detecting and assessing trends and
occurrences that are outside the control of a particular firm” to examine the
external factors that influence organizational performance. In Strategy
Formulation, The Business Snapshot will be offered, briefly establishing the
5Ps3 that will actualize the opportunity.

Solution

In Action Plan, the "What" will be decided. First, define the segmentation and
positioning by identifying target customers on whom to focus marketing
efforts, namely Target Consumer and Target Foodservice, and describing Brand
Positioning. When businesses launch a mobile application in their business
then productivity will rise and it affects all departments positively.

4.1.3 Literature Review by Bikash

“Mobile app introduction and shareholder returns” by Mengyang Qin, Chun-
Hung (Hugo) Tang, Soocheong (Shawn) Jang, and Xinran Lehto
The article “Mobile app introduction and shareholder returns” by Mengyang
Qin, Chun-Hung (Hugo) Tang, Soocheong (Shawn) Jang, and Xinran Lehto is
insightful and informative because the authors have talked about how the
introduction of a mobile application for unmanaged businesses can increase
the popularity and sales of the business. The article also highlights the
importance of mobile applications in the hospitality and tourism sectors in
growing sales and developing a strategy for the business as well as it brings
value to the customers and improves operating efficiency. “Mobile travel sales
for leisure and unmanaged business travel grew from $26.14 billion in 2014 to
$52.08 billion in 2015 (Qin, Tang, Jang, & Lehto, 2017)”. 
Furthermore, the study of this article shows that the introduction of mobile
applications might increase the internal operating costs, but it can incorporate
long-term strategic implications that create value for shareholders. “Sales from
desktop devices slowed from $119 billion to $115.91 billion in 2015 (Qin et al.,
2017)”. Moreover, the articles also present some of the businesses such as
Orbitz, Expedia, etc. that generated more sales because of the use of the
mobile application. Orbitz reported that one-third of the booking are from
mobile devices and it is also similar to the case of Expedia. This article not only
highlights the importance of the mobile application to any business but also
reflects its benefits in many ways such as: improving operating efficiency,
creating revenue opportunities, reducing distribution cost, and fostering
customer loyalty and brand recognition.

4.1.4 Literature Review by Bikash

Return on Engagement Initiatives: A Study of a Business-to-Business Mobile
App
The article “Return on Engagement Initiatives: A Study of a Business-to-
Business Mobile App” by Manpreet Gill, Shrihari Sridhar, & Rajdeep Grewal
talks about different methods that can be used to connect the business and
customer, one of which is using the mobile application. The authors have
placed forward and implemented a method to evaluate and investigate a
business-to-business mobile application to access RoEI (Returns on
Engagement Initiatives). The outcomes of that methodology in different types
of a specification along with choosing the observable and unobservable
showed the increase in revenues. The research shows that data were taken
from a manufacturer company on its mobile application where the yearly sales
were more than $1 billion. The mobile application gathers the data from the
buyer company and after certain evaluation, it provides suggestions to the
buyer. 

In addition to this, the study of this article also shows that the buyer who
adopted this free mobile application has increased their sales and revenue and
the application also provided cost savings. This in return also motivated the
other buyers to use the free mobile application. “The app increased the
manufacturer's annual sales revenues by 19.11%–22.79%; even after
accounting for development costs, it resulted in positive RoEI(Gill, Sridhar, &
Grewal, 2017)”. This RoEI was higher when buyers created more projects using
the app, so customer participation intensity appears to underlie RoEI.

4.1.5 Literature review by Bikash

Mobile app-etite: Consumer attitudes towards and use of mobile technology
in the context of eating behaviour

The article “Mobile appetite: Consumer attitudes towards and use of mobile
technology in the context of eating behavior” has enlightened the readers
about the importance to business organization that how the consumers use
the mobile application to keep up their eating behavior like creating food item
lists, ordering food from a restaurant. “The study of this article shows that
segments of users and non-users of food-related technology and described
differences in their food-related app use and interest in food-related app
functionality (Doub, Levin, Heath, & LeVangie, 2015)”. As the mobile
application is everywhere, the business organization must understand
customer behavior towards the use of certain types of application such as
food-related application has become important for business. 
As per the article, participants were asked what types of mobile devices they
have, how many applications they have installed on their smartphones, and
whether they have any food-related applications or not. From the answers of
participants, it was found that 48% have android smartphones, 35% have
iPhones and the rest use other smartphones. Also, it was found that almost
73% of participants have a food-related application on their mobile devices.

4.1.6 Literature review by Pradeep

Online Table and Menu Booking System for Restaurants.
Introduction/problem: This article is are about the android mobile applications
where customers can book the menu and available tables at the desired time
and date. The article was done to fulfill the gap of desired outcomes. Earlier,
restaurant reservations were done by hand, which is becoming less common in
well-recognized restaurants. However, customers are increasingly moving into
the digital world of hotel bookings, and producers are thinking about switching
to a computerized billing system (Kale, S., Goti, P., & Roychaudhary, R. C). The
main motto of the article is to make clients directly linked to the customer so
that clients can identify the customer request about the booking, specific
number of tables in the section.
Solutions: The customer can register to the system; then the customer supplies
the appropriate credentials. Following that, the required table number is
chosen by the customers on the desired benefits. The menu is also reserved if
necessary. When making a menu reservation, the client must first pay half of
the total price and then confirm the reservation. This system helps the admin
to keep a record of the customer's information and cater to their needs. The
mobile applications help to customize all the table booking processes and let
the customer reserve the menu which helps the restaurant can manage the
reservations and food preparation.
Conclusion: According to the study's findings, if a customer wants to go to a
restaurant but there are no tables available, the client will have to wait a long
time. The user may use this app to find the best table for their needs based on
their location. Tables and menus, for example, can be reserved based on the
number of persons attending. In addition, the consumer may view interior
photographs straight from the app. Given the requirement for the proposed
project, which provides a variety of alternatives and allows customers to
reserve a table and menu without having to wait for an extended period via an
Android mobile application.

4.1.7 Literature review by Pradeep

User Acceptance of Mobile Apps for Restaurants: An Expanded and Extended
UTAUT-2
Introduction/problem: This article explains the use of restaurant mobile
applications in the real world. How the mobile applications are getting popular
in the world. This article study explores what is the real customer's activities
and behaviour when using restaurant mobile applications to address the
shortage of research on customer point of view. The author has done various
research and uses technology to identify the behaviour of customers while
using mobile applications.
Solutions: The article started with system design, measurement, and data
collection which are elaborated on first. The study is to identify the increasing
popularity of the use of smartphones among customers. The author has
identified the attitudes of customers during using the restaurant mobile
applications for search purpose which is expected to be shaky intermediaries
on their objectives to utilize those applications.
Conclusion: This research shows the behaviour of consumers while using the
mobile applications of the restaurant. A mobile application for researching
and/or making reservations at restaurants. a free smartphone application that
allows customers to identify, choose, and book the venue, and more precisely,
to identify the location (53 %), look for a menu (49 %), investigate for brand-
new restaurants (37 %), and make a request for pick-up or delivery %) (Palau-
Saumell, R., Forgas-Coll, S., Sánchez-García, J., & Robres, E. (2019)).

4.1.8 Literature review by Sagar

La Mono Website
La Mono Restaurant already have their own restaurant, however that is a static
website. User cannot interact or do anything within the app. According to
research more than 80% users access services from mobile application. This
makes huge loss for business who does not have mobile application. [ CITATION
Lam21 \l 1033 ]
4.2 Relevant Theories and Frameworks
4.2.1 As – IS Model
As-is process identifies and evaluates the business's current processes. The
biggest benefit of as-is process analysis is creating a solid foundation in an
organization’s processes. As-is analysis allows a business to assess the current
state of its processes and identify opportunities for improvement if necessary
("The Basics of Documenting and Analysing Your As-Is Process | Lucidchart
Blog", 2021). So, without the basic information, it is hard to assemble the
processes and that can lead to a tough time to get where the business wants to
be in terms of profit and revenue. 

There are several factors for implementing as-is analysis such as cost control,
improving the existing processes or creating new processes, client/customer
satisfaction, etc. Considering your present status helps associations archive,
track, and enhance their cycles for better execution, more noteworthy
productivity, and improved results. The as-is phase outlines any gaps or issues
with the existing business process and once we have mapped out those gaps or

issues, we can start to develop the to-be model which consists of the
improvements for solving the problems that the as-is model is facing.

Below is the simple as-is model of the La Mono restaurant website.

 Figure 1: As-Is Model

The above figure resembles the as-is model of the La mono restaurant website.
It is very simple and very few restaurant-related features are available on the
website. The customer visits the La Mono restaurant website and they explore
different types of menus such as takeaway menu items, dine-in menu items,
dessert and coffee items, and other food items. They can also view the prices
of those items from the website. There are no features available on the
website such as ordering the food items and booking the table. Also, the
restaurant cannot keep the contact details of their customer to send them
their promotions, giving information about the new food items as well as other
discounted food items on certain days. These problems are being faced by the
business owner regularly and hence many changes and improvements are
required to run the business smoothly to increase the sales as well as the
popularity of the business and these are identified through the as-is model.

4.2.2 To -be Model.

In simple terms, a to-be model is the changes that have been made in the
organization's current system or current business model. It can also be called
the future process model that an organization plans to carry out. The to-be
model is only needed if the organization demands any changes to the current
working model. 

To be
As is
Process model
model
The to-be model is the solution to the problems that the organization is facing
in its business environment. This model can be considered as the improved
version of the as-is model. If an organization is thinking that their current
system is out of date or doesn’t meet the present business demands and
needs, then they require a change in their business environment which can be
solved by developing a to-be model. After the to-be model has been
developed, it should be shown to stakeholders for their approvals, and they
can suggest some more improvement.
Below is a to-be model for our client La Mono Restaurant, which is an Android-
based operating system mobile application. A lot of changes have been made
to the current working model as per the client requirement for a better and
smoother operation of the restaurant business.
 Figure 2: To-be model of mobile application

If we compare the as-is model and to-be model of La mono restaurant, there
are significant changes. The previous model is just the working website where
customers visit a website and only explore the food items, but they cannot
order from the website either book a table in the restaurant. The to-be model
is a mobile application where most of the modern restaurant features have
been added. The customer or user after the successful login on the application
through their google credentials, can view different food items, order food
items, reserve table, and after the successful ordering and reserving, all those
details are stored on a database. The restaurant can use the contact details of
their customer to send them information about their newly added food items,
discounted food items only if the customer wants this information. There are
some features for admin and manager as well. The admin or manager can edit
food items as well as their price, they can add popular food items on the home
page of the application in an image slider function and they can also view the
booking details. All this information is also stored on the same database. There
will also be an admin dashboard where different visual analysis can be seen,
for example, in which days which food items were sold more, which items
were sold less, etc. Since it is a mobile application rather than a website, it is
also estimated that more people will have access to the restaurant and
ultimately the popularity and sales of the business will increase at good pace.
4.2.3 Wireframing
Before developing any mobile application, website, webpage, or anything,
their user interface needs to be designed which simply can be called
wireframing. A wireframing is just a simple outline of a mobile application that
consists of simple lines and shapes that resembles the working methodology of
the application. A wireframing is a model that is created or designed in the
early stages of the development process or before starting the coding phase of
the application.
Wireframes are usually created to illustrate clients, product managers,
stakeholders, and other team members to get them to know how the User
Interface (UI) will look like and how it might work. A wireframe does not
include every detail and all the features of the application, but it only shows
how the system might work. It is more like a non-functional model which
provides some hints and idea about how the product may look like. A
wireframing model does not have to be the same as the final product as the
wireframing model is a simple outline with different shapes that helps the
programmer how to structure the code to finalize the product.

Reasons to use Wireframe.

1. Incorporate feedback and encourage collaboration early: To make sure
every team member, client, graphics designers, the coding team, and
any other who are part of product development is on the same page, a
wireframing model helps everyone to be on the same stage of the work
and it also makes them easier in providing feedback.

2. Keep teams focused and on track:

As the product work moves forward, to keep a record of the progress of
the work and to use something as a reference, a wireframing model can
be used. It also can be used to keep the team focused and on right track.

3. Enhance agile development:

Since a wireframe is not a final product, it's very simple to get feedback
and clarify the design as the development team may require making any
changes. Also, it is always better to get any type of feedback before
much of the development work has been done.
 4. Save time and money:
A wireframe that is designed well can ensure to save time and cost as
the development team can have a clear vision of the final product and
with this, they can build error products avoiding possible bugs. Along
with this, the team does not have to make any changes that might affect
the functionality of the application. 

Figure 3: Wireframing model of Mobile application

The above figure is the wireframing of the La Mono mobile application. The
wireframing has been designed using the Miro wireframing tool which is an
online wireframing application. The tool is very easy to use and they offer
many different templates which make users design the wireframe with ease. In
the figure, we can see the home page, add to the cart page, login page, and
another page of the mobile application. The final application is a bit different
than shown here but this wireframing shows how the La Mono mobile
application might work.

4.2.4 Research Methodology

Whenever we start any research project, there comes the term “Research
Methodology”, “Research methods”, “Data collection” and many more.
Research methodology simply means how the research is carried out and how
the researcher designs a study method to make sure the results meet the
research aims and objectives. The research methodology provides an answer
to how the data are collected and how those data are analyzed.
There are three main different types of methodologies:
1. Quantitative Research
2. Qualitative Research 
3. Mixed-methods
Qualitative, quantitative, and mixed-methods are different types of research
methodologies, differentiated by whether they focus on words, numbers, or
both.
Quantitative research
Quantitative research is a technique that is more focused on conducting tests
using mathematical and numerical data collected through various methods and
sources. It is normally concerned with collecting and converting raw data into
numerical form so that different numerical analyses of those data can be
drawn. Any organization uses quantitative analysis to gauge certain numerical
values such as sales, profit, etc. The collected data should be valid and reliable
to accurately perform the research and draw any conclusion from the
research. So, it is very important to make sure the data are:
 Valid – Valid data are the logical data.
 Accurate – Accurate data means those data that are free from any kinds
of error.
 Timely – Timely data are those that are recorded in the present state, or
they can be called present data.
 Complete – Data is complete when it fulfils all the requirements to
perform the research.

The numerical data that we collected for this project for visualization and
better understanding the client’s business process, all those data are valid,
accurate, and complete, and meets the above-mentioned data requirements,
i.e., the those collected data are valid, accurate, timely and complete.
Qualitative Research
In simple terms, qualitative research can be defined as the type of research
method which is more focused on collecting data through conversational
method performed on various topics with a wide range of audience. Those
forms of data are not in numbers or mathematical form, unlike quantitative
research. “Qualitative research can be better used when we want to know
people’s thinking towards any circumstance or any events that might have
happened. So, this method helps a researcher understand what participants
think and why they think in a particular way ("What is Research- Definition,
Types, Methods & Examples", 2021)”. 
Some important types of qualitative research can include:
 One-to-one Interview: This includes certain questions asked to
participants for collecting data.
 Ethnographic Studies: This ethnographic study is a qualitative research
method in which an analyst or a researcher observes and connects with
participants of that study in their real-life environment.
 Text analysis: This method extracts useful and meaningful information
from the text.
 Case studies: This involves studying different articles and books related
to the research project.
For the qualitative research of this project, we were mainly focused on case
studies as well as textual analysis. The qualitative data that we collected were
mainly from the case studies that are related or similar to this project. Those
case studies helped us to better understand the project terms and
requirements as well as showed some ways to solve the problems.
Mixed-method
The mixed-method could be a technique that's used when both qualitative and
quantitative methods are best fitted to any research. “This method is taken
into account as the best method because researchers have the liberty to use
any of the methods, techniques and procedures typically related to
quantitative or qualitative research ("Alzheimer Europe - Research -
Understanding dementia research - types of research - The four main
approaches", 2021)”.
 Since every research method has its limitations, we used this mixed-method
because we wanted to cut back as many limitations as we can for our research,
and also we've got best to use the qualities of both qualitative and quantitative
methods wherever possible. Both qualitative and quantitative research may be
well presented in mixed methods. we've quantitative data directly from the
client and plenty of literature reviews findings as qualitative data.

4.3 Data Collection Methods

“The decision of which data collection strategy to utilize relies upon your
overall research aims and targets, just as items of common sense and asset
requirements ("What Is Research Methodology? Simple Definition (With
Examples) - Grad Coach", 2021)”. The data collection process should be
considered a very important aspect of any research project because the result
of the research is so much dependent on those data and their analysis.
There are many different methods and ways of data collection. Below are
some of the main and important data collection methods:
 Interviews
 Online or Physical surveys
 Observations
 Documents and records
 Case studies
For our research purpose, we have collected data using document and records
methods. For this, we ask the client for the necessary data and they gave us
the data from their records. This method can be considered as easy and less
time-consuming as the data are already present in digital form, and we just
have to record them. This process also makes it easier in the analysis and
visualization part as data are already in digital form and we do not have to
organize the data which saves more time. Also, the visualization and analysis
part can be more accurate as the data are obtained directly from the client
which ultimately helps the client's business model from those accurate analysis
outcomes. Other than this, some textual data through different case studies
also have been useful for us as those case studies helped to better understand
the project problems and their solutions.
4.3.1 Data Collection and analysis
We have not done any specific types of the survey with any customers. When
we had a second meeting with clients then we ask with our clients about the
business trend. Which time of day is pick hour for business?
 Which items are most sale in a day?
 Which is busiest day? i.e., weekdays or weekends.
 Which is most busy either Takeaway or Dine in in weekdays?
 Which is most busy either Takeaway or Dine in in Weekends?
 Which items are most sale in weekends? etc.

Then, the client answered our queries and he also provided one-week sales
raw data to us to do data analysis.
I have used Microsoft Power BI tools to analyze the data and find out some
trends in the business. The main reason behind doing analysis and finding out
trends is that we have planned to include a dashboard in our web application
also which is accessed by Admin.
Here is some analyzed trend.

Figure 4: Trend of sales in weekdays

In the above diagram, I have analyzed the data of weekdays during the
daytime and nighttime in both takeaway and dine-in. we can see that during
the daytime the takeaway sales are high especially chicken meal (Family pack)
is high. But during nighttime rather than chicken the salad and sauce have sold
much.

Figure 5: Trend of sales in Weekends

In the above diagram, I have analyzed the data of Friday during the daytime
and nighttime in both takeaway and dine-in. we can see that during daytime
the platters and Tabouli have gone much than any other items and the least
sale item is the garlic plate. But during nighttime, the platters have been sold
out more than any items. It seems that people love to eat in the restaurant at
nighttime when the weekend starts.

4.3.2 Dashboard
It is a graphical representation of information of a business’s records, metrics,
performance indicators, data to analyze the status of the business. [ CITATION
Kli19 \l 16393 ]
 Figure 6: Dashboard of one week's sales of La Mono

After analyzing few trends, I have created one dashboard using Microsoft
power BI software. I have used different types of diagrams here; we can see
different days and night sales are showing us the versatility of sales during
weekdays and weekends. It will help the client to see the sales trending and
make enough back up for their business. For example, like above we saw that
on weekends platters have been sold too much, so they can make back up for
platters ingredients on Wednesday or Thursday.
Chapter 5: Project Approach

5.1 Agile Development Approach

We followed the Agile Developmental methodology for developing this
system. We work on the project for 12 weeks (about 3 months) which includes
3 sprint works. During this phase, we continuously do the analysis, coding, and
testing part. According to agile development, we can include the change in any
phase of product development. Changes are not a good thing to perform
however as we are developing a complex system using new tools for us, it was
quite difficult for us to adapt to the modern technology we used. (Wrike, 2020)
The formed end for our admin panel is build using React JS. Which is a popular
library of build interactive front end of a web application. It is a lightweight
library that is easy to learn and use. We hosted our admin panel on a free
hosting site called Netlify and it can be accessed
at https://lamono.netlify.app/login. 
Similarly, we used the java programming language for the android application.
All the coding for the app was done using Android Studio. Our agile
development approach was simple. We build the android app first, then the
database and the admin page.

5.2 Product Design Approach

5.2.1 Product Design
Product design is the holistic approach when it comes to creating products that
are Mobile applications for the La Mono restaurant by combining the real
customers with the restaurant's respective goals. Product design is the process
of defining the problem, identifying the market opportunity, developing the
alternatives of the solution, validating the alternatives of the solution with real
users.
Product design is the method through which designers combine customer
demands with commercial objectives to assist businesses in creating
consistently effective products. Product designers strive to experience for
users in the services they create for their customers, as well as support their
brands by ensuring that their products are long-lasting and meet long-term
business goals (Babich, N. (2018)).
Initially, when thinking about the mobile app development process, designers
should understand the company goals and objectives and should answer some
important questions they are:
1. What is the problem with the current situation?
2. What are the problems that are going to be solved?
3. Who and how will get benefit from the new product?
Moreover, finding out the answer to all these questions helps the developer to
develop the product for a better user experience and for the company to
achieve its goals.
After having the design structure, it's time to follow the certain product design
process to stay on the right path and focused on the expected outcomes. For
the mobile application development process, the project has different steps:
1. Define strategy:
When all solution is determined then the first step is to make the
strategy to fulfill it. It all involves careful planning. It determines your
destiny and the road you will take to get there.
The product strategy is the collection of the vision and achievable goals
which go together and leads the team towards the desired outcomes.
After having a clear vision, it was time for developing the strategy
through evolving ideas into a successful mobile application for the La
Mono restaurant. In this step, the developer establishes the app's
platform, goals and objectives, and users. In addition to that various
strategies are done like brainstorming, designing framework, paper-
based wireframe, flowchart, and many more. Spending time on vision
and strategy development is a worthwhile choice since it sets the
framework for a product's success.

2. Analysis and planning:

In the second stage, the concept of creating mobile applications will take
shape and become a tangible product. Identifying use cases and
establishing functional requirements are the first steps in the analysis
process. Following the identification of our app's needs, the following
stage is to create a product road map.
 A product roadmap is a single source of truth that details the aim,
objective, priority, and successes of a product across time. It is a strategy
for uniting the organization around the goals of a product or project, as
well as how those goals will be fulfilled. Product backlog refers to new
features, upgrades to existing systems, bug fixes, infrastructure
upgrades, and other services that a team may deliver to achieve a set
goal. It comes in a variety of formats, with user tales being the most
common. A User Story is a little (indeed, the tiniest) piece of work that
represents one value to an end-user and can be delivered during the
sprint (Stormotion).

3. User interface/ User experience (UI/UX) Design:

The main objective of a mobile application design is to deliver a simple,
clean, and effortless user experience. The successful application is
determined by how the users are benefited from the features and
attributes of the mobile application. The UI/UX design is to create a
proper and excellent creative and interactive app, user-friendly, intuitive
for a better user experience.
Mobile app design is started by developing wireframes, they are digital
sketches. Wireframes are more concerned about attractiveness and
usability than with color combinations and designs. Wireframes are a
simple and affordable way to build application interfaces and develop
throughout them the developing review. You must include the
platform's unique style when designing the storyboard and user
experience.

4. Application development:
The planning step of the android app development strategy is still quite
important. Before you begin any construction work, you must:
 Establish the technological framework
 Choose a software system and implement it.
 Mobile app Front-end, Agile methodology and the Back
end/server technology are the three main components of a typical
mobile application project.

5. Testing:
Product testing (Quality assurance) testing is an important part of the
android app development phase since it ensures that the app is reliable,
 functional, and secure. You must first build test cases that cover all
elements of app testing to assure thorough QA testing of your app. Unit
testing and acceptance testing are done for the project.

5.2.2 Design Heuristic Model Approach

This approach supports recognizing where the User interface (UI) is lacking
behind of user-friendly understanding. [ CITATION Jor \l 1033 ]
There are so many points which supports these principles and some of them
are described below:
 System structure should be lucidity.
A user interface should give the user the feeling that they are in the
correct context, and they should know clearly that where are they right
now and after that where they will move forward. If the user will get
confused and lost during using the application, then the application
won't be considered a good one.

 Feedback should be Rapid.

If a user is using any applications and there is a chatbot or technical
supports and they ask something, but they will not receive their answer
rapidly then it will not be valuable for the user. So, feedback should be
always fast and correct.

 The consciousness of an errors

Nobody has perfection or complete knowledge of everything. If
someone is developing an application with his full skills but some other
users will find some glitches, or they will add some new suggestion so
they will always be ready to face it.

 Flexibility of use
An application is always known as good when everyone can use it
without any training or guidance from anyone. It should be simple and
user-friendly. If someone needs someone’s guidance to use the mobile
application, then it should not be considered a good one.

 Selection of Design and Information

The selection of content and design in any application is one of the
major tasks for developers or designers because using a different color
 or using too much information is not good because it may create
confusion among users. So, we should be always careful about our
content.

 Accessibility of Information
While using a mobile application user should not need to remember the
information of the application. The options should be given clearly so
that customers can fully depend on the application. [ CITATION Jor \l 1033 ]

5.2.3 Balance Scorecard Model

Balance scorecard model is performance indicator which is used to
enhance, detect, and govern the different operations of a company.
[ CITATION Tar20 \l 1033 ]

It is executive tools rather than quantity tool because of its use by

business's staffs.

Financial

Business
Customer BSC Process

Learning &
Growth

 Learning and Growth

 It analyzes how much training has been provided to an employee
and not only the training provided it also analyze how much
employees are using it and increasing productivity.

 Business Process
It analyzes how the products or goods are manufactured in an
organization, and it also deals with any gap which an organization
may face to make good products.

 Customer
Customer is always a key asset for any businesses. So, we cannot
ignore the customer, so we need to make them happy. So,
customer feedback is also necessary.

 Financial Data
It includes like sales, expenditures, and income of any
organization. It deals with different data related to finances.

Advantages of Balance Scorecard

 It assists departments with crucial vision into their company's services
and quality.
 It facilitates the organization to gather all necessary information into a
single report.
 It backs the business to diminish their inadequacies.

5.2.4 Flow Analysis

The system is mapped out on a chart and given a title. Each step of a process's
material is gathered and recorded on something like a card. The different
process elements are in the proper sequence. Other persons participating in
the project study and analyze the flowchart. Recommendations for improving
or addressing problems are made. Individual process stages or flow of
information within just a system or process are displayed.
It explains the boundaries of the process and system to be demonstrated are
defined:
• Where or how does the process start?
 • Where and how does it end?

Flow chart for customer

Figure 7:Flowchart from Customer's View

This figure shows how the customer can login through the mobile applications
and can do the bookings and order the food items.

5.2.5 Root Cause Analysis

Root cause analysis is the practice of identifying the root causes of issues to
generate effective solutions (RCA). The most common problem-solving
approach is root cause analysis. One of the most essential techniques for
determining the organization's fundamental problem is root cause analysis. To
create and execute the most complete protection, root cause analysis is a way
of discovering the underlying causes of an event (Rooney, J. J., & Heuvel, L. N.
V. (2004)). It is most frequently used when something goes wrong, although it
might also be used when things go well. Internally, a company's problem-
solving and risk-assessment processes. The three basic phases of the root
cause technique are as follows:

1. What is the problem?

It defines the issue or cause which directly or indirectly affects the
overall goals and objectives of the restaurant. The main problem of the
restaurant was the loss of sales and profit. Usually, La Mono is a popular
restaurant and people have to wait for a long time for tables and
services which impact profit.
2. Why did it happen?
After identifying the problem, it is needed to break down the real cause
into the visual map. It helps find out the reasons behind the problem.
For La Mono restaurant lack of a proper system for table booking,
improper allocation of resources, waste of food, frequent complaint
form customer was identified which was main causes for the creation of
the problem.
3. What will be done to solve it?
It was necessary to solve the problems through the best alternatives.
The development of android mobile applications was the best solution
for the restaurant to solve all the problems. These effective solutions can
bring a vast change in the restaurant as it is expected to increase sales
and profit in the coming future.

The root cause analysis was necessary to find out the problem the current
system was having. RCA is the effective way for identifying the problem,
determining the effective solutions, prevention of repetition of problems which
directly saves time, resources, and money (Peerally, M. F., Carr, S., Waring, J.,
& Dixon-Woods, M. (2017)). Root cause analysis is done by the
fishbone/Ishikawa diagram. The root cause analysis was necessary to find out
the problem the current system was having. RCA is the effective way for
identifying the problem, determining the effective solutions, prevention of
repetition of problems which directly saves time, resources, and money
(Peerally, M. F., Carr, S., Waring, J., & Dixon-Woods, M. (2017)).

For the problem analysis, the fishbone/Ishikawa diagram is used. The fishbone
diagram, also known as the Ishikawa diagram, is a cause-and-effect visual
representation that supports management to determine the causes of
problems, inconsistencies, mistakes, and errors. The graphic resembles the
skeletal of a fish, with both the problems at the top and the causes of the
problem flowing through into spines.

Figure 8: Fishbone/ Ishikawa Diagram

A Fishbone diagram is a visible way of looking into the problem and its effect. It
shows the cause-and-effect relationship of the events occurring in the
company. The figure, clearly shows that the main problems like loss of sales
and overcrowd are because of different elements. In proper managements of
bookings, overcrowded, a frequent complaint from a customer, waste of food,
information’s delay was the major problems of the current system. Improper
management of table booking, disruption of delivery, overcrowd, loss of
regular customer was the main cause for the loss of the restaurant. The old
system does not have any pre-booking facility and food ordering system which
was making restaurants in a high gloss. Overall, the best way to solve these
issues is through mobile applications where customer can easily order the food
as they like and books the tables on different date and time as they wish.
5.2.6 GAP Analysis
The comparative analysis of the current condition with the projected state is
known as a gap analysis. A gap analysis analyses the performance of a
company's data management or software packages to evaluate if business
procedures are being met, but if not then, what steps should be taken to
ensure that they are. (Alagheband, M. R., Mashatan, A., & Zihayat, M. (2020)).
Gap Analysis assists the company in concentrating its efforts and making well-
informed decisions. Furthermore, by considering its major problems, a
corporation may distribute finite resources to create effective budgets.
Objectives are classed as high, medium, or low; the categorization somehow
does not necessarily imply that one priority is more important than another in
terms of attention or funds, but it might aid where resources are insufficient.
Furthermore, the gap analysis is explained by the table below:

Figure 9: GAP Analysis: User stories are filled or not

The gap analysis helps to find out whether user stories are fulfilled or not. The
gap analysis helps to find out what activities are accomplished, and which are
not over a period. Form the application customer can log in through Gmail id
but cannot use the app as a guest, though this is the gap of the project. In
addition to that delivery system and online system which was expected to be
achieved in the final product is not accomplished which is the gap for the app
development. The customer can order the food items by adding them to its
cart and book the tables on their date and time. Likewise, the admin can view
and edit the food items by looking at the stock. Moreover, the admin can log
out and log in to the admin panel.

Figure 10: Project GAP Analysis

This figure explains the whole gap analysis and the strategy followed to
minimize the gap. Initially, when the problem was identified by root cause
analysis the main solution is to develop a mobile application. There was
various gap stating the project like there was no proper mobile applications
model to start, specific time and no allocated budget, limited resources, and
knowledge in specific are, lack of structural process, in proper analysis of data
structure and market segments. To reduce the gap various initiatives and
strategy are done like dividing work in each team members based on
knowledge and skills, a system design that is wireframe, estimate time and
allocates limited resources to execute the strategies, doing review time to time
with a client, supervisor, and client to make that the all the steps are on right
track. All these steps and guidelines help to achieve the final product that is an
android mobile application for the La Mono restaurant.
Chapter 6: Discussion of Product
6.1 Description of the product developed.
In this project, we develop 2 products a web app and an android application.
The customers can download the Android app from the play store. They can
use their google account to login into the app. From the app, they can check
the menu for takeaway and can order the food they love. All the data will be
store in our firebase database and can be visible into the admin pan which is
our web app. The customer can also book a table from 2 weeks from the
current date. We have a restriction for the table book which allows users to
book a table below 10. They cannot book more than 10 people at one time. 
All the data shown in the application are dynamic. The app fetches all the data
from the database which can easily be changed by the administrator. 
We also have developed a website for our admin where he can monitor and
manage the system. The admin side is developed using React JavaScript library
which is developed by face and is extremely popular in terms of UI
applications. The admin can add or remove new products and check the
booking status. He can also check the ordering status.
In conclusion, we have 3 systems connecting the admin side, Firebase
database, and android application. All these 3 systems work together to share
information.
6.2 UML Diagram
6.2.1 Use Case Diagram

Figure 11:Use Case Diagram

Use case diagram are UML diagram, which helps to shows how our actors will
interact with the system. In our system the user and admin will have a very
interactive relation as all the operation perform by the user will be monitor by
the admin. The user can order food, log in into the account and do table
reservation. The admin on the other hand will view and manage those things.
Also, the admin is responsible for managing the content in the app and
manage the product by changing, editing, or adding products according to the
requirements.[ CITATION UML21 \l 1033 ]
Use Cases:
Use Case 1: Signup
Primary Actor: Customer
Objective: To sign into the application.
Pre-condition: Need a Google Account.
Post Condition: Can access the app content.
Basic Flow: User enter their details and have access to the app content.
Use Case 2: View Items
Primary Actor: Customer
Objective: To view the menu of the application.
Pre-condition: Must be logged in.
Post Condition: Can check the details of the menu.
Basic Flow: User view the menu and have access to the app content.
Use Case 3: Add to Cart
Primary Actor: Customer
Objective: To add item into the cart for takeaway.
Pre-condition: Need to access the menu items.
Post Condition: Can add the food item to the cart.
Basic Flow: User can select the food item they like and add them to the cart.
Use Case 4: Signup
Primary Actor: Customer
Objective: Conform Ordering
Pre-condition: Need to add some food item into the cart.
Post Condition: Can order the food item for pickup.
Basic Flow: User view their crat item and conform the food for pick up.
Use Case 5: Manage Products
Primary Actor: Admin
Objective: Add or modify the product in the admin page.
Pre-condition: Need to log in into the web app.
Post Condition: Can modify the menu.
Basic Flow: Admin can add new product or delete or modify the food items.

6.2.2 Class Diagram

Figure 12: Class Diagram

The above figure shows our class diagram which shows how the application
will work. The main starting class once after the app is run is the menu class.
The user can select the food item and do the ordering. The user can also call
the BOOKING class for table booking. The TABLEBOOKING class connect with
our database and the admin can view it.
6.2.3 Activity Diagram

Figure 13: Activity Diagram for Admin

 Figure 14:Activity Diagram for User

The diagram above shows the activity diagram for our customers and admin.
The user can log inn to the application and either select food item for ordering
or Table booing. Once the desired option is selected the user can quite the
application.
Similarly, the Admin can also log in into the system and check multiple options.
The admin can either add new products, manage table booking and manage
the food ordering.
6.2.4 Sequence Diagram

Figure 15: Sequence Diagram for Admin

Figure 16: Sequence Diagram for User

The sequence diagram for the admin and user shows the follow of the system
in a sequence order. The user can navigate to call the order function or table
booking function. The system then calls the database function to conform the
request of the user. The admin can login into the panel to manage the system
by calling validOrder() function and validReservation() function.
6.2.5 BPMN Diagram

Figure 17:BPMN Diagram

Business process diagram are flowchart which shows the business model for
the project. It shows highlights the flows of the content in the system so that
the business can get an overview of the operation occurring. In our system the
customer will first connect with our database and then the admin will manage
all the process requested by the user.

6.3 Tools and Methodology Used

Google Firebase

We will be using Google fire base as our back end. They provide services like
Authentication, Database, Hosting, Analytics. Push messages etc. Right now,
we are using the free version of Firebase. One of the main reasons for using
firebase is that the data are very secure and amazingly fast. We do not need to
refresh the application to update new data. Everything is supper fast with
firebase.[CITATION htt21 \l 1033 ]
Java

As this is an android application, we will be using java programming language.

Java is the most widely used language for android Apps. In this project we used
Java and XML for the development of the app. We followed Model-View-
Controller pattern while coding.

Android Studio

Android studio will be our IDE for all coding purpose. All the testings can be
done directly in it. Developed by google, android studio is widely used ID for
android app development and is the official IDE also. This application was our
main tool which was used for the coding as well as testing purposes.

React JS.

React is a front-end JavaScript library which are used to build interactive

application. It is used in developing complex system which have multiple
functionalities. In work based on different component which can work
independently, and those components can be reused, so that the number of
lines of code is reduced drastically. React JS was used to build our web admin
page.[ CITATION Spr20 \l 1033 ]

Git Hub

GitHub is a code management platform for version control. All the major
changes of the code will be available on GitHub at
https://github.com/sagarparajuli02. This will help us to manage and control of
the code anytime. And we can easily track the development of the project.
Database Design

Figure 18: Database Design

The diagram above shows the database structure for our system. It is a NO SQL
database so instead of tables it has categories. We have distinct categories for
each functionality like booking, products, cart, and orders. We check the
endpoint requested by the users and the database provides the requires API
endpoint accordingly.

6.4 Testing
We used 2 methodologies of Software testing for the development of our
application which are:

 Acceptance Testing
Acceptance testing was done on the admin side as we are developing a
web site. In acceptance testing we check how the application runs in
different systems. In case for our web app, it should be compatible with
web browsers. So, we run it in different browsers like Firefox, edge,
opera and chrome and mobile phones. The application will run in all the
latest web browsers in a normal way. We did not find any difference in
the run time or user compatibility. We used an online website named.
https://www.browserstack.com/ where we check the compatibility in
different devices, browsers, and OS.[ CITATION Sof20 \l 1033 ]
 Figure 19: Accepting Testing

 Unit Testing
Unit testing is a java programming framework for unit testing. It provides
features like: Fixtures, Test Suites, Junit Class and Test Runners.
For Unit testing we used Junit framework. This testing as done to check
the execution of specific function and block of code runs accordingly or
not. We performed some unit testing to check the reliability of the code
functionality and performance.[ CITATION 99G20 \l 1033 ]

6.5 Technical Document

6.5.1 User Manual
The system will be required internet connection for their proper functionality.
User should allow internet permission before using the system. They should
also need to provide cookies for session handling and data management.
System Features for Mobile application:
Login

The user will need an android phone and can download the app. Then they will
need a google account to login into the application.
https://play.google.com/store/apps/details?id=com.la.mono
Figure 20:App Login Page
 Figure 21:Select Google Account

Successful Login

On successful Login the user can see the homepage of all the application
where he can view all the items.
View Food items

Figure 22:App Menu Page

Once The User is logged, they can start using the app. You can find different
variety of category for different food items.
Order Food Item

Once you add the desired food item into your cart you can order the food
items. You can see the list of the food and then click the conform order button
to finalize the order.
Book Table

Figure 23:Table Reservation

Go to the booking section then you can select the date, time, and number of
guests. Note that the number of guests cannot be above 10. Then click the
conform booking button for finalizing the conformation.
Sign Out

Figure 24:User Sign Out Page

In the account section you can see your profile page with your image. Click the
sign out button to log off the app. This is not necessary in most of the case. You
can continue using your account, as all the data and information are secure.
6.5.2 System Features for Mobile Application

Login and sign out.

Figure 25:Login Page for Admin

The admin will have unique email and password which is provide by the
developer. Use that credential for logging.

Figure 26:Dashboard Page

Once Logged, the user can view the dashboard page showing the booking and
ordering details. You can navigate to different section according to your
requirement.
Check Table Booking

Figure 27:Table Booking Page

Go to the Booking section where you can see the details regarding all the
booking done by the customers from the app.
Check Food Ordering

Figure 28:Food Ordering List View

In the order page you can see the orders done by the customers.
6.5.3 Developer Manual
Web Admin Panel
The code for the admin side id done in react JS which can be run using the
command NPM START. Developer will need node JS running in their system
which will provides the development testing server.

Figure 29:Start Admin App in Local Host

Android Application
We can import the project in android studio. We will be required latest version
of android studio. For connecting with our database, we will need a json file
containing the credentials of authentication. Also, we will need an android app
or emulator to run the application.
 Figure 30:Database Authentication

Testing Template
Models Test Test Test Precondi Test Excepte Actual Test
Case Type Scenario tion Step d Result Result Result
ID s
User login T1 Function Verify App Enter The user The user Successful
ality that the should The must be can login
user be details able to into the
input the downloa into the be app.
correct d in their text box. logged
Gmail phone. into the
credenti applicati
als. on.

Admin Login T2 Function Verify Admin Enter The The Successful

ality that the must The admin admin
user have details can log can log
input access to into the into the in into
correct the text box. admin app.
input website panel.
provided in a
by the browser.
super
admin.
Ordering T3 Usability Check Verify The user The user The user Complete
Food Items whether that the can can be was able d
the user has select able to to do it.
orders added at any date order
food least one available food.
item is item into within 2
their weeks.
stored
cart.
into the
 database
.
Table T4 Usability Check Verify The user The user The user Complete
Booking whether that the can can as able d
the user user had select select to order
can book selected any date table food.
the number available booking.
desired of within 2
table. people weeks.
value
below
10.
Manage T5 Function Allows Check The The The Complete
Content ality the the admin admin admin as d
admin to admin is tries to wants to able to
manage logged add and manage manage
the into the manage content. the
content system. new contents
of the products .
database .
.
6.6 Result and Findings

6.6.1 Results and Finding by Dhiraj

During these 12 weeks, we have gone through up and down. Doing a project
by myself is a big challenge for any individual when there are too many things
to do so, first, I learned how to work in a team and guide the team as a scrum
master. Through this project, I have done so much research. Few of the topics
were familiar for me but few were completely new for me, but I did it. I got the
chance to learn so many new things.
Whatever we learn we have applied in our project and linked with our project
to give a better output. We came to know that to work in the real world, we
need patience with wise skills to use our knowledge in right place.

6.6.2 Results and Finding by Sagar

One of the things we found while working on this project was that it is difficult
to work in real-life work alone. Having a team means a division of workloads.
This helps in the better achievement of goals. Object-oriented programming
helps in developing better applications with a better workflow. 
Similarly, we came to know about modern technology for testing our system.
We use Google firebase as our backend which gives us a new idea about the
NO SQL database. We get familiar with project management also. During the
last week, I also found out about some free web hosting providers where we
can share our project. Such things will help us to share our project online for
free.

6.6.3 Results and Finding by Pradeep

• This project taught me how to do work together in a real-world
situation.
• While doing the literature review, I came to knew that the design of the
android application not only depends on the developer but also on its
user and the system designer.
• I learnt how to present the work I have done in a proper organization.
• How to identify the problem and critical thinking.
• In future, how I can improve the online business by implementing a well-
designed and secured android mobile application, that has the capability
of showing the day-to-day business processes along with the analysis of
ongoing business.
Chapter 7: Summary, Limitation, and Recommendation

7.1 Summary
After doing research and implementing it, in the end, we successfully made a
mobile application and web application. A mobile application is made for a
customer who wants to buy or knows about the menu of the restaurant where
customers can order online and pay at pick up and they can also reserve the
table for dine-in service. A web application is launched for the admin panel
where the admin has varieties of features like they can edit the menus, they
can add special events, they can manage the reservations, they manage the
orders, they have a dashboard from where they can see the sales trend and
ratios.
After researching so many frameworks, theories and linked up with the real
world, we can say that we have used our skills in the different field which we
have learned during our whole courses.
This master project is a get way of learning real-world programming
experience. We develop a mobile application that provides dynamic content
through the web admin page. From design to research and coding, we learn
how to work in a group to complete a project at the given time interval.
At the end of our semester, we develop an android application and a web
application which was quite a big achievement for us. The skill we learned
during this semester will help us for pursuing a career in Software Engineering.
All the insignificant things we did from analysis to deployment of our system
everything will help us to boost our knowledge and confidence in future real-
life work projects. All the research and development procedures we adopted
helped us to increase our knowledge.

7.2 Limitation
As being ERP students, we know we can do even better than this in so many
fields like we can organize different types of surveys and we can follow
different types of survey measuring methods like the Likert scale. We can work
more on our wireframing model, to be a model to make a more attractive and
real-time effective application but we have a limitation of time, resources. 
We cannot develop such a complex application in just a few months. This is not
a fully completed application and has lots of bugs and many features to be
added. Some of the features we can add in the future are.
 Home Delivery System using GPS navigation so that customers can check
the status of their food item.
 Online Payment can also be added which will help in a faster and secure
method of payment gateway using a customer’s credit card. This will
also help in a faster process in food takeaway.
 More Optimized system: We believe that the current system has many
bugs we need to fix. Such a thing can be optimized by a better testing
approach.
For the time being, the software is only offered for Android phones. As a result,
in the long term, we will be able to create an iPhone application as well. 

7.3 Recommendation
Besides the requirement of the client, we would recommend them to add
musical events in a restaurant like live music, any game and make publicity
through application in special events. As the client was asking about
debit/credit cards only in payment systems but we recommend adding
AMEX(American Express) too. We would like to recommend that rather than
depending on Uber, Doordash, or Menulog, the restaurant itself start
delivering facilities.

7.4 YouTube Links for Individual Reflection

Student’s Name YouTube Link

Dhiraj Kumar Thakur
Bikash KC https://youtu.be/qs0VJrfKx3c

Pradeep Thapa

Sagar Parajuli https://www.youtube.com/watch?v=h8WR2Qp66P4

7.5 List of Tasks
Student ID Student Name Role Tasks
1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 2.1,
30378004 Dhiraj Kumar Thakur Scrum Master 2.2, 2.3, 2.4, 3.1, 3.2, 4.1.1, 4.1.2,
4.3.1, 4.3.2, 5.2.2, 5.2.3, 6.6.1, 7.1,
7.2, 7.3
4.1.3, 4.1.4, 4.1.5, 4.2.1, 4.2.2,
30380267 Bikash KC Team Member 4.2.3, 4.2.4, 4.3

4.1.6, 4.1.7, 5.2.1, 5.2.4, 5.2.5,

30377119 Pradeep Thapa Team Member 5.2.6, 6.6.3

4.1.8, 5.1, 6.1, 6.2.1, 6.2.2, 6.2.3,

30381175 Sagar Parajuli Developer 6.2.4, 6.2.5, 6.3, 6.4, 6.5.1, 6.5.2,
6.5.3, 6.6.2, 7.1, 7.2
References
99Guru. (2020, 11). Unit Testing Tutorial: What is, Types, Tools & Test EXAMPLE. Retrieved from
99Guru: https://www.guru99.com/unit-testing-guide.html

Bargiela, S. S. (3rd June, 2016). A BUSINESS PLAN FOR A NEW MOBILE APPLICATION .

Devos, J. (n.d.). Heursitic Principles for Mobile Interface. Toptal.

Diagram, U. (2021, 06 01). UML Use Case Diagram Example. Retrieved from UML Diagram:
https://www.uml-diagrams.org/restaurant-uml-use-case-diagram-example.html

Fundamentals, S. (2020). Acceptance Testing. Retrieved from Software Fundamentals:

https://softwaretestingfundamentals.com/acceptance-testing/

Klipfolio. (2019). Data Dashboard. Klipfolio.

Rosencrance, L. (2021, 06 02). Google Firebase. Retrieved from Tech Target:

https://searchmobilecomputing.techtarget.com/definition/Google-Firebase

Shugan, D. &. (1999). Distribution of Pricing Incentives.

Spring. (2020, 02 02). React.js and Spring Data REST. Retrieved from Spring:
https://spring.io/guides/tutorials/react-and-spring-data-rest/

Susskind, R. &. (2004). Mobile service for Restaurants.

Tarver, E. (Jul 5, 2020). Balance Scorecard. Investopedia.

Wrike. (2020, 02 07). What Is a Project Management Approach? Retrieved from Wrike:
https://www.wrike.com/project-management-guide/faq/what-is-a-project-management-
approach/

Babich, N. (2018). A Comprehensive Guide To Mobile App Design. Smashing Magazine, 12.

Rooney, J. J., & Heuvel, L. N. V. (2004). Root cause analysis for beginners. Quality
progress, 37(7), 45-56.
Peerally, M. F., Carr, S., Waring, J., & Dixon-Woods, M. (2017). The problem with root cause
analysis. BMJ quality & safety, 26(5), 417-422.
Alagheband, M. R., Mashatan, A., & Zihayat, M. (2020). Time-based gap analysis of
cybersecurity trends in academic and digital media. ACM Transactions on Management
Information Systems (TMIS), 11(4), 1-20.
Kale, S., Goti, P., & Roychaudhary, R. C. Online Table and Menu Booking System for
Restaurants.
What is Research- Definition, Types, Methods & Examples. QuestionPro. (2021). Retrieved 20 May
2021, from https://www.questionpro.com/blog/what-is-research/.
What Is Research Methodology? Simple Definition (With Examples) - Grad Coach. Grad Coach. (2021).
Retrieved 17 May 2021, from https://gradcoach.com/what-is-research-methodology/.

Alzheimer Europe - Research - Understanding dementia research - Types of research - The four main
approaches. Alzheimer-europe.org. (2021). Retrieved 20 May 2021, from https://www.alzheimer-
europe.org/Research/Understanding-dementia-research/Types-of-research/The-four-main-
approaches.

The Basics of Documenting and Analyzing Your As-Is Process | Lucidchart Blog. Lucidchart.com.
(2021). Retrieved 23 May 2021, from https://www.lucidchart.com/blog/as-is-process-analysis.

Doub, A. E., Levin, A., Heath, C. E., & LeVangie, K. (2015). Mobile app-etite: Consumer attitudes
towards and use of mobile technology in the context of eating behaviour. Journal of direct,
data and digital marketing practice, 17(2), 114-129.
Gill, M., Sridhar, S., & Grewal, R. (2017). Return on engagement initiatives: A study of a business-to-
business mobile app. Journal of Marketing, 81(4), 45-66.
Qin, M., Tang, C.-H. H., Jang, S. S., & Lehto, X. (2017). Mobile app introduction and shareholder
returns. Journal of Hospitality and Tourism Management, 31, 173-180.