CAPSTONE PROJECT REPORT

(Project Term July-November 2019)

Yummy.com

Submitted by

Ashok Sharma Registration Number :11615486

Deepak Soni Registration Number :11615772
Subhash Singh Registration Number :11609212
Ujjwal Kumar Mishra Registration Number :11608047

Project Group Number CSERGC00096

Course Code CSE 439

Under the Guidance of

Prof. Vipin Kumar

School of Computer Science and Engineering

PAC Form

ii
 DECLARATION

We hereby declare that the project work entitled “Yummy.com” is an authentic record of our own
work carried out as requirements of Capstone Project for the award of B.Tech degree in Computer
Science Engineering from Lovely Professional University, Phagwara, under the guidance of Mr.
Vipin Kumar, during August to November 2019. All the information furnished in this capstone
project report is based on our own intensive work and is genuine.

Project Group Number: CSERGC0096

Name of Student 1: Ashok Sharma

Registration Number:11615486

Name of Student 2: Ujjwal Kumar Mishra

Registration Number:11608047

Name of Student 3: Subhash Singh

Registration Number:11609212

Name of Student 4: Deepak Soni

Registration Number:11615772

(Signature of Student 1)
Date:

(Signature of Student 2)
Date:

(Signature of Student 3)
Date:

(Signature of Student 4)
Date:
 CERTIFICATE

This is to certify that the declaration statement made by this group of students is correct to the best
of my knowledge and belief. They have completed this Capstone Project under my guidance and
supervision. The present work is the result of their original investigation, effort and study. No part
of the work has ever been submitted for any other degree at any University. The Capstone Project
is fit for the submission and partial fulfillment of the conditions for the award of B.Tech degree in
Computer Science and Engineering from Lovely Professional University, Phagwara.

Name of the Mentor: Mr. Vipin Kumar

Signature:

Designation: Assistant Professor

School of Computer Science and Engineering,

Lovely Professional University,
Phagwara, Punjab.

Date:

iii
 ACKNOWLEDGEMENT

It gives us immense pleasure to state that we have successfully accomplished the task of
completing our capstone project report. This task of ours would not have been a reality had it not
been the effortless work of team members who gave their 100% day in and day out and left no
stone unturned. We would also like to express our gratitude to our mentor and guide Mr. Vipin
Kumar for guiding us throughout this experience. His vivid expertise has been a great virtue tapped
for this accomplishment. Further, we would like to thank all those who helped us consciously or
unconsciously and our parents who supported and motivated us throughout.

Regards

iv
 Table of Content
Inner first page…………………………………………………………………………………. (i)
PAC form………………………………………………………………………………………. (ii)
Declaration…...…………………………………………………………………………………(iii)
Certificate...…...…….…………………………………………………………………………..(iv)
Acknowledgement…………………...…………………………………………..........................(v)
Table of Contents……………………...………………………………………………………...(vi)

1. INTRODUCTION 1
2.PROFILE OF THE PROBLEM 3
3. EXISTING SYSTEM 4
3.1 INTRODUCTION 4
3.2 EXISTING SOFTWARE 4
3.3 DFD FOR PRESENT SYSTEM 5
3.4 WHAT’S NEW IN THE SYSTEM TO BE DEVELOPED 7
4. PROBLEM ANALYSIS 11
4.1 PRODUCT DEFINITION 11
4.2 FEASIBILITY ANALYSIS 11
4.3 PROJECT PLAN 13
5. SOFTWARE REQUIREMENT ANALYSIS 15
5.1 INTRODUCTION 15
5.2 FUNCTIONAL REQUIREMENTS 15
5.3 NON-FUNCTIONAL REQUIREMENTS 16
6. DESIGN 18
6.1 FLOW CHART 18
6.2 PSEUDO CODE 21
7. TESTING 23
7.1 FUNCTIONAL TESTING 23
7.2 STRUCTURAL TESTING 24
v
 7.3 LEVELS OF TESTING 25
7.4 TESTING THE PROJECT 25
8. IMPLEMENTATION 27
8.1 IMPLEMENTATION OF THE PROJECT 27
8.2 CONVERSION PLAN 28
8.3 POST-IMPLEMENTATION AND SOFTWARE MAINTENANCE 29
9. PROJECT LEGACY 32
9.1 CURRENT STATUS OF THE PROJECT 32
9.2 REMAINING AREAS OF CONCERN 32
9.3 TECHNICAL AND MANAGERIAL LESSONS LEARNT 32
10. USER MANUAL 34
11. SOURCE CODE OR SYSTEM SNAPSHOTS 35
12. BIBLIOGRAPHY 43

vi
1. INTRODUCTION
Our University, Lovely Professional University has huge strength of students.
University gives One hour to finish our lunch but because of the huge strength of the university it
takes a lot of time to get the lunch. Teachers and students also have to wait while their meal is
cooking. Because of the crowd both students and teachers face problem. Teachers and students
also have to wait while their meal is cooking and shopkeeper do not have any idea that on this
particular day how many students will be having lunch.

