ONLINE CAFE MANAGEMENT

A Project Report
Submitted in partial fulfilment of the Requirements for the award of the Degree of

BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY)

By

Kirtiraj Kiran Sonawane

Seat No.: 35037

Under the esteemed guidance of

Mrs. Manisha Mahadik
Professor

DEPARTMENT OF INFORMATION TECHNOLOGY

DR. BABASAHEB AMBEDKAR COLLEGE OF ARTS, COMMERCE AND
SCIENCE
(Affiliated to University of Mumbai)
MAHAD, 402303
MAHARASHTRA
2021-22

PROFORMA FOR THE APPROVAL PROJECT PROPOSAL

Page | 1
 PRN No.: Seat no.:

1. Name of the Student

2. Title of the Project

Online Cafe management System

3. Name of the Guide

4. Teaching experience of the Guide

5. Is this your first submission? Yes No

Signature of the Student Signature of the Guide

Date:-………………… Date: …………………….

Signature of the Coordinator

Date: …………………

Page | 2
 DR. BABASAHEB AMBEDKAR COLLEGE OF ARTS, COMMERCE
AND SCIENCE
(Affiliated to University of Mumbai)

MAHAD, MAHARASHTRA-402301

DEPARTMENT OF INFORMATION TECHNOLOGY

CERTIFICATE

This is to certify that the project entitled, " Online Cafe management

System ", is bonafied work of Kirtiraj Kiran Sonawane bearing Seat No.: 35037 submitted in
partial fulfillment of the requirements for the award of degree of
BACHELOR OF SCIENCE in INFORMATION TECHNOLOGY from University of Mumbai.

Internal Guide Coordinator

External Examiner

Date: College Seal

Page | 3
 ACKNOWLEDGEMENT
The success and final outcome of this project required a lot of guidance and assistance from many people
and I am extremely privileged to have got this all along the completion of my project. All that I have done
is only due to such supervision and assistance and I would not forget to thank them.

I would like to express my deepest appreciation to all those who provided me the possibility to complete
project topic on “ONLINE CAFE MANAGEMENT
SYSTEM ”. I am extremely thankful to our Principal Dr. Dhanaji Gurav. I heartly thank our internal
project guide Prof. Manisha Mahadik whose valuable guidance and suggestions helped us in
accomplishing my project. I would like to extend my sincere esteems to all Library staff for providing
reference project reports books.

Finally, I would like to thank my friends for their cooperation to finalizing this project within the limited
time frame.

Sincere Thanks from,

Kirtiraj Kiran Sonawane

Page | 4
 TABLE OF CONTENTS
ABSTRACT ............................................................................................................................................................................... 6
CHAPTER 1: INTRODUCTION: ................................................................................................................................................ 7
1.1 BACKGROUND ................................................................................................................................................. 7
1.2 PROJECT OBJECTIVES ...................................................................................................................................... 8
1.3 PURPOSE, SCOPE, AND APPLICABILITY ......................................................................................................... 9
1.3.1 Purpose .................................................................................................................................................... 9
1.3.2 Scope ...................................................................................................................................................... 10
1.3.3 APPLICABILITY ........................................................................................................................................ 10
1.4 ACHIEVEMENTS ............................................................................................................................................. 10
1.5 ORGANIZATION OF REPORT ......................................................................................................................... 11
Chapter 2: Survey of Technologies .......................................................................................................................12
CHAPTER 3: REQUIREMENTS AND ANALYSIS ...................................................................................................................... 19
3.1 PROBLEM DEFINITION .................................................................................................................................. 20
3.2 REQUIREMENTS SPECIFICATION .................................................................................................................. 23
3.3 PLANNING AND SCHEDULING…………………………………………………………………………………………………………… 32
3.4 SOFTWARE AND HARDWARE REQUIREMENTS……………………………………………………………………………………39
CHAPTER 4: SYSTEM DESIGN ................................................................................................................................................ 41
4.1 Basic Modules ............................................................................................................................................... 42
4.2 DATA DESIGN ................................................................................................................................................ 44
4.2.1 Schema Design ....................................................................................................................................... 44
4. 2.2Data Integrity and Constraints ............................................................................................................... 46
4.3 PROCEDURAL
DESIGN ................................................................................................................................... 47
4.3.1 Logic
Diagrams .............................................................................................................................
.......... 47
4.3.2 Data
Structures ............................................................................................................................
.......... 49
4.3.3 Algorithms
Design .................................................................................................................................
. 50

Page | 5
 4.4 USER INTERFACE
DESIGN .............................................................................................................................. 53 4.5
Security
Issues ...............................................................................................................................................
56
4.6 TEST CASE DESIGN ............................................................................................Error! Bookmark not defined.
CHAPTER 5: IMPLEMENTATION AND TESTING ................................................................................................................... 58
5.1 IMPLEMENTATION APPROACHES ................................................................................................................ 59
5.2 CODING DETAILS AND CODE EFFICIENCY ..................................................................................................... 61
5.2.1 Code Efficiency ...........................................................................................Error! Bookmark not defined.
5.3 TESTING APPROACH ...................................................................................................................................................... 62
5.3.1 Unit Testing ............................................................................................................................................
62
5.3.2 Integrated Testing ..................................................................................................................................
65
5.3.3 Beta Testing ...........................................................................................................................................
66
5.4 MODIFICATIONS AND IMPROVEMENTS ....................................................................................................................... 67
5.5 TEST CASES ..................................................................................................................................................................... 68

Page | 6
 ABSTRACT
This Cafe Management System is the web-based project developed using asp.net and SQL server.
This website is used to order food items through online. The best way to optimize these activities is
growing the business online as well. Today’s generation encourages high-tech services especially over the
Internet. The main advantage of this project is it saves user time looking out for restaurants. This system
will automate day to day activity of a Cafe. This system generates online bill for every table. For business
owners it saves time, business resources and expenses. The customer can also have a preference to reserve
a table for them so that it will be reserved for them when they arrive. The online cafe system gives an
online display of different and variety of dishes where Customer can have a look of all items. In this project
there will be a Menu bar in the site where customer can find their list of food which they want to place as
an order.
Our main goals are to get customer a freely interface with website so that they can easily place
order and enjoy with there meal. Once placing order, the customer have the invoice and after that the
order will be completely get successful. The customer can change their dishes that they will be placing
through order.
Also, they can cancel the order. The Invoice will be sent also with the parcel when delivered to customer.
On the admin side, the admin receives the Table Reservation and process it. The order which
customer has placed will be checked and it will be parcelled in time. After Successful Delivery of Food, the
customer gives feedback on feedback panel in the online Cafe Management System. This system can be
used rather than using paper work.

Page | 7
 CHAPTER 1:INTRODUCTION:
1.1 BACKGROUND
The Online Cafe management system is the system for manage the restaurant business. The main
point of developing this system is to help Cafe administrator manage the cafe business and help customer
for online ordering and reserve table. By using manual customer ordering is very difficult for waiters to
keep the correct information of food for customer and maybe they can loss the customer information. The
project is developing because , many restaurants have a lot of difficulties to manage the business such as
customer ordering and reservation of tables, with this system when the customer will reserve the table then
customer will not have to stand in queue for table to have their meal.
So, online cafe management system will develop to help the cafe administrator to manage cafe
management and for customer make their online ordering and reservation table. Other than that, this project
is to upgrade the manual system and make the business easily to access and systematic. In this online cafe
system, the customer can easily have a selection of food items. There will be time consumed of people that
they don’t have to go out to take or place order the all the needs will be in system. The main advantage of
my system is that it greatly simplifies the ordering process for both the customer and the cafe and also
greatly lightens the load on the cafe’s end, as the entire process of taking orders is automated. Online Cafe
helps customer to find nearby cafe’s which will help them for having delivery in time. As it shows you
most rated cafe location for ordering your meal. It gives safety process to get order of food online. For
example, when a person goes to restaurant, he has to drive or go through the public vehicle to the cafe, then
he looks for table where he will be comfortable to sit or if its full then they have to wait in que for a long
time, if they got the table then some of the order maybe misplaced because of the manual paper work.
Online cafe management system helps customer to avoid these disadvantages. In this online system the
customer has to logs on the internet, visit the online cafe system website, and select your dishes he desires.
The disadvantages of online cafe are that every customer not chooses the services of getting food
online. Some people like physically going out to have meal so that they will get to know how the clean
café’s are actually. Also, they are afraid of net banking because they think of card details can be stollen in
between while doing payments and some of them also get hesitate to give card details , therefore they
prefer to go physically to cafe.

In fact, they can order more meal or starter if they want. This is highly inconveniencing to
the customer that the dish is not having tastes as the ingredients are given below the picture
of meal. Online Cafe system are now become a trend that everyone is ordering online in
offices, home, etc. It is interesting to know that people in the age group of 15 to 45 use online
Page | 8
cafe system more as compared to other age groups. Normally in this age group, students and
professional people come.

1.2 PROJECT OBJECTIVES

