INFINITY VENDOR (SMALL BUSINESS SYSTEM)

RAJA NUR NAJWA HUSNA BT RAJA ABDUL HALIM

BACHELOR OF COMPUTER SCIENCE (SOFTWARE

DEVELOPMENT) WITH HONOURS

UNIVERSITI SULTAN ZAINAL ABIDIN

2021

INFINITY VENDOR (SMALL BUSINESS SYSTEM)

RAJA NUR NAJWA HUSNA BT RAJA ABDUL HALIM

BACHELOR OF COMPUTER SCIENCE (SOFTWARE

DEVELOPMENT) WITH HONOURS

Universiti Sultan Zainal Abidin

2021

i

DECLARATION

I hereby declare that the 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: Raja Nur Najwa Husna binti

Raja Abdul Halim

Date: 27th January 2021

ii

CONFIRMATION

This is to confirm that this project entitled Infinity Vendor (Small Business System)

was prepared and submitted by Raja Nur Najwa Husna binti Raja Abdul Halim with

matric number BTAL19056847 and has been satisfactory in terms of scope, quality,

and presentation as partial fulfilment of the requirement for the Bachelor of Computer

Science (Software Development) with Honors in University Sultan Zainal Abidin. The

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

_______________________________

Name: Puan Rohana binti Ismail

Date: 27th January 2021

iii

DEDICATION

In the Name of Allah, the Most Gracious and the Most Merciful.

Alhamdulillah, I thank God for His grace and grace, I can prepare and complete this

report successfully.

First of all, I would like to thank my supervisor, Puan Rohana binti Ismail because with

guidance, the advice, and the thoughtful ideas are given g me the opportunity to prepare

this report successfully.

Besides, my gratitude is also to my colleagues who share ideas, opinions, knowledge,

and reminders. They helped me answer every question that was important to me in

completing this report.

Thanks also to my beloved mother and father always support and motivated me to

prepare for this report for Final Year Project.

I would like to take the opportunity to thank all lecturers of the Informatics and

Computing Faculty for their attention, guidance, and advice in helping and sharing ideas

and opinions in making this report successful.

May Allah SWT bless all the efforts that have been given in completing this report.

Thank you.

iv

ABSTRACT

Infinity Vendor System is a web-based system to help Malaysians during this critical

time. Since the pandemic, most of people need to work from home, including small

business owners. People also simply cannot go out to buy their needs. Therefore, since

there are so many people start to make online business, there will be a lot of similar

items sold in the market and the potential buyer will be having a hard time choosing

from which shop they want to buy from. This system designed to solve those problems

including the problem of inaccurate rating of each shop. By using this system, the

customer or potential buyer can save their time deciding from which shop to buy since

this system will suggest the preferred shop among them. This system also will benefit

the small business owner since they will have chance to promote their business in the

system. This system also will provide a complete details about each shop and goods

sold to make it easier for the customer to find what they need. Customer also can give

ratings and reviews to each shop to ease the next buyer in making decision. The

technique that used in the system is Collaborative Filtering to filter items that user might

like based on their previous rating. In conclusion, this system will be a great solution to

solve problems related to online small business.

v

ABSTRAK

Infinity Vendor System adalah sistem berasaskan web yang dibina untuk membantu

rakyat Malaysia pada masa kritikal ini. Sejak wabak ini merebak, kebanyakan orang

perlu bekerja dari rumah, termasuk pemilik perniagaan kecil. Orang ramai juga tidak

boleh keluar untuk membeli keperluan mereka. Oleh kerana terdapat banyak orang

yang mula menjalankan perniagaan dalam talian, akan ada banyak barang serupa

yang dijual di pasaran dan bakal pembeli akan menghadapi kesukaran untuk memilih

dari mana kedai yang ingin mereka beli. Sistem ini dirancang untuk menyelesaikan

masalah-masalah tersebut termasuk masalah penilaian tidak tepat bagi setiap kedai.

Dengan menggunakan sistem ini, pelanggan atau pembeli dapat menjimatkan masa

mereka untuk memutuskan dari mana kedai yang akan dibeli kerana sistem ini akan

mencadangkan kedai pilihan di antara mereka. Sistem ini juga akan menguntungkan

