BOARDING SCHOOL OUTING MANAGEMENT SYSTEM SITI NAZIRAH BINTI ABD HALIM

BOARDING SCHOOL OUTING MANAGEMENT SYSTEM SITI NAZIRAH BINTI ABD HALIM BACHELOR OF COMPUTER SCIENCE (SOFTWARE DEVELOPMENT) WITH HONOURS UNIVERSITI SULTAN ZAINAL ABIDIN 2018

BOARDING SCHOOL OUTING MANAGEMENT SYSTEM SITI NAZIRAH BINTI ABD HALIM Bachelor of Computer Science (Software Development) With Honours Faculty of Informatics and Computing Universiti Sultan Zainal Abidin, Terengganu, Malaysia 2018

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: Siti Nazirah Bt Abd Halim Date: i

CONFIRMATION This is to confirm that: The research conducted and writing of this report was under my supervision. Name: Madam. Nor Surayati Binti Mohamad Usop Date: ii

DEDICATION First of all, I am thankful to Almighty Allah the Most Gracious and the Most Merciful, who give me strength and patience to work and finish this proposal report. I would like to take the opportunity to express my heartiest gratitude to my supervisor, Madam Nor Surayati for the support, patience, guidance and invaluable advice. Besides, I would like to thank all panel of Faculty Informatics and Computing and other lecturers like Sir Faisal Amri Bin Abidin @ Bharun for guide me for the guidance to help me to complete this final year project. Last but not least, a big thanks to my family and friends that always give me great support and encouragement along the journey in completing of project. iii

ABSTRACT Nowadays, boarding school uses outing card for the students to go outing. Before they go outing they need to fill in the card and warden needs to stamp on it as an approval to go outing. However, some student outing without getting stamp from warden because they had no time as they must wait for warden s approval. This will cause the problem later because the student goes outing without permission. Besides, outing card possibly lost due to irresponsible action from student or warden themselves. To overcome these problems, a web-based system can help the warden to overcome these problems in which student can go outing without get stamp from warden as they only need to add on the system before and after add outing and warden will approve their outing through the system. They can view the student s outing activity from the report. Besides, the parent of student also can view their children outing activity. iv

ABSTRAK Pada masa kini, sekolah asrama menggunakan kad outing untuk pelajar keluar. Sebelum mereka keluar, mereka perlu mengisi kad dan warden perlu menandatanganinya sebagai kelulusan untuk keluar. Walau bagaimanapun, sesetengah pelawat pelajar keluar outing tanpa mendapatkan cop dan tanda tangan daripada warden kerana mereka perlu menunggu untuk mendapatkan kelulusan warden. Ini akan menyebabkan masalah berlaku apabila pelajar keluar tanpa izin. Selain itu, kad outing mungkin hilang disebabkan oleh tindakan yang tidak bertanggungjawab daripada pelajar atau warden sendiri. Untuk mengatasi masalah ini, sistem berasaskan web boleh membantu warden untuk mengatasi masalah ini di mana pelajar boleh keluar tanpa mendapatkan cop dari warden kerana mereka hanya perlu menambah aktiviti outing di dalam sistem sebelum mereka keluar dan warden akan meluluskan aktiviti outing mereka melalui sistem. Warden juga boleh melihat status keluar sama ada pelajar kembali atau tidak dari laporan outing. Selain itu, ibu bapa pelajar juga dapat mengetahui aktiviti outing anak-anak mereka. v

TABLE OF CONTENT DECLARATION CONFIRMATION DEDICATION ABSTRACT ABSTRAK TABLE OF CONTENT PAGE i ii iii iv v vi CHAPTER 1 INTRODUCTION 1 1.1 Project Background 1 1.2 Problem Statement 2 1.3 Objective 2 1.4 Scope 3 1.5 Expected Outcome 4 1.6 Limitation of Work 5 1.7 Report Structure 5 CHAPTER 2 LITERATURE REVIEW 7 2.1 Introduction 7 2.2 Literature Review 7 2.2.1 Existing Outing System 7 2.2.2 Staff Attendance System 8 2.3 Summary 9 CHAPTER 3 METHODOLOGY 10 3.1 Introduction 10 3.2 Justification Selection 10 3.3 Project methodology 11 3.4 Context Diagram 13 3.5 Data Flow Diagram (DFD) 14 3.5.1 Data Flow Diagram Level 0 14 3.5.2 Data Flow Diagram Level 1 17 3.6 Entity-Relationship Diagram 21 (ERD) 3.7 Database Design 22 3.8 System Requirement 24 3.8.1 Software Requirement 24 3.8.2 Hardware Requirement 25 3.9 Conclusion 25 CHAPTER 4 MODELLING AND DESIGN 26 4.1 Introduction 26 4.2 Test Result (Interface) 26 4.2.1 Student Module 26 4.2.2 Warden Module 31 4.2.3 Parent Module 34 4.3 Test Cases 37 vi