One of the main objectives of any business is to maximize profit by increasing
efficiency and decreasing overheads without compromising customer satisfaction. Currently,
many cafe’s use a paper-based system to communicate between the cafe and kitchen which
can be shown to be one of the least efficient approaches. Even though this approach is
implemented in successful profitable café’s, there are several problems which could be seen
as reducing the cafe’s efficiency:
• Miscommunication caused by handwriting.
• Unmanageable order logging.
• Inefficient cafe-kitchen communication.
• Difficult order tracking and time management.
• Difficult stock management.
• Limited statistical output.
A recipe for a menu item has a chef, preparation instruction sand associated
ingredients. Main objective builds the system this is to provide ordering and reservation
service by online to the customer. Each menu item has a name, price and associated recipe.
With this system online, ordering and reservation management will become easier and
systematic to replace traditional system where are still using paper.
To resister a meal online, the customer has to become a member first then he can
access the later part of the site. This project to facilitate customer for make online ordering
and reservation. The option of becoming member was only an attempt to avoid (to some
extent) placing the fake bookings.

1.3 PURPOSE, SCOPE, AND APPLICABILITY

Page | 9
1.3.1 Purpose
Nowadays, many cafe’s manage their business by manual especially take customer
ordering. . In traditional booking system, a customer has to go to restaurant or make a phone
call in order to get his meal reserved. Today, waiter takes the customer ordering by manual
system with using paper. Customer does some formal conversation like hello, hi, etc.
Then he demands for today’s menu and do some discussion over menu items then he orders.
It takes 5 to 10 minutes to book the order and waiter book the order on paper so there is
probability of lost and duplicates customer information. Restaurant management system puts
the order in a queue with specific priority according to time and quantity, and then a cook is
assigned for the specific order to complete it.
Besides, the waiter information also by manual system kept use paper and this is
difficult for cafe administrator to find waiter information, probability missing the paper and
difficult to arrange the schedule. Initial problem is that the customer has to get connected over
the phone, it would be harder if the cafe is very popular and busy. Sometimes, waiter
information and customer information are important to cafe administrator for reference in the
future. The chances of committing mistakes at the cafe side in providing a menu list for a
specific time would be more.

1.3.2 Scope
The study focuses on the appraisal of the Documentation for On-line restaurant
management system. The ONLINE CAFE MANAGEMENT SYSTEM includes:
Billing, Inventory, Website, and Reservation. This system will change the manual system of
the business in order for the user to work easier and provide faster transaction for the
customer. It can produce an accurate and reliable report which includes print-outs of receipt
for customer’s payment and inventory of menu’s, beverages, etc.
The system will only be manipulated by the authorized person like the
owner or the personnel. An authorized person has a registered account in the system for the
History of the system. Our study does not offer payroll system for the employees.

1.3.3 APPLICABILITY

The System is a standalone system, so multiple users can order the food. They can also
reserve the table before they visit to cafe. Our main goals are to get customer a freely
Page | 10
interface with website so that they can easily place order and enjoy with their meal. This
website will provide customer to choose nearby cafe and then the whole information will be
display to user. Where menu card and images of dishes will be displayed at interface after
selection of the dish the next process is detail. Where the customer should be given his
delivery details so that food can be reached till him. In this the invoice will be created
through which customer can verify the bill with delivery bill. This all thing will be in a
system where there will be two login one for user where people can only see that where are
cafe located and what’s in the menu and how the dish will look which speciality will be in
dish this all will be show to the customer and one for developer side where he can change
menu, remove cafes from location, managing databases, etc. This all thing will be applicable
to our website.

1.4 ACHIEVEMENTS

Following will be the goals which we have achieved during the project:
• Ordering from home
The primary aim of this project is to buy food from online cafe . So, the customer doesn’t
need to go out of the home to take food from restaurant or call to the cafe and ask for the
menu to place the order.
• Time and Energy saving
It is time and energy saving. The people can log on to an online cafe site while sitting in
any corner of the home or offices. The customer doesn't go physically to cafe for take away
the meal. So, we can say that it is time and energy saving. • Comparison of
Products
Online cafe gives the benefit of compares the price of each dish of every cafe. So,
customer can easily decide the right price for him. The customer can also see the reviews on
the dishes means in short he can compare that which dish to order or select while ordering.
• Wide Variety Selection
Online cafe gives varieties of dishes with different prices and different rating. It gives the
different tastes to dishes while adding some ingredient so we have more option while
choosing the food to place order and get delivery directly to our home.

Page | 11
1.5 ORGANIZATION OF REPORT

In chapter 1, we have discussed about the overview and introduction of the project.
We have discussed about the objectives and scope of the online Cafe project. Also, we have
discussed that why we are doing this project, that is it will cover the disadvantages of
traditional or physical ordering of food and convenient way of getting customer satisfied by
having delivery in time.
In further chapter 2, we will discuss about the technologies which we will be using in
the project. Also, a brief overview of all the technologies required in our online shopping
project. We will be explained that why we will use these technologies. And we will explain
the technologies available in the environment and a comparative study of all the available
technologies.
In further chapter 3, we will discuss the component and overview of requirements and
analysis. We will describe the problem definition of the project that what we are achieving
from the project. And the basic hardware requirements for the application. We will also give
the details of conceptual models such as data flow diagram, ER diagram, use case diagram s
that are in our project. Planning and scheduling of the project will also be done in this
chapter. The Problem Definition Requirements, Specification, Planning and Scheduling,
Hardware Requirement, Software Requirements, Conceptual Models will be covered in this
chapter.
In further chapter 4, we will describe desired features and operations in detail,
including screen layouts, business rules, process diagrams, pseudo code and other
documentation. We will give the descriptions of layout of screens and the modules of
different phases and screens. We will discuss how the data is organized in data design and
data constraints and integrity checks. Different validation cases for different input and forms
also formed in this chapter. A systematic way for developing the algorithms and pseudo
codes will be provided. And the different charts like control flow chart and process diagrams.
The logic design and data organizations for the project. We will discuss about the different
security issues related with our project and can be come in future. And at the last we will
design the use cases, which will provide easy detection of errors and mistakes within a
minimum period of time and with the least effort.

Page | 12
 Chapter 2: Survey of Technologies
• INTRODUCTION TO C#
C# is an elegant and type-safe object-oriented language that enables
developer to build a variety of secure and robust application that run on the .NET
Framework. We can use C# to create traditional windows client application, XML
web services, distributed components, client-server applications, database application,
and much, much more. Visual C# 2010 provides an advanced code editor, convenient
user interface designers, integrated debugger, and many other tools to make it easier
to develop application based on version 4.0 of the C# language and version 4.0 of
the .NET framework.
C# syntax simplifies many of the complexities of C++ and provides powerful
features such as nullable value types, enumerations, delegates, lambda expression and
direct memory access, which are not found in java. C# supports generic methods and
types, which provide increased type safety and performance, and iterators, which
enables implementers of collection classes to define custom iteration behaviours that
are simple to use by client code.
As an object-oriented language, C# supports the concept of encapsulation,
inheritance, and polymorphism. All variables and methods, including the main
method, the applications entry point, are encapsulated within class definitions. A
class may inherit directly from one parent class, but it may implement any number of
interfaces. Methods that override virtual methods in a parent class require the override
keyword as a way to avoid accidental redefinition. In C#, a struct is like a lightweight
class; it is a stack-allocated type that can implement interfaces but does not support
inheritance.

• C# features
In addition to these basic object-oriented principles, C# makes it easy to develop
software components through several innovative language constructs, including the
following:

Page | 13
  Encapsulated method signatures called delegates, which enable type-safe
event notifications.
 Properties, which serve as accessors for private member variables.
 Attributes, which provide declarative metadata about types at run time.
 Inline XML documentation comments.

If you have to interact with other Windows software such as COM objects or
native Win32 DLLs, you can do this in C# through a process called "Interop". C# even
supports pointers and the concept of "unsafe" code for those cases in which direct
memory access is absolutely critical. The C# build process is simple compared to C
and C++ and more flexible than in Java. There are no separate header files, and no
requirement that methods and types be declared in a particular order. A C# source file
may define any number of classes, structs, interfaces, and events.

• .NET FRAMEWORK PLATFORM ARCHITECTURE

C# programs run on the .NET Framework, an integral component of Windows
that includes a virtual execution system called the common language runtime (CLR)
and a unified set of class libraries. The CLR is the commercial implementation by
Microsoft of the common language infrastructure (CLI), an international standard that
is the basis for creating execution and development environments in which languages
and libraries work together seamlessly. The IL code and resources, such as bitmaps
and strings, are stored on disk in an executable file called an assembly, typically with
an extension of .exe or .dll. An assembly contains a manifest that provides
information about the assembly's types, version, culture, and security requirements.
When the C# program is executed, the assembly is loaded into the CLR, which
might take various actions based on the information in the manifest. Then, if the
security requirements are met, the CLR performs just in time (JIT) compilation to
convert the IL code to native machine instructions. Code that is executed by the CLR
is sometimes referred to as "managed code," in contrast to "unmanaged code" which
is compiled into native machine language that targets a specific system.

Page | 14
 Fig 1 Structure of .NET

Language interoperability is a key feature of the .NET Framework. Because

the IL code produced by the C# compiler conforms to the Common Type
Specification (CTS),IL code generated from C# can interact with code that was
generated from the .NET versions of Visual Basic, Visual C++, or any of more than
20 other CTScompliant languages. A single assembly may contain multiple modules
written in different .NET languages, and the types can reference each other just as if
they were written in the same language.
In addition to the run time services, the .NET Framework also includes an
extensive library of over 4000 classes organized into namespaces that provide a wide
variety of useful functionality for everything from file input and output to string
manipulation to XML parsing, to Windows Forms controls. The typical C#
application uses the .NET Framework class library extensively to handle common
"plumbing" chores.

