EVENT PLANNING SUGGESTION SYSTEM NURUL NAJWA BINTI AWANG HARUN BACHELOR OF COMPUTER SCIENCE (SOFTWARE DEVELOPMENT) WITH HONOURS

Transcription

1 EVENT PLANNING SUGGESTION SYSTEM NURUL NAJWA BINTI AWANG HARUN BACHELOR OF COMPUTER SCIENCE (SOFTWARE DEVELOPMENT) WITH HONOURS UNIVERSITI SULTAN ZAINAL ABIDIN 2018

2 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 : ii

3 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 : iii

4 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. iv

5 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. v

6 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. vi

7 TABLE OF CONTENTS Contents Pages DECLARATION... ii CONFIRMATION... iii DEDICATION... iv ABSTRACT... v ABSTRAK... vi TABLE OF CONTENTS... vii LIST OF TABLES... ix LIST OF FIGURES... x LIST OF ABBREVIATIONS / TERMS / SYMBOLS... xii LIST OF APPENDICES... xiii CHAPTER I... 1 INTRODUCTION Background Problem Statement Objectives Scope Limitation of Works Expected Outcome... 5 CHAPTER II... 6 LITERATURE REVIEW Introduction Proposed System Rule Based Technique (Backward Chaining) Comparison Table of Existing System Conclusion... 9 vii

8 CHAPTER III METHODOLOGY Introduction Justification Selection Methodology System Requirement Framework Context Diagram DFD Level DFD LEVEL Manage User Manage Package Manage Company (for admin) Entity Relation Diagram CHAPTER IV IMPLEMENTATION AND TESTING Introduction Implementation and Output Interface Design Test Case CHAPTER V CONCLUSION Introduction Project Contribution Project Constraints and Limitation Future Works Conclusion REFERENCES APPENDIX A: GANTT CHART FYP APPENDIX A: GANTT CHART FYP viii

9 LIST OF TABLES Table 2.1 Table Comparison of Existing System... 9 Table 3.1: List of software Table 3.2: List of hardware Table 4.1: Table Admin Table 4.2: Table Booking Table 4.3: Table Event Table 4.4: Table Client Table 4.5: Table Company Table 4.6: Table User Table 4.7: Table Package Table 4.8: Test Case Register For User Table 4.9 : Test Case Package For User Table 4.10: Test Case Approve Company for Admin Table 4.11: Test Case Update Company for Admin Table 4.12: Test Case Delete Company for Admin Table 4.13: Test Case Add Package for Company Table 4.14: Test Case Update Package for Company Table 4.15: Test Case Delete Package for Company ix

10 LIST OF FIGURES Figure 3.1: Waterfall Model Figure 3.2: Context Diagram for Event Planning Suggestion System Figure 3.3: DFD Level 0 for Event Planning Suggestion System Figure 3.4: DFD Level 1 for Manage User (for client) Figure 3.5: DFD Level 1 for Manage User (for company) Figure 3.6: DFD Level 1 for Manage User (for admin) Figure 3.7: DFD Level 1 for Manage Package (for client) Figure 3.8: DFD Level 1 for Manage Package (for company) Figure 3.9: DFD Level 1 for Manage Company (for admin) Figure 3.10: ERD for Event Planning Suggestion System Figure 4.1: Tables in the Event Planning Suggestion System Database Figure 4.2: Homepage interface Figure 4.3: Homepage Company Registration interface Figure 4.4: Homepage Contact Us Figure 4.5: User Registration Page Figure 4.6: Login Page Figure 4.7: Event Type and Budget Range Selection Page Figure 4.8: Result Page Figure 4.9: Edit Profile Page Figure 4.10: Homepage for Company interface Figure 4.11: Update Profile interface Figure 4.12: Register New Package interface Figure 4.13: Update Package Details interface Figure 4.14: Delete Package Details interface Figure 4.15: Homepage for Admin Figure 4.16: Update Profile for Admin x

11 Figure 4.17: Company Report Page Figure 4.18: Company Report (All) Page Figure 4.19: Package Report Page Figure 4.20: Update Company Details Page Figure 4.21: Delete Company Details Page Figure 4.22: Company Approval Page Figure 4.23: Pop-up notification after approving a company Figure 4.24: Change Password Page Figure 4.25: Page after Successfully Change Password xi

