Contents

Chapter 1: Introduction.............................................................................................................1

1.1Objectives........................................................................................................................2

1.2Problem Statement:.........................................................................................................2

Chapter 2: Requirements of the analysis of the system.............................................................3

Functional Requirements......................................................................................................3

2.1 Feasibility Analysis.........................................................................................................4

2.2 Hardware and Software Requirements............................................................................5

0........................................................................................................................................8

2.4 The Web Ordering System..........................................................................................9

2.4.1Menu Management System.......................................................................................9

2.4.2 Order Retrieval System..........................................................................................10

2.4.3 Web Ordering System............................................................................................10

2.5 Non-functional Requirements.......................................................................................11

2.6 System Evolution..........................................................................................................12

CHAPTER 3: SYSTEM DESIGN..........................................................................................14

3.1 Introduction..................................................................................................................14

MVC Design pattern................................................................................................................14

3.2 System Flowchart.........................................................................................................15

3.3 Context Diagram...........................................................................................................16

3.4 Level 1: Data flow Diagram..........................................................................................18

3.5 ER Diagram..................................................................................................................18

Chapter 4: Coding...................................................................................................................19

4.1 Model............................................................................................................................19

4.2 Header..............................................................................................................................27

4.3Signup................................................................................................................................31

CHAPTER 5: TESTING..............................................................................................................34
 5.1 Introduction..................................................................................................................34

5.2 Testing strategies..........................................................................................................35

5.3 Login Screen..................................................................................................................35

CHAPTER 6: TEST REPORT...................................................................................................41

6.1 Test Reports..................................................................................................................41

6.2 User Documentation.....................................................................................................42

Chapter 7: Conclusion.............................................................................................................43

7.1 Conclusion of the project..............................................................................................43

7.2 Limitations....................................................................................................................43

7.3 Future enhancements of the project............................................................................43

REFERENCE.............................................................................................................................45
 Chapter 1: Introduction
Food ordering system is an application which will help restaurant to optimize and

control over their restaurants. For the waiters, it is making life easier because they

don’t have to go kitchen and give the orders to chef easily. For the management point

of view, the manager will able to control the restaurant by having all the reports to

hand and able to see the records of each employees and order. In today’s age of fast

food and take-out, many restaurants have chosen to focus on quick preparation and

speedy delivery of orders rather than offering a rich dining experience. Until very

recently, all of these delivery orders were placed over the phone, but there are many

disadvantages to this system. First, the customer must have a physical copy of the

restaurant’s menu to look at while placing their order and this menu must be up to -

date. While this expectation is not unreasonable, it is certainly inconvenient.

The orders are placed using strictly oral communication, which makes it far

more difficult for the customer to receive immediate feedback on the order they have

placed. This often leads to confusion and incorrect orders. The current system is also

inconvenient for the restaurant itself, as they must either have a dedicated staff

member to answer the phone and take orders, or some employees must perform

double-duty, distracting them from their regular tasks.

Menu, complete with all available options and dynamically adjusting prices

based on the selected options. After making a selection, the item is then added to their

order, which the customer can review the details of at any time before checking out.

This provides instant visual confirmation of what was selected and ensures that items

in the order are, in fact, what was intended.

1
 1.1Objectives
The application helps the restaurant to do all functionalities more accurately and faster

way. This application is helping food ordering to maintain the stock and cash flows

and there are many functions like.

 To store records.

 Control orders and services.

 Billing

 Control staff

 Help manager to control each part of the restaurant

1.2Problem Statement:
Many restaurant is storing all of their data in manual way. They have hug number of

customers daily. So because large number of customers, they need the help of some

features so they can maintain and stores the record accurately. For managers it is

difficult to view the tables. Orders, kitchen, reception and the counter simultaneously.

They need to full-fledged software to maintain their day by day transaction, orders

and also regular update on records, cash transaction, daily staff reports, customer

feedback etc. In the existing system, entering all the details are done manually. It is

talking many lots of time and also there are chances for mistake.

