Project Report

On

LAUNDRY MANAGEMENT
SYSTEM

Submitted By:
{Your Name}

In partial fulfillment for the award of the degree of

{Your Degree}

In

{Your College Name}

 {Your College Name}

CERTIFICATE
Certified that this is a bonafide record of the project work titled

LIBRARY MANAGEMENT SYSTEM

Done by

{Your Name}

Of { _} semester {Your degree} in the year 20_ _ in

partial fulfillment of the requirements for the award of Degree of {Your Degree} of
{Your College Name.}

{Guide name} {Head of the division name}

Project Guide Head of the
Division
 ACKNOWLEDGEMENT

We take this occasion to thank God, almighty for blessing us with his grace and taking

our endeavor to a successful culmination. We extend our sincere and heartfelt thanks to

our esteemed guide, {Guide Name}, for providing us with the right guidance and advice

at the crucial junctures and for showing me the right way. We also take this opportunity

to express a deep sense of gratitude to our class coordinators, {Coordinators name1}

and {Coordinators name2} for their cordial support, valuable suggestions and guidance.

We extend our sincere thanks to our respected Head of the division {Name}, for

allowing us to use the facilities available. We would like to thank the other faculty

members also, at this occasion. Last but not the least, we would like to thank our friends

and family for the support and encouragement they have given us during the course of

our work.
 ABSTRACT

We present the design and implementation of a laundry management system (LMS) used
in a laundry establishment. Laundry firms are usually faced with difficulties in keeping
detailed records of customers’ clothing; this little problem, as seen by most laundry firms,
is highly discouraging as customers are filled with disappointments, arising from issues
such as customer clothes mix-ups and untimely retrieval of clothes.

The aim of this application is to determine the number of clothes collected, in relation
to their owners, as this also helps the users fix a date for the collection of their clothes.
Also, the customer’s information is secured, as a specific id is allocated per registration
to avoid contrasting information.
 CHAPTER 1
INTRODUCTION

Laundry firms currently use a manual system for the management and maintenance of
critical information. The current system requires numerous paper forms, with data stores
spread throughout the laundry management infrastructure. Often information (on forms)
is incomplete or does not follow management standards. Records are often lost in transit
during computation requiring a comprehensive auditing process to ensure that no vital
information is lost. Multiple copies of the same information exist in the laundry firm data
and may lead to inconsistencies in data in various data stores.

A significant part of the operation of any laundry firm involves the acquisition,
management and timely retrieval of great volumes of information. This information
typically involves customer personal information and clothing records history, user
information and retrieval period, users scheduling as regards customers details and
dealings in service rendered, also our products package waiting list. All of this
information must be managed in an efficient and cost-wise fashion so that the
organization resources may be effectively utilized.

The goal of laundry management system is to automate the management of the laundry
firm, making it more efficient and error free. It aims at standardizing data, consolidating
data, ensuring data integrity and reducing inconsistencies, through the use of a highly
computerized process that is stress free, reliable and quick through the use of asp.net
computer programming language and SQL database application to both the users and the
staff in charge of the registration and laundry management processes. HTML would be
at the front-end and provide the graphical user interface that relates with the user, while
the SQL database will be at the back end to handle the data storage process.
1.1 BACKGROUND OF PROJECT

Today' s modernization flow of the world has witnessed tremendous change in lifestyle of society.
Computerized systems in managing laundry have been well accepted, especially in developing countries.
This service is well accepted because it gives flexibility in terms of time for laundry management team to
use it and this really helps them with their time management. The concept of computerized laundry
management system in higher institutions is being developed by Katsina State Laundry companies. Katsina
state has a very large number of laundry shops and Companies. Before this, the management of this
company is constructing by using manual business process. All the information about the customer and
staff are kept separately by using file system. It will cause the process of searching for information take
more time and quite difficult.

Laundry management system (LMS) is a new system that replaced the file system which
most of laundry shops use. LMS is developed in order to ease the management in the
laundry shop and to change the manual business process to the systematic business
process. The LMS is developed for the managers and staff that rolled onto the laundry
business.

1.2 OBJECTIVES

The aim of this project is to develop a system that can handle and manage the activities
involved in a laundry in an efficient and reliable way.

The objectives for this project are:

i. Computerized System: The proposed system will implement the computerized
system which can perform a better managing process for the laundry. The data of the
laundry service and the customer will keep in the save manner without the problem
of losing the data.

ii. System and User Privileges: System and user privileges will be implemented in the
proposed system to setting up the user level for each system user. This function is to
provide the limitation of system accessing.

