FUTSAL MATCHMAKING SYSTEM USING RULE-BASED

Transcription

1 FUTSAL MATCHMAKING SYSTEM USING RULE-BASED MUHAMMAD A DZIM BIN AZMAN SARJANA MUDA SAINS KOMPUTER (PEMBANGUNAN PERISIAN) UNIVERSITI SULTAN ZAINAL ABIDIN 2018

2 SUPERVISOR S DECLARATION I hereby declare that I have checked this project and in my opinion, this project is adequate in term of scope and quality for the award of the Bachelor of Science Computer (Software Development) Signature:. Name of Supervisor: Dr. Syarilla Iryani Binti Ahmad Saany Position: Lecturer Date: i

3 STUDENT S DECLARATION I hereby declare that this project paper is the result of my personal research. This dissertation is submitted to the Faculty of Informatics and Computing, University Sultan Zainal Abidin as partial fulfillment of the requirements for the Degree of Bachelor of Computer Science in Software Development. All stated information which has been obtained from other sources is fully referenced. Signature: Name: Muhammad A dzim Bin Azman Matric Number: BTAL Date:. ii

4 ACKNOWLEDGMENT In the name of Allah, Most Gracious, Most Merciful. First of all, Alhamdulillah and praise to Allah the Most Gracious and the Most Merciful for giving me a pink of health and be able to finish and complete my Final Year Project Next, I am grateful and would like to express my sincere thanks and appreciation to my supervisor, Dr. Syarilla Iryani Binti Ahmad Saanyfor her guidance. I really appreciate her continuous support from the initial to the final level in making this research possible. Without her advices, my project will not be completed. Also, I sincerely thanks for her time in guiding and correcting my mistake the whole time. I would like also to express special thanks also to all of my panel reviews that have been given me a chance to correct to my proposal and other suggestion for my project. My sincere thank goes to all lecturers and SMSK (PP) group members who help me in many ways. Last but not least, I would also like to express my gratitude to my parents, siblings and friends for giving me their support and encouragement for me to finish this project and to propose this project as my final year project. iii

5 ABSTRACT Futsal is an exciting, fast-paced small sided football game that is widely played across the world and is officially recognized by both UEFA and FIFA. Futsal is a five-a-side game, normally played on a flat indoor pitch with hockey sized goals and a size for ball with a reduced bounce. Although Malaysians young adults are popular with futsal games, it is hard to find another players to play with. Nowdays, most of the players only play futsal with someone that they knew. These lead to a problem which is caused the game being canceled if either one of the party un-able to play within the agreements. Thus, this project is proposed to help players to find others players to play futsal with. This system will help players to connect with others players through web based application. Futsal Matchmaking System will using String Searching Algorithm to search others players registered information. Then, players will decide the court that they could play (provided by the system) using Rule-Based Technique. When the systems meets the conditions, the system will then use Random Generator Algorithm to match making with players. By using FMS, it will helps players significantly by finding others players to play futsal together. iv

6 TABLE OF CONTENTS SUPERVISOR S DECLARATION STUDENT S DECLARATION ACKNOWLEDGMENT ABSTRACT I II III IV CHAPTER 1 INTRODUCTION BACKGROUND PROBLEM STATEMENT OBJECTIVES SCOPE EXPECTED RESULT LIMITATION OF WORKS THESIS STRUCTURE 5 CHAPTER 2 LITERATURE REVIEW INTRODUCTION RESEARCH COMPARISON 6 v

7 CHAPTER 3 METHODOLOGY AND DESIGN INTRODUCTION RESEARCH PARADIGM AND JUSTIFICATION SYSTEM DEVELOPMENT METHODOLOGY/SOFTWARE PLANNING PHASE REQUIREMENT ANALYSIS PHASE DESIGN PHASE IMPLEMENTATION PHASE TESTING PHASE DEPLOYMENT PHASE SYSTEM REQUIREMENTS SOFTWARE REQUIREMENTS HARDWARE REQUIREMENT PROCESS DESIGN CONTEXT DIAGRAM DATA FLOW DIAGRAM LEVEL DATA FLOW DIAGRAM LEVEL PROCESS 2.0: MANAGE PLAYER PROCESS 3.0: MANAGE COURT PROCESS 4.0: CREATE TEAM PROCESS 5.0: MANAGE TEAM PROCESS 6.0: FIND OPPONENTS FRAMEWORK 26 vi

8 3.6 DATABASE DESIGN ENTITY RELATIONSHIP DIAGRAM (ERD) DATA DICTIONARY ADMIN COURT PLAYER TEAM CHAPTER SUMMARY 32 CHAPTER 4 IMPLEMENTATION INTRODUCTION INTERFACE DESIGN USER INTERFACE ADMIN INTERFACE SUMMARY 52 CHAPTER 5 RESULT AND TESTING INTRODUCTION RULE-BASED DECISION SUPPORT SYSTEM (DSS) INTRODUCTION TO RULE-BASE DSS THEORY OF RULE-BASED SYSTEM BRIEF EXPLANATION ABOUT TEST ANALYSIS WHITE BOX TESTING 57 vii

