Laundry ERP

1
Laundry ERP

2
Laundry ERP

Index
Chap. Chapter Topic Page No.
No
1 INTRODUCTION

1.1 Company Profile/ Institute Profile 8

1.2 Abstract 10
1.3 Existing System and Need for System 11
1.4 Scope of System 13
1.5 Operating Environment- Hardware and Software 14
1.6 Brief Description of Technology Used 15

2 PROPOSED SYSTEM

2.1 Study of Similar Systems (Literature Survey) 22

2.2 Feasibility Study 25
2.3 Objectives of Proposed System 26
2.5 User Requirements 27

3 ANALYSIS & DESIGN

System Requirements (Functional and Non- 29

3.1
Functional Survey)
3.2 Data Flow Diagrams (DFD) 37
3.3 Entity Relationship Diagram (ERD) 39
3.4 Table Structure 40
3.5 Use Case Diagrams 48
3.6 Class Diagram 49
3.7 Activity Diagram 50
3.8 Sequence Diagram 52
3.9 Deployment Diagram 53
3.11 User Interface Designs 54
Report 57
3.12

3
Laundry ERP

4 CODING

4.1 Algorithms 66

4.2 Code Snippet (Sample Code) 67

5 TESTING

5.1 Test Strategy 75

5.2 Test Case / Test Script 77

5.3 Defect Report / Test Log 79

6 LIMITATIONS OF PROPOSED SYSTEM 81

7 PROPOSED ENHANCEMENTS 84

8 CONCLUSION 86

9 BIBLIOGRAPHY 89

4
Laundry ERP

CHAPTER 1
INTRODUCTION

5
Laundry ERP

1.1 Abstract

In today's fast-paced laundry ERP system face numerous challenges in managing their day-to-
day operations. Manual processes and disparate systems can lead to inefficiencies and errors, which
canhinder the overall productivity and effectiveness of the laundry system. The laundry management
system seeks to address these challenges by integrating key functionalities into single, cohesive
platform. The laundry management system is a sophisticated software solution designed to streamline
and automate various administrative, academic, and operational processes within laundry system.

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 to 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,
customer’s information is secured, as a specific id is allocated per registration to avoid contrasting
information.

The system ensures comprehensive management of customer information, maintaining

detailed profiles that include personal details, billing records, schedule, and other relevant data. This
information is easily accessible to authorized personnel for administrative, fostering better decision-
making and personalized support for customer.

6
Laundry ERP

1.2 Existing System and Need for System

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 (on forms) 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 led 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.

In the existing system the whole work is done manually. All the information is recorded in register and
MS Excel application. All student entries and customer records process is very time consuming and
errorprone. It needs lots of paper work. When any customer related data needed it is required to search
in the records. Several functions like generate the results for details were given manually.

In the present system, the authority is required to collect the information about the customer
throughmanually communication.

Limitations of existing system:

• Problem in keeping the data of various departments together.

• In the existing system all the information is recorded into registers. Register entries and record
process is very time consuming and error possibilities.
• Several functions like generate exam time table were given manually.
• Problem in keeping data of customer’s & number of staff increases.
• Report generation is very slow.

7
Laundry ERP

Need for System

Hence computerization of the existing system is proposed. The new system must
completely remove all manual burdens and provides efficient on the entry system. The existing
system is fully manual and requires the computerized system because of following reason:-

The main motive of new system is to maintain details of customer and maintain records easily

Followings are the drawback of existing system:

• Manual system is Time-consuming.

• Manual system is more prone to errors as compared to computerized system.
• Manual system is not user friendly and not secured.
• Handling manual system is tedious job.
• File management is needed in manual system.
• In manual system, it is not possible to keep back-up for each and every transaction.
Itis created for study only.

8
Laundry ERP

1.3 Scope of System

• Easy to maintain Data.

• Easy to generate report.

• Admin feels Secure to maintain customer data.

• Admin generate order wise data.

• Admin generate mobile number wise data.

• Registration of customer, select cloth type and service type as per customer requirements.

• If customer information is already register then we can search that customer by their mobile

number also.

• Admin generates bill records more securely.

• Admin can set his charges as per cloths type and service.

9
Laundry ERP

1.4 Operating Environment- Hardware and Software

HARDWARE REQUIREMENTS (MINIMUM):-

• RAM Capacity : 128MB
• Pentium processor : 233 MHZ
• Hard Disk : 20GB
• CD-ROM Drive : 32 HZ
• Keyboard : 108 Standard
• Mouse : Optical
• Monitor : 15’’ Color Monitor

SOFTWARE REQUIREMENTS:-
• Web Presentation : HTML,CSS
• Client – side Scripting : JavaScript
• Programming Language : Java
• Web based Technologies : Servlets, jsp
• database Connectivity : JDBC
• Java Version : JDK1.6
• Backend Database : Oracle 10g
• Operating System : Windows
• Web Server : Tomcat 6.0
• Browser : IE/Mozilla

10
Laundry ERP

1.5 Brief Description of Technology Used

Introduction: (Java)

Java is a high-level, third generation programming language, like C, FORTRAN, Smalltalk, Perl,
and many others. You can use Java to write computer applications that play games, store data or do any
of the thousands of other things computer software can do. Compared to other programming languages,
Java is most similar to C. However, although Java shares much of C's syntax, it is not C. Knowing how
toprogram in C or, better yet, C++, will certainly help you to learn Java more quickly, but you don't
need to know C to learn Java. A Java compiler won't compile C code, and most large C programs need
to be changed substantially before they can become Java programs. What's most special about Java in
relation to other programming languages is that it lets you write special programs called applets that can
be downloaded from the Internet and played safely within a web browser. Java language is called as an
Object-Oriented Programming language and before beginning for Java, we have to learn the concept of
OOPs (Object-Oriented Programming).