12 LIST OF ABBREVIATIONS / TERMS / SYMBOLS CD DFD ERD EPSS Context Diagram Data Flow Diagram Entity Relationship Diagram Event Planning Suggestion System xii

13 LIST OF APPENDICES APPENDIX TITLE PAGE A Appendix 1 57 B Appendix 2 58 xiii

14 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. 1

15 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 overbudget 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. 2

16 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, company and client 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 event companies - Able to manage security and maintenance of the system 3

17 ii) Company - Able to manage company s profile - Able to manage packages for the client to choose based on their selected budget range iii) 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 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. 4

18 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. 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. 5

19 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. 6

20 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. 7

21 2.4 Comparison Table of Existing System Author / Year Project Title Method / System Advantages Disadvantages Technique Description Robin van Personalized Content- -This The items will be Limited content Meteran, Recommender Based system is to recommended analysis System Filtering create based on a much Maarteen van (PRES) associations larger range of Someren between aspects than items in a searching would University of collection allow Amsterdam -When a user shows a preference for specific item, the system will compare those other items Siti Azmira binti Development Rule Based This system The system will The range or Azmi of E-Faraid provides automatically amount from the System by systematic calculate faraid calculation might 2015 Using Rule calculation based on the rule not be the exact Based based on that already amount but it can Quran, generated in which be self-reference Hadith and user had given before user get rules of details such as the real result Shafie. deceased detail, total deceased 8

22 property and list of heir Wan Nur Ain Wedding Rule Based Users are After selecting the This system is binti Wan Abdul Planning Technique required to budget range not developed for Hadi Suggestion choose desired, the system booking that if System budget will automatically the customers are 2017 range first display the interested, they so that the packages and had to call or system will services which send messages display the only suit the range. through next service COMMENT and option. section. Table 2.1 Table Comparison of Existing System 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. 9

23 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 scientificallyproven, 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. 10

24 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) iii) iv) System and software design Implementation and unit testing Integration and system testing v) Operational maintenance Figure 3.1: Waterfall Model 11

25 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. 12

26 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. 13

27 3.4 System Requirement Software Requirement Google Chrome Type of Software Description Used to do research on the project and to run the project PHP Adobe Dreamweaver CS6 MySQL Database ClickChart Diagram Flowchart Software MySQL Workbench 5.2 CE Microsoft Office 2010 Language used to develop the system Used to develop interface system Used as a database system Used to draw CD and DFD model Used for reverse engineering of the database As a platform for documentation Hardware Requirement Table 3.1: List of software 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 Table 3.2: List of hardware Used as a backup for the data and system 14

28 3.5 Framework 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 three users which are Admin, Company 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 approve companies, update and delete the process in the system. They are also able to manage their own profile. Login is also essential to the Company. But first, they need to register first at the system. When the admin already approved them, they will be given out the ID and temporary password through an . They will be able to change password and manage profile once they are successfully logon into the system. Company are able to add, update, and delete packages for the system. 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. 15

29 3.6 Context Diagram Description: Figure 3.2: Context Diagram for Event Planning Suggestion System Based on the figure 3.6 above, there are three actors in this Event Planning Suggestion System which are ADMIN, COMPANY and CLIENT. The context diagram above display the flow between three 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. Other than that, Company will also be able to insert their own details during registration and login. After being approved by Admin, Company can manage their profile and insert, update and delete package details. 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 approve companies and do report viewing. 16

30 3.7 DFD Level 0 Figure 3.3: DFD Level 0 for Event Planning Suggestion System 17

31 Description: The DFD has three entities which are ADMIN, COMPANY 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 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. COMPANY input COMPANY DETAILS into MANAGE COMPANY process which outputs COMPANY DETAILS into COMPANY data store. 9. COMPANY input PACKAGES DETAILS into MANAGE PACKAGES process which outputs PACKAGES DETAILS into PACKAGE data store. 18

32 10. ADMIN update COMPANY DETAILS into MANAGE COMPANY process which outputs COMPANY DETAILS into COMPANY data store. 11. 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. 19