9 5.2.3 TEST CASES USER TEST CASES EXECUTION SUMMARY 74 CHAPTER 6 CONCLUSION INTRODUCTION PROJECT ACHIEVEMENT PROJECT CONSTRAINS SUGGESTION OF IMPROVEMENT IN THE FUTURE MORE COURT AND EXPANDED REGION SUMMARY 78 REFERENCES 79 JOURNAL 80 APPENDIX 81 GANTT CHART 81 viii

10 CHAPTER 1 INTRODUCTION 1.1 BACKGROUND Futsal is a very popular sport in all ages either kids, teenagers or adults. However, futsal cannot be play alone but must have at least two teams to play with. Each team at least to have five players and the players also need a place (court) to play futsal. Futsal is played between two teams of five players each, one of whom is the goalkeeper. Although it only consist of two team and five players each for each team, not enough players usually become the main problems for the game which may lead to canceling of the game. This propose project is design to help players to finds others players. The system will help a players to search for a team to play and a team can search for another team (opponent) to play futsal. Futsal Matchmaking System is mainly focus on connecting others players through various ways. 1

11 1.2 PROBLEM STATEMENT Futsal Matchmaking System is developed to overcome several problems that arise which are: i) A player does not have a team to play with. An individual players does not have team members to play futsal. The System will help the individual players to search for a team. ii) A team does not have an opponent to play with. At least two team are present to play futsal and each team must have five team members. iii) There is no place to play the game. The System will provide the location of courts and each team will choose which court they are available to play then the system will save it into the database. 2

12 1.3 OBJECTIVES To develop a system that will help players finding information faster and efficient. To design a system that will help players finding team mate or opponents to play futsal. To implement the rule in the proposed system which is rule-based technique algorithm that wills choose the court based on players choices. To test the development and implemented the system. 1.4 SCOPE This system focuses on futsal players that wanted to search for others players. Futsal Matchmaking system is divided into two parts which is user (players) and admin. Admin in this system will act as an administrator for the system and manage the system. a) User (Players): Able to search for others player information. Able to update their information. Able to search for futsal teams. Able to search choose the location of courts. 3

13 b) Admin: Able to log in as administrator. Able to approve users registrations to the system Able to update users (Add or Delete). Able to add and update, delete courts. 1.5 EXPECTED RESULT The system will connect players with each other. The system can help players to find players and accurate information with just one click. The system will provide locations of courts. This system work with full functionality and meets user requirement. 4

14 1.6 LIMITATION OF WORKS The system is not developed for booking process. In order to book the court, the users need to do it by themselves. Only admin allowed adding, updating and deleting the data about the court. 1.7 THESIS STRUCTURE This thesis consists of five chapters. Chapter one is introduced that contains project background, problem statement, objectives, scope and thesis structure. Chapter two is a literature review and discuss the technique and theory that had been carried out by another researcher and existing computer application that related to the on-going project. Chapter three is a methodology that discusses method or technique that are used in the project also design framework, specifying in detail design of development projects. Chapter four is the implementation of the project and the report of testing that had been done to the development system. Chapter five is the conclusion of the overall project followed by references. 5

15 CHAPTER 2 LITERATURE REVIEW 2.1 INTRODUCTION This chapter provide the literature review for the system that will be developed. The literature review is a process of reading, analysing, evaluating and summarizing scholarly material about a specific. It can be a guideline to develop a new system so that the new system can provide better or more functional than existing system. 2.2 RESEARCH COMPARISON There are several journal related to the topic of the system that will be develop. Many of them use different ways to make the appointment. There are some advantages and disadvantages that we can analyse and then try to think for the added value that we can apply in the system that we will develop 6

16 Title Author Journal THE OPTIMAL LOCATION OF INSPECTION STATIONS Kyong-sik Kang, Keneth A. Ebeling, Seuong-houn La An expert system has the potential to solve problem using a rule-based system to determine the near optimal location of inspection stations. The prototype expert system is divided into a static database, dynamic database and knowledge base. Based on defined production systems, the sophisticated rules are generated by the simulator as part of knowledge base Year 1990 Method Rule-based methodology Table 2.2.1: Research 1 Title Author Journal A COMPARATIVE STUDY ON STRING MATCHING ALGORITHMS OF BIOLOGICAL SEQUENCES. Pandiselvam.P, Mariuthu.T, Lawrance.R String matching is a technique to discover pattern from the specified input string. String matching algorithms are used to find the matches between the pattern andspecified string. For example Let U is an alphabet; the basics of U are called symbols or characters. For example, if U= {A,G} then AGAG is a string. The pattern is denoted by P (1 M) the string denoted by T (1 N). The pattern occurs in thestring with the shifting operation. Year 2016 Method String matching algorithms Table 2.2.2: Research 2 7