4.3 Conclusion 42 CHAPTER 5 CONCLUSION 43 5.1 Introduction 43 5.2 Project Contribution 43 5.3 Project Constraint and Limitation 43 5.4 Future Work 44 5.5 Conclusion 44 Reference 46 vii

LIST OF TABLES TABLE TITLE PAGE 3.1 First table in chapter 3 22 3.2 Second table in chapter 3 22 3.3 Third table in chapter 3 23 3.4 Forth table in chapter 3 23 4.1 First table in chapter 4 37 4.2 Second table in chapter 4 38 4.3 Third table in chapter 4 38 4.4 Forth table in chapter 4 39 4.5 Fifth table in chapter 4 39 4.6 Sixth table in chapter 4 39 4.7 Seventh table in chapter 4 40 4.8 Eight table in chapter 4 40 4.9 Ninth table in chapter 4 41 4.10 Tenth table in chapter 4 41 4.11 Eleventh table in chapter 4 41 4.12 Twelfth table in chapter 4 42 4.13 Thirteenth table in chapter 4 42 viii

LIST OF FIGURES FIGURE TITLE PAGE 2.1 First figure in chapter 2 8 3.1 First figure in chapter 3 11 3.2 Second figure in chapter 3 13 3.3 Third figure in chapter 3 15 3.4 Forth figure in chapter 3 18 3.5 Fifth figure in chapter 3 19 3.6 Sixth figure in chapter 3 20 3.7 Seventh figure in chapter 3 21 4.1 First figure in chapter 4 26 4.2 Second figure in chapter 4 27 4.3 Third figure in chapter 4 28 4.4 Forth figure in chapter 4 28 4.5 Fifth figure in chapter 4 29 4.6 Sixth figure in chapter 4 29 4.7 Seventh figure in chapter 4 30 4.8 Eighth figure in chapter 4 31 4.9 Ninth figure in chapter 4 32 4.10 Tenth figure in chapter 4 32 4.11 Eleventh figure in chapter 4 33 4.12 Twelfth figure in chapter 4 33 4.13 Thirteenth figure in chapter 4 34 4.14 Fourteenth figure in chapter 4 34 4.15 Fifteenth figure in chapter 4 35 4.16 Sixteenth figure in chapter 4 36 ix

4.17 Seventeenth figure in chapter 4 36 x

LIST OF APPENDICES APPENDIX TITLE PAGE A Appendix 1 48 B Appendix 2 50 xi

CHAPTER I INTRODUCTION 1.1 BACKGROUND Outing is a one part of the activity that each boarding school record to know the information of student who going outing. It managed by student and warden themselves at each boarding school. In a manual outing management system, student need stamp on their outing book before go outing. This will require some time to student to get a stamp and warden that need to stamp on it as a permission for student to go outing. So, to overcome the problem of outing management, we need to build a database for the management of outing Boarding School Outing Management System(BSOMS) is a system for the boarding school student that can ease the outing management. BSOMS act as record keeper for warden to analyse the student. Next, BSOMS also helps warden to monitor outing activity more efficient compared to manual system using the system. When student using an outing online system they only need to add on their outing activity whether weekly outing, co-curriculum activity or emergency. Besides, they need choose the date and time when they want to go out. When a student adds their outing activity, the warden will approve through the system. Moreover, warden can view the report to analyse the student who going to outing on that week. 1

The system is developed using PHP for web development and MySQL as the database platform. 1.2 PROBLEM STATEMENT The problem about this project is student need a stamp drop as approval from warden to go outing and outing card possibly lost due to irresponsible action of the student their self. Next, when the outing card lost student need to buy the new one from the cooperative of the school. So, they need to spend some money to buy new outing card. Then, the process of manual management is time consuming especially when it involves large number of student. 1.2 OBJECTIVE Besides overcoming all the problems on the current techniques, there are the objectives that wish to accomplish by the system: To design an outing system for high school hostel. To develop a system that can manage outing activity of boarding school student of SMK Tembila. To test the functionality of Boarding School Outing Management system (BSOMS). 2

1.3 SCOPE This scope explains about the user that involved in the system and also the function that existed in the system. This system will develop to warden as admin and student. The scope is divided into two parts as user and system scope. 1.4.1 SCOPE FOR USER i. Admin (warden) The person who will control this system and update the system based on situation. People who responsible to register student, parent and new admin. People that update the student outing record every week. ii. Student (hostel student) User need to log in to the system first. Next, add the outing activity before and after they go outing. User also able to view approval from warden in this system. 1.4.2 SCOPE FOR SYSTEM Login -There is login and registration to enter this system based on type of user. 3

