Project Siddhi

HOMEMADE FOOD DELIVERY APP| 2022
CHAPTER 1
INTRODUCTION
Online food ordering and delivery is the process in which order for the food is placed
through internet and delivered to the customer to the specified place. Food delivery Apps, online
food ordering systems is basically designed for those People that do not have time to go to
restaurant. As the say, money is not money but time is money. These systems impressively
simplify the ordering process for both customers and restaurants owner, this is the main
advantage of online food ordering or delivery system. In past manual food ordering system will
be used. In this system customers must go to the restaurant and waiter takes order from the
customer and writes down in the paper. In this system each type of record is stored on the paper.
Then the waiter sends the order to the kitchen for the further processing. Then Personal Digital
Assistant technology was used. Personal digital assistant is a portable device like smartphone
every waiter should have the PDA and take order form customers. To cover the limitation of
PDA multi touch technology come to market, where the user has the authority to perform and
control different type of operations at a time on multi touch screen. To cover the limitation of all
the previous food ordering systems, mobile food ordering system been developed. This system
automates all food ordering process. In the recent time of information technology people are
familiarized to use computer, mobile and mobile Apps. On the other hand, the use of mobile
application and their development is also growing fast area of information technology. Mobile
Application has not only impacted the Smart phone users but also play a vital role in our daily
business life. The first mobile which is come to market is so simple, that just have, clock, alarm,
and simple calculator. Basically, mobile Apps consists a set of instruction that runs on Smart
phones and perform a specific task. Developer built mobile application for different purposes.
Mobile applications are Easy to use, User friendly, Inexpensive, Convenient to carry, Powerful
development framework, simply downloadable, run on most of the mobile phone. There are a
number of Apps which are pre-installed in Smart phones and others Apps users can easily
download, installed in smartphone.
1|P ag e
In the past, people used mobile phone just for receiving call, messaging, and doing
simple calculations etc. Now a day, Mobile Phones are Used Commonly due to different
functionalities i.e., user can used for calling, used for messaging, used for browsing, used for
chatting, used for social network communication, and users can also use for audio, video, games
etc. Mobile food ordering and food delivery is one of most popular area of mobile application
development. The online food delivery application is impressively good for those people that do
not have time to go the restaurant. Anyone who have smart phone they can easily order for the
food from anywhere and they can receive food at her/her home. Payment can be either on
delivery or by credit card.
2|P ag e
1.1 Background
This application is developed for the common users who usually do not know to operate a
complex application. If any person wants buy any thing which is related to foods in his daily life
you can buy from this app. The Project is based on various events that are managed by
information and its services i.e. Registration of User, Login, checking for the Items, looking for
foods, etc. Others app are too vast and complicated. In this project use of reduced complexity of
app is well illustrated by making the UI simple and making the application which will meet the
needs of the common people.
1.1 Objectives
1. To discuss the concept of online food delivery applications.

2. To identify the pros and cons of the online food delivery apps from the point of view of
restaurants.
3. To analyze the pros and cons of the online food delivery apps from the view point of the
customer.
1.2 Purpose, Scope, and Applicability

1.2.1 Purpose
1.The purpose of the app is to deliver homemade food at the customer’s doorstep.
2. Women who love cooking are enrolled as chefs, and they bring home cooked food to your
doorstep.
3.To provide fresh, hygienic, affordable, and home food cooked through an online food
delivery app.
3|P ag e
1.3.2 Scope
Food Ordering app can sale Food product, preferred brands, kitchen needs, essential restaurant
supplies and more, through this online, one stop Food store. It provides you with a convenient
way to sale from your Food shopping app. You can use this app as one big super market app to
sale product of your store. This app makes easy for user to buy product from store with easy
steps and store can get easy order.
It may help collecting perfect management in detail. In a very short time, the
collection will be obvious, simple, and sensible. It will help a person to know the
management of passed year perfectly and vividly. It also helps in current all works
relative to Online Food Ordering System. It will be also reduced the cost of collecting
the management & collection procedure will go on smoothly.
Our project aims at Business process automation, i.e. we have tried to
computerize various processes of Online Food Ordering System.
 In computer system the person must fill the various forms & number of copies of
the forms can be easily generated at a time.
 In computer system, it is not necessary to create the manifest but we can directly
print it, which saves our time.
 To assist the staff in capturing the effort spent on their respective working areas.
 To utilize resources in an efficient manner by increasing their productivity through
automation.
 The system generates types of information that can be used for various
