Online Food Ordering System

A Project Report Submitted by

Mansi Kadvani – 92200938221

in partial fulfilment for the Software Engineering

Diploma Engineering
in
Computer Engineering

Faculty of Diploma Studies

Marwadi University, Rajkot
2023-2024
 Marwadi University
Faculty of Diploma Studies
Computer Engineering Department
2023-2024

CERTIFICATE

This is to certify that the project entitled Online Food Ordering System has

been carried out by Mansi Kadvani – 92200938221, under my guidance in

fulfilment of term work, for the subject Software Engineering of 4th semester in

Computer Engineering of Marwadi University, Rajkot during the academic year

2023-24.

Date: ___________________

Subject Faculty Head of the Department

 Acknowledgement

The presentation of this report gives us a great pleasure and satisfaction in presenting this
report on my project work as a part of the final fulfillment for the Bachelor of Engineering.
We would like to take this opportunity to express our sincere gratitude to several people,
without whose help and encouragement, it would have been impossible for us to carry out the
desired work.
We are thankful to Prof. (Subject Faculty) for her help during our project duration, which
enabled us to complete our project with desired results. We are also very much thankful to all
other faculty members for their support throughout our study.
Last but not the least the most important of all out association to Faculty members and project
guide. They not only guided us throughout the project but also gave us a constant
encouragement, which instilled in us a confidence to make the best of this project. We are
heartily thankful to them.

With Sincere Regards,

Mansi Kadvani
ABSTRACT
 Index
Acknowledgements................................................................................................................i
Abstract.................................................................................................................................ii
List of Figures.........................................................................................................................
List of Tables...........................................................................................................................
List of Abbreviations..............................................................................................................

1 Introduction....................................................................................................................
1.1 Project Summary ......................................................................................................
1.2 Purpose.....................................................................................................................
1.3 Scope........................................................................................................................
1.4 Technology and Literature Review..........................................................................

2 Project Management.................................................................................................... 0
2.1 Project Planning and Scheduling………………………………………………...
2.1.1 Project Development Approach…………………………………………….
2.1.2 Project Plan…………………………………………………………………
2.1.3 Schedule Representation…………………………………………………...

2.2 Risk Management………………………………………………………………..

2.2.1 Risk Identification………………………………………………………….
2.2.2 Risk Analysis……………………………………………………………….
2.2.3 Risk Planning……………………………………………………………….

2.3 Estimation…………………………………………………………………………
2.3.1 Effort Estimation……………………………………………………………
2.3.2 Cost Analysis……………………………………………………………….

3 System Requirement Study......................................................................................... 0

3.1 User Characteristics..................................................................................................
3.2 Hardware and Software Requirements.....................................................................
3.3 Constraints………………………………………………………………………...

4 System Analysis............................................................................................................ 0
4.1 Study of Current System..........................................................................................
4.2 Problem and Weakness of Current System..............................................................
4.3 Requirements of New System..................................................................................
 4.4 Feasibility Study.......................................................................................................
4.5 Requirements Validation………………………………………………………….

4.6 Functions of System……………………………………………………………..

4.7 Data Modeling…………………………………………………………………..,

4.8 Functional and Behavioral Modeling……………………………………………
4.9 Main Modules of New System…………………………………………………..
4.10 Selection of Hardware and Software Justification………………………………

5 System Design............................................................................................................... 0
5.1 Database Design/ Data Structure Design………………………………………..
5.1.1 Mapping objects/ Classes to Tables (if non 00 languages)………………...
5.1.2 Tables and Relationship……………………………………………………
5.1.3 Logical Description of Data………………………………………………..
5.2 System Procedural Design………………………………………………………
5.2.1 Designing Pseudo Code or Algorithm for Method or Operations………….
5.2.2 Flow Chart or Activity Design………………………………………………

5.3 Input/ Output and Interface Design………………………………………………

5.3.1 Samples of Forms, Reports and Interface……………………………………
5.3.2 Access Control and Security…………………………………………………
5.3.3 State-Transition Diagram…………………………………………………….

5.4 System Architecture Design………………………………………………………

6 Implementation Planning and Details........................................................................ 0

6.1 Implementation Environment………………………………………………………