iii. Increase time performance: The time management is very important for the laundry
management to ensure the service performs in better condition and on time. In
 addition, by using the computerized system, the business process will be more
effective and faster.

iv. Improve Inventory Management: Accurately track inventory levels, monitor

usage, and automate replenishment to reduce stockouts and overstocking.

v. Support Sustainability: Implement energy-efficient practices, reduce water

consumption, and promote eco-friendly laundry practices to minimize environment
impact.

vi. Expand Market Share: Increase market share through improved customer
satisfaction, competitive pricing, and expanded services.

vii. Support Business Growth: Provide a scalable and flexible platform to support
business growth, expansion, and diversification.

1.3 SCOPE
1. Order Management: Manage customer order, including order placement, tracking,
and status updates.

2. Inventory Management: Track and manage laundry inventory, including supplies,

equipment, and linen.

3. Equipment Monitoring: Monitor and track laundry equipment performance,

Including usage, maintenance, and repair.

4. Billing and payment: Manage billing and payment processes, including invoice,
payment tracking, and reporting.

5. Customer Management: Manage customer information, including contact details,

order history, and preferences.

6. Reporting and Analytics: provide real-time reporting and analytics on laundry

operations, including order volume, revenue, and equipment performance.

7. User Management: Manage user roles and permission, including, administrator,

staff, and customer access.
 CHAPTER 2
SYSTEM ANALYSIS

System analysis is the detailed study of various operations performed by a system and
their relationships within and outside of the system. Here the key question is —what all
problems exist in the present system? What must be done to solve the problem?

2.1 SRS (SOFTWARE REQUIREMENTS SPECIFICATION)

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.

2.1.1 FUNCTIONAL REQUIREMENTS

1. User Registration and Authentication:

• Users should be able to create accounts and log in securely.
• Different user roles (e.g., customers, administrators, laundry staff) may have
different levels of access and permissions.

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.
 3 Scheduling and Routing:

• 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.

4. Billing and Payment Processing:

• 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.

2.1.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.

2.2 FEASIBLITY ANALYSIS

Whatever we think need not be feasible.it is wise to think about the about the feasibility
of any problem we undertake. Feasibility is the study of impact, which happens in the
organization by the development of a system. The impact can be either positive or
negative. When the positive nominate the negative, then the system is considered
feasibility study can be performed in two ways such as technical feasibility and
economical feasibility.

1. TECHNICAL FEASIBILITY:
We can strongly say that it is technically feasible, since there will not be much
difficulty in getting required resources for the development and maintenances of the
same is available in the organization here, we are utilizing the resources which are
available already.

2. OPERATIONAL FEASIBILITY:

Operational feasibility refers to the measure of solving problems with the help of a
new proposed system. It helps in taking advantage of the opportunities and fulfills
the requirements as identified during the development of the project. It takes care
that the management and the users support the project.

3. ECONOMICAL FEASIBILITY:
Development of this application is highly economically feasible. The organization
needed not spend much money for the development of the system already available.
The only thing is to be done is making an environment for the development with an
effective supervision. lf we are doing so, we are attain the maximum usability of the
corresponding resources. Even after development, the organization will not be in
 condition to invest more in the organization. Therefore, the system is economically
feasible.

2.3 EXISTING VS. PROPOSED SYSTEM

1. EXISTING SYSTEM:
Laundry firm currently uses a manual system for the management and maintenance of
critical information. The current system requires numerous paper forms, with data stores
spread throughout the laundry firm management infrastructure. Often information is
incomplete or does not follow management standards. Forms are often lost in transit
between departments requiring a comprehensive auditing process to ensure that no vital
information is lost. This has leads to inconsistencies in various data due to large volume
of contrasting customer details leading to mix-up of clothes in the laundry firm which
thus leads to delay in collecting the clothes back.

2. PROPOSED SYSTEM:
The Laundry Management System is designed for any laundry firm to replace their
existing manual, paper-based system. These services are to be provided in an efficient,
cost-effective manner, with the goal of reducing the delay and resources currently
required for such tasks as clothes details are bounded by customer name. Since the
existing system makes use of tedious administrative tasks, lots of paperwork and time, in
which full information cannot be gotten from busy customers.
The goal of the laundry database management system is to provide a computerized
process that is stress free, reliable PHP would be at the front-end and provide the
graphical user interface that relates with the user, while the SQL database will be at the
back-end to handle the data storage process.

The objective of this work is to implement a management system that will streamline
registration process, reduce administrative tasks and paperwork so as to improve the
registration cycle process flow.
 CHAPTER 3
SOFTWARE TOOLS