Page | 15
• TECHNOLOGY USED IN ASP.NET
 INTRODUCTION
ASP.NET is more than the next version of Active Server Pages (ASP); it
provides a unified Web development model that includes the services necessary for
developers to build enterprise-class Web applications. While ASP.NET is largely
syntax compatible with ASP, it also provides a new programming model and
infrastructure for more scalable and stable applications that help provide greater
protection. You can feel free to augment your existing ASP applications by
incrementally adding ASP.NET functionality to them.
ASP.NET is a compiled, .NET-based environment; you can author applications
in any .NET compatible language, including Visual Basic .NET, C#, and JScript .NET.
Additionally, the entire .NET Framework is available to any ASP.NET application.
Developers can easily access the benefits of these technologies, which include the
managed common language runtime environment, type safety, inheritance, and so on.
Developers can use Web Forms or XML Web services when creating an
ASP.NET application, or combine these in any way they see fit. Each is supported by
the same infrastructure that allows you to use authentication schemes, cache frequently
used data, or customize your application's configuration, to name only a few
possibilities.
 Web Forms allow you to build powerful forms-based Web pages. When building
these pages, you can use ASP.NET server controls to create common UI elements,
and program them for common tasks. These controls allow you to rapidly build a Web
Form

out of reusable built-in or custom components, simplifying the code of a page. For
more information, see Web Forms Pages. For information on how to develop
ASP.NET server controls.
 An XML Web service provides the means to access server functionality remotely.
Using XML Web services, businesses can expose programmatic interfaces to their
data or business logic, which in turn can be obtained and manipulated by client and
server applications. XML Web services enable the exchange of data in client-server or
serverserver scenarios, using standards like HTTP and XML messaging to move data

Page | 16
 across firewalls. XML Web services are not tied to a particular component technology
or object-calling convention. As a result, programs written in any language, using any
component model, and running on any operating system can access XML Web services.

• ASP.NET FEATURES
ASP stands for Active Server Pages. ASP.net is a web application framework developed and
marketed by Microsoft so that programmers can create dynamic websites. It supports languages
like VB.Net, C#, Jscript.Net, etc. The programming logic and content can be developed
separately in Microsoft Asp.Net. Asp.net covers features like reusable code, deploying the .net
application on the server, testing web application, debugging and so on.

• ASP.NET was released in 2002 as the higher version of Classic ASP.

• Extensions of ASP.Net pages are .aspx and are usually written in C#.

• The latest official version of ASP.NET is ASP.NET 4.6.

• ASP.Net 5 was expected to have an important upgrade to ASP.NET.

• ASP works on top of the .NET HTTP protocol, and browser-to-server uses HTTP
commands and policies to set bilateral communications and collaboration.

• ASP.NET is used to produce interactive, data-driven web applications on the Internet.

• In this to create HTML pages, there are large number of controls such as text boxes, buttons
and labels to collect, configure and manipulate the code.

• ASP and ASP.NET are server-side technologies. The code is executed by an Internet server.

• When a browser requests ASP or ASP.NET file, then the ASP engine reads the file,
executes any code in the file, and returns the result to the browser.

• ASP.NET is a technology, which works on the .Net framework that contains all web related
functionalities. The .NET framework is composed of an object-oriented hierarchy. An
ASP.NET Web App is made up of pages. When a user requests the ASP.NET page, the IIS
sends the processing of the page to the ASP.NET Runtime system.

Page | 17
• The ASP.Net Runtime transforms the .aspx page to a class instance, which is derived from
the base class page of the Net Framework. Each ASP.NET page is an object and all its
components and server-controls are also objects.

Components of .Net Framework 3.5 and their features

Component Features

Common Language Runtime It performs exception handling, debugging, thread

or CLR execution, memory management, code execution, code
security, verification, security checks, and compilation.
The code managed directly by CLR is called managed
code. The compiler converts the source code into a CPU
independent intermediate language (IL) code, then the
JIT (Just in Time) compiler compiles the IL code into
native code, which is machine specific.

.Net Framework Class It has a huge library of reusable types. Classes,

Library interfaces, and structured values, which are collectively
called types.
Common Language It includes specifications for the implementation of .NET
Specification support languages and language integration.

Common Type System It provides guidelines for using, managing and declaring,
types at runtime, and cross-language communication.

Metadata and Assemblies Metadata is binary information describing the program,

which is stored in either a portable executable file (PE) or
memory. Assembly is a logical unit consisting of a set of
resources such as Assembly Manifest, Type Metadata, IL
Code, and Image Files

Windows Forms A graphical representation of any window displayed in

the application is Windows Forms

Page | 18
ASP.NET and ASP.NET ASP.NET is the web development model and the
AJAX ASP.NET extension is to develop and implement AJAX
& AJAX functionality. ASP.NET AJAX components
are those that allow the developer to update data on a
website without reloading the page full.

ADO.NET This technique is used to work with data and databases. It

provides access to data sources such as SQL Server, OLE
DB, and XML etc. ADO.NET allows connections from
data sources to recover tamper and update data sources.

Windows Workflow It helps in creating workflow-based applications in

Foundation (WF) Windows. This includes activities, workflow runtime,
workflow designer and rule engine.

Windows Presentation It provides an isolation between user interface and

Foundation business logic. It helps in developing amazing visual
interfaces using documents, media, two and
threedimensional graphics, animations, etc.

Windows Communication It is the technology used to create and execute connected

Foundation (WCF) systems.

Windows CardSpace It provides protection to access resources and to share

personal information on the Internet.

LINQ It provides data querying capabilities. .Net languages use

a syntax which is similar to the tradition query language
SQL.

Table 1 ASP.NET Components and Features.

CHAPTER 3: REQUIREMENTS AND ANALYSIS

Page | 19
 Software Life cycle models describe the steps of the software cycle and the order in
which those steps are executed. Each stage produces the deliverables required by the next
step in the life cycle. Requirements are translated into the design. The code is made according
to the design which is called the development phase. After coding and development testing
phase verify the delivery of the implementation. The test team follows Software Testing Life
Cycle (STLC) which is similar to the development cycle. There are following six phases in
Software development life cycle model:

 Requirement analysis
 System Design
 Implementation or Coding
 Testing
 Deployment
 Maintenance

Fig 2 Waterfall Model

Page | 20
  Requirement Analysis − All the potential requirements of the developing system have
been captured at this stage and a requirement has been documented in the
specification document.

 System Design − The requirements above phase are studied. And the system design
is prepared. This system design helps to specify hardware and software requirements
and it helps in defining the overall system architecture.
 Implementation – The design phase inputs are used in this phase and the system is
first developed in small programs called units and then these units are integrated in
the next phase. Each unit is developed and tested for its functionality, which is
known as Unit Testing.
 Testing − All the units developed in the implementation phase are integrated into one
system after testing of each unit. Post Integration the whole system is tested for any
flaws and failures.
 Deployment – Once all testing is done, the product is deployed in the customer
machine or released in the market.

 Maintenance − There are some issues may come in the client environment. To fix
those issues, patches are released. Some better versions have been released to
increase the product. Maintenance is done to deliver the changes in the customer
environment.

3.1 PROBLEM DEFINITION

The online café system covers the various issues-  The customer can
order his food from anywhere.
 It saves times for customer.
 It is convenient way of ordering.
 It shows us variety of dishes by menu of the restaurant.
 Customer can compare the price as per their choice of dishes.
 They can have the table reservations before the time the want to visit the restaurant.

Page | 21
 Problems in existing system
It is true that human made mistakes as a computer are always accurate. The manual
system can have problems with paper-based work. We have seen some problems that are
covered in this project.
We will categories these problems in following types –

• Technical Problem
The following are some technical issues with existing online cafe system
 It requires space for keeping all the registers and files of the cafes i.e., Menu.
 Difficult to maintain the ordering record by owner or manager.
 Less Secured
 Difficulties in checking the availability of tables which are not reserved.
 Files may be damaged by cockroaches or some insects.

• General Problem
General problems include that basic file and data organizing system for existing system.
Some of them are following

 Required more time for searching old files and details of the dishes and menu’s. 
No proper stores and organization technique for the files and data of customers.
 Require lot of paper invoice for the orders.
 Difficult to prepare Ingredients reports on daily basis.
 Difficult to remember prices for small-small dishes.
 Its also difficult to manage the tables record.

• Financial Transaction / Data Calculation

The following are some data problems can be there in existing shopping system.
 Sometime the manual calculation may be incorrect.
 Difficulty to generate the correct number of vegetables reports for daily uses.

 Difficult to manage customer’s record in more crowd for getting tables.

 Sometimes Difficult to have card transactions.

Page | 22
All the above issues are covered in online restaurant system.
 The system is work on computer, so there are no chances of calculation problem.
 There is a separate database records stored in a hard disk.
 It provides most secured way for ordering food online.
 Easy to generate daily vegetables need reports.
 Easy to check the available dishes and the Ingredient which will be used for dish.
 User friendly GUI.

We are going to build a software café automation system that will have several features such
as:

Stock management

Internet online reservation

Online ordering via network enabled handheld computer

Customer management

Accounting
Executive information system

In addition to those features, we are planning to add

Statistical data about sales using graphics

Customer profile (customer name, address, preferences, etc.)

Problem Solution :
We tried to make the problem more obvious. Because of the fact that the project is in
abstract state now, we tried to concretize the project. To achieve that, we tried to think about
the similar software examples that are used in real life, like restaurants. One of the reasons to
do that was to draw the borders of the problem, how much we can achieve. After drawing the
borders of the problem, we divided the solution into several parts, which may change during
the development of the project:

