Minor Project Report

Of
Men Saloon management System
In partial fulfillment for the award of the degree
Of
BACHELOR OF COMPUTER APPLICATION
[B.C.A]
Year 2024-2025

SUBMITTED BY: GUIDED BY:

Dhruvi Meghpara Prof. Pratiksha Patel

BCA-5th SEMESTER

Submitted to:

SHRI SHAMBHUBHAI V. PATEL COLLEGE OF

COMPUTER SCIENCE & BUSINESS
MANAGEMENT
Affiliated to

Veer Narmad South Gujarat University

 Acknowledgement

The success and final outcome of this project required a lot of guidance and

assistance from many people, and we are extremely fortunate to have gotten

this all along with the completion of our project work. Whatever we have done

is only due to such guidance and assistance.

We would not forget to thank I/C Principal C.H Thakkar , IQAC coordinator

and trust representative Yesha Patel, Head of BCA Department Riddhi Joshi

and Project guide Pratiksha Patel and all other assistant professors, who

took a keen interest in our project work and guided us all along till the

completion of our project work by providing all the necessary information for

developing a good system.

We are extremely grateful to her for providing such nice support and

guidance, though she had a busy schedule managing the college dealings.

We are thankful and fortunate enough to have gotten support and guidance

from all the teaching staff in the Bachelor of Computer Application

Department, which helped us successfully complete our project work. Also,

we would like to extend our sincere regards to all the non-teaching staff of the

Bachelor of Computer Application Department for their timely support.

From Dhruvi Meghpara

page 2
 INDEX

Sr. No Description Page No.

1 Introduction
1.1 Project description 4
1.2 Project Profile 4
2 Environment Description
2.1 Hardware and Software Requirements 6
2.2 Technologies Used 6
3 System Analysis and Planning
3.1 Existing System and its Drawbacks 10
3.2 Feasibility Study 10
3.3 Requirement Gathering and Analysis 12
4 Proposed System
4.1 Scope 13
4.2 Project modules & functionalities Constraints 13
5 Detail Planning
5.1 Data Flow Diagram / UML 15
5.2 Process Specification / Activity Flow Diagram 17
5.3 Data Dictionary 17
5.4 Class Diagram 19
6 System Design
6.1 user side 20
6.2 admin side 24
7 Software Testing
7.1 Unit Testing 31
7.2 Integration Testing 32
7.3 System Testing 33
8 Limitations and Future Scope of Enhancements 34
9 Reference 36

1. Introduction
1.1 Project Profile:-

page 3
Project Title Man Saloon Management System

Front End HTML, CSS, JavaScript, jQuery, Bootstrap

Back End PHP MySQL

Guided By Prof. Pratiksha patel

Submitted To Shri Shambhubhai v. Patel college of CS & B.M, Surat.

Developed By Dhruvi meghpara

page 4
 2.Environment Description

2.1 Hardware & Software Requirement:-

At Development Time…

❖ Hardware Requirement:

⮚ Processor: x86 or x64

⮚ RAM: 512 MB minimum,1 GB recommended

⮚ Hard Disk: UP to 200 MB of available space

⮚ Web Server: Apache Web Server,LigHTTPD,IIS(with ISAPI_Rewrite

Installed)

⮚ Database: MySQL 5.7 or Above,Microsoft SQL Server 2008 or Above

❖ Software Requirement:

⮚ Operating System : Windows

⮚ PHP Version

⮚ Web Browser: Microsoft Internet Explorer,Google Chrome

⮚ MYSQL Server (Back-end)

2.2 Technologies Used:-

Front End :- HTML

⮚ HTML stands for Hyper Text Markup Language. HTML is the
standard markup language for creating Web pages. HTML describes the
structure of a Web page. HTML consists of a series of elements. HTML
elements tell the browser how to display the content.HyperText allows a user
to click a link and be redirected to a new page referenced by that link.
⮚ Uses of HTML in the Real World: Web Pages Development.
⮚ some form written in HTML code.
⮚ Navigating the Internet.
⮚ Responsive Designs.
⮚ Storage Function in the Browser.
⮚ Data Entry Support

page 5
CSS :-
Cascading Style Sheets (CSS) is a style sheet language used for
describing the presentation of a document written in a markup language.
Although most often used to set the visual style of web pages and user
interfaces written in HTML and XHTML, the language can be applied to
any XML document, including plain XML, SVG and XUL, and is applicable
to rendering in speech, or on other media. Along with HTML and
JavaScript, CSS is a cornerstone technology used by most websites to
create visually engaging web pages, user interfaces for web applications,
and user interfaces for many mobile applications. Before CSS, nearly all
presentational attributes of HTML documents were contained within the
HTML markup. All font colors, background styles, element alignments,
borders and sizes had to be explicitly described, often repeatedly, within
the HTML.