Basic Concept of OOP (Object-Oriented Programming):

There are some basic concepts of object-oriented programming as follows:

1. Object
2. Class
3. Data abstraction
4. Data encapsulation
5. Inheritance
6. Polymorphism
7. Dynamic binding

1. Object

Objects are important runtime entities in object oriented method. They may characterize a location, a
bank account, and a table of data or any entry that the program must handle.

2. Classes

11
Laundry ERP

A class is a set of objects with similar properties (attributes), common behaviour (operations), and
common link to other objects. The complete set of data and code of an object can be made a user defined
data type with the help of class. The objects are variable of type class. A class is a collection of objects of
similar type. Classes are user defined data types and work like the build in type of the programming
language. Once the class has been defined, we can make any number of objects belonging to that class.
Each object is related with the data of type class with which they are formed.

3. Data Abstraction

Data abstraction refers to the act of representing important description without including the
background details or explanations.

Classes use the concept of abstraction and are defined as a list of abstract attributes such as size, cost
and functions operate on these attributes. They summarize all the important properties of the objects that
are to be created. Classes use the concepts of data abstraction and it is called as Abstract Data Type
(ADT).

4. Data Encapsulation

Data Encapsulation means wrapping of data and functions into a single unit (i.e. class). It is most
useful feature of class. The data is not easy to get to the outside world and only those functions which are
enclosed in the class can access it.

These functions provide the boundary between Object‘s data and program. This insulation of data
from direct access by the program is called as Data hiding.

5. Inheritance

Inheritance is the process by which objects of one class can get the properties of objects of another
class. Inheritance means one class of objects inherits the data and behaviours from another class.
Inheritance maintains the hierarchical classification in which a class inherits from its parents.

Inheritance provides the important feature of OOP that is reusability. That means we can include
additional characteristics to an existing class without modification. This is possible deriving a new class
from existing one.

In other words, it is property of object-oriented systems that allow objects to be built from other
objects. Inheritance allows openly taking help of the commonality of objects when constructing new

12
Laundry ERP

classes. Inheritance is a relationship between classes where one class is the parent class of another
(derived) class. The derived class holds the properties and behaviour of base class in addition to the
properties and behaviour of derived class.

6. Polymorphism

(Poly means ―many‖ and morph means ―form‖). Polymorphism means the ability to take more than
one form. Polymorphism plays a main role in allocate objects having different internal structures to share
the same external interface. This means that a general class of operations may be accessed in the same
manner even though specific activities associated with each operation may differ. Polymorphism is
broadly used in implementing inheritance.

It means objects that can take on or assume many different forms. Polymorphism means that the
same operations may behave differently on different classes. Booch defines polymorphism as the
relationship of objects many different classes by some common super class. Polymorphism allows us to
write generic, reusable code more easily, because we can specify general instructions and delegate the
implementation detail to the objects involved.

7. Dynamic Binding

Binding refers to the linking of a procedure call to the code to be executed in response to the call.
Dynamic binding means that the code related with a given procedure call is not known until the time of
the call at run time.

Java (Hibernate)

Hibernate ORM (Hibernate in short) is an object-relational mapping library for the Java
language, providing a framework for mapping an object-oriented domain model to a traditional relational
database. Hibernate solves object-relational impedance

mismatch problems by replacing direct persistence-related database accesses with high-level object
handling functions. Hibernate is a free software that is distributed under the GNU Lesser General Public
License.

Hibernates primary feature is mapping from Java classes to database tables (and from Java data
types to SQL data types). Hibernate also provides data query and retrieval facilities. It generates SQL

13
Laundry ERP

calls and relieves the developer from manual result set handling and object conversion. Applications
using Hibernate are portable to supported SQL databases with little performance overhead

Mapping

Mapping Java classes to database tables is accomplished through the configuration of an XML
file or by using Java Annotations. When using an XML file, Hibernate can generate skeleton source code
for the persistence classes. This is unnecessary when annotations are used. Hibernate can use the XML
file or the annotations to maintain the database schema.

Facilities to arrange one-to-many and many-to-many relationships between classes are provided.
In addition to managing associations between objects, Hibernate can also manage reflexive associations
where an object has a one-to-many relationship with other instances of its own type.

Hibernate supports the mapping of custom value types. This makes the following scenarios
possible:
• Overriding the default SQL type that Hibernate chooses when mapping a column to a property.
• Mapping Java Enum to columns as if they were regular properties.
• Mapping a single property to multiple columns.

Definition: Objects in a front-end application follow OOP principles, while objects in the back-end
follow database normalization principles, resulting in different representation requirements. This
problem is called "object-relational impedance mismatch". Mapping is a way of resolving the impedance
mismatch problem.
Mapping tells the ORM tool which java class object to store in which database table

Hibernate Query language (HQL)

Hibernate provides an SQL inspired language called Hibernate Query Language (HQL) which
allows SQL-like queries to be written against Hibernates data objects. Criteria Queries are provided as an
object-oriented alternative to HQL. Criteria Query is used to modify the objects and provide the restriction
for the objects.

Persistence
14
Laundry ERP

Hibernate provides transparent persistence for Plain Old Java Objects (POJOs). The only strict
requirement for a persistent class is a no-argument constructor, not necessarily public. Proper behavior in
some applications also requires special attention to the equals() and hashCode() methods.[2]
Collections of data objects are typically stored in Java collection objects such as Set and List. Java
generics, introduced in Java 5, are supported. Hibernate can be configured to lazy load associated
collections. Lazy loading is the default as of Hibernate 3.
Related objects can be configured to cascade operations from one to the other. For example, a
parent Album object can be configured to cascade its save and/or delete operation to its child Track objects.
This can reduce development time and ensure referential integrity. A dirty checking feature avoids
unnecessary database write actions by performing SQL updates only on the modified fields of persistent
objects.