purposes.
 It satisfies the user requirement
 Be easy to understand by the user and operator
 Be easy to operate
 Have a good user interface
 Be expandable
 Delivered on schedule within the budget
4|P ag e
1.2.2 Applicability
Purpose of this research is making an ordering food application based on Android with New
Order, Order History, Restaurant Profile, Order Status, Tracking Order, and Setting Profile
features. The research method used in this research is water model of System Development Life
Cycle (SDLC) method with following phases: requirement definition, analyzing and determining
the features needed in developing application and making the detail definition of each features,
system and software design, designing the flow of developing application by using storyboard
design, user experience design, Unified Modeling Language (UML) design, and database
structure design, implementation an unit testing, making database and translating the result of
designs to programming language code then doing unit testing, integration and System testing,
integrating unit program to one unit system then doing system testing, operation and
maintenance, operating the result of system testing and if any changes and reparations needed
then the previous phases could be back. The result of this research is an ordering food
application based on Android for customer and courier user, and a website for restaurant and
admin user. The conclusion of this research is to help customer in making order easily, to give
detail information needed by customer, to help restaurant in receiving order, and to help courier
while doing delivery.
5|P ag e
1.3 Organization of Report
Our project study is organized from project contents that performed in each chapter of the
project and the purpose of this is to show activities and its sequence in each chapter. Activities
are shown below:
Chapter 1:- This chapter deals about introduction of the project. Determine objective: based on
the identified problem we design the objective of the project to be achieved. Determine Scope of
the project.
Chapter 2:- This chapter deals about the compatible technologies used in this project
Chapter 3:- This chapter deals about feasibility study, system analysis and the requirements.
Also deals with planning and scheduling of the project. It also depicts a conceptual model of the
project.
Chapter 4:- This chapter deals about system design in details.
Chapter 5:- This chapter deals with all the screen outputs displayed after the execution of the
project.
Chapter 6:- This chapter deals with the conclusion of the project and also discussed about the
future enhancement of the project.
Chapter 7:- This chapter deals with the websites, books used for the references.
6|P ag e
CHAPTER 2
SURVEY OF TECHNOLOGIES
FRONTEND: - ANDROID STUDIO 3.0.1
1. Android Studio is the official integrated development environment (IDE) for Google's
Android operating system, built on JetBrains' IntelliJ IDEA software and designed specifically
for Android development. It is available for download on Windows, macOS and Linux based
operating systems. It is our placement for the Eclipse Android Development Tools (ADT) as
primary IDE for native Android application development.VB.NET is totally object oriented. This
is a major addition that VB6 and other earlier releases didn't have.
2. Releases of Android Studio vary and will likely continue to, but at the time of writing, by
default Android Studio initially displays an editor area for Java and XML files together with the
preview area to the right of the screen. Experiment with the project view by expanding the
folders that appear within it. Expand "My Application" to access the contents of your new
project. You will find the items we will work with as we continue to learn Android development
inside the " src /main" directory. We will be particularly interested in the content of the "java"
and "res" folders.
3. One of the better features in Android Studio is that many of the tools you need are accessible
via the buttons in the toolbar. Take a moment to scroll over these now. Notice that there are
quick links to launch various utilities including the AVD Manager, SDK Manager, and the
Monitor that includes debugging tools.
4. Like Eclipse, Android Studio provides a range of views you can use to interact with the
contents of your projects. Select the "View" and "Tool Windows" menu to see the range of
options. Clicking these toggles, them in-and-out of visibility. Views you may find useful include
the Structure view, which is similar to the Outline view in Eclipse and the Event Log view,
which displays system output messages.
7|P ag e
5. One view you may find particularly useful once you are attempting to develop and debug apps
is the "Android" view. Open it now from the "Tool Windows" menu. This view displays
information about actual and virtual devices, together with the Log Cat for outputting debugging
messages.
6. As with Eclipse, you need to keep your Android Studio installation up to date to get the best
use out of it. You can use the "Help", "Check for Update" tool to keep the software itself up to
date regularly. This is advisable since Android Studio is under constant development, with
patches often released to address issues you may be facing.
BACKEND: FIREBASE DATABASE
1. Firebase is a Backend-as-a-Service — BaaS — that started as a YC11 startup and grew up into
a next-generation app-development platform on Google Cloud Platform.
2. Firebase stores data in Jason Tree formant with a root node and child inside the root node.
3. Firebase frees developers to focus crafting fantastic user experiences. You do not need to
manage servers. You don’t need to write APIs. Firebase is your server, your API and your
datastore, all written so generically that you can modify it to suit most needs. Yeah, you will
occasionally need to use other bits of the Google Cloud for your advanced applications. Firebase
cannot be everything to everybody. But it gets pretty close.
4. There are some services provided by Firebase used in this project.
8|P ag e
CHAPTER 3
REQUIREMENTS AND ANALYSIS