JAVASCRIPT :-
JavaScript is a high-level, dynamic, untyped, and
interpreted programming language. It has been standardized in the
ECMAScript language specification. Alongside HTML and CSS,
JavaScript is one of the three core technologies of World Wide Web
content production; the majority of websites employ it, and all modern
Web browsers support it without the need for plug-ins. JavaScript is
prototype-based with first-class functions, making it a multi-paradigm
language, supporting object oriented, imperative, and functional
programming styles. It has an API for working with text, arrays, dates

page 6
and regular expressions.

BOOTSTRAP :-
Bootstrap is a free and open-source front-end
web framework for designing websites and web applications. It
contains HTML- and CSS-based design templates for typography,
forms, buttons, navigation and other interface components, as well
as optional JavaScript extensions.
It aims to ease the development of dynamic websites and web
applications. Bootstrap is a front end web framework, that is, an
interface for the user, unlike the server-side code which resides on
the "back end" or server.

Backend End:- PHP

PHP, or Hypertext Preprocessor, is a general-purpose scripting language

and interpreter that is free and open-source. It is primarily used for server-
side scripting, but can also be used for command-line scripting and
desktop applications.PHP is well-suited for web development and is
embedded in HTML. It is used to create dynamic web pages, applications,

page 7
customer relationship management systems, and more.PHP is compatible
with almost all servers used today, including Apache and IIS.It allows you
to create dynamic web pages, handle form submissions, and interact with
databases.

MySQL:-

MySQL is a relational database management system (RDBMS) that is

open source and free. It is a client/server system that uses structured
query language (SQL). MySQL is used by many popular applications,
including Facebook, Twitter, Netflix, Uber, Airbnb, Shopify, and
Booking.com.A database management system is crucial for storing and
managing data related to showrooms, cars, employees, and customers.
MySQL is a popular choice for PHP-based applications.To build a web
site that shows data from a database, you will need:An RDBMS database
program (like MySQL)A server-side scripting language, like PHP To use
SQL to get the data you wantTo use HTML / CSS to style the page.

3. System Analysis and Planning

page 8
3.1 Existing System and its Drawbacks:-
System
In traditional or semi-digital furniture stores, customer interaction is usually
limited to physical store visits or basic online catalogs. These systems may
not be fully integrated with real-time inventory tracking, customer service, or
secure online payment systems. Traditional methods involve significant
manual labor for both the customer and the business.
Some stores may offer online browsing through websites or social media, but
key functionalities such as automated order management, real-time product
availability, and personalized user accounts are often missing.

Drawbacks of the Existing System:

 Limited Online Access: Many furniture stores either don’t have an
online presence or have basic, static websites that don't offer e-
commerce capabilities.
 Manual Data Handling: Inventory, customer information, and sales are
often managed manually, increasing the risk of human error.
 Lack of Real-time Inventory Updates: Customers may browse products
only to find that items are out of stock once they inquire or visit the
store.
 No Customer Personalization: Customers cannot create accounts,
save Wishlist, or view their order history, reducing the chances of
repeat business.
 Inefficient Sales Process: Customers need to call or visit the store to
finalize purchases, which is inconvenient and time-consuming.
 No Automation: Processes like order management, invoice generation,
and customer queries are often handled manually.

3.2 Feasibility Study:-

The Feasibility Study is conducted to evaluate whether the project is viable in

terms of technology, operations, and cost. The goal is to ensure that the
project can be completed successfully within the available resources.

page 9
1.Technical Feasibility: Evaluate the technical aspects of the project.
Consider factors such as the technology stack (e.g., PHP, MySQL),
development tools, hosting requirements, scalability, and integration
capabilities with other systems (e.g., accounting software, CRM).

2.Resource Assessment: Determine the resources needed for the project,

including human resources (developers, designers, testers), hardware
(servers, computers), software (development tools, licenses), and time.
Assess if you have the necessary skills and resources internally or if you'll
need to hire external help.

3.Cost Estimation: Estimate the costs associated with developing the

Furniture. This includes both one-time costs (e.g., development, infrastructure
setup) and recurring costs (e.g., hosting, maintenance, support). Compare the
estimated costs with the expected benefits to assess the project's financial
viability.

