LAUNDRY DIGITAL ORDERING SYSTEM

USING VOICE RECOGNITION

NUR IRYANA BINTI MOHD AFZAL

BACHELOR OF COMPUTER SCIENCE

(INTERNET COMPUTING) WITH HONOURS

FACULTY OF INFORMATICS AND COMPUTING

UNIVERSITI SULTAN ZAINAL ABIDIN

2020

DECLARATION

I hereby that this report is based on my original work except for quotations and citations,

which have been duly acknowledged. I also declare that it has not been previously or

concurrently submitted for any other degree at Universiti Sultan Zainal Abidin or other

institutions.

______________________________

Name : Nur Iryana binti Mohd Afzal

Date :

i

CONFIRMATION

This is to confirm that:

The research conducted and the writing of this report was under my supervision.

______________________________

Name : Dr. Suhailan bin Safei

Date :

ii

ACKNOWLEGDEMENT

Foremost, I would like to express my appreciation for my beloved family who

continually support me and provide the necessary resources for me to complete my

degree final year project.

I also wish to express my sincere thanks to my supervisor Dr. Suhailan bin Safei,

for provide guiding along the way of writing my thesis. Besides, I am feeling thankful

to him for sharing his expertise, valuable knowledge in voice processing and

encouragement extended to me.

Lastly, I would like to take this opportunity to express gratitude to all my friends

who directly or indirectly, have lent their hands for help to develop my project. Thanks

to my friend who assist me by giving the idea of coding to develop the system. Thanks

to my colleague who always supports me mentally and giving encouragement in the

process of developing my final year project.

Most of all, thanksgiving, praise, and glory is all to Allah SWT, who gives me

grace, patience, healthy, wisdom, and ability to walk through all the problems and

obstacles during the period of my study.

iii

ABSTRACT

Nowadays, the laundry service is growing from time to time. Laundry is one of

the favourite premises. However, it is common if customers complain about not feeling

happy about the services offered. There are many reasons that cause customer

dissatisfaction. The reason is that when customers make their own bookings using the

facilities provided such as computers, there is also to damage and lose on the keyboard

or mouse. Therefore, other customers will find it difficult to place an booking using the

facilities provided. To make technology more age and current situation friendly, it is

important to understand the advantages that disabled persons and senior citizens

perceive in using it. To assist laundry management with users placing their own booking

without any problems. This project will propose a Digital Laundry Ordering System

that uses web basics for PCs and techniques using Voice Recognition. The technique to

be used is the Web Speech API. Applying voice recognition technology seems will help

a lot in enhancing safety for certain situations. It can prevent the loss and damage of the

keyboard and mouse. It also can be reduced the space for placing multiple monitors in

the kiosk. Voice recognition is to facilitate senior citizens and disabled persons to make

their daily routine easier. With their voice, they can book our services. The flow of this

system is customer must go to the laundry kiosk to place an booking. Customers need

to say "HELLO" at the screen monitor to get unique customer identification. After that,

customer need to choose items and how many items their wants. Lastly, customers can

get the receipt from the booking and go to counter to give their clothes. It's easy for the

customer to make a booking at any time.

iv

CONTENTS

PAGE

DECLARATION i

CONFIRMATION ii

ACKNOWLEDGMENT iii

ABSTRACT iv

CONTENTS v

LIST OF FIGURES ix

LIST OF TABLES xi

CHAPTER I INTRODUCTION

1.1 Project Introduction 1

1.2 Problem statement 2

1.3 Objectives 3

1.4 Scopes 3

1.5 Limitation of Works 4

1.6 Expected Result 4

1.7 Summary 5

v

CHAPTER II LITERATURE REVIEW

2.1 Introduction 6

2.2

2.2.1

2.2.2

2.2.3

2.3

2.4

2.4.1

2.4.2

2.4

Related Works

iLaundry

Maurice Dry Cleaners

CD One Price Cleaners

Technique Speech Recognition

Application using Voice Recognition

Google Assistant

Google Cloud Speech-to-Text

Summary

7

7

8

9

10

11

11

12

13

vi

vii