pemilik perniagaan kecil kerana mereka berpeluang mempromosikan perniagaan

mereka dalam sistem tersebut. Sistem ini juga akan memberikan perincian lengkap

mengenai setiap kedai dan barang yang dijual untuk memudahkan pelanggan mencari

barang yang mereka perlukan. Pelanggan juga dapat memberikan penilaian dan

ulasan untuk setiap kedai bagi memudahkan pembeli lain membuat keputusan. Teknik

yang digunakan dalam sistem ini adalah Collaborative Filtering untuk menyaring

barangan yang mungkin disukai oleh pengguna berdasarkan penilaian mereka

sebelumnya. Kesimpulannya, sistem ini akan menjadi penyelesaian yang baik untuk

menyelesaikan masalah yang berkaitan dengan perniagaan kecil dalam talian.

vi

CONTENTS

PAGE

DECLARATION i

CONFIRMATION ii

DEDICATION iii

ABSTRACT iv

ABSTRAK v

CONTENTS vi

LIST OF TABLES viii

LIST OF FIGURES ix

LIST OF ABBREVIATIONS x

CHAPTER 1 INTRODUCTION 1 1.1 Introduction 1

1.2 Project Background 1

1.3 Problem Statement 2

1.4 Objectives 2

1.5 Scope 3

1.6 Limitation of Work 3

1.7 Expected Result 4

1.8 Activities, Milestones (Gantt Chart) 4

CHAPTER 2 LITERATURE REVIEW 5 2.1 Introduction 5

2.2 Research on Related Research Technique 5

2.3 Solution Approach 7

2.3.1 E-Commerce 7

2.3.2 Recommender System 8

2.3.3 Collaborative Filtering 9

2.4 Algorithm 10

2.4.1 RATING BASED ON DATE 10

2.4.2 RATING BASED ON AVERAGE 11

2.4.2.1 Calculation for Shop A 12

2.4.2.2 Calculation for Shop B 13

2.4.2.3 Calculation for Shop C 14

2.5 Research on Existing System 15

2.5.1 TripAdvisor Website 15

2.5.2 Tiendeo Website 16

2.5.3 Google Maps Website 17

2.6 Conclusion 18

CHAPTER 3 METHODOLOGY 19 3.1 Introduction 19

3.2 Agile Methodology 19

3.2.1 Requirement Phase 20

3.2.2 Design Phase 20

3.2.3 Development Phase 21

3.2.4 Testing Phase 21

3.2.5 Deployment Phase 21

3.2.6 Review Phase 21

vii

3.3 Project Requirement 22

3.3.1 Software Requirement 22

3.3.2 Hardware Requirement 23

3.4 Framework Design 23

3.5 System Design and Modelling 24

3.5.1 Context Diagram (CD) 25

3.5.2 Data Flow Diagram (DFD) 25

3.5.2.1 DFD Level 1 25

3.5.2.2 DFD Level 2 26

3.5.2.3 Manage Goods 26

3.5.2.4 Manage Shop 27

3.5.2.5 Search Shop 27

3.5.2.6 Search Goods 28

3.5.3 Entity Relationship Diagram (ERD) 28

3.6 Data Dictionary 30

3.6.1 Overall System Database 30

3.6.2 Table Admin 30

3.6.3 Table Customer 31

3.6.4 Table Goods 31

3.6.5 Table Business Owner 32

3.6.6 Table Rating 32

3.6.7 Table Shop 33

3.7 Summary 34

REFERENCES 35

viii

LIST OF TABLES

Table No. Title Page

Table 2.1 Related Research Techniques in recommender system 6

Table 2.2 Example calculation of rating based on date 10

Table 2.3 Example calculation of rating based on average 11

Table 2.4 Rating calculation for Shop A 12

Table 2.5 Rating calculation for Shop B 13

Table 2.6 Rating calculation for Shop C 14

Table 2.7 Advantages and disadvantages of TripAdvisor website 15

Table 2.8 Advantages and disadvantages of Tiendeo website 16

Table 2.9 Advantages and disadvantages of Google Maps 17

Table 3.1 Software Requirement 22

Table 3.2 Hardware requirement 23

Table 3.3 Table for overall system 30

Table 3.4 Table for admin 31

Table 3.5 Table for customer 31

Table 3.6 Table for goods 32