So here our website takes place through this website food booking will be done to make user’s life
easy. From this website user can take many benefits to get their food on time and also, they can
utilize their one hour of lunch. By using this website user will have to only enter the timing when
and from where they want food, they can have their food on that timing. Users of this website will
be different from other crowd in the process of taking food.

This website will be also having the function where shopkeeper of respective shop will be able to
change menu on any particular day. For every user’s identity our website will have a unique token
number which will expire after 1 minutes of given time the user will not be able to pick-up his/her
order.

Requesting online food was intended for greater adaptability and execution, any page or applicati
on ensures that the system has enough route function through the image data or noteworthy logo
to manage customers like undergraduates and educators seeking the means to complete the reque
sting nutrition process, apart from that we expected to handle a huge number of requests from the
students and teachers.

Basically, this web-based requesting venture outline how to administer for good execution and
better administrations for the University clients. Everywhere throughout the world, the
nourishment conveyance as of now have represents the 83 million, the one percent is structure
complete nourishment advertise and including the 4 percent food shops and cheap food chains, in
many mature areas, this number of growth rate will continually to increase at 3.5 percentage in the
next four years, by far, the traditional category which is waiting for the restaurant to bring the food
to the customer has stands 90 percentage, but almost three-quarters are still using by phone. In this
surprising pace of web-based requesting may even now shroud some hindrance or issue which we
have to deal with it, for example, site costs, framework cost, security and misrepresentation,
protection laws, PC morals and publicizing cost. In any case, all present requesting sites have
pretty much issues that reason various gatherings of individuals to experience a few issues when
utilizing these applications. In this undertaking we will plan a site that take care of the issues of
the Students just as the instructor of our University.

2
2. PROFILE OF THE PROBLEM

As every University who has big strength, our University is also having huge strength of
students. University gives One hour to finish our lunch but because of the huge strength of the
university it takes a lot of time to get the lunch. Teachers and students also have to wait while their
meal is cooking. Because of the crowd both students and teachers face problem. Teachers and
students also have to wait while their meal is cooking and shopkeeper do not have idea that on this
particular day how many students will be having lunch.

This is the problem which needs solution so this is where our website comes in picture to
solve this problem.

3
3. EXISTING SYSTEM
3.1 INTRODUCTION
To make new things firstly we have to look what websites are available and what is
the drawback and qualities of that websites. We will examination the present websites, for that we
have chosen 3 applications or sites: Swiggy, Zomato, Uber Eats. Each site offers administration to
the user of particular part. We investigation the user's fulfillment with these websites. We
additionally plan to think about the qualities and drawbacks inside and out and started code for
development. We will basically three aspects of websites they are

3.2 USABILITY

• Accessibility - For certain individual users who have a few defects, the plan of items,
gadgets, services, or situations.
• Efficiency – In this we will check how comfortably, quickly and accurately users can
perform the functionality of the website.
• Memorability - Regardless of whether users of this website can recall how to order it
again after their order.
• Learnability – It tells us the straightforwardness with which users are capable and figure
out how to finish their order very effectively.
• Errors – It tells us about the errors while user perform ant task on website.

3.2.1 ACCESSABILITY

Every one of these kinds of website offer a few clients removing administrations, yet they
are not able to gather what user want which we can consider as their feedbacks. Making a food
delivery site targets to make what our user might want to eat, and when he needs to eat their food,
for this, it is critical to give some advancement to the website.

3.2.2 EFFICIENCY
In this we will try to fulfill that It is imperative to make a website that can control the
user to have their food. As we all know Adaptable that implies Create functionality that can be
introduced in various types for more straightforward design, without losing structure. Utilize an
arrangement or singe might be helpful.
4
3.2.3 MEMORABILITY
For the websites which gets request, the fact is that the website is extremely coherent,
so for users, they just need to pursue the essential requesting rationale, they can undoubtedly recall
how to utilize this website at whatever point they visit the website next time. This guideline
underlines whether a user can recollect the application's means after different employments.

3.2.4 LEARNABILITY
The rule of learnability alludes to that when a customer first uses this application, the
user can clearly get the strategy for utilizing this website or give an unmistakable rule to the user
inside the website to lead the user to acquaint with and totally utilize this framework to complete
what the individual in question needs to do. It is the rule for the customers who are curious about
this sort of website.

3.2.5 ERRORS
To lessen the client's odds of making blunders in utilizing the website, it is imperative to
pursue the propensities and rationale of most users what they need in their site which they are
utilizing at configuration time, and originators ought to likewise diminish the variables that may
instigate clients to commit errors. This pointer likewise influences productivity to a limited degree,
and if some nonsensical plans lead to a higher likelihood of errors made by the client, it can
likewise prompt an uncommon decrease in proficiency.

3.3 DFD FOR PRESENT SYSTEM

Data flow-oriented technique defines that the significant information things which is sent
by client is to be dealt with by a website must be first recognized and afterward the preparing
required on these information things to deliver the ideal yields ought to be dictated by the site. The
DFD which is a straightforward graphical formalism that can be utilized to speak to an application
regarding input information to the framework, different handling did on this information and the
yield created by the application.