17 Title FUTSAL MATCHMAKING SYSTEM USING RULE-BASED Author MUHAMMAD A DZIM BIN AZMAN (2018) Journal To design and develop a new system which can help to manage player in more organize and to matching players with others players with Rule- Based. This way, the task can be handling according to player choices. Inside the system, Users (players) will able to register and make groups with others players and then matching with others players. Year 2018 Method Advantage Rule-Based 1. Able to gathers players. 2. Able to manage players. 3. Able to provide a status about others players. 4. Able to provide more information to the players. Table 2.2.3: Research Summary 8

18 CHAPTER 3 METHODOLOGY AND DESIGN 3.1 INTRODUCTION In this section, the methodology that used to develop this system is described. The use of the methodology is to solve the entire problem arising and to ensure that the project will work as well as the planning to develop this system smoothly and complete within the given time. There are many types of methodology that we can apply and used in the development of the system. The approach must be chosen correctly so that it is suitable for the development of the project. It is the important step to guide the researcher to manage the given task. Hence, I would like to use Waterfall Model for the project of Futsal Matchmaking System using Rule-Based. Furthermore, I will explain more details about every phase that involve in the development of this project and also the system requirement. 3.2 RESEARCH PARADIGM AND JUSTIFICATION Waterfall model is a model which was developed for software development. The basic idea it is called as such because the model develops systematically from one phase to another phase in downwards style like a waterfall. The phases consist of definition study or analysis, basic design, technical design, construction and implementation, testing, integration, and maintenance 9

19 Figure 3.2: Waterfall Model Waterfall model has been chosen based on the following consideration: 1. Project Monitoring - Each phase of the development is monitored from time to time to ensure all the system module match earlier system requirement. 2. Allow changes - Any changes in developing the system can be implements at every phase to improve the functionality of the system. 10

20 3. Save cost - The development of the system can save the cost because the information collected at each phase is very particular until the final test of the system. 3.3 SYSTEM DEVELOPMENT METHODOLOGY/SOFTWARE This project is using Structured Analysis and Design Methodology (SADM) by applies waterfall model. This methodology is adaptable to time given for complete the task. It starts with the planning, requirement analysis, design, implementation and testing and operation and maintenance. Every phase must fulfil the requirement specification. After the system complete, it will undergo maintenance as final test PLANNING PHASE The objective of this phase is to choose and decide the system and title for this project with the supervisor. The title that has been agreed to proceed was Futsal Matchmaking System. This system will develop for players a site facility for players to manage and find others players to play futsal. An abstract is done based on information gathered and the system that has been agreed to develop. 11

21 3.3.2 REQUIREMENT ANALYSIS PHASE The objective of this phase is to gather the entire requirement needed to develop the system and analyse the existing system. In this phase, the information gathered regarding on technique is based on the analysing from the internet searching to understand more about the system will develop. For better understanding about the existing Futsal Matchmaking system, an observation and interview from the owner and the workers of futsal court at Kota Bharu to see and learn how the real system is performed. I also get to know what the element that is needed for this project to be implemented with the new technique use. 12

22 3.3.3 DESIGN PHASE Design phase contains several diagrams to show the process of the system will function. This project will be divided into three types of design that are Process Design, Database Design, and Interface Design. In Process Design, the items that are needed such as Context Diagram, Data Flow Diagram (DFD) Level 0, Data Flow Diagram (DFD) Level 1, Data Flow Diagram (DFD) Level 2, Data Decomposition and Algorithm that will be applied in this project. In Database Design, the items that are needed are Entity Relationship Diagram (ERD). For Interface Design, the items that are needed such as Homepage design, Menu design, Input form design and Output design. These entire diagram and items listed above is the guide for the user to understand the flow of the system that will be functioning. The database for the overall system also is developing at this phase IMPLEMENTATION PHASE This phase will transform the design into the real system by implementing the coding. The project is developing using Java programming. JSP language will be used to link the web-based on the database by using MySQL as the platform for the database and XAMPP as the localhost server. Rule-Based technique will be implemented to decide the location of futsal. Some validation will be added to make sure the request information that we need from the user to so that the searching can be done successfully. 13