Table 3.7 Table for business owner 32

Table 3.8 Table for rating 33

Table 3.9 Table for shop 33

ix

LIST OF FIGURES

Figure No. Title Page

Figure 1.1 Gantt Chart 4

Figure 2.1 TripAdvisor Website 15

Figure 2.2 Tiendeo Website 16

Figure 2.3 Google Maps 17

Figure 3.1 Figure of Agile methodology 20

Figure 3.2 Framework Design 24

Figure 3.3 Context Diagram 25

Figure 3.4 Data Flow Diagram Level 1 26

Figure 3.5 Data Flow Diagram Level 2 Manage Goods 27

Figure 3.6 Data Flow Diagram Level 2 Manage Shop 27

Figure 3.7 Data Flow Diagram Level 2 Search Shop 28

Figure 3.8 Data Flow Diagram Level 2 Search Goods 28

Figure 3.9 Entity Relationship Diagram 29

Figure 3.10 Entity Relationship Diagram Model 29

x

LIST OF ABBREVIATIONS

CD Context Diagram

CF Collaborative Filtering

DFD Data Flow Diagram

ERD Entity Relatioship Diagram

1

CHAPTER 1

INTRODUCTION

1.1 Introduction

This chapter will discuss about the project proposed. This chapter consists of

project background, problem statement, objectives and the scope of the project.

Limitations of the work and expected result for this project also will be mentioned in

this chapter. Other than that, this chapter will also show the Gantt Chart that describes

the timeline for this project. Lastly, summary for this chapter will be at the end of this

chapter.

1.2 Project Background

Nowadays, technology in business is a growing necessity. Over time, the

business world has becoming more technological. Technology gives a big impact in

business operations. No matter how big your business is, technology can bring many

advantages to help you increase the income and producing the goods demanded by your

customers.

This project is to develop a system with the aim of making it easier for small

business owners to promote their business and it also will provide convenience to

customer to find and choose their preferred store within thousands of stores at one place.

“Infinity Vendor” system can help the users in finding the store to buy their needs based

on their input criteria. Based on applied filters, this system will display the suggested

store after the user give the input of what kind of goods they are looking for and the

user’s budget. Finally, this system will also allow the user to rate and give their review

2

into the system, they also can see the rating of each store which will make this system

more useful to the other users.

1.3 Problem Statement

There are few problems that have been discovered while proposing the system.

The problem statement includes, small business owners these days tend to promote their

business online. It is easier for the owner who just started their business since they do

not have enough money to rent a physical shop to run their business. By promoting their

business online, they can just do that from home. But from the other side, the users are

having a hard time choosing a store that match to their preferences. Usually, to those

who are new to the online shopping, they will find it difficult to choose which store that

can be trusted. Most of the user need to be convinced by reading feedbacks from other

users. By referring to this system, they can see the review and which store suggested by

other users.

1.4 Objectives

The objectives of this system are identified as below:

1. To design a system that can allow the user to find a store to buy their needs

based on their preferences.

2. To develop a system that can implement collaborative filtering technique to each

store in the system.

3. To test the functionalities of the small business system to meet the user

requirement.

3

1.5 Scope

The scope of this system are Admin, Customer and Small Business Owner.

Admin

Can handle the management of the system

Can view all the shops registered in the system

Can delete shops and goods from the system.

Customer

Can register and manage personal information.

Can search for the shop and goods based on their preferences.

Can view the shop based on the rating given.

Can give the rating to the shop after sign in to the system.

Business Owner

Can register and manage profile.

Can add, delete and update the shop details.

Can add, delete and update the goods details.

1.6 Limitation of Work

A There are several limitation and constraint that occurred throughout the

development of the system. These problem and limitations in conducting this study are:

1. This system is only available for small businesses in Malaysia.

2. It is a web-based system, it can only be accessed through web browser.

4

1.7 Expected Result

This system is expected to provide information about small businesses to the users

and the user can choose the shop based on their preferences such as type of goods and

the price of the goods. This system also expected to provide fully function for functional

requirement. Lastly, accurate rating will be implemented after the user give rating to the

shop.

1.8 Activities, Milestones (Gantt Chart)

Table 1.1 shows gantt chart for the whole process of the proposed system.

