Veer Narmad South Gujarat University, Surat.

Department of Information and

Communication Technology

M.Sc. (Information Technology) Programme

Project Report

7th Semester

M.Sc. (Information Technology)

5 Year Integrated Course

Year 2022 – 2023

Online Food Order System

Guided By : Submitted By :

Mr.Naitik Shah(External Guide) Falguni Dabhi(E19110018000610018)

Dr.Shilesh Chaudhari(Internal Guide)

302 Sundaram Sky, Opp. Central Bank of India, Athugar Street, Nanpura, Surat,
Gujarat - 395001
 Index

Sr. No Topics Page no

1 Introduction
1.1 Company Profile 4
1.2 Customer Profile 5
1.2.1 Current System – about the 6
existing system (manual or s/w)
1.2.2 Customer Detail 6
2 Proposed System
2.1 Scope 7
2.2 Objective 7
2.3 Constraints – things that cannot be done 7
2.3.1 H/w Constraints
2.3.2.S/W Constraints
2.4 Advantages 7
2.5 Limitation – things that are not there, but 7
could be achieved
3 Environment Specification
3.1 Hardware & Software Requirements – things that 8
are needed for your s/w
3.2 Development Description 8
4 System Planning
4.1 Feasibility Study 9
4.2 Software Engineering Model 10
4.3 Risk Analysis 11
4.4 Project Schedule
4.4.1 Task Dependency 12
4.4.2 Timeline Chart 13
4.4.3 Project Table 14

5 System Analysis
5.1 Detailed SRS 14
5.2UML Diagram
5.2.1 Use Case Diagram 16
5.2.2 CRC
5.2.3 Class Diagram 19
5.2.4 Activity Diagram 20

2
 5.2.5 Sequence Diagram 25
5.3 E-R Diagram 28
6 Software Design
6.1 Database Design 29
6.2 Interface Design sitemap followed with 36
page snapshots
6.3 Architecture Design 62
7 Testing
7.1 Unit Testing 63
7.2 Integration Testing 63
8 Future Enhancement 68
9 Glossary 68
10 Reference 69

3
 1. Introduction:

1.1 Company Profile

Elite Technocrats
Elite Technocrats was established in 2015 to provide information
technology solutions for small to enterprise-sized businesses. Our mission from
the very first day has been to cultivate professional relationships with our clients
to provide efficient and reliable information technology solutions for their needs.
Elite Technocrats team is of highly-skilled developers with decades of experience
not only in information technology but also in business processes across a range
of industry sectors. This type of experienced team makes us uniquely positioned
to offer unparalleled solutions promising greater operational efficiency,
productivity gains and cost savings for each of our clients, regardless of their
industry.
As an established technology-intensive company, we pride ourselves
on providing a comprehensive suite of solutions comprising of Technological
consultancy, on/off-site services, mobile application development, custom
software & web development, manual testing, and enterprise architecture
consulting.

"At Elite Technocrats, we guarantee rapid, reliable and robust information

technology solutions that work."

1. Our Mission: – To provide cost effective, timely and technology driven

end-to-end WebSolutions to grow and enhance with every project.

2. Our Vision: –To Create and Think Forward giving complete Web Design Solutions;
tohelp grow your Brand and Business in the Market.

3. Our Goal: – To be among the top Web Development companies serving clients
around theworld, round the clock, thereby maintaining long-term relationship
with them.

Contact no: +91 98254 79404

Email ID : [email protected]

Website: http://www.elitetechnocrats.com/

4
1.2 Project Profile

Project Title Online Food Order System

Group Members Dabhi Falguni Ramehsbhai

College J.P. Dawer Institute of Information Science

and tech

Company Name Elitetechnocrats

Duration Three Months

Internal Project Dr. Shilesh Chaudhari

Guide

Submitted By Dabhi Falguni Rameshbhai

Submitted To Department Of ICT, VNSGU

5
System Configuration:

Project Title Online Food Order System

Front End Angular

Back End Asp.Net

Operating System Microsoft Windows

Language Asp.Net , Bootstrap , Html , CSS, Angular

Database Server IIS Server

Development Asp.Net,Angular
Environment

Front End Angular