23 3.3.5 TESTING PHASE After writing the code, the system module is tested by using single unit testing to test the single module of the system. Then, the integration testing is conducted to test the integrated modules. After that, system testing is conducted to test error of the whole system. Any errors or bugs will be fixed and the system will repeat the testing phase until there none of errors and bugs is founds. The finishing of the testing phase will be released the first version of the system DEPLOYMENT PHASE After the system is bug-free, the system can be released and users can use the system. Once the system is in the steady state, it is reviewed that the system has met all the goals, requirement and the objective of the project plan satisfactory results. 14

24 3.4 SYSTEM REQUIREMENTS SOFTWARE REQUIREMENTS LIST OF SOFTWARE NEEDED: NO. SOFTWARE PURPOSE 1. Netbean IDE Editor to write code program 2. XAMPP Server Act as a local server to run and test the application 3. MySQL Platform for the database of the application 4. UC Browser / Google Chrome A browser to run the localhost and searching for information 5. Edraw Max A tool to create figures and diagram such as Context Diagram, DFD and ERD 15

25 6. MySQL Workbench A tool to create ERD and SQL command for database 7. - Microsoft Word 2010 Platform for documentation of system - Microsoft PowerPoint Balsamiq Mockups 3 Platform to design the interface 10. Snipping Tool Used to captured and screen shot the images Table 3.4.1: List of Software Requirement 16

26 3.4.2 HARDWARE REQUIREMENT LIST OF HARDWARE NEEDED: NO. HARDWARE PURPOSE 1. Laptop - To develop, testing and implement the system - Documentation 2. Printer - Print the document 3. Pendrive and Hard Disk - Storage Table 3.4.2: List of Hardware Requirements 17

27 3.5 PROCESS DESIGN CONTEXT DIAGRAM Figure 3.5.1: Context Diagram Figure above shows the Context Diagram for Futsal Matchmaking System data flow. There are two main users involve in this system which is Admin, and Player. All users are required to log in to the system in order to use this system. There are 12 data flows involved in the interaction between primal process and the users. 18

28 3.5.2 DATA FLOW DIAGRAM LEVEL 0 Figure 3.5.2: Data Flow Diagram (DFD) Level 0 19

29 Figure shows the DFD Level 0 for Futsal Matchmaking System which represents the graphical flow of the data in the system. In DFD, all processes connect with an entity and data store which allows data flow from an external data sources or an internal data sources. This system has six processes which are Register, Manage Player, Manage Court, Create Team, Manage Team, and Find Opponents. This system also has three data store which is D1 for Player that stored all player information, D2 for Court that stored all court information, and D3 for Team that stored team information. 20

30 3.5.3 DATA FLOW DIAGRAM LEVEL PROCESS 2.0: MANAGE PLAYER Figure DFD Level 1: Manage Player Figure above shows DFD Level 1 for process 2.0 Manage Player for the users. This process lets player and admin view and updates the player profile. In other hand admin also can add or delete the available players. 21

31 PROCESS 3.0: MANAGE COURT Figure DFD Level 1: Manage Court Figure above shows DFD Level 1 for process 3.0 Manage Court for admin. This process lets the admin add, update and delete court information. All the data will be saved in table Court. 22

32 PROCESS 4.0: CREATE TEAM Figure DFD Level 1: Create Team Figure above shows DFD Level 1 for process 4.0 Create Team for Player. In this process, player can add a new team, find others player to join their team or to join any existing team. All the information needed are retrieve and stored from Player and Team database. 23

33 PROCESS 5.0: MANAGE TEAM Figure DFD Level 1: Manage Team Figure above shows DFD Level 1 for process 5.0 Manage Team that involves Admin. This process lets the Admin update the team details. This process also enable admin to add player into a team and admin also can remove player from a team. Next, inside this process, admin also can delete an existing team. 24

34 PROCESS 6.0: FIND OPPONENTS Figure DFD Level 1: Manage Team Figure above shows DFD Level 1 for process 6.0 Find Opponents that involves Player. This process lets the Player to choose available court first from the system and then the system will begin the searching for other team that have choose the same courts. Then, the system will display the list of the team. 25

35 3.5.4 FRAMEWORK Figure 3.5.4: Framework for Futsal Matchmaking System Figure shows the framework for Futsal Matchmaking System. In order to use this system, the admin and the players need to login to the system first. After succeeding authenticates the identification, the user can proceed with the next process provided. Players will able to create a Team or join any existing Team. If a player decide to create a Team, the player will able to search others players and invite them to their team. Then, the player will choose which courts their team will able to play so that they will able to have a match with other team that have the same conditions. 26

36 3.6 DATABASE DESIGN ENTITY RELATIONSHIP DIAGRAM (ERD) Entity Relationship Diagram (ERD) is a data model which is tools used in analysis to describe the data requirement and assumptions in the system from top-down perspectives. The ERD shows it using derived table. Derived are used for making a relationship between two or more main tables, it will have only record of foreign key from the main table. 27