2
 Chapter 2: Requirements of the analysis of the system
The structure of the system can be divided into three main logical components.

The first component must provide some form of menu management, allowing the

restaurant to control what can be ordered by customers. The second component is the

web ordering system and provides the functionality for customers to place their order

and supply all necessary details. The third and final logical component is the order

retrieval system. Used by the restaurant to keep track of all orders which have been

placed, this component takes care of retrieving and displaying order information, as

well as updating orders which have already been processed.

Web Ordering Restaurant

Customer Database Order Retrieval
System Employee

Menu
Management

Restaurant
Employee

Functional Requirements
As can be seen in the system model diagramed above, each of the three system
components essentially provides a layer of isolation between the end user and the
database. The motivation behind this isolation is twofold. Firstly, allowing the end
user to interact with the system through a rich interface provide a much more
enjoyable user experience, particularly for the non-technical users which will account
for the majority of the system’s users. In addition, this isolation layer also protects the
integrity of the database by preventing users from taking any action outside those
which the system is designed to handle. Because of this design pattern, it is essential
to enumerate exactly which functions a user will be presented and these functions are
outlined below, grouped by component.

3
 2.1 Feasibility Analysis

Feasibility analysis begins once the goals are defined. It starts by

generating broad possible solutions, which are possible to give an
indication of what the new system should look lime. This is where
creativity and imagination are used. Analysts must think up new ways of
doing things- generate new ideas. There is no need to go into the detailed
system operation yet. The solution should provide enough information to
make reasonable estimates about project cost and give users an indication
of how the new system will fit into the organization. It is important not to
exert considerable effort at this stage only to find out that the project is not
worthwhile or that there is a need significantly change the original goal.

Feasibility of a new system means ensuring that the new system, which we
are going to implement, is efficient and affordable. There are various types
of feasibility to be determined. They are:

2.1.1 Economically Feasibility

Development of this application is highly economically feasible. The only
thing to be done is making an environment with an effective supervision.

It is cost effective in the sense that has eliminated the paper work
completely. The system is also time effective because the renting system
are easy to handle.

2.1.2 Technical feasibility

The technical requirement for the system is economic and it does not use
any other additional Hardware and software. Technical evaluation must
also assess whether the existing systems can be upgraded to use the new
technology and whether the organization has the expertise to use it.

4
Install all upgrades framework into the package supported widows based
application. This application depends on Microsoft office and intranet
service, database.

2.1.3 Operational Feasibility

The system working is quite easy to use and learn due to its simple but
attractive interface. User requires no special training for operating the
system. Technical performance include issues such as determining whether
the system can provide the right information for the client and admin , and
whether the system can be organized so that it always delivers this
information at the right place and on time using intranet services.
Acceptance revolves around the current system and its personnel.

2.2 Hardware and Software Requirements

The testing to be performed will require no special hardware, but some

specially designed software may be used, particularly when performing stress testing.

We plan on writing and utilizing a multi-threaded Java program to bombard the

system with an increasing number of HTTP requests and then measure response times

and see at what point things begin to break down. We also will be using the Firefox

plug-in Firebug to monitor the JSON requests and responses.

Throughout all of the design and development phases, we have been

performing unit tests on each component, assuring that it works properly before

introducing it into the rest of the system, but we plan on beginning rigorous testing of

the system starting in the first week of December. We will begin by putting the

5
system through its normal paces as a normal user would be expected to. We will test

the entire functionality of the system, but will do so following the normal logical

flow, and only providing reasonable values for user input.

Once we are happy with how the system performs for normal use cases (which

hopefully will be completed), we will move on to testing the exceptional use cases.

These are the use cases that would never be encountered by the average user, but,

whether through confusion or malice, may come up. Two examples would be adding

hundreds of items to an order or attempting to supply an SQL statement as a login

credential.

2.2.1 Hardware and Software Requirements

Hardware Details:

 1 GHz CPU
 512 MB RAM
 300 MB disk space

