i

EVENT PLANNING SUGGESTION SYSTEM

NURUL NAJWA BINTI AWANG HARUN

BACHELOR OF COMPUTER SCIENCE

(SOFTWARE DEVELOPMENT)

UNIVERSITI SULTAN ZAINAL ABIDIN

2018

ii

DECLARATION

I hereby declare 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 : Nurul Najwa binti Awang Harun

Date :

iii

CONFIRMATION

This is to confirm that:

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

Name : Pn Nor Surayati binti Mohamad Usop

Date :

iv

DEDICATION

In the name of Allah the most Gracious and the most Merciful

Firstly, Alhamdulillah, all thanks to Allah for giving me the chance, strength and ability to

complete this final year project in time. Without His permission, I would not be able to

complete and handle this project properly. I would like to express my gratitude to those who

have helped me whether directly or indirectly. Special thanks to my dedicated supervisor,

Puan Nor Surayati binti Mohamad Usop for her guidance, ideas, comments and

encouragement throughout the whole process in completing this final year project in time that

had led me to produce project with good quality. My personal gratitude goes to my parents

and all my family members for all of the moral supports and understanding that they gave to

me. Finally, I would like to this chance and opportunity to thanks my friends who always

willing to help and support me through this journey to done this project. May Allah S.W.T

repays them with great reward for their generosity.

v

ABSTRACT

Mostly event are to be done for celebrating a special occasion. To prepare for such an

event requires a lot of works and stuff to buy. Even so, each people would have different

events and budgets that need to be considered before making the event. The problem was

people sometimes getting into the over-budget situation and to avoid doing so, they have to

going through from one to another event planner just to have the best possible price.

However, if user using the suitable and helpful system, it will be able to help them

manage their financial well and their budget will not exceed. By using the system also, they

will be able to cut more time rather than comparing one by one services and packages

manually.

For developing the system, rule-based technique which is backward chaining will be

used to suggest the possible event packages for the user to pick based on their event type and

budget range. This technique is possibly the best method to use as the goal is given in the

problem statement, or can sensibly be guessed at the beginning of the consultation. And for

this system, user needs to select the event and budget range first before the system will

automatically direct user to the packages and services available based on the chosen budget.

vi

ABSTRAK

Kebanyakan acara diadakan untuk sambutan yang istimewa. Untuk menyediakan

acara tersebut memerlukan banyak kerja dan barang-barangan untuk dibeli. Demikian pula,

setiap orang mempunyai acara dan bajet yang berlainan yang perlu diambil kira sebelum

membuat sesuatu acara. Permasalahannya adalah kadang-kadang seseorang akan

mengalami situasi melebihi bajet dan untuk mengelaknya, mereka perlu merujuk daripada

satu kepada satu pengaturcara yang lain untuk mendapatkan harga yang terbaik.

Walaupun begitu, jika pengguna menggunakan system yang sesuai dan membantu, ia

akan dapat membantu mereka untuk mengurus kewangan mereka dengan baik dan bajet

mereka akan cukup. Dengan menggunakan system tersebut juga, mereka dapat menjimatkan

masa daripada membandingkan setiap satu servis dan pakej secara manual.

Untuk membangunkan sistem ini, teknik rule-based iaitu backward chaining telah

diaplikasikan untuk mencadangkan pakej acara terbaik untuk dipilih oleh pengguna

berdasarkan jenis acara dan lingkungan bajet. Teknik ini mungkin merupakan metod terbaik

untuk digunakan kerana tujuan yang diberikan dalam pernyataan masalah, atau boleh

secara bijak diteka diawal konsultasi. Untuk sistem pula, pengguna perlu memilih acara dan

lingkungan bajet dahulu sebelum sistem akan secara automatik mengarahkan pengguna

kepada pakej-pakej dan servis-servis yang terdapat berdasarkan pilihan bajet.

vii

TABLE OF CONTENTS

Contents Pages

DECLARATION .................................................................................................................................... ii

CONFIRMATION ................................................................................................................................. iii