37 Figure Entity Relationship Diagram(ERD) DATA DICTIONARY Figure 3.6.2: Table for Overall System 28

38 Figure shows the overall table that will be used in this system. The database is named with futsal. There are four tables in futsal database which is admin table, court table, player table, and team table ADMIN Figure : Table for Admin Figure shows the table customer for futsal database. This table is used to store the admin information. This table has two fields which are adminid and password COURT Figure : Table for Court Figure shows the table vehicle for futsal database. This table is used to store the court information. This table has three fields which are courtid as primary key, courtname and courtphonenumber. 29

39 PLAYER Figure : Table for Player Figure shows the table staff for futsal database. This table is used to store the player information. This table has five fields which are playerid as primary key, fname, lname, phonenumber and teamname which is foreign key from TEAM table 30

40 TEAM Figure : Table for Service Figure shows the table service for futsal database. This table is used to store the team information. This table has five (or more depends on number of court) which are teamname as primary key, court_a, court_b, court_c and court_d (at the moments). 31

41 3.7 CHAPTER SUMMARY In this chapter discusses methodology for the system development, hardware and software required to develop the system thus make them able to run on specific platform. Every phase in development follows the project methodology that mention in this chapter. System requirement which is hardware and software required for developing system is briefly explained. Throughout this chapter also focussed about data modelling which are context diagram, data flow diagram and entity relationship diagram. In data modelling, the discussion is more about the structure of the data represent in the database. Diagrams were constructed to give more understanding of the system. 32

42 CHAPTER 4 IMPLEMENTATION 4.0 INTRODUCTION Implementation phase is a systematic structured approached to integrate software based service or component into the workflow of an organizational structure or an individual end-user. The system need to be customized to meet with requirement from the user. 4.1 INTERFACE DESIGN The goal of user interfaces is to create a communication display between the system and user. In this proposed project, user will interact with the system using 100 percent interface display. The interface design should lead user to understand the flow of the system. Many aspect need to be consider in designing the interface so that the interface will be able to guide user all the way throughout the system. An interface design should consider about user friendly aspect for the users, make sure that user understand what need and what not to be inserted in the field on the interface display. Also, the consistency of the interface which means the locations of the button, color schemes, etc. 33

43 4.1.1 USER INTERFACE Figure 4.1 shows example of index interface of the system. Figure 4.1 Index Interface 34

44 Figure 4.2 shows Login interface for user to login. But first, users have to register as a player for the system. Users need to pick a username and create a password at registration interface, and they must re-insert the username and password at this login interface. Figure 4.2 Login Interface 35

45 Figure 4.3 shows the user profile after login into the system. And this page, user will able to edit profile, change password or leave team. Figure 4.3 User profile interface. 36

46 Figure 4.4 shows a form that enable users to edit their details. Figure 4.4 User Profile Interface to Edit Profile. 37

47 Figure 4.5 shows a form that works to changes users Password. Figure 4.5 User Profile Interface to change Password. 38

48 Figure 4.6 shows the homepage for TEAM section at for users. At this page, users have three options which is to view their team at My Team, to search for others team at Search Team or to create a new team Create Team. Figure 4.6 Team homepage section for users. 39

49 Figure 4.7 shows the interface of users when they click on My Team on previous page. At this page, users will able to see their team members details, invite new player, view team matches and leave the team. Figure 4.7 View Team homepage. 40

50 Figure 4.8 shows the interface of users when they click on Search Team. At this page, users will able to see others registered Team and if a user does not register to any team yet, user will able to view the team and request to join that team. Figure 4.8 Search Team homepage. Figure 4.9 shows request button to join selected team. Figure 4.9 Request Button to join selected team for the next page after selecting a Team 41

51 Figure 4.10 shows the interface of user for Create Team section. If user are not registered in any team yet, users will able to choose this option. Users will fill the form and decide which Court their team will able to play. Figure 4.10 Create Team form. 42

52 Figure 4.11 shows the interface of user for Find Opponents section. In this section, users need to registered to a team first. If not, users are unable to access this page. At this page, users will notified about their team court selection and able to change their court desired for the matchmaking with other team to begin. Figure 4.11 Find Opponent by courts. Figure 4.12 shows the interface after users select GO. At this page, users again need to choose which court their team want to play. 43

53 Figure 4.12 Find Opponent select court. Figure 4.13 shows the result of matchmaking system by randomize all possible team that agree to play at certain court. User can random again to get another team or proceed to book the date and time with that selected team. Figure 4.13 Result after Matchmaking the opponents. 44

54 Figure 4.14 shows booking form if user click Proceed to Booking from previous page. Figure 4.34 Booking date and time interface. 45