Manage Profile -User can update their own profile by themselves. Add outing activity -Student can add their outing activity before and after go outing. Manage staff -Admin can add new warden for this system. Manage outing information -Admin will update the information of outing in this module every week. View report -Admin able to view the report outing activity of each student. 1.5 EXPECTED OUTCOME This system is capable to manage outing activity of SMK Tembila. Student can add their own outing activity before going and after going outing. Then, the warden can 4

approve the outing when student add new outing activity. Lastly, this system able to function as outing card as in outing manual system. 1.6 LIMITATION OF WORK Boarding School Outing Management System(BSOMS) is provided for SMK Tembila s student. The outing activity is based on outing activity of SMK Tembila, which means this system suitable for this hostel school only and other hostel school that have same outing activity as SMK Tembila. The system only can be accessed by warden, parent and student that stay in the hostel. 1.7 REPORT STRUCTURE This report contained 5 chapters. In chapter one, it contains introduction of the system, system background, problem statement, objective, scope, limitation of work and thesis structure. While in chapter two, there are literature review of some research paper related to the proposed system. It contains introduction of the literature review, E-Outing system will be used for this proposes system and conclusion. In the chapter three, there are description of methodology that will be used for this proposed system. It explains the process of the system in every stage. There are Context Diagram (CD), Data Flow Diagram (DFD) level 0 and level 1, framework that 5

show the flow of process in the system and ERD that show relationship between entities of the system which will describe how the system worked. Next, in chapter four, it consists interface and user manual of the system. Each interface is labelled and explained specifically and properly. In chapter five, there are test cases of the system. The result from system testing are included in this chapter. Besides, there are project contribution, project constraints and future of the system. The conclusion from the system has been discussed, concluded and summarised. 6

CHAPTER 2 LITERATURE REVIEW 2.1 INTRODUCTION A literature review is a body of text that aims to review the critical points of current knowledge on particular topic. Most often associated with science-oriented literature, such as a thesis, the literature review usually precedes a research proposal, methodology and results section. Its ultimate goal is to bring the reader up to date with current literature on a topic and forms the basis for another goal, such as future research that may be needed in the area. 2.2 LITERATURE REVIEW Boarding School Outing Management System is based on literature review which is existing outing system and the other system that use same concept as outing system. 2.2.1 E-Outing System E-Outing System already been used for boarding school. From the observation, I take Sekolah Menengah Sains Dungun (SMSD) that already use this system for example [1]. In this system there are form for outing, approval status checking, approval of outing from warden, and merit record. All the menus state above can be viewed at: 7

Figure 1 Example of Outing System in SM Sains Dungun Based on the observation, we can conclude that enhancement can be made by add notify the admin or warden when student fill the form as warden can know about it. Then they can give their approval without have to check up the system every minute to know if there any student has add their outing activity in the system. Besides, student should also can view if they have merit or not before applying the next outing activity. 2.2.2 Staff Attendance System using RFID Staff Attendance System is a system to monitor the staff attendance to daily work. This system uses RFID. The proposed system used the system passive to record staff attendance. Frequency identification technology will read the staffs tag and the attendance are recorded automatically and store it in database. RFID system consists various components that are connected to one another by a dedicated communication path. 8

In manual way, Staff Attendance is recorded using paper card such as Bundy Clock a stamping [2]. Automated system uses a device to verify the identity of the person such as electronic tags or barcode badges. Since the attendance need to be recorded by staff their self every day, there will be possibly they forget to record. If staff did not record the attendance more than 3 times they will get warning letter. This system concept is same as outing manual system. Student need to record their outing activity in the outing book or card as evidence before they go outing. If they did not record their outing activity and have been caught they are outing, then they will be getting warning letter from hostel later. 2.3 SUMMARY After going through two things, we can see outing system is contain same concept as staff attendance system. In staff attendance system, staff need to record their attendance everyday while in outing system, student in boarding school need to record their outing activity as evidence before they can go outing. Lastly, the parent also can know when and where their child goes outing. 9

CHAPTER 3 METHODOLOGY 3.1 INTRODUCTION This chapter explains the methodology design that being applied in the software development. Boarding School Outing Management System will undergo some phases from the beginning until project submission. In this chapter, the modelling and design is also being explained to give the overall view on how this system including database works. The modelling and design is shown by the Entity Relationship Diagram(ERD), context diagram and Data Flow Diagram which are provided in this chapter. Besides, this chapter also explain the model of methodology that able help developer manage project efficiently and able to achieve objective and scope of this project. 3.2 JUSTIFICATION SELECTION For this proposed system, we use Software Development Life Cycle which is Waterfall Model[3]. Waterfall model has been widely used for system development life cycle to create a system with a linear and sequential approach. There are many advantages of using Waterfall Model because it is very simple to understand and use. 10

