Table of Contents

Approval ......................................................................................................................................
...
Declaration .................................................................................................................................
iiiAcknowledgement ...................................................................................................................
...
abstract .......................................................................................................................................
chapter
I.......................................................................................................................................... 11.0
Introduction ...........................................................................................................................
11.1 Background of the
Study ....................................................................................................... 11.2 Statement of the
Problem ...................................................................................................... 11.3 Aim
and Objectives ............................................................................................................... 21.4
Justification of the Study .......................................................................................................
21.5
Scope .....................................................................................................................................
31.5.1 User .................................................................................................................................
31.5.2 Module ............................................................................................................................
31.6 Limitation of the
Study ......................................................................................................... 41.7 Definition of
Terms ............................................................................................................... 41.8 Outlines of
the Project ........................................................................................................... 4Chapter
II ........................................................................................................................................ 62.0
Literature Review ..................................................................................................................
6Chapter
III ..................................................................................................................................... 183.0
System Analysis and Design ...............................................................................................
183.1 Analysis of the Existing
System ......................................................................................... 183.2 Description/Analysis
of the New System............................................................................ 193.3 System
Design ..................................................................................................................... 193.4
Output Design .....................................................................................................................
203.5 Input
Design ........................................................................................................................ 223.6
Database Design ..................................................................................................................
233.7 Entity Relationship
Diagram ............................................................................................... 26Chapter
IV ..................................................................................................................................... 274.0
System Implementation and Documentation ......................................................................
274.1
System Implementation .......................................................................................................
274.2 Changeover
Method ............................................................................................................ 27
1.0 Introduction1.1 Background of the Study
Today’s modernization flow of the world has witnessed tremendous change in
lifestyle of society.
Computerized system in managing laundry has 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 institution 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
information take more time and quite difficult. Laundry management system
(LMS) is new system that replaced the file system which most of laundry shop
used. 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 staffs that rolled onto the Laundry
bu1.0 Introduction1.1 Background of the Study
Today’s modernization flow of the world has witnessed tremendous change in
lifestyle of society.
Computerized system in managing laundry has 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 institution 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
information take more time and quite difficult. Laundry management system
(LMS) is new system that replaced the file system which most of laundry shop
used. 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 staffs that rolled onto the laundry
business.

Solutions Provided:
The use of manual system also creates an additional workload for staff to keep
and obtain the customer and staff information because this information is kept
in a different file.
1. Time Consumption:
Manual systems are time consuming, as the business owner must keep track
of laundry sales on a daily basis, while updating the system manually at the
end of the day.
2. Poor Communication:
A manual laundry system requires employees and managers to write down
each time a service been processed in the Laundry. If one employee forgets to
mention that the last cloths has been brought to the Laundry, a manager
expects there is not cloths brought to the Laundry. Compared with a technical
laundry system, a manual laundry system does not help the communication in
the workplace.
3. Physical Counts:
A manual laundry system does not provide any number, as all numbers from
the Laundry are gained through physical laundry counts. One of the difficulties
of running a manual laundry system is that physical laundry counts must be
performed frequently to control the services in the Laundry. This is time
consuming and can cost the business money, if employees must come in to
help out outside of business hours

Scope
User
The target users for this system are laundry staffs, managers and system
administrator.
Staff
Staff of Laundry has privileges to insert, view, update and delete customer
records. Beside managing service and launder details, staff also has a privilege
to calculate payment foreach transaction made.

Manager
Owner or manager of laundry shop or company is a person who has privileges
to view staff information and update their information.

Administrator
Administrator is a person who has responsibility to maintain the system.
Administrator has all privileges to this system and may grant the privileges to
another system User.

Limitation of the Study

Time factor was the greatest barrier to the successful completion of this
exercise since it had to be done within the semester. I also had financial
constraints since all the activities involved were self-sponsored

Software Requirements Specification (SRS) Document

Online Laundry System

Introduction

The Online Laundry System is a web-based application designed to facilitate the

management of laundry services online. This system allows customers to schedule
laundry pickup and delivery services, select the type of laundry service, and make
payments through a secure online portal.

Scope

The Online Laundry System is intended to provide a convenient and efficient solution
for laundry services. The system provides a web-based platform for customers to
schedule laundry services and make payments online. The system will also provide an
administrative panel for managing orders, laundry processing, and delivery services.

Functional Requirements

3.1 User Management The system shall provide the following user roles:

Customers

Administrators

3.2 Customer Functionality The system shall provide the following functionality for
customers:

Register and create an account

Login to the system

Schedule laundry pickup and delivery services

Select the type of laundry service