55 4.2 ADMIN INTERFACE Figure 4.15 shows Admin login page. Figure 4.15 Shows Admin Login. Figure 4.16 shows homepage of admin which is have three section, Player section, Team section and Court section (match details including booking). Figure 4.16 Shows the homepage of Admin site. 46

56 Figure 4.17 shows details about registered users at Player section. Admin can search and view the selected user info. Figure 4.17 Players Details at Admin Site 47

57 Figure 4.18 shows the profile of selected user from previous page. Admin are able to edit user profile, change user password, delete the user or forcefully remove the player from their current team. Figure 4.18 Shows selected Player details. 48

58 Figure 4.19 show the interface of Team Section at admin site. This page enable admin to see registered team and view it profile. Figure 4.19 List of Registered Team 49

59 Figure 4.20 shows the profile and members of selected team from previous page. Admin are able to remove selected player or disband the team. Figure 4.20 Shows Team profile from Admin Site 50

60 Figure 4.21 shows Admin interface at Court section which is to view the record of court used by which team at which date and time. In this page, Admin also can cancel the booking too. Figure 4.21 shows Match and Court records. 51

61 4.3 SUMMARY In this chapter, all of the interfaces is design and functioning as what is stated in the methodology and the flow of the system. All interfaces were design according the flow of the system. 52

62 CHAPTER 5 RESULT AND TESTING 5.0 INTRODUCTION In this chapter, we will discuss the test that had been conducted alongside with its results. The technique implemented for evaluating this system is test case testing, in which test cases of the system functionality is check modules by modules to ensure that all elements in the system is working properly and meeting its specification and requirement. 5.1 RULE-BASED DECISION SUPPORT SYSTEM (DSS) Rule-based method is a type of a Decision Support System (DSS) that being used by this system to produce desired outcome. The Rule-Based method is implemented by the system when the system need to match with other team that been produced by using some rules, conditions and facts. The rule is where the Team and Court state been compromised. Then from the compromised data, the condition is produced based on the compromised data. The rule that matched the condition will be used to display the Team selected. 53

63 5.1.1 INTRODUCTION TO RULE-BASE DSS Using a set of assertions, which is collectively from the working memory, and a set of rules that specify how to act on the assertion set. A rule-based system can be created. Rule-based system are fairly simplistic, consisting of little more than a set of if-then statements, but provide the basic for so-called expert system which are widely used in many fields. The concept of an expert system is this: the knowledge of an expert is encoded into the rule set. When exposed to the same data, the expert system AI will perform in a similar manner to the expert. Rule based system are a relatively simple model that can be adapted to any number of problems. As with any AI, a rule-based system has its strengths as well as limitations that must be considered before deciding if it s the right technique to use for a given problem. Overall, rule-based system are really only feasible for problems for which any and all knowledge in the problem area can be written in the form of if-then rules and for which this problem area is not large. If there are too many rules, the system can become difficult to maintain and can suffer a performance hit. To create a Rule-Based System for a given problem, you must have (or create) the following: A set of facts to represent the initial working memory. This should be anything relevant to the beginning state of the system. A set of rules. This should encompass any and all actions that should be taken within the scope of a problem, but nothing irrelevant. The number of rules in the system can affect its performance, so you do not want any that are not needed. 54

64 A condition that determines that a solution has been found or that none exists. This is necessary to terminate some rule-based system that find themselves in infinite loops otherwise THEORY OF RULE-BASED SYSTEM The rule-based system itself uses a simple technique: It starts with a rule-based, which contains all of the appropriate knowledge encoded into If-Then rules, and a working memory, which may or may not initially contain any data, assertions or initially known information. The system examines all the rule conditions (IF) and determines a subset, the conflict set, of the rules whose conditions are satisfied based on the working memory. Of this conflict set, one of those rules is triggered (fired). Which one is chosen is based on a conflict resolution strategy. When the rule is fired, any actions specified in its THEN clause are carried out. These actions can be modify the working memory, the rule-base itself, or do just about anything else the system programmer decides to include. This loop of firing rules and performing actions continues until one of two conditions are met: there are no more rules whose conditions are satisfied or a rule is fired whose action specifies the program should terminate. 55

65 5.2 BRIEF EXPLANATION ABOUT TEST ANALYSIS In order to test the system functionality if it is fully functioning, satisfying user requirement and error free, testing is needed to be done. There are 3 types of testing which are unit testing, integration testing and system testing. Unit testing is use to verify the functionality of a specific sections of a code, usually conducted at the function phase. Integration testing on the other hand, works by exposing the defects in the interface and the interaction among integrated components or between modules. System testing or known as End-to-End testing is conducted to test is the completely integrated system meets its requirements BLACK BOX TESTING Black box testing a software testing technique where the functionality of the software that being tested or SUT (Software Under Testing) is testing without looking at the internal coding structure, implementation details and knowledge of the internal path of the software. This type of testing is based entirely on the software requirements and its specifications. Black Box testing focuses on inputs and the output of the software system without bothering about the internal knowledge of the software programs. 56