4.Risk Analysis: Identify potential risks that could affect the success of the
project. This may include technical challenges, market competition, regulatory
compliance issues, and resource constraints. Develop mitigation strategies to
address these risks and minimize their impact.

5.Legal and Compliance Considerations: Consider any legal and

compliance requirements relevant to the project, such as data protection
regulations (e.g., GDPR), intellectual property rights, and industry-specific
regulations (e.g., automotive industry standards). Ensure that the proposed
system complies with these requirements to avoid legal issues in the future.

6.Conclusion and Recommendation: Based on the findings of the feasibility

study, conclude whether the project is feasible or not. If feasible, provide
recommendations on how to proceed with the development of the car
showroom management system, including a proposed timeline and action
plan.

page 10
3.3 Requirement Gathering and Analysis:-

Requirement Gathering:-

The purpose of this step is to identify the functional and non-

functional requirements of the system. These requirements will be
derived from various stakeholders, including customers, store owners,
and administrative staff.

Functional Requirements

1. User Registration and Authentication:

 Customers should be able to register an account, log in, and manage
their profile.
 Store administrators should have separate access to manage the
store’s inventory and customer orders.
2. Product Catalog Management:
 Display furniture items categorized by type, material, style, and price.
 Products must be accompanied by high-quality images, descriptions,
stock availability, and customer reviews.
 Admins must be able to add, update, or remove products from the
catalog through an intuitive interface.
3. Shopping Cart:
 Users can add products to a shopping cart, update quantities, and
remove items.
 The cart should dynamically calculate the total price and applicable
taxes.
4.Checkout and Payment Processing:
 Secure checkout flow integrated with payment gateways like Card or
UPI Id.
 Customers should receive confirmation emails upon successful
transactions.
5.Customer Support and Inquiry System:
 Users can submit inquiries about specific products, which will be
automatically recorded in the system for admins to review and respond.

Non-Functional Requirements
1. Performance:
The website should load pages quickly and handle high traffic without
degrading performance.
2. Scalability:
The system should be scalable to accommodate a growing catalog of
products and increasing customer numbers without a major redesign.
3. Security:

page 11
 o User data, including personal and payment information, must be
encrypted and stored securely.
o The system must prevent unauthorized access and potential
attacks (e.g., SQL injection, cross-site scripting).
4. UX
The user interface must be intuitive, easy to navigate, and responsive
across various devices (desktop, mobile, and tablets).
5. Reliability:
The system must ensure consistent availability and offer regular
backups to prevent data loss.

Analysis:-

⮚ The system should be designed to be easy to use and maintain. The user
interface should be intuitive and the system should be able to handle a large
number of users and transactions. The system should also be secure to
protect customer and car information.
⮚ The system should be implemented using the PHP programming language
and the MySQL database. PHP is a popular and well-supported language for
web development and MySQL is a powerful and reliable database.
⮚ The system should be developed in a modular fashion so that it can be
easily extended and modified in the future. The system should also be well-
documented so that it is easy to understand and maintain.
⮚ The system should be tested thoroughly before it is deployed to production.
The testing should include unit testing, integration testing, and system testing.
⮚ The system should be deployed to a production server that is reliable and
secure. The server should be configured to meet the system's performance
and security requirements.
⮚ The system should be monitored after it is deployed to production. The
monitoring should include tracking the system's performance and security.
⮚ The system should be backed up regularly to protect against data loss. The
backups should be stored in a secure location.

page 12
 4.Proposed System

4.1 Scope:-

The proposed system will offer a comprehensive solution tailored specifically

to enhance the efficiency and user experience of purchasing furniture online.
Here’s what it covers:

 Comprehensive Product Catalog: A detailed and easily navigable

product catalog featuring diverse furniture categories such as sofas,
beds, tables, storage solutions, and more.

 User-Friendly Interface: A sleek, responsive web design that is easy

to navigate on a variety of devices, including smartphones, tablets, and
desktops.

 Customer Account Management: Personalized user accounts where

customers can manage their profiles, view order history, track current
orders, and save favorite products.

 Shopping Cart and Checkout Process: A seamless, secure checkout

process integrated with various payment methods. The shopping cart
will allow modifications such as quantity adjustment or item removal up
until the purchase.

 Real-Time Inventory Management: The backend will automatically

update product availability to reflect current stock levels, preventing
order cancellations due to out-of-stock items.

 Order Management System: A backend system that allows the