Software Details:

 PHP (front end)

 HTML
 JavaScript
 MS Word 2007 or later
 Web Browser: Microsoft Internet Explorer, Mozilla, Google Chrome or later
 MySQL Server (back-end)
  Operating System: Windows XP / Windows7/ Windows 10
6
7
 2.3Gantt chart
 A Gantt chart is a useful graphical tool which shows activities or tasks

performed against time. It is also known as visual presentation of a project where the

activities are broken down and displayed on a chart which makes it is easy to

understand and interpret.

Task/Date 09/ 09/ 09/ 09/ 09/ 09/ 09/ 09/ 09/ 09/ 09/ 09/ 09/ 09/ 09/ 0
10 11 12 13 14 06 07 08 09 10 11 12 13 14 15 1

Requirement
Analysis

Design Phase

Software
Development

System Testing

Documentation
and Presentation
Reports

8
2.4 The Web Ordering System
Users of the web ordering system, namely restaurant customers, must be

provided the following functionality:

 Create an account.

 Manage their account.

 Log in to the system.

 Navigate the restaurant’s menu.

 Select an item from the menu.

 Customize options for a selected item.

 Add an item to their current order.

 Review their current order.

 Remove an item/remove all items from their current order.

 Provide delivery and payment details.

 Place an order.

 Receive confirmation in the form of an order number.

As the goal of the system is to make the process of placing an order as simple

as possible for the customer, the functionality provided through the web ordering

system is restricted to that which most pertinent to accomplish the desired task. All of

the functions outlined above, with the exceptions of account creation and

management, will be used every time a customer places an order.

2.4.1Menu Management System

The menu management system will be available only to restaurant employees

and will, as the name suggests, allow them to manage the menu that is displayed to

9
users of the web ordering system. The functions afforded by the menu management

system provide user with the ability to, using a graphical interface:

 Add a new/update/delete vendor to/from the menu.

 Add a new/update/delete food category to/from the menu.

 Add a new/update/delete food item to/from the menu.

 Add a new/update/delete option for a given food item.

 Update price for a given food item.

 Update default options for a given food item.

 Update additional information (description, photo, etc.) for a given food item.

2.4.2 Order Retrieval System

Of the three components, the order retrieval system is

functionally the simplest. Like the menu management system, it is designed to be

used only by restaurant employees, and provides the following functions:

 Retrieve new orders from the database.

 Display the orders in an easily readable, graphical way.

 Mark an order as having been processed and remove it from the list of active

orders.

2.4.3 Web Ordering System

Users of the web ordering system will interact with the application through a

series of simple forms. Each category of food has its own form associated with it

which presents a drop down menu for choosing which specific item from the category
10
should be added to the order, and a series of check boxes and radio buttons for

selecting which options are to be included. Adding an item to the order is

accomplished by a single button click. Users select which category of food they

would like to order, and therefore which form should be displayed, by navigating a

menu bar, an approach which should be familiar to most users.

Entering delivery and payment deals is done in a similar manner. The user is

presented with a form and must complete the required fields, which include both drop

down and text boxes, before checking out and receiving a confirmation number. One

thing worth noting here is that whenever possible drop down boxes and buttons were

used over freeform input in order to both simplify the ordering process and reduce the

possibility of and SQL injection attempt.

2.5 Non-functional Requirements

Because the design patterns of the Online Ordering System are pretty much

the standard for a web application, the non-functional requirements of the system are

very straightforward. Although written using Google Web Toolkit, the application is

cross-compiled to HTML and JavaScript, along with a PHP backend, all of which are

supported by any reasonably well maintained web server, although I would

recommend Apache2, and particularly the free XAMPP distribution.

All of the application data is stored in a PostgreSQL database, and therefore a

PostgreSQL server must also be installed on the host computer. As with Apache2, this

software is freely available and can be installed and run under most operating

systems.

The server hardware can be any computer capable of running both the web

and database servers and handling the expected traffic. For a restaurant that is not
11
expecting to see much web traffic, or possibly doing only a limited test run, an