6
2. System Specification

2.1 Scope

The Restaurant point of sale includes: Sales Order , Reservation.

This system will change the manual system of the business in order
for the user to work easier and provide faster reservation for the
customer.
2.2 Objective:

• Customer can Online Reservation.

• It is easy to use and easy to understand.
• Customer data will found very fast either for updating or
deleting.
• Manager can show datalist of the stock
• Message via Email.

2.3 Constraints
2.3.1Software Constraints:
 Any web browser .
 Internet Connection Required.

2.3 Advantages

 User Can easily Booking a Table.

 User can use the facilities online

2.4 Limitations:

 Payment and delivery not done Yet.

 Internet Connection is required.

7
3.Environment Specification

3.1 Hardware & Software Requirements:

Processor P4/Dual Core or Higher Frequency

Processor
Hard Disc 50 GB or Higher
RAM 4 GB or Higher
Key Board Microsoft Slim Key Board
Mouse Microsoft Optical Mouse
Monitor CRT, LCD, TFT (anyone can use)

3.2 Development description:

Software Requirements (for Development):

 Asp.net
 Operating System (for Development):
 IIS
 Microsoft Windows
 Javascript
 JQuery
 SQL Server
 HTML5
 CSS3
 BOOTSTRAP

8
4..System Planning

4.1.1 Feasibility Study

A feasibility study is an evaluation and analysis of the potential of the proposed
project which is based on extensive investigation and research to give full
comfort to the decisions makers.

 Technical feasibility:

A large part of determining resources has to do with assessing technical feasibility. It

considers the technicalrequirements of the proposed project. The technical
requirements are then compared to the technical capability of the organization. The
systems project is considered technically feasible if the internal technical capability is
sufficient to support the project requirements.

 Operational feasibility:

Operational feasibility is dependent on human resources available for the project

and involves projecting whether the system will be used if it is developed and
implemented.
Operational feasibility is a measure of how well a proposed system solves the
problems and takes advantage of the opportunities identified during scope definition
and how it satisfies the requirements identified in the requirements analysis phase
of system development.

 Economic feasibility:

As development tools and software are already we own, there isn’t any burden of
buying them. The organization doesn’t have the same system, so it is certainly
required for them. So here we do not need to invest extra funds to develop the
system. Thus, it is economically feasible to the organization.

 Time Schedule feasibility:

9
 Projects are initiated with specific deadline. We need to evaluate whether the
deadlines are mandatory or desirable. Time is the one of the critical factor in the
development of any system but this kind of feasibility is hardly perfect in any system.
We have been asked to complete the project within the working days of the
organization having period of 3 months approximately. So, we have managed to
complete the project before given deadline. In the project planning section, we
elaborate our ideas to develop the system within the given period.

4.2 Software Engineering Model

We followed Iterative Waterfall Model for Software development .So, we can
add new functionalities as per requirement.

10
4.3 Risk Analysis
• The probability of any unwanted incident is defined as Risk. In
Software Testing, risk analysis is the process of identifying the
risks in applications or software that you built and prioritizing
them to test. After that, the process of assigning the level of risk
is done. The categorization of the risks that takes place, hence,
the impact of the risk is calculated.
• Risks in our project

 Changes in database or model.

 Issues with designing after updating module.

11
4.4 Project Schedule

4.4.1 Task Dependency

Requirements Gathering

Requirements Analysis

Estimation Sc heduling

Designing

Coding and Integration

Testing

12
4.4.2 Timeline Chart

13
 5 System Analysis

5.1 Software Requirement Specification

The purpose of SRS is to write the functional and non-functional
systemrequirements that represent the characteristic of Restaurant point
of sale.This system must be designed as Employee required. So, the
complete requirement must be found.

 Features
 Admin:
 Login:
At the first admin need to login themself.
 Reservation:
o Admin can Show Reservation.
 Booking:
o Admin can show booking.
 Category:
o Admin can add ,edit ,delete and view
category.
 Item :
o Admin can add , edit, delete and view Items.
 Menu:
o Admin can add ,edit, delete and view Menu.
 Purchase:
o Admin can add, edit, delete and view
Purchase.
 Supplier:
o Admin can add, edit, delete and view
Supplier.
 Order:
o Admin can view Order.
 Table:
o Admin can add, edit, delete and view Table.
 User:
o Admin can add, edit, delete and view user.

14
Manager:
 Login:
o Manager can login using email and password.
 Employee:
o Manager can view Employee.
 Order:
o Manager can Add Order and view Order.
 Category:
o Manager can Add Category and Show Category.
 Item:
o Manager can Add item and Show Item.
 Stock List:
o Manager can show Stock list.
 Sales Report and Purchase Report:
o Manager can show sales reports and purchase
reports.

Client(Userside):
Customer:
 Home:
o Customer can view home page and our story.
 Reservation:
o Customer can Add a reservation.
 Menu:
o Customer can show Menu.
 Gallary:
o Customer can show Gallary.
 Contact us:
o Customer can contact the admin.

15
5.2 UMl Diagrams
5.2.1 Use Case Diagram

16
Manager:

17
Client(customer):

18
5.2.3 Class Diagram :

19
5.2.4 Activity Diagrams:

Admin Activity Diagram:

20
Manager Activity Diagram:

21
User Activity Diagram:

22
Login Activity Diagram

Login

23
Change Password Activity Diagram:

Change Password

24
5.2.5 Sequence Diagrams:
Admin:

25
Manager:

26
Client(Customer)

27
5.2 E-R Diagram

28
5.3 Database Design:
Table name : Booking
Element Name DataType Constraint Description

booking_id_pk int Primary Key Id Primary Key

table_id_fk int Foreign Key Table id foreign key
cust_id_fk int Foreign Key Customer id foreign
key
book_date Varchar Not Null Booking date
book_time varchar Not Null Booking Time
no_of_person varchar Not Null No of person
is_active tinyint Null Is active

Table name : Category

Element Name DataType Constraint Description

cat_id_pk int Primary Key Id

cat_name varchar Not Null Category id
is_active tinyint Null Is active

Table name : menu

Element Name DataType Constraint Description

menu_id_pk int Primary Key Id

menu_path varchar Not Null Menu Path
is_active tinyint Null Is active

29
Table name : customer

Element Name DataType Constraint Description

cust_id_pk int Primary Key Id Primary Key

cust_name varchar Not Null Customer Name
cust_email varchar Not Null Customer Email

cust_contact varchar Not Null CustomerContactno

is_active tinyint Null Is active

Table name : item

Element Name DataType Constraint Description

item_id_pk int Primary Key Id Primary Key

cat_id_fk int Foreign Key Category id Foreign
Key
item_name varchar Not Null Item Name

item_price varchar Not Null Item Price

item_image varchar Not Null Item Images
is_kitchen tinyint Null Is_Kitchen
is_active tinyint Null Is active

30
Table name : Order-item

Element DataType Constraint Description

Name

order_item_pk int Primary Key Id Primary Key

order_id_fk int Foreign Key Order id Foreign Key
item_id_fk int Foreign Key Item id Foreign Key

quantity varchar Not Null Quantity

price varchar Not Null Price
notes varchar Not Null Notes
is_active tinyint Null Is active

Table name : order

Element Name DataType Constraint Description

order_id_pk int Primary Key Id Primary Key

emp_id_fk int Not Null Emp Id Foreign Key
table_id_fk int Not Null Table Id Foreign Key

total_amount varchar Not Null Total Amount

date varchar Not Null Date
time varchar Not Null Time
emp_name varchar Not Null Employee Name
table_name varchar Not Null Table Name
is_active tinyint Null Is active
is_completed tinyint Null Is Completed
is_paid tinyint Null Is Paid

31
Table name :payment

Element Name DataType Constraint Description

payment_id_pk int Primary Key Id Primary Key

item_id_fk int Foreign Key item id Foreign Key
cust_id_fk int Foreign Key Customer id Foreign
Key
sub_total_amt varchar Not Null Sub total Amount
total_amt varchar Not Null Total Amount
payment_type varchar Not Null Payment type :
Cash,Check,UPI,Debit
date varchar Not Null Date
discount varchar Not Null Discount
cust_name varchar Not Null Customer Name
order_name varchar Not Null Order Name
is_active tinyint Null Is active

