Find Delicious Dishes Near You

Table of Contents
1.1 Introduction ........................................................................................................................................ 3

1.2 Purpose.......................................................................................................................................... 3
1.3 Problem Statement...................................................................................................................... 4
1.4 Objective ...................................................................................................................................... 4
1.5 Executive Summary .................................................................................................................... 4
1.6 Existing Solution ......................................................................................................................... 4
1.7 Proposed Solution ........................................................................................................................... 4
2.2 Overall description .................................................................................................................... 8
2.3 Specific requirement ............................................................................................................... 19
2.1. Architecture Diagram .............................................................................................................. 31
ERD with data dictionary .................................................................................................................... 32
2.1. Data Flow diagram .................................................................................................................. 33
2.1. Class Diagram .......................................................................................................................... 35
1.1 Activity diagram .......................................................................................................................... 37
1.1 Admin ................................................................................................................................................ 37
1.1 Manager ............................................................................................................................................ 38
1.1 User/Customer .................................................................................................................................. 39
2.2. Sequence Diagram .................................................................................................................. 40
2.1. Collaboration........................................................................................................................... 44
2.2. ...................................................................................................................................................... 44
2.3.
1|Page
Error! Bookmark not defined.
2|Page
2.1. State Transition Diagram ........................................................................................................ 46
2.1. Component Diagram ............................................................................................................... 49
2.1. Deployment Diagram .............................................................................................................. 50
1.1 Introduction
Now a days, Smartphones are emerging exponentially and are prevalent to provide tech
services like navigation, web surfing, games, and almost all functionality just in your hand. This
change encourages the developers to develop apps that personalized to mobile phone terms and
could be used easily through this simple, light weight hand-held device.
Mobile applications (apps) can help people manage their own health and food, promote
healthy living through food, and gain access to useful information about restaurants when and
where they need it. These tools are being adopted almost as quickly as they can be developed.
Mobile has become an inseparable part of our existence. It is observed the unavailability
of information about nearby and top-rated do dishes has resulted into disappointment.
“DELICIOUS FOOD FINDER”. Addresses the concern of our society by using android
application development especially for Pakistan. However, developing this type of app gives a big
challenge because of the limited mobile resources such as the memory size, the CPU cycle, the
battery life, etc. Therefore, the approach that is used to solve this problem is to develop apps
conferring to the resource’s capacity of each mobile device.
Any new user that is new in country/city while entering a restaurant for food, one usually
struggles to acquire their Menu and Reviews to compare their food items, quality, pricing, service
and general ambiance. It is difficult to find a Restaurant with most liked dishes for a stranger or
for a new person. For this purpose, people head to social media or ask their colleagues. Using this
app user will beneficially helpful in a search for a restaurant and dishes by different criteria such
as restaurant name, dish name, or city name etc. It is basically food social app, which encircles all
taste needy persons to help them as early as possible. That’s why we name this application
“DELICIOUS FOOD FINDER”.
1.2 Purpose
Our main purpose of developing this app is to facilitate the people to find the delicious food in a
particular area. This application will make the eatery decision better of the people. It is very easy
to find the good taste in a particular area through the mobile application. With the help of this
application people don’t need to ask anyone spreading awareness of how we can consume extra
food wisely, instead of littering or wasting it. It is better to feed any hungry needy than to later liter
in bins, rotten on road and streets, and spread contagious diseases. It is an important cause of our
environment pollution. By using this app, people will be able to donate food at their doorstep in
just couple of minutes.
This application is based on some simple steps that allow donors to avail services by few clicks.
3|Page
1.3 Problem Statement
While entering a restaurant one usually struggles to acquire their menus and reviews to compare their
food items, quality, price, services and general ambiance.
Or visiting new place people head to social media or ask their colleagues. People have no idea about the
famous dishes of different restaurants. They always need help to make the decision about good taste.
1.4 Objective
 Facilitate the people to find the restaurant easily through navigation.
 People can find the famous dishes of different restaurants easily.
 Management can enhance the publicity of their most delicious dishes.
 People can find by their own.
1.5 Executive Summary