Online Reservation: Customers will be able to give their orders via internet. In order to
achieve this, we are planning to build this part of project in .NET, as this platform has
many facilities in this area.

Page | 23
 Wireless Connection: This type of connection will be used to establish the connection
between the hand terminals and main computer. We are planning to use .NET
platform as it has many facilities to generate source code for PDAs. Hand terminals
are going

to be used for getting the orders from customers and transforming these to the main
computer.
Statistical Analysis: In this part statistics about the products and their sales will be
generated. These statistics will be displayed by graphics. This is an extra part for the
problem solution in order to ease the sales management.
Customer Profile: This is another extra part in order to know the customer and his/her
preferences better. The information such as customer’s name, favourite food, address,
phone number, birthday (system will send automatic greeting via SMS) will be hold
in database.
Database Management: At the moment we are going to use MySQL as database
management system. Database will hold the information and data coming from
online reservation system, hand terminals, stock management system and customer
profiles.
Database management is going to be the most frequently used part of the project.

3.2 REQUIREMENTS SPECIFICATION

System requirements are presented in a software requirement document which is

called as SRS. The software requirement specification (SRS) is the official statement of the
task or project that what is required for the system developers. The system requirement
document includes the requirements specifications and software requirements. The
software requirement document is not a created or designed document. The requirement
specification should be set in this document then the document will complete and
consistent. It is the process of gathering information about the project and product. It is a
problem solving activity which works on renewal of existing system or a new proposed
system. In system analysis all the requirements i.e., inputs are identified and a brief study on
it and the results should be written in a document which is called as SRS document.

Page | 24
The software requirement specification document should satisfy the following:

• It should cover the existing system features.

• It should be easy to change.

• It contains new techniques for better environment

• It acts as reference document for future activities.

• It should fulfil customer requirements.

In requirement analysis, we have to find out what are the requirements for our project and
it can be come from existing system and from new ideas for the project. According to all
requirements, we specify each requirement and study about to check whether it will be fulfilled
or not. Following is the existing system-

• Existing System:

The existing online cafe system is the manual going to a physical restaurant and order
the food. From the dishes available in the menu customer can buy it. It helps in to try the
item
and views the price differences.

The following are the drawbacks of physical or manual cafe system-

1. The customer must go to physical restaurant for buying the food.

2. The customers get fewer choices because of not maintained data.

3. It is difficult to choose the right restaurant from available restaurant.

4. No extra description about the dishes is given.

5. The customers need to allocate extra time from their work for going till cafe i.e., it is
time consuming process.
Page | 25
 6. The customers need to wait in a queue at the tables counter to get a place to sit and
have a lunch/breakfast.

7. It is fewer users friendly.

8. The customer has to find space for parking their vehicles.

9. No user review for the restaurant or dish in menu.

• Proposed System:

In proposed system i.e., online restaurant system the customer doesn’t need to go to
physical restaurant for ordering the food or beverages. The customer can order the item
through online restaurant website from computer or from mobile. The admin receives the
order online and process it for delivery. The customer may wish to pursue any food or
beverages from online restaurant can buy it. There is different requirement for the
proposed product.

• Functional requirements
The system should provide the following features and functionalities-
 The system should maintain records of all the items that are supposed to be
delivered
online.

 The system should keep record for all transaction that the customers do.

 Maintain the record of all customers, their login information, session state, their
wishing products and cart information.

 The system should keep track of delivery of the product.

 Temporary storage for non-registered users.

 It stores all the feedbacks and complaints send by the customer.

 The system should store the record of customer that they order.

 The system needs security system to prevent data from hacking.

 The records are updated and deleted.

Page | 26
 • Non-Functional Requirements

The non-functional requirements are the system integrity and failure maintenance. The
following are some non-functional requirements-

 Performance – The system should perform well in 24x7 manners. It should not give
low performance after some time.
 Security – The system should be secured with security protocols like https and SSL
certification.

 Portability – The system should be run on any operating systems like in Windows,
Linux, UNIX, and Mac OS.

 Reliability – The system should be more reliable i.e.; the failure rate should be less. In
other way the system should not fail in less time, it should work for a long time.

 Maintainability – The maintenance cost should be very high. If the systems fail then it
should be repaired in less time with less cost.

 Extensibility – The system should be capable for adding new modules and new ideas.

 Reusability – The system can be reused for making new software similar to it. Its
codes
and flow can be applied in different software development.

The System aims at providing an efficient interface to the user for managing of
inventory, it shall also provide the user varied options for managing the inventory through
various functions at hand. The ingredient levels are continuously monitored based on their
usage and are checked for the threshold levels in the inventory and accordingly the user is
alerted about low levels of certain ingredients. The design is such that the user does not
have
to manually update the inventory every time, the System does if for the user.

The System calculates and predicts the amount of usage for specific set days that are
pre-set by the user(admin) , it also alerts the user of an impending action to order
ingredients before the specific day set by the user. Therefore, the user never has to worry

Page | 27
about manually calculating the estimated usage of the ingredients as the System does it for
the user.

The simple interface of the System has functions like adding a recipe, removing or
updating the recipe. It also extends to functions such as adding a vendor for an ingredient,,
removing the vendor, checking threshold levels, processing orders, altering processed
orders
etc.

Usability
The system must be easy to use by both managers and chefs such that they do not need to read an
extensive number of manuals. o The system must be quickly accessible by both managers and
chefs.
o The system must be intuitive and simple in the way it displays all relevant data and
relationships.

o The menus of the system must be easily navigable by the users with buttons that are easy
to understand.

Reliability
o The System must give accurate inventory status to the user continuously. Any inaccuracies are
taken care by the regular confirming of the actual levels with the levels displayed in the system.

o The System must successfully add any recipe, ingredients, vendors or special occasions given by
the user and provide estimations and inventory status in relevance with the newly updated
entities.

Performance
o The system must not lag, because the workers using it don’t have down-time to wait for it to
complete an action.

o The system must complete updating the databases, adding of recipe, ingredient, vendor and
occasions successfully every time the user requests such a process. o All the functions of the
system must be available to the user every time the system is turned on.

o the calculations performed by the system must comply according to the norms set by the user
and should not vary unless explicitly changed by the user.

Page | 28
Feasibility Study
After all the requirement specification a feasibility study is prepared which will show us
that the project is feasible or not i.e., the project is worth doing or not. It estimates the
rough development cost of the project which describes the profit from the project. In
feasibility analysis we should study the following feasibilities-

1. Technical Feasibility

The technical feasibility deals with the available resource for development. That is, it works
with availability of hardware and software resources required for the development of the
project. It gives the idea that the project should be completed in available resources only.
The project should be compatible with available resources. After the study we can conclude
that we further proceed for the development in available resources.

2. Operational Feasibility

Operational feasibility is the study of all the problems that will be facing in the
development of the system. It is study of user interaction with systems and operations
performed by the user. It defines the how the data input process with the system. Our
system should be made in such a way that it should perform the all the operation that a user
can do. It should be user friendly. After the study of operational feasibility, we conclude that
our
system should capable of running all the inputs.

3. Financial Feasibility

It is the measure of cost benefit analysis estimates of the project. It is the study of the
estimated the economy required for the project. The development and operational cost are
estimated at this level. The possible benefit of the financial feasibility is to resolve and find
the finance problem related with project. However, when all requirements are gathered, we
can estimate the cost of the project. The finding cost and benefit for the project is called as
cost benefit analysis. It may have some issue if user does not have clear requirements. All
the

Page | 29
costs required for hardware and technology.

From the entire above all the studies we conclude our benefit or profit in doing this
project. After the feasibility study a valid business case is prepared. Requirement is gathered
about the proposed system. Requirement elicitation can be complex and difficult for the
project. The study could be a part of a strategic planning which examines a range of
potential
software developments.

3.3 PLANNING AND SCHEDULING

Project Planning
Planning is an identification of all of the tasks to be performed in the scope of the project
and the technical and business constraints. It is also referred as efforts for each activity or
tasks. Project planning identifies uncertainties associated with a project. Planning is done
after a valid business case and feasibility study. Planning gives the demerits of the system, so
that we can modify the project objectives to improve the project. This means that planning
for adding new features to the system. A major principle of project planning is to plan in
outline first and then in more details as the time to carry out an activity approach.

Planning is required for various stages and regions-

Page | 30
 Fig 4 Project Planning and Scheduling

Planning is an identification of all of the tasks to be performed in the scope of the

project and the technical and business constraints. It is also referred as efforts for each
activity or tasks. Project planning identifies uncertainties associated with a project.
Planning is done after a valid business case and feasibility study. Planning gives the
demerits of the system, so that we can modify the project objectives to improve the
project. This means that planning for adding new features to the system. A major principle
of project planning is to
plan in outline first and then in more details as the time to carry out an activity approach.

Here comes the most popular part of the project management process. Newbie
project manager things this is the only and the most important part of project
management. Though not entirely true, project scheduling plan is important. Some
organizations have specific people, designation called project scheduler or project planner
to take care of project scheduling process. It involves taking into account deliverables,
Page | 31
 milestones, task schedules, dependencies, resources, cost, baseline, critical path, Gantt
chart, etc.

Gantt chart

The following Gantt chart is prepared in Microsoft excel 2019