Integration
Hibernate can be used both in standalone Java applications and in Java EE applications using
servlets, EJB session beans, and JBI service components. It can also be included as a feature in other
programming languages. For example, Adobe integrated Hibernate into version 9 of ColdFusion (which
runs on J2EE app servers) with an abstraction layer of new functions and syntax added into CFML

Entities And Components

In Hibernate jargon, an entity is a stand-alone object in Hibernate's persistent mechanism which
can be manipulated independently of other objects. In contrast, a component is subordinate to an entity and
can be manipulated only with respect to that entity. For example, an Album object may represent an entity
but the Tracks object associated with the Album objects would represent a component of the
Album entity if it is assumed that Tracks can only be saved or retrieved from the database through the
Album object. Unlike J2EE, it can switch databases.

What Struts is?

According to the Struts main page: Apache Struts is a free open-source framework for creating Java
web applications.
According to Wikipedia: Apache Struts is an open-source framework for developing Java EE
web applications. It uses and extends the Java Servlet API to encourage developers to adopt a model- view-
controller (MVC) architecture.

15
Laundry ERP

Struts has 4 Main Components

1. The Struts Framework: java classes that provide the Action Servlet and Action classes as part of the
MVC Controller, the Action Form class to facilitate moving data to and from the View, and the Action
Forward class to aid the controller in forwarding requests.
2. JSP Tag Libraries: Tags expand on HTML forms and fields, help you work with beans and provide
other useful features.
3. Tiles Plugin: Allows you to create HTML inner-usable pieces (tiles) that can be put together to make
a whole page
4. Validator Plugin: Allows you specify validation information in an xml file and then perform those
validations in the browser and/or the on the server.

MySQL
For a more general introduction see the SQL Workbook. Structured Query Language is a third
generation language for working with relational databases. Being a 3G language it is closer to human
language than machine language and therefore easier to understand and work with.
• Dr. E. F. Ted Codd who worked for IBM described a relational model for database in 1970.
• In 1992, ANSI (American National Standards Institute), the apex body, standardized most of
the basic syntax.
• Its called SQL 92 and most databases (like Oracle, MySQL, Sybase, etc.) implement a subset of
the standard (and proprietary extensions that makes them often incompatible).

Java Script
JavaScript is a Client-side scripting language, which empowers the developers to write
functionality to run at the users client .It is very useful and powerful if the developers want to pre-
process data on the client before submission to the server, this can reduce traffic over the network and
offload processing from the server to the client. Since JavaScript is a Scripting language (not compiled)
and runs primarily on the client. Most JavaScript used today is used to manipulate different aspects of
the browsers. JavaScript uses an object-oriented programming (OOP) approach.
There are four primary components to JavaScript’s OOP methodology:
1. Object: A JavaScript object can be almost any elements of a web documents such as the
documents, tables, forms, buttons, images.

16
Laundry ERP

2. Properties: Each object has its own properties such as the history of the browser. History length
contains the count of the items in the history list.
3. Methods: Objects can do certain things known as methods. Basically a method Is a means of a
making an object do something like open or close.
4. Events: An events an actually triggers the function or method to run.

JavaScript is good to the do the following:

• User input Validation.
• Calculations and simple graphing.
• Mouse over buttons.
• Counters.
• Quick reaction to user actions.
• Opening new windows and sizing them.

17
Laundry ERP

CHAPTER 2
PROPOSED SYSTEM

22
 Exam ERP System
ERP Systems in laundry: A Literature Review

2.1 Study of Similar Systems (Literature Survey)

Title Authors Publication Summary

Year

ERP Systems in Engr. Dr. November 2026 This paper presents a

Laundry: A Oluwagbemiga comprehensive literature
Literature Review Omotayo Shoewu review on the implementation
and use of ERP systems in the
laundry sector. This section
takes critical review of
existing system implemented,
the success factors, challenges
faced, technologies used and

unresolved problems. This

forms the basis for
implementing later versions

Design and Nghia Truong Van July 2018 In this paper, we propose RFID
Laundry Management System
Development of an (LMS), in order to provide low
ERP System for power consumption, high
services, low operation costs and
laundry better monitoring. The proposed
system consists of RFID tag,
wireless RFID hanger and MFC
software.To compare with other
existing RFID system, our
system was developed as a web
application. Therefore, customer
can check their cloth status
through web page or smart-
phone devices. RFID reader was
designed on

22
Exam ERP System

Clothing Management Sung Boo Chung August 2020 In this paper, we proposed the
System Using the clothing management system
Smart Hanger using the smart hanger.
Embedded RFID Proposed system consists of
smart hanger, base module,
and server, and the smart
hanger consists of MCU, LED,
RFID reader, RF chip, ring
sensor, and battery. The smart
hanger reads the RFID tag
attached to the clothes and
wirelessly transmitted to the
server. The server associated
base module communicates
with the smart hanger and
transmits information to the
server.

23
Exam ERP System

2.2 Feasibility Study

At OmVsab, the feasibility analysis is designed to determine whether or not, given
the project environment, the proposed project will be successful. It is useful to evaluate the
cost and the benefit of the requested system. Feasibility study tries to anticipate future
scenarios of software development. In feasibility study proposed system was reviewed and
evaluated to determine the usability and feasibility of the system.

The proposed system was reviewed considering three feasibility tests:

The Key Considerations in feasibility Analysis: -

• Economic feasibility
• Technical feasibility
• Operational feasibility

Economic feasibility: -
The proposed system is economically feasible because the cost involve in purchasing
the hardware and software are within approachable personal cost like salaries of employee
hired are also nominal. The operating environment costs are marginal. The less time involve
also helped in its economic feasible.

Technical feasibility: -

It is possible with current technical support and hardware development in the

organization to fulfill defines objectives and proposed activities. It is always desirable to
select the best package that will be easy to implement for the system design and must be a
flexible as possible with other programmers and outside developer as interactive as possible
to use. The technical requirement regarding hardware and software should not be very high.

Operational feasibility:

This system is very user friendly and very easy to use. The application does not have
complex menus and not having complex operations. All the work is going verysmoothly,
all the facilities are having very good user interface so that’s why there is noany difficulty
while doing work on the system.

25
Exam ERP System

2.3 Objectives of Proposed System

The objective of laundry Result ERP is to provide an efficient and integrated software solution that
streamlines various administrative processes within a data. The system aims to enhance productivity,
improve communication, and facilitate data management for different including customer, admin,
staff. Some specific objectives of laundry ERP may include:
1. Reduce the manual work.
2. Reduces the total time required.
3. Provides accuracy.
4. User friendly.
5. Data is secure.
6. System should not be hectic.

Overall, the objective of laundry ERP is to automate administrative tasks, improve operational
efficiency, enhance communication, and provide a comprehensive and reliable platform for managing
various aspects of college operations.

26
Exam ERP System

2.4 User Requirements

• The laundry ERP system offers a range of user-oriented features to enhance the management
of customer records while saving both time and cost.
• The Laundry ERP system ensures faster access to data, enabling users to retrieve
informationswiftly and conveniently.
• It focuses on increasing efficiency; the laundry ERP system optimizes various operations related
to examinations.
• The ability to generate reports quickly is another valuable aspect of the laundry ERP system.
• The Laundry ERP system offers an easy-to-use interface, ensuring user-friendliness
andaccessibility.

• To provide centralized database support for the user to access project related
information.

• User need to insert information of customer carefully and correctly.

• Generate bill receipt of customer as per their orders.

• Set rate by cloths and service type.

27
Exam ERP System

CHAPTER 3
ANALYSIS & DESIGN

28
 Exam ERP System

3.1 System Requirements (Functional and Non-Functional Survey)

3.1.1 Admin Use Case

Use Case: Register New Customer

Brief Description: Admin can create a new user which may be admin or normal user also.

Initial Step-By-Step Description:

Before this use case can be initiated, the Admin has already connected to the laundry ERP system as
anadmin user.
1. Click on Register New User tab
2. Enter required details.
3. Click on Save button.
4. The system verifies the new user information and show the pop-up of Saved Successfully.

3.1.2 User use Case

Test Test Case Form Pre- Input Expected Observed Pass

Case Name Name requisite Data Results Result /Fail
Id
1 Email Login Open abc Prompt message Pass
Validation Page Website message box
box showing
showing message
message “Please
“Please Enter
Enter Valid
Valid Email
Email Address”
Address” appeared

29
 Exam ERP System
2 Email Login Open 123 Prompt message Pass
Validation Page Website message box
box showing
showing message
message “Please
“Please Enter
Enter Valid
Valid Email
Email
Address”

3 Password Login Open xyzpq Password Password Pass

Validation Page Website r show in * shown
as ******

4 Password Login Open xyzpq Password Password Fail

Validation Page Website r show in * shown
as xyzpq
r

Barcode Cloths Open If(yes) Barcode Barcode Pass

5 Status page Cloths No. No.
Mandator Page must be became
y Field Mandatory Mandatory

6 Barcode Cloths Open ghdfrfhdgdf Barcode Barcode Pass

Validation page Cloths No should No not
Page not Generate
generate

7 Barcode Cloths Open 11313221 Barcode Barcode Pass

Validation page Cloths No should No
Page generate Generate

30
Exam ERP System

8 Cloths Cloths Open cloth Prompt Prompt Pass

stock Page Website message message
Mandator box box
y field showing showing
message message
“Please “Please
Enter Enter Valid
Valid Stock”
Stock”

9 Cloths Cloths Open 1000 Details should Stock 1000 Pass

stock Page Website save in Cloths saved
Mandator database
y field

10 Cloths Cloths Open Xyzpq Prompt Prompt Pass

barode Page Website R message message
sticker box box
generator showing showing
message message
“Please “Please
Enter Enter Valid
Valid Sticker
Sticker number” number”

11 Cloths Cloths Open 20 Description Description Pass

barode Page Website , Quantity , Quantity
sticker & & Amount
generator Amount will be
will be Display
Display related to
related to the Cloths
the Cloths

31
Exam ERP System
12 Barcode Cloths Open If(yes) Barcode Barcode Pass
Status page Cloths No.must be No.
Mandator Page Mandatory became
y Field Mandatory

13 Cloths Cloths Open Select Description Description Pass

Validatio page Cloths Item , Quantity ,
n Page From & Stock Quantity
the will be &stock
Item Display Amount
List. related to Displayed
the Cloths related to
the
Cloths

14 Sale order Order Open Select Description Description Pass

validation page Order Order ,Quantity,stock & ,Quantity,st
page Cloths Amount will be ock
From the Display & Amount
Cloths list related to the will be
List. Cloths Display
related to
the Cloths

15 Check for Order Open 12/07/20 Prompt message Prompt Pass

order date Page Order 021 box showing message
page message “Please box
Enter Valid order showing
Date” message
“Please
Enter Valid
order
Date”