We are going to develop the application which will provide the information about the famous dishes of
the different restaurants depending on the basis of reviews of people. People can find the restaurants
according to their famous dishes in the nearby area. This application will provide information directly
about the famous dishes instead of asking from others.
1.6 Existing Solution

There are many applications available which just take reviews of particular restaurants as a whole.
People cannot find best food easily. While entering a restaurant for food, one usually struggles to
acquire their menu to compare their food items, quality, pricing, service and general ambiance.
1.7 Proposed Solution

Tagline of system: Make Your Eatery Decision Better.

Restaurant Finder & Navigate Yourself
With basic restaurant information on virtually every most liked dishes in user’s locality. Google map,
identify user’s location with automate navigation system and provide a route to the users nearest
restaurant of most liked dish (e.g. Chicken Karahi – Tabaq Restaurant, Chicken Biryani – Punjab
Restaurant etc.)

Recommendation and Searching Dishes
On the bases of your current location most liked dishes of your nearby restaurants will be
recommended. It will beneficially helpful in a search for any restaurant and their dishes on the basis
of different criteria such as name of dish, city name or fields such as specialty (GPS LOCATION-AREA)
etc.
Rating of Dishes
Verified reviews from user on Dish. It will generally impact on Dish Rating and it also helpful for
Restaurant fame and their good taste.
Google Play Services
4|Page
Google Map API + v2 Key

Data Storage
API in PHP Web view

Admin Panel
 Login
 View Data (Restaurant + User + reviews)
 Add, View, Remove, Update Restaurants
 Add, View, Update, Remove Dishes
 Update Timing of Restaurants
 Send Discount Notification
 Add, View, Update user, Delete user
 View, Update, Remove user review
 Change password

Restaurant Admin Panel
 Signup and Login
 View Data (Restaurants + Dishes + reviews)
 Delete (Restaurants + Dishes)
 Update (Restaurants + Dishes)
 Send Discount Notification Through SMS
 Add and Update location of Restaurant
 View, Update basic information of Restaurant (timing + outdoor sitting + Wi-Fi)
 Change Password

User Panel
 Signup and Login
 View (Restaurant + Dishes + Reviews)
 View (Restaurants + Dish) Information in Detail
 View Most Liked Nearby Restaurants Dishes
 Give 5-Star Rating + Review on Dish
 Received Discount Notification Through SMS
 Get Recommendation of nearby dishes
 Navigate path towards Restaurant (Google Map)
 Searching (restaurant name) etc.
 Change Password
5|Page
Chapter 2 Software Requirements Specification
6|Page
2.1 Introduction
2.1.1 Purpose
This document provides requirement specification for finding the nearest restaurants with their best
dishes. Our purpose is to make a user friendly, economic and common solution for our customers/users.
The users can also view information according to their roles. Our intention is to give access to the people
who want to identify best food nearby. The purpose is to develop an application that allows user to login
after creating account, user can search dish on the basis of quality and price, navigate towards restaurant
and provide recommendation.
2.1.2 Scope
The delicious food finder application includes all accessibility to the people who wants to know about
famous dishes of particular area. This application can be use country wide, in any city or town but the
application is running in Lahore, yet. Any person who wants to get information about delicious food can
use this application in just few clicks. By using Google maps API, user can access to the nearest restaurants
with their best dishes, where they can find the good food. In short, this app will help to make eatry decision
better, effective and efficient.
2.1.3 Definitions, acronyms, and abbreviations
Term Definition
User/Customer Someone who interacts with the application to find delicious food.
Admin/Administrator System administrator who is given specific permission for managing and
controlling the system
Web-Portal A web application which present special facilities for donors and
Volunteers
Google Maps API Google maps application program interface
SDK Software Development Kit
2.1.4 References
 https://www.w3schools.com/
 https://www.tutorialspoint.com/
 https://developer.android.com/reference/org/w3c/dom/Document.html
2.1.5 Overview
Overall d The SRS is divided into three major components:
The first part contains the introduction about the project to be prepared; it also describes the basic
purpose and the scope of the document.
The second part describes the overall description about the project. Then in the last part specific
requirements are listed.
Next, we explain the design procedures with the help of different UML diagrams. In the next phase we
explain all the testing strategies that are used and finally the document lists down all the technologies
that the project is using.
7|Page
2.2 Overall description
2.2.1 Product perspective

