Finalreport Merged
Finalreport Merged
CERTIFICATE
This is to certify that Harini.V, Rakshitha.V, and Rakshitha.R has satisfactorily completed
the project entitled “LAUNDRY MANAGEMENT” in partial fulfilment of the requirement
for the award of the degree of VI semester BCA (Bachelor of Computer Application) as per the
curriculum of Bengaluru City University for the period of MARCHJULY-2024
Signature of Examiners:
1.
2.
Date of Examination:
ACKNOWLEDGEMENT
We would like to thank Mrs. Varshini J.K, Asst. Professor and Miss
Pranamya EA, Asst.Professor for giving timely and valuable guidance during
the successful completion of this project.
They have been a constant source of inspiration, motivation for hard work, and
very co-operative throughout this project work. It could be our almost pleasure
to express our warm thanks for her encouragement, cooperation, and consent
without which we might not be able to accomplish this project. We also thank
Mrs. Nalini L, HOD, Dept. of Computer Science who has continuously
supported us in completing the project.
This project has been a new learning experience, which will stand worthy for us
in years to come. We would also like to thank our principal Dr. Vasundhara DE
for providing the facilities and allotted slots to work in the lab.
Finally, we would like to thank all individuals directly and indirectly related to
our project.
Harini.V
Rakshitha V
Rakshitha.R
DECLARATION
We, Harini.V, Rakshitha .V, and Rakshitha.R hereby declare that the project
work entitled “LAUNDRY MANAGEMENT SYSTEM” submitted to the
Bengaluru City University is a record of original work done by us under the
guidance of Mrs. Varshini J.K and Miss Pranamya. This project is submitted
in the partial fulfillment of the requirements for the award of degree of Bachelor
of Computer Applications.
Harini.V
Rakshitha. V
Rakshitha. R
ABSTRACT
2. Literature Survey 2
3. SRS 3-5
3.1 Functional Requirement
3.2 Non-Functional Requirement
3.3 Hardware Requirement
3.4 Software Requirement
4. Design 6-18
4.1 ER Diagram
4.2 Use Case Diagram
4.3 Data Flow Diagram
4.4 Database Design
5. Implementation 19-29
6. Testing 30-35
6.1 Test case table for user signup
6.2 Test case table for admin login
6.3 Test case table for user login
6.4 Test case table for cart
6.5 Test case table for payment
7. Screenshots 36-41
8. Conclusion 42
9. Future Enhancement 43
10. Bibliography 44
LAUNDARYMANAGEMENT
CHAPTER 1
INTRODUCTION
In an era where time is of the essence and efficiency is paramount, the laundry industry stands as a
cornerstone of convenience for individuals and essential for the smooth operation of various businesses.
However, the traditional methods of managing laundry operations often prove to be laborious, error-
prone, and time-consuming, leading to inefficiencies that can hinder both service providers and
customers a like.Recognizing these challenges, our project endeavors to revolutionize the landscape of
laundry services through the development of a sophisticated Laundry Management System (LMS). Built
upon the pillars of innovation and user-centric design, our LMS aims to streamline every aspect of the
laundry process, from intake to delivery, leveraging the latest advancements in technology to deliver
unparalleled efficiency and convenience.For customers, our LMS offers a seamless and intuitive
experience, allowing them to effortlessly schedule pickups, and make payments securely online. With
personalized options and transparent communication channels, customers can rest assured that their
laundry preferences and special instructions are meticulously catered to, ensuring a truly customized
Experience.
CHAPTER 2
LITERATURE SURVEY
The Laundry Management System is a comprehensive software solution designed to streamline and
automate various processes involved in managing a laundry business. It caters to the needs of laundry
service providers by offering efficient customer management, order processing, inventory management,
and reporting functionalities. At its core, the system provides a user-friendly interface accessible via web
browsers and mobile devices, ensuring convenience and accessibility for both customers and staff. Users
can create, update, and delete customer profiles, facilitating personalized service and efficient
communication.
Order processing is simplified through the system, allowing users to create new orders, and manage the
workflow seamlessly. Inventory management is another key feature, with the system maintaining a
comprehensive database of available items such as detergents, fabric softeners, and cleaning supplies.
Reporting functionalities provide valuable insights into inventory levels, and customer activity. Users
can generate detailed reports on a daily, weekly, or monthly basis, empowering informed decision-making
and strategic planning. Overall, the Laundry Management System offers a robust and efficient solution
for laundry businesses to optimize operations, enhance customer satisfaction, and drive business growth.
With its user-friendly interface, comprehensive features, and powerful functionalities, it is poised to
revolutionize the way laundry services are managed and delivered.
CHAPTER 3
A Software Requirements Specification (SRS) is a document that outlines the functional and non-
functional requirements of a software system. It serves as a blueprint for software development,
providing a comprehensive overview of what the system is expected to do and how it should behave.
Module 3.1
FUNCTIONAL REQUIREMENTS
2. Order Management:
• Customers should be able to place laundry orders, specifying details such as service type (e.g.,
wash & fold, dry cleaning), pickup/delivery preferences, and special instructions.
• Laundry businesses should be able to view and manage incoming orders, including accepting,
rejecting, or modifying orders as needed.
• The system should allow customers to schedule pickup and delivery times for their laundry
orders.
• Laundry businesses should be able to optimize pickup and delivery to maximize efficiency and
minimize travel time.
• Real-time tracking of delivery vehicles may be implemented to provide customers with accurate
ETAs.
• Customers should be able to view pricing information for different laundry services and make
payments securely through the system.
• The system should generate invoices for completed orders, including itemized breakdowns of
charges.
• Integration with payment gateways (e.g., credit card processors, mobile wallets) may be required
to facilitate online payments.
Module 3.2
NON-FUNCTIONAL REQUIREMENTS
1.Performance:
• Response Time: The system should respond to user interactions (e.g., order placement, status
updates) within a reasonable timeframe, typically within a few seconds.
• Throughput: The system should be capable of handling a large number of concurrent users and
transactions, especially during peak hours.
• Scalability: The system should be able to scale horizontally to accommodate increasing user load
without significant degradation in performance.
2.Security:
• Data Encryption: Sensitive user data (e.g., personal information, payment details) should be
encrypted both in transit and at rest to protect against unauthorized access or interception.
• Access Control: Role-based access control (RBAC) should be implemented to restrict access to
certain features or data based on user roles and permissions.
• Audit Trails: The system should maintain audit logs of user activities and system events for
accountability and traceability purposes.
• Security Compliance: The system should adhere to industry standards and best practices for data
security, such as GDPR, PCI DSS, or HIPAA, depending on the nature of the data being handled.
3. Usability:
• User Interface Design: The user interface should be intuitive, visually appealing, and easy to
navigate, catering to users with varying levels of technical expertise.
• Accessibility: The system should be accessible to users with disabilities, complying with
accessibility standards such as WCAG (Web Content Accessibility Guidelines).
• Multi-platform Compatibility: The system should be compatible with different devices and
operating systems, including desktop computers, tablets, and smartphones.
4 Maintainability:
• Modularity: The system should be designed with a modular architecture, allowing for easy
maintenance, updates, and future enhancements.
• Documentation: Comprehensive documentation should be provided for developers,
administrators, and end-users, covering installation, configuration, usage, and troubleshooting
procedures.
• Code Quality: The system code should adhere to coding standards and best practices to facilitate
readability, maintainability, and collaboration among developers.
• Response Time: The system should respond to user interactions (e.g., order placement, status
updates) within a reasonable timeframe, typically within a few seconds.
Module 3.3
H/W System Configuration:
Module3.4
S/W System Configuration:
Technology Php,sql
Front End Html,CSS
CHAPTER 4
DESIGN
Module 4.1
Definition: An Entity Relationship (ER) Diagram is a type of flowchart that illustrates how
"entities" such as people, objects or concepts relate to each other within a system. ER Diagrams
are most often used é to design or debug relational databases in the fields of software
engineering, business information systems, education, and research. Also known as ERDs or
ER Models, they use a defined set of symbols such as rectangles, diamonds, ovals, and
connecting lines to depict the interconnectedness of entities, relationships, and their attributes
They mirror grammatical structure, with entities as nouns and relationships as verbs. ER
diagrams are related to data structure diagrams (DSDs), which focus on the relationships of
elements within entities instead of relationships between entities themselves. ER diagrams also
are often used in conjunction with data flow diagrams (DFDs), which map out the flow of
information for processes or systems. ER models ad and data models are typically
drawn at up to three levels of detail:
-Conceptual data model: The highest-level view containing the least detail. Its value is
showing the overall scope of the model and portraying the system architecture. For a system
of smaller scope, it may not be necessary to draw. Instead, start with the logical model.
- Logical data model: Contains more detail than a conceptual model. More detailed operational
and transactional entities are now defined. The logical model is independent of the technology
in which it will be implemented
Physical data model: One or more physical model may be developed from each logical model.
The physical models must show enough technology detail to produce and implement the actual
database.
SYMBOLS FUNCTION
OVAL Represents different attributes of the entity.
Adds
Created
By Amount
Date
Paid
Type
Packages
Admin price
Package Description
name
Password
Admin Id Packages
Admin Login Add
Admin name
Add services
Order list
Customer
Date Amount
Name
Module 4.2
Module 4.3
The data flow diagram (DFD) is one of the most important tools used by system analysis. Data
Flow diagrams are made up of a number of symbols, which represent system components. Most
data flow modeling methods use four kinds of symbols. These symbols are used to represent four
kinds of system components. Processes are represented by ircles in DFD. Data Flow is
represented by a thin line in the DFD and each data store has a unique name and a square or
Unlike a detailed flowchart, a Data Flow diagram does not supply a detailed description of the
modules but graphically describes a system's data and how the data interact with the system
DFD DIAGRAM
ADMIN
Level 0:
ADMIN
LAUNDRY
MANAGEMENT
DD
Level 1:
ADMIN
Verification
Admin details Login
Validation
Dashboard
Level 2:
ADMIN
Verification
Admin details LOGIN
Validation
ADD SERVICES
ADD QUANTITY
CUSTOMER
Level 0:
CUSTOMER
LAUNDRY
MANAGEMENT
Level 1:
CUSTOMER
Level 2:
CUSTOMER
Verification
Customer LOGIN
reregistration
details
Validation
HOME PAGE
MODULE 4.4
DATABASE DESIGN
Screenshot 4.4.1 USER SIGNUP TABLE(THIS TABLE CONTAINS THE USER DETAILS)
Screenshot 4.4.2 ADMIN LOGIN TABLE (THIS TABLE CONTAINS THE ADMIN DETAILS)
CHAPTER 5
IMPLEMENTATION
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>LAUNDRY MATE</title>
<link href="https://fonts.googleapis.com/css2?family=Open+Sans:wght@400;600;800&
display=swap" rel="stylesheet">
<link href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.0/css/all.
min.css" rel="stylesheet"
</head>
<body>
<div class="container">
<div class="row">
</div>
</div>
</div>
</div>
</div>
</div>
</nav>
</div>
</div>
</a>
data- target="#navbarCollapse">
<span class="navbar-toggler-icon"></span>
</button>
id="navbarCollapse">
</div>
</div>
</body> </html>
</div>
</div>
</nav></div>
<div class="carousel-inner">
</div>
</div>
</div>
<div class="carousel-item">
</div>
</div>
</div>
</div>
</div>
</a>
</div>
</a>
</div>
</div>
<div class="row">
<div class="d-inline-flex">
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div></div></div>
</div>
<div class="col-lg-5">
</div>
<div align-text:center>
<p>Word’s got around, hasn’t it? We are Bengaluru’s shiny new app backed by world-class
facilites. We pick up and deliver at your doorstep... and that too at amazingly affordable prices.
Everyday laundry, next-day delivery! Couldn’t get better than that.</p></div>
<div>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<style>
.image-container {
display: flex;
justify-content: space-between;
.rounded-image {
.rounded-image:last-child {
margin-right: 0;
</style>
</head>
<body>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Icon Container</title>
<style>
.icon-container {
display: flex;
justify-content: space-between;
align-items: center;
.icon {
text-align: center;
max-width: 300px;
.icon img {
width: 150px;
height: 150px;
overflow: hidden; /* This ensures the image stays within the rounded border */
.icon p:first-of-type {
font-weight: bold;
margin-bottom: 5px;
</style>
</head>
<body>
<div class="icon-container">
<div class="icon">
<p>At Bengaluru</p>
<p>A professional laundry service near you that delivers high standards of quality, care and service.
So reassuring, isn't it?</p>
</div><div class="icon">
<p style="font-color:blue;">Get laundry pickup and drop right where you are – no stepping out or
chasing or waiting or worrying. How convenient is that?</p>
</div><div class="icon">
<p>When we say 24-hour laundry service, it's exactly that – because it's on-the-spot, on-the-dot.
What's that word you immediately thought of... clockwork?</p>
<p>You'd never have guessed how amazingly affordable it is. You can even ask for reprocessing or
a refund, no questions asked. Isn't that thoughtful?</p>
</div>
</div>
</body>
</html>
CHAPTER 6
TESTING
-SYSTEM TESTING
Testing
Testing forms the first step in determining the error in whether the actual software product matches
expected requirements and to ensure that the software program Testing is a method to check product is
Defect free. It involves the execution of software/system components using manual or automated tools
to evaluate one or more properties of interest. The purpose of software testing is to identify errors, gaps,
or missing requirements contrast to actual requirements.
-TYPES OF TESTING
Unit Testing:
This software testing approach S followed by the programmer to test the unit of the program.helps
normally considered adjacent to the coding step. After the source-level code has been developed,
reviewed. and verified for the correct syntax, unit test case design begins. The local data structure for a
module is a common source of errors.
Integration Testing:
The next level of testing is integration testing. In this level many tested modules are combined into
subsytems which are then tested.This is done to detect errors.This level of testing emphasizes on the
interfaces between the module.
System Testing:
The third level of testing is system testing.When the system is put together,system testing is done.In
this,the system is used to see if all requirements are met and whether it performs as per the
requirements.
This is a major activity in the testing process.Test cases have to be specified in each unit .The test case
specification gives the details of all cases,inputs to be used and the expected outputs for these test cases.
APPROACHES TO TESTING:
Functional Testing:
In the functional testing the structure of the program is not considered.The test cases are decided on the
basis of the requirement of the program module and the intervals of the module are not considered for
the selection of the test cases.
Validation:
The goals of verification and validation activities are to access and 1mprove the quality of the work
products are generated during the development and modification of software.Quality Attributes of
interest include correctness usefulness efficiency and cost efficitiveness.Verfication and validation
involves the assessment of work products to determine confirmence of specification.Validation is a
process of evaluating the software at the end of the software development Testing.
CHAPTER -7
SCREEENSHOTS
CHAPTER 8
CONCLUSION
In conclusion, the laundry management system emerges as a transformative solution for optimizing
laundry operations across various sectors. With its centralized management capabilities, automation
features, the system promises to revolutionize traditional laundry processes, bringing efficiency and
convenience to both operators and customers alike. By streamlining tasks such as order processing, and
customer management, the system enhances operational efficiency, reduces manual errors, and improves
resource utilization. Moreover, the inclusion of a customer portal empowers users to conveniently place
orders, and make payments, thereby enhancing the overall customer experience and fostering loyalty.
Furthermore, the system's integration capabilities ensure compatibility with existing hardware and
software systems, enabling seamless adoption and scalability. The benefits of the laundry management
system extend beyond operational improvements, offering economic, environmental, and social impacts.
By reducing costs, improving productivity, and enhancing accessibility to laundry services, the system
has the potential to generate significant economic benefits and contribute to sustainability efforts.
Ultimately, the laundry management system represents a paradiagram shift in the industry, leveraging
innovation and technology to deliver superior services, create value, and meet the evolving needs of
modern laundry facilities and their customers.
CHAPTER 9
FUTURE ENHANCEMENT
In envisioning future enhancements for a laundry management system, several key areas can significantly
elevate its efficiency and customer satisfaction. Enhanced customer communication tools, such as SMS,
email can keep customers informed about order status and promotions, enhancing their overall experience.
Integrating payment options into the system ensures seamless and secure transactions, improving
convenience for customers. Furthermore, customizable reporting and analytics tools empower operators
to gain actionable insights into key performance metrics, facilitating data-driven decision-making and
continuous improvement. Sustainability initiatives, including eco-friendly practices and energy-efficient
appliances, can minimize the environmental impact of laundry operations while attracting
environmentally conscious customers.By incorporating these future enhancements, a laundry
management system can become more efficient, and sustainable, positioning the business for long-term
success in a competitive market.
CHAPTER-10
BIBILIOGRAPHY
• https://youtu.be/lpqtph4VuIA?feature=shared
• https://www.canva.com/en_in/
• https://openai.com/blog/chatgpt/
• https://laundrymate.in/
• https://uriverse.com/
• https://youtu.be/lpqtph4VuIA?feature=shared