16 Check for Order Open 2023/04/ Order details Order Pass

order date Page Order 22 should show details
page should
show

32
Exam ERP System
17 Check for Order Open 100020 Prompt message Prompt Pass
order Page Order box showing message
Cloths page message “Please box
quantity Enter Valid showing
Quantity message
number” “Please
Enter Valid
Quantity
number”

18 Check for Order Open 20 Description Description Pass

order Page Order , Quantity & , Quantity &
Cloths page Amount will be Amount will
quantity Display related to be Display
the Cloths related to
the Cloths

19 Check for Invoice Open If(yes) Description and Description Pass

invoice Page Invoice amount and amount
details Page will be Display will be
related to Display
the Cloths related to
the Cloths

20 Check for Tax& Open Jjhkjhjflj Prompt message Prompt Pass

tax and discoun Tax& lh box showing message
discount t page discount message “Please box
page Enter Valid showing
number” message
“Please
Enter Valid
number”

33
 Exam ERP System
Check for Tax& Open 2.1% Description Description Pass
21 tax and discoun Tax& 3.1% About the Total About the
discount t page discount 10% and discount Total and
page discount
Page

22 Check for Order Open Select a Generate the Verify that Pass
generatin g Page Reports report report the report is
reports: Page type (e.g., generated
Reports sales with
Page report, accurate
inventor y data and
report) formatting

23 Check for Order Open Scan a Verify that the Verify that Pass
barcode Page Order valid corresponding the
scanning: page barcode Cloths details are correspondi
Barcode of a displayed ng Cloths
Scanner Cloths details are
displayed

Check for Cloths Open Search Confirm the Verify that Pass
24 deleting a Page Cloths for an deletion the Cloths is
Cloths: Page existing successfull
Cloths Cloths y removed
Page Click on from the
the inventory
"Delete"

34
Exam ERP System

Functional Requirements:

Functional requirements are responsible for the behavior of your website and can vary as per the needs
and business industry niche. For e.g. the site development lets the customers choose different item
attributes such as price area etc.; on the other side the travel companies may require a Chat bot for
providing user assistance, luxury goods or jeweler brands come with a zoom option on the product
detail page. Here are the other important functional requirements that you must consider for your
development site

35
Exam ERP System

Non-functional Requirements:

Usability:

The system should have a user-friendly interface, allowing easy navigation and interaction for all
types of users. The system should provide clear instructions and feedback to users.

Performance:

The system should handle multiple concurrent users efficiently. Response times for user
interactions should be reasonable and within acceptable limits.

Security:

The system should ensure secure user authentication and authorization. Personal information and
sensitive data should be encrypted and protected.Access control mechanisms should be in place to ensure
data privacy.

Reliability:

The system should be available and accessible to users without significant downtime. Data
integrity should be maintained, ensuring accurate and reliable information storage.

Scalability:

The system should be designed to accommodate future growth in the number of users and data
volume. It should be scalable to handle increased demands on resources.

Integration:

The system should be able to integrate with existing systems and databases, such as student
information systems or learning management systems, for seamless data exchange.

Documentation and Support:

The system should have comprehensive documentation, including user manuals and technical
guides. Adequate support and maintenance should be provided to address issues and ensure system
availability.

36
Exam ERP System

3.2 Data Flow Diagrams (DFD)

DFD Level 0:

37
Exam ERP System

DFD Level 1:

DFD Level 2:

38
Exam ERP System

3.3 Entity Relationship Diagram (ERD)

39
 Exam ERP System

3.4 Table Structure

1. Cloth Type Model

Sr.No Field DataType Constraint Description

1 cothTypeId Int(11) Primary key AUTO_INCREMENT

2 CothType Varchar(225)

3 fag Int(11)

4 shopid Int(11)

2. Customer Detail Model

Sr.No Field DataType Constraint Description

1 cId INT(11) Primary key AUTO_INCREMENT

2 ShopName VARCHAR(255)

3 cAddress VARCHAR(255)

4 cAmount DOUBLE Foreign Key

5 cMobile VARCHAR(255)

6 cName VARCHAR(255)

7 cStatus VARCHAR(255)

8 cWallet DOUBLE Foreign Key

9 gender VARCHAR(255)

10 shopId INT(11) Foreign Key

40
 Exam ERP System

3. Customer Order Model

Sr.No Field DataType Constraint Description

1 id INT(11) Primary key AUTO_INCREMENT

2 Status VARCHAR(255)

3 amount DOUBLE Foreign Key

4 clothType VARCHAR(255)

5 deleveredDate VARCHAR(255)

6 invoiceNo INT(11)

7 orderDate VARCHAR(255)

8 orderId VARCHAR(255)

9 preferanceType VARCHAR(255)

10 quantity INT(11) Foreign Key

11 rate DOUBLE Foreign Key

12 serviceType VARCHAR(255)

13 shopId INT(11) Foreign Key

14 cId INT(11)

4. Customer Order Model_2

Sr.No Field DataType Constraint Description

1 Id INT(11) Primary key AUTO_INCREMENT

2 Status VARCHAR(255)

3 amount DOUBLE Foreign Key

4 clothType VARCHAR(255)

5 deleveredDate VARCHAR(255)

41
 Exam ERP System
6 invoiceNo INT(11) Foreign Key

7 orderDate VARCHAR(255)

8 orderId VARCHAR(255)

9 preferanceType VARCHAR(255)

10 quantity INT(11) Foreign Key

11 rate DOUBLE Foreign Key

12 serviceType VARCHAR(255)

13 shopId INT(11) Foreign Key

14 cId INT(11)

5. Number Data