DEDICATION ....................................................................................................................................... iv

ABSTRACT ............................................................................................................................................ v

ABSTRAK ............................................................................................................................................. vi

TABLE OF CONTENTS ...................................................................................................................... vii

CHAPTER I ............................................................................................................................................ 1

INTRODUCTION .............................................................................................................................. 1

1.1 Background ......................................................................................................................... 1

1.2 Problem Statement .............................................................................................................. 2

1.3 Objectives ........................................................................................................................... 3

1.4 Scope ................................................................................................................................... 3

1.5 Limitation of Works ............................................................................................................ 4

1.6 Expected Outcome .............................................................................................................. 5

1.7 Project Planning .................................................................................................................. 6

CHAPTER II ........................................................................................................................................... 7

LITERATURE REVIEW ................................................................................................................... 7

2.1 Introduction ......................................................................................................................... 7

2.2 Proposed System ................................................................................................................. 7

2.3 Rule Based Technique (Backward Chaining) ..................................................................... 8

2.4 Comparison Table of Existing System ................................................................................ 9

2.5 Conclusion ........................................................................................................................ 10

viii

CHAPTER III ....................................................................................................................................... 11

METHODOLOGY ........................................................................................................................... 11

3.1 Introduction ....................................................................................................................... 11

3.2 Justification Selection ....................................................................................................... 12

3.3 Methodology ..................................................................................................................... 13

3.4 System Requirement ......................................................................................................... 15

3.5 Framework ........................................................................................................................ 16

3.6 Context Diagram ............................................................................................................... 18

3.7 DFD Level 0 ..................................................................................................................... 19

3.8 DFD LEVEL 1 .................................................................................................................. 21

3.9 Entity Relation Diagram ................................................................................................... 26

CHAPTER IV ....................................................................................................................................... 27

IMPLEMENTATION AND TESTING ............................................................................................ 27

4.1 INTRODUCTION .................................................................................................................. 27

4.2 IMPLEMENTATION AND OUTPUT............................................................................. 28

CONCLUSION ..................................................................................................................................... 34

REFERENCES ..................................................................................................................................... 35

1

CHAPTER I

INTRODUCTION

1.1 Background

Based on my findings on the Internet, it is found that most of the current existing

Event Planning System does not consist and provide the budget estimation for the event.

Mostly, the system will started with the planning first then the budget. This sometime causes

the client to have the over-budget situation. To avoid that situation, we have come out with a

system that offers a platform for client to choose their own budget range as well other

services and product. This proposed system will help event planner to assist client in decision

making based on their preferred services and product but still in their selected budget range.

They can also manage the event smoothly without any budget shortened problem. This

project is useful to cut user’s time in event planning with only simple click of a mouse.

Event Planning Suggestion System is able to solve problems such as time constraints

and over-budget used. This system will use Rule Based Technique because it provides the

simplest and most understandable way of expressing knowledge.

As for conclusion, Event Planning Suggestion System will be a good solution in

solving real life problems and makes the user life easier and simpler.

2

1.2 Problem Statement

There are some problems faced by the client who are intended to plan an event which are:

i) Most people do not have any experience in planning and handling an event.

- Event planning itself is not an easy thing. Many aspects need to be considered

when planning the event such as budgeting, scheduling, site selection,

arranging decor, event security, catering, and emergency plans.

- By this Event Planning Suggestion System is going to be built to help and ease

the customer to search about their planning stuff using the online application

ii) People sometimes getting into the over-budget situation while planning the event.

- People sometimes already set their own budget range but at the same time

since there are many things to buy and to have, they often went into the over-

budget situation.

- They also tend to compare many sites and stores just to have the best possible

price for the things needed in an event.

- With this system, just by choosing the budget range, the system will

automatically display all the services and packages available based on the

range.

iii) The current system does not provide a decision making process on event budget.

- With the proposed system, the client will be able to manage their financial

effectively and efficiently.

3

1.3 Objectives

The objectives of Event Planning Suggestion System are:

i. To design a web based system for Event Planning Suggestion System that helps user

to plan their event successfully without over budget situation.

ii. To develop a system that assist user to make the best and suitable judgement for

planning birthday and anniversary.

iii. To evaluate a system using Rule-Based Technique which is backward chaining where

this technique working from the conclusion to the facts.

1.4 Scope

There are main actors which are the event planner and client.

1.4.1 Scope of the User

i) Admin

- Able to log in as admin

- Able to manage user

- Able to manage birthday and anniversary

- Able to manage budget range provided for user

- Able to manage packages for the client to choose based on their selected

budget range

- Able to manage event companies

- Able to manage security and maintenance of the system

4

ii) Client

- Able to select events whether birthday and anniversary

- Able to select budget range provided by the system

- Able to choose packages available in any event companies that is registered

with the system based on budget range selected

1.4.2 Scope of the System

In this Event Planning Suggestion System, user needs to select the events they desire

to hold which is birthday or anniversary. Then, they need to choose the budget range. After

user selects their desired budget range, the system will automatically display the list of

companies that offer packages available based on the selected budget range. Then, the system

will display all the services that can be choose by the client and generate report based on it.

1.5 Limitation of Works

- The system only provides two types of event which are birthday/anniversary

and family event only.

- The system will only allow customer to view the packages based on the

budget range that they have selected.

- If the user willing to book the package, they need to deal directly with the

event company as the system only will give notification to the said event

company.

5

1.6 Expected Outcome

This project aims to:

- Suggest and recommend the event packages and services based on the budget

range selected by the user.

- Assist the client and event planner to manage and organize their event wisely.

- Functioning with full functionality and meets the specified user’s requirement.

6

1.7 Project Planning

ACTIVITY

WEEK

01 02 03 04 05 06 07 08 09 10 11 12 13 14 15

1. Project Title Discussion and Briefing

2. Project Title Registration

3. Proposal Writing Chapter 1: Introduction

4. Proposal Writing Chapter 2: Literature

Review

5. Proposal Progress Presentation and

Evaluation

6. Correction of the Proposal

7. Proposed solution – Chapter 3: Methodology

8. Proof of Concept

9. Seminar Preparation

10. Seminar Presentation and Evaluation

11. Finalizing Report of the Proposal

12. Final Report Submission and Evaluation

7

CHAPTER II

LITERATURE REVIEW

2.1 Introduction

This chapter discussed simple summary of the some sources, in which was reviewed

before developing a certain system. It gives me a new interpretation of old materials related

directly and indirectly to the Event Planning System or it might trace the intellectual

progression of the field, including major debates. By this literature review, I had summarized,

compared and evaluated all those researches.

2.2 Proposed System

. An event planner is someone who coordinates and organizes all aspects of business

meetings and events. The process of planning and organizing the event is normally referred to

as event planning and which can include budgeting, scheduling, site selection, arranging

décor, event security, catering, and emergency plans. Each event is different in its nature so

process of planning & accomplishment of each event varies on basis of type of event. To

organize an event, a specified budget must be considered and measured before the event is

planned and held.

Event Planning Suggestions System is developed using rule based technique which

usually used to support decision making classification.

8

2.3 Rule Based Technique (Backward Chaining)

Backward chaining is opposite to the forward chaining, and begins from the goal and

tries to find data to prove its goal. Thus, it is also called a goal-driven reasoning. After

beginning from the given goal, the search of THEN parts of the given rules (action part)

(RHS) is conducted, and if the rule is found and its IF part matches the data in the database,

then the rule is executed. Otherwise, if the condition does not match the data in the database,

the inference engine sets the rule that is working on a stack and makes a new sub goal to

prove the condition in the current rule. The knowledge base keeps looking for rules to prove

the sub goal. The process of stacking the rules is repeated until the knowledge base has no

rules to prove the sub goal.

Backward chaining concept is used to develop many types of expert systems, and

especially the interactive systems simulate conversion between users and an expert person.

Using backward chaining technique, the system will know what to ask and when to ask the