The important symbols used for making DFD’s are:

5
A process is represented by circle.

Figure 3.1: Symbol of process

An external entity is represented by rectangle.

Figure 3.2: Symbol of External Entity

A source of the system data is represented by square.

Figure 3.3: Symbol of Source

3.3.1 DFD FOR FOOD MANAGEMENT

Figure 3.4: DFD of Food Management

6
 3.3.2 DFD FOR CUSTOMER

Figure 3.5: DFD For Customer

3.4 WHAT’S NEW IN THE SYSTEM TO BE DEVELOPED

As every website will be the center of attraction if it is having new feature in it.
This new feature is called as the novelty of the project.

So, this website will be having a unique feature which is that every shopkeeper will be able to
update the menu on every day bases. For example, menu is having thali in it and shopkeeper
makes new vegetables daily so he can update that today what is being made by him. From this
new feature user of this website will be having knowledge what will made in which shop. So,
they can book accordingly what they like and what they want to have today in their meal Data
Flow diagram for customer:

7
3.4.1 DATA FLOW DIAGRAM OF YUMMY.COM

Figure 3.6: DFD of Yummy.com

8
3.4.2 DATA FLOW DIAGRAM FOR CUSTOMER

Figure 3.7: DFD for Customer

9
3.4.2 DATA FLOW DIAGRAM FOR SHOP OWNER

Figure 3.8: DFD for Shop Owner

10
4. PROBLEM ANALYSIS

Our University has huge strength of students. University gives One hour to finish
our lunch but because of the huge strength of the university it takes a lot of time to get the lunch.
Teachers and students also have to wait while their meal is cooking. Because of the crowd both
students and teachers face problem. Teachers and students also have to wait while their meal is
cooking and shopkeeper do not have idea that on this particular day how many students will be
having lunch.

4.1 PRODUCT DEFINITION

Today, web is loaded with sites entrance that helps a large number of their users to
discover important information supportive to them in their field. You can discover thousands for
online entrances to look for food and their booking. Gateways have made crafted by the clients
especially simple and pleasant. Clients can now rapidly locate the sort of information that they
need from their separate gateway and in this way making their work simple with little endeavors
and greater fruity outcomes. This undertaking will do likewise and satisfy user's necessity.

From this product which is a website user can take many benefits to get their food on
time and also, they can utilize their one hour of lunch. By using this website user will have to
only enter the timing when and from where they want food, they can have their food on that
timing. This website will be also having the function where shopkeeper of respective shop will
be able to change menu on any particular day.

4.2 FEASIBILITY ANALYSIS

The feasibility study is a significant stage during the improvement of any

undertaking, its will likely decide if the task is possible or not. Our capstone project is tied in with
building a web application, which intention is to help individuals in picking and booking their
preferred nourishment from shops, and enabling to retailer to more readily speak with their users.

4.2.1 TECHINAL FEASIBILITY

It is to comprehend in the event that it is conceivable to finish the task with the present
innovations. This application is going to utilize many programming dialects and structures so as
11
to guarantee a decent client experience for the end client, just as receiving great coding rehearses
for the engineer. The structure of the application will comprise of a backend and a frontend. The
backend will be executed utilizing PHP, its motivation is to deal with database questions and
confirmation. The frontend ought to be finished utilizing HTML, CSS, and JAVASCRIPT.

System is compatible with all window system with proper internet connection. System is
user friendly.

• Less RAM is requiring.

• Less memory is used.

4.2.2 ECONOMICAL FEASIBILITY

The economic attainability is fundamental to realize the monetary allowance required

for the completion of the website, and how much budget it is ready to create once discharged.
The essential spending plan for this undertaking is low, the advancements required for this
venture are allowed to utilize.

• It is a money saving advantage investigation keeping in see the framework is financially

achievable. It is so because of following Points.

• The advantages in decreasing expense are in type of sparing of administrative work.

• Different costs brought about to actualize the framework are installment of information
section administrator, a tad bit of upkeep required for equipment and programming from
time to keep up consistency and proficiency.

4.2.3 OPERATIONAL FEASIBILITY

Proposed framework is useful just in the event that they can be transformed into data
framework that will meet the client's necessities.

• As the website is easy to use, all through the website is all around connected and
affirmed by the client's needs greater office that can be gives.

12
 • The website has been planning remembering the user's present prerequisites change in
future. The proposed framework won't make any damage the user however rather, it will upgrade
the outcome in a superior way.

4.2.4 BEHAVIORAL FEASIBILITY

As it is anything but difficult to store information and access information, user will act
decidedly to this venture. It will be effectively satisfactory by the client as is gives a GUI
situation that make it easy to use.

4.2.5 TEMPORAL FEASIBILITY

It is essential to ensure that it is conceivable to finish the undertaking on schedule. There