Track the status of laundry orders

Make online payments

View order history

Cancel or reschedule orders

Leave feedback and ratings for laundry services

3.3 Administrator Functionality The system shall provide the following functionality
for administrators:

Login to the system

Manage customer accounts

Manage laundry orders

View laundry processing status

Assign orders to laundry processing staff

Manage delivery services

Generate reports on laundry services and finances

3.4 Laundry Processing The system shall provide the following functionality for
laundry processing staff:

View assigned orders

Update the status of laundry processing

Update the status of delivery services

Non-functional Requirements

4.1 Performance The system shall be able to handle a large number of simultaneous
user requests without any significant performance issues.

4.2 Security The system shall ensure the security and confidentiality of user data by
implementing appropriate security measures, including:

Password encryption

Secure communication protocols

Access controls

Data backup and recovery mechanisms

4.3 Reliability The system shall be highly reliable and available at all times, with a
minimum downtime of 99%.

Assumptions and Constraints

5.1 Assumptions

Users have access to a computer or mobile device with an internet connection

Users have a valid email address to register and receive notifications from the system

Users have a valid payment method to make online payments

5.2 Constraints
The system is constrained by the availability of internet connectivity and server
resources

The system is dependent on the availability and reliability of third-party payment

gateways for processing online payments

System Architecture

The Online Laundry System shall be a web-based application that utilizes a client-
server architecture. The system shall be hosted on a cloud-based server and shall use
a secure connection protocol (HTTPS) for communication between the client and
server.

Glossary

Online Laundry System: A web-based application designed to facilitate the

management of laundry services online

Customer: A user of the system who schedules laundry pickup and delivery services,
selects the type of laundry service, and makes payments through a secure online
portal

Administrator: A user of the system who manages customer accounts, laundry orders,
and delivery services

Laundry Processing: The process of cleaning, drying, and folding laundry

Payment Gateway: A third-party service that facilitates online payments

8. Payment Gateway: A third-party service that facilitates online payments Use Cases

The use cases section will provide detailed descriptions of the scenarios that the system should
support. The following use cases should be included:

 Register Account: The customer can register a new account with the system by providing
personal details such as name, email address, and phone number.
 Login: The customer and administrator can log in to the system by providing a valid email
address and password.
 Schedule Pickup: The customer can schedule a pickup time and date for laundry services,
including selecting the type of laundry service required.
 Payment: The customer can make online payments for laundry services through the
system's secure payment gateway.
 Order Management: The administrator can manage and track laundry orders, including
assigning orders to laundry processing staff, updating the order status, and generating
reports on orders.
 Laundry Processing: The laundry processing staff can update the status of laundry orders,
including cleaning, drying, and folding.
 9. User Interface

The user interface section will provide a detailed description of the system's user interface. This
section should include mockups or wireframes of the screens that the customer and
administrator will interact with.

10. Data Management

The data management section will provide a detailed description of the system's data storage
and retrieval methods. This section should include the following details:

 Data Models: The system should have data models for customers, orders, and laundry
processing staff, including the required attributes and relationships between the models.
 Database: The system should store data in a database that is accessible to the client and
server. The database should support data backup and recovery mechanisms.
 Data Retrieval: The system should retrieve data from the database using appropriate
query methods and should display data in a readable format for the user.
11. System Integration

The system integration section will provide a detailed description of the system's integration with
third-party services, such as payment gateways. This section should include the following details:

 Payment Gateway: The system should integrate with a third-party payment gateway to
process online payments. The payment gateway should support secure communication
protocols and be reliable and available at all times.
 Email Notification: The system should send email notifications to customers and
administrators for account registration, order confirmation, and order status updates.
12. Technical Requirements

The technical requirements section will provide a detailed description of the system's technical
requirements, including hardware, software, and network requirements. This section should
include the following details:

 Server: The system should be hosted on a cloud-based server with sufficient resources to
handle a large number of simultaneous user requests.
 Programming Language: The system should be developed using a programming
language that supports web development, such as Python, Ruby, or JavaScript.
 Framework: The system should use a web development framework that provides the
necessary tools and libraries for web development, such as Django, Ruby on Rails, or
Express.js.
 Browser Compatibility: The system should be compatible with modern web browsers,
including Google Chrome, Mozilla Firefox, and Microsoft Edge.
13. Conclusion

The Online Laundry System SRS document provides a detailed description of the system's
requirements, including functional and non-functional requirements, use cases, user interface,
data management, system integration, and technical requirements. This document serves as a
guide for developers to build the system and ensures that the system meets the user's needs and
requirements.