Figure 3.1: Waterfall Model 3.3 PROJECT METHODOLOGY In Boarding School Outing Management System(BSOMS), Waterfall Model has been chosen as a methodology. There are six phase that involved in the waterfall model that include requirement gathering and analysis, System design, Implementation, Testing, Deployment of system and maintenance. 1) Requirement Analysis The phase start with brainstorming the ideas of current problem and system request. Besides, meet up with user to know the detail requirement for this system. In this phase also, the requirement gathering is been discuss with supervisor to conclude the requirement suitable for the system [4]. 11

2) System Design The requirement specifications from first phase are studied in this phase and the system design is prepared. This system design helps in specifying hardware and system requirements and helps in defining the overall system architecture. 3) Implementation The inputs from the system design are converted, to small program called unit in first developed then it will have integrated in the next phase. Each unit is developed and tested for its functionality, which is referred to as Unit Testing. 4) Testing All the unit in implementation phase are integrated into system after testing of each unit. Any change of coding, error, functionality or upgrades are also will be tested. User Interface will be checked to ensure they are connected to database and appropriate with the system. 5) Deployment of System Once the functional and non-functional testing is done; the product is deployed in the customer environment or released into the market 12

6) Maintenance After the system deploy in the customer environment, there will be some issue arise. To fix those issue patches are released to enhance the functionality of the system to better version. 3.4 CONTEXT DIAGRAM Context diagram is a diagram that defines the boundary between the system, or part of a system, and its environment, showing the entities that interact with it. [4] Figure 3.2: Context Diagram of the system. 13

Figure 3.2 show the data flow in Boarding School Outing Management System. There are three main users which is student, warden and parent. This diagram shows the data flow involving those three main users. Users are required to register, and login to access the system. 3.5 DATA FLOW DIAGRAM(DFD) A data flow diagram (DFD) maps out the flow of information for any process or system. It uses defined symbols like rectangles, circles and arrows, plus short text labels, to show data inputs, outputs, storage points and the routes between each destination. [5] 3.5.1 DATA FLOW DIAGRAM LEVEL 0 Data flow diagram is a two-dimensional diagram that explains how data processed and transferred into the system. Figure 3.3 show the Data Flow Diagram level 0 for the Boarding School Outing Management System. Since the Figure 3.3 has been explained the flow of the actors which Student, Warden and Parent is, in this chapter, the more details about the flow will be explained with DFD LEVEL 0 and following by DFD LEVEL 1. The functionality for each process also will be described and able ensure that developer understand their system. 14

Figure 3.3: Data Flow Diagram (DFD) Level 0 of this system. According to the DFD in Figure 3.3 above, there are three main entity which is WARDEN, STUDENT and PARENT. The process of the system is LOGIN, MANAGE PROFILE, MANAGE OUTING, and MANAGE REPORT. Next, the data stores for the Boarding School Outing Management System are WARDEN, STUDENT, PARENT, and OUTING. 15

Process 1.0: Login In Login process, WARDEN, STUDENT and PARENT input LOGIN DETAIL into LOGIN process and the output is LOGIN DETAIL into three data store which is WARDEN, STUDENT and PARENT. Process 2.0: Manage Profile In Manage profile process, WARDEN input WARDEN DETAIL into MANAGE PROFILE, then output WARDEN RECORD into WARDEN data store and invoke WARDEN RECORD input into MANAGE PROFILE process which output WARDEN RECORD into WARDEN. STUDENT also input STUDENT DETAIL into MANAGE PROFILE and output STUDENT RECORD into STUDENT data store the from data store STUDENT, invoke STUDENT RECORD into MANAGE PROFILE process which output STUDENT RECORD into STUDENT. Process 3.0: Manage Outing In Manage Outing process, STUDENT input REQUEST OUTING into MANAGE OUTING process. Then, MANAGE OUTING process will output OUTING RECORD into data store OUTING, invoke OUTING RECORD into MANAGE OUTING and MANAGE OUTING process output OUTING RECORD to WARDEN and WARDEN will output OUTING CONFIRMATION and the OUTING RECORD is input into OUTING data store again. Then, PARENT input REQUEST OUTING REPORT into MANAGE OUTING process and MANAGE OUTING process will output OUTING 16

RECORD into data store OUTING, invoke OUTING RECORD into MANAGE OUTING and MANAGE OUTING process output OUTING REPORT to parent. Process 5.0: Manage Report In Manage Report process, WARDEN data store input WARDEN RECORD, STUDENT data store input STUDENT RECORD, PARENT data store input PARENT RECORD and OUTING data store will input OUTING RECORD into MANAGE REPORT process and output REPORT RECORD to WARDEN entity. 3.5.2 DATA FLOW DIAGRAM LEVEL 1 Data Flow Diagram Level 1 shows the processes in DFD Level 0. There are DFD Level 1 of Register, Manage Profile and Manage Outing. 17