appropriate question. It helps to disassemble the complex problem into easy, small, fixed

sections, and the system use them automatically if needed.

In this system, the client needs to select or choose his/her wanted budget range. Then,

the system will display the packages and services to compatible with the price and budget

that they have.

9

2.4 Comparison Table of Existing System

Author / Year Project Title Method /

Technique

System

Description

Advantages Disadvantages

Robin van

Meteran,

Maarteen van

Someren

University of

Amsterdam

Personalized

Recommender

System

(PRES)

Content-

Based

Filtering

-This

system is to

create

associations

between

items in a

collection

-When a

user shows

a preference

for specific

item, the

system will

compare

those other

items

The items will be

recommended

based on a much

larger range of

aspects than

searching would

allow

Limited content

analysis

Siti Azmira binti

Azmi

2015

Development

of E-Faraid

System by

Using Rule

Based

Rule Based This system

provides

systematic

calculation

based on

Quran,

Hadith and

rules of

Shafie.

The system will

automatically

calculate faraid

based on the rule

that already

generated in which

user had given

details such as

deceased detail,

total deceased

property and list of

heir

The range or

amount from the

calculation might

not be the exact

amount but it can

be self-reference

before user get

the real result

10

Wan Nur Ain

binti Wan Abdul

Hadi

2017

Wedding

Planning

Suggestion

System

Rule Based

Technique

Users are

required to

choose

budget

range first

so that the

system will

display the

next service

and option.

After selecting the

budget range

desired, the system

will automatically

display the

packages and

services which

only suit the range.

This system is

not developed for

booking that if

the customers are

interested, they

had to call or

send messages

through

“COMMENT”

section.

2.5 Conclusion

In this chapter, technique to be used is studied and a few collection of literature

review has been done. By this, knowledges have been gain to help to develop a good and

functioning system. By literature review also helps to gain knowledge about techniques and

past systems that has been used in previous research.

11

CHAPTER III

METHODOLOGY

3.1 Introduction

In this chapter, the methodology in this system development will be discussed.

Methodology is a defined combination of logically related practices, methods and processes

that determine how best to design, develop, and deliver a project throughout the continuous

implementation process until successful completion and termination. It is a scientifically-

proven, systematic and disciplined approach to project design, execution and completion. The

project methodology should be organized in a scientific investigation to solve problems to

make sure this project achieves the objective and target.

12

3.2 Justification Selection

This project implement waterfall model. Since this project is smaller scale of project and

takes only shorter time to complete, waterfall model was chosen. This model is a sequential

design process that often used in software development process because of it is easy to

understand and easy to use. The phases of the project in this type of model flow downward.

The model requires that you move from one phase to another only once that phase has been

successfully completed. The figure below show the phase involve in conducting the research.

Usually, there are five phases in this model, which are;

i) Requirement definition

ii) System and software design

iii) Implementation and unit testing

iv) Integration and system testing

v) Operational maintenance

Figure 3.1: Waterfall Model

13

3.3 Methodology

These are the phases that involved in development system in waterfall model and also

the descriptions.

i) Requirement definition

In this phase, the system requirements have been collected and analyzed. The

problem statements, objectives, scopes and technique to be used have been

defined. This help to understand more about the system that will be developed. In

this phase also, information about event planning system is collected. This

includes reviewing the existing system which similar to the proposed system,

articles and journal revising and interviewing expert with event planning was

conducted. After all data being collected, the data will be analyzed to get

requirement of the system.

ii) System and software design

In system and software design phase, flow of the processing is developed into

chart, and most logical data flow and storage are determined. Data flow diagram

(DFD) and Entity Relationship Diagram (ERD) that visualize the process flow

developed.

iii) Implementation and unit testing

For the implementation and unit testing phase, the plan laid out in the system

design phase is executed. The system is mainly implemented in PHP language. At

this phase, real data will be used to make sure all result show as expected.

14

iv) Integration and system testing

During the test phase, each module will be testing to make sure that the

process runs correctly. After testing, all modules must combine in one system.