6.2 Program / Modules Specification…………………………………………………..

6.3 Security Features…………………………………………………………………...

6.4 Coding Standards…………………………………………………………………..

6.5 Sample Coding……………………………………………………………………..

7 Testing........................................................................................................................... 0

7.1 Testing Plan…………………………………………………………………………

7.2 Testing Strategy…………………………………………………………………….

7.3 Testing Methods…………………………………………………………………….

7.4 Test Cases…………………………………………………………………………..

8 Screen Shots and User Manual................................................................................... 0
9 Limitation and Future Enhancement......................................................................... 0
10 Conclusion and Discussion……………………………………………………………………….0

List of Figure

Figure No. Description Page No

Fig.1 Name of Figure

Fig.2 Name of Figure
 List of Table

Table No. Description Page No

Table.1 Name of Table

Table.2 Name of Table
 List of Abbreviations

Symbol Abbreviations

HTML Hypertext markup language

sql Structured query language.

RAM Random Access Memory

CSS Cascading style sheet

PK Primary key

FK Foreign key

APE As per expectation

 1. Introduction
1.1 Project Summary :

The food order app offers a user-friendly platform for ordering food with
essential features including user login and registration, category-wise menu browsing, adding items to
cart, and seamless checkout. Users can easily create accounts, providing basic information for
registration, and then log in to access the app's functionalities. The app categorizes menus based on
different types of cuisine or meal options, making it simple for users to explore and find what they're
craving. Once they've found their desired items, users can add them to their cart with a single click. The
checkout process is smooth and efficient, allowing users to review their orders and securely complete
their transactions. With these fundamental features, the food order app provides a convenient solution for
users to satisfy their food cravings quickly and effortlessly.

1.2 Purpose :

Goals :
• Provide users with a user-friendly interface for effortless menu exploration.
• Enable secure and efficient order placement and payment processing.
• Empower admin dashboard for streamlined management.

Objectives:
• Implement a responsive frontend for an engaging user experience.
• Utilize SQL database for efficient and organized data storage.

1.3 Scope :

What HungryHaven Can Do:

• Allow users to register accounts, browse restaurant menus, and place orders.
• Provide a secure and user-friendly payment process.

What HungryHaven Can't Do:

• HungryHaven does not handle real-time order tracking (for future
enhancements).
• We have only Site note have any Application (for future enhancements).

1.4 Technology And Literature Review :

Technology Stack:
The HungryHaven website is built upon a robust technology stack tailored to its specific
functionalities:
a) Frontend Development: The frontend is developed using HTML, CSS, CSHTML, and
JavaScript to create a user-friendly and responsive interface for seamless user interaction.
b) Backend : ASP.NET MVC
c) Programming Language: C# is the primary programming language for the backend
development, ensuring efficient code execution and compatibility with ASP.NET.
d) Database: SQL, a powerful open-source relational database management system, is
employed to store user data, information, and profiles.

Literature Review:
• Extensive research on existing online food ordering systems.
• Evaluation of technologies for frontend, backend, and database integration.
• Consideration of user feedback and web best practices to inform system design.
 2 . Project Management

2.1 Project Planning and Scheduling :

2.1.1 Project Development Approach :

Choosing a suitable strategy for project development is crucial

to the triumph of Hungry Haven. The approach selected for this initiative is the Agile methodology,
which emphasizes flexibility and cooperation. Its iterative structure conforms to the dynamic necessities
of an internet-based food ordering platform. The rationale behind this decision lies in its capacity to react
promptly to varying user inclinations, technological advancements, and market trends.

2.1.2 Project Plan :

The project plan for HungryHaven provides a comprehensive road-map for

the entire development life-cycle. It outlines key milestones, deliverable,and the roles and responsibilities of
each team member involved. This ensures a clear understanding of individual contributions and fosters
collaboration. Additionally, dependencies are meticulously identified and documented to facilitate a smooth and
synchronized workflow.

2.1.3 Schedule Representation :

A visual representation of the project schedule is essential

for effective communication and monitoring progress. The Gantt chart below illustrates the timeline, milestones,
and inter-dependencies of key tasks throughout the development phases of HungryHaven.

2.2 Risk Management :

2.2.1 Risk Identification :