Table name : table

Element Name DataType Constraint Description

table_id_pk int Primary Key Id Primary Key

table_name varchar Not Null table name
no_of_person varchar Not Null No of person

is_book tinyint Null Is book

is_active tinyint Null Is active

32
Table name : purchase

Element Name DataType Constraint Description

prod_id_pk int Primary Key Id Primary Key

cat_id_fk int Foreign Key Category id Foreign
Key
supplier_id_fk int Foreign Key Supplier id Foreign
Key
prod_description varchar Not Null Product description

purchase_price varchar Not Null Purchase price

sales_price varchar Not Null Sales prices
prod_name varchar Not Null product Name
manufacture_date varchar Not Null Manufacture date
expire_date varchar Not Null Expire date
prod_quantity varchar Not Null Product quantity
prod_weight varchar Not Null Product weight
purchase_date varchar Not Null Purchase date
prod_image varchar Not Null Product images
is_tax tinyint Null Is Tax
is_active tinyint Null Is active

33
Table name : reservation

Element Name DataType Constraint Description

reservation_id_pk int Primary Key Id Primary Key

reservation_date varchar Not Null Reservation date
reservation_time varchar Not Null Reservation time

no_of_person varchar Not Null No of person

customer_name varchar Not Null Customer Name
customer_email varchar Not Null Customer email
customer_phone varchar Not Null Customer phoneno
is_active tinyint Null Is active

Table name : supplier

Element Name DataType Constraint Description

supplier_id_pk int Primary Key Id Primary Key

supplier_name varchar Not Null Supplier name
supplier_gstno int Not Null Supplier gstno

supplier_address varchar Not Null Supplier address

supplier_contact varchar Not Null Supplier contactno
is_active tinyint Null Is active

34
Table name : user

Element Name DataType Constraint Description

user_id_pk int Primary Key Id Primary Key

user_email Varchar Not Null User emailed
user_contact Varchar Not Null User contactno

user_name varchar Not Null User name

user_password varchar Not Null User password
user_type varchar Not Null User type
user_image varchar Not Null User images
is_active tinyint Null Is active

35
6.Interface Design
Admin:
Login

Dashboard

36
View Reservation

View Booking

37
Add Category

View Category

38
Add Item

View Item

39
View Customer

40
View Order

View Payment

41
Add Menu

View Menu

42
Add purchase

View Purchase

43
Add Supplier

View Supplier

44
Add Table

View Table

45
Add User

View User

46
Manager:
Dashboard

Choose Table

47
Take Order

Show Order

48
Kitchen Display

Add-item

49
Stock List

50
Add Category

View Category

51
 Sales Reports

Purchase Reports

52
 Show User

Employee :
Dashboard

53
Choose Table

54
Kitchen Display

Show Order

55
Client(customer)
Dashboard

Our Story

56
Weekly Deals

Opening

57
Our Restaurants

Our Team

58
Show Menu

59
Our Gallery

60
Add Reservation

Our Contacts

61
6.3Architecture Design
The MVC architectural pattern has existed for a long time in software engineering. All most
all the languages use MVC with slight variation, but conceptually it remains the same.

MVC stands for Model, View, and Controller. MVC separates an application into three
components - Model, View, and Controller.

Model: Model represents the shape of the data. A class in C# is used to describe a model.
Model objects store data retrieved from the database.

Model represents the data.

View: View in MVC is a user interface. View display model data to the user and also enables
them to modify them. View in ASP.NET MVC is HTML, CSS, and some special syntax
(Razor syntax) that makes it easy to communicate with the model and the controller.

View is the User Interface.

Controller: The controller handles the user request. Typically, the user uses the view and
raises an HTTP request, which will be handled by the controller. The controller processes the
request and returns the appropriate view as a response.

Controller is the request handler.

The following figure illustrates the interaction between Model, View, and Controller.

62
7. Testing

7.1 Unit Testing

This testing focuses on verification effort on the smallest unit of software