Figure 1.1 Gantt Chart

5

CHAPTER 2

LITERATURE REVIEW

2.1 Introduction

This chapter basically will discussed about few sources that have been reviewed

before developing the project. Few journals and articles about the related technique and

approach was analyzed to make the project fully function and can fulfilled all the

requirements. The analysis, summarizing, evaluating and observation of the existing

system will also be made during this chapter. And by all the information collected, it

will be used to develop a new system that can provide a better function to user compared

to the existing system.

2.2 Research on Related Research Technique

Table 2.1 show the reviews on three related research techniques in recommender

system which are A Particle Swarm Approach to Collaborative Filtering based

Recommender Systems through Fuzzy Features, Evaluating Collaborative Filtering

Recommender Algorithms: A Survey, and An Efficient Deep Learning Approach for

Collaborative Filtering Recommender System.

6

Table 2.1 Related Research Techniques in recommender system

Authors Title Objective Methodology Result

Mohammed

Wasid, Vibhor

Kant

A Particle

Swarm

Approach to

Collaborative

Filtering based

Recommender

Systems

through Fuzzy

Features

To test the

effectiveness

of the proposed

recommender

system through

an experiment

regarding

different

performance

using the

MovieLens

dataset.

Collaborative

Filtering

The system

will able to

give a better

recommendatio

ns to the user

by using

FPSO-CF

approach.

Mahdi Jalili,

(Senior

Member, Ieee),

Sajad

Ahmadian,

Maliheh Izadi,

Parham

Moradi,

Mostafa Salehi

Evaluating

Collaborative

Filtering

Recommender

Algorithms: A

Survey

To make

comparison

between a few

popular model-

based

Collaborative

Filtering (CF)

algorithms in

terms of

various

Collaborative

Filtering

The result of

the survey

shows that

there is no

golden

algorithm that

perform better

than each other

in all

evaluation

metrics.

7

evaluation

metrics.

Mohammed

Fadhel Aljunid,

Manjaiah DH

An Efficient

Deep Learning

Approach for

Collaborative

Filtering

Recommender

System

To make a

comparison

between a

proposed and

existing

methods.

Recommender

System

The

experiment

that have been

made shows

that the

proposed gives

better results

compared to

the existing

methods.

2.3 Solution Approach

Solution approach describes the possible approach that will be taken to be apply

in the system. Therefore, in order to find the solutions, we need to make sure whether

the approaches are capable to implement or not. So, the technique that will be used in

this system is Collaborative Filtering.

2.3.1 E-Commerce

E-commerce or Electronic-Commerce are defined as the ‘trading of goods or

services over computer networks such as internet’ (Tolstoy et al., 2020). It is also one

of representation on how digital transitions continue to grow in individuals,

organizations and societies (Bjerkan et al., 2020). Online shopping also has become

8

more popular and it is become the central platform for the shoppers throughout the

development of e-commerce (Parveen et al., 2021). The number of online shoppers has

increased by 85% since the last decade in Europe and e-commerce is expected to

comprise 36% of world trade by 2030 (Bjerkan et al., 2020).

Electric commerce is growing steadily as a result of the advantages it gives to

the customers and businesses (Hurtado et al., 2019). It has a big impact on economic

growth and offers equal opportunities for anybody to start a business without obstacle

(Haryanti & Pribadi, 2019). The increased of accessibility of the Internet via computers

and smartphones has led to the establishment of the e-commerce industry worldwide

(Hurtado et al., 2019).

2.3.2 Recommender System

Recommender system play an important role in today’s business intelligence,

helping businesses to maximize their income while giving personalized suggestions.

When it comes to algorithms, existing recommender system can be gathered into three

broad categories, context-aware, collaborative and hybrid models. In context-aware,

recommender system will learn a profile of new user’s preferences based on the features

describes the items user has rated before. While for collaborative, the recommender

system learns to identify the similarities in a user-item matrix to suggest a

recommendation. Lastly, hybrid models will combine two or more algorithms with the

aim to boost the overall performances (Nápoles et al., 2020).

9

2.3.3 Collaborative Filtering

Collaborative Filtering (CF) is an approach that suggests the item based on the

similarity between the users and/or the items. The algorithm of CF are divided into two

groups which are memory-based and model-based Collaborative Filtering (CF).