This is to make sure process between modules run correctly. Essentially, the key

elements of testing phase are to verify that the system contains all the end user

requirements laid out in analysis phase.

v) Operational maintenance

This step occurs after installation, and involves making modifications to the

system or an individual component to alter attributes or improve performance.

These modifications arises either changes requests or defects uncovered during

live use of the system.

15

3.4 System Requirement

3.4.1 Software Requirement

Type of Software Description

Google Chrome Used to do research on the project and to run

the project

PHP Language used to develop the system

Adobe Dreamweaver CS6 Used to develop interface system

MySQL Database Used as a database system

ClickChart Diagram Flowchart Software Used to draw CD and DFD model

MySQL Workbench 5.2 CE Used for reverse engineering of the database

Microsoft Office 2010 As a platform for documentation

Table 3.4.1: List of software

3.4.2 Hardware Requirement

Type of Hardware Description

Laptop Processor: Intel Core i5

RAM: 4.00 GB

OS: 64 bit

Hard disk 1.0 TB

Used as a backup for the data and system

Pendrive 8.00 GB

Used as a backup for the data and system

Table 3.4.2: List of hardware

16

3.5 Framework

Figure 3.5 : Framework for Event Planning Suggestion System

17

Description:

Framework is basically a broad overview or outline of interlinked items which

supports a particular approach to a specific objective, and serves as a guide that can be

modified as required by adding or deleting items. In the Event Planning Suggestion System,

there are only two users which are Admin and Client.

Admin needs to login first before using the system. After successfully login, the

admin will be directed to their designed interface. Since the admin is to manage the system,

they will be able to add, update and delete the process in the system. They are also able to

manage their own profile.

To use this system, client or user needs to register and login first. Login is essential in

this system as user can do booking. After done login, user needs to choose the event that they

intended to do and the system only provides two events which are birthday and anniversary

event. Then, user has to select the budget range that the system displays. By the event and

budget range selected, the system will automatically display various packages that can be

chosen from different companies. User is given the button to book or they can just log out of

the system after choosing their intended package. When they choose to book, the system will

send the notification to the company.

18

3.6 Context Diagram

Figure 3.6: Context Diagram for Event Planning Suggestion System

Description:

Based on the figure 3.6 above, there are two actors in this Event Planning Suggestion System

which are ADMIN and CLIENT. The context diagram above display the flow between two

actors and what are they able to do in the system based on their roles. Client is able to insert

their own details during registration and login. Then, they can select the event, budget range

and packages provided by the system. Client can also select booking if they intended to book.

Meanwhile, Admin will be able to manage their profile and the information that the system

will display and also user’s information. Admin can also do report viewing.

19

3.7 DFD Level 0

Figure 3.7 DFD Level 0 for Event Planning Suggestion System

Description:

The DFD has two entities which are ADMIN and CLIENT. There are six processes involved

in the system which are MANAGE USER, MANAGE EVENT, MANAGE BUDGET

RANGE, MANAGE PACKAGES, MANAGE COMPANY, and GENERATE REPORT.

There are four data stores created in the system which are CLIENT RECORD, ADMIN

20

RECORD, PACKAGE RECORD, and COMPANY RECORD. The flow of the system is like

below:

1. CLIENT input CLIENT DETAILS into MANAGE USER process which outputs

CLIENT DETAILS into CLIENT data store.

2. CLIENT input EVENT SELECTION into MANAGE EVENT process which outputs

EVENT SELECTION into PACKAGE data store.

3. CLIENT input BUDGET RANGE SELECTION into MANAGE BUDGET RANGE

process which outputs BUDGET RANGE SELECTION into PACKAGE data store.

4. CLIENT input PACKAGES SELECTION into MANAGE PACKAGES process

which outputs PACKAGES SELECTION into PACKAGE data store.

5. ADMIN input ADMIN DETAILS into MANAGE USER process which outputs

ADMIN DETAILS into ADMIN data store.

6. ADMIN input EVENT DETAILS into MANAGE EVENT process which outputs