33 3.8 DFD LEVEL Manage User Manage User (for client) Figure 3.4: 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. 20

34 Manage User (for company) Figure 3.5: DFD Level 1 for Manage User (for company) Description: 4. COMPANY input COMPANY DETAILS into REGISTER process which output COMPANY DETAILS into COMPANY data store. 5. COMPANY input COMPANY DETAILS into LOGIN process which output COMPANY DETAILS into COMPANY data store. 6. COMPANY input COMPANY DETAILS into UPDATE PROFILE process which output COMPANY DETAILS into COMPANY data store. 21

35 Manage User (for admin) Figure 3.6: 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. 22

36 3.8.2 Manage Package Manage Package (for client) Figure 3.7: 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. 23

37 Manage Package (for company) Figure 3.8: DFD Level 1 for Manage Package (for company) Description: 1. COMPANY input PACKAGE DETAILS into ADD PACKAGE process which output PACKAGE DETAILS into PACKAGE data store. 2. COMPANY input PACKAGE DETAILS into UPDATE PACKAGE process which output PACKAGE DETAILS into PACKAGE data store. 3. COMPANY input PACKAGE DETAILS into DELETE PACKAGE process which output PACKAGE DETAILS into PACKAGE data store. 24

38 3.8.3 Manage Company (for admin) Figure 3.9: DFD Level 1 for Manage Company (for admin) Description: 1. ADMIN approve COMPANY DETAILS into APPROVE 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. 25

39 3.9 Entity Relation Diagram Figure 3.10: 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. 26

40 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. 27

41 4.2 Implementation and Output 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 Event Planning Suggestion System Database Figure 4.1: Tables in the Event Planning Suggestion System Database There are seven tables in the database which are Admin, Budget Range, Client, Company, Event, Package and User. For each table, there are attributes at every column. 28

42 Table Admin NO ATTRIBUTES DESCRIPTION TYPE LENGTH REMARK 1 adminid Represents the unique id. 2 name The attribute for VARCHAR 10 PRIMARY KEY TEXT - - admin s name. 3 ID Represents the VARCHAR 14 - admin s identification card. 4 address Represents the VARCHAR 50 - admin s address. 5 Represents the VARCHAR 50 - admin s . 6 notel Represents the VARCHAR 14 - admin s phone number Table 4.1: Table Admin 29

43 Table BudgetRange NO ATTRIBUTES DESCRIPTION TYPE LENGTH REMARK 1 budetid Represents the unique id. 2 budgetrange The range of price VARCHAR 3 PRIMARY KEY VARCHAR 20 - in the system Table 4.2: Table Booking Table Event NO ATTRIBUTES DESCRIPTION TYPE LENGTH REMARK 1 eventid Represents the unique id. 2 event The type of VARCHAR 3 PRIMARY KEY VARCHAR 20 - events in the system Table 4.3: Table Event 30

44 Table Client NO ATTRIBUTES DESCRIPTION TYPE LENGTH REMARK 1 custid Represents the unique id. 2 custname The name of the VARCHAR 10 PRIMARY KEY TEXT - - client 3 custaddress Represents the VARCHAR 50 - address of the client. 4 Attribute for VARCHAR 50 - client s address 5 notel Attribute for INT 11 - client s phone number Table 4.4: Table Client 31

45 Table Company NO ATTRIBUTES DESCRIPTION TYPE LENGTH REMARK 1 companyid Represents the unique id. 2 comname The name of the company. 3 OwnerName Represents the name of the company s owner VARCHAR (10) VARCHAR (50) VARCHAR (50) 10 PRIMARY KEY nophone Attribute for INT (10) 10 - company s phone number 5 Attribute for company s address 6 address The company s address VARCHAR (50) VARCHAR (50) postcode Refers to the INT (5) 5 - company s address postcode 8 state The company s TEXT - - state 32

46 9 status The status of the TEXT - - company either PENDING, ACCEPTED or REJECTED Table 4.5: Table Company Table User NO ATTRIBUTES DESCRIPTION TYPE LENGTH REMARK 1 username username represents the VARCHAR 10 PRIMARY KEY unique id. 2 password password is the VARCHAR 20 - password for all of users Table 4.6: Table User 33