would be an advancement stage in which I would need to code the application with the picked
devices. Likewise, there will be a learning stage, during which, I should find out about the
advancements that I would use for this undertaking. Since I am as of now acquainted with a portion
of these advances, because of the courses I have finished and to my University experience, I will
just concentrate on the ones I don't have the foggiest idea.

4.3 PROJECT PLAN

Project plans are produced as management activities commences. It represents the

processes and tasks that are to be conducted, people who will do work, and the mechanisms
to assess the risks, control change, and evaluate quality.

To make this website, we followed Evolution Model. In which our requirements can change
while make this project only.

13
4.3.1 GANTT CHART

The complete Gantt Chart of our work flow is as follows:

Table 1: Gantt Chart

14
5. SOFTWARE REQUIREMENT ANALYSIS

Today, web is brimming with sites entryway that helps a large number of their
clients to discover significant information supportive to them in their field. You can discover
thousands for online entries to scan for nourishment and their booking. Gateways have made
crafted by the clients especially simple and pleasant. Clients can now rapidly locate the sort of
information that they need from their individual entrance and in this way making their work simple
with little endeavors and greater fruity outcomes. This project will do likewise and satisfy user's
necessity.

5.1 CUSTOMER/USER PROFILE:

In this project there will be two types of users. One will be the customers who
will book the food and second will be the owner of food shop. They can update their profile
wherever they want and can perform use different types of function on this platform. User will be
able to use different types of function as every website provide like user will be able to signin and
signup. User can upload their photo on the profile portion as well as he or she will be able to the
data which is provided by the user on any point whenever he or she wants.

5.2 FUNCTIONAL REQUIREMENTS:

Functional Requirements characterize an element of a framework and segment,

where a capacity is portrayed as a detail of conduct among information sources and yields.
Practical prerequisites may include figuring, specialized detail, information control and other
explicit usefulness that characterizes what a framework should do. Conduct necessity depicts every
one of the situations where the framework utilizes the practical prerequisite, this is caught being
used cases. Useful necessities are upheld by non-utilitarian prerequisite, which force requirements
on the plan and execution.

5.2.1 USER CAN BOOK A UNIQUE TOKEN:

If you are in a queue and you want to be recognized then you need something
from which you can be recognized. This Website will generate a unique token for you. By this

15
token you will be recognized by the owner of food shop. This token will be generated by the
combination of your email and mobile number.

5.2.2 OWNER OF FOOD SHOP WILL BE ABLE TO CHANGE MENU ON EVERYDAY

BASES

As an owner of food shop, you do not want to repeat the same menu of food on
everyday.so we have a great facility to update your delicious menu on everyday bases. So, you can
make delicious food every day and can attract the customer. Also, you will have a great chance to
earn profit as much as you will be capable of.

5.2.3 USER CAN SEE THE MENU EVERY DAY:

We have so much facilities for shop owner and it will not be nice for their
customer if you do not provide this type of services to them.so user can see the menu whenever
they will think to order food. They can choose their choice of food as well as their choice of shop.

5.2.4 USER CAN GIVE THE FEEDBACK OF FOOD:

Everything on every moment need improvement because this make things from
good to better. So, this website will give you option to give feedback of food as well as for this
website because we also need improvement in our website. Feel free to give feedback and rating
to food so they can also improve their quality and quantity of food.

5.3 NON- FUNCTIONAL REQUIREMENTS:

Non-Functional Requirements are the requirements that specifies criteria that

could be used to judge what system do, rather than specific behavior. Non-Functional
Requirements are contrasted with functional requirement that defines specific behavior function.
The plan for implementing functional requirements are detailed in the system design. The plan for
implementing non-functional requirements are detailed in the system architecture, because it is
usually architecturally significant requirement. Functional requirement defines what a system is
supposed to do and Non-Functional requirements define how a system is supposed to be.

16
5.3.1 PERFORMANCE PARAMETERS:

Performance parameters include the response time of the system utilization level
of both static and volumetric types throughput. These parameters are standardized so the systems
have to follow them. For example, if the performance of a website is not up to the mark if it is
giving slow response to the user and it is taking time while loading this website will be considered
as bad performance. We will consider a website good if it is giving good response and also taking
no time while loading so user can enjoy this website while booking and generating their token.

5.3.2 SECURITY:

Safety efforts ought to be implanted in the framework to guarantee that the records
present in the framework are secure and no unapproved staff can get to them. As everyone wants
their data and personal information in safe hand. No one wants their data to be misused by someone
for their benefits that’s why security is must for any project. This project will also take care of the
security of the information which will be given by the user. We assure that user’s data will not be
leaked by any point of time. User’s experience will be awesome on this website.

5.3.3 MAINTAINABILITY:

The framework ought to be planned so that they can be overhauled and kept up on an
occasional premise. Everyone likes new things on everyday if some improvement is not their user
will feel bored with user interface of this website. So. we as a developer will try to provide the
improvement as much as we will be able to do so they will not will with this project.

5.3.4 ENVIRONMENT REQUIREMENT:

It is one of the lawful and administrative prerequisites also. The framework ought to
be structured so that its assembling and activity doesn't influence the earth in negative manner. As
a developer you have to take care of many things. Which will include the environment of the
website we can assure that the designing of this will not affect any other website who will be our
competitors in negative way. We will not use such kinds of negative things and also will not
promote it.

17
6. Design
6.1 FLOW CHART
The Flow chart of any website shows the flow of the website. A flowchart is a type
of diagram that represents a workflow or process. A flowchart can also be defined as a
diagrammatic representation of an algorithm, a step-by-step approach to solving a task.This is very
important component while making website it helps developer to understand the requirement of
any website.
6.1.1 OVERVIEW
6.1.1.1 START/END SYMBOL

The terminator symbol marks the starting or ending point of the System. It usually
contains the word Start or End.

Figure 6.1: Start/End Symbol

6.1.1.2 ACTION OR PROCESS SYMBOL

A box can represent a single step (add two cups of flour), or an entire sub-process
(make bread) within a larger process.

Figure 6.2: Action Symbol

6.1.1.3 DECISION SYMBOL

A decision branching point. Lines representing different decision from different

points of the diamond.

18
 Figure 6.3: Decision Symbol
6.1.1.4 INPUT/OUTPUT SYMBOL
Represents material or information entering or leaving the system, such as
customer order (input) or a firms (output).

Figure 6.4: Input/ Output Symbol

6.1.1.5 ARROWS

It indicates the direction and order of program execution.

Figure 6.5: Arrow Symbol

19
6.1.2 FLOWCHART FOR REGISTRATION

Following Figure illustrate the flow of Registration activity

Figure 6.6: Flowchart of Registration

20
6.1.3 FLOWCHART FOR LOGIN MODULE

Figure 6.7: Flowchart of Login Module

6.2 PSEUDO CODE

Before you keep in touch with one bit of PC code, you need to recognize what the program
should do. Before you keep in touch with one line of code in any language, it is a smart thought to

21
compose it in a basic path first to guarantee you have included all that you need. The most ideal
approach to set this up is by utilizing pseudocode.

Pseudocode is a straightforward method for composing programming code in English. Pseudocode

isn't real programming language. It utilizes short expressions to compose code for programs before
you really make it in a particular language. When you comprehend what the program is about and
how it will work, at that point you can utilize pseudocode to make proclamations to accomplish
the necessary outcomes for your program.

6.2.1. PSEUDO CODE OF REGISTRATION PROCESS

Input: Enter Correct detail for registration Process

Output: Check user detail is correct if yes then save into database otherwise send
error message to user.

6.2.2 PSEUDO CODE OF LOGIN MODULE

Input: Select account type and enter login account Email Id and password.

Output: Check email and password if correct credentials then send to respective
home page otherwise show relative error.

If the login account is correct then the user can access the functional modules
provided by the system by redirecting it to the home page of the system.

If the user is not registered for accessing the system then the user notified through a message saying
“Setup your account first”.

If the user has the successful access to the database then he can repeatedly access the functionalities
of the system and access all the data of food shops.

After all this can logout at any time.

22
7.Testing

7.1 FUNCTIONALITY TESTING

Functional Testing is a quality confirmation (QA) process and a sort of discovery testing that
puts together its experiments with respect to the determinations of the product part under test.
Capacities are tried by sustaining them input and looking at the yield, and inner program structure
is once in a while (dislike in white-box testing). Useful Testing for the most part portrays what the
framework does. Test for – every one of the connections in site pages, database association,
structures utilized in the pages for submitting or getting data from client, Cookie testing.

7.1.1 CONNECTIVITY OF ACTIVITIES

• Test the outgoing links from all the pages from specific domain undertest.

• Test all internal links.

• Test links jumping on the same pages.

. • Link checking, check for broken links in all above-mentioned links.

7.1.2 TEST FORMS IN ALL PAGES

Structures are the indispensable piece of any site. Structures are utilized to get data
from clients and to keep connection with them. In this way, things that ought to be kept an eye
on these structures are-First check every one of the approvals on each field.

• Check for the default values of fields.

• Wrong inputs to the fields in the forms. Options to create forms if any, form delete.

• View or modify the forms.

We should take case of the task as of now we are chipping away at, in this undertaking we have
clients and client login steps. Each login step is diverse however subject to different steps. In this
way, login stream ought to get executed effectively. There are distinctive field approvals like

23
client Ids, secret word approvals. Every one of these approvals ought to get checked in manual or
robotized web testing.

7.2 STRUCTURAL TESTING

7.2.1 STRUCTURAL TESTING TECHNIQUES:

7.2.1.1 STATEMENT COVERAGE

This strategy is planned for practicing all programming explanations with negligible tests.

7.2.1.2 BRANCH COVERAGE

This procedure is running a progression of tests to guarantee that all branches are tried at
any rate once.

7.2.1.3 PATH COVERAGE

This procedure relates to testing every conceivable way which implies that every
announcement and branch are secured.

7.2.2 ADVANTAGES OF STRUCTURAL TESTING

• Forces test designer to reason cautiously about execution.

