Vish Removed
Vish Removed
I express my sincere gratitude to Dr. Mukesh Kumar Gupta, Professor and Head,
Department of Computer Science and Engineering for providing me an oppor-
tunity to undergo In-house Internship programme at SKIT, Jaipur. I am thankful
to Mr. Manish Bhardwaj Coordinator (II year In-house internship 2022-23), for
his support, cooperation and motivation provided during the internship for constant
inspiration, presence and blessings. I also extend my sincere appreciation to Mr.
Manish Bhardwaj, Mr. Sumit Kumar, Mr. Pawan Kumar Patidar, Ms. Mamta
Sakpal, Mr. Loveleen Kumar, Mr. Madhav Khatri, Ms. Surbhi Sharma and
Ms. Priyanka Sharma who helped me in learning HTML, CSS, JAVASCRIPT,
PHP and SQL.
I also extend my I also extend my sincere appreciation to Mr. Alisha Goyal who
flourished and helped me in lab sessions conducted during internship.
I also extend my sincere appreciation to Mr. Manish Bhardwaj who provided his
valuable suggestions and precious time in accomplishing my report.
At last I must express my sincere heartfelt gratitude to all the staff members of
Department of Computer Science and Engineering, who helped me directly or
indirectly during this course of work.
1 INTRODUCTION 1
1.1 Problem Identification . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Project Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 Intended Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.4 Tools and Technologies to be used . . . . . . . . . . . . . . . . . . 2
2 METHODOLOGY 6
2.1 Software Model Used . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 Product User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . 8
2.3 Product Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.4 Design and Implementation Constraints . . . . . . . . . . . . . . . 12
2.5 E-R Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.6 Use-Case Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.7 Activity Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3 DEPENDENCIES 16
3.1 Assumptions and Dependencies . . . . . . . . . . . . . . . . . . . 16
3.2 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . 16
3.3 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . 17
4 NON-FUNCTIONAL REQUIREMENTS 18
4.1 Security Requirements . . . . . . . . . . . . . . . . . . . . . . . . 18
4.2 Scalability Requirements . . . . . . . . . . . . . . . . . . . . . . . 18
REFERENCES............................................................................. 33
A description of the background and context of the project and its relation to work
already done in the area. Made statement of the aims and objectives of the project.
The description of Purpose. Scope, and applicability We define the problem on
which we are working in the project. We describe the requirement Specifications
of the system and the actions that can be done on these things. We understand the
problem domain and produce a model of the system, which describes operations
that can be performed on the system. We included features and operations in detail,
including screen layouts. We designed user interface and security issues related to
system. Finally the system is implemented and tested according to test cases.
Here we can maintain the records of Food Item and Category. Also, as it can be seen
that now-a-days the players are versatile,i.e. so there is a scope for introducing a
method to maintain the Online Food Ordering System. Enhancements can be done
to maintain all the Food Item, Category,Customer, Order, Confirm Order.We have
left all the options open so that if there is any other future requirement in the system
by the user for the enhancement of the system then it is possible to implement them.