“Delicious Food Finder” is an interactive web and android based application A Web, that will allow master
admin to add restaurants, and manage all the functionalities about restaurants, their dishes, schedule
updates.one the other hands manager can update, delete, view and send the notifications. And the user
can search the restaurants on the basis of dishes reviews, price and time category like breakfast, lunch
and dinner. User can navigate towards the restaurants through google maps. User can give reviews about
the dishes and user can view the reviews also.
2.2.1.1 System Interfaces

This should list each system interface and identify the functionality of the software to accomplish the
system requirement and the interface description to match the system
.
2.2.1.2 User Interface
As it is mentioned above this product would contain numerous user interfaces ranging of that from the
android application. The list below shows the user interfaces that are comprised respectively. There are
numerous features that we are trying to embed in this particular software so quite a few screens are used
to show clarity amongst different interfaces
.
Screens for Application
 Create Account
 Login
 Login verification page
 Home page
 Restaurant Details page
 Dish details page
 Google maps
 Review page
Correct username and password must be fed into the website to make sure that the correct user is using
the system. If for some odd reason the correct values are not entered then the system would quickly
prompt the user to enter correct data.
2.2.1.3 Hardware Interface
To enjoy the food donor web application following hardware tools must be used:
Processor core i3/i5 | dual core
Hard Disk 250 GB
RAM: 2 GB
LAN CAR
8|Page
Keyboard 108 keys
Monitor VGA
Mobile/Tab Minimum 1 GB Ram
2.2.1.4 Software Interface
User / Interface Material Design / UI /UX / API in php / Bootstrap
Language Android Programming, Php,
Database: MYSQL
2.2.1.5 Communication Interface
As this application is web and android based, the communication between the web and android application will
be done by volley library.
2.2.1.6 Memory
There are no constraints on either primary or secondary memory.
2.2.1.7 Operations
The basic operations that will be done by Admin, Restaurant manager and Customer/User are as follow:
 Admin will add, delete or update the accounts of restaurant Manager and Customer. Admin will maintain
the website, records, etc.
 Restaurant manager will register, login website, update, view and some delete functionalities.
 Customer/User will register, create profile, find restaurant detail, dishes details, and navigation towards
restaurant, and even can search the restaurant or dishes on the basis of quality and price through
reviews.
2.2.1.8 Site adaptation requirements
There are no special requirements for this site adaption a user just must have any smart phone, laptop or
computer.
2.2.2 Product Functions
ID FR_01
Name signup
Description Input Output Requirements Basic Work Flow
To Create Account Open the application Signup page is Internet Connectivity Open application to
and click signup shown required sign up.
button
Table 1 Functional Requirement create account

9|Page
ID FR_01
Name Login
To log in to the Open the application Log in page is shown Internet Connectivity Open the
page and click signup and registration is Application to
button required. login
Table 1 Functional Requirement login
ID FR_01
Name Search
To search the User should login to Searching Options Internet Connectivity Login to the
details the account displayed and login required application and
search the restaurant
or their dishes
Table 1 Functional Requirement search
10 | P a g e
ID FR_01
Name Navigate
To get direction Open the application Navigation started Internet Connectivity Open the
and login, then use successfully required application login,
navigation, current use navigation
location is required towards restaurants
open
Table 1 Functional Requirement navigation
ID FR_01
Name View highlights
To view Enter URL to open Highlights viewed Internet Connectivity Open website and
highlights the website and successfully required click on highlights
click highlights button to view
button highlights
3 Table 1 Functional Requirement View highlights
ID FR_01
Description Input Output Requirements Basic Work F
To view Enter URL to open Highlights viewed Internet Connectivity Open website
highlights the website and successfully required click on highli
11 | P a g e
button highlights
5
ID FR_01
button highlights
7
ID FR_01
button highlights
9
ID FR_01
12 | P a g e
button highlights
11
ID FR_01
button highlights
13
ID FR_01
button highlights
15
ID FR_01
13 | P a g e
button highlights
17
ID FR_01
button highlights
19
ID FR_01
button highlights
21
ID FR_01
14 | P a g e
button highlights
23
ID FR_01
button highlights
25
ID FR_01
button highlights
27
ID FR_01
15 | P a g e
button highlights
29
ID FR_01
button highlights
31
ID FR_01
button highlights
33
16 | P a g e
ID FR_01
button highlights
35
ID FR_01
button highlights
37
ID FR_01
button highlights
17 | P a g e
39
ID FR_01
button highlights
41
ID FR_01
To view Enter URL to open Highlights viewed Internet Connectivity Open website and
Highlights the website and successfully required click on highlights
button highlights