3.5.2.1 Manage Profile Figure 3.4: DFD Level 1 of Manage Profile process In the process of Manage Profile as shown in Figure 3.5, warden is required to enter warden details such as warden ID, warden Name, password, birth date, gender, address, phone no, and email. Then after submitting the edit profile form, the data will be stored in the database and the system will show detail to warden. Then, from data store Warden, the Warden detail will be input into view updated detail and the process of view updated detail will be output the warden record to warden. 18

Figure 3.5: DFD Level 1 of Manage Profile process In the process of Manage Profile as shown in Figure 3.5, Student is required to enter warden details such as Student ID, Student Name, password, birth date, gender, address, phone no, and email. Then after submitting the edit profile form, the data will be stored in the database and the system will show detail to warden. Then, from data store Student the Student detail will be input into view updated detail and the process of view updated detail will be output the student record to student. 19

3.5.2.2 Manage Outing Figure 3.6: DFD Level 1 of Manage Outing process In the process Manage Outing, the SMS-Gateway is used as a technique to send SMS notification from web server to handphone. SMS-Gateway will use Outing Request from student data store. Student is required to insert Outing detail to request outing. Then from process Request Outing, it will output Outing Record Request into View Outing Confirmation. Warden will be managed outing to give outing approval. Lastly, Parent can view the outing report. 20

3.6 Entity Relationship Diagram (ERD) Entity Relationship Diagram (ERD) consist of identifying and defining the entities, determine entities interaction and the cardinality of the relationship. This ERD show the entity of the system and the interaction of each table. Figure 3.7: Entity-Relationship Diagram (ERD) of the system ERD in Figure 3.7 shows the entities relationship from one table to another table. There are four table in the ERD above which is STUDENT, PARENT, WARDEN and OUTING. 21

3.7 Database Design Database design is important to ensure the flow of data in the system are save and display properly in the system. In this section, the basic structure of the tables composing the database for the project are shown along with information about primary and foreign key. Table Name: warden Description: This table keeps personal data about warden of SMK Tembila. This data enters by administrator of the school and be kept in the database for the login authentication and edit profile warden. Attribute Description Type Size Remark WardenID ID of warden varchar 10 NN, PK, UNIQUE WardenName Warden Full Name varchar 40 NN Pwd Warden s account Password varchar 10 BirthDate Birthdate of Warden date gender Gender of Warden varchar 1 address Address of Warden varchar 40 phone_no Phone number of Warden int 12 email Warden s email varchar 20 Table 3.1: warden data entity Table Name: student Description: This table keeps personal data about student of SMK Tembila who stay in hostel. This data enters by administrator of the school and be kept in the database for the login authentication and edit profile student. Attribute Description Type Size Remark StudentID ID of student who stay in hostel. varchar 10 NN, PK, UNIQUE StudentName Student full name varchar 20 NN Pwd Student s account password varchar 10 BirthDate Student s birthdate varchar 15 gender Student s gender varchar 1 address Student s address varchar 40 phone_no Student s phone number int 12 Table 3.2: student data entity 22

Table Name: parent Description: This table keeps personal data about parent of student of SMK Tembila who stay in hostel. This data enters by administrator of the school and be kept in the database for the login authentication. Attribute Description Type Size Remark IC_Num The IC number of parents. varchar 20 PK, NN, UNIQUE Parent_Name Parent s name varchar 10 StudentName Their child name who stay in hostel varchar 40 Pwd Parent s account password varchar 10 Gender Parent s gender varchar 1 Address Parent s address varchar 40 phone_no Parent s phone number int 12 email Parent s email varchar 20 Table 3.3: parent data entity Table Name: outing Description: This table keeps personal data about outing activity of SMK Tembila student. This data enters by student and be kept in the database to be approve and view by warden and parent. Attribute Description Type Size Remark OutingID ID of outing activity int 3 PK, NN, AI StudentID ID of student who stay in hostel. varchar 10 FK WardenName Name of Warden that responsible for varchar 14 outing activity on that week Outing_type Type of outing activity varchar 20 Outing_desc Reason of outing varchar 20 DateOfOuting Date of student go outing date Time_out Time of student go outing time DateOfReturn Date of student return from outing date Time_in Time of student return from outing time status Status of outing activity varchar 20 Table 3.4: outing data entity 23

3.8 System Requirement In order to develop the system, software and hardware are required. Below are the list of software requirements and hardware requirement which are been used to develop the system efficiently. 3.8.1 Software Requirement 1. Microsoft Word 2016 - Tools for writing report and proposal 2.Microsoft PowerPoints 2016 - Tools for preparing the slideshow presentation 3.XamppServer - Tools for connecting with MySQL database - Tools that support PHP programming 4.Lucid - Tools for designing and draw diagram such as CD and DFD. 5.Snipping Tool -Tools for print screen and cropping image 6.UC Browser 24