Memory-based CF algorithms will predict estimate the new ratings based on available

data, using similarity of other user or items to a target user/items. A group of similar

user to a target user or similar items to a target item is called their neighbor set which

is used to identify users/items with common rating history. While model-based CF

algorithms used different technique on training set to identify the patterns in the data

and learn a model for predicting new ratings. Model-based CF has so much techniques

can be used compared to memory-based CF, but even though there is a rich literature

on model-based CF, the algorithms have a very selective applicability in real scenarios

(Jalili et al., 2018).

10

2.4 Algorithm

2.4.1 RATING BASED ON DATE

M = Month of the rating given

C = Current Month

R = Rating

Total = __________________________

Example:

(The current month is June)

Table 2.2 Example calculation of rating based on date

Month Customer

Rating

Shop A Shop B Shop C

January Customer 1 3 4 5

February Customer 2 2 - 4

March Customer 3 4 - 4

April Customer 4 3 - 4

May Customer 5 3 - 5

June Customer 6 3 - 5

Total Rating 1.95 0.67 2.67

∑ (M/C)*R

Number of ratings

11

2.4.2 RATING BASED ON AVERAGE

Total Average = ________________________

Example:

(The current month is June)

Table 2.3 Example calculation of rating based on average

Month Customer

Rating

Shop A Shop B Shop C

January Customer 1 3 4 5

February Customer 2 2 - 4

March Customer 3 4 - 4

April Customer 4 3 - 4

May Customer 5 3 - 5

June Customer 6 4 - 5

Sum of Rating 19/6 4/1 27/6

Total Rating 3.17 4 4.5

Sum of all ratings

Number of ratings

12

2.4.2.1 Calculation for Shop A

Table 2.4 shows the rating calculation for Shop A.

Table 2.4 Rating calculation for Shop A

Month Customer Calculation

Rating by average

Rating based

on date

Shop A Shop A

January Customer 1 (1/6)*3 = 0.5 3 3

February Customer 2 (2/6)*2 = 0.67 2 2

March Customer 3 (3/6)*4 = 2 4 4

April Customer 4 (4/6)*3 = 2 3 3

May Customer 5 (5/6)*3 = 2.5 3 3

June Customer 6 (6/6)*4 = 4 4 4

Sum of ratings 19/6 11.67/6

Total average 3.17 1.95

13

2.4.2.2 Calculation for Shop B

Table 2.5 shows the rating calculation for Shop B.

Table 2.5 Rating calculation for Shop B

Month Customer Calculation

Rating by average

Rating based

on date

Shop B Shop B

January Customer 1 (1/6)*4 = 0.67 4 4

February Customer 2 - - -

March Customer 3 - - -

April Customer 4 - - -

May Customer 5 - - -

June Customer 6 - - -

Sum of ratings 4 0.67

Total average 4 0.67

14

2.4.2.3 Calculation for Shop C

Table 2.6 shows the rating calculation for Shop C.

Table 2.6 Rating calculation for Shop C

Month Customer Calculation

Rating by average

Rating based

on date

Shop C Shop C

January Customer 1 (1/6)*5 = 0.83 5 5

February Customer 2 (2/6)*4 = 1.33 4 4

March Customer 3 (3/6)*4 = 2 4 4

April Customer 4 (4/6)*4 = 2.67 4 4

May Customer 5 (5/6)*5 = 4.17 5 5

June Customer 6 (6/6)*5 = 5 5 5

Sum of ratings 27/6 16/6

Total average 4.5 2.67

15

2.5 Research on Existing System

2.5.1 TripAdvisor Website

Figure 2.1 shows the image of TripAdvisor website.

Figure 2.1 TripAdvisor Website

Table 2.7 shows the details of TripAdvisor website.

Table 2.7 Advantages and disadvantages of TripAdvisor website

Description Advantages Disadvantages

This website focused on

finding shop based on

their location. It also have

choices based on type of

the shop.

Can give and see the

reviews and ratings for

each shop.

Not all the shop have

reviews and ratings.

Shows other attraction

nearby and activities

that can be done

within the area.

Only two filters

available for shop

section.

16

2.5.2 Tiendeo Website

Figure 2.2 shows the image of Tiendeo website.

