0% found this document useful (0 votes)
9 views

rtp final

The document is a project report for 'Spicy Bistro', a web-based platform designed to enhance customer interaction with restaurants by allowing online menu browsing, reservations, and feedback. It outlines the project's objectives, existing system limitations, proposed solutions, and technical requirements, emphasizing the need for a user-friendly and efficient dining experience. The report is submitted by students of Bhoj Reddy Engineering College for Women as part of their Bachelor of Technology degree in Computer Science and Engineering.

Uploaded by

myplaylist.271
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
9 views

rtp final

The document is a project report for 'Spicy Bistro', a web-based platform designed to enhance customer interaction with restaurants by allowing online menu browsing, reservations, and feedback. It outlines the project's objectives, existing system limitations, proposed solutions, and technical requirements, emphasizing the need for a user-friendly and efficient dining experience. The report is submitted by students of Bhoj Reddy Engineering College for Women as part of their Bachelor of Technology degree in Computer Science and Engineering.

Uploaded by

myplaylist.271
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 50

A Real Time Research Project Report on

SPICY BISTRO
Submitted in partial fulfillment for award of the degree of Bachelor of Technology in

Computer Science and Engineering

by

V Raja Sri 22321A0573

P Veda Samhitha 22321A0583

K Sai Sharanya 22321A0584

Under the Esteemed Guidance of


Coordinator
AVS Radhika
Assistant Professor, CSE

Bhoj Reddy Engineering College for Women


Department of Computer Science and Engineering
(Sponsored by Sangam Laxmibai Vidyapeet,Approved by AICTE & Affiliated JNTUH)
Vinaynagar, IS Sadan Crossroads, Hyderabad –500059
Ph: +91-40-24537282;Website:www.brecw.ac.in;Email: [email protected]

2023-2024
Bhoj Reddy Engineering College for Women
(Sponsored by Sangam Laxmibai Vidyapeet, approved by AICTE& affiliated to JNTUH)
Vinaynagar, I S Sadan Crossroads, Hyderabad 500 059, Telangana
Telephone:040-24537282,Website:www.brecw.ac.in,Email:[email protected]

Date:05.07.2024

CERTIFICATE
This is to certify that the Real Time Project Report entitled “SPICY BISTRO” is a
bonafide work carried out by

V Raja Sri 22321A0573

P Veda Samhitha 22321A0583

K Sai Sharanya 22321A0584

in partial fulfillment for award of the degree of Bachelor of Technology in Computer


Science and Engineering department from Bhoj Reddy Engineering College for Women,
Hyderabad,affiliated to Jawaharlal Nehru Technological University Hyderabad(JNTUH).

Coordinator Head of the Department

AVS Radhika Dr. B Raveendranadh Singh

External Examiner

Sangam Laxmibai Vidyapeet is an educational society for promotion of education among girls and women.
It is established in 1952 and registered under the Telangana Societies Registration Act.
ACKNOWLEDGMENT

It is our pleasure to express our whole-hearted thanks to Dr B Raveendranadh Singh,


Professor & Head of Computer Science and Engineering Department for providing the
necessary facilities to undergo this project.

We are thankful to our project coordinator Venkata Sai Radhika Ande, Assistant Professor,
Computer Science and Engineering Department, for giving us this opportunity to do this
project.

We are also thankful to our project reviewer Dr P Sumalatha, Associate Professor, Computer
Science and Engineering Department for his/her extreme guidance and support in completing
this project successfully.

We are also thankful to the staff members of Computer Science and Engineering Department,
my friends and to our parents who helped us in completing this project successfully.

V Raja Sri (22321A0573)


P Veda Samhitha (22321A0583)
K Sai Sharanya (22321A0584)
CONTENTS

Page No

List of Figures i
List of Tables ii
Abbreviations iii
Abstract iv

1. Introduction 1-3

1.1Introduction of project 2

1.2Existing system 2
1.3Problems in existing system 3
1.4Proposed system 3
1.5Advantages of proposed system 3

2. Requirements Analysis 4-9

2.1Functional requirements 5
2.2Non-functional requirements 6

2.3Computational resource requirements 6


2.3.1Hardware requirements 6
2.3.2Software requirements 7
2.4Lifecycle model 8

3. Architecture 10-17

3.1 Architectures 11

3.1.1 Software Architecture 11


12
3.1.2 Technical Architecture
3.2Use case diagram 12-13