47 Table Package NO ATTRIBUTES DESCRIPTION TYPE LENGTH REMARK 1 pic The picture VARCHAR 10 - attribute for the package 2 packageid Represents the unique id. 3 pdetails Details of the VARCHAR 10 PRIMARY KEY VARCHAR package 4 companyid Represents the company ID who VARCHAR 10 FOREIGN KEY which provides the package 5 budgetrange Attribute for VARCHAR 20 - budget range of the package 6 event Attribute for VARCHAR 20 - event type of the package Table 4.7: Table Package 34

48 4.3 Interface Design Main Page Figure 4.2: Homepage interface This interface is the public homepage on which user does not have to login first to view the system. Figure 4.3: Homepage Company Registration interface If any company intended to register their company, they need to go to this page. 35

49 Figure 4.4: Homepage Contact Us User can view the location and post comment about the system. Figure 4.5: User Registration Page This page where is user wants to register in the system. All the stars in the page indicate that user needs to fill out the required field. 36

50 Figure 4.6: Login Page 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. 37

51 4.3.2 User Page Figure 4.7: Event Type and Budget Range Selection Page In this page, a signed up user can choose either Birthday Event or Anniversary Event. Then, they need to choose the budget range. Figure 4.8: Result Page In this page, the results based on the selection before is shown. If the user intended to choose the package, they will click the CHOOSE button and then the system will automatically redirected to the package s provider details. 38

52 Figure 4.9: Edit Profile Page User can also manage their profile by editing them except for the User ID. 39

53 4.3.3 Company Page Figure 4.10: Homepage for Company interface This is the example of homepage for Company which contains Manage Package, Profile and Logout. Figure 4.11: Update Profile interface The Company can update their profile in this page. 40

54 Figure 4.12: Register New Package interface The Company can register their packages in this page. Figure 4.13: Update Package Details interface The package details can be updated in this page by choosing the desired Package ID. Figure 4.14: Delete Package Details interface The package details can be deleted in this page by choosing the desired Package ID. 41

55 4.3.4 Admin Page Figure 4.15: Homepage for Admin This figure shows the homepage for Admin. Admin page contains Homepage, Profile, Report and Manage Company. Figure 4.16: Update Profile for Admin Admin can also manage he/she own profile in this page. 42

56 Figure 4.17: Company Report Page Admin can view Company Report either by all or by Company ID. The example of all of the company reports. Figure 4.18: Company Report (All) Page Figure 4.19: Package Report Page Admin can view Package Report either by all or by Package ID. 43

57 Figure 4.20: Update Company Details Page Admin can update company details by Company ID. Figure 4.21: Delete Company Details Page Admin can delete company details by Company ID. 44

58 Figure 4.22: Company Approval Page The Admin is to approve company in this page. In this page also, only company with status PENDING will be shown. There are only two actions which are APPROVE and REJECT. Figure 4.23: Pop-up notification after approving a company. Figure 4.24: Change Password Page 45

59 Figure 4.25: Page after Successfully Change Password Both on Figure 4.24 and Figure 4.25 shows change password pages where all three types of user can do. But most important user to change is Company as they were the only user that password were given by the Admin. 46

60 4.4 Test Case A test case is a set of condition under which a tester will determine whether a system function works as expected and based on its objective. Test cases can help to analyze the problems on the system requirements. The tables below show the test cases for the process in Event Planning Suggestion System Test Cases for User Step Procedure Expected Result Pass/Fail 1. Click Sign Up to register Application form Pass 2. Enter the following details: Pass 1. Usernama : na 2. Name : Nurul Najwa 3. Address : Kuala Nerus 4. wa@gmail.com 5. No Tel : Password : Click Submit button Message preview Pass successful or failure Table 4.8: Test Case Register For User 47

61 Step Procedure Expected Result Pass/Fail 1. Click Start Now to start Two types of event; Pass Birthday or 2. Choose one of the event: 1. Example: Birthday Event 3. Choose one of the list of budget range 1. Example: RM500-RM1000 Anniversary Event List of budget range List of packages based on the budget range selected Pass Pass 4. Click Choose button System will provide Pass the details of the package. Table 4.9 : Test Case Package For User 48