CHAPTER III METHODOLOGY

3.1 Introduction 14

3.2

3.2.1

3.2.1.1

3.2.2

3.2.2.1

3.2.2.2

3.2.2.3

3.2.2.4

3.2.2.5

3.2.3

3.2.4

3.2.5

3.2.6

Project Methodology

Requirement Phase

Gantt Chart

Design Phase

Context Diagram

Data Flow Diagram Level 0

Data Flow Diagram Level 1

Entity Relationship Diagram

Data Dictionary

Development Phase

Testing Phase

Deployment Phase

Review Phase

15

16

17

18

19

20

21

22

23

24

25

25

25

3.3

3.3.1

3.3.2

Project Requirement

Hardware Requirement

Software Requirement

26

26

27

3.4 Summary 27

viii

CHAPTER IV IMPLEMENTATION Pages

4.1

4.2

4.2.1

4.2.2

4.2.3

Introduction

Interfaces

Interface Customer

Interface Staff

Interface Admin

28

29

29

33

36

4.3

4.3.1

4.3.2

4.3.3

4.3.4

Testing and Result

Introduction

Testing Analysis

Test Case

Results

40

40

40

41

45

4.4 Summary 45

CHAPTER V CONCLUSION AND DICUSSION

5.1 Introduction 46

5.2 Project Contribution 47

5.3 System Constraints 48

5.4 Suggestion for Improvement 49

5.5 Summary 49

REFERENCES 50

LIST OF FIGURES

FIGURES TITLE PAGE

2.1 iLaundry 7

2.2 Maurice Dry Cleaners 8

2.3 CD One Price Cleaners 9

2.4 Google Assistant 12

2.5 Google Cloud Speech-to-Text 13

3.1 Agile Methodology 15

3.2 Context Diagram 19

3.3 Data Flow Diagram Level 0 20

3.4 Data Flow Diagram Level 1 21

3.5 Entity Relationship Diagram 22

4.1 First interface of customer site 29

4.2 Second interface of customer site 30

4.3 Third interface of customer site 31

4.4 Fourth interface of customer site 32

4.5 First interface of staff site 33

4.6 Second interface of staff site 34

4.7 Third interface of staff site 35

4.8 First interface of admin site 36

4.9 Second interface of admin site 37

ix

x

4.10 Third interface of admin site 39

4.11 Fourth interface of admin site 39

4.12 Fifth interface of admin site 40

LIST OF TABLES

xi

TABLES TITLE PAGE

3.1 Gantt Chart 17

3.2 Data Dictionary 24

3.3 List of hardware requirement 26

3.4 List of software requirement 27

4.1 Test case for successful of open and login 41

4.2 Test case for successful register 41

4.3 Test case for view and update the items 42

4.4 Test case for customer booking items 43

4.5 Test case for staff view booking 44

CHAPTER I

INTRODUCTION

1.1 Project Introduction

Every day we will change the clothes we wear. Clothes that are dirty will be washed

a wear on another day. These clothes will be washed by hand or washing machine to

make sure the clothing is clean from all dirt. Today, most homes already have a washing

machine. There are also companies that have opened laundry services. The laundry

service makes it easier for individuals who have time constraints to wash their clothes.

Nowadays, the laundry service is growing from time to time. Laundry is one of the

favourite premises. However, it is common if customers complain about not feeling

happy about the services offered. There are many reasons that cause customer

dissatisfaction. The reason is that when customers make their own bookings using the

facilities provided such as computers, there is also to damage and lose on the keyboard

1

or mouse. Therefore, other customers will find it difficult to place an order using the

facilities provided. To assist laundry management with users placing their own booking

without any problems. This project will propose a Digital Laundry Ordering System

that uses web basics for PCs and techniques using Voice Recognition. The technique to

be used is the Web Speech API.

1.2 Problem Statement

In our daily life, we use many online systems and new technologies in order to

improve the quality of our life but most of them are not user friendly for those users

who face difficulties in typing. Besides that, some people face difficulties using online

systems. However, it is common if customers complain about not feeling happy about

the services offered. There are many reasons that cause customer dissatisfaction. The