3.3Class diagram 14
3.4Sequence diagram 15
3.5Activity diagram 16-17
4. Implementation 18-22

4.1 Technologies 19

4.1.1 HTML 19

4.1.2 CSS 19

4.1.3 JavaScript 19

4.1.4 PHP 20

4.1.5 My SQL 20
4.2 Pseudo code 21-22

5. Testing 23-28

5.1 Overview 24
5.2Dimensions of Testing 24

5.3 Stages of Testing 25-36


5.3.1 Unit Testing 25

5.3.2 Integration Testing 25


5.3.3 System Testing 26

5.3.4 Acceptance Testing 26


5.4 Types of Testing 26

5.5 Test Cases 27-28

6. Screenshots 29-36

7. Conclusion and Future Scope 37-38

7.1 Conclusion 38

7.2 Future Scope 38

8. References 39-40
LIST OF FIGURES

Fig. No Figure Name Page No


2.1 Spiral Model 9

3.1 Software Architecture 11

3.2 Technical Architecture 12

3.3 Use Case Diagram for User 13

3.4 Use Case Diagram for Restaurant Manager 13

3.5 Class Diagram 14

3.6 Sequence Diagram 15

3.7 Activity Diagram for Reserve Table 16

3.8 Activity Diagram for Order Food 17

3.9 Activity Diagram for Feedback 17

i
6 Screenshots 29-36

6.1 Sign up Page 30

6.2 Sign in Page 30

6.3 Main Page 31

6.4 Menu Page 31

6.5 Payment mode after orders 32

6.6 Reserving Table 32


33
6.7 Gallery
33
6.8 About Us
34
6.9 Feedback Form
34
6.10 Review
35
6.11 Sign in and Sign up Database
35
6.12 Reserving of table Database
36
6.13 Food Ordering Database

ii
LIST OF TABLES

Table No Table Name Page No


5.5.1 User 27

5.5.2 Restaurant Manager 28

iii
ABBREVATIONS
IDE: Integrated Development
Environment OS: Operating System
RAM: Random Access
UI: User Interface
UML: Unified Modelling Language
HTML: Hyper Text Markup Language
CSS: Cascading Style Sheet

iv
ABSTRACT

The "Spicy Bistro" is a user-friendly web-based platform aimed at transforming the way people
interact with restaurants. Designed to make dining more convenient, this system allows
customers to browse the menu, make reservations, and provide feedback. By simplifying the
interaction process, it seeks to increase customer engagement and ensure that every experience
is managed accurately and securely. Users can easily view the menu, check operating hours,
and find location details in a few simple steps. The system employs strong encryption to
safeguard user data and secure authentication to prevent unauthorized access. Detailed records
of customer activity and feedback ensure transparency and build trust in the dining experience.
This innovative approach not only reduces administrative burdens and the potential for human
error but also encourages greater participation in dining activities. By harnessing digital
technology, the Restaurant Website creates a more inclusive and efficient dining experience,
reinforcing customer satisfaction and empowering restaurants to engage actively with there
patrons.
INTRODUCTION
SPICY BISTRIO Introduction

1. INTRODUCTION

1.1 Introduction of project

The Spicy Bistro aims to make dining more accessible, efficient, and enjoyable for
customers. By using digital technology, it modernizes how people interact with
restaurants, making the process easier and more convenient. The system solves
problems like managing reservations and providing accurate information online. It
helps everyone easily find menus, hours, and location details. The website ensures
high-quality service by preventing errors and accurately handling reservations and
feedback. It also focuses on being clear and trustworthy, building customer confidence
in the restaurant's services. Creating this website highlights the need for secure and
efficient ways to connect with customers in today's digital world. Overall, it aims to
provide a better and more reliable dining experience for everyone.

1.2 Existing System

The existing system of restaurants typically relies on traditional methods such as printed
menus, phone calls for reservations, and walk-in customers. While these methods have
been effective for many years, they come with several limitations. Printed menus cannot
be updated easily, which makes it difficult to keep them current with the latest offerings
and prices. This process is not only time-consuming but also costly, as new menus must
be printed and distributed regularly. Customers must physically visit the restaurant to
check the menu, learn about special offers, and get other necessary information. This
can be inconvenient and may deter potential customers who prefer the ease of accessing
information online. Additionally, managing reservations through phone calls can lead
to errors, missed bookings, and misunderstandings, which can negatively impact
customer satisfaction. In simple terms, the existing system for restaurant operations
involves offline methods that might not be as convenient or accessible for customers in
today’s digital life. This highlights the need for a more advanced and user-friendly
solution to meet the demands of the current market.