62 4.4.2 Test Cases for Admin Step Procedure Expected Result Pass/Fail 1. Click Approve Company List of Companies Pass that is wait to be approved or already approved 2. Click Approve The status of Pass company changes from Pending to Approved Table 4.10: Test Case Approve Company for Admin Step Procedure Expected Result Pass/Fail 1. Click Update Company Selection of Pass 2. Choose company ID 1. Example : C Pick one attribute to be updated 1. Example: Fax No: Company ID Form of details of the selected company ID Pass Pass 4. Click Submit button Message preview successful or failure Table 4.11: Test Case Update Company for Admin 49

63 Step Procedure Expected Result Pass/Fail 1. Click Delete Company Selection of Pass 2. Choose company ID 2. Example : C001 Company ID Form of details of the selected company ID Pass 3. Click Delete button Message Pass confirmation Yes or No 4. Click Yes Company deleted Pass 5. Click No Company cancel Pass deleted Table 4.12: Test Case Delete Company for Admin 50

64 4.4.3 Test Cases for Company Step Procedure Expected Result Pass/Fail 1. Click Add Package Application form Pass 2. Enter the following details: Pass 1. Package ID: P Details: Barbie Package 3. Company ID: C Budget Range: RM500- RM Event: Birthday Event 4. Click Submit button Message preview Pass successful or failure Table 4.13: Test Case Add Package for Company Step Procedure Expected Result Pass/Fail 1. Click Update Package Selection of Package Pass 2. Choose package ID 3. Example : P Pick one attribute to be updated 2. Example: Details ID Form of details of the selected package ID Pass Pass 4. Click Submit button Message preview Pass 51 successful or failure Table 4.14: Test Case Update Package for Company

65 Step Procedure Expected Result Pass/Fail 1. Click Delete Package Selection of Pcakage Pass 2. Choose package ID 1. Example : P001 ID Form of details of the selected package ID Pass 3. Click Delete button Message Pass confirmation Yes or No 4. Click Yes Package deleted Pass 5. Click No Package cancel Pass deleted Table 4.15: Test Case Delete Package for Company 52

66 CHAPTER V CONCLUSION 5.1 Introduction This chapter focused on project contribution, constraints of the project, the conclusion, and also future works that can be gained from this project. From this project, we can find out how to improve the system. 5.2 Project Contribution Event Planning Suggestion System was successfully developed before its timeline. The user will be able to choose any packages from various companies by selecting their desired event type and budget range. The company also will be able to promoting their own company and packages that they provide in this system. They can manage the package by adding, updating and deleting it in this system. So, eventually this system gives both benefits to public user and also the company. 53

67 5.3 Project Constraints and Limitation In the process of developing the project and preparation of fully functioning system, there are a few limitations of work that cause the constraints and difficulties to the developer. For this system, the limitations of work is that the rule based in this system does not implemented well due to limited characteristic to be chosen from. Other than that, if the user wants to book the package, they have to directly contact the company themselves, as the system already provided the company s information. They need to discuss the location and time for them to do the booking themselves with the company. 5.4 Future Works In the future, there are still a lot work can be made into this system. One, this system needs to provide more variation of characteristics such as location and time to the user and not only limit to just event type and budget range. Also, this system needs to have more validation. 54

68 5.5 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. 55

69 REFERENCES 1. SITI AZMIRA BINTI AZMI Development of E-Faraid System by Using Rule Based. University Sultan Zainal Abidin. 2. WAN NUR AIN BINTI WAN ABDUL HADI Wedding Planning Suggestion System. University Sultan Zainal Abidin. 3. Inferencing in Rule Based Systems: Forward and Backward Chaining. Accessed on February ROBIN VAN METEREN, MAARTEN VAN SOMEREN. Using Content-Based Filtering for Recommendation. University of Amsterdam. 56

70 APPENDIX A: GANTT CHART FYP1 ACTIVITY WEEK 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 57

71 APPENDIX A: GANTT CHART FYP2 ACTIVITY/WEEK Discussion Project Project Development Project Development and Testing Documentation and Report Project Progress Presentation and Evaluation Project Presentation and Evaluation Final Submission of Project Report 58