reason is that when customers make their own bookings using the facilities provided

such as computers, there is also to damage and lose on the keyboard or mouse.

Therefore, other customers will find it difficult to place an order using the facilities

provided. In addition, the difficulty for disabled persons and senior citizens to use the

facilities provided to book their bookings.

2

1.3 Objective

There are three main objectives for this proposal. These objectives are derived to

overcome problems that stated before. The objectives are:

i.To analyze the usage of the digital ordering technique using a voice recognition

system.

ii.To design a system that can capture voice ordering for the laundry system.

iii. To develop the laundry system using voice recognition to receive customer booking.

1.4 Scope

The scope of this project is divided into three entities which are knows as the

customers, staff and, admin. In customer scope, customers need to speak what item their

wants for booking. After that, in staff scope staff will manage the booking and also can

change the status from new to uncompleted to completed. Lastly in the admin scope,

admin will add, delete, or update items and staff also can view the report.

3

1.5 Limitation of Works

The limitation of this project is as the following:

i.Does not cover storing audio file

ii. Just support Google Chrome only

iii. The customer's different dialect might be a problem.

iv. Just cover the English language

1.6 Expected result

The expected result after releasing this system is user should be able to make

booking service by the system through voice recognition. The benefit is this system also

can reduce the save time and energy and it easy for the customer to make a booking at

any time. While on the admin site, they can view, update, or delete the data of the

system. The developer also expected that the system could function well and fulfill the

user requirement standard.

4

1.7 Summary

In this chapter 1 focuses on the project introduction of the system, problem

statement, objective, scope, and limitation of work in the voice recognition system. For

the system, background explains the process of voice recognition. The problem

statement is about why voice recognition important to make booking more reliable. For

this chapter 1 has the objective for this holding system that means the income of this

project. The project scope just focus on the user and this project has a few limitations

of works.

5

CHAPTER 2

LITERATURE REVIEW

2.1 Introduction

This section takes a critical review of the existing system implemented, the

success factors, challenges faced, technologies used, and unresolved problems. This

forms the basis for implementing later versions.

6

2.2 Related Works

2.2.1 iLaundry

iLaundry puts over 20 years of expert care refer to figure 2.1 from