EVENT DETAILS into PACKAGE data store.

7. ADMIN input BUDGET RANGE DETAILS into MANAGE BUDGET RANGE

process which outputs BUDGET RANGE DETAILS into PACKAGE data store.

8. ADMIN input PACKAGES’ DETAILS into MANAGE PACKAGES process which

outputs PACKAGES’ DETAILS into PACKAGE data store.

9. ADMIN input COMPANY DETAILS into MANAGE COMPANY process which

outputs COMPANY DETAILS into COMPANY data store.

10. When ADMIN wants to view the reports, ADMIN INFO, CLIENT INFO,

PACKAGE INFO, and COMPANY INFO are taken from ADMIN, CLIENT,

PACKAGE, and COMPANY RECORDS data stores respectively into REPORT

process which outputs REPORT to ADMIN.

21

3.8 DFD LEVEL 1

3.8.1.1 Manage User (for client)

Figure 3.8.1.1: DFD Level 1 for Manage User (for client)

Description:

1. CLIENT input CLIENT DETAILS into REGISTER process which output CLIENT

DETAILS into CLIENT data store.

2. CLIENT input CLIENT DETAILS into LOGIN process which output CLIENT

DETAILS into CLIENT data store.

3. CLIENT input CLIENT DETAILS into UPDATE PROFILE process which output

CLIENT DETAILS into CLIENT data store.

22

3.8.1.2 Manage User (for admin)

Figure 3.8.1.2: DFD Level 1 for Manage User (for admin)

Description:

1. ADMIN input ADMIN DETAILS into LOGIN process which output ADMIN

DETAILS into ADMIN data store.

2. ADMIN input ADMIN DETAILS into UPDATE PROFILE process which output

ADMIN DETAILS into ADMIN data store.

23

3.8.2.1 Manage Package (for client)

Figure 3.8.2.1: DFD Level 1 for Manage Package (for client)

Description:

1. CLIENT input PACKAGE DETAILS into VIEW PACKAGE process which output

PACKAGE DETAILS into PACKAGE data store.

2. CLIENT input PACKAGE DETAILS into SELECT PACKAGE process which

output PACKAGE DETAILS into PACKAGE data store.

24

3.8.2.2 Manage Package (for admin)

Figure 3.8.2.2: DFD Level 1 for Manage Package (for admin)

Description:

1. ADMIN input PACKAGE DETAILS into ADD PACKAGE process which output

PACKAGE DETAILS into PACKAGE data store.

2. ADMIN input PACKAGE DETAILS into UPDATE PACKAGE process which

output PACKAGE DETAILS into PACKAGE data store.

3. ADMIN input PACKAGE DETAILS into DELETE PACKAGE process which

output PACKAGE DETAILS into PACKAGE data store.

25

3.8.3 Manage Company (for admin)

Figure 3.8.3: DFD Level 1 for Manage Company (for admin)

Description:

1. ADMIN input COMPANY DETAILS into ADD COMPANY process which output

COMPANY DETAILS into COMPANY data store.

2. ADMIN input COMPANY DETAILS into UPDATE COMPANY process which

output COMPANY DETAILS into COMPANY data store.

3. ADMIN input COMPANY DETAILS into DELETE COMPANY process which

output COMPANY DETAILS into COMPANY data store.

26

3.9 Entity Relation Diagram

Figure 3.9: ERD for Event Planning Suggestion System

An entity relationship diagram (ERD), also known as an entity relationship model, is a

graphical representation of an information system that shows the relationships among people,

objects, places, concepts or events within that system.

27

CHAPTER IV

IMPLEMENTATION AND TESTING

4.1 INTRODUCTION

In this chapter, the implementation and testing of the system will be described. During

implementation, the system is developed. Project developers begin building and coding the

software. While in testing, this phase includes detection of errors in the system. Also, in this

chapter, interface of the system will assist user to understand the system.

28

4.2 IMPLEMENTATION AND OUTPUT

4.2.1 Database Design