Sr.No Field DataType Constraint Description

1 Id INT(11) Primary key

7. Order Details

Sr.No Field DataType Constraint Description

1 oId INT(11) Primary key AUTO_INCREMENT

2 DeliveredQty INT(11) Foreign Key

3 Discription VARCHAR(255)

4 NewBalance DOUBLE Foreign Key

5 NotReadyQty INT(11) Foreign Key

6 PaymentMode VARCHAR(255)

7 ReadyQty INT(11) Foreign Key

8 actualPaid DOUBLE Foreign Key

9 amountPaid DOUBLE Foreign Key

10 amountRemaining DOUBLE Foreign Key

42
 Exam ERP System
11 dueDate VARCHAR(255)

12 flag INT(11) Foreign Key

13 invoiceNo INT(11) Foreign Key

14 oDate VARCHAR(255)

15 oStatus VARCHAR(255)

16 orderDate VARCHAR(255)

17 orderId VARCHAR(255)

18 orderStatus INT(11)

19 shopId INT(11) Foreign Key

20 totalAmount DOUBLE Foreign Key

21 totalQuantity INT(11) Foreign Key

22 cId INT(11)

8. Order Payment Model

Sr.No Field DataType Constraint Description

1 orderPaymentId INT(11) Primary key AUTO_INCREMENT

2 amountPaid DOUBLE Foreign Key

3 amountRemaining DOUBLE Foreign Key

4 nowPaid DOUBLE Foreign Key

5 paymentDate VARCHAR(255)

6 shopId INT(11) Foreign Key

7 totalAmount DOUBLE Foreign Key

8 oId INT(11)

43
 Exam ERP System

9. Order Separate Entry Model

Sr.No Field DataType Constraint Description

1 saparateId INT(11) Primary key AUTO_INCREMENT

2 Status VARCHAR(255)

3 clothType VARCHAR(255)

4 deleveredDate VARCHAR(255)

5 invoiceNo INT(11) Foreign Key

6 orderDate VARCHAR(255)

7 orderId VARCHAR(255)

8 preferanceType VARCHAR(255)

9 serviceType VARCHAR(255)

10 shopId INT(11) Foreign Key

11 cId INT(11)

10. Owner Details Model

Sr.No Field DataType Constraint Description

1 ownerId INT(11) Primary key AUTO_INCREMENT
2 ShopName VARCHAR(255)
3 ownerAddress VARCHAR(255)

4 ownerContact VARCHAR(255)
5 ownerEmail VARCHAR(255)
6 ownerName VARCHAR(255)
7 ownerPassword VARCHAR(255)
8 ownerUserName VARCHAR(255)
9 shopId INT(11)

44
 Exam ERP System

11. Preference Model

Sr.No Field DataType Constraint Description

1 id INT(11) Primary key AUTO_INCREMENT

2 flag INT(11) Foreign Key

3 preferanceName VARCHAR(255)

4 preferancePrice DOUBLE Foreign Key

5 shopId INT(11) Foreign Key

12. Rate Master Model

Sr.No Field DataType Constraint Description

1 rateId INT(11) Primary key AUTO_INCREMENT

2 flag INT(11) Foreign Key

3 rate DOUBLE Foreign Key

4 shopId INT(11) Foreign Key

5 clothTypeID INT(11)

6 serviceTypeID INT(11)

13. Return Order Details

Sr.No Field DataType Constraint Description

1 returnOrderId INT(11) Primary key AUTO_INCREMENT
2 ReturnOrderDate VARCHAR(255)
3 TotalQuantity INT(11) Foreign Key
4 invoiceNo INT(11) Foreign Key
5 orderId VARCHAR(255)
6 totalCompleteQty INT(11) Foreign Key
7 cId INT(11)

45
 Exam ERP System

14. Return Order Entry Model

Sr.No Field DataType Constraint Description

1 entryId INT(11) Primary key AUTO_INCREMENT

2 ClothTypeID VARCHAR(255)

3 CompleteQty INT(11) Foreign Key

4 Quantity INT(11) Foreign Key

5 ServiceTypeID VARCHAR(255)

6 invoiceNo INT(11) Foreign Key

7 orderDate VARCHAR(255)

8 orderId VARCHAR(255)

9 cId INT(11)

15. Service Type Model

Sr.No Field DataType Constraint Description

1 serviceTypeID INT(11) Primary key AUTO_INCREMENT

2 flag INT(11) Foreign Key

3 serviceType VARCHAR(255)

4 serviceTypeName VARCHAR(255)

5 shopId INT(11) Foreign Key

46
 Exam ERP System

16. Shop Details Model

Sr.No Field DataType Constraint Description

1 shopId INT(11) Primary key AUTO_INCREMENT

2 flag INT(11) Foreign Key

3 gstNo VARCHAR(255)

4 shopAddress VARCHAR(255)

5 shopName VARCHAR(255)

47
Exam ERP System

3.5 Use Case Diagrams

48
Exam ERP System

3.6 Class Diagram

49
Exam ERP System

3.7 Activity Diagram

Activity diagram for user

50
Exam ERP System

Activity diagram for Admin

51
Exam ERP System

3.8 Sequence Diagram

52
Exam ERP System

3.9 Deployment Diagram

53
Exam ERP System

3.10 User Interface Designs

Login

Dashboard

54
Exam ERP System

Order Receipt

Customer Details

55
Exam ERP System

Add Cloths

Add Service Master

56
Exam ERP System

Add rate with service

All Orders

57
Exam ERP System

Save ready cloths

Customer Order Details

58
Exam ERP System

Delivered Ready Cloths

Print all barcode

59
Exam ERP System

Specific Order Details