store’s management to view, process, and update order statuses from
placement to delivery.

 Administrative Dashboard: A powerful administrative panel for

managing product listings, setting promotions, handling customer
service inquiries, and generating sales reports.

4.2 Project modules & functionalities Constraints:-

The proposed system is modular, each serving a specific function while

seamlessly integrating with the others. The constraints associated with these
modules ensure robust, efficient operations:

1. Product Management Module:

page 13
  Constraints: Must be able to handle multiple product attributes
(size, color, material, etc.) and reflect changes in real-time across
the customer-facing site.

2. User Management Module

 Constraints: Needs to securely manage user data, support password recovery
and user authentication processes, and handle concurrent sessions reliably.

3. Order Processing Module:

Constraints: Should integrate with inventory and ensure that stock levels
are adjusted in real-time as orders are placed and processed.
4. Payment Integration Module:
 Constraints: Must support multiple payment gateways and ensure
secure transaction processing, including compliance with PCI-DSS
standards.
5. Reporting and Analytics Module:
 Constraints: Requires high performance to generate real-time sales,
inventory, and customer behavior analytics without impacting the user
experience.
6.Customer Service Module:

o Constraints: Must be integrated with the user management module to

provide personalized service and support ticket tracking.

Constraints:
1.Cost:A Shop can be a significant investment for a car dealership. The cost
of the software, the hardware, and the implementation can all add up.

2.Complexity:A online Shop can be a complex system to implement and

manage. Dealerships need to have the staff and the resources to support the
system.

3.Integration:A Shop needs to be integrated with other dealership systems,

such as the accounting system and the customer relationship management
(CRM) system. This can be a challenge, especially for smaller dealerships.

4.Security:A Shop needs to be secure to protect customer data. Dealerships

need to take steps to protect the system from hackers and other threats.

page 14
 5.Detail Planning

5.1 :-Entity Relationship Diagram

Entity Relationship Diagram is also known as the ER diagram, ERD or ER model. It
is a type of structural diagram for use in database design. An ERD contains different
symbols and connectors that visualize major entities within scope and inter-
relationships among these entities

Entity Relationship Diagram for man saloon Online management system

page 15
The above Entity-Relationship explains the database relationship between the entities
at the implementation level of the system.

5.2 Data Flow Diagram

A DFD (Data Flow Diagram) is a graphical representation used to visualize

the flow of data within a system. It helps to understand how data is processed
by a system in terms of inputs and outputs, and how data moves between
different processes, data stores, and external entites for man saloon Online
management system

Contect level DFD

page 16
page 17
page 18
page 19
CLASS DIAGRAM

page 20
System design

page 21
Service list

page 22
Contact page

page 23
Appointment book

page 24
Admin sign in

page 25
Admin Dashboard

page 26
 Add Services

Manage services

page 27
About us update page

Contact update page

page 28
Admin panal appointment

page 29
Add Customer

page 30
Subscriber

Sales Report

page 31
 Software testing
1.Unit testing
1. User Authentication and Authorization

 Test Cases:
o Test login functionality with valid and invalid credentials.
o Test registration functionality with valid and invalid inputs.
o Ensure password recovery and reset work properly.
o Verify that unauthorized users cannot access protected routes/pages.
o Check user roles (admin, employee, customer) have appropriate
access.

2. Appointment Booking

 Test Cases:
o Test booking an appointment with valid inputs (time, date, service,
barber).
o Ensure no overlapping appointments for the same barber.
o Verify that canceled appointments update the availability.

3. Customer Management (Admin/Staff)

 Test Cases:
o Test adding a new customer with valid data (name, contact
information).
o Edit customer details and verify the update.
o Delete customer records and ensure they are removed from the system.
o Ensure no duplicate customer entries with the same contact
information.

4. Payment and Billing

 Test Cases:
o Process payment for a service and ensure correct billing.
o Handle different payment methods (credit card, cash, etc.).
o Test for insufficient funds or invalid payment methods.
o Ensure receipts are generated after successful payment.

page 32
2.Integration testing

1. User Registration and Appointment Booking

 Test Case: Ensure that once a new user registers, they can successfully log in
and book an appointment.
 Scenario:
o A new customer registers.
o The customer logs in.
o The customer books an appointment with a barber for a specific
service.
 Expected Outcome:
o Registration should return a success response.
o After login, the user should be able to access the appointment booking
functionality.
o The appointment should be confirmed, and the user should receive a
booking confirmation

2. Customer Deletion and Related Data Removal

 Test Case: Ensure that when a customer is deleted, their related appointments,