-Tools platform to display the system. 7.Dropbox -Tools for cloud storage of backup data. 3.8.2 Hardware Requirement 1. Laptop - The laptop used was Lenovo Idea pad 310 with DDR4 memory, 64-bit 2. Printer Operating System. - Canon E400 series printer was used to print document (proposal and final report) 3.9 Conclusion Every phase is crucial to ensure the development of the proposed system will be implemented correctly. Waterfall model approach is suitable development model to follow with the system development for this proposed system Next, the design methods and system design like context diagram, data flow diagram and entity relationship diagram in this chapter explained the data flow of the system on how the system are working. 25

CHAPTER 4 MODELLING AND DESIGN 4.1 INTRODUCTION This chapter will be explained the implementation of system and the input and output of the system during testing phase. Interfaces and user manual of the system are included in this chapter for user understanding how the system work. 4.2 TEST RESULT (INTERFACE) Test result interface consist of result interface of the system. There are three module interfaces in this test result which is Student Module, Warden Module and Parent Module. 4.2.1 STUDENT MODULE Student Module consist the interface of system function that can be access by student through the system. 4.2.1.1 INTERFACE: HOMEPAGE Figure 4.1 Homepage 26

Figure 4.1 shows the homepage interface of the system. The system provides about Home, Warden, Student and Parent option on the menu bar. Student need to choose Student menu to login to the system. 4.2.1.2 INTERFACE: LOGIN Figure 4.2 Login Interface Figure 4.2 shows the login interface of the system. When the student click the Login button login form will be pop out. Student is required to enter their ID to login to the system. The system is only accepted registered StudentID so it can verify the StudentID and password. 27

4.2.1.2.1 INTERFACE: LOGIN FAILED Figure 4.3 Login Failed Figure 4.3 shows the failed login to the system. Student cannot be login the system since the system cannot verify the StudentID and password that enter by the Student. The message pops up when the user enters invalid StudentID and password to inform the user. 4.2.1.3 INTERFACE: EDIT USER PROFILE Figure 4.4 Student Profile Figure 4.4 show Student profile interface of the system. Student can alter the input which they would like to edit and click button CONFIRM. After Student click the 28

CONFIRM button they can view their profile that have been edited as in Figure 4.5. While, the button RESET is when Student want to reset the detail as before they edit and CANCEL button is for Student who feel no need to edit their profile at that time and go back to homepage. Figure 4.5 Updated Student Profile 4.2.1.4 INTERFACE: ADD OUTING Figure 4.6 Add Outing 29

Figure 4.6 show add outing form. If the Student want to add their new outing activity their need to fill in the form. Student need to choose the warden name that duty on that week for WARDEN NAME on the form. Then Student also need to choose outing type either BACK HOME, WEEKLY OUTING and EMERGENCY. BACK HOME is suitable when school have public holiday and Student can back home for few days. While, WEEKLY OUTING is the half-day outing on every week. Lastly, the EMERGENCY is for emergency case as Student need to be admitted to hospital suddenly. Student need to fill in all attribute in the form. As an addition, DATE OF RETURN and TIME IN in the form is expected date and time that Student will be return to hostel. When Student click the CONFIRM button there will be pops up message that tell outing activity is successfully registered. 4.2.1.5 INTERFACE: DISPLAY OUTING Figure 4.7 Outing Detail Figure 4.7 show the outing detail of Student that have been add outing. Student can view their outing activity whether have been approve or not by warden by click the 30

Status menu. If their outing activity did not been approve yet, they can delete their outing activity. If their outing activity have been approved they can print the outing detail as an evidence for their outing. 4.2.2 WARDEN MODULE Warden Module consist of the interface of system function that can be access by warden through the system. 4.2.2.1 INTERFACE: LOGIN Figure 4.8 Login Interface Figure 4.8 shows the login interface of the system. After Warden click Warden at menu bar in homepage of the system, it will go to warden homepage. There is login button in menu bar and when the Warden click the Login button, login form will be pop out. Warden is required to enter their ID to login to the system. The system is only accepted registered WardenID, so it can verify the WardenID and password. 31

4.2.2.1.2 INTERFACE: LOGIN FAILED Figure 4.9 Login Failed Figure 4.9 shows the failed login to the system. Warden cannot be login the system since the system cannot verify the WardenID and password that enter by the Warden. The message pops up when the user enters invalid WardenID and password to inform the user. 4.2.2.2 EDIT PROFILE WARDEN Figure 4.10 Edit Profile Warden Figure 4.10 show Warden profile interface of the system. Warden can alter the input which they would like to edit and click button CONFIRM. After Warden click the 32

CONFIRM button they can view the profile that have been edited as in Figure 4.11. While, the button RESET is when Warden want to reset the detail as before they edit and CANCEL button is for Warden who feel no need to edit their profile at that time and go back to homepage. Figure 4.11 Updated Warden Profile 4.2.2.3 INTERFACE: APPROVE OUTING Figure 4.12 Display Outing Figure 4.12 show approve student s outing activity page. Warden need to approve Student outing activity for Student to go outing. Warden can click the update button then go to another page that they can choose status of outing either Approve or Reject as in Figure 4.13. Then the status of student outing activity will be updated. 33