The Laundry Management System (LMS) project is structured into two main
components: the front end and the back end. Each component utilizes specific tools and
technologies to achieve the desired functionality and performance.

3.1 Front End

The front end of the LMS is developed using a combination of HTML, CSS, JavaScript,
and PHP. These technologies work together to create a dynamic, interactive user interface
for the application.

3.1.1 HTML (Hypertext Markup Language):

HTML is the foundational markup language for creating web pages. It provides the
structure of the web pages by using tags enclosed in angle brackets (e.g., <html>,
<head>, <body>). HTML elements, such as headings, paragraphs, lists, and links,
form the basic building blocks of web content. HTML enables the embedding of
images, videos, and interactive forms, making it essential for structuring the content
of the LMS web pages.

3.1.2 CSS (Cascading Style Sheet):

CSS is used to control the visual presentation and layout of HTML documents. It
allows for the separation of content from presentation, enabling developers to define
styles for elements such as colours, fonts, and layouts. CSS enhances the visual
appeal of the LMS by providing consistent styling across different pages and
ensuring a responsive design that adapts to various devices and screen sizes. CSS
also allows for the application of different styles based on user preferences and
device characteristics.
 3.1.3 JavaScript:
JavaScript is a versatile scripting language used to create dynamic and interactive
elements on web pages. It enables client-side scripting, allowing the LMS to
respond to user actions in real time, such as form submissions, button clicks, and
asynchronous data loading. JavaScript also supports features like form validation,
interactive interfaces, and improved user experience through real-time updates.
Additionally, JavaScript frameworks and libraries (such as jQuery) may be
employed to simplify development and enhance functionality.

3.1.4 PHP (Hypertext Preprocessor):

PHP is a server-side scripting language used to develop dynamic web applications.
It processes server-side logic and interacts with databases to generate dynamic
content. In the LMS, PHP handles tasks such as user authentication, data processing,
and interaction with the MySQL database. PHP scripts are embedded within HTML
documents to create responsive and interactive web pages that can handle complex
operations and user interactions.

3.2 Back End

The back end of the LMS is built using MySQL, a robust relational database
management system (RDBMS) designed for handling data storage and retrieval.

3.2.1 MySQL
MySQL is a widely used open-source RDBMS that provides a reliable and efficient
platform for managing and querying databases. It supports SQL (Structured Query
Language) for database operations, including data retrieval, insertion, updating, and
deletion. MySQL is known for its performance, scalability, and ease of use, making
it a popular choice for web applications. In the LMS, MySQL is used to design and
manage the database that stores essential information such as user profiles, book
records, and transaction histories. MySQL’s integration with PHP allows for
seamless data handling and dynamic content generation on the front end.
3.3 Working Environment

Hardware Requirements

XAMPP Software installs on a standard PC system. Minimum Hardware

requirements are as follows:

✓ Processor – Celeron (R) Dual – Core CPU [email protected] 1.90 GHz.

✓ Installed Memory (RAM) – at least 350 MB.
✓ System type – 32-bit Operating System.
✓ Model - Presario CQ42 Notebook PC.
✓ Resolution - 1366/768.

Software requirements

XAMPP
XAMPP is an easy to install Apache distribution containing MySQL, PHP and Perl.
XAMPP is really very easy to install and to use - just download, extract and start.

XAMPP for Windows

The distribution for Windows 2000, 2003, XP, Vista, 7 and 8. This version contains:
Apache, MySQL, PHP + PEAR, Perl, mod_php, mod_perl, mod_ssl, OpenSSL,
phpMyAdmin.

Webalizer, Mercury Mail Transport System for Win32 and NetWare Systems v3.32,
Ming, FileZilla FTP Server, mcrypt, eAccelerator, SQLite, and WEB-DAV +
mod_auth_mysql.

✓ Apache 2.4.9
✓ MySQL 10.1.31
✓ Maria DB
✓ PHP 7.2.3
✓ phpMyAdmin 4.7.9

Programming Language

✓ HTML
✓ CSS
✓ jQuery
✓ PHP
✓ MySQL
 CHAPTER 4

SYSTEM DESIGN

4.1 System Flow chart

User Flow chart

Admin Flow chart
Use Case flow Diagram (User)

CHANGE
PASSWORD
Use Case flow Diagram (admin)
4.2 ER Diagram Symbols Description

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 model’s 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
shows the overall scope of the model and portrays 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.
ER Diagram Symbols Description Tables

SYMBOLS FUNCTION

OVAL Represents different attributes of the entity.

RECTANGLE Represents different entity set used in a

diagram.

DIAMOND Represents the relationship among the entity.

LINE Represents the link between entity set to