66 5.2.2 WHITE BOX TESTING White box testing is a test where a software solutions internal coding structure and infrastructures is being tested. It is focuses on strengthening the security, flows of the inputs and produced output throughout the system and improving design and functionality. Testing can be done at the system integration phase and unit levels of software development. One of the goals of white box testing is to verify a working flow of an application. White box testing involves testing a series of pre-defined inputs against expected output TEST CASES A test case is a set of conditions or variable which will be testing by a tester whether a requirement upon an application is partially or fully satisfied. Test cases are also defined as a sequence of steps to test the correct behavior of functionality or the features of the applications. 57

67 5.3 USER TEST CASES EXECUTION Test Case No: 1 Test Case Name: Login System : Futsal Matchmaking System Sub-System : Login Design by : Muhammad A dzim Bin Azman Design Date : 25/7/2018 Executed By : Muhammad A dzim Bin Azman Execution Date : 08/8/2018 Pre-Condition(s) User must have an account for the system. User must have valid Username and Password. 58

68 STEP ACTIONS EXPECTED STATUS COMMENT SYSTEM RESPONSE 1. Enter correct combination of user name and password on login form Live Validation. Login Success! Pass 2. Enter Wrong combination of user name and password on login form Live Validation Password Do not Match Fail 3. Enter null username and password on the login form Live Validation Please fill in this form! Fail Post-Condition(s) Users are able to log in and view their homepage and inserted data. 59

69 Test Case No: 2 Test Case Name: Insert New Data System : Futsal Matchmaking System Sub-System : Data Design by : Muhammad A dzim Bin Azman Design Date : 25/7/2018 Executed By : Muhammad A dzim Bin Azman Execution Date : 08/8/2018 Pre-Condition(s) User must have an account for the system. 60

70 STEP ACTIONS EXPECTED STATUS COMMENT SYSTEM RESPONSE 1. View Data If current user, data of Pass current data will be displayed. 2. Enter Data for new user System will display forms to enter data (First Name, Last Name, Phone number, , Birth date, Gender, Address). Pass Post-Condition(s) System will show the entered data/ current data. 61

71 Test Case No: 3 Test Case Name: Update Data System : Futsal Matchmaking System Sub-System : Update Design by : Muhammad A dzim Bin Azman Design Date : 25/7/2018 Executed By : Muhammad A dzim Bin Azman Execution Date : 08/8/2018 Pre-Condition(s) User must have record of data in the system. 62

72 STEP ACTIONS EXPECTED STATUS COMMENT SYSTEM RESPONSE 1. Update data for user. System will display Pass forms to enter data (First Name, Last Name, Phone number, , Birth date, Gender, Address). Post-Condition(s) System will show update user data. 63

73 Test Case No: 4 Test Case Name: View User Current Team System : Futsal Matchmaking System Sub-System : Team View Design by : Muhammad A dzim Bin Azman Design Date : 25/7/2018 Executed By : Muhammad A dzim Bin Azman Execution Date : 08/8/2018 Pre-Condition(s) User must have registered Team in the system. 64

74 STEP ACTIONS EXPECTED STATUS COMMENT SYSTEM RESPONSE 1. View current Team. System will display Pass user s current team according to latest update. Post-Condition(s) System will show user current team data. 65

75 Test Case No: 4 Test Case Name: Find Opponents System : Futsal Matchmaking System Sub-System : Team View Design by : Muhammad A dzim Bin Azman Design Date : 25/7/2018 Executed By : Muhammad A dzim Bin Azman Execution Date : 08/8/2018 Pre-Condition(s) User must have registered Team in the system. A Team must choose which court they able to play. 66

76 STEP ACTIONS EXPECTED STATUS COMMENT SYSTEM RESPONSE 1. Finding opponents. System will generate Pass and select which teams are able to play a match with current saved court for each team. 2. Randomize the Team All of selected team will be randomized and the system will only pick one of it. Pass Post-Condition(s) System will show selected team. 67

77 5.4 ADMIN TEST CASE EXECUTION Test Case No: 1 Test Case Name: Login System : Futsal Matchmaking System Sub-System : Login Design by : Muhammad A dzim Bin Azman Design Date : 25/7/2018 Executed By : Muhammad A dzim Bin Azman Execution Date : 08/8/2018 Short Description : Admin logging into the system. Pre-Condition(s) Admin must have an account for the system. Admin must have valid Username and Password. 68