Department of CSE, BRECW Page No.2


SPICY BISTRIO Introduction

1.3 Problems in Existing System

• You can’t easily promote daily special dishes, discounts, or events to attract
customers

• The restaurant can only reach people nearby and might miss out on customers
who are interested but far away.

• Customers may struggle to find basic details like your menu, prices, hours, and
location, making it harder for them to decide if they want to visit.
1.4 Proposed System

The proposed system for a restaurant website aims to address the drawbacks of
traditional methods by creating a user-friendly online platform. By having a website, a
restaurant becomes visible to anyone searching online for places to eat in your area,
vastly increasing its reach and accessibility. The website will showcase your menu,
prices, operating hours, location, and any special offers, making it convenient for
customers to decide whether to visit. Additionally, you can easily update the menu and
other details, ensuring that customers always have the most current information.
Moreover, an online reservation system simplifies the booking process for both
customers and staff, reducing errors and wait times. Customers can reserve tables from
the comfort of their homes or on-the-go, enhancing their overall dining experience. The
feedback feature allows customers to leave reviews and suggestions, helping the
restaurant to improve its services and build a strong relationship with its patrons. It also
provides a platform for integrating with social media, allowing you to engage with
customers on multiple fronts and further expand your reach.

1.5 Advantages of Proposed System

• An online reservation system simplifies the booking process for both customers and
staff, reducing errors and wait times.

• Improving efficiency and customer service.

• Having a website puts you on par with competitors and gives you an edge in
attracting customers.

Department of CSE, BRECW Page No.3


REQUIREMENT
ANALYSIS
SPICY BISTRO Requirement Analysis

2. REQUIREMENT ANALYSIS

2.1. Functional Requirements

The Restaurant Website is a web-based application developed to facilitate secure and


efficient interaction between customers and the restaurant through the use of digital
technology. It aims to enhance accessibility, convenience, and customer engagement by
allowing users to browse menus, make reservations, and provide feedback from any
location with internet access. The system comprises three main modules, each designed
to handle specific functionalities and user profiles.

The Spicy Bistro consists of the following modules:

1. Restaurant Manager Module

2. User Module

1. Restaurant Manager Module:


• Manage Menu: The manager can add, update, and delete menu items to keep the
menu current and accurate.
• View and Manage Reservations: The manager can view all reservations, update
their status, and manage table availability.
• View and Manage Orders: The manager can view all food orders, update their
status, and ensure timely preparation and delivery/pickup.
• View Orders: The manager can access and review all orders placed by customers,
including order details and status updates.
• View Feedback: The manager can access customer feedback and reviews to
understand customer satisfaction and areas for improvement.
2. User Module:

• Browse Menu: Users can view the restaurant's menu, including item descriptions,
prices, and availability.

• Order Food: Users can select menu items and place food orders online. The system
will confirm the order and provide an estimated delivery or pickup time.

Department of CSE, BRECW Page No. 5


SPICY BISTRO Requirement Analysis

• Make Reservations: Users can reserve tables by selecting the date, time, and
number of guests. The system will confirm the reservation and provide details.

• Provide Feedback: Users can submit feedback and reviews about their dining
experience, which helps the restaurant to improve its services.

• View Contact Information: Users can easily find the restaurant's contact details,
location, and operating hours.

2.2. Non-Functional Requirements


These requirements ensure the online voting system operates effectively and provides
a reliable and user-friendly experience. They address key aspects such as security,
performance, maintainability, and usability.

• Security: Implement robust encryption mechanisms to safeguard the


integrity and confidentiality of vote data.
• Performance:Ensure the system can handle high volumes of concurrent users
and provide fast response times, even during peak voting periods.
• Maintainability: Design the system with clean and well-
documented code to facilitate easy updates and modifications by
developers.
• Usability: Create an intuitive user interface that adheres to usability standards,
ensuring a seamless and enjoyable voting experience for all users.

2.3. Computational Resource Requirements

2.3.1.Hardware Requirements

i Processor : Inteli4

ii Hard Disk : 50GB

iii RAM : 4GB

Department of CSE, BRECW Page No. 6


SPICY BISTRO Requirement Analysis