attributes and entity set to relationship.
ER Diagram
4.3 Data Flow chart

A DFD does not show a sequence of steps. A DFD only shows what the different process
in a system is and what data flows between them.

Rules for DFD:

• Fix the scope of the system by means of context diagrams.

• Organize the DFD so that the main sequence of the actions reads left to
right and top to bottom.
• Identify all inputs and outputs.
• Identify and label each process internal to the system with rounded
circles.
• A process is required for all the data transformation and transfers.
Therefore, never connect a data store to a data source or the
destinations or another data store with just a data flow arrow.
• Do not indicate hardware and ignore control information.
• Make sure the names of the processes accurately convey everything the
process is done.
• There must not be unnamed process.
• Indicate external sources and destinations of the data, with squares.
• Number each occurrence of repeated external entities.
• Identify all data flows for each process step, except simple Record
retrievals.
• Label data flow on each arrow.
• Use details flow on each arrow.
• Use the details flow arrow to indicate data movements.
• There can’t be unnamed data flow.
• A data flow can’t connect two external entities.
Level of DFD

The complexity of the Railway Ness system means that it is a responsible to represent
the operations of any system of single data flow diagram. At the top level, an Overview
of the different systems in an organization is shown by the way of context analysis
diagram.

They are represented by:

• LEVEL 0: SYSTEM INPUT/OUTPUT
• LEVEL 1: SUBSYSTEM LEVEL DATAFLOW FUNCTIONAL
• LEVEL 2: FILE LEVEL DETAIL DATA FLOW.
The input and output data shown should be consistent from one level to the next.

LEVEL 0: SYSTEM INPUT/OUTPUT

A level 0 DFD describes the system-wide boundaries, dealing with inputs to and outputs
from the system and major processes. This diagram is similar to the combined user-level
context diagram.

LEVEL 1: SUBSYSTEM LEVEL DATAFLOW FUNCTIONAL

A level 1 DFD describes the next level of details within the system, detailing the data
flows between subsystems, which makeup the whole.

LEVEL 2: FILE LEVEL DETAIL DATA FLOW.

All the projects are feasible given unlimited resources and infinite time. It is both
necessary and prudent to evaluate the feasibility of the project at the earliest possible
time. Feasibility and risk analysis are pertained in many ways. If project risk is great.
Zero Level DFD Flow
FIRST LEVEL DTAFLOW DIAGRAM
SECOND LEVEL DTAFLOW DIAGRAM

Admin
User
4.4 Database Design

The data in the system has to be stored and retrieved from the database. Designing the
database is part of system design. Data elements and data structures to be stored have
been identified at analysis stage. They are structured and put together to design the data
storage and retrieval system.

A database is a collection of interrelated data stored with minimum redundancy to serve

many users quickly and efficiently. The general objective is to make database access
easy, quick, inexpensive and flexible for the user. Relationships are established between
the data items and unnecessary data items are removed. Normalization is done to get an
internal consistency of data and to have minimum redundancy and maximum stability.
This ensures minimizing data storage required, minimizing chances of data
inconsistencies and optimizing for updates. The MS Access database has been chosen
for developing the relevant databases.

Laundry Management System (lmsdb) contains for MySQL tables:

✓ tbladmin
✓ tbllaundryreq
✓ tblpricelist
✓ tbluser

Structure of MySQL tables :

tbladmin Table (This table contains admin login details)

 tbllaundryreq Table (This table contacts all laundry requests)