78 STEP ACTIONS EXPECTED STATUS COMMENT SYSTEM RESPONSE 1. Enter correct combination of user name and password on login form Live Validation. Login Success! Pass 2. Enter Wrong combination of user name and password on login form Live Validation Password Do not Match Fail 3. Enter null username and password on the login form Live Validation Please fill in this form! Fail Post-Condition(s) Admin are able to log in and view their homepage and inserted data. 69

79 Test Case No: 2 Test Case Name: Update Player Data System : Futsal Matchmaking System Sub-System : Data Design by : Muhammad A dzim Bin Azman Design Date : 25/7/2018 Executed By : Muhammad A dzim Bin Azman Execution Date : 08/8/2018 Short Description : Admin edit (update) selected player data. Pre-Condition(s) Selected player data is already existed. 70

80 STEP ACTIONS EXPECTED STATUS COMMENT SYSTEM RESPONSE 1. Edit Player Data 1. The System will Pass display selected player data. 2. Admin click on the Update Button. 3. The system will display editable form. Post-Condition(s) The data will be saved and the system will re-directed to player homepage. 71

81 Test Case No: 3 Test Case Name: Delete Player Data System : Futsal Matchmaking System Sub-System : Data Design by : Muhammad A dzim Bin Azman Design Date : 25/7/2018 Executed By : Muhammad A dzim Bin Azman Execution Date : 08/8/2018 Short Description : Admin edit (delete) selected player data. Pre-Condition(s) Selected player data is already existed. 72

82 STEP ACTIONS EXPECTED STATUS COMMENT SYSTEM RESPONSE 1. Delete Player Data 1. The System will Pass display selected player data. 2. Admin click on the Delete Button. 3. The system will delete the selected player. Post-Condition(s) The data will be deleted and the system will re-directed to player homepage. 73

83 5.5 SUMMARY System testing plays an important role in the system development, in order to test whether the system that has been developed has achieves its specified objectives and user requirement. It is also ensure that the developer knows what and where to be fixed and thus leading to a complete and successful system. 74

84 CHAPTER 6 CONCLUSION 6.0 INTRODUCTION While completing this project proposal, there are several constraints that came up. The first constraint is to determine the correct flow / path used in the system. Since there are many lookup table and confusion about the method selected they may some delay might happened to user. The lookup table in the database need to be accurately determine so that the matchmaking between team is working perfectly and efficient. Each step has been documented so it will be very clear to complete and later on developing the system. 75

85 6.1 PROJECT ACHIEVEMENT Futsal Matchmaking System Using rule based method can help people who wanted to play futsal with team and challenging opponents. This system will select all available team that are agreed to play at certain court and randomized it to find a single team. By using this system, it is only requiring a simple and precise data from user which is the team built by user with selected courts to generate and randomize opponents. At the end of the semester, Futsal Matchmaking System is successfully developed. Besides giving users the appropriate opponents, it is also used to introduce and communicate users between users. 76

86 6.2 PROJECT CONSTRAINS There are several problem and limitations occurred in the development of the system. But luckily, most of them are able to be solves within the time frames of the development. These are the problems that occurred during the process: 1. To understand the flow and path of the added value selected method (Rule- Based Decision Support System). The developer need to understand the flow, keyword and phases required to achieve desirable results. 2. Taking in consideration of adding and removing unnecessary / necessary module proposed by panels and supervisor because sometimes, different understanding may lead to different result. 3. Developer often to overlook small details but play a big contribution to the output of the system 77

87 6.3 SUGGESTION OF IMPROVEMENT IN THE FUTURE. As for the future of the system, I hope that the interface can be regenerate to make it more users friendly and more suitable for user view. Also, maybe the background color, picture and quotes can be change to give user a better viewing pleasure of the system MORE COURT AND EXPANDED REGION. As now, the system only provide four registered court inside the system. With having more courts and team, users have more choices and more result upcoming output. This can help to improve the reliability of the system. 6.4 SUMMARY By using this system, users can connect with other users. This system will help them to find other users as opponents according to their court choices. The match between the users will be monitored by admin to make sure everything is doing well. As for conclusion, all of the objectives to develop this system had been achieves. 78

88 REFERENCES Webpages [1] What is Rule Based? [2] w3school 79

89 JOURNAL [3] Kyong-sik Kang, Keneth A. Ebeling, Seuong-houn La : THE OPTIMAL LOCATION OF INSPECTION STATIONS [4] Pandiselvam.P, Mariuthu.T, Lawrance.R : A COMPARATIVE STUDY ON STRING MATCHING ALGORITHMS OF BIOLOGICAL SEQUENCES [5] Dr Inés Salas, University of Santiago, Chile : TEAM BUILDING [6] Christos K. Volos1 : Chaotic Random Bit Generator Realized with a Microcontroller [7] Ankit R. Chadha, Rishikesh Misal, Tanaya Mokashi : Modified Binary Search Algorithm 80

90 Appendix GANTT CHART 81