payments, and other data are handled correctly (either removed or flagged).
 Scenario:
o Admin deletes a customer account.
o Check whether all the customer’s appointments, payments, and records
are handled correctly.
 Expected Outcome:
o The customer should be deleted.
o Related records (e.g., future appointments) should also be removed or
flagged

6. Admin Dashboard and Reporting

 Test Case: Ensure that data from different subsystems (appointments,
payments, inventory) is correctly reflected in the admin dashboard and reports.
 Scenario:
o Admin views the sales report for a particular time period.
o The report should reflect accurate data from the appointment and
payment systems.
 Expected Outcome:
o The admin dashboard should display correct information regarding
appointments and sales.

 .

page 33
 3.System testing
a. User Registration and Login

 Test Case:
o Ensure that new users can register with valid data.
o Test that registered users can log in with valid credentials and are
redirected to their dashboard.
o Verify that invalid login attempts are handled correctly with error
messages.

Expected Outcome:

 Users should be able to register and log in successfully. Error messages should
appear for incorrect credentials.

b. Appointment Booking

 Test Case:
o Ensure customers can book appointments by selecting a service,
barber, date, and time.
o Check that available times are updated in real-time when bookings are
made.
o Verify that customers cannot book overlapping appointments.

Expected Outcome:

 Appointments should be successfully booked and the system should reflect the
updated schedule.

c. Service Management (Admin)

 Test Case:
o Admins should be able to add, edit, and delete services from the
system.
o Test that these changes are immediately reflected in the booking
system.

Expected Outcome:

 Any changes made to services should be visible in the customer’s booking

options.

page 34
 Limitations and Future Scope of
Enhancements

limitations
1. Scalability Issues

 Description: The system might not be designed to handle a growing number

of users, services, appointments, or data entries efficiently.
 Impact: As the salon expands, or if the system is used by multiple branches,
the system could experience slowdowns or crashes if it is not properly scaled
to handle larger loads.
 Mitigation: Ensure scalable infrastructure, cloud hosting, and load-balancing
mechanisms are in place.

2. Limited Customization
 Description: The system may not allow salons to fully customize features
such as service offerings, appointment types, or payment options based on
specific business needs.
 Impact: Different salons may have unique workflows, pricing models, or
customer preferences that cannot be accommodated, leading to operational
inefficiencies.
 Mitigation: Implement flexibility in service offerings, pricing structures, and
user interfaces to allow for better customization.

3. Dependency on Internet Connectivity

 Description: Being a web-based system, the salon management system
requires a stable internet connection to function.
 Impact: If the internet goes down, the salon staff may not be able to access
appointments, process payments, or manage inventory, which could disrupt
business operations.
 Mitigation: Develop offline functionality where possible, allowing certain
actions (like viewing appointments) to be available without an internet
connection.

page 35
 Future Scope of Enhancements
1. Advanced Reporting and Analytics
 Description: Provide detailed reporting and analytics on various aspects of the
business, including staff performance, customer demographics, service
popularity, and revenue.
 Benefit: Salon owners and managers can make data-driven decisions to
improve business efficiency, identify trends, and optimize resources.
 Enhancement Ideas:
o Customizable dashboards for real-time data monitoring.
o Revenue forecasting and cost analysis reports.
o Customer satisfaction surveys and feedback analysis.

2. Integration with Wearable Devices

 Description: Integrate the system with wearable devices such as smart

watches to send notifications and manage appointments directly from
wearables.
 Benefit: Customers can receive reminders, appointment confirmations, and
offers through their wearable devices, while staff can get schedule updates on-
the-go.
 Enhancement Ideas:
o Appointment alerts and reminders sent to smartwatches.
o Seamless booking through voice commands (Siri, Google Assistant).

3. Enhanced Customer Loyalty and Referral Programs

 Description: Implement more robust customer loyalty programs that offer

points, discounts, or rewards for frequent visits, referrals, and reviews.
 Benefit: Encouraging customer loyalty through rewards programs will
increase retention and incentivize customers to bring in referrals.
 Enhancement Ideas:
o Referral bonus programs integrated with social media.
o Tiered loyalty programs that unlock exclusive benefits.
o Digital loyalty cards for ease of use.

page 36
 Reference
https://www.w3schools.com/

https://www.mysql.com/

https://www.wikipedia.org/

https://getbootstrap.com/

Book referred…
1. HTML and CSS

2. PHP 5.power programming

3. PHP/MYSQL bible

4. PHP manual

page 37