43
2.2.3 User Characteristics

There are three type of people that are interacting with the system: Admin, Restaurant Manager, and the
Customer. Each of these users have different use of system so each of them have their own requirement.
2.2.4 Constraints
The internet connection is the main constraint for the application. Since the application can perform functions only
when user login and use map to select location, so internet connection is crucial.
Some of the constraints are as follows:
2.2.4.1Hardware Limitations
There is no tough hardware required for using our application but it is recommended to use better machine to run
application perfectly.
18 | P a g e
2.2.4.2 Parallel Operations
There are no parallel operations in our system because we design interface in such a way that all operations are
in sequence and it consists of simple and easy steps.
2.2.4.3 Control Functions
Functions should be in control of admin so the ordinary user don’t get any access of the system. We make sure
that our system doesn’t allow any un-authorized access.
2.2.5 Assumptions and Dependencies
Dependency of our product is that always be used if you have internet connection. Some of the others are
as follows:
 User must have mobiles or pc/laptops according to system requirement for the intermediate connection.
 Updates are required so that the admin work properly all the time.
 The website will target the both system users and smart phone users according to their requirement.
 If there is anything which need to update in the website, it should be deal well.
 User should have the basic knowledge of the system.
 Catalogue or manual would be provided.
2.2.6 Apportioning of requirements
If there are any updates in the software, we may need a few additional requirements to cope with the problem.
2.3 Specific requirement

2.3.1 Functional Requirement
Functional requirement is used to define a function of a system and its components. Functional requirements of
Delicious Food Finder application may be its technical details, data manipulation and processing and other
specific functionality that define “what is system going to do”.
There are three main modules in our project:
 Admin
 Restaurant Manager
 Customer/User
2.3.1.1 Google Play Services
 System should show the map integration through Google Map API + v2 Key
2.3.1.2 Data Storage
 System should save data in API in PHP Web and android view
2.3.1.3 Admin Panel
 System should Add Restaurant, Remove Restaurant, Update Restaurant
 System should View Dishes, Delete Dishes, Update Dishes
 System should Update Timing of Restaurants.
 System should Send Discount Notification
 System should View user and Restaurant Owner Profile
 System should Add location through Google map
 System should View, Update, Remove review
 System should View, Update basic information of Restaurant (timing +
 outdoor sitting + Wi-Fi)
 System should Create New Admin
 System should Change Password
19 | P a g e
2.3.1.4 Restaurant Manager Panel
 System should show Login & Signup in Restaurant interface
 System should show Interface of View Data (Restaurants + Dishes + Reviews)
 System should Add Restaurant, Remove Restaurant, Update Restaurant
 System should View Dishes, Delete Dishes, Update Dishes
 System should Update Timing of Restaurant
 System should Add location through Google map
 System should Send Discount Notification
 System should View, Update basic information of Restaurant (timing +
outdoor sitting + Wi-Fi)
 System should Change Password
2.3.1.5 User Panel
 System should show Login & Signup in User interface
 System should show Interface of View Data (Restaurants + Dishes + Reviews)
 System should View Nearby Most Liked Dishes of Restaurants
 System should Receive Discount Notification 
 System should Search Dishes (Dish Name + City Name)
 System should get recommendation of nearby most liked dishes
 System should view profile, update profile
 System should do five star ratings, reviews
 System should change password
 System should Navigate path towards Restaurant (Google Map)