All Paid orders

60
Exam ERP System

Pending Orders

Promotional msg print

61
Exam ERP System

Incomplete Report

Lock Screen

62
Exam ERP System

Forgot recovery password

Forgot password

63
Exam ERP System

Return Cloths by barcode search

Rate Master

64
Exam ERP System

CHAPTER 4
CODING

65
Exam ERP System

4.1 Algorithms

1. Algorithm Admin Module:

Prompt the Admin to enter their username and password. Validate the credentials against the stored
admin details.

If the credentials are valid, proceed to the main menu; otherwise, display an error message.

• Admin Login Module:

Step 1: Start the login process.

Step 2: Prompt the user to enter the admin login credentials (Username and Password)

Step 3: Validate the entered credentials with the stored user database.

Step 4: If credentials are valid:

Grant access to the admin portal

Else:

Display an error message and return to step 2.

• Register New User Module:

Step 1: Login with Admin credentials.

Step 2: Select the New User tab on the page.

Step 3: Enter the required details and click on Save button.

Step 4: If all the details are in valid format:

New user will be added in the DB

Else:

Display an error message and return to step 3.

66
Exam ERP System

4.2 Code Snippet (Sample Code)

Login:

User:

67
Laundry ERP

Home:

Inventory:

68
Laundry ERP

Category:

Admin:

69
 Laundry ERP

Report:

Order:

70
Laundry ERP

Add preferences:

Rate Master:

71
Laundry ERP

Print barcode:

Delivered:

72
Laundry ERP

Service Master:

Add cloths:

73
Laundry ERP

CHAPTER 5
TESTING

74
Laundry ERP

5.1 Test Strategy

• Requirements Analysis: Thoroughly analyse the requirements of the laundry ERP

system to understand the functionality, features, and user expectations. This analysis
will form the basis for designing the test strategy.
• Test Planning: Develop a comprehensive test plan that outlines the testing objectives,
scope, test coverage, and test schedules. Identify the different types of testing
required, such as functional testing, performance testing, security testing, and
usability testing.
• Test Data Preparation: Create a variety of test data that represents different
scenarios and use cases. This includes customer records, bill payment, and other
relevant data. Ensure that the test data covers both normaland boundary conditions.
• Functional Testing: Conduct functional testing to validate the system against the
specified requirements. Test various functionalities such as customer data, report
generation, report generation, and data validation.Verify that the system is
performing as expected and that all features are workingcorrectly.
• Performance Testing: Perform performance testing to assess the system's response
time, scalability, and stability under varying loads. Simulate realistic user scenarios
and stress test the system to identify any bottlenecks or performance issues. Measure
and optimize the system's performance to ensure it can handle the expected user load
during peak times.
• Security Testing: Conduct security testing to identify vulnerabilities and ensure that
the system is protected against unauthorized access, data breaches, and other security
risks. Test authentication mechanisms, access controls, encryption, and data privacy
measures. Perform penetration testing to assess the system's resilience against
potential attacks.
• Usability Testing: Evaluate the user-friendliness and intuitiveness of the laundry
ERP system's interface. Conduct usability tests with representative users to identify

75
Laundry ERP

any usability issues, navigation problems, or inconsistencies. Gather user feedback

andincorporate necessary improvements to enhance the overall user experience.

• Integration Testing: Verify the smooth integration and interoperability of the

laundry ERP system with other existing systems or external services. Test data
exchanges, API integrations, and ensure proper synchronization between different
modules andcomponents.
• Regression Testing: Perform regression testing after each system update or bug fix to
ensure that existing functionalities are not affected by the changes. Re-test previously
executed test cases and verify that all previously identified issues have been resolved
without introducing new defects.
• Documentation and Reporting: Document all test cases, test results, and any defects or
issues encountered during testing. Provide clear and concise reports that summarize
the overall testing progress, test coverage, and any recommendations for
improvement.
• Continuous Improvement: Continuously assess and refine the test strategy based on
feedback, lessons learned, and evolving requirements. Incorporate new testing
techniques, tools, and best practices to enhance the effectiveness and efficiency of the
testing process.

By following this test strategy, you can ensure a comprehensive and systematic approach to
testing the laundry ERP system, ultimately resulting in a reliable and high-quality software
product.

76
Laundry ERP

5.2 Test Case / Test Script

Test case Test Test Case Test case Steps to Expected Status
Case Description Preconditions execute Result
#

Login TC- Validate 1. Site should 1. lunch the An Pass

001 login be lunched site appropriate
functionality 2.Selct the 2. remain message
with admin admin option the should be
NULL input from drop username displayed
down list and and the user
password should not
blank be allowed
to login.

TC- Validate 1. Site should 1. lunch the User will be PASS

002 login be lunched site able to login
functionality 2.Selct the 2. enter successfully
with Admin admin option correct
Valid from drop username
credentials down list and
password

TC- Validate 1. Site should 1. lunch the An Pass

003 login be lunched site appropriate
functionality 2.Selct the 2. enter message
with admin admin option Wrong should be
Invalid from drop username displayed
credentials down list and and the user
password should not
be allowed
to login.

77
Laundry ERP
TC- Validate 1. Site should 1. lunch the User are Pass
004 login be lunched site able to login
functionality 2.Selct the 2. enter in System
with user user option correct
credentials from drop username
down list and
password

Reports TC- Customer 1. Site should 1.Select An Pass

010 record be lunched customer, appropriate

Date 1. 2. Go to Document error

the report type and message
tab and incorrect should be
select date date 2. displayed
Click Get like “No
report Data Found”
button

TC- Report with 1. Site should 1.Select An Pass