Figure 2.2 Tiendeo Website

Table 2.8 shows the details of Tiendeo website.

Table 2.8 Advantages and disadvantages of Tiendeo website

Description Advantages Disadvantages

This website focused on

finding shop based on

their location.

Can find the nearest

shop.

Cannot filter the result

such as budget and

ratings.

Can view catalogs for

each shop.

Only available for

well-known

department store,

supermarkets and

brands.

17

2.5.3 Google Maps Website

Figure 2.3 shows the image of Google Maps website.

Figure 2.3 Google Maps

Table 2.9 shows the details of Google Maps website.

Table 2.9 Advantages and disadvantages of Google Maps

Description Advantages Disadvantages

This website focused on

finding shop based on

their location.

Can find the nearest

shop.

Some of the location

for the shop are not

accurate.

Can choose the best

shop based on the

ratings given.

The filter of the shop

result is so limited.

Cannot choose budget

or items preferred.

18

2.6 Conclusion

In this chapter, the technique and approach to be used in the system is studied

and a few collection of literature review has been done. By studying this chapter, few

information has been acquired that can help to develop a good and functioning system.

On the other hand, literature review also helps to gain knowledge about technique and

past systems that has been used in previous research.

19

CHAPTER 3

METHODOLOGY

3.1 Introduction

In this chapter, the methodology used for the system development will be

discussed. Methodology refers to the overarching strategy and rationale of the project.

There are many type of software development methodologies that are mainly used such

as Agile Software Development Methodology, Waterfall Model, Spiral Model and

Scrum Development Model. And the proposed system use Agile Methodology as a

guide to develop the system.

3.2 Agile Methodology

Agile methodology is used to build Infinity Vendor System. Agile methodology

is a type of project management process, mainly used for software development that

promotes continuous iteration of development and testing throughout the software

development lifecycle of the project. There are six stages of agile method which is

requirement, design, development, testing, deployment and review phase.

20

Figure 3.1 Figure of Agile methodology

3.2.1 Requirement Phase

In requirement phase, after the title of project, which is Infinity Vendor System

has been selected, the initial documentation that will list all of the requirements needed

to design and develop the new system need to be created. The Gantt Chart also needed

as a guideline and references while developing the project. Based on the findings from

articles, techniques and method that is suitable for the project has been decided.

3.2.2 Design Phase

In this phase, the development team will discuss on how to tackle all the

requirements created during the previous stage. All the requirements obtained during

the previous phase are transformed into the design. Diagrams to show the flow of the

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

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

designed also as a guidance throughout developing the system.

21

3.2.3 Development Phase

This phase is about writing code and converting the design into the actual

software within the software development process. To develop the proposed system

using collaborative filtering, the system will be using Xampp server for database,

Bootstrap, PHP and Notepad++ language to code. Development phase is a critical phase

because user part need to be fulfilled and to make sure the objectives of this system

accomplish. This phase also will take the longest time since it is the backbone of the

whole process.

3.2.4 Testing Phase

After the development phase has been done, Infinity Vendor System will be test

to make sure that the system is bug-free and to ensure that the function run well as a

whole system. Any error or bugs will be fixed and testing will be repeated until all the

functions work well.

3.2.5 Deployment Phase

This phase is where the system is deployed on the servers and is ready to be used

by the users. The system will finally be provided to the user either for the demo or actual

use of the system.

3.2.6 Review Phase

After all the previous development phases are completed, this phase is where all

the feedbacks and reviews from the user will be accepted and for the maintenance and

the feedbacks used to work it into the requirements of the next iteration.

22

3.3 Project Requirement

In developing a system, system requirements is needed to achieve and assist the

development of the project. There are two requirements needed which is software

requirement and hardware requirement. All these are important to ensure the

development of the project went well and it is also important for future references. List

of software and hardware requirements are shown below:

3.3.1 Software Requirement

Table 3.1 shows the software requirement for the proposed system.

Table 3.1 Software Requirement

No Software Description

1 Microsoft Office Word 2013 Platform for documentation of the report.

2 Notepad++ Source code editor used to code the program.

3 PHP

Scripting language to be used for web

development.

4 Bootstrap CSS Framework to develop system.

5 Draw.io Diagrams Tool to create and design CD, DFD and ERD.