average personal computer may be appropriate. Once the site starts generating more

hits, though, it will likely be necessary to upgrade to a dedicated host to ensure proper

performance. The exact cutoffs will need to be determined through a more thorough

stress testing of the system.

2.6 System Evolution

As mentioned in the system model, at the heart of the entire ordering system is

the database. In fact, the system could be completely operational using nothing but the

database and an appropriate shell utility, assuming that all users are well-versed in

SQL and enjoy using it to order food. While this would be a bit extreme, it does

illustrate the point that the one part of the system which will stay relatively constant is

the database. On the other hand, it is very probable that the other components will

continue to evolve with time. For example, with the booming popularity of mobile

applications, we would really like to make the web interface available as a phone

application as well. Also it may make sense to at some point migrate the menu

management and order retrieval systems to web, or even mobile, applications as well,

as some users may prefer to use them as such.

We are also certain that if this system goes into actual use, many requests will

arise for additional features which had not previously considered, but would be useful

to have. For this reason, we feel as though the application can be constantly evolving,

which we consider a very good thing.

12
13
 CHAPTER 3: SYSTEM DESIGN

3.1 Introduction

System design is the process of designing the elements of a system such as the
architecture, modules and components, the different interfaces of those components
and the data that goes through that system.

System Analysis is the process that decomposes a system into its component pieces
for the purpose of defining how well those components interact to accomplish the set
requirements.

The purpose of the System Design process is to provide sufficient detailed data and
information about the system and its system elements to enable the implementation
consistent with architectural entities as defined in models and views of the system
architecture.

MVC Design pattern

The Model View Controller (MVC) design pattern specifies that an application consist
of a data model, presentation information, and control information.

MVC mostly relates to the user Interface/interaction layer of an application.

In the MVC pattern the user sees the View which is updated by the model which is

turn manipulated by the Controller.

14
MVC Pattern

 The Model contains only the pure application data, it contains no logic

describing how to present the data to a user. They are the parts of the application
that implement the logic for the application’s data domain. They retrieve and store
model state in a database.

 The View presents the model’s data to the user. The view can only be used to
access the model’s data. They are the components that display the application’s
user interface (UI).

 The Controller exists between the view and the model. It listens to events

triggered by the view and executes the appropriate commands. They are the
components that handle user interaction, work with the model, and ultimately
select a view to render that displays UI.

3.2 System Flowchart

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.

The flowchart shows the steps as boxes of various kinds, and their order by
connecting the boxes with arrows. This diagrammatic representation illustrates a
solution model to a given problem. Flowcharts are used in analyzing, designing,
documenting or managing a process or program in various fields.

15
 start

Customer
place order

order request
system confirms the receipt of orders

is order no is order is special? no End

normal?

yes
confirm Order

yes

dispatch order

stop

Figure 1 System Flow Chart

3.3 Context Diagram

The Context Diagram shows the system under consideration as a single high-level

process and then shows the relationship that the system has with other external
entities (systems, organizational groups, external data stores, etc.).  
16
Another name for a Context Diagram is a Context-Level Data-Flow Diagram or a
Level-0 Data Flow Diagram.  Since a Context Diagram is a specialized version
of Data-Flow Diagram, understanding a bit about Data-Flow Diagrams can be helpful.

Supplier

Food odering Kitchen

Customer
system

Manager

Figure 2 Context Diagram

17
 3.4 Level 1: Data flow Diagram

A data-flow diagram (DFD) is a way of representing a flow of a data of a process or a

system (usually an information system). The DFD also provides information about the
outputs and inputs of each entity and the process itself. A data-flow diagram has no
control flow, there are no decision rules and no loops. Specific operations based on
the data can be represented by a flowchart.

Receipt
Customer Kitchen

0
customer order Food order
Food ordering
System

Management
Reports

Restaurent
manager
Figure DFD

3.5 ER Diagram

An entity-relationship diagram (ERD) is a data modeling technique that graphically