2.3.2 Non-Functional Requirement
According to the goal of the project, the resulting prototype should be extendible, tailor able, and explore able and
put existing innovational technologies as many as possible as building blocks in the project. And user interface
should be readable, user friendly, easy to understand, and easy to operate. More over some nonfunctional
requirements are:
2.3.2.1 Usability
Product should be used by specified users to achieve specified goals with Effectiveness, efficiency, and satisfaction
in a specified context of use.
2.3.2.2 Operability
The whole installation should be in a safe and reliable functioning condition, according to pre-defined operational
requirements.
2.3.2.3 Reliability
The specified components should be able to perform its required functions under stated conditions for a specified
period of time.
2.3.2.4 Performance
Focus should be kept on monitoring and managing the performance and service availability of software of
applications.
20 | P a g e
Chapter no.3
21 | P a g e
3.1 Use Case Diagram


Figure 1 integrated Use Case diagram
22 | P a g e
3.1.1 Signup
Figure 2 Use Case for Signup
 Use Case Id: 01

 Use Case Name: UC – Register
 Level: User
 Primary Actor: User
 Goal: To create an account
 Pre-condition System has been programmed for register/signup
 Post Condition: After filling required field user successfully registered
 Trigger: User
User Activity System response
1.User observed register form

2.User fill require field
3.User press register button 3.System verify require field
4.System saves user data
23 | P a g e
 Alternative path
1.Field not filled properly

2.System signal error and reject signup process
and redirect to registration page
3.1.2 Login
 Use Case Id: 02

 Use Case Name: UC – Login
 Level: User
 Goal: To grant access to user to perform some tasks
 Pre-condition System has been programmed for login
 Post Condition: After entering id and password user successfully login
 Trigger: User
24 | P a g e
1.User observed login panel
2.User enter user name and password
3.User press login button 3.System verify user name and password
4.System view profile page
1.invalid password or user name
2.System signal error and reject login process and
redirect to login page
3.1.3 Rating
25 | P a g e
 Use Case Id: 03
 Use Case Name: UC – Rating
 Level: User
 Goal: To give review and rating on dishes
 Pre-condition User should be login
 Post Condition: Give rating and review successfully
 Trigger: User
1.User observed list of dishes

2.User click on single dish
3.User give rating and review 3.System shows dish information in detail
4.System saves ratings and reviews
1.If user not login

2.System notify to be login
3.1.4 Navigation
Figure 5 Use Case for Navigation
26 | P a g e
 Use Case Id: 04
 Use Case Name: UC – Navigation
 Level: User
 Goal: Navigate path toward restaurant
 Pre-condition System display a list of top dishes
 Post Condition: A path will be shown to user restaurant
 Trigger: User

1.User observed list of dish
2.User select a dish
3.User press navigation button 3.Show restaurant detail of that dishes
4.Show path from user to restaurant on google map

1.Field not login
System should notify to be login
3.1.5 Add Location
Figure 6 Use Case for Add Location

27 | P a g e
 Use Case Id: 05
 Use Case Name: UC – Add location
 Level: Restaurant admin/Main admin
 Primary Actor: Restaurant admin/Main admin
 Goal: Add location of restaurant
 Pre-condition Admin should be login
 Post Condition: Add location on google map successfully
 Trigger: Restaurant admin/Main admin
1.User press add restaurant button 1.Show google map with moving pointer on map
2.User after searching city more cursor on map to Save exact location of restaurant
save exact location
1.If restaurant manager/Admin not login

3.1.6 SMS Notification
Figure 7 Use Case for SMS Notification
28 | P a g e
 Use Case Id: 06
 Use Case Name: UC – SMS notification
 Level: Restaurant admin/Main admin
 Primary Actor: Restaurant admin/Main admin
 Goal: Send SMS notification of dish discount
 Pre-condition Admin should be login
 Post Condition: Send dish discount notification through SMS to user that give rating
 Trigger: Restaurant admin/Main admin

1.Restaurant manager/Admin login 1.System verify authorized admin/restaurant
manager show
2. Restaurant manager/Admin press dish update 2.System show update field
button
3. Restaurant manager/Admin login set discount 3.System send SMS of discount to User
1.If restaurant manager/Admin not login

29 | P a g e
Delicious Food Finder


Chapter 4
30 | P a g e
2.1. Architecture Diagram
31 | P a g e
ERD with data dictionary
32 | P a g e
2.1. Data Flow diagram
 The level 0
The flow of information inside the system is defined in this level
33 | P a g e
 The level 1