011 correct date be lunched customer, appropriate
1. Go to the Document result sheet
Report tab type and will be
and select date visible
report 2.Click Get
report
button

78
Laundry ERP

Defect Report / Test Log

Test Case 1: Register New User

1. Open the Laundry ERP system.

2. Login with Admin Credentials.
3. Click on Register New User tab.
4. Enter required details.
5. Click on Save button.
6. Verify that new user has Saved Successfully.

Test Case 2: Report

1. Open the Laundry ERP system.

2. Login with User Credentials.
3. Select the Customer name.
4. Choose the Reports inside Report tab.
5. Select the options as per your requirement.
6. Click on Get Reports.
7. All the Results are generated as per selected format.

79
Laundry ERP

CHAPTER 6
LIMITATIONS OF
PROPOSED SYSTEM

80
Laundry ERP

6. LIMITATIONS OF PROPOSED SYSTEM

The proposed system is a web-based application designed for college administration. The
system will be maintained by the administrator and will provide a comprehensive set of
features to streamline various administrative tasks. These features include:

1. Customer Details Management:

• The system enables the storage and management of customer information.
• It facilitates the process of recording new customer, updating existing
users, and cancelling order when necessary.
2. Reporting:
• The system provides the ability to generate reports on various aspects of
college administration, such as customer statistics, cloth-wise data.

3. Scalability Challenges:

As the user base grows, the system may face difficulties in handling increased traffic and
demand. Scaling the infrastructure to accommodate more users and data might require significant
effort and resources.

4. Compatibility Issues:
The system might encounter compatibility problems with certain devices, browsers, or
operating systems, leading to suboptimal user experiences for some users.

5. Data Security Risks:

Despite implementing security measures, the system may still be vulnerable to potential data
breaches or cyberattacks, which could compromise sensitive user information.

6. Maintenance and Updates:

Regular maintenance and updates are necessary to keep the system running smoothly
and to address bugs and security vulnerabilities. However, performing updates may cause
temporary disruptions to the system.

7.Resource Intensive:
The system might require significant hardware and computing resources to operate
efficiently, potentially leading to higher operational costs

8.Dependency on Internet Connectivity:

Since the system is online-based, users heavily rely on stable internet connectivity. Limited
or unstable internet access can hinder their ability to use the system effectively.

81
Laundry ERP

9.Customer Support:
Users may require ongoing customer support to address their queries, troubleshoot issues,
and ensure smooth operations, which may incur additional expenses and resources.

10.Training and Onboarding:

The need for training and onboarding can be time-consuming and costly, especially for new
users who are not familiar with the system's functionalities.

11.Regulatory Compliance:
The system may need to comply with various legal and regulatory requirements, and keeping
up with these changes can be challenging and time-consuming.

12. Language and Localization:

If the system is designed to cater to a global audience, language and localization barriers may
arise, requiring translation and adaptation to various regions.

82
Laundry ERP

PROPOSED
ENHANCEMENTS

83
Laundry ERP

7. PROPOSED ENHANCEMENTS

In future enhancements, there are plans to incorporate additional modules and functionalities
into the system, including:

1. Payment Module:
• A payment module can be integrated into the system to facilitate financial
transactions related to customer payment, online payment mode and other
financial obligations.
• This module would allow customer and dealers to make payments online,
view payment histories, and receive payment receipts.
• Add Barcode Generation.

2. Customizable Functionality:
• The system will be designed to accommodate the specific requirements of
different stores.

These future enhancements aim to further expand the capabilities of the system and cater to
the evolving needs of colleges. By incorporating a payment module, financial transactions
can be streamlined, providing convenience and transparency to customers and dealers.
Additionally, the system's flexibility will allow colleges to customize and tailor its
functionalities to align with their specific administrative processes and requirements.

84
Laundry ERP

CONCLUSION

85
Laundry ERP

8. CONCLUSION

➢ Computerized system is more effective than manual system.

➢ During development of this system we learned new technologies, which would serve us in future.
We have tried our level best to develop a system according to user requirement.

➢ Save and manage time.

➢ Automation of the entire system improves the efficiency.

➢ It provides a friendly graphical user interface which proves to be better when compared to the
existing system.

➢ It gives appropriate access to the authorized user depending on their permissions.

➢ Updating of information becomes so easier.

➢ System security, data security and reliability are the striking features.

➢ The System has adequate scope for modification in future if it is necessary.

➢ It reduces paper work and also provides flexibility for data Retrieval.

➢ It is eco-friendly.

➢ It gives appropriate access to the authorized user depending on their permissions.

➢ Updating of information becomes so easier.

86
Laundry ERP

➢ System security, data security and reliability are the striking features.

➢ The System has adequate scope for modification in future if it is necessary.

➢ Continuing with the advantages and learnings from the development of the proposed laundry
management system:

87
Laundry ERP

BIBLIOGRAPHY

88
Laundry ERP

9. BIBLIOGRAPHY

Bibliography

• Phillips, P. 2003. e-Business Strategy. McGraw-Hill: London, UK. Kumar, S. K.

• Whitten, Bentley, and Dittman. 2004. System Analysis and Design Methods (5th ed).
New York, NY.

• PerlScriptsJavaScripts.com. 2006. “SQL Tutorial, Database Commands, Beginners

Guide, Perl

Web site References:

• www.google.co.in

• http://www.perlscriptsjavascripts.com/tutorials/sql/index.html

• Free Perl Scripts. Free JavaScripts (perlscriptsjavascripts.com)

• http://jakartha.apache.org
• https://wikipedia.org/wiki/ASP
• www.programmerheaven.com
• http://indiastudychannel.com
• www.develoeradvantage.com

89
Laundry ERP

90