2.3.2.Software Requirements

i Operating System : Windows10

ii IDE : Visual Studio Code

iii User Interface : HTML,CSS

iv Scripting language : JS

v Database : Xampp Server

Department of CSE, BRECW Page No. 7


SPICY BISTRO Requirement Analysis

2.4. Life Cycle Model

We use Spiral Model, it is a risk-driven model, meaning that the focus is on managing
risk through multiple iterations of the software development process. It consists of the
following phases:
• Planning: The first phase of the Spiral Model is the planning phase, where the
scope of the project is determined and a plan is created for the next iteration of
the spiral.
• RiskAnalysis: In the risk analysis phase, the risks associated with the project
are identified and evaluated.
• Engineering: In the engineering phase, the software is developed based on the
requirements gathered in the previous iteration.
• Construction: During this phase the software is actually built based on the
specifications outlined in the previous phases. It involves coding, testing,
integration.
• Of components, and system testing. The emphasis implementing the
requirements gathered in the earlier stages.
• Release: Once a version of the software is deemed stable and functional, it is
released to the customer or stakeholders. The release may be a prototype, an
alpha version ,or a betaversion, depending on the progress and the agreement
with the customer. Feedback from users and stakeholders gathered during this
phase is vital for refining the software.
• Customer Evaluation: In the evaluation phase, the software is evaluated to
determine if it meets the customer’s requirements and if it is of high quality.
• Customer Communication: Communication with the customer is continuous
throughout the Spiral model. It involves regular interactions together
requirements, discuss progress, share prototypes or interim deliverables, and
collect feedback. This ongoing communication allows for adjustments and
improvements based on the customer's evolving needs.

Department of CSE, BRECW Page No. 8


SPICY BISTRO Requirement Analysis

2.1SpiralModel

Department of CSE, BRECW Page No. 9


SPICY BISTROSICY BISTRO

ARCHITECTURE
SPICY BISTRO Architecture

3. ARCHITECTURE

3.1 Architecture

Project architecture represents number of components we are using as a part of our


project and the flow of request processing i.e. what components in processing the
request and in which order. An architecture description is a formal description and
representation of a system organized in a way that supports reasoning about the structure
of the system. Architecture is of two types. They are
(1) Software Architecture

(2) Technical Architecture

3.1.1 Software Architecture

Fig3.1Software architecture

Department of CSE, BRECW Page No.11


SPICY BISTRO Architecture

3.1.2 Technical Architecture:

Fig3.2Technical architecture

UML Diagrams

Design engineering deals with the Unified Modelling Language(UML) which is a standard
language for writing software blue prints. The UML is a language for
• Visualizing

• Specifying

• Constructing

• Documenting the artifacts of a software intensive system

The UML is a language which provides vocabulary and the rules for the rules combing
words in that vocabulary for the purpose of communication. A modelling language is
a language whose vocabulary and the rules focus on the conceptual and physical
representation of a system. Modelling yields an understanding of a system.

3.2 Use Case Diagram:

Use case diagram are used to gather the requirements of a system including internal
and external influences. A use case represents a functionality of a system. So, use case
diagrams are used to describes the relationships among the functionalities and their
internal/external controllers. These controllers are known as actors.

Department of CSE, BRECW Page No.12


SPICY BISTRO Architecture

Fig3.3UsecasediagramforUser

Fig3.4UsecasediagramforRestaurant Manager

Department of CSE, BRECW Page No.13


SPICY BISTRO Architecture

3.3 Class Diagram:

A class diagram in UML represents the static structure of a system by showing its
classes, attributes, operations, and relationships. Key components include classes
(depicted as rectangles divided into sections for name, attributes, and operations),
attributes (properties of a class), operations (methods of a class), and various
relationships like associations, aggregations, compositions, generalizations, and
dependencies. It is used for designing and modeling object-oriented systems, serving as
a blueprint for software development and facilitating communication among developers
and stakeholders. Class diagrams can be used for both forward and reverse engineering
of systems.

Fig3.5Class Diagram

Department of CSE, BRECW Page No.14


SPICY BISTRO Architecture

3.4 Sequence Diagram:


A sequence diagram illustrates the sequence of messages between objects in an
interaction. A sequence diagram consists of a group of objects that are represented by
lifelines, and the messages that they exchange over time during the interaction.
Purpose of Sequence Diagram:
• Model high-level interaction between active objects in a system.
• Model the interaction between object instances within a collaboration that realizes a use
case.
• Model the interaction between objects within a collaboration that realizes an operation.