• Reveals blunders in "covered up" code.
• Spots the Dead Code or different issues regarding best programming practices.

7.2.3 DISADVANTAGES OF STRUCTURAL BOX TESTING

• Expensive as one needs to invest both energy and cash to perform white box testing.
• Every probability that couple of lines of code is missed coincidentally.
• In-profundity information about the programming language is important to perform white
box testing.

24
7.3 LEVELS OF TESTING
7.3.1 UNIT TESTING
It is a testing of the product testing process where singular units/parts of a product/framework
are tried. The object is to approve that every unit of the product executes as planned.
7.3.2 INTEGRATION TESTING
It is a testing of the product testing process where singular units are joined and tried as a
gathering. The reason for this degree of testing is to uncover blames in the association between
incorporated units.
7.3.3 SYSTEM TESTING
It is a testing of the product testing process where a total, coordinated framework/programming
is tried. The reason for this test is to assess the framework's consistence with the predefined
necessities.
7.3.4 ACCEPTANCE TESTING
It is a degree of the product testing process where a framework is tried for adequacy. The
motivation behind this test is to assess the framework's consistence with the business prerequisites
and evaluate whether it is worthy for conveyance.

7.4 TESTING THE PROJECT

7.4.1 ALPHA TESTING

Under Alpha testing, Our Project was disseminated among our companions to test and
share their experience of the site we made. Following seven days of testing, the accompanying
Problems or bugs were accounted for.

• Under the Choose food category, all food was not showing. There was a problem in the
connectivity of the data on our food page. This was resolved by us by changing the query
that we were using earlier.

• No Display of Image of some food while ordering. There was a problem in the linking
of the images. We resolved this.

25
 • In the Token ID section, there was a problem with the token key which was used to
generate the Token ID. This issued was handled by us by replacing the dynamically
generated key.

7.4.2 BETA TESTING

After fruition of alpha testing and enhancements done on the task, the project was handed
to our supervisor. He demanded for the addition of certain modules that were a simpler sign in
for the shop owner and the users.

• A better and brighter view of the layout of the system.

26
8. IMPLEMENTATION
8.1 IMPLEMENTATION OF THE PROJECT
Task execution is where dreams and plans become reality. This is the obvious end result,
in the wake of assessing, choosing, visioning, arranging, applying for assets and finding the money
related assets of a task. Project is

This is the process whereby Project inputs are converted to project outputs.

• Putting in real life the exercises of the venture. Task usage is where dreams and plans
become reality
• Putting into training what was proposed in the task proposition into the real venture.
• Management of the venture or executing the task aims.
• Project Implementation stage includes venture actuation and undertaking activity.

This implies making plans to have the undertaking begun. In this way, every one of the
prerequisites required for making the product helpful and address every one of the issues of our
group was accumulated by having sittings with the customer. The achievability study was made
about the undertaking that whether the venture requested by our group was conceivable to
actualize or not. At that point, in like manner the language or the stage that was required for the
improvement of the undertaking was chosen with the goal that the most basic, secure, powerful
stage ought to be picked so all that what was required by the customer can be actualized by the
designers effectively.

8.1.1 PROJECT ACTIVATION

Project initiation basically implies making game plans to have the undertaking
begun. It is the fundamental or establishment phase of undertaking execution and it includes
the coordination and assignment of assets to make the task operational.

The following activities are undertaken during project activation

• Establishment of Project Implementation Units (PIUs)

• Recruitment of project supervisor

27
 • Tendering and obtainment of machines, hardware and different providers.
• Preparation of emergency courses of action.
• Designation of the inner undertaking experts for basic leadership.
• code of direct Setting up linkages with the objective gathering.
• Location and arrangement of locales.

8.1.2 PROJECT OPERATION

This is useful administration of an undertaking. Here, venture inputs are changed

into yields to accomplish prompt destinations.

In this the fundamental prerequisites being taken from the customer, at that point those were
actualized into the useful structure by giving the contribution to the framework and acquiring
the ideal yield from the framework. Finally, the output that was desired by our team was
made to happen.

8.2 CONVERSION PLAN

This area of the framework transformation plan depicts the general change
procedure. The way to deal with changing over the present framework which is manual to
the robotized framework is one that outcomes in another framework database is both far
reaching and simple. A progression of robotized strategies is joined to meet the general
objectives of the change procedure for a complete and legitimate framework for the
association, these objectives are accomplished through a helpful, effective, and
straightforward approach embraced by the designers. The achievement the transformation
system is dependent upon confirmation that various obviously distinguished essential
conditions are met before change exercises start at the testing level.

28
 Table 1: Conversion Plan

8.3 POST-IMPLEMENTATION AND SOFTWARE MAINTENANCE

8.3.1 SOFTWARE MAINTENANCE

Programming upkeep is done to address deficiencies, improve execution, or adjust a product

framework to another condition. Software must be kept up when:

The reality the software models changes,

29
 • New usefulness is included.
• is simpler to change programming, equipment.
• Software must be refreshed to run on.
• Improved equipment or with improved.

There are several types of software maintenance.