After analyzing the requirements of the project to be performed, the next step is to
analyze the problem. The first activity in the phase is studying the existing system and other is to
understand the requirements and domain of the new system. Both the activities are equally
important. The designing part starts after the requirement analysis is complete.
ANALYSIS MODEL:
The model that is basically being followed is the” WATER FALL MODEL”.
Fig No: 1. Waterfall Model
9|P ag e
The waterfall model is a sequential design process, often used in software development
processes, in which progress is seen as flowing steadily downwards (like a waterfall) through
the phases of Conception, Initiation, Analysis, Design, Construction, Testing and
Maintenance.
The first formal description of the waterfall model is often cited as a 1970 article by
Winston W. Royce, though Royce did not use the term "waterfall" in this article. Royce
presented this model as an example of a flawed, non-working model (Royce 1970).
Advantages of the Waterfall Model:
 Simple and easy to understand and use.

 Easy to manage due to the rigidity of the model – each phase has specific deliverables
and a review process.
 Phases are processed and completed one at a time.
 Works well for smaller projects where requirements are very well understood.
FEASIBILITY STUDY
The feasibility of the project is analyzed in this phase and business proposal is put forth
with a, very general plan for the project and some cost estimates. During system analysis the
feasibility study of the proposed system is to be carried out. This is to ensure that the proposed
system is not a burden to the company. For feasibility analysis, some understanding of the major
requirements for the system is essential. Three key considerations involved in the feasibility
analysis are
 Economical Feasibility
 Technical Feasibility
 Social Feasibility
10 | P a g e
ECONOMICAL FEASIBILITY
This study is carried out to check the economic impact that the system will
have on the organization. The amount of fund that the company can pour into the research and
development of the system is limited.
TECHNICAL FEASIBILITY
T his st udy is car r ied o ut t o check t he t echnic a l fe as ib i l it y, t hat is, t he

t echnic a l requirements of the system. Any system developed must not have a high
demand on the available technical resources. This will lead to high demands on the
available technical resources. This will lead to high demands being placed on the client. The
developed system must have a modest requirement, as only minimal or null changes are required
for implementing this system.
SOCIAL FEASIBILITY
The aspect of study is to chec1 the level of acceptance of the system by the user. This includes
the process of training the user to use the system efficiently. The user must not feel threatened by
the system, instead must accept it as a necessity. The level of acceptance by the users solely
depends on the methods that are employed to educate the user about the system and to make him
familiar with it. His level of confidence must be raised so that he is also able to make
some constructive criticism, which is welcomed, as he is the final user of the system.
11 | P a g e
3.1 Problem Definition
As seen clearly a lot of time is spent and much effort is made for managing the daily records and
the staff records. In today’s world which is growing, these all tasks should have taken minimum
efforts and less time. But in the present system the user must maintain the records on paper
which is very difficult and complex. The existing system is working with the manual system.
And we all know that the manual system has many disadvantages. The manual system requires
more time for processing. It requires more critical work. The manual system is more error prone.
It is also very difficult to maintain. Manual system is costly. Immediate response to the queries is
difficult and time consuming in manual system. Here more man power is needed. So to
overcome the disadvantages of the existing system we need to create a new system. The new or
proposed system requires less time for completion of any work. The proposed system will also
help the users in decreasing the chances of errors. This system will work smoothly and very fast
as compared to the existing system. This system will also help in saving time and manpower.
This system is user friendly and anyone having computer knowledge can handle it easily. It is
suitable for computerized data entry. The main motto behind creating this software is to maintain
information, Staff information & Customer information.
3.2 Requirement Specification
Requirement analysis for web applications encompasses three major tasks: formulation,
requirement gatherings and analysis modeling. During formulation, the basic motivation and
goals for the web application are identified, and the categories of users are defined. In the
requirements gathering phase, the content and functional requirements are listed and interaction
scenarios written from end-user’s point-of-view are developed. This intent is to establish a basic
understanding of why the web application is built, who will use it, and what problems it will
solve for its users.
12 | P a g e
Proposed System
 The proposed system provides basic information about the various types of meals, foods like