(http://www.ilaundry.co/,2000) handling, and experience behind every garment. Their

award-winning facility uses green energy & environmentally friendly processes,

providing brighter, fresher, and cleaner garments. iLaundry is one of the largest online

laundry service providers in Bangalore. There's are dedicated to providing you with the

best care for your garments.

Figure 2.1 iLaundry

7

2.2.2 Maurice Dry Cleaners

Maurice Dry Cleaners their pride themselves refer to figure 2.2 above from

(http://www.mauricedrycleaners.com.au/) on being leaders in garment cleaning

technology servicing throughout the Sydney CBD. Their service to the CBD of Sydney

is second to none with their highest quality cleaning and same-day delivery always our

priority. This is only achieved by 10 handy locations and fleet of vehicles that allow us

to keep our prices competitive and delivered on time without fuss. From their high-end

designer wear through to their crisp white business shirt service, no piece of clothing

you wear is left out. At Maurice, with over 30 years of experience, we are committed to

obtaining the most up to date of machinery with the greatest of consideration to our

environment. Their all-new hydrocarbon dry cleaning machines along with our many

states of the art shirt machines allows us to be leaders in the dry clean industry in the

Sydney metro area.

Figure 2.2 Maurice Dry Cleaners

8

2.2.3 CD One Price Cleaners

CD One Price Cleaners concept is the result refer to figure 2.3 above

from(https://www.cdonepricecleaners.com/), of nearly 30 years of industry experience,

applied with sophisticated business and process knowledge, techniques, and discipline

to create unrivaled quality and customer satisfaction. CD One Price Cleaners centers on

volume, efficiency, and customers. Specializing in garments, with all equipment-as well

as the operator-on premises, enables our low price offering and creates a buyer

experience you will not find at any other same-day laundry service CD One Price

Cleaners process is proven. It's designed to the last detail to deliver high volume while

maintaining exceptional quality. Our people work hard every day to operate it

flawlessly. That's why it works.

Figure 2.3 CD One Price Cleaners

9

2.3 Techniques for Speech Recognition

Voice recognition can capture the word you say and type it on a computer. It

can be helpful to the people who are physically disabled and for those who cannot work

on the computer. Speech recognition is the ability of a machine or program to identify

words and phrases in spoken language and convert them to a machine-readable format

and known as automatic speech recognition. In other words, rather than using a

keyboard to communicate with the computer, the user speaks commands into a

microphone that is connected to a computer. The technique used is the Web Speech API

designed for speech analysis and speech synthesis. It allows web users to send speech

input to web applications. Web applications use the Web Speech API to transform the

speech into text. While mobile phone users have become used to a speech as a new input

method, it is currently uncommon to see voice-controlled web applications. Altogether,

the speech recognizer has difficulties with many of the sentences. The sentences are

difficult, at least when judged by a human listener. They sound uncommon and are

sometimes difficult to understand for non-native English speakers. How this relates to

the difficulty level for machine understanding is out of the scope of this work. This

definition from (Julius Adorf- May 27, 2013).

10

2.4 Application using Voice Recognition

2.4.1 Google Assistant

Google Assistant is Google's voice assistant refer to figure 2.4 from

(https://assistant.google.com/intl/en_my/platforms/phones/). When it launched, Google

Assistant was an extension of Google Now, designed to be personal while expanding

on Google's existing "OK Google" voice controls. Originally, Google Now smartly

pulled out relevant information for you. It knew where you worked, your meetings and

travel plans, the sports teams you liked, and what interested you so that it could present

you with information that mattered to you. Google has long killed Google Now, but

Assistant lives in the same space, fusing these personalized elements with a wide range

of voice control. Google Assistant supports both text or voice entry and it will follow

the conversation whichever entry method you're using. Google Assistant offers voice

commands, voice searching, and voice-activated device control, letting you complete a

number of tasks after you've said the "OK Google" or "Hey, Google" wake words. It is

designed to give you conversational interactions. This definition from (Julius Adorf-

May 27, 2013).

11

Figure 2.4 Google Assistant

2.4.2 Google Cloud Speech-to-Text

Google Cloud Speech-to-Text enables developers refer to figure 2.5 from

(https://cloud.google.com/speech-to-text/), to convert audio to text by applying

powerful neural network models in an easy-to-use API. The API recognizes 120

languages and variants to support your global user base. You can enable voice

command-and-control, transcribe audio from call centers, and more. It can process real-

time streaming or pre-recorded audio, using Google’s machine learning technology.

12

Figure 2.5 Google Cloud Speech-to-Text

2.5 Summary

In conclusion, the literature review gave details understanding or assumptions

on the developer documentation. It involves some of the research and studies that are

done by other people who are related to the project. Based on the research, the flow to

develop this project can be seen clearly throughout the system development process.

There is no laundry system that uses voice recognition for customers to place their

bookings.

13

CHAPTER 3

METHODOLOGY

3.1 Introduction

Suitable project methodology plays an important role to ensure the research can

be done well. This chapter will focus on the project methodology used to run this

project. Research on this topic is made to understand how Laundry Digital Ordering

System using Speech Recognition works using the Agile Model. The type of research

methodology used in this project will be described. Furthermore, this methodology is

used to ensure that the project can fulfil the objective of this project and to make sure

the system can be accomplished completely.

14

3.2 Project Methodology

The methodology is a method used to develop a system and defined as a set of

procedures. This chapter will cover the methodology used based on research that has

been done. The project system of the Laundry Digital Ordering System is using Agile

methodology. This chapter will fully explain to achieve the project’s objectives that

have been mention earlier in this research report. The methodology is an important part

to make sure the system can be accomplished successfully.

Figure 3.1 Agile Methodology

15

3.2.1 Requirement Phase

In this phase, the project title had been selected. The project title for the system

was the Laundry Digital Ordering System. This project starting with brainstorming

ideas with the supervisor and proposed the title of the project. An abstract and

description of the project module have also been done and attached. Besides, the Gantt

chart also needed as a guideline and references for the project. The phase is to analyze

the existing system and the article of technique or method that is needed to design and

develop the new system. Based on the collection of information through article, method,

and technique that is suitable been decided.

16

3.2.1.1 Gantt Chart

The timeline of this project as a following:

3.1 Table of Gantt Chart

17

NO WEEK/

ACTIVITIES

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

1 Topic

Discussion and

Determination

2 Project Title

Proposal

3 Proposal

Writing –

Introduction

4 Proposal

Writing –

Literature

Review

5 Proposal

Writing

(Continued)

6 Proposal

Progress

Presentation

and Panel’s

Evaluation

7 Methodology

Workshop

8 Proposal

Writing -

Methodology

9 Final Year

Project Format

Writing

Workshop

10 Drafting Report

of Proposal

11 Submit Draft of

Report to

Supervisor

12 Preparation for

Final

Presentation

13 Final

Presentation

and Panel’s

Evaluation

14 Final Report

Submission

3.2.2 Design Phase

In the design phase, all the data or requirements obtained during the planning

and analysis phase transformed into the design. Diagrams to show the flow of the system

will be developed in this chapter such as Context Diagram (CD), Data Flow Diagram

(DFD) Level 0, and 1, Entity Relationship Diagram (ERD). These diagrams are

designed as a guideline to developing the system. After that, will be designing the

database and system interface.

18

3.2.2.1 Context Diagram

Figure 3.2 shows the context diagram (CD) of the system. This CD describes

the overview of the system work. There are three entities involved that are customer,

staff, and admin. The customer can make an booking to the system

While the staff site, they can see the booking details from the customer then

update the process booking in the system. Admin can manage the data about the system.

With this data, the admin can update and delete information users also can view all

report.

Figure 3.2 Context Diagram

19

3.2.2.2 Data Flow Diagram

Figure 3.3 shows the Data Flow Diagram (DFD) of the system in more detail.

The system carried out four processes. The core of this system in the fourth process.

The fourth process includes three entities which are customer, staff, and admin. The

ability of customers only can know the status while staff and admin can update the data

beside know the process.

Figure 3.3 Data Flow Diagram

20

3.2.2.3 Data Flow Diagram Level 1

Figure 3.4 below show DFD Level 1 for customer manage booking which is

customer can add, update and delete booking from the system.

Figure 3.4 Manage Booking Process Level1

21

3.2.2.4 Entity Relationship Diagram

Figure 3.5 shows the Entity Relationship Diagram (ERD) for this system. ERD

is a data modelling technique that can help define business processes and can be utilized

as the basis a relational database. In this system, the developer needs to create four

entities represented four tables into the database. Each entity has its own attributes

shown in figure 3.5. The relationship between entities explains the process that will

carry out by every entity. This entity relationship diagram also explains the data needed

to run the application successfully. The figure also showed the different role between

customer and staff in more detail.

Figure 3.5 Entity Relationship Diagram

22

3.2.2.5 Data Dictionary

Table 3.2 of Data Dictionary

Entity Attribute Description Data Type Size Remark

Admin adminId Identification of admin int 11 PK

password Password admin to login varchar 10

adminName Name of admin varchar 255

Customer custId Identification of customer int 11 PK

Order orderId Identification of order int 11 PK

voiceid Identification of voice int 11 FK

custId Identification of customer int 11 FK

staffId Identification of staff int 11 FK

serviceId Identification of service int 11 FK

status Status of order varchar 255

quantity Quantity of order varchar 255

date Date of order Datetime

Staff staffId Identification of staff int 11 PK

staffName Name of staff varchar 255

password Password to staff login varchar 10

orderId Identification of order int 11 FK

Service serviceId Identification of service int 11 PK

serviceName Name of service varchar 255

23

3.2.3 Development Phase

This phase is where the design will implement into the coding. This system will

develop regarding the user and system requirements. In this project, to develop the

system will be used Xampp server for the database, Laravel as a framework and the

technique to be used is the Web Speech API. This is a critical phase because the user

part needed to be fulfilled and to make sure the objective accomplished.

24

3.2.4 Testing Phase

When all the module has to be done as a full system, the system testing has been

carried out. This testing phase will test the system to check the error and ensure the

function runs well as a whole system. Any error or bugs will be fixed and repeated

testing the system until all the functions can be used.

3.2.5 Deployment Phase

This phase is when the system has successfully done and fulfilled all the

objectives. The system can be deployed and finally, the system will be published to the

user for use as their need.

3.2.6 Review Phase

This phase also gets feedback and review from the user for the maintenance.

This phase will, follow-up with the user to upgrade the system to another version in the

future.

25

3.3 Project Requirement

In this project, the requirement includes two parts which are software

requirement and hardware requirement. The project requirements to make sure the

completion process well and every aspect requirement that needs to be used for the

implementation phase. This also ensure the correct usage of the application.

3.3.1 Hardware Requirement

Table 3.3 List of hardware requirement

No. Hardware Description

1. Laptop LENOVO IDEAPAD

2. Processor Intel (R) Core (TM) i5-7200u CPU 2.50Ghc

2.70Ghz

3. Memory 4GB RAM

4. Operating System Windows 10

5. System Type 64-bit Operating Sytem

6. Pen Drive Kingston 16GB

7. Mobile Phone IPHONE 7PLUS

26

3.3.2 Software Requirement

Table 3.4 List of software requirement

No. Software Description

1. Notepadd++ Used to code the program, especially connection

application to database

2. Java, XML, PHP Programming language

3. MYSQL Database for system

4. Microsoft Word 2016 Used to do documentation of application

5. Google Chrome A browser to run the localhost and searching

information

3.4 Summary

This chapter discussed the model methodology approach to be used in the

development system. The methodology that been used for this project is the Agile

Methodology that explains about six-phase. This chapter so includes Context Diagram

CD Data Flow Diagram DFD and Entity Relationship Diagram ERD. The diagram

explains about the process or steps A to Z to develop the System.

27

CHAPTER 4

IMPLEMENTATION

4.1 Introduction

This project is implemented using Hypertext Preprocessor (PHP) language. This

will help developers design, code, test, debug, and execute the main process of the

project. The main of the project is focused on the customer, staff and admin site. The

customer functions are speak what items and how items their want to wash. While staff

has function view all booking laundry from customers and make updating the process

from new to uncompleted to completed.

Implementation and testing are the main phases in this development process.

The technique adopted for the evaluation and testing of the project is test case testing

which tests the system functionalities modules by modules to ensure that the software

conforms to its specification and meets the requirements. This chapter should finish

before the application is complete.

28

4.2 Interfaces

4.2.1 Interfaces Customer

Figure 4.1 shows the first site before the user can use the system. They should

say ‘HELLO’ to go to the next page.

Figure 4.1 First interface of customer site

29

Figure 4.2 shows the second customer site, they will get one unique customer

identification upon entering this site. They have to say what items they need and data

will save into the database.

Figure 4.2 Second interface of customer site

30

Figure 4.3 shows the third customer site. After customer did choose the services,

their need to say how many clothes to wash.

Figure 4.3 Third interface of customer site

31

Figure 4.3 shows the fourth customer site. After customers done bookings, they

can see what items they choose in this interface and the price will display. If a customer

wants to add clothes to wash, they need to say ''ORDER'' and turn back into the second

site. If customer want to make confirmation for their booking, there must say ''YES''.

Then confirmation booking is done. If the customer wants to cancel the selected items,

they must say “DELETE” and turn back into the second site to book new items.

Figure 4.4 Fourth interface of customer site

32

4.2.2 Interfaces staff

Figure 4.5 shows the first staff site. They need to log in first before they can use

the website.

Figure 4.5 First interface of staff site

33

Figure 4.6 shows the second staff site. After log into the website, the staff will

see a table that has all the booking items from the customer. Staff need to click

“COMPLETED” or “UNCOMPLETED” to make update status.

Figure 4.6 Second interface of staff site

34

Figure 4.7 shows the third staff website. Staff can print receipts when laundry

is completed and give to the customer

Figure 4.7 Third interface of staff site

35

4.2.3 Interfaces admin

Figure 4.8 shows the first admin site. They need to log in first before they can

use the website.

Figure 4.8 First interface of admin site

36

Figure 4.9 shows the second admin site. After log into the website, the admin

will see a table that has all the booking items from the customer. Staff need to click

“COMPLETED” or “UNCOMPLETED” to make update status.

Figure 4.9 Second interface of admin site

37

Figure 4.10 shows the third admin site. Admin can insert the full name, email,

phone number and password of staff.

Figure 4.10 Third interface of admin site

Figure 4.11 shows the fourth admin site. Admin can insert item name and item

price.

Figure 4.11 Fourth interface of admin site

38

Figure 4.12 shows the fifth admin site. Admin can view all report between items

and quantity.

Figure 4.12 Fifth interface of admin site

39

4.3 Testing and Result

4.3.1 Introduction

A test case is a set of conditions or variables under which a tester will determine

if a requirement upon an application is partially or fully satisfied. A test case also can

define as a sequence of steps to test the correct behaviour of functionality or feature of

the system. There is a list of steps, test, procedures, and expected outcomes would be

stated in a test case. The test case for login, insert new items, update the items, and

display all the data of booking and status laundry. The test case for the main system

which database for admin, staff, and booking items.

4.3.2 Testing Analysis

Testing is needed to test system full function and free error. There are three types

of testing in the system. Those are unit testing, integration testing, and system testing.

Unit testing is carried out to verify the functionality of specific section code and

integration testing works to exposed defects in the interfaces and interaction between

modules. End-to-end testing or system testing tests a complete integrated system to

verify that it meets its requirements.

40

4.3.3 Test Case

Table 4.1 Test case for successful of open and login the system

Test Case For Successful Of Open The System

Steps Test Procedure Expected Result

1. Open the system of iWash Laundry View login page

2. User enter the following details:

Email:yayairyana98@gmail.com

Password : 123

3. User click “Login” button Login page loaded. Login is successful

and redirected to booking page.

Table 4.2 Test case for successful register

41

Test Case For Successful Add Items

Steps Test Procedure Expected Result

1. Click the “Add Items” button to enter

page register

View register items page

2. Admin enter the following details:

Itemse Name : Pant

Price/Unit/KG(RM) : RM0.50

3. Admin click “Submit” button Register page loaded. Register is

successful and redirected to items page.

Table 4.3 Test case for view and update the items information.

42

Test Case For View and Update The Services Information

Steps Test Procedure Expected Result

1. Click “Items” button View items page that have items information. In

the page also has “Edit” button.

2. Click “Edit” button View update page that have edit text to edit

2. User enter the following details:

Items Name : Pant

Price/Unit/KG(RM) : RM0.80

Only written can be updated.

3. Select “Update” button The system redirected to page items to view

updated information. Update detail is saved.

Table 4.4 Test case for customer booking items

Test Case For Customer Booking Service

Steps Test Procedure Expected Result

1. Say “HELLO” View home page.

2. Say what items you want View items page

2. Say how much cloth to wash View items page

3. Customer get items and total price The system carries customer information, items,

and price to confirm the booking. View all detail

before making a confirmed booking. There is a

button “YES”, “ORDER” and “DELETE”.

4. Say “YES” The system saves the booking details and

redirected to home page

5. Say “ORDER” The system back to the items page.

6. Say “DELETE” The system deleted the items and back to add

new items page.

43

Table 4.5 Test case for staff view booking

Test Case for Staff View Booking

Steps Test Procedure Expected Result

1. Menu page booking View of list customer and information about

cloths process.

2. Click “COMPLECTED” for update

status

The system redirected to page booking to view

updated information. Update detail is saved.

2. Click “UNCOMPLECTED” for

update status

The system redirected to page booking to view

updated information. Update detail is saved.

4.3.4 Results

The expected result after releasing the Laundry Digital Ordering System using

Voice Recognition is the customer should be able to make booking items by the system.

It is easy for customers to make bookings at any time. The benefit this laundry also can

help staff to reduce their work, save time and energy. While on the admin site, they can

view, update, or delete the data of the system. The developer also expected that the

system could function well and fulfil the user requirement standard.

44

4.4 Summary

In a nutshell for this chapter, the developer shows the interfaces that developed

for the Laundry Digital Ordering System using Voice Recognition. The developer also

put a few of pop up message after the user does certain activities. This will help the user

alert with the action they act. Next, the testing phase did by the developer by testing the

system. This phase also important because it optimizes the system for a high level. A

few errors can be identifying and the developer fixed to improve the functionality of the

system. The developer does test from unit testing until integrated testing. If there has an

error, the developer will be fixed immediately. Finally, the case necessary to guide the

tester to test the system. The system will repeatedly be tested to minimize the error.

45

CHAPTER V

CONCLUSION AND DISCUSSION

5.1 Introduction

By the end of this study, Laundry Digital Ordering System using Voice

Recognition is expected that it can encourage the citizens to use the system platform to

use laundry service in their daily life. The interfaces less complex design and easy to

use which the user only need to fulfil the booking form and confirmation. Then, the

automatic result for their laundry service will display. While on the staff site, this system

will help them to view a list of booking data from the customer and update the data.

46

5.2 Project Contribution

Laundry Digital Ordering System using Voice Recognition that will be applied

to Laundry Company in Malaysia. This system also contributes toward solving some of

the challenging problems due to issue customers. It's easy for the customer to make a

booking at any time. Users can use voice recognition more interactive since the user

does not need to navigate the computer by using a keyboard. The system also

contributes to the staff of company laundry. They can manage the data related to

customer booking also help staff to reduce their work and energy. They just need to

access the website to manage that data.

47

5.3 System Constraints

There are few problems that can be found during the process to achieve the project

objectives. The problem during the development of the system as the following:

i.Technology is growing very rapidly. The developer must alert the new update. This is

because we want to prevent the system is developed will exist some bug or not

compatible with the current technology. So, the developer must follow the current

technology.

ii. Laundry Digital Ordering System using Voice Recognition it also has constraints.

The constraints are the construction phase. Developing this system was the biggest

challenge faced in this project. With limited knowledge on framework LARAVEL, a

lot of time we're spending in understand the system and research on ways to program

voice recognition. However, with the help of the supervisor skills and friends, it has

made the learning process much shorter.

48

5.4 Suggestion for Improvement

Although the system operates properly and follows the milestone of the project

respectively, there exist some changes that can be taken for better performances. The

constraint as described before this can be corrected and improve the quality for the

future. The developer must come up to date with the current technology to ensure the

system that developed will meet the standard. For the future, the system also can be an

application and also can see their laundry status.

5.5 Summary

In a nutshell, Laundry Digital Ordering System using Voice Recognition was

developed to assist a variety of people either customers and staff of the company

laundry. With the development of the system, it was systematically the management

and planning of the customer and staff of laundry service. Then, the management on the

staff site also becomes easy and systematic in managing the data. Finally, the developer

hopes this system can use for the business market and achieve user expectations. So,

the system can give a better solution or suggestion to them while giving feedback for

improving the system in the future.

49

REFERENCE

Amanina Bt Abu Hassan, “ Laundry Broker System”, University of Sultan Zainal

Abidin, (2015).

Abdul Latif Bin Alias, “ One Click Laundry Mobile Application”, University of Sultan

Zainal Abidin, (2015).

Nurul Amirah Syuhada Binyti Yaacob , “ Speech To Text To Voice Using

Authentication Melfrequency Cepstral Coeficient”, University of Sultan Zainal Abidin,

(2018).

Noor Azizan Bin Nor Azli, “ School Attendance Via Voice Recognition By Using

Android Based”, University of Sultan Zainal Abidin, (2018).

Zalilawati Binti Ghazali, “ Laundry Management System”, University of Teknologi

Malaysia, (2008).

Mozilla Developer, “ How to Use Web Speech API ”, Web Technology Developer,

March 2019.

Julius Adorf, “ Wep Speech Api”, KTH Royal Institute of Technology, (2013).

50