6 XAMPP Server Server to run localhost.

7 MYSQL database For system database.

8 Google Chrome

Browser to run localhost and search for

information needed.

9 Google Drive Cloud storage to back up all the documents.

23

3.3.2 Hardware Requirement

Table 3.2 shows the hardware requirement for the proposed system.

Table 3.2 Hardware requirement

No Hardware Description

1 Laptop Asus ZenBook UX305CA

2 Processor Intel(R) Core(TM) m3-6Y30 CPU @

0.90GHz 1.51 GHz

3 Random Access Memory (RAM) 4.00 GB

4 Operating System Windows 10

5 System Type 64-bit Operating System

6 Thumb drive Kingston 64GB

3.4 Framework Design

Figure 3.2 shows the framework of Infinity Vendor System. The design shows

the flow process of what the users can do with the system. The customer can search

shop, get the shop details and give ratings to the system. While admin can update shop

details to the system. The small business owner also can update the shop details, add

shop and add goods details.

24

Figure 3.2 Framework Design

3.5 System Design and Modelling

The flow of the system is organized in order to make the development process

smoother. The representation of data are called conceptual data modelling used to

display data structure. Based on the Infinity Vendor System, Context Diagram (CD)

and Data Flow Diagram (DFD) shows the physical design of the system while Entity

Relationship Diagram (ERD) is the logical design of the system.

25

3.5.1 Context Diagram (CD)

Figure 3.3 shows the Context Diagram of Infinity Vendor System. This system

consists of three entities which are Admin, Customer and Business Owner. Admin can

view customer and owner information. Admin also can delete shop and goods

information. While customer will able to update their data, get shop and goods

information and also give rating to the shop. Lastly, the small business owner can update

their data as well as the shop and goods details. Business owner also can view shop

rating from customer.

Figure 3.3 Context Diagram

3.5.2 Data Flow Diagram (DFD)

3.5.2.1 DFD Level 1

Figure 3.4 shows the DFD for the Infinity Vendor System. This system used

three entities and four processes in DFD Level 1. The three entities are Admin,

Customer and Business Owner while four processes are Login, Manage Shop, Manage

Rating and Manage Goods. All the processed data will be stored in the data stores

provided which are Admin, Customer, Business Owner, Shop, Rating and Goods.

26

Figure 3.4 Data Flow Diagram Level 1

3.5.2.2 DFD Level 2

Data Flow Diagram (DFD) Level 2 will show the details of the process that

involves in manage goods, manage shop, search shop and search goods.

3.5.2.3 Manage Goods

Figure 3.5 shows the details of the flow for the process of managing goods.

Business owner can add goods, delete goods and update goods details. While Admin

can only delete goods.

27

Figure 3.5 Data Flow Diagram Level 2 Manage Goods

3.5.2.4 Manage Shop

Figure 3.6 shows the DFD level 2 for manage shop. Business owner can add

shop, delete shop and update shop details. While admin can only delete shop.

Figure 3.6 Data Flow Diagram Level 2 Manage Shop

3.5.2.5 Search Shop

Figure 3.7 shows the DFD level 2 for search shop. Customer can browse shop

and they will get the shop suggestions from the system.

28

Figure 3.7 Data Flow Diagram Level 2 Search Shop

3.5.2.6 Search Goods

Figure 3.8 shows the DFD level 2 for search goods. Customer can browse goods

and they will get the goods suggestions from the system.

Figure 3.8 Data Flow Diagram Level 2 Search Goods

3.5.3 Entity Relationship Diagram (ERD)

Entity Relationship Diagram (ERD) which also known as entity relationship

model is a type of structural diagram to be used in database design. ERD is one of

representative diagram that shows the relationship between entities in the system. There

are six tables in this system which are Admin, Business Owner, Customer, Shop, Goods

and Rating. The ERD for Infinity Vendor System is shown in Figure 3.9 below:

29

Figure 3.9 Entity Relationship Diagram

Figure 3.10 shows the ERD model of the proposed system.

Figure 3.10 Entity Relationship Diagram Model

30

3.6 Data Dictionary

Data dictionary is a set of database tables that are used to store information and

contains database metadata. It also contains records about the object in the database

such as data relationship. The database management system needs the data dictionary

in order to access the data within the database.