Figure 4.13 Approve Outing status 4.2.2.3 INTERFACE: REPORT Figure 4.14 Outing Report Figure 4.14 show Outing Report which is detail of outing activity of student. Warden can view the detail of outing when Warden choose Report menu. 4.2.3 PARENT MODULE Parent Module consist of the interface of system function that can be access by parent through the system. 34

4.2.3.1 INTERFACE: LOGIN Figure 4.15 Login Interface Figure 4.14 shows the login interface of the system. After Parent click Parent at menu bar in homepage of the system, it will go to parent homepage. There is login button in menu bar and when the Parent click the Login button, login form will be pop out. Parent is required to enter their IC Number to login to the system. The system is only accepted registered IC Number, so it can verify the IC Number and password. 35

4.2.3.2 INTERFACE: VIEW OUTING ACTIVITY Figure 4.16 View Outing Activity Figure 4.16 shows view outing activity page. When Parent click the Outing button they will come to this page. Parent need to choose their child StudentID to view their children outing record. After choosing the StudentID they must click CONFIRM button then they can view their child s outing record as in Figure 4.17. Figure 4.17 Detail Outing 36

4.3 Test Cases Test case is to ensure the Boarding School Outing Management System is developed according to requirement and achievement the objective of this system. Test cases can help out configure the problem of the system. Input, action, event or unexpected response of the system will be described in test cases in this chapter. The tables below show the test cases for the several processes of the system. 4.3.1 Student Module Test Cases for Login Step Test Procedure Expected Result Result 1. Student click Student menu System will go to Homepage Success in Main page of the system. of Student. 2. Student click Login button from Homepage Success System Display login form consist of StudentID, and password. 3. Student enter StudentID and password. 4. Student click Login button. Validation: If Student enter wrong StudentID and password, system display a message pop-up StudentID or password is wrong. If student click the login button with empty form, system display pop-up message to fill out the StudentID and password to login. Else, system will redirect to Student Homepage interface. Table 4.1 Test Case for Student Login Success Success Test Cases for Update Profile Step Test Procedure Expected Result Result 1. Student click System will display Success Profile menu in Student homepage. Student profile in a form. 37

2. Student changes any data 3. Student click Update button. A pop-up message displayed Update Profile Successfully and data is updated to the database and system displayed the updated profile. Table 4.2 Test Case for Student Update Profile Success Test Cases for Add Outing Step Test Procedure Expected Result Result 1. Student click System display Success Outing menu. 2. Student fill in the form. 3. Student click Confirm button to submit the outing form. outing form for student who wish to go outing. System will pop-up Data successfully added and data will be insert into the database. If Student did not fill in the form fully there will be popup message Please fill out this field. Table 4.3 Test Case for Student Add Outing Success Test Cases View Outing Status Step Test Procedure Expected Result Result 1. Student click System display Success Status menu. outing detail of student and there will be Delete 2. Student can choose Delete button to delete the outing detail if their 38 and Print button. System will be deleting the outing detail when Success

outing not approve yet. If the outing has been approve they can choose Print button. Student choose Delete button. Else, system will be display outing detail document when Student choose Print button. Table 4.4 Test Case for View Outing Status Failed Test Cases for Logout Step Test Procedure Expected Result Result 1. Student click System display Success Logout menu. Student Homepage. Table 4.5 Test Case for Logout 4.3.2 Warden Module Test Cases for Login Step Test Procedure Expected Result Result 1. Student click Warden System will go to Homepage Success menu in Main page of the of Warden. system. 2. Student click Login button from Homepage System Display login form consist of WardenID, and password. 3. Student enter WardenID and password. 4. Student click Login button. Validation: If Warden enter wrong WardenID and password, system display a message pop-up WardenID or password is wrong. If student click the login button with empty form, system display pop-up message to fill out the WardenID and password to login. Else, system will redirect to Warden Homepage interface. Table 4.6 Test Case for Student Login Success Success Success 39

Test Cases for Update Profile Step Test Procedure Expected Result Result 1. Warden click System will display Success Profile menu in Student homepage. Warden profile in a form. 2. Warden changes any data 3. Warden click Update button. A pop-up message displayed Update Profile Successfully and data is updated to the database and system displayed the updated profile. Table 4.7 Test Case for Student Update Profile Success Test Cases for Approve Outing Step Test Procedure Expected Result Result 1. Student click System display Success Outing menu. outing detail of Student outing who did not been 2. Warden click Approve button. 3. Warden choose the Outing status. approved yet. System will go to another next page. In this page Warden need to choose the status whether approve of reject the outing. System will pop-up Approve outing Successfully and the status of outing will be updated into the database. Table 4.8 Test Case for Approve Outing Success Success 40