They are:

Table 2: Types of Maintenanace

The maintenance that will be provided to the user after the getting of the project will be:

• The rectification of the modules that won't work as indicated by the

requirements of client.
• The upkeep of the database will be given to the client now and again.
• The expansion of the modules will be done when the client's need will develop.
The viability of the framework will be enhanced the auspicious premise.

30
A Post-Implementation Review is led in the wake of finishing the project. Its motivation is to
assess whether project targets were met, to decide how adequately the undertaking was run, to
learn exercises for the future, and to guarantee that the association gets the best conceivable
profit by the task.

8.3.2 DID THE PROJECT FULLY SOLVE THE PROBLEM THAT IT WAS DESIGNED
TO ADDRESS?

The system after being developed fully was handed over to the similar users and
the reviews were taken from them. After concentrating on those reviews the addition and
updating were done on the system and then the project was handed over to the out supervisor
for the review purpose and also the system after being developed was compared with the
SRS document that developed during the start of the project so as to ensure all the
requirements asked down by our team to be having given the desired output from the system.

8.3.3 WHAT LESSONS DID WE LEARN THAT WE CAN APPLY TO FUTURE

PROJECTS?

• To start the work on implementation at the earliest possible so that more functions can be
added to system to even make the user/client fully satisfied with the system.
• To work in a group of developers, so that the work handling tasks can be completed at the
required time frame by the individual developers so that the task of the other developer is
not hampered.
• To have the timely reviews of the user so that the finality being asked by the user is
added at the earliest possible time, so that no more troubles are faced afterwards.

31
9. PROJECT LEGACY
9.1 CURRENT STATUS OF THE PROJECT
The current status of the Website is that the system is fully functional according to the
requirements being listed by our team during the meeting period. The changes were made
into the system after the testing phase so that the system can meet up the needs of the user to
the fullest possible way it can.

But still the updating and maintenance will be provided to the website time to time. All
modules of the project are developed. Designing is completed and made quirky for the user
to get more user experience. All plug-in is checked, food images are updated and cropped
according to the size described in the website.

9.2 REMAINING AREAS OF CONCERN

• Customer care service will be provided.
• Problem FAQs would be provided for better self-solution.
• User rating will be added to give the review of food shops.

9.3 TECHNICAL AND MANAGERIAL LESSONS LEARNT

9.3.1 TECHNICAL

From this project we got the concept in depth of web development. In web
development we used HTML, CSS, JS and PHP so we got the knowledge in depth of this
language. We learnt theoretical concept of this language and how to use them practically.

9.3.2 MANAGERIAL
• Learnt Team Management.
• Learnt how to manage various circumstances when stuck during the coding and the
planning part.
• Learnt how to function in gathering of engineers.
• Learnt to appropriate errands to individuals.
• Learnt about the authority quality

32
 • Learnt about the product abilities that must be available in an architect to be a decent
undertaking director.

9.3.2.1 LEARNING ABILITY

During the underlying period of the item we are simply having the essential
information about the innovations. Be that as it may, during the advancement of the task we
as a rule examine about the advances utilized in the venture with our instructor and
companions who are working in the fields of site improvement. To satisfy our errand, we
began perusing from the sites and from the book about the methods we are utilizing in the
item. By this we adapted loads of new systems which are going to help us later on.

9.3.2.2 TEAM WORK

We formed the task into the gathering of four individuals. In this way, we came to
think about how we can regard the recommendation of the gathering individuals and the
morals to do work in the group. This will help us later on when we are working in the
gatherings.

9.3.2.3 PUNCTUALITY

The venture which we created it was our plan to make this undertaking and we
have to pursue the prerequisites of the customer to build up the item. While building up the
task we came to think going to regard the significance of the time as we have to convey the
item in the characterized timespan.

33
10. User Manual

10.1 INSTALLING THE APPLICATION

• Proper internet Connection.

• Smartphone or Laptop
• Minimum hardware configuration of 512 MB RAM and 1 GB internal storage.

10.2 ASSESSING THE APPLICATION

There will be 3 modes to use application

• Existing User
• New user
• Shop Owner as user
10.3 COPYRIGHT ISSUES

Copying content or idea of the application is strictly prohibited and use of any content
from the web application will be considered.

34
11. Source Code or System Snapshots
11.1 HOME PAGE

11.1.1 CODE OF HOME PAGE

<?php
session_start();
?>

<html>

<head>
<title> Home | Yummy.com </title>
</head>

<link rel="stylesheet" type = "text/css" href ="css/bootstrap.min.css">

<link rel="stylesheet" type = "text/css" href ="css/index.css">

<body>

<button onclick="topFunction()" id="myBtn" title="Go to top">

<span class="glyphicon glyphicon-chevron-up"></span>
</button>
<script type="text/javascript">
window.onscroll = function ()
{
35
 scrollFunction()
};

function scrollFunction() {
if (document.body.scrollTop > 20 || document.documentElement.scrollTop > 20) {
document.getElementById("myBtn").style.display = "block";
} else {
document.getElementById("myBtn").style.display = "none";
}
}