Fig 5 Gantt chart

Gantt charts are used for planning and scheduling project activities. The Gantt chart
gives the clear picture when activities will actually take place and highlights which one will
be executed at the same time. Activity network can be misleading in this project. The Gantt
chart is a horizontal bar that represents the project plan visually. The following Gantt chart
shows the activities that are planned for developing online shopping system. It shows each
activity time schedule, start date, activity completion date.
As You Planning or Managing Project

• Before you start managing projects, you need to understand goals and objectives
• You also need to set and manage expectations of project sponsors, customers and
other
stakeholders

Page | 32
• Project managers also need to set a clear understanding of expectations from project
team members
• Developing a high-level project deliverable timeline as well as detailed schedule
(Gantt Chart, Agile/Kanban)
• Set a project budget and estimate the cost of project
• Identifying right resources to carry out project activities
• Establishing and enabling a common platform for identification and addressing
project
issues and project risks
• Set a process to submit, evaluate and approve project change requests
• Controlling project during its execution and concluding it for completion
As you see look at above list, you realize, a lot of work goes into project even before kicking
it off. That’s where the project planner, project manager has to do solid homework or call it
drawing room work.
For planning and managing projects, there are various documents project manager has to
consider, refer, prepare, share and update such as
• Project charter that establishes
• Project goals,
• Objectives,
• Background and
• Approach
• Project scope document or project requirement document
• List of project deliverables
• Project Constraints/assumptions
• Exclusion list of requirements/deliverables
• Project Schedule
• WBS
• Task Schedule
• Milestones
• Project cost plan
• Budget
• Estimated cost
Page | 33
 • Actual cost tracking mechanism
• Billing/revenue
• Margins/profits,
• Resource management plan
• Other supporting plans
• Risk management plan
• Quality management plan
• Change management plan
• Document control plan
• Communication plan
• Other approvals, sign off approval process

3.4 SOFTWARE AND HARDWARE REQUIREMENTS

• Hardware Requirements:
The hardware serves as a tool in development of this proposed study. The following
hardware specifications should be considered for the development of the website and system.
Hardware Unit Specification:
Device name LAPTOP-PN355JRA
Processor Intel(R) Core(TM) i5-10300H CPU @ 2.50GHz 2.50
GHz
Installed RAM 8.00 GB (7.83 GB usable)
Device ID 7D0F669E-2DFB-4CE6-ABB2-75FD680137C4
Product ID 00327-35888-87943-AAOEM
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display
• Software Requirements:
The software provides the standard structure of the proposed study to make sure that the
needs are met during testing and the realization of the system.
Operating System: Windows XP or Higher version
Developing Tools: Asp.Net, Adobe Photoshop
Scripting Language Html, C#.
Database: SQL database.

Page | 34
Software Connectivity: USB Driver, XAMPP, Internet
Hardware and Software Requirements
In developing this system, the proponents are both hardware and software recommended.
The Hardware Requirements and Software Requirements Specification are produced at
culmination of analysis task. As part of the system engineering, the software and hardware
allocated functions and performance are refined by establishing complete details, display
requirements and design barriers, appropriate verification criteria and other data according to
the requirements.
The system which can provide the online shopping services for the customer to be able
to help the customer for selecting his item and to help the owner in managing the orders from
the customers.

Use Cases
A use case diagram that is part of the Unified Modelling Language (UML) which was
introduced in Section 2.6 gives a graphical overview of the functionality of a system. A use
case diagram consists of actors that are normally the stakeholders of the system and their use
cases commonly defined as goals.
Use Case Model
Use case modelling is one of the commonly applied modelling techniques in
requirement modelling. Its primary use is to capture interactions between users with the
system. Interactions that occur within a system could be user interactions such as input
gesture, communication with external systems, or collaboration between components of the
system. Knowing users’ preferred ways to interact with the system also allows developers to
capture precise requirements and build a more usable system.
Use cases are simple descriptions of system features from the point of view of users.
Use cases also capture scenarios of what the user could perform with the system and the
expected response from system. Nevertheless, a use case is often used to capture functional
requirements of the system and generally are inappropriate for non-functional requirement.
Use case modelling involves two major artefacts: use case diagram and use case description.

Use Case:

Page | 35
 Manage recipe collection Description User intended to create, update or delete recipes
Actors Chef Scenario The use case starts when user elects to manage recipe collections from
command menu. The system will present a collection of recipes. The user then can elect create
update or delete actions. Create and Update recipe will prompt user to input the details. Delete
action will remove the recipes from database. After selected action is completed, the user
confirms to persist the result.
MYSQL
• A structured collection of data is database. It can be text, number, images etc.
• MySQL is the database management system.
• MySQL (My Sequel) is the world's most used open-source relational database
management system (RDBMS) and it is a popular choice of database for use in web
applications.
• It is developed, distributed, supported by ORACLE.
• MySQL is used to store, access and modify the data in database.
• MySQL is the main component of the LAMP () software. Explanation for LAMP is
"Linux, A- Apache, MySQL, Perl/ PHP/ Python".
• MySQL user interface is very user-friendly and flexible to design and maintenance of
the data.
• MySQL is very fast, multi-threaded, multi-user and robust SQL database server.
MYSQL
• A structured collection of data is database. It can be text, number, images etc.
• MySQL is the database management system.
• MySQL (My Sequel) is the world's most used open-source relational database
management system (RDBMS) and it is a popular choice of database for use in web
applications.
• It is developed, distributed, supported by ORACLE.
• MySQL is used to store, access and modify the data in database.
• MySQL is the main component of the LAMP () software. Explanation for LAMP is
"Linux, A- Apache, MySQL, Perl/ PHP/ Python".

• MySQL user interface is very user-friendly and flexible to design and maintenance of
the data.

Page | 36
• MySQL is very fast, multi-threaded, multi-user and robust SQL database server.

Features of MySQL

• RDBMS
A relational database stores data in different tables rather than putting all the data in a
large storeroom. The database structures are organized into files. The data speed is very fast,
when we retrieve the data from files. The logical models with objects are database, tables,
views, rows, and columns. It gives the flexible programming environment. Rules between
tables are one-to-one, one-to-many, unique, and required. The database is very flexible and
easy to maintain.

Open Source
MySQL is open-source software i.e., anyone can download it from internet by free of cost.
• MySQL Limits
MySQL supports for large database. MySQL server can be used for a database that can
contain 50 million records. MySQL supports up to 64 indexes per table.
• Connectivity Languages
MySQL programs can be written in many languages. The languages are C, C++, Eiffel,
Java, .NET, Perl, PHP, Python, Ruby, and Tcl etc.

Page | 37
 Online Cafe Management System Use Case Model

Fig 10 Admin management

Shows the Online Cafe Management System use case diagram illustrates the

interaction between the user and the system. Reserve Service

Page | 38
 Fig 11 Customer Table Reservation

Use Case Description

The table below describe the function, condition and alternative flows to be met of all the
entities used in the use case diagram.

Manage Package

Page | 39
 Fig 12 Admin Manage Package

Shows the Online Restaurant Management System use case diagram illustrates the flow on
how the admin manage packages.

Manage Reservation

Fig 13 Data of Modifying reservation

Shows the Online Restaurant Management System use case diagram illustrates the interaction
between the user and the admin.
Manage Inventory

Fig 14 Inventory Management

Page | 40
Shows the Online Cafe Management System use case diagram on how to
manage the flow of inventory.
Class Diagram

Class Diagram

Activity Diagram
Activity diagram help people on the business and development sides of an organization come
together to understand the same process and behaviour. It demonstrates the logic of an algorithm.
It is used to improve any process by clarifying complicated use cases. It also models architecture
elements such as method, functions, and operations.

Symbols of Activity diagram-

Name Symbol Description

Start Represent the start of a process or

task.

Activity Indicates the activities that make up a

modelled process.

Connector Show the control flow of activity

Synchronization bar Combines two concurrent activities

into one activity.

Fork Splits an activity into two concurrent

activities.

Decision Represent a decision i.e., has two parts

true, false

Page | 41
 Flow Final Represent the end of a specific process
flow

End End of an activity

Table 4 Symbols to Represent Activity Diagram

Activity Diagram for Admin

Page | 42
Fig 16 Admin Side Activity Diagram

Page | 43
 Fig 17 User Side Activity Diagram

CHAPTER 4: SYSTEM DESIGN

Systems design is simply the design of systems. The design of the online shopping
system involves the design of the different module, web pages for listing the products,
Page | 44
searching and buying the product. Design also made for products description display and the
complete specification for the product.

Designing involves-

• designing of various blocks for system

• designing various databases

• designing of user interface and modules

• designing of I/O system

It implies a systematic and rigorous approach to design the system. It is an approach

demanded by the scale and complexity of many systems problems. It involves the module,
user interface, control flow chart, different validation check, test cases design etc. Following
are described some system design components –

4.1 Basic Modules

The online shopping system has following modules-

• Admin Module

The administrator is the super user of the online shopping system. The admin has

right to access the admin page. The admin has all information about users, products, orders

etc.

Administrator tasks-

• Can change the product price, description.

• Can add products to different categories.

• Can delete or modify the product.

• Manage orders i.e., view order and process them.

• Manages users.
• Generate reports of sales.

Page | 45
 • User Module
The user can be anyone who visits the website. The user can do the following tasks-

• Login – if the user is registered then we can login to the system else can-do registration for
future use.

• Registration – The visitor can registration by providing his details to the system.