3.6.1 Overall System Database

Table 3.3 shows the overall database for Infinity Vendor System that have six

tables which are iv_admin, iv_customer, iv_goods, iv_owner, iv_rating and iv_shop.

Table 3.3 Table for overall system

3.6.2 Table Admin

Table 3.4 shows the table for admin of the system. This table is used to store the

information of admin that only have two attributes which are adminID and password.

31

Table 3.4 Table for admin

3.6.3 Table Customer

Table 3.5 shows the table for customer. This table is used to store the

information of customer. This table have six attributes which are cust_ID,

cust_username, password, cust_name, cust_phone and cust_email.

Table 3.5 Table for customer

3.6.4 Table Goods

Table 3.6 shows the table for goods in the Infinity Vendor System database. This

table is used to store the information of goods. This table have six attributes which are

goods_ID, shop_ID, goods_name, goods_categories, goods_price and goods_image.

32

Table 3.6 Table for goods

3.6.5 Table Business Owner

Table 3.7 shows the table for business owner in the Infinity Vendor System

database. This table is used to store the information of business owner. This table have

five attributes which are owner_ID, owner_username, password, owner_phone and

owner_email.

Table 3.7 Table for business owner

3.6.6 Table Rating

Table 3.8 shows the table for rating. This table is used to store the information of the

ratings given by the customer. This table have nine attributes which are rating_ID,

cust_ID, shop_ID, rating_title, date_create, date_modify, rating_comment,

rating_number and rating_status.

33

Table 3.8 Table for rating

3.6.7 Table Shop

Table 3.9 shows the table for shop in the Infinity Vendor System database. This

table is used to store the information of the shop. This table have nine attributes which

are shop_ID, owner_ID, shop_name, shop_phone, shop_address, shop_image, shop_fb,

shop_shopee and shop_ig.

Table 3.9 Table for shop

34

3.7 Summary

To sum up, methodology is very important in order to make sure the

development of the proposed system done within the time provided. This chapter has

briefly explained the methodology used in this project. The agile method is used to

develop Infinity Vendor System. This chapter also mentioned what are the software and

hardware requirements needed to achieve the objective of this project. Lastly, the

explanation of context diagram (CD), data flow diagram (DFD), entity relationship

diagram (ERD) and database are included in this methodology chapter.

35

REFERENCES

Bjerkan, K. Y., Bjørgen, A., & Hjelkrem, O. A. (2020). E-commerce and prevalence

of last mile practices. Transportation Research Procedia, 46, 293–300.

https://doi.org/10.1016/j.trpro.2020.03.193

Haryanti, T., & Pribadi, A. (2019). E-commerce service design readiness using ITIL

framework with IT balanced scorecard objective (Case Study: University e-

Commerce). Procedia Computer Science, 161, 283–290.

https://doi.org/10.1016/j.procs.2019.11.125

Hurtado, P. A., Dorneles, C., & Frazzon, E. (2019). Big Data application for E-

commerce’s Logistics: A research assessment and conceptual model. IFAC-

PapersOnLine, 52(13), 838–843. https://doi.org/10.1016/j.ifacol.2019.11.234

Jalili, M., Ahmadian, S., Izadi, M., Moradi, P., & Salehi, M. (2018). Evaluating

Collaborative Filtering Recommender Algorithms: A Survey. IEEE Access, 6,

74003–74024. https://doi.org/10.1109/ACCESS.2018.2883742

Nápoles, G., Grau, I., & Salgueiro, Y. (2020). Recommender system using Long-term

Cognitive Networks. Knowledge-Based Systems, 206, 106372.

https://doi.org/10.1016/j.knosys.2020.106372

Parveen, N., Santhi, M. V. B. T., Ramani Burra, L., Pellakuri, V., & Pellakuri, H.

(2021). Women’s e-commerce clothing sentiment analysis by probabilistic model

LDA using R-SPARK. Materials Today: Proceedings, 4.

https://doi.org/10.1016/j.matpr.2020.10.064

Tolstoy, D., Nordman, E. R., Hånell, S. M., & Özbek, N. (2020). The development of

international e-commerce in retail SMEs: An effectuation perspective. Journal of

World Business, 101165. https://doi.org/10.1016/j.jwb.2020.101165