Test Cases for Report Outing Step Test Procedure Expected Result Result 1. Warden click System display Success Report menu. outing detail of Student outing. Table 4.9 Test Case for Report Outing Test Cases for Logout Step Test Procedure Expected Result Result 1. Warden click System display Success Logout menu. Student Homepage. Table 4.10 Test Case for Logout Test Cases for Login Step Test Procedure Expected Result Result 1. Parent click Parent menu in System will go to Homepage Success Main page of the system. of Parent. 2. Parent click Login button from Homepage Success System Display login form consist of IC Number, and password. 3. Parent enter IC Number and password. 4. Parent click Login button. Validation: If Parent enter wrong IC Number and password, system display a message pop-up IC Number or password is wrong. If student click the login button with empty form, system display pop-up message to fill out the IC Number and password to login. Else, system will redirect to Parent Homepage interface. Table 4.11 Test Case Parent Login Success Success Test Cases for View Outing Activity Step Test Procedure Expected Result Result 1. Parent click System will be Success Outing menu. display form which is Parent need to 41

choose their child s StudentID. System will go to another next page. In this page Parent can view their children outing activity. There is Print button to print the outing detail. System will be display outing document to be print out. Table 4.12 Test Case for Parent View Outing 2. Parent click Approve button. 3. Parent click Print button Success Fail Test Cases for Logout Step Test Procedure Expected Result Result 1. Parent click System display Success Logout menu. Student Homepage. Table 4.13 Test Case for Parent Logout 4.3 Conclusion The interface and user manual described the functions and the flow of the system. User will be able to use the system properly if they follow the user manual. The information of the implementation of the system is delivered by using test cases. The main functionality of the system has been tested for its capability on carrying multiple tasks and the test results come back mostly positive. 42

CHAPTER 5 CONCLUSION 5.1 INTRODUCTION This chapter focused on project contribution, constraints of the project and its conclusion, 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 Boarding School Outing Management System was successfully developed before its timeline. This system very useful to another people. Warden in boarding school can manage their outing activity with efficient. Not only the warden, but the student also feel ease to go outing by use the system. This system help student to record their outing activity using the system. This system also eases the warden and parent to check outing activity of student by view the report of outing student. 5.2 PROJECT CONSTRAINTS AND LIMITATION Every system must be having its own obstacle or difficulties in developing the system. It can occur on developing phase or design phase. This constraint can affect the schedule for developing system. 43

For this system, the difficulties that has been faced is to upgrade the system into mysqli. Although already found the suitable way, there will be possibility network error and server down because the system is depend on the server and network connection. Besides, the system unable to detect the student who cancel their outing once the outing activity have been approved. 5.3 FUTURE WORKS In the future, there are still a lot work can be made into this system. Firstly, for the risk network, the paginations should be done to make friendly viewed by user. Next, more information should be added in the system and Student should be able to cancel the outing if something happens last minute. Then, the system should have SMS notification to notify Warden when student add new outing activity and to notify parent about their child outing activity. Lastly, the system should be having its security to improve its user privileges. 5.4 CONCLUSION As conclusion, the outing system should be applied in each boarding school to ease the warden and student to manage the outing in efficient way. Besides, parent can know their children activity from the system itself. Then Student, Warden and Parent can use this system because this system already achieved its objectives. However, the Student and Parent still need refer to warden if any change in system happen. Since the warden required some time in manual way to stamp the outing book and audit the report of 44

student outing activity to be send to head of school, hopefully the system can short the consuming time with precise result. 45

REFERENCES 1) Norarina Ezzati Johan, Nor Azila Awang Abu Bakar and Nik Marsyahariani Nik Daud.2018.http://journaleacademiauitmt.uitm.edu.my Accessed 8 August 2018 2) Muhammad Thariq Abdul Razak and Chuah Chai Wen, 2018. Staff Attendance System Using RFID 3) Sharma, L. (2018). WaterFall Model in Software Developement Life Cycle SDLC. 4) SDLCWaterfallModel,2018.https://www.tutorialspoint.com/sdlc/sdlc_waterfal l_model.html Accessed 8 August 2018 5) Lucidchart,2018.https://www.lucidchart.com/pages/data-flow-diagram> Accessed 8 August 2018 46

APPENDIX A: GANT CHART FYP 1 47

APPENDIX A: INTERVIEW QUESTION 48

APPENDIX B: GANTT CHART FYP 2 TASK/WEEK 1 2 3 4 5 6 7 8 Project Meeting with Supervisor Project Development Progress presentation Project Testing & Project Meeting with Supervisor Project Testing (Continue) & Project Meeting with Supervisor Submission draft report Project meeting with supervisor Final Presentation Submission Final Report 49