function topFunction() {
document.body.scrollTop = 0;
document.documentElement.scrollTop = 0;
}
</script>

<nav class="navbar navbar-inverse navbar-fixed-top navigation-clean-search"

role="navigation">
<div class="container">
<div class="navbar-header">
<button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-
target="#myNavbar">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand" href="index.php">Yummy.com</a>
</div>

<div class="collapse navbar-collapse " id="myNavbar">

<ul class="nav navbar-nav">
<li class="active" ><a href="home.php">Home</a></li>
<li><a href="aboutus.php">About</a></li>
<li><a href="contactus.php">Contact Us</a></li>

</ul>

<?php
if (isset($_SESSION['login_user1'])) {
?>

36
 <ul class="nav navbar-nav navbar-right">
<li><a href="#"><span class="glyphicon glyphicon-user"></span> Welcome
<?php echo $_SESSION['login_user1']; ?> </a></li>
<li><a href="myrestaurant.php">MANAGER CONTROL PANEL</a></li>
<li><a href="logout.php"><span class="glyphicon glyphicon-log-
out"></span> Log Out </a></li>
</ul>
<?php
} else if (isset($_SESSION['login_user2'])) {
?>
<ul class="nav navbar-nav navbar-right">
<li><a href="#"><span class="glyphicon glyphicon-user"></span> Welcome
<?php echo $_SESSION['login_user2']; ?> </a></li>
<li><a href="foodlist.php"><span class="glyphicon glyphicon-
cutlery"></span> Food Zone </a></li>
<li><a href="cart.php"><span class="glyphicon glyphicon-shopping-
cart"></span> Cart
(<?php
if (isset($_SESSION["cart"])) {
$count = count($_SESSION["cart"]);
echo "$count";
} else
echo "0";
?>)
</a></li>
<li><a href="logout.php"><span class="glyphicon glyphicon-log-
out"></span> Log Out </a></li>
</ul>
<?php
}
else {
?>

<ul class="nav navbar-nav navbar-right">

<li><a href="#" class="dropdown-toggle active" data-toggle="dropdown"
role="button" aria-haspopup="true" aria-expanded="false"><span class="glyphicon glyphicon-
user"></span> Sign Up <span class="caret"></span> </a>
<ul class="dropdown-menu">
<li> <a href="customersignup.php"> User Sign-up</a></li>
<li> <a href="managersignup.php"> Manager Sign-up</a></li>

</ul>
</li>

37
 <li><a href="#" class="dropdown-toggle active" data-toggle="dropdown"
role="button" aria-haspopup="true" aria-expanded="false"><span class="glyphicon glyphicon-
log-in"></span> Login <span class="caret"></span></a>
<ul class="dropdown-menu">
<li> <a href="customerlogin.php"> User Login</a></li>
<li> <a href="managerlogin.php"> Manager Login</a></li>

</ul>
</li>
</ul>

<?php
}
?>

</div>

</div>
</nav>

<center> <h1>Choose Your Block</h1></center>

<br>

<div class="wide2">

<div class="col-xs-3 box" >

<img src="images/locationx.png" height="200px" width="200px" style="border:

#265a88 dashed thin">
<center><a class="btn btn-success btn-lg" href="customerlogin.php" role="button" >
Block 34 </a></center>
</div>

<div class="col-xs-3 box" >

<img src="images/locationx.png" height="200px" width="200px" style="border:
#265a88 dashed thin">
<center><a class="btn btn-success btn-lg" href="customerlogin.php" role="button" >
Apartment </a></center>
</div>

<div class="col-xs-3 box" >

<img src="images/locationx.png" height="200px" width="200px" style="border:
#265a88 dashed thin">

38
 <center><a class="btn btn-success btn-lg" href="customerlogin.php" role="button" >
Block 55 </a></center>
</div>
<div class="col-xs-3 box">
<img src="images/locationx.png" height="200px" width="200px" style="border:
#265a88 dashed thin">
<center><a class="btn btn-success btn-lg" href="customerlogin.php" role="button" >
Campus Cafe </a></center>
</div>

</div>

<br/>
<script type="text/javascript" src="js/jquery.min.js"></script>
<script type="text/javascript" src="js/bootstrap.min.js"></script>

</body>

<?php include_once 'footer.php';?>

</html>

11.2 SIGN UP AS USER

39
11.3 LOGIN PAGE

11.4 BLOCK PAGE

40
11.5 FEEDBACK PAGE

11.6 CART PAGE

41
11.7 PAYMENT PAGE

42
12. BIBLIOGRAPHY
12.1 BOOKS

• HTML5 BLACK BOOK by KOGENT LEARNING SOLUTIONS INC.,

DREAMTECH PRESS
• PROGRAMMING PHP by KEVIN TATROE, SHROFF/O'REILLY
12.2 WEB LINKS

• YouTube (www.youtube.com)

• GITHUB (www.github.com)
• PHPtPoint (www.phptpoint.com/)
• W3Schools(www.w3schools.com/)

43