Fig3.6 Sequence diagram

Department of CSE, BRECW Page No.15


SPICY BISTRO Architecture

3.5 Activity Diagram:


Activity Diagram describe how activities are coordinated to provide a service which can
be at different levels of abstraction. Typically, an event needs to be achieved by some
operations, particularly where the operation is intended to achieve several different
things that require coordination, or how the events in a single use case relate to one
another use cases where activities may overlap and require coordination. It is also
suitable for modelling how a collection of use cases coordinate to represent business
workflows.

Fig3.7 Activity diagram for Reserve Table

Department of CSE, BRECW Page No.16


SPICY BISTRO Architecture

Fig3.8 Activity diagram for Order food

Fig3.9 Activity Diagram for Feedback

Department of CSE, BRECW Page No.17


IMPLEMENTATION
SPICY BISTRO Implementation

4 IMPLEMENTATION
4.1 Technologies
This online voting system is developed using various web technologies to ensure a
seamless, secure, and user-friendly experience. The core technologies used in the
development of this system include HTML, CSS, JavaScript, and PHP, along with a
MySQL database for backend
data management.
4.1.1 HTML
HTML (Hyper Text Markup Language) is the standard markup language used to create
web pages. It forms the backbone of the web application, providing the structure and
layout of the content displayed on the online voting platform. HTML is used to define
the elements of voting system, including the login forms, voting ballots, and user
interface components.
4.1.2 CSS
CSS (Cascading Style Sheets) is used to control the presentation and layout of the web
pages. It allows for the styling of HTML elements, making the online voting system
visually appealing and easy to navigate. CSS is used to define the look and feel of the
platform, ensuring a consistent and
professional appearance across all pages.
4.1.3 JavaScript
JavaScript is a versatile scripting language that enables dynamic and interactive features
on web pages. In the online voting system, JavaScript is used to enhance user interaction,
validate input data, and manage client-side operations. It plays a crucial role in providing
real-time feedback to users, such as confirming vote submissions and updating election
results without requiring page

Department of CSE, BRECW Page No.19


SPICY BISTRO Implementation

4.1.4 PHP
PHP (Hypertext Preprocessor) is a server-side scripting language used to handle backend
operations. It is responsible for processing user input, managing sessions, and interacting
with the database. PHP scripts handle the authentication of users, record votes, and
generate reports on election results. It ensures the secure transmission and storage of
sensitive data, such as voter information and vote records.
4.1.5 My SQL
My SQL is a robust and widely used relational database management system. It is used
to store and manage all the data associated with the online voting system. This includes
user registration details, voter credentials, candidate information, and vote counts.
MySQL ensures that data is stored securely and can be retrieved efficiently, supporting
the smooth operation of the voting process.
Integration and Security:
The integration of these technologies ensures a cohesive and functional online voting
platform. The combination of HTML, CSS, JavaScript, PHP, and MySQL provides a
robust foundation for developing a secure, reliable, and user-friendly system. Security
measures such as encryption, secure authentication, and data validation are implemented
to protect the integrity of the voting process and safeguard user information. By
leveraging these web technologies, the online voting system offers a modern and efficient
solution for conducting elections, enhancing voter participation, and ensuring the
accuracy and transparency of the electoral process.

Department of CSE, BRECW Page No.20


SPICY BISTRO Implementation

4.2 Pseudo code