• User can search for a product for viewing or buying purpose.

• User can view the product details, price, and description.

• User can buy a product or add to the cart.

Page | 46
 • Update the cart
• After user make confirmation the order for a product.

• Further user can cancel the order.

4.2 DATA DESIGN

Page | 47
4.2.1 Schema Design
The schema design refers how the database is constructed and organization of data in
database. The schema design shows the relationship between different columns with the
use of constraints. It is a graphical representation of database. The following is schema
design for online shopping system -

Fig 22 Schema Design

A component diagram is part of UML and its main purpose is to show the structural
relationship between components in the system. A component diagram is useful for this
system as it shows the higher architecture, as shown in figure

Data Layer
The Data Layer is responsible for storing and retrieving data to/from the relational database.
Here, the database is mapped to entity classes with the help of Entity Framework (EF). The
EF is an object relational mapper that enables .NET developers to work with relational data
using domain specific objects. It eliminates the need for most of the dataaccess code that
developers usually need to write [8]. The Data Layer has two components, namely Data
Entity and Data Providers. The Data Entity maps tables in the database to the classes using
the EF mapping files. It avoids writing more SQL queries to fetch and store data from the
database. Similarly, Data Providers has the query logic for create, read, update and delete
(CRUD) operations. This layer provides a set of interfaces to the Business Layer for accessing
its functionalities

Page | 48
Database Design Concepts
The database was the backbone to some highly important functional requirements,
therefore the schema (Figures 4.3 and 4.4) needed to have the structure to deal with them.
Some important design concepts of the database are:
• Ability to store prepared ingredients to reduce the size of the meal ingredient list. Recall,
that a prepared ingredient is a collection of ingredients.

• Ability to allow numerous options for optional ingredients within meals so that every
ingredient (or prepared ingredient) is part of a category. If an ingredient is optional, then
that ingredient should be able to be removed or swapped with any other ingredient in the
same category.

• Ability to control the stock levels by allocating a variable to all prepared ingredients and
meals with the variable reacting in real time to the status of the item’s ingredient stock
level.

• Ability to cope with new supplies where the price differs to the current price within the
database.

Fig 22 Database Design Concept

4.2.2Data Integrity and Constraints

Constraints used for data integrity-

• NOT NULL – It does not allow the customers to blank any columns while registering or ordering
a product.

Page | 49
 • UNIQUE - Ensures that all values in a column are different. The customer username should be
different for different users.

• PRIMARY KEY - A combination of a NOT NULL and UNIQUE. Uniquely identifies each row in a
table
• FOREIGN KEY - Uniquely identifies a row/record in another table, used to give relationship
between tables in database.

• CHECK - Ensures that all values in a column satisfies a specific condition

• DEFAULT - Sets a default value for a column when no value is specified

• INDEX - Used to create and retrieve data from the database very quickly
• An entity relationship (ER) diagram is a modelling language used to represent a type of semantic
data model of a system. The ER diagrams are often used to represent a relational database and
its requirements in a top-down fashion usually defined as the database schema. The database
schema for this database has been split into two ER diagrams.

• graphically shows the objects and their relationships that are contained within a meal. The meal
object will be made of at least two ingredients that can be either a normal ingredient or a
prepared ingredient. Note, a prepared ingredient is a collection of ingredients used to either
group commonly used ingredients or to group optional ingredients. Each ingredient will have a
default and manual measurement with the default measurement entered on input of the
ingredient and the manual measurement entered if the meal ingredient link requires a different
amount.

4.3 PROCEDURAL DESIGN

4.3.1 Logic Diagrams

A flowchart is a type of diagram that represents an algorithm, workflow or process. 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
analysing, designing, documenting or managing a process or program in various fields.

Symbols for flow Chart

• Terminal / Terminator

Page | 50
 The terminator shows the starting and ending of a process.

• Process / Rectangle

The Rectangle symbol is used to represent a process or an operation.

• Data (I/O)

The Parallelogram represents the data object shows the input to and output from
a process.

• Decision / Conditional

The Diamond represents a decision. This shape is used to ask a question and it
has two outputs, true or false and/or yes or no.

• Document

Document object is a rectangle with a wave-like base. It is used to represent a

document in a process flow.

• Subroutine / Predefined process

This means the flowchart for the predefined process has to be already drawn,
and you should reference the flowchart for more information

Page | 51
 Fig 23 Logical Diagram

4.3.2 Data Structures

A data structure is a specialized format for organizing, storing, and managing data.
General data structure types include the array, the file, the record, the table, the tree, and
so on. Any data structure is designed to organize data to suit a specific purpose so that it
can be accessed and worked with in appropriate ways.
The Online shopping system’s data is stored in tables in a database. We have used
MySQL for database purpose. All the records are stored in different tables in a database.
Data structure of Online Shopping is designed in a way that we can easily find the relation
between different tables and their columns.
Procedures are designed to detect invalid inputs in database at a lower level of detail. Data
validations have been provided in the system to check in almost every area where there is a
possibility for the user to commit errors. The system will not accept any invalid inputs.
Page | 52
Whenever an invalid data is entered in, the system immediately provides an error popup in
the user sections and the user has to again key in the data and the system will accept the data
only if the data is correct. Validations have been included where needed.
The system is designed in a user-friendly manner. In other words, the system has been
designed to deal efficiently with the user. The system has been designed with popup menus
in case of any error.
An effective MySQL database system of Online Shopping System saves the following
records-

• Customer personal information

• Customer ‘s orders

• Customer ‘s saved products i.e., cart

• The administrator information

• All customers password in encrypted format

• The product information including product id, product name, product price and
their description

• The all the orders from different customers.

• The customers feedback

• Cart information

4.3.3 Algorithms Design

User Side

• Customer Registration

Step1. Start

Step2. Enter Online Restaurant Site

Step3. Click on Registration Button

Step4. Fill the Registration form

Page | 53
Step5. Site automatic gives a Username and Password

Step6. Stop

• Placing an Order
Step1. Start
Step2. Enter Online Restaurant Site
Step3. Browse or Search a Restaurant
Step4. Click on View Menu
Step5. Click on Add to Cart Button

Step6. Login
Step7. Ordered Successful
Step8. Stop

• View Cart

Step1. Start
Step2. Go to Online Restaurant Site
Step3. Click on Login

Step4. Enter Username and Password

Step5. Click on Cart

Step6. A list of Cart Products will be displayed step

7. Add or Delete the dishes or hole order
Step8. Stop

• Explorer Dishes by Category

Step1. Start
Step2. Go to Online Restaurant Site
Step3. Click on Category tab
Step4. Select a Category

Step5. Select a Sub-category

Step6. All Dishes with selected Category and Sub-category will be displayed Step7. Stop

Page | 54
ADMIN SIDE

• Add Product

Step1. Start
Step2. Open Admin Section on Site

Step3. Admin Log In

Step4. Click on Add Menu to add Dish

Step5. Select Category, Sub-category, Image

Step6. Set price

Step7. Stop

• Delete Product

Step1. Start
Step2. Open Admin Section on Site
Step3. Admin Log In
Step4. Click on Delete Dish

Step5. Select Category, Sub-category

Step6. A list of Dishes will be displayed

Step7. Select Dishes checkbox

Step8. Click Delete Button Step9.
Stop

• View Order

Step1. Start

Step2. Open Admin Section on Site

Step3. Admin Log In
Step4. Click on View Order tab
Step5. All the orders from Customer will be displayed Step6.

Page | 55
Stop

• View Feedback

Step1. Start
Step2. Open Admin Section on Site

Step3. Admin Log In

Step4. Click on Feedback tab
Step5. View all the Feedbacks from different customers Step6.
Stop

• Edit Product Price

Step1. Start
Step2. Open Admin Section on Site
Step3. Admin log In

Step4. Click on Edit Menu tab

Step5. Select Category and Sub-Category to view the Dishes for editing

Step6. Select a Dish to Update Step7.

Set New price Step8.
Stop

4.4 USER INTERFACE DESIGN

The UI design deals with the communication between user and the system. It starts
with home page design and then other modules are designed. . These sketches are made by
gathering the information for the system. The GUI windows for the system are developed to
confirm the underlying GUI presentation software. The development of user interfaces

Page | 56
begins with early sketches of GUI windows. The different prototypes are made to get the
actual
design of the system.

Primary Window / Home Page

This window is basically remaining common for all the web pages. It has a bordered
frame contains different menus. It has the following menus or component-

• Title of Project

• Category Menu

• Product Menu under Category Menu

• A Menu bar with different buttons i.e., Home, about us, Contact, Cart etc.

• A Right-side frame where all the data will be displayed

• The right-side menu is changing on different input i.e., we click on login then login
form will be displayed etc.
Page | 57
User Interface for admin

The admin is the super user of the system. Admin have rights to make changes in
system. The rough sketch of admin side is given below-

Fig 25 Admin UI
The admin panel contains admin related tasks and operations that admin can
perform. It has title window, content window and task window. The content window
contain is changeable, when admin clicks on any operation, its related page will be open in
content
window. The task window contains all the task and operations of admin.

Use Case Diagram

A UML use case diagram is the primary form of system/software requirements for a
new software program under developed. Use cases specify the expected behaviour of the
system. Use cases once specified can be denoted both textual and visual representation
(such as UML). A key concept of use case modelling is that it helps us design a system from
end user's perspective. It is an effective technique for communicating system with external
users.