Thali, Tiffin, Dessert etc.
 The application is integrated to reduce the complexity of the present system HFD App
 The UI of this application is simple and easy to understand for the common peoples.
 The application reduces the complexity by providing the things that are useful for common
man’s daily needs
 The database used for this application is a real-time database that reflects the changes quickly.
 A proper authentication is used for this application with email-id and password for registration
of the user.
 A user feedback form is provided to get know about the application.
 A unique identifier is provided to each product which identifies product uniquely.
13 | P a g e
3.3Planning and Scheduling
A Planning and Scheduling is a chart that shows all of the different tasks of a project and how
they relate to each other in terms of time. It’s a way of displaying your project schedule and it
helps get the work done on time. It shows all of the tasks That need to be done, the amount of
time each task is expected to take, the time frames in which individual tasks are to be completed,
and the relationship between various tasks. This way everything gets done on schedule.
Gantt chart
Fig No: 2.Gantt chart
14 | P a g e
3.4 Software and Hardware Requirements
3.4.1 Software Requirements
Operating System : Windows 10
User interface : HTML, CSS, JavaScript
Database : Firebase Database
Documentation Tool : Ms Office, Sublime Code Editor
Server : XAMPP Local Server
3.4.2 Hardware Requirements
Processor : Intel
RAM : 8 GB Ram or more
Hard Disk : 512 MB
Monitor : Standard Monitor
Keyboard : Standard Keyboard
Mouse : Standard Mouse
15 | P a g e
3.5 Preliminary Product Description
Food delivery service is somewhat like courier service in which the ordered food is delivered from
the restaurant to the customer either by the restaurant's staff or by delivery agents of a food
ordering company. This obviously depends on the medium through which a customer places
his/her order.
3.6 Conceptual Models

3.6.1. Use Case Diagram
A use case diagram is a diagram that shows a set of use cases and actors and
relation.
Fig No: 3. Use Case Diagram
16 | P a g e
3.6.2 Activity Diagram
 An activity diagram shows the flow from activity to activity. An activity is an ongoing non- atomic
execution within a state machine.
 Activities ultimately result in some action, which is made up of executable atomic
computations that result in a change in state of the system or the return of a value.
A. Customer Activity Diagram
Fig No: 3. Customer Activity Diagram
17 | P a g e
B. Admin Activity Diagram
Fig No: 4. Admin Activity Diagram
18 | P a g e
3.6.3 Data Flow Diagram
 A data flow diagram (DFD) is a graphical representation of the “flow” of data through an
information system.
 DFDs can also be used for the visualization of data processing.
First Level DFD:
Level 1 DFDs are still a general overview, but they go into more detail than a context diagram.
In level 1 DFD, the single process node from the context diagram is broken down into sub-
processes. As these processes are added, the diagram will need additional data flows and data
stores to link them together.
Fig No: 6. First Level DFD
19 | P a g e
3.6.5 Class Diagram
A class diagram represents the structure of the system. It shows set of classes, interfaces,
and relationships between them.
Fig No: 9. Class Diagram
20 | P a g e
3.6.6 Sequence Diagram
 An interaction diagram shows an interaction, consisting of a set of objects and their

relationships, including the messages that may be dispatched among them.
 A sequence diagram is an interaction diagram that emphasizes the time ordering of
messages.
 Graphically, a sequence diagram is a table that shows objects arranged along x-axis and
messages, ordered in increasing time, along the y-axis.
A. Customer Sequence Diagram
Fig No: 10.A. Customer Sequence Diagram
21 | P a g e
B. Admin Sequence Diagram
Fig No: 10.B. Admin Sequence Diagram
22 | P a g e
3.6.7 Entity-Relationship (E-R) Diagram
An entity relationship diagram (ERD), also known as an entity relationship model, is a graphical
representation that depicts relationships among people, objects, places, concepts or events within
an information technology (IT) system. An ERD uses data modeling techniques that can help
define business processes and serve as the foundation for a relational database.
Fig No: 11. E-R Diagram
23 | P a g e
CHAPTER 4
SYSTEM DESIGN
4.1 Basic Modules
Food Item Management Module: Used for managing the Food Item details.
 Confirm Order Module : Used for managing the details of Confirm Order
 Payment Module : Used for managing the details of Payment
 Category Management Module: Used for managing the information and details of