The flow of information outside the system is defined in this level
34 | P a g e
2.1. Class Diagram

Class diagrams are the backbone of almost every object oriented method, including UML. They describe
the static structure of a system. It shows the classes in a system, attributes and operations of each class
and the relationship between each class. In most modeling tools a class has three parts, name at the
top, attributes in the middle and operations or methods at the bottom. Different relationships between
classes are shown by different types of arrows
35 | P a g e
36 | P a g e
1.1 Activity diagram

1.1 Admin
37 | P a g e
1.1 Manager
38 | P a g e
1.1 User/Customer
39 | P a g e
2.2. Sequence Diagram
Sequence diagrams describe interactions among classes in terms of an exchange of messages

over time. Sequence diagrams in UML shows how object interact with each other and the
order those interactions occur. The processes are represented vertically and interactions are
show as arrows. A characteristic of a sequence diagram is that time passes from top to
bottom: the interaction starts near the top of the diagram and ends at the bottom. Sequence
diagrams has certain benefits:
 You can easily see how tasks are distributed between components.
 You can identify patterns of interaction that make it difficult to update the software.

a) Login
This sequence diagram is to elaborate login sequence of system for user.
40 | P a g e
Rating
This diagram shows how user perform rating and review of dish.
41 | P a g e
c) Navigation
This sequence diagram show how user navigate its path towards restaurant.
42 | P a g e
e) Add location
This sequence diagram show how Main Admin/Restaurant Admin add location
of Restaurant through Google Map.
43 | P a g e
2.1. Collaboration
44 | P a g e
45 | P a g e
2.1. State Transition Diagram
46 | P a g e
47 | P a g e
48 | P a g e
2.1. Component Diagram
49 | P a g e
2.1. Deployment Diagram
50 | P a g e

Find Delicious Dishes Near You

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Find Delicious Dishes Near You

Hochgeladen von

Copyright:

Verfügbare Formate

Table of Contents

1.1 Introduction ........................................................................................................................................ 3

1.5 Executive Summary

1.6 Existing Solution

1.7 Proposed Solution

Google Play Services

2.1.3 Definitions, acronyms, and abbreviations

2.2.1 Product perspective

2.2.1.1 System Interfaces

2.2.2 Product Functions

Description Input Output Requirements Basic Work Flow

Table 1 Functional Requirement create account

Description Input Output Requirements Basic Work Flow

Table 1 Functional Requirement login

Description Input Output Requirements Basic Work Flow

Table 1 Functional Requirement search

Description Input Output Requirements Basic Work Flow

Table 1 Functional Requirement navigation

Name View highlights

Description Input Output Requirements Basic Work Flow

3 Table 1 Functional Requirement View highlights

Name View highlights

Description Input Output Requirements Basic Work F

4 Table 1 Functional Requirement View highlights

Name View highlights

Description Input Output Requirements Basic Work F

6 Table 1 Functional Requirement View highlights

Name View highlights

Description Input Output Requirements Basic Work F

8 Table 1 Functional Requirement View highlights

Name View highlights

Description Input Output Requirements Basic Work F

10 Table 1 Functional Requirement View highlights

Name View highlights

Description Input Output Requirements Basic Work F

12 Table 1 Functional Requirement View highlights

Name View highlights

Description Input Output Requirements Basic Work F

14 Table 1 Functional Requirement View highlights

Name View highlights

Description Input Output Requirements Basic Work F

16 Table 1 Functional Requirement View highlights

Name View highlights

Description Input Output Requirements Basic Work F

18 Table 1 Functional Requirement View highlights

Name View highlights

Description Input Output Requirements Basic Work F

20 Table 1 Functional Requirement View highlights

Name View highlights

22 Table 1 Functional Requirement View highlights

Name View highlights

Description Input Output Requirements Basic Work F

24 Table 1 Functional Requirement View highlights

Name View highlights

Description Input Output Requirements Basic Work F

26 Table 1 Functional Requirement View highlights

Description Input Output Requirements Basic Work F

28 Table 1 Functional Requirement View highlights

Name View highlights

Description Input Output Requirements Basic Work F

30 Table 1 Functional Requirement View highlights

Name View highlights

Description Input Output Requirements Basic Work F