Identifying potential risks is a crucial step in proactive risk
management. The project has conducted a comprehensive analysis to discover possible threats
to the successful completion of the HungryHaven project.
Key identified risks include:

1. User Acceptance: User preferences and expectations may evolve, impacting the
acceptance of the platform.
2. Data Security: Potential vulnerabilities in the handling of user data may lead to
security breaches.
3. Resource Constraints: Unexpected limitations in manpower or technology
resources could impede project progress.

2.2.2 Risk Analysis :

Each identified risk is individually assessed to understand its potential
impact and likelihood of occurrence.
1. Technological Challenges:
• Probability: Moderate
• Impact: High
• Mitigation: Regular communication and testing between frontend and
backend teams, coupled with agile development practices, can minimize the
impact.
2. User Acceptance:
• Probability: Low to Moderate
• Impact: Moderate
 • Mitigation: Continuous user feedback loops and a flexible development
approach to adapt to changing preferences.
3. Data Security:
• Probability: Low
• Impact: High
• Mitigation: Implementation of robust encryption protocols and regular
security audits.
4. Resource Constraints:
• Probability: Moderate
• Impact: Moderate
• Mitigation: Regular resource assessments, contingency planning, and
potentially outsourcing certain tasks if necessary

2.2.3 Risk Planning :

Strategies are formulated to manage and mitigate the identified risks
effectively.
1. Technological Challenges:
• Regular cross-functional team meetings to address and resolve integration
issues promptly.
• Continuous testing and code reviews to catch potential challenges early in
the development phase.
2. User Acceptance:
• Implement an iterative development approach to accommodate evolving
user preferences.
• Regular user testing and feedback sessions throughout the development
lifecycle.
3. Data Security:
• Implementation of industry-standard encryption and security measures.
• Regular security audits and updates to ensure the platform meets the latest
security standards.
4. Resource Constraints:
• Periodic resource assessments to identify potential constraints in advance.
• Develop contingency plans, including the possibility of outsourcing certain
tasks or bringing in additional resources as needed.

2.3 Estimation :

2.3.1 Effort Estimation :

2.3.2 Cost Analysis :

 3 System Requirement Study
3.1 User Characteristics :
Understanding the characteristics of the users who will interact
with HungryHaven is paramount for designing an intuitive and user-friendly system.
3.1.1 Types of Users:
• Customers: Individuals utilizing the platform to browse menus, place orders, and
track deliveries.
• Admins: System administrators responsible for overall platform management,user support, and
system maintenance.
3.1.2 User Requirements:
• Customers: Easy navigation, secure payment options, and real-time order tracking.
• Restaurants: User-friendly interface for menu management, order processing, and
analytics.
• Admins: Comprehensive dashboard for system monitoring, user management, and
reporting tools.

3.2 Hardware and Software Requirements :

Delineating the minimum hardware and software
specifications necessary for the optimal functioning of HungryHaven.
3.2.1 Hardware Requirements:
• Server Infrastructure: Dedicated servers with sufficient processing power and
storage to handle concurrent user requests.
• Database Servers: Robust database servers to efficiently manage and retrieve data.
3.2.2 Software Requirements:
• Operating System: Windows, macOS, Linux, or mobile OS (for mobile
access).modern JavaScript frameworks.
• SQL database management system.

3.3 Constraints :
Identifying and addressing various constraints that might influence the
development and deployment of HungryHaven.
3.3.1 Regulatory Policies:
• Compliance with data protection and privacy regulations, ensuring secure handling
of user information.
3.3.2 Hardware Limitations:
• Ensuring the system is designed to operate within the defined hardware constraints.
3.3.3 Interfaces to Other Applications:
• Seamless integration with payment gateways, ensuring secure transactions.
3.3.4 Parallel Operations:
• Managing concurrent user operations to maintain system efficiency.
3.3.5 Higher Order Language Requirements:
• Multilingual support to cater to a diverse user base.
3.3.6 Reliability Requirements:
• Implementing features for system backup and recovery to ensure data integrity.
3.3.7 Safety and Security Consideration:
• Encryption protocols and secure data transmission to protect user information.
3.3.8 Assumptions and Dependencies:
• Clear documentation of assumptions made during system design and dependencies
on external factors.