the Category.
 Customer Module : Used for managing the Customer details
 Order Module : Used for managing the Order information’s
 Login Module: Used for managing the login details
 Users Module : Used for managing the users of the system
4.2 Data Design

4.2.1 Schema Design
4.2.1.1 Table name: Admin
Field Name Data Type Constraint

Name VARCHAR NOT NULL
Email Id VARCHAR NOT NULL
Password VARCHAR NOT NULL
24 | P a g e
4.2.1.2 Table Name: Customer

Name Varchar NOT NULL
Address Varchar NOT NULL
Phone no Int PRIMARY KEY
4.2.1.3 Table Name: Food Menu

mDesc Varchar NOT NULL
mPrice Int/ Number PRIMARY KEY
Image Image NOT NULL
25 | P a g e
4.2.1.4 Table Name: Thali 1

4.2.1.5 Table Name: Tiffin

4.2.1.2 Table Name: Sabjiya

26 | P a g e
4.2.1.2 Table Name: Starter

4.2.1.2 Table Name: Add on

27 | P a g e
4.2.1.2 Table Name: Combos

4.2.1.2 Table Name: Salad

4.2.1.4 Table Name: Complaint

28 | P a g e
4.2.2 Data Structures
In computer science, a Design and Analysis of Algorithm is a particular way of organizing data
in a computer so that it can be used efficiently. It can implement on or more particular Abstract
Data Types (ADT), which are the means of specifying the contract of operations and their
complexity. In comparison, it is a concrete implementation of the contract provided by an ADT.
Data structures provide a means to manage large amounts of data efficiently for uses such as
large databases and internet indexing services. Usually, efficient data structure is the key to
designing efficient algorithms. Some formal design methods and programming languages
emphasize data structures, rather than algorithms, as the key organizing factor in software
design. Storing and retrieving can be carried out on data stored in both main memory and
secondary memory. The implementation of a data structures usually requires writing a set of
procedures that create and manipulate instances of that structure. The efficiency of data structure
cannot be analyzed separately from those operations.
4.2.3 Algorithms Design
The algorithm used for sorting in the software is Merge sort. It divides the list of records into two
equal lists and so on. After that, the sub lists are joined in the sorted manner and the final sorted
list is obtained. The Merge sort has complexity of n(logn) for all the cases. So, it requires same
time to execute irrespective of the position and value of elements. The linear search is also used
along with file handling which looks for the record in the list provided by user and then performs
29 | P a g e
the operation according to the requirement. The concept of linear search is used in insertion and
searching effectively.
4.3 User Interface Design

User Interface Design is concerned with the dialogue between a user and the computer. It is
concerned with everything from starting the system or logging into the system to the eventually
presentation of desired inputs and outputs. The overall flow of screens and messages is called a
dialogue.
The following steps are various guidelines for User Interface Design:
 The system user should always be aware of what to do next.
 The screen should be formatted so that various types of information, instructions and
messages always appear in the same general display area.
 Message, instructions, or information should be displayed long enough to allow the
system user to read them.
 Use display attributes sparingly.
 Default values for fields and answers to be entered by the user should be specified.
30 | P a g e
Login Page:
31 | P a g e
4.4 Security Issues
To make the project safer than previous one following safety mechanism are done:
1. Back up for project file is done through external hard disk and flash disk.
2. Uses antivirus to protect from attacks
4.5 Test Cases Design
This testing is a series of different tests whose primary is to fully exercise the computer-based
system. This involves:
• Implementing the system in a simulated production environment and testing it.
• Introducing errors and testing for error handling.
• The process of executing a system with the intent of finding an error.
• Testing is defined as the process in which defects are identified, isolated, subjected for
rectification and ensured that product is defect free in order to produce the quality product and
hence customer satisfaction.
32 | P a g e
• Quality is defined as justification of the requirements
• Defect is nothing but deviation from the requirements
• Defect is nothing but bug.
• Testing --- The presence of bugs
• Testing can demonstrate the presence of bugs, but not their absence
• Debugging and Testing are not the same thing!
• Testing is a systematic attempt to break a program or the AUT.
• Debugging is the art or method of uncovering why the script /program did not execute properly.
Sr. Test Case Title Description Expected Result