Database is a structured set of data held in a computer, especially one that is

accessible in various ways. So basically, database is needed to hold all the data needed in the

system.

4.2.1.1 Event Planning Suggestion System Database

Figure 4.2.1.1: Tables in the Event Planning Suggestion System Database

There are six tables in the database which are Admin, Booking, Client, Company, Package

and User. For each table, there are attributes at every column.

29

4.2.1.2 Table Admin

Figure 4.2.1.2: Table Admin

Table Admin contain adminID, name, ID, address, email, noTel. In this table, adminID is a

primary key and not null.

4.2.1.3 Table Booking

Figure 4.2.1.3: Table Booking

Table Booking contains bookingID, custID, packageID, and status. In this table, bookingID is

a primary key and not null. custID is foreign key reference to Table Client while packageID

is foreign key reference to Table Package.

30

4.2.1.4 Table Client

Figure 4.2.1.4: Table Client

Table Client contains custID, custName, gender, custAddress, email and noTel. In this table,

custID is a primary key and not null.

4.2.1.5 Table Company

Figure 4.2.1.5: Table Company

Table Company contains companyID, comName, noPhone, noFax, address, and adminID. In

this table, companyID is a primary key and not null. adminID is foreign key reference to

Table Admin.

31

4.2.1.6 Table Package

Figure 4.2.1.6: Table Package

Table Package contains packageID, pDetails, companyID, budgetRange, and event. In this

table, packageID is a primary key and not null. companyID is foreign key reference to Table

Company.

4.2.1.7 Table User

Figure 4.2.1.7: Table User

Table User contains only two attributes which are username, and password. In this table,

username is a primary key and not null. username is also foreign key reference to Table

Admin (adminID) and Client (custID).

32

4.2.2 Interface Design

Figure 4.2.2.1 Login interface

This interface is where all users login into the system. There are two users in this system,

which are Admin and Client. For Admin, they need to enter adminID while Client need to

enter custID. Both are also required to enter password as well. If not a member, client needs

to click on the link “Register Now” to sign up as a new member.

33

Figure 4.2.2.2 Event selection interface

User will be directed to this page after they login into the system. They need to choose

between those two events first before continuing to the next page.

Figure 4.2.2.3 Budget range selection interface

In this page, user need to select budget range of the event that they already selected. This

selection will determine which packages is suitable with the budget. The packages come from

different companies.

34

CONCLUSION

As the conclusion, Event Planning Recommendation System will be implemented using the

rule based technique. As the technique is to find the goal first before anything else, it proves that this

method is the most suitable in order to develop this system. This system will help users to achieve

their goals, as in this system which is budget. So when the users already had their budget set, the

event planning will comes easy as well. However, this system only functioning in suggesting, so the

users need to deal with their desired event planning company by themselves.

So, hopefully this Event Planning Suggestion System can solve headache in managing the

event planning budget in short amount of time and various packages to be offered. Other than that,

implementation of this system can help event planning companies to widen their business by online

web system.

35

REFERENCES

1. SITI AZMIRA BINTI AZMI. 2015. Development of E-Faraid System by Using Rule

Based. University Sultan Zainal Abidin.

2. WAN NUR AIN BINTI WAN ABDUL HADI. 2017. Wedding Planning Suggestion

System. University Sultan Zainal Abidin.

3. Inferencing in Rule Based Systems: Forward and Backward Chaining. Retrieve from

http://lecturer.ukdw.ac.id/jokop/wp-content/uploads/2011/6-

7Penalaran%20pada%20Inference%20Engine2.pdf

Accessed on February 2018

4. ROBIN VAN METEREN, MAARTEN VAN SOMEREN. Using Content-Based

Filtering for Recommendation. University of Amsterdam

http://lecturer.ukdw.ac.id/jokop/wp-content/uploads/2011/6-7Penalaran%20pada%20Inference%20Engine2.pdfhttp://lecturer.ukdw.ac.id/jokop/wp-content/uploads/2011/6-7Penalaran%20pada%20Inference%20Engine2.pdf