tblpricelist (This table contains the price of the laundry

tbluser Table (This table contains the user details)

MySQL Tables Relationship
Class Diagram:
A description of a set of objects that share the same attributes operations,
relationships, and semantics
 CHAPTER 5
IMPLEMENTATION

5.1 Modules
In this project, we use PHP and MySQL database. It has two modules:
✓ User
✓ Admin

5.1.1 User Modules

• User Signup – In this section user can register himself. After successful signup,
he/she can sign in into the system.
• Dashboard: In this section, the user can view the status of his laundry request
and price of the laundry.
• Laundry Request: In this section, user can send the laundry request by filling the
laundry detail form.
• Request Status: In this section, user can check his/her laundry request status
which is done by admin (means his/her request is at what step).
• A user can also update his/ her profile, change the password and recover the
password.

5.1.2 Admin Modules

• Dashboard: In this section, admin can see laundry requests of all user(means
how many are a new request, accept the request, in-process request and finish
request) in brief.
• Reg Users: In this section, admin can view user detail and update user detail.
• Laundry Request: In this section, admin can see the detail of the laundry
request and also change the stage of the laundry request.
• Manage Laundry Price: In this section, admin can change the laundry price
according to a market price
• Reports: In this section, admin can see the laundry request according to dates
and admin can also count request on the basis of month and year.
 • Notification: In this section, admin gets the notification if any user request for
laundry.

5.2 Codes
<?php session_start ();
error_reporting (0);
include('user/include/dbconnection.php');
?>
<!DOCTYPE html>
<html>
<head>
<title>Laundry Management System</title>
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta charset="utf-8">
<link href="css/bootstrap.min.css" rel="stylesheet" type="text/css"
media="all">
<link href="css/font-awesome.min.css" rel="stylesheet" type="text/css"
media="all">
<link href="css/owl.carousel.css" rel="stylesheet">
<link rel="stylesheet" href="css/lightbox.css">
<link type="text/css" rel="stylesheet" href="css/cm-overlay.css" />
<link href="css/style.css" rel="stylesheet" type="text/css"
media="all"/>
<link href="//fonts.googleapis.com/css?family=Open+Sans"
rel="stylesheet">
<link href="//fonts.googleapis.com/css?family=Roboto+Condensed"
rel="stylesheet">
<link href="//fonts.googleapis.com/css?family=Sintony:400,700&amp;
subset=latin-ext"
rel="stylesheet">
</head>
<body>
<! -- banner -->
<div class="w3l_banner">

<div class="w3_bandwn">
<div class="container">
<div class="col-md-6 w3_l">
<i class="fa fa-envelope-o" aria-hidden="true"></i> <a
href="mailto:[email protected]">Laundry Management System</a>
</div>

<div class="clearfix"></div>
</div>
</div>
<nav class="navbar navbar-default">
<div class="container">
<! -- Brand and toggle get grouped for better mobile display -->
<div class="navbar-header">
<button type="button" class="navbar-toggle collapsed" data-
toggle="collapse" data-target="#bs-example-navbar-collapse-1" aria-
expanded="false">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
 <h1><a class="navbar-brand" href="#">LMS</a></h1>
</div>

<!-- Collect the nav links, forms, and other content for toggling -->
<div class="collapse navbar-collapse" id="bs-example-navbar-
collapse-1" >
<ul class="nav navbar-nav">

<li><a href="#index.php" class="page-scroll">HOME</a></li>

<li><a href="#about" class="page-scroll">ABOUT</a></li>
<li><a href="#services" class="page-
scroll">SERVICES</a></li>
<li><a href="#gallery" class="page-
scroll">GALLERY</a></li>
<li><a href="#contact" class="page-scroll">PRICING</a></li>
<li><a href="user/" class="page-scroll">User</a></li>
<li><a href="admin/" class="page-scroll">Admin</a></li>

</div><! -- /.navbar-collapse -->

</div><! -- /.container-fluid -->
</nav>
<div class="w3l_bandwn">
<h2>Welcome to Laundry</h2>
<div class="about-p text-center">
<span class="sub-title"></span>
<span class="fa fa-star" aria-hidden="true"></span>
<span class="sub-title"></span>
</div>
<h3>Washing Clothes</h3>

</div>
</div>
<! -- /features -->
<div class="about" id="about">
<div class="features" id="features">
<div class="container">
<h3>About Us</h3>
<div class="tittle_head_w3layouts">
<h4>Powerful Features</h4>

</div>
<div class="inner_sec_info_agileits_w3">
<! -- <div class="border1"> -->
<div class="w3_banup">
<div class="col-md-4 w3_ret">
<div class="col-md-10 w3_txt">
<h4>Wash Cycle</h4>
</div>
<div class="col-md-2 w3ls_ic">
<i class="fa fa-comment-o" aria-
hidden="true"></i>
</div>

<div class="clearfix"></div>

<div class="col-md-10 w3_txt">

 <h4>Tumble Drying</h4>
</div>
<div class="col-md-2 w3ls_ic">
<i class="fa fa-microphone" aria-
hidden="true"></i>
</div>
<div class="clearfix"></div>

<div class="col-md-10 w3_txt">

<h4>Customize Quickly</h4>
</div>
<div class="col-md-2 w3ls_ic">
<i class="fa fa-cubes" aria-hidden="true"></i>
</div>
<div class="clearfix"></div>

</div>
<div class="col-md-4 w3l_mid">
<div class="bulb">
<img src="images/pic.jpg" alt="" />
</div>
</div>
<div class="col-md-4 wthree_r">
<div class="col-md-2 w3ls_ic">
<i class="fa fa-street-view" aria-hidden="true"></i>
</div>
<div class="col-md-10 w3_txt">
<h4>Sorting</h4>
 </div>
<div class="clearfix"></div>

<div class="col-md-2 w3ls_icr">

<i class="fa fa-futbol-o" aria-hidden="true"></i>
</div>
<div class="col-md-10 w3_txt">
<h4>Mildew Effect</h4>
</div>
<div class="clearfix"></div>

<div class="col-md-2 w3ls_icr">

<i class="fa fa-laptop" aria-hidden="true"></i>
</div>
<div class="col-md-10 w3_txt">
<h4>Crocking. </h4>
</div>
<div class="clearfix"></div>
</div>

<div class="clearfix"></div>
</div>
</div>
<! -- </div> -->
</div>
</div>
</div>
<! -- //features -->
</div>
</div>
<! -- Order Form-->
<! -- /Order Form-->
<! -- Services-->
<div class="services" id="services">
<div class="container">
<h3>Services</h3>
<div class="col-md-4 hhh">
<div class="wthree_rt">
<h4>Normal Cloths Washing</h4>
</div>
</div>
<div class="col-md-4 hhh">
<div class="wthree_rt">
<i class="fas fa-tshirt" aria-hidden="true"></i>
<h4>Woolen Clothes Washing</h4>
</div>
</div>
<div class="col-md-4 hhh">
<div class="wthree_rt">

<h4>
Washing and Ironing</h4>
</div>
</div>
<div class="clearfix"></div>
<div class="w3l_serdwn">
<div class="col-md-4 hhh">
<div class="agile_ser">
<h4>
Bedsheets, Sofa Cover and Quilt Cleaning</h4>
</div>
</div>
<div class="col-md-8 W3ls_serv">
<div class="agile_ser ">
<div class="col-md-6 wthree_l">
<p>FREE CUFF ANDCOLLAR CLEANING</p>
</div>
<div class="col-md-6 wthree_rts">
<img src="images/s1.jpg" class="img-responsive" alt="">
</div>
<div class="clearfix"></div>
</div>
</div>
<div class="clearfix"></div>
</div>
</div>
</div>
<! -- /Services-->
<! -- gallery -->
<div class="gallery" id="gallery">
<div class="container-fluid">
<h3>Gallery</h3>

<div class="about-bottom w3ls-team-info">

<div class="col-md-12">
<div id="Carousel" class="carousel slide">
<! -- Carousel items -->
 <div class="carousel-inner">

<div class="item active">

<div class="row">
<div class="col-md-3 col-sm-6 col-xs-6 img-
gallery-w3l">
<a href="images/g1.jpg" class="thumbnail
cm-overlay">
<img src="images/g1.jpg" class="img-
responsive" alt="Image" style="max-width:100%;">
</a>
</div>
<div class="col-md-3 col-sm-6 col-xs-6 img-
gallery-w3l">
<a href="images/g2.jpg" class="thumbnail
cm-overlay">
<img src="images/g2.jpg" class="img-
responsive" alt="Image" style="max-width:100%;">
</a>
</div>
<div class="col-md-3 col-sm-6 col-xs-6 img-
gallery-w3l">
<a href="images/g3.jpg" class="thumbnail
cm-overlay">
<img src="images/g3.jpg" class="img-
responsive" alt="Image" style="max-width:100%;">
</a>
</div>
 <div class="col-md-3 col-sm-6 col-xs-6 img-
gallery-w3l">
<a href="images/g4.jpg" class="thumbnail
cm-overlay">
<img src="images/g4.jpg" class="img-
responsive" alt="Image" style="max-width:100%;">
</a>
</div>
</div>
<! --.row-->
</div>
<! --. item-->

<div class="item">
<div class="row">
<div class="col-md-3 col-sm-6 col-xs-6 img-
gallery-w3l">
<a href="images/g5.jpg" class="thumbnail
cm-overlay">
<img src="images/g5.jpg" class="img-
responsive" alt="Image" style="max-width:100%;">
</a>
</div>
<div class="col-md-3 col-sm-6 col-xs-6 img-
gallery-w3l">
<a href="images/g6.jpg" class="thumbnail
cm-overlay">
<img src="images/g6.jpg" class="img-
responsive" alt="Image" style="max-width:100%;">
 </a>
</div>
<div class="col-md-3 col-sm-6 col-xs-6 img-
gallery-w3l">
<a href="images/g7.jpg" class="thumbnail
cm-overlay">
<img src="images/g7.jpg" class="img-
responsive" alt="Image" style="max-width:100%;">
</a>
</div>
<div class="col-md-3 col-sm-6 col-xs-6 img-
gallery-w3l">
<a href="images/g1.jpg" class="thumbnail
cm-overlay">
<img src="images/g1.jpg" class="img-
responsive" alt="Image" style="max-width:100%;">
</a>
</div>
</div>
<! --.row-->
</div>
<! --.item-->
<div class="item">
<div class="row">
<div class="col-md-3 col-sm-6 col-xs-6 img-
gallery-w3l">
<a href="images/g2.jpg" class="thumbnail
cm-overlay">
 <img src="images/g2.jpg" class="img-
responsive" alt="Image" style="max-width:100%;">
</a>
</div>
<div class="col-md-3 col-sm-6 col-xs-6 img-
gallery-w3l">
<a href="images/g3.jpg" class="thumbnail
cm-overlay">
<img src="images/g3.jpg" class="img-
responsive" alt="Image" style="max-width:100%;">
</a>
</div>
<div class="col-md-3 col-sm-6 col-xs-6 img-
gallery-w3l">
<a href="images/g4.jpg" class="thumbnail
cm-overlay">
<img src="images/g4.jpg" class="img-
responsive" alt="Image" style="max-width:100%;">
</a>
</div>
<div class="col-md-3 col-sm-6 col-xs-6 img-
gallery-w3l">
<a href="images/g5.jpg" class="thumbnail
cm-overlay">
<img src="images/g5.jpg" class="img-
responsive" alt="Image" style="max-width:100%;">
</a>
</div>
</div>
 <!--.row-->
</div>
<!--.item-->

</div>
<!--.carousel-inner-->
<a data-slide="prev" href="#Carousel" class="left
carousel-control">‹</a>
<a data-slide="next" href="#Carousel" class="right
carousel-control">›</a>
</div>
<!--.Carousel-->

</div>
</div>
</div>

</div>
<!-- //gallery -->

<!-- contact -->

<div class="contact" id="contact">
<div class="container">
<div class="agile-contact-grids">
<h3>Laundry Price(Per Unit)</h3>
<div class="col-md-12 agile-contact-left">
<div class="agileits-map">

</div>
 <div class="map-grid">

<?php
$ret=mysqli_query($con,"select * from tblpricelist");
$cnt=1;
while ($row=mysqli_fetch_array($ret)) {

?>

<table border="1" class="table table-bordered mg-b-0">

<tr>
<th>Top Wear Laundry Price</th>
<td><?php echo $row['TopWear'];?></td>
</tr>

<tr>
<th>Bootom Wear Laundry Price</th>
<td><?php echo $row['BottomWear'];?></td>
</tr>

<tr>
<th>Woolen Cloth Laundry Price</th>
<td><?php echo $row['Woolen'];?></td>
</tr>

</table>

<?php } ?>
 </div>
</div>
</div>

<div class="clearfix"> </div>

</div>
</div>
</div>
<! -- //contact -->

</div>
<! -- //footer -->
<div class="copyright">
<div class="container">
<p>Laundry Management System</p>
</div>
</div>

<script src="js/jquery.min.js"></script>
<script src="js/jquery.easing.min.js"></script>
<script src="js/move-top.js"></script>
<script src="js/bootstrap.min.js"></script>
<script src="js/grayscale.js"></script>
<script src="js/SmoothScroll.min.js"></script>
<! -- flexSlider -->
<script src="js/owl.carousel.js"></script>
<script>
$(document).ready(function() {
$("#owl-demo").owlCarousel({
 items :2,
itemsDesktop : [800,2],
itemsDesktopSmall : [414,1],
lazyLoad : true,
autoPlay : true,
navigation :true,

navigationText : false,
pagination : true,

});

});
</script>

<! -- //flexSlider -->

<! -- /gallery -->
<script src="js/jquery.tools.min.js"></script>
<script src="js/jquery.mobile.custom.min.js"></script>
<script src="js/jquery.cm-overlay.js"></script>

<script>
$(document).ready(function () {
$('.cm-overlay').cmOverlay();
});
</script>
<! -- //gallery -->

<! -- Move-to-top-->
<script type="text/javascript">
$(document).ready(function() {
var defaults = {
containerID: 'toTop', // fading element id
containerHoverID: 'toTopHover', // fading element hover id
scrollSpeed: 1200,
easingType: 'linear'
};
$().UItoTop({ easingType: 'easeOutQuart' });
});
</script>
<! --/Move-to-top-->

</body>
</html>
 CHAPTER 7
SYSTEM TESTING

Software testing is a critical element of software quality assurance and represents the
ultimate review of specification, design and coding. In fact, testing is the one step in
the software engineering process that could be viewed as destructive rather than
constructive.
A strategy for software testing integrates software test case design methods into a well
planned series of steps that result in the successful construction of software. Testing is
the set of activities that can be planned in advance and conducted systematically. The
underlying motivation of program testing is to affirm software quality with methods
that can economically and effectively apply to both strategic to both large and small-
scale systems.

STRATEGIC APPROACH TO SOFTWARE TESTING

The software engineering process can be viewed as a spiral. Initially system engineering
defines the role of software and leads to software requirement analysis where the
information domain, functions, behavior, performance, constraints and validation criteria
for software are established. Moving inward along the spiral, we come to design and
finally to coding. To develop computer software, we spiral in along streamlines that
decrease the level of abstraction on each turn.

A strategy for software testing may also be viewed in the context of the spiral. Unit testing
begins at the vertex of the spiral and concentrates on each unit of the software as
implemented in source code. Testing progress by moving outward along the spiral to
integration testing, where the focus is on the design and the construction of software
architecture. Talking another turn on outward on the spiral we encounter validation
testing where requirements established as part of software requirements analysis are
validated against the software that has been constructed. Finally, we arrive at system
testing, where the software and other System elements are tested as a whole.
7.1 Unit Testing

Unit testing focuses verification effort on the smallest unit Of software design, the
module. The unit testing we have is white box oriented and some modules the steps
are conducted in parallel.

• WHITE BOX TESTING

This type of testing ensures that

✓ All independent paths have been exercised at least once.

✓ All logical decisions have been exercised on their true and false sides.
✓ All loops are executed at their boundaries and within their operational
bounds.
✓ All internal data structures have been exercised to assure their validity.

To follow the concept of white box testing we have tested each form .we have
created independently to verify that Data flow is correct, All conditions are
exercised to check their validity, All loops are executed on their boundaries .

• CONDITIONAL TESTING

In this part of the testing each of the conditions were tested to both true and false
aspects. And all the resulting paths were tested. So that each path that may be
generate on particular condition is traced to uncover any possible errors .

• DATA FLOW TESTING

This type of testing selects the path of the program according to the location of
definition and use of variables. This kind of testing was used only when some local
variable were declared. The definition-use chain method was used in this type of
testing. These were particularly useful in nested statements.
 • LOOP TESTING

In this type of testing all the loops are tested to all the limits possible. The following
exercise was adopted for all loops:

✓ All the loops were tested at their limits, just above them and just below them.
✓ All the loops were skipped at least once.
✓ For nested loops test the inner most loop first and then work outwards.
✓ For concatenated loops the values of dependent loops were set with the help
of connected loop.
✓ Unstructured loops were resolved into nested loops or concatenated loops
and tested as above.

7.3 TEST PLAN

A Software Test Plan is a document describing the testing scope and activities. It is
the basis for formally testing any software/product in a project, Test Plans are
Comprehensive evaluation of programs, and procedures.

Test Plans: Plans for each level of testing.

✓ Black Box Testing

✓ Program Testing/ Unit Testing
✓ System Testing
✓ Parallel Testing

• Black Box Testing:

In this testing functional design of the system will be checked, without regard to the
internal program structure.
• Unit Testing:
In the testing individual programs are checked to extend of desired output i.e.
program specifications. While checking boundary conditions, exceptional
Handling, error Handling etc.

• Integration Testing:
It is the process of combining multiple components together. To ensure that the
software units or components operate properly when combined together.

• System Testing:
These are used to test all programs, which together constitute the system-the
system testing is conducted using synthetic data both valid and invalid transaction
are used in this test.

The step used in the system testing is:

✓ Decompose and analyse the requirement specification.

✓ Partition the requirements into logical categories and for each component
make a list of the detailed requirements.
DESIGN IMPLEMENTATION AND RESULTS

Design implementation refers to the real live running of the designed program. This
section consists of the program modules, showing what they do, and how the system
can be deployed.

Home Page
 Admin Panel

Login Page

Forgot Password
Reset Password

Dashboard
Profile

Change Password
Registered Users

Update Users Details

New Laundry Request

View New Laundry Request

Accepted Laundry Request

View Details of Accepted Laundry Request

In-process Laundry Request

View In-process Laundry Request

Finish Laundry Request

View Details of Finish Laundry Request

Manage Laundry Price

Update Laundry Price

Between Dates Report

View All between Dates Report

Request Count Report

View Request Count Report

 User Panel

Registration Page

Login Page
Dashboard

User Profile
Change Password

Laundry Request
Payment Page

New Request
View New Request Details

Accepted Laundry Request

In-process Laundry Request

View In-process Laundry Request

Finish Laundry Request

View Details of Finish Laundry Request