No Outcome
1. Successful User The login to the system Login should be Pass
Verification should be tried with the successful and the user
login assigned by the should enter in to the
admin and the correct system
password.
2. Checking the controls of Cases Verify that all the All the labels should be Pass
the Login Page labels and controls properly working
including text-boxes,
buttons, and links are
present on the Login page.
3. Checking Insert, Update This case helps to verify All data should be Pass
and Delete of data that all the data is been inserted /updated and
inserted /updated and deleted as specified
33 | P a g e
deleted as specified
CHAPTER 5
CONCLUSION AND FUTURE WORK
5.1 Conclusion
 System helps to keep all the data about customers and admin to be stored in
computer and there is no need to do paper work.
 Data is going to be preserved carefully for longer period hence proper backup is
required otherwise there is chance of losing entries.
 There are also chances that calculation error can occur which can cause huge
problem.
 Admin can add the information about new products as the user needs.
 This information can be modified, deleted as required.
 This information can be modified, deleted as required.
5.1.2 Limitations of the System

34 | P a g e
 This application is an android application so, a system with android operating system is
needed to run this application
 Data is stored in firebase database, which is real-time database. So, any update made is
overwritten.
 Adding food items is totally depend on the admin.
 User has to use the working mail id so its easy for the user to reset the password if forgotten.
 There would be problem if the application is launched in the system having operating system
less than API 24: Android 7.0 (Nougat).
 Primary internet connection is required for registration and further product booking.
 As the user authentication is based on the email id, Customer would not be able to reset the
password if proper email id is not provided.
5.1.3 Future Scope of the Project
 HFD App would be added for payment like online payment.
 Add location or tracking would be add in application.
35 | P a g e
CHAPTER 6
REFERENCES
 Professional Android™ 4 Application Development, Reto Meier, John Wiley & Sons, Inc.
2012.
 Android Application Development, Black Book, Pradeep Kothari, Kogent Learning Solutions,
DreamTech Press
 Google Android Developers - https://developer.android.com/index.html
 https://developer.android.com/index.html
36 | P a g e

Project Siddhi

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Project Siddhi

Uploaded by

Copyright:

Available Formats

HOMEMADE FOOD DELIVERY APP| 2022

1. To discuss the concept of online food delivery applications.

1.2 Purpose, Scope, and Applicability

1.3 Organization of Report

FRONTEND: - ANDROID STUDIO 3.0.1

BACKEND: FIREBASE DATABASE

4. There are some services provided by Firebase used in this project.

REQUIREMENTS AND ANALYSIS

Fig No: 1. Waterfall Model

Advantages of the Waterfall Model:

 Simple and easy to understand and use.

T his st udy is car r ied o ut t o check t he t echnic a l fe as ib i l it y, t hat is, t he

3.1 Problem Definition

3.2 Requirement Specification

3.3Planning and Scheduling

Fig No: 2.Gantt chart

3.4 Software and Hardware Requirements

3.4.1 Software Requirements

Operating System : Windows 10

User interface : HTML, CSS, JavaScript

Database : Firebase Database

Documentation Tool : Ms Office, Sublime Code Editor

Server : XAMPP Local Server

3.4.2 Hardware Requirements

RAM : 8 GB Ram or more

Hard Disk : 512 MB

Monitor : Standard Monitor

Keyboard : Standard Keyboard

Mouse : Standard Mouse

3.5 Preliminary Product Description

3.6 Conceptual Models

Fig No: 3. Use Case Diagram

3.6.2 Activity Diagram

A. Customer Activity Diagram

Fig No: 3. Customer Activity Diagram

B. Admin Activity Diagram

Fig No: 4. Admin Activity Diagram

3.6.3 Data Flow Diagram

First Level DFD:

Fig No: 6. First Level DFD

3.6.5 Class Diagram

Fig No: 9. Class Diagram

3.6.6 Sequence Diagram

 An interaction diagram shows an interaction, consisting of a set of objects and their

A. Customer Sequence Diagram

Fig No: 10.A. Customer Sequence Diagram

B. Admin Sequence Diagram

Fig No: 10.B. Admin Sequence Diagram

3.6.7 Entity-Relationship (E-R) Diagram

Fig No: 11. E-R Diagram

4.1 Basic Modules

4.2 Data Design

Field Name Data Type Constraint

Password VARCHAR NOT NULL

4.2.1.2 Table Name: Customer

Field Name Data Type Constraint

Phone no Int PRIMARY KEY

4.2.1.3 Table Name: Food Menu

Field Name Data Type Constraint

4.2.1.4 Table Name: Thali 1

Field Name Data Type Constraint

4.2.1.5 Table Name: Tiffin

Field Name Data Type Constraint

4.2.1.2 Table Name: Sabjiya