PizzaHub

Web Application

Project Details

Project Information

Project Title: PizzaHub

Category: Web Application

Semester: Spring 2025

Course: CS619

Complexity: Easy

Supervisor Details

Project Description

PizzaHub

Project Domain / Category

Web Application

Abstract / Introduction

PizzaHub is a comprehensive web application designed for pizza fast-food shops, combining Point of Sale (POS) functionality with an online ordering system. The application allows administrators to manage products (pizzas, fast food, drinks, etc.) and process sales through the POS module, generating printable invoices for completed orders. Additionally, customers can create accounts on the website, browse the menu, place orders online, and track their orders. The admin can log in to the website to view and manage both online and in-store orders through a unified dashboard. Pizza Hub aims to streamline operations, enhance customer experience, and provide a seamless integration of online and offline sales.

 

Functional Requirements

1.  Admin Module (POS + Dashboard)

·         Login/Logout: Admin can log in securely to access the POS and dashboard.

·         Product Management:

o    Add, update, or delete products (pizzas, fast food, drinks, etc.).

o    Categorize products (e.g., Pizza, Fast Food, Drinks).

·         Order Management:

o    Create and manage in-store orders through the POS.

o    Add multiple products to an order and calculate the total bill.

o    Apply discounts or promotions to orders.

·         Invoice Generation:

o    Generate and print invoices for completed orders.

o    Invoices include order ID, product list, total amount, taxes, discounts, and date/time.

·         Sales Reporting:

o    View daily, weekly, and monthly sales reports.

o    Track most sold products, total revenue, and average order value.

 

2.  Customer Module (Website)

 

·         User Registration/Login:

o    Customers can create accounts and log in securely.

·         Menu Browsing:

o    Customers can view the menu with categories (pizzas, fast food, drinks, etc.).

·         Online Ordering:

o    Customers can add products to their cart and place orders online.

o    Customers can provide delivery/pickup details and payment information.

·         Order Tracking:

o    Customers can view the status of their orders (e.g., pending, in progress, completed).

·         Order History:

o    Customers can view their past orders and invoices.

3.  Admin Dashboard (Website)

·         Order Management:

o    Admin can view and manage both online and in-store orders.

o    Admin can update order status (e.g., pending, in progress, completed).

·         Sales Reporting:

o    Admin can view sales reports for both online and in-store orders.

·         User Management:

o    Admin can view and manage customer accounts.

4.  Shared Features

·         Responsive Design:

o    The website and POS are accessible on desktops, tablets, and mobile devices.

·         Search and Filter:

o    Customers and admin can search and filter products by name, category, or price.

 

 

 

Non-Functional Requirements

1.      Performance:

o    The system should handle up to 500 concurrent users without performance degradation.

o    Invoice generation should take less than 5 seconds.

2.     Security:

o    All sensitive data (e.g., admin credentials, customer information) must be encrypted.

o    The system should prevent unauthorized access and SQL injection attacks.

3.     Scalability:

o    The application should be scalable to accommodate future features like delivery tracking or loyalty programs.

4.     Usability:

o    The user interface should be intuitive and easy to navigate for both customers and admin.

o    The system should provide tooltips or guidance for first-time users.

5.     Reliability:

o    The system should have a 99.9% uptime.

o    Data backups should be performed daily to prevent data loss.

6.     Compatibility:

o    The application should be compatible with major browsers (Chrome, Firefox, Safari, Edge).

o    The invoice PDF should be printable on standard A4 paper.

7.     Maintainability:

o    The code should be well-documented for future updates.

o    The system should support easy integration with third-party tools (e.g., payment gateways, delivery APIs).

 

 

Tools/Programming Languages

XAMPP/WAMPP Server, Php , MySQL, react (it is mandatory to use the mention language framework. Any other framework or language will not be acceptable)

 

 

Note: VU will not provide you with any resources to buy any Software, Framework or any services if used in this project. Students must manage all the project on its own.

 

Supervisor:

Name: Muhammad Hashir Khan

Email ID: hashir.khan@vu.edu.pk

Skype ID: hashir.khan9996

 

Languages

  • HTML, CSS, Boot Strap, JavaScript, PHP, MySQL Language

Tools

  • WAMP/XAMPP Server, Sublime Text / VS Code Tool

Project Schedules

Assignment #
Title
Start Date
End Date
Sample File
1
SRS Document
Friday 2, May, 2025 12:00AM
Thursday 22, May, 2025 12:00AM
2
Design Document
Friday 23, May, 2025 12:00AM
Tuesday 29, July, 2025 12:00AM
3
Prototype Phase
Wednesday 30, July, 2025 12:00AM
Friday 12, September, 2025 12:00AM
4
Final Deliverable
Saturday 13, September, 2025 12:00AM
Monday 3, November, 2025 12:00AM

Viva Review Submission

Review Information
Supervisor Behavior

Student Viva Reviews

No reviews available for this project.