illustrates an information system’s entities and the relationships between those
entities. An ERD is a conceptual and representational model of data used to represent
the entity framework infrastructure.

The elements of an ERD are:

 Entities
 Relationships
 Attributes

18
 Password
pid
view id

pname
Email

price
User products mst

fname

image

have
have
ccv

quantity card
order mst payment

have
price bank

pid
oid
email email

Figure 3.3 ER Diagram

Chapter 4: Coding

4.1 Model
<?php

function db_connect() {

$db['host'] = "localhost";

$db['username'] = "root";

$db['password'] = "";

$db['db_name'] = "oxford";

$conn = new mysqli($db['host'], $db['username'],

$db['password'], $db['db_name']);

19
// Check connection

if ($conn->connect_error) {

die("Connection failed: " . $conn-

>connect_error);

return $conn;

function signup_new_user($name, $email, $password,

$address, $phone, $create_date) {

$conn = db_connect();

$stmt = $conn->prepare("INSERT INTO userdata

(Name,email,password,address,phone,Date)
values(?, ?, ?,?, ?, ?)");

$stmt->bind_param('ssssii', $name, $email, $password,

$address, $phone, $create_date);

$result = $stmt->execute();

if ($result) {

$stmt->close();

$conn->close();

return $result;

} else {

$stmt->close();

$conn->close();

return false;

20
function signup_new_employer($name, $job, $email,
$passwordmd5, $address, $phone, $create_date) {

$conn = db_connect();

$stmt = $conn->prepare("INSERT INTO employeedata

(Name,Job,email,password,address,phone,Date) values(?, ?,
?,?, ?, ?,?)");

$stmt->bind_param('sssssii', $name, $job, $email,

$passwordmd5, $address, $phone, $create_date);

$result = $stmt->execute();

if ($result) {

$stmt->close();

$conn->close();

return $result;

} else {

$stmt->close();

$conn->close();

return false;

function find_user_by_email($email) {

$conn = db_connect();

$sql = "SELECT * FROM userdata where email='$email'

limit 1";

$result = $conn->query($sql);

$conn->close();

if ($result->num_rows > 0) {

return $result;

} else {

21
 return false;

function find_employer_by_email($email) {

$conn = db_connect();

$sql = "SELECT * FROM employeedata where

email='$email' limit 1";

$result = $conn->query($sql);

$conn->close();

if ($result->num_rows > 0) {

return $result;

} else {

return false;

function db_login($email, $password) {

$conn = db_connect();

$sql = "SELECT * FROM userdata where email='$email'

and password='$password' limit 1";

$result = $conn->query($sql);

$conn->close();

if ($result->num_rows > 0) {

$row = $result->fetch_assoc();

return $row;

} else {

return false;

22
 }

function db_employerlogin($email, $password) {

$conn = db_connect();

$sql = "SELECT * FROM employeedata where

email='$email' and password='$password' limit 1";

$result = $conn->query($sql);

$conn->close();

if ($result->num_rows > 0) {

$row = $result->fetch_assoc();

return $row;

} else {

return false;

function additem($category, $Name, $target, $price) {

$conn = db_connect();

$stmt = $conn->prepare("INSERT INTO fooddata

(category, Name, img, price) values(?, ?, ?,?)");

$stmt->bind_param('sssi' , $category, $Name,

$target, $price);

$result = $stmt->execute();

if ($result) {

$stmt->close();

23
 $conn->close();

return $result;

} else {

$stmt->close();

$conn->close();

return false;

function allproducts() {

$conn = db_connect();

$sql = "SELECT * FROM fooddata order by FID asc ";

$result = $conn->query($sql);

$conn->close();

if ($result->num_rows > 0) {

return $result;

} else {

return false;

function deleteproductby_id($fid) {

$conn = db_connect();

$sql = "Delete from fooddata where FID=$fid";

$conn->query($sql);

if ($conn->affected_rows > 0) {

24
 $conn->close();

return TRUE;

} else {

$conn->close();

return false;

function product_byid($fid) {

$conn = db_connect();

$sql = "SELECT * FROM fooddata where FID=$fid";

$result = $conn->query($sql);

$conn->close();

if ($result->num_rows > 0) {

return $result;

} else {

return false;

function edititem($pid, $Ptype, $Pname, $SP, $Quantity,

$Pdescription, $target, $Qsold) {

$conn = db_connect();

$stmt = $conn->prepare("UPDATE productdata set

Ptype='$Ptype', Pname='$Pname', SP='$SP'

25
 , Quantity='$Quantity', Pdescription='Pdescription',
img='$target', Qsold='$Qsold' where PID='$pid' ");

$result = $stmt->execute();

if ($result) {

$stmt->close();

$conn->close();

return $result;

} else {

$stmt->close();

$conn->close();

return false;

function product_bytype($ftype) {

$conn = db_connect();

$sql = "SELECT * FROM fooddata where

category='$ftype'";

$result = $conn->query($sql);

$conn->close();

if ($result->num_rows > 0) {

return $result;

} else {

return false;

26
 4.2 Header

<!DOCTYPE html>

<html lang="en">

<head>

<meta charset="UTF-8">

<title>Foodbank- The Perfect Food at Your Door!</title>

<meta name="viewport" content="width=device-width, initial-scale=1.0"/>

<!-- <meta http-equiv="refresh" content="1"> -->

<link href="css/anit.css" rel="stylesheet">

<link href="https://fonts.googleapis.com/icon?family=Material+Icons"
rel="stylesheet">

<link href="https://fonts.googleapis.com/css?family=Pacifico&display=swap"
rel="stylesheet">

<link href="https://fonts.googleapis.com/css?
family=Bree+Serif&display=swap" rel="stylesheet">

<link rel="stylesheet"
href="https://cdnjs.cloudflare.com/ajax/libs/materialize/1.0.0/css/materialize.min.css"
>

<link rel="stylesheet" href="css/style.css">

<link rel="stylesheet" href="resource/other/signupko.css">

<link rel="stylesheet" href="resource/other/loginko.css">

27
</head>

<section class="fnavbar">

<div class="navbar-fixed">

<nav>

<div class="nav-wrapper">

<a href="<?php echo $base_url ?>?r=site" class="brand-

logo">FoodBank</a>

<?php

if(empty($_SESSION['user']['login'])){ ?>

<ul class="right hide-on-med-and-down">

<li><a class="active" href="<?php echo $base_url ?>?

r=site">Home</a></li>

<li><a href="<?php echo $base_url ?>?r=login">User

Login</a></li>

<li><a href="<?php echo $admin_base_url ?>?

r=employerlogin">Admin Login</a></li>

<li><a href="<?php echo $base_url ?>?

r=productstable">FoodItems List</a></li>

<?php

}else{

?>

<ul class="right hide-on-med-and-down">

<li><a class="active" href="<?php echo $base_url ?>?r=site">Home</a></li>

<li><a href="<?php echo $base_url ?>?

r=viewcart">Cart</a></li>

<li><a href="<?php echo $base_url ?>?r=products">Menu</a></li>

<li><a href="<?php echo $base_url ?>?r=logout">Logout</a></li>

28
</ul>

<?php

?>

</ul>

</div>

</nav>

</div>

</ul>

</section>

<form method="post">

<?php if( isset($user) && is_array($user) ): ?>

<?php foreach ($user as $key => $value) : ?>

29
 <label for="<?php echo $key; ?>"><?php echo ucfirst($key); ?></label>

<input type="text" name="<?php echo $key; ?>" id="<?php echo $key; ?>"
value="<?php echo escape($value); ?>" <?php echo ($key === 'id' ? 'readonly' : null);
?> >

<?php endforeach; ?>

<input type="submit" name="submit" value="Submit">

<?php

else:

//echo 'Problem with user???' ;

endif;

?>

</form>

</html>

4.3Login
<?php

include 'header.php';

?>

<div class="login-page">

30
<h1>User Login Form</h1>

<div class="form">

<form class="login-form" action="<?php echo $base_url ?>?r=login"

method="post">

<input type="email" name="email" placeholder="Email"/>

<input type="password" name="password" placeholder="password"/>

<input type="submit" value="Login" />

<p class="message">Not registered? <a href="<?php echo $base_url ?>?

r=signup">Create an account</a></p>

<p class="message"><a href="<?php echo $admin_base_url ?>?

r=employerlogin">Admin Login</a></p>

</form>

</div>

</div>

</body>

</html>

4.3Signup

<?php

include 'header.php';

?>

31
 <!-- main -->

<div class="main-w3layouts wrapper">

<a href="<?php echo $base_url ?>?r=site"><h1>User SignUp Form</h1></a>

<div class="main-agileinfo">

<div class="agileits-top">

<form action="<?php echo $base_url ?>?r=signup" method="post"

enctype="multipart/form-data">

<input class="text" type="text" name="Name" placeholder="Name"

required="">

<input class="text email" type="email" name="email" placeholder="Email"

required="">

<input class="text" type="password" name="password" placeholder="Password"

required="">

<input class="text w3lpass" type="password" name="repassword"

placeholder="Confirm Password" required="">

<input class="text" type="text" name="address" placeholder="Address"

required=""> <br><br>

<input class="text" type="text" name="phone" placeholder="Contact No."

required=""> <br>

32
 <div class="wthree-text">

<label class="anim">

<input type="checkbox" class="checkbox" required="">

<span>I Agree To The Terms & Conditions</span>

</label>

<div class="clear"> </div>

</div>

<input type="submit" value="SIGNUP">

</form>

<p>Already have an Account? <a href="<?php echo $base_url ?>?r=login">

Login Now!</a></p>

</div>

<!-- copyright -->

<div class="colorlibcopy-agile">

<p>© 2019 FoodBank. All rights reserved</p>

</div>

<!-- //copyright -->

<ul class="colorlib-bubbles">

<li></li>

<li></li>

<li></li>

<li></li>

33
 <li></li>

<li></li>

<li></li>

<li></li>

<li></li>

<li></li>

</ul>

</div>

<!-- //main -->

</body>

</html>

CHAPTER 5: TESTING
5.1 Introduction

Once source code has been generated, application must be tested to uncover (and
correct) as many errors as possible before delivery to customer. Our goal is to design
a series of test cases that have a high likelihood of finding errors. To uncover the
errors software techniques are used. These techniques provide systematic guidance for
designing test that

(1) Exercise the internal logic of application components, and

(2) Exercise the input and output domains of the program to
uncover errors. In program function, behavior and
performance.
Importance:
 To deliver high-quality products or software application proper testing is
required. This enhances the level of support or facilities given to the
customers. Moreover, a well-tested product incurs lesser maintenance cost and
so the results delivered are more accurate, consistent and reliable.

 To design any product or software a lot of expenses are incurred so it’s critical
for an application or product to give positive results to avoid any unwanted or
sudden expenses.

34
  To consolidate your position in the market the product performance should be
really good and durable. This kind of certainty can only be achieved by proper
testing methods in place.

5.2 Testing strategies

5.2.1 Unit Testing

Unit testing focuses verification effort on the smallest unit of software design- the
software component or module. The unit test is white-box oriented. The unit testing
implemented in every module of student attendance management System. by giving
correct manual input to the system ,the data are stored in database and retrieved. If
you want required module to access input or get the output from the End user. any
error will accrued the time will provide handler to show what type of error will
accrued .

5.2.2 Performance Testing

Performance testing is designed to test the run-time performance of software within

the context of an integrated system. Performance testing occurs throughout all steps in
the testing process. Even at the unit level, the performance of an individual module
may be assessed as white-box tests are conducted.

5.2.2 System Testing

System testing is actually a series of different tests whose primary purpose is to fully
exercise the computer-based system. Below we have described the two types of
testing which have been taken for this project. it is to check all modules worked on
input basis .if you want change any values or inputs will change all information. So
specified input is must.

5.3 Login Screen

Client Login:

35
Admin Login:

5.4 Input and output screen of main functions

FoodList:

36
ClientSignup:

37
Cart:

Menu:

Information:

38
Admin Dashboard:

39
40
 CHAPTER 6: TEST REPORT
6.1 Test Reports
Project Basic Project Overview
Information

Project Name: FoodOrderingSystem

Name Of Product: Foodbank

Product Description: FoodOrderingSystemWebApplication

Project Description:
 Food ordering system is an application
which will help restaurant to optimize and
control over their restaurants..
 Admin can edit, delete and add food
 Manage the address book
 The manager will able to control the
restaurant by having all the reports to hand
and able to see the records of each
employees and order.
 The application helps the restaurant to do all
functionalities more accurately and faster
way.
 This application is helping food ordering to
maintain the stock and cash flows
Project Type: Testing and Verification

Project Duration: Start Date: 2076/06/18 End Date:2076/09/18

6.2 User Documentation

Food ordering system is an application which will help restaurant to optimize and

control over their restaurants. For the waiters, it is making life easier because they

don’t have to go kitchen and give the orders to chef easily. For the management point

of view, the manager will able to control the restaurant by having all the reports to

41
hand and able to see the records of each employees and order. In today’s age of fast

food and take-out, many restaurants have chosen to focus on quick preparation and

speedy delivery of orders rather than offering a rich dining experience. Until very

recently, all of these delivery orders were placed over the phone, but there are many

disadvantages to this system. First, the customer must have a physical copy of the

restaurant’s menu to look at while placing their order and this menu must be up to

date. While this expectation is not unreasonable, it is certainly inconvenient.

The orders are placed using strictly oral communication, which makes it far

more difficult for the customer to receive immediate feedback on the order they have

placed. This often leads to confusion and incorrect orders. The current system is also

inconvenient for the restaurant itself, as they must either have a dedicated staff

member to answer the phone and take orders, or some employees must perform

double-duty, distracting them from their regular tasks.

Menu, complete with all available options and dynamically adjusting prices

based on the selected options. After making a selection, the item is then added to their

order, which the customer can review the details of at any time before checking out.

This provides instant visual confirmation of what was selected and ensures that items

in the order are, in fact, what was intended.

Chapter 7: Conclusion
7.1 Conclusion of the project
 RMS makes works easy and faster than current applications.

 All the data will be saved in the database. So the administer can view all the

data on time.

42
  This system reduces manual works.

 RMS will store all the records permanently and also gives the raises and

deviation in the status of the restaurant in the markets.

 All the record of the current and ex-staffs will be stored in database.

 All the expenses per day will be updated in the database

7.2 Limitations

Application won’t be able to send some notifications about any report or any delivery
system to owner or customer.

Application will require the java, MySQL and three different system which should be
connected to one network for using application to full functionality.

User won’t able to change the skin or any functionality of applications.

User can only get the reports in some formats only.

7.3 Future enhancements of the project

Delivery options: Add delivery option

Payment options: Add different payment options like Esewa

Order Process Estimate, Order Ready Notifications.

Enhance user interface by adding more user interactive features. Provide deals and
promoting offer details to home page.

Provide Recipes of the week/day to home page.

Restaurant locator: Allow to find restaurant.

43
44
 REFERENCE
Book Reference:

 Learning PHP, MySQL, JavaScript, and CSS: A Step-by-Step Guide to

Creating Dynamic Websites – by Robin Nixon
 PHP& MySQL Web Development – by Luke Welling & Laura Thompson

Web Reference:
 https://getbootstrap.com/docs/4.4/getting-started/introduction/
 https://www.w3schools.com/html/default.asp
 https://www.w3schools.com/css/default.asp
 https://www.w3schools.com/js/default.asp
 https://www.w3schools.com/sql/default.asp
 https://www.w3schools.com/php/default.asp
 https://phpgurukul.com/php-projects-free-downloads/

45