Page | 58
4.5 Security Issues

Security risks associated with e-commerce can be because of human error, an accident or
unauthorized access to systems. Online retailers are most likely to face credit card fraud or
data errors. Their online stores are also likely to face phishing attacks, distributed denial of
service (DDoS) attacks and man-in-the-middle attacks as explained below.

• Operating Level Security

This level of security provides a safety kit at times when any user free of worries and
tension and tension of how the software may behave if they provide wrong details in input at
any level of operating the software. For this several of security checks are made with the
software of the software with on the Spot correction making etc.

• Man-in-the-middle Attacks
As hackers are becoming smarter with technology, they are devising ways of
listening to the communications made by users of an e-commerce website. Through an
Page | 59
approach known as a man-in-the-middle attack, these hackers maliciously trick users into
connecting to a public wireless network. They gain access to people’s devices once they
are on public wireless networks. Hackers get to see a people’s browsing history, credit
card numbers, passwords and usernames if the websites they are visiting lack strong
encryptions.

• Distributed Denial of Service (DDoS) Attacks

This type of security threat aims at taking down an online retail store by sending
overwhelming requests to its servers. The attacks originate from thousands of
untraceable IP addresses. When this type of threat hits the servers, they slow down or
completely shut down.
An e-commerce site can also go offline temporarily when a DDoS attack affects its servers.

• Malware
In information technology, malware simply refers to malicious software programs.
Attackers usually inject web pages or files with these malicious programs to help them in
gaining access to online retails stores. Through means such as SQL injection, they can
easily insert the malware into a website’s database allowing it to compromise the data
stored in the database.
• Phishing Scams
E-commerce sites are also prone to phishing scams sent by known or unknown
people in form of emails. These scams focus on targeting important user data like credit
card numbers and login credentials. An attacker may use a scheme known as social
engineering to lure online shoppers to give out their personal information. When sent in
an email to an online shopper, a phishing scam may contain a link to a malicious site that
resembles an ecommerce site.
• Bad Bots
Bots, either good or bad, are all over the worldwide web. Search engines such as
Bing and Google use good bots for indexing search results. On the other hand, there are
hackers that use malicious bots for gathering data such as product data, inventories and
pricing data. These bots are also capable of accessing the database of an e-commerce site
and listing the logins of user accounts.
• Database Security
Page | 60
 The security of the databases that are used to store information from software in one
of the most necessary steps that should be kept in the mind while making the software
secure as all the data that is purpose. If, by mistake anything happens to the database, then
the entire software will be useless or is of no use. So, one should not provide access to
databases to the user of the software only for admin and if in some conditions it become
essential to give permissions to the users, then, one should provide read only, write only
etc. as permission types.

• Credit Card Fraud

Credit card fraud is the most common security threat that online retailers face. It
occurs when a hacker gains unauthorized access to customers’ personal and payment
information. To access this data, the hacker may penetrate the database of an e-
commerce site using malicious software programs. At times, a hacker’s intention when
stealing
customers’ data is to sell it on black markets.
The following are some methods to avoid security concerns-

• Use HTTPS:
HTTPS is a protocol used to provide security over the Internet. HTTPS
guarantees that customers interacting with the server are secured, and that nobody
else can intercept or change the content they're seeing in transit. We will use HTTPS
for our online shopping site to make it secured from attackers and hackers. We allow
the HTTPS to interact with user and the server and all queries should be pass through
this protocol. At the time of login, the HTTPS authenticate the user with server
database and maintain a session for a user, so that his session can be kept safe.

• Validate the Password:

The password validation for every user should do before login. We will
prompt the user to update or change after one month. We will also validate the
empty field provided by the user and prompt the user to fill compulsory these fields.
All the passwords stored in database will be encrypted format.

Page | 61
 • Up to date our website:

The online shopping system will be updated every day. We will backup and
restore the user files on separate location. It blocks the unwanted advertisements to
our website.

• Use Security Tools:

There are some tools which provide security to website. We will use them in our
website to make its data secure. Nets parker is good for testing SQL injection and
XSS. OpenVAS is most advanced open-source security scanner for scanning
vulnerabilities.

• Use a network firewall:

A web application firewall (WAF) can be software or hardware based. It sets

between your website server and the data connection and reads every bit of data
passing through it. It blocks the signal coming from an unknown network.

CHAPTER 5: IMPLEMENTATION AND TESTING

Implementation: Implementation simply means carrying out the activities described in our
project plan or putting our plan into action. Project implementation is the phase where
visions and plans become reality. This is the logical conclusion, after evaluating, deciding,
visioning, planning, applying for funds and finding the financial resources of a project.
Testing: Software testing is defined as an activity to check whether the actual results match
the expected results and to ensure that the software system is defect free. It involves
execution of a software component or system component to evaluate one or more
properties of interest.

5.1 IMPLEMENTATION APPROACHES

There are various approaches for implementing our project plan and strategy into
action. A food website implementation method is a systematically structured approach to
effectively integrate a Webpage-based service or component into the workflow of an
organizational structure or an individual end-user. Implementation approach focuses on the

Page | 62
process modelling side of the implementation of large product software, using the
implementation planning systems as the main component.

A food website implementation method is a blueprint to get users and/or

organizations running with a specific website product. The method is a set of rules and views
to cope with the most common issues that occur when implementing a software product:
business alignment from the organizational view and acceptance from human view. The
implementation of product software, as the final link in the deployment chain of software
production, is in a financial perspective of a major issue.

Implementation methods can on the one hand be used as a guiding principle,

indicating that the method serves as a global idea about how the implementation phase of
any project should run. This choice leaves more room for situational factors that are not
taken into account in the chosen method, but will result in ambiguity when questions arise
in the execution of the implementation process.

On the other hand, methods can be used as a profession, meaning that the method
should be taken strict and the usage of the method should be a profession, instead of a
guiding principle. This view is very useful if the implementation process is very complex and
is very dependent on exact and precise acting. Organizational and quality management will
embrace this view, as a strict usage of any method results in more clarity on organizational
level.

We have used DSDM method of implementation for our project. The power of
dynamic systems development method is that the method uses the principles of iteration
and incremental value, meaning that projects are carried out in repeating phases where
each phase adds value to the project. the possibility to execute different phases of the
implementation process iteratively enables the process to be executed by incrementally
aligning the product to be implemented with the enduser. In this way implementation
phases can be carried out incrementally and add value to important project aspects such as
the degree of acceptance, awareness and skills within every increment. We have designed
our project in increments. The incremental approach consists of successively realizing the
functional elements of the product that are directly usable. The project is divided into a
number of deliverable elements, which are called increments. Each increment is an
operational product, partially in the beginning of the cycle (with a reduced perimeter) and
totally in the end of the cycle (with a full perimeter).

Page | 63
 An increment is a coherent functional part of the final product. It is characterized by the
fact that:
• Each increment is like making a small part of big system.

• Each increment adds new features to the system.

• Each increment is tested as a final product.

The incremental approach is only possible if we have a clear idea of the software
application’s architecture and interfaces (we must not return to the parts that are
developed at each increment) and the expected features are separable (ability to be
developed independently).
So, first we have started with gathering the requirement. Initially, we were thinking of
making an online restaurant management system which helps peoples to reserve table
online. We were thinking that making this project is very easy because there are lots of
similar sites are available from there, we can grab our requirement. But that is not so easy,
we were confused that there are millions of Dishes in varieties are available, so we choose
Indian dishes and then we little moved to different categories.
After requirement gathering and analysis, we started planning for designing. We had
used different tools for flow and definition of design of system. First, we create design for
home page and there after we designed various different pages like login, register, Menu
display, About Us, and more. After each module design, we connect it to whole system.
Then we have stared with coding each increments and testing them as separate unit. In
initial phase of coding first we have done code for modules i.e. for each increment. After GUI
of admin using ASP.NET and CSS. Once the GUI coding is finished. We have started with SQL
data processing and validation coding using ASP.NET C# and Css. We have faced lot of
problems in coding. The designs and coding of increments are done with help of
implementation planning. The plan helps in testing each increment and according to testing
we have faced with different types of errors and bugs. We have done used unit testing,
integration testing for checking bugs and errors in system. Beta testing is used for user
acceptance and user satisfaction. We have done everything Successfully; the system has
been designed in response to the system analysis. All possible error in the program have
been eliminated. Necessary validation techniques have been used and normal, abnormal
and extremely data was used to test the system. After all the testing have done, the final
system is ready with some bugs that cannot be removed due to lack of skills. After all the
operable system is ready for deployment.

Page | 64
5.2 CODING DETAILS AND CODE EFFICIENCY

Some web development lifecycle phases

Planning
• What is the purpose of the Web site?
• Who will use this Web site?
• What are their computing environment?
• Who owns and authors the information on the Web site?

Analysis
• What information is useful to the user?

Design and development

• What type of Web site layout is appropriate?
• What forms of multimedia is helpful to the user?

Testing
• Is the Web site content correct?
• Does the Website functions correctly?
• Are users able to find the information they need?
• Is the navigation easy to use?

Implementation and maintenance

• How is the Web site published?
• How is the Web site updated?
• Who is responsible for content updates?

• Will the Web site be monitored?

Page | 65
5.3 TESTING APPROACH

Software Testing is a process of verifying a computer system/program to decide whether it

meets the specified requirements and produces the desired results. There are various approaches
for testing our project.

5.3.1 Unit Testing