design-the component or module. Using the component - level design
description as s guide, important control paths are tested to uncover errors
within the boundary of the module. The relative complexity of tests and the
error those tests uncover is limited by constrained scope established for the unit
testing . The unit testing focuses on internal processing logic and data structure
with boundaries of the component. This type of testing can be conducted in
parallel for multiple components.

7.2 Integration Testing

• Once the modules were unit tested, integration testing was carried out to
ensure that the modules worked properly when interfaced with each
other.
• The main objective of integration testing was to ensure that ,
• No data was lost across the interface.

• No side effects were encountered while integrating the modules.

• Sub functions when combined produced the desired result.

• Numbers of input parameters are equal to number of arguments.

• Tests scenarios which were created in a specific format to carry out

functional testing were extensively used during this stage.
• Each time a new module was added as a chapter of integration
testing, regression testing was carried to ensure that changes have
not propagated any unidentified side effects.

63
• Admin Side:

Test Case 1

Description Login

Pre-Condition Admin should know username and password. Username and

password should not be empty.

Test action Allow access or deny access

Error Message Invalid user.

Test Case 2

Description View/edit/delete data

Pre-Condition Admin should login itself for view/edit/delete the data

Test action Edit/View/Deletion of data

Error Message Please enter details.

Test Case 3

Description Add/Edit/Delete Booking

Pre-Condition Booking details

Test action New Booking insert

Error Message Invalid Booking details

64
• ManagerSide:
Test Case 1

Description Login

Pre-Condition Manager should know username and password. Username and

password should not be empty.

Test action Allow access or deny access

Error Message Invalid user.

Test Case 2

Description View/edit/delete data

Pre-Condition Manager should login itself for view/edit/delete the data

Test action Edit/View/Deletion of data

Error Message Please enter details.

Test Case 3

Description Add/Edit/Delete Booking

Pre-Condition Booking details

Test action New Booking insert

Error Message Invalid Booking details

65
• EmployeeSide
Test Case 1

Description Login

Pre-Condition Admin should know provide username and password. Username

and password should not be empty.

Test action Allow access or deny access

Error Message Invalid user.

Test Case 2

Description View/edit/delete data

Pre-Condition Employee should login itself for view/edit/delete the data

Test action Edit/View/Deletion of data

Error Message Please enter details.

Test Case 3

Description Add/Edit/Delete Booking

Pre-Condition Booking details

Test action New Booking insert

Error Message Invalid Booking details

66
• Client Side:
Test Case 1

Description Login

Pre-Condition User should know email and password.

Test action Allow access or deny access

Error Message Invalid user

Test Case 2

Description Register

Pre-Condition Customer information

Test action Create new user

Error Message Invalid user details

Test Case 3

Description Book Reservation

Pre-Condition Login Required

Test action Create new booking

Error Message Invalid User details

67
7. Future Enhancement
 In future payment module can add.
 Customer can show time slot of the Restaurant.

9. Glossary

Dependency in a project network is a link amongst a project's terminal elements.

Duration of a project's terminal element is the number of calender periods it takes

from the time to execution of element starts to the moment it is completed.

Management in business and human organization activity is simply the act of getting
people together to accomplish desired goals. Management comprises planning,
organizing , staffing , leading or detection and controlling and organization or efforts
for the purpose of accomplishing a goal.

Planning in organization and public policy is both the organizational process of

creating and maintaining a plan and the psychological process of thinking about the
activites required to create a desired goal on some scale.

Project A temporary endeavor undertaken to create a unique product, service or result.

Risk management is a management specialism aiming to reduce different risks related

to preselected domain to the level accepted by society . It may refer to numerous
types of threts caused by environment,technology ,humans, organization and politics.

Scope of a project in project management is the sum total of all of its products and
their requirements or features.

Timeline is a graphical representation of a chronological sequence of events , aslo

referred to as a chronology . It can also mean a schedule of activities, such as a
timetable.

Work in project management is the amount of effort applied to produce a deliverable

or to accomplish a task(a terminal element).

68
10 . References
• www.w3schools.com
• www.stackoverflow.com
• www.youtube.com
• www.google.com
• www.themeforest.net
• www.tutorialsteacher.com
• http://codepickup.in/asp-net-mvc/razorpay-integration-in-asp-net-
mvc/

69