#Pseudo code for Signup:
display("Welcome”)
display("Sign Up")
display("Sign In")
display("Exit")
choice = getUserInput()
if choice == "Sign Up" then
// User Sign Up
display("Enter Username:")
username = getUserInput()
display("Enter Password:")
password = getUserInput()
// Save username and password to database
saveToDatabase(username, password)
display("Sign Up Successful!")
#Pseudo code for Signin:
choice = getUserInput()
end if
if choice == "Sign In" then
// User Sign In
display("Enter Username:")
username = getUserInput()
display("Enter Password:")
password = getUserInput()
// Verify username and password from database
if verifyCredentials(username, password) then
display("Sign In Successful!")

Department of CSE, BRECW Page No.21


SPICY BISTRO Implementation
# Pseudo Code for Reservation:
display("Welcome to Spicy Bistro!")
display("Reserve Table")
display("View Menu")
display("Order Food")
display("Give Feedback")
display("Logout")
choice = getUserInput()
if choice == "Reserve Table" then
// Reserve Table
display("Enter Date (YYYY-MM-DD):")
date = getUserInput()
display("Enter Time (HH:MM):")
time = getUserInput()
display("Enter Number of People:")
people = getUserInput()
// Save reservation to database
saveReservationToDatabase(date, time, guests)
display("Table Reserved Successfully!")

#Pseudo Code for ordering food:


if choice == "Order Food" then
// Order Food
// View Menu first
menuItems = getMenuItemsFromDatabase()

display("Menu:")
for each item in menuItems do
display(item)
end for
display("Enter Item Number to Order:")
itemNumber = getUserInput()
display("Enter Quantity:")
quantity = getUserInput()

// Save order to database


saveOrderToDatabase(itemNumber, quantity)
display("Order Placed Successfully!")

Department of CSE, BRECW Page No.22


TESTING
SPICY BISTRO Testing

5 TESTING
5.1 Overview
Software testing is a process, to evaluate the functionality of a software application with
an intent to find whether the developed software met the specified requirements or not
and to identify the defects to ensure that the product is defect free in order to produce the
quality product.

As per the current trend, due to constant change and development in digitization, our
lives are improving in all areas. The way we work is also changed. We access our bank
online, we do shop online; we order food online and many more. We rely on software’s
and systems. What if the systems turnout to be defective? We all know that one small
bug shows huge impact on business in terms of financial loss and goodwill. To deliver
quality product, we need to have Software Testing in the Software Development Process.

Some of the reasons why software testing becomes very significant and integral part in
the field of information technology are as follows.

1. Cost effectiveness

2. Customer Satisfaction

3. Security

4. Product Quality

5.2 Dimensions of Testing

There are many different dimensions to consider:

1. Layers of the application (database, APIs, UI)


2. Scale of testing (unit, module, integration, scenario)
3. Type of testing (functional, performance, security, etc.)
4. Methodology(exploratory, scripted manual, automated)

5.3 STAGES OF TESTING


Department of CSE, BRECW PageNo.24
SPICY BISTRO Testing
5.3.1 Unit Testing

During This first round of testing, the program is submitted to assessments that focus on
specific units or components of the software to determine whether each one is fully
functional. In this phase, a unit can refer to a function, individual program or even a
procedure ,and Whitebox testing method is usually used to get the job done. One of the
biggest benefits of this testing phase is that it can be run every time a piece of code is
changed, allowing issues to be resolved as quickly as possible. It quite common for
software developers to perform unit tests before delivering software to testers for formal
testing.

5.3.2 Integration Testing

Integration testing allows individuals the opportunity to combine all of the units within
a program and test them as a group. This testing level is designed to find interface defects
between the modules/functions. This is particularly beneficial because it determines how
efficiently the units are running together. Keep in mind that no matter how efficiently
each unit is running, if they properly integrated, it will affect the functionality of the
software program. In order to run these types of tests, individuals can make use of various
testing methods, but the specific method that will be used to get the job done will depend
greatly on the way in which the units are defined.

5.3.3System Testing

System testing is the first level in which the complete application is tested as a whole.
The goal at this level is to evaluate whether the system has complied with all of the
outlined requirements and to see that it meets Quality Standards. System testing is
undertaken by independent testers who haven’t played a role in developing the program.
This testing is performed in an environment that closely mirrors production. System
Testing is very important because it verifies that the application meets the technical,
functional, and business requirements that were set by the customer.

Department of CSE, BRECW PageNo.25


SPICY BISTRO Testing
5.3.4 Acceptance Testing
The final level, Acceptance testing (or User Acceptance Testing), is conducted to
determine whether the system is ready for release. During the Software development life
cycle, requirements changes can sometimes be misinterpreted in a fashion that does not
meet the intended needs of the users. During this final phase, the user will test the system
to find out whether the application meets their business needs. Once this process has been
completed and the software has passed, the program will then be delivered to production.
The extensiveness of these tests is just another reason why bringing software testers in early
is important. When a program is more thoroughly tested, a greater number of bugs will be
detected; this ultimately results in higher quality software.

5.4 Types of testing


5.3.5 Black box testing

It is also called as Behavioral/Specification-Based/Input-Output Testing. Black Box


Testing is a software testing method in which testers evaluate the functionality of the
software under test without looking at the internal code structure. This can be applied to
every level of software testing such as Unit, Integration, System and Acceptance Testing.

5.3.6 White box testing

It is also called as Glass Box, Clear Box, Structural Testing. White Box Testing is based
on applications internal code structure. In white-box testing an internal perspective of
the system, as well as programming skills, are used to design test cases. This testing
usually done at the unit level.

White Box Testing Techniques:

1. Statement Coverage
2. Branch Coverage
3. Path Coverage

Department of CSE, BRECW PageNo.26


SPICY BISTRO Testing

5.5 Test Cases


Table5.5.1User
Test Test Name Inputs Process Expected Actual Status
ID output output
1 Login user Username, Register User is User is success
email and user in the successfully successfully
password system registered registered
2 Browse none User Menu page is Menu page success
menu navigates displayed is
to menu with all displayed
page menu items with all
menu
items
3 Place order Menu items, User Order Order Success
user details selects confirmation confirmati
Menu Page is on
items and displayed Page is
places an displayed
order
4 Submit Reservation User fills Reservation Reservatio Success
Reservation details in and confirmation n
submit the page is confirmati
reservation displayed on page is
form displayed

Department of CSE, BRECW PageNo.27


SPICY BISTRO Testing
Table5.5.2 Restaurant Manager

Test Test Name Inputs Process Expected Actual Status


ID output output
1 Access none Manager Menu Menu success
menu navigates to management management
management the menu page is page is
management displayed displayed
page
2 View orders none Manager Order page Order page success
navigates is displayed is displayed
order page
3 View none Manager Reservation Reservation success
reservation navigates page is page is
reservation displayed displayed
page
4 View none Manager Feedback Feedback success
feedback navigates page is page is
feedback displayed displayed
page

Department of CSE, BRECW PageNo.28


SCREENSHOTS
SPICY BISTRO Screenshots

6 SCREENSHOTS

Screenshot 6.1: Sign up page

Screenshot 6.2: Sign In page

Department of CSE,BRECW Page No.30


SPICY BISTRO Screenshots

Screenshot 6.3: Main page

Screenshot 6.4: Menu Page

Department of CSE,BRECW Page No.31


SPICY BISTRO Screenshots

Screenshot 6.5: Payment mode after ordering

Screenshot 6.6: Reserving Table

Department of CSE,BRECW Page No.32


SPICY BISTRO Screenshots

Screenshot 6.7: Gallery

Screenshot 6.8: About us

Department of CSE,BRECW Page No.33


SPICY BISTRO Screenshots

Screenshot 6.9: Feedback Form

Screenshot 6.10: Review

Department of CSE,BRECW Page No.34


SPICY BISTRO Screenshots

6.11 Sign in and Sign up Database

6.12 Reserving of table Database

Department of CSE,BRECW Page No.35


SPICY BISTRO Screenshots

6.13 Food Ordering Database

Department of CSE,BRECW Page No.36


CONCLUSION &
FUTURESCOPE
SPICY BISTRO Conclusion&Future Scope

7.1 Conclusion & Future Scope


Restaurant website helps customers get accurate info like hours and deals, making them trust and
like the place more. Plus, features like online ordering and booking tables make dining easier for
customers and the restaurant.Nowadays, having a website like this isn't just nice it's necessary to
keep up with the times and make customers happy. So, having a real-time website isn't just good
for customers, it's great for the restaurant's success in the long run.

a. Future Scope

• Advanced Data Analytics: Employ advanced data analytics to gain deeper insights into
customer behavior, preferences, and trends, helping the restaurant to tailor its offerings and
marketing strategies more effectively.
• Integration with Smart Devices: Enable compatibility with smart home devices and virtual
assistants, allowing customers to make reservations or place orders using voice commands.
• Mobile App Development: Develop a dedicated mobile app to complement the website,
offering additional features like push notifications for special offers and seamless in-app
ordering and reservations.

Department of CSE,BRECW Page No.38


REFERENCES
SPICY BISTRO References

8. References
1. Web Technologies, Uttam K Roy, Oxford University Press.

2. Eloquent JavaScript: A Modern Introduction to Programming

3. Software Engineering: Sommerville, 7th edition, Pearson Education

4. https://ieeexplore.ieee.org/document/9587443

5. https://ieeexplore.ieee.org/document/9609723

Department of CSE,BRECW Page No.40

You might also like