What is unit testing?

Unit testing is a software development process in which the smallest testable parts of
an application, called units, are individually and independently scrutinized for proper
operation.
Unit testing can be done manually but is often automated.

Unit testing is a component of test-driven development (TDD), a pragmatic

methodology that takes a meticulous approach to building a product by means of continual
testing and revision. Test-driven development requires that developers first write failing unit
tests. Then they write code and refactor the application until the test passes. TDD typically
results in an explicit and predictable code base.

Unit testing involves only those characteristics that are vital to the performance of the
unit under test. This encourages developers to modify the source code without immediate
concerns about how such changes might affect the functioning of other units or the program
as a whole. Once all of the units in a program have been found to be working in the most
efficient and error-free manner possible, larger components of the program can be evaluated
by means of integration testing.

Unit testing does have steep learning curve. The development team needs to learn
what unit testing is, how to unit test, what to unit test and how to use automated software
tools to facilitate the process on an on-going basis. The great benefit to unit testing is that the
earlier a problem is identified, the fewer compound errors occur. A compound error is one
that doesn't seem to break anything at first, but eventually conflicts with something down the
line and results in a problem.

Before started with unit testing, first we understand the meaning of unit. So, unit is the
smallest part of software which includes codes, classes, and methods and can be tested
Page | 66
individually for correctness. Unit testing is a validation technique using black box
methodology which mainly concentrates on requirements of the system. In unit testing,
individual components and units are tested to ensure that they work as an individual as
defined in design.

We have selected register module for unit testing. The registration module field has
following fields –

Username
Password
Confirm Password
Type
Mobile Number
Email Id
Captcha Box
Enter Captcha Image
Link Button

The following tests we have performed on registration module –

 All fields should not be empty.

 Username Should be assign so that user can know the availability of that existing
name.
 Password should be with length between 5 to 8 char or digit.
 Confirmation of password is must for to know that fields are correct entered.
 Type should be confirmed.
 Email should be in a valid format.
 Check the captcha image gives the authentication or not.
 The proper characters should be entered which given in image.

 Link button for the one’s who had been registered.

 On click of Submit Button the user should be register Successfully.

Page | 67
Results after testing registration module –

 When any field is empty, it gives empty field warning.

 when user enter username then is check that this name should not repeat. If it in
database it will print “Username available”.

 When password is short than 6 digit or long than 8 digits, it gives password length
should be between 6 to 8 digits.
 When password and confirm password are not matches, it gives password not match
warning.
 Type is important to define

 When user enters email in invalid format, it gives Invalid email format warning.

 When mobile number length is less than 10, it gives mobile number length should be
10 digits warning.

 When user enters characters in mobile number field, it gives mobile number should
not take character value warning.

 When user enters captcha image then, if there is space then It will be not excepted

 If user clicks on register button, and all details are verified, user is registered with
site
and redirect to login module to proceed login.

So, we have tested register module and find that all the fields are working properly and
user will be registered successfully. In the similar way, all the modules are tested.

Page | 68
5.3.2 Integrated Testing
Integration testing involves integration of units to make a module / integration or modules
to make system integration. Integration testing may start at module level, where different units and
components come together to form a module and go up to system level.

Integration testing has following types –

• Bottom-Up Testing- In this type of testing, it focuses on testing individual units and
modules first and then goes upward by integrating tested and working units and
modules for system testing and intersystem testing.

• Top-Down Testing- In this type of testing, the top level of application is tested first and
then it goes downward until it reaches the final component of the system.

We have used bottom-up approach for testing our project. First, we start with testing the
lower units viz. are register, login and logout module. Then, we integrate them to test whether these
components functioning correctly or not.

Following tests have been performed for integration of these modules –

• After registration the user is logged in or not.

• Database is connected or not.

• On clicking logout, the user is logged out or not.

• User is authenticated from backend database record of that user or not.

• After logged in the status of Log-in changed to Log-out or not.

Results of integration testing are as follows-

• After the successful registration, the user is automatically logged in and a session has
started.

• Database is connected for fetching the user’s credential.

• On click of logout, the session is terminated, and the user is log-out.

• Whatever user enters into login field, if that are matches with database the user is
login.

• After log-in the status of log-in automatically changed to log-out.

So, we have completed integration testing of 3 modules. In the same way the other different modules are
integrated and tested together and tests are successful .

Page | 69
5.3.3 Beta Testing
Beta testing is a part of user acceptance testing and done by the end user to validate the
usability, functionality, compatibility and reliability of system. Beta testing adds value to the software
development life cycle as it allows the "real" customer an opportunity to provide inputs into the
design, functionality, and usability of a product. These inputs are not only critical to the success of
the product but also an investment into future products when the gathered data is managed
effectively. Also, the user checks that the software is working proper as they had suggested.

For beta testing of our project we handled our project to our friends and tell them to use it
and give us feedbacks. They used the project they find some difficulties and errors while registration,
it takes some time to sending mail to them and give unknown asp.net error while using some special
characters. This is because of using send mail as our mailing server, which is little bit slower than
other paid services for mail.

Following are success lines of system-

• They are easily able to register and login.

• They loving how the dishes are present in menu page.

• The Table reservation is user friendly.

• Look of the web pages were good.

• The Navigation bar is design nice.

• Password forget and change option was awesome.

• Minor Changes to loading of pages.

• Available in selected sizes.

So, after beta testing we conclude that our system is working correctly and user friendly but there are
some bugs that need to be fixed and new modification should be done.

Page | 70
5.4 MODIFICATIONS AND IMPROVEMENTS
As the testing was started, we might not expect that there are lots of errors occurred.

We have also improved our GUI to make it more user friendly. Following are some modification and
improvement we have done –

• Initially the user interface of system was not so attractive like all the Menu were
displayed on left side and were not looking good at main page, so we learned
attractive designing of site with advanced CSS and make them align with hovering
on
menu then Description will be displayed.

• On registration page, in username column it was giving error by not showing

availability but now it can be seen as you enter your username.

• Also, on the same form sql injection coding was disabled on every filed due to
which any attacker can able to attack the database directly. Then we modified our
system and used a function of ado.net (Server Explorer) which takes two
parameters, one is connection object to database and second is value from the
input field and make it stored in database and not allow the hacker to find a
loophole to the database.

• The password was not encrypted before, after that we have used encryption
function for encrypt the password and make it secure the system.

• Once the user was login successfully, the log in button was not changing. There
after we used session which is started after login and with help of if else statement,
we
modified the system.

• In Menu view page, the huge Dishes details were displayed on single line and it
was looking very crowded words. We used the new line tag of html to make them
displayed on different line. The “/n” separate the string values based on dot.

• We also need to make changes while adding the dishes images by giving Css to it.

Page | 71
 • On the reservation page, booking Id will be generated with table no and timing, so
that customer visit restaurant and say that booking id and admin can check the
data
for booked tables.

5.5 TEST CASES

Test Test Case Pre- Expected Actual Resul

Cas conditions t
e (Pass
ID /
Fail)
TC00 Customer Valid The customer The customer is Pass
1 Login username and should be able able to login
password to login

Invalid The It gives invalid Pass

username and customer username or
password should not password
be able to message and
login the user is not
able to login

Empty Gives empty It gives empty Pass

username and field field alert.
password error

TC00 Customer All valid The The Customer Pass

2 Registration credential customer is successfully
should able registered
to register

Mobile It should give It alerts mobile Pass

number mobile no. no. should be
in character should numbers
be
numbers error

Email is not in It should It alerts invalid Pass

proper format give email format
invalid
email
format

Page | 72
Page | 73
 Page|

69

Empty all It should give It alerts all Pass

textboxes empty field error fields should
not empty

Password is of It should give It gives Pass

5 digits password should password
be long than 6 should be at
digits error least 6 digits
long

Confirm It should It gives Pass

Password is give password and
password confirm
different from and password not
Password confirm match alert
password
not match
error
Mobile no. is It should It gives mobile Pass
8 digits or 12 give mobile number should
digits number be 10 digits
should be 10 long
digits error alert

Username is It should give It gives Pass

already username is username is
registered already already
registered registered

TC00 Admin Valid The admin The admin is Pass

3 Login username and should be able able to login
password to login

Invalid The admin The admin is Pass

username and should not able not
password to login able to login

Page | 74
 Page|

Empty It should give It gives empty Pass

username and empty field error field alert
password

70

TC00 Customer View of Food The appropriate Price can be Pass

4 Menu View list List can view confirm before
visit

TC00 Table All valid The Booking Id Pass

5 Booking credential customer Should generate
should able on label
to book
table

TC00 View the User clicks on The Dish image The Dishes are Pass
6 Dish View Dishes and details viewed full
should be
displayed

Page | 75
 Page|

71

TC011 View all Click on All bookings All bookings Pass

bookings Button should display are displayed
with with
appropriate appropriate
Username users

TC012 View all Click on Users All users should All users are Pass
Users button be displayed displayed

TC013 Logout Click on The admin The admin is Pass

Button Logout should be able to logged out
logout

TC014 Edit Product Click on The product The product Pass

edit button details should be details are
in product display in edit displayed in edit
view page fields fields

TC015 Edit User Click on The user details The user Pass
edit button should be details are
in user view display in edit displayed in
page fields edit fields

TC016 Delete User Click on The user should The user is Pass
delete button be deleted deleted
in user view successfully
page

Page | 76
 Page|

Table 6 : Test Cases Results

Page | 77