UNISZA AUDITORIUM & HALL MANAGEMENT SYSTEM

USING PRIORITY SCHEDULING

SITI NOR SHUHADA BINTI MOHAMAD (BTAL16044385)

Bachelor of Computer Science (Software Development)

Faculty of Informatics and Computing

University Sultan Zainal Abidin, Terengganu, Malaysia

2018
 DECLARATION

I hereby declare that the work have been done by myself and no portion of the work

contained in this thesis has been submitted in support of any application for any other degree

or qualification of this or any other university or institute of learning.

Name: Siti Nor Shuhada Binti Mohamad

Date: 27/12/2018

i
 CONFIRMATION

This project report titled UniSZA Auditorium & Hall Management System was

prepared and submitted by Siti Nor Shuhada Binti Mohamad (044385) and has been found

satisfactory in terms of scope, quality and presentation as partial fulfilment of the requirement

for the Bachelor of Computer Science (Software Development) with honours in University

Sultan Zainal Abidin.

Supervisor: Mr. Mohd Isa Bin Awang

Date:

ii
 ACKNOWLEDGEMENT

I would like to acknowledge and extend my heartfelt gratitude to the following

persons who have made the completion of this project possible. I would like to express my

gratitude to my supervisor, Mr. Mohd Isa Bin Awang for his invaluable advice, guidance and

his enormous patience throughout the development of the research. In addition, I would also

like to express my gratitude to my loving family who had helped and given me

encouragement, support and motivation.

Special thanks also go to all of my friends for the additional information that really

helps in understands this project well. Finally, I would like to give my greatest honour to God

who made all things possible.

iii
 ABSTRACT

The process of booking auditorium and hall is a frequent and important activity in any

areas in University of Sultan Zainal Abidin (UniSZA). But the process becomes very

tiresome and time consuming when there is no proper and convenient system. Manual

booking system which is currently used has a lot of limitations to the student and staff. Some

of them end up booking the places they don’t prefer simply because they don’t have full

information about the available auditorium and hall, and also the booking process requires

their physical presence. There are cases where student book but fail to show up thereby cause

a lot of inconvenient. In some auditorium and hall booking is done via phone without any

commitment made which is not aptly effective but online booking system seeks to remedy

this citing its traits of simplicity, accuracy and efficiency.

Hence, to deal with this problem, a UniSZA Auditorium & Hall Management System

(UAHMS) will be very necessary. Online booking system is accessed on internet by using

devices which have internet connection at any time. UAHMS is a convenient and an efficient

way to deal with this problem. The booking process in UniSZA community is manual file

system which is quite inconvenient. The UAHMS will enable student and staff access details

of auditorium and hall online and also do the booking online. The system will have all the

necessary information about auditorium and hall areas within UniSZA community on one

single website which accessible by student and staff of UniSZA who wants to book it.

iv
 ABSTRAK

Proses tempahan auditorium dan dewan adalah aktiviti yang kerap dan penting

dalam kawasan Universiti Sultan Zainal Abidin (UniSZA). Tetapi prosesnya menjadi sangat

memenatkan dan memakan masa apabila tidak ada sistem yang tepat dan mudah. Sistem

tempahan manual yang kini digunakan mempunyai banyak batasan kepada pelajar dan staf.

Sesetengah daripada mereka akhirnya menempah tempat yang mereka tidak suka kerana

mereka tidak mempunyai maklumat yang penuh tentang auditorium dan dewan yang ada,

dan juga proses tempahan memerlukan kehadiran fizikal mereka di tempat tersebut. Terdapat

kes di mana pelajar membuat tempahan tetapi tidak muncul sehingga menyebabkan banyak

kesulitan. Sesetengah tempahan auditorium dan dewan dilakukan melalui telefon tanpa

komitmen yang dibuat yang tidak tepat tetapi sistem tempahan dalam talian bertujuan untuk

memulihkan sistem ini memetik sifat kesederhanaan, ketepatan dan kecekapannya.

Oleh itu, untuk menangani masalah ini, Auditorium & Dewan Pengurusan Sistem

UniSZA (UAHMS) sangat diperlukan. Sistem tempahan dalam talian boleh diakses melalui

internet dengan menggunakan peranti yang mempunyai sambungan internet pada bila-bila

masa. UAHMS adalah cara yang mudah dan berkesan untuk menangani masalah ini. Proses

tempahan di komuniti UniSZA adalah sistem fail manual yang agak menyusahkan. UAHMS

akan membenarkan pelajar dan staf mengakses butiran auditorium dan dewan dalam talian

dan juga melakukan tempahan dalam talian. Sistem ini akan mempunyai semua maklumat

yang diperlukan mengenai auditorium dan kawasan dewan dalam komuniti UniSZA di dalam

satu laman web yang boleh diakses oleh pelajar dan kakitangan UniSZA yang ingin

menempahnya.

v
 TABLE OF CONTENT

DECLARATION....................................................................................................................... i
CONFIRMATION ...................................................................................................................ii
ACKNOWLEDGEMENT ..................................................................................................... iii
ABSTRACT ............................................................................................................................. iv
ABSTRAK ................................................................................................................................ v
TABLE OF CONTENT.......................................................................................................... vi
CHAPTER 1 ............................................................................................................................. 1
INTRODUCTION.................................................................................................................... 1
1.1 BACKGROUND.............................................................................................................. 1
1.2 PROBLEM STATEMENT .............................................................................................. 2
1.3 OBJECTIVES .................................................................................................................. 3
1.4 SCOPE ............................................................................................................................. 4
1.5 LIMITATION OF WORK ............................................................................................... 5
CHAPTER 2 ............................................................................................................................. 6
LITERATURE REVIEW ....................................................................................................... 6
2.1 INTRODUCTION ............................................................................................................ 6
2.2 UNISZA AUDITORIUM & HALL MANAGEMENT SYSTEM (UAHMS) ................ 6
2.3 SUMMARY OF LITERATURE REVIEW ..................................................................... 7
CHAPTER 3 ............................................................................................................................. 9
METHODOLOGY .................................................................................................................. 9
3.1 INTRODUCTION ............................................................................................................ 9
3.2 ITERATIVE AND INCREMENTAL MODEL .............................................................. 9
3.2.1 Initial Planning Phase .............................................................................................. 10
3.2.2 Planning Phase ......................................................................................................... 10
3.2.3 Requirement Phase .................................................................................................. 11
3.2.4 Analysis and Design ................................................................................................ 11
3.2.5 Implementation and Testing .................................................................................... 11
3.2.6 Evaluation ................................................................................................................ 12
3.2.7 Deployment ............................................................................................................. 12

vi
 3.3 SOFTWARE AND HARDWARE REQUIREMENT ................................................... 13
3.3.1 Hardware Requirement ............................................................................................ 13
3.3.2 Software Requirement ............................................................................................. 14
3.4 FRAMEWORK AND SYSTEM DESIGN .................................................................... 15
3.4.1 Framework ............................................................................................................... 15
3.4.2 Entity Relationship Diagram (ERD)........................................................................ 17
3.4.3 Context Diagram (CD) ............................................................................................ 18
3.4.4 Data Flow Diagram (DFD) ...................................................................................... 19
3.4.5 Data Flow Diagram (Level 1) .................................................................................. 21
3.4.6 Database Design Specification ................................................................................ 24
3.5 PRIORITY SCHEDULING (ALGORITHM) ............................................................... 26
REFERENCES ....................................................................................................................... 27
APPENDIX A ......................................................................................................................... 28
GANTT CHART .................................................................................................................. 28

vii
 CHAPTER 1

INTRODUCTION

This chapter presents an introduction of the project proposal, UniSZA Auditorium and

Hall Management System (UAHMS). It comprises five sections. The first section will be

described on the background of the project. Furthermore, the second section identified the

problem statement related to this project. The third section is the objectives to achieve the

project. Then, the fourth section will be covered the scopes for the project. Lastly, the fifth

section states the activities and milestones of the project.

1.1 BACKGROUND

UniSZA Auditorium & Hall Management System (UAHMS) is a web application

where the management of multiple auditorium and hall in UniSZA is computerized. It

includes all the features and functions needed to efficiently manage an auditorium and hall. It

includes an administrator account which is used to handle/control all the system functionality.

The system keeps track of auditorium/hall status and advance bookings. Besides that, the

system keeps records of auditorium/hall bookings along with associated event details and

user contacts in a well maintained database. The administrator can easily check the

auditorium/hall bookings and timings in the system. The system also allows notifies when

new event timing draws near.

1
 In this project, details like student/staff details reserves and booking details are

maintained. The reservation process of reserving specific auditorium and hall for the

student/staff booking, all is computerized and the management is done without any difficulty.

The report can be viewed completely by the admin by daily, weekly or monthly and can

review it. This proposed system will be interactive faster and user-friendly for the end-users.

The following activities that can be performed are reserving specific slot, booking a time slot,

offense-specific auditorium and hall, total reservation and email notification will be sent on

booking confirmation.

1.2 PROBLEM STATEMENT

The current booking system is manual as all the work is done and kept in files and it also

proven time and energy consuming also difficult for both student and staff. There are some

problems highlighted in this project.

a) Lacks of information regarding the availability and equipment of the auditorium

and hall.

The student/staff having a hard time to book because the description regarding

auditorium and halls availability, capacity and halls equipment booking such as tables

and chair, fan, red carpet and other equipment’s for the whole UniSZA halls were not

stated clearly which should be provided by the staffs that responsible to manage the

matters of halls. There are a lot of work to do as student/staff need to either pay a visit

to the centre or make phone call asking for the details which take some time.

Moreover, the staffs only available at specific periods of time that is working hours.

2
 b) Student/Staff need to go to the centre itself.

Currently, in order to do reservation users itself needs to come to the centre which

takes few minutes to travel from their place. Thus, a lot of student complaint that it

was too far because they had to go to the centre first without knowing the availability

of auditorium or hall that they want to book.

c) Difficult for staffs to manage properly.

Current manual booking system does not provide systematic details of user’s

bookings that will be difficult to manage for a long term. A bunch of sheets of

booking details stacked together might take some time to trace how many bookings

were done in a week. The bookings are done by filling in forms manually which are

submitted to custodians therefore taking a lot of time to book a auditorium or hall

meaning performance of the current system is slow and insufficient.

1.3 OBJECTIVES

There are three main objectives in this project. The objectives are as follows:

a) To design a web-based system for booking auditorium and hall in UniSZA.

b) To implement Priority Scheduling methods in booking system.

c) To test performance of the system in receiving and cancelling the bookings of users

without any problems.

3
1.4 SCOPE

The scope of this project consists of three users which are admin, student and staff

including a system scope.

a) Admin

 It has admin login who is has the authority of the system and he is responsible

for approving and disapproving the users request for auditorium/hall booking.

 Admin can add and delete notifications and updates in the system.

 Admin will manage auditorium/hall booking which will allow him or her to

observe the availability and unavailability of the auditorium for any date and

hourly time interval also.

b) Student/Staff

 There is user registration form available where new users can create their

account by providing required information to the system.

 Once approved by the admin, user can log in and raise a request for

auditorium/hall booking as per the scheduled event for any meeting or event.

 User can request for the booking for a particular date and time slot.

c) System

 The system will inform the respective users through an email about their status

of booking request whether approved or disapproved.

 The system keeps track of auditorium/hall status and advance bookings.

 The system keeps records of auditorium/hall bookings along with associated

event details and user contacts in a well maintained database.

 The system also allows notifies when new event timing draws near.

4
1.5 LIMITATION OF WORK

a) Booking and cancel the booking

This project only provides booking system that enables student/staff to book or cancel

the booking of the auditorium or hall in UniSZA. The system will not receive any online and

manual payment such as credit card, debit card or cash because the auditorium and hall is

provided for UniSZA community used.

5
 CHAPTER 2

LITERATURE REVIEW

2.1 INTRODUCTION

The literature review is a process to read, analyse, evaluate and summarize the

scientific material in respect of any topic (Fink, 2015). To come up with all the elements in

UniSZA Auditorium & Hall Management System (UAHMS), a review of related literature

was conducted by gathering information from the research papers and journals. The main

elements in UAHMS are online auditorium and hall booking platform to the UniSZA

community using Priority Scheduling.

2.2 UNISZA AUDITORIUM & HALL MANAGEMENT SYSTEM (UAHMS)

UAHMS is a system that enables people access details of auditorium and hall online

and also does the booking online. The system will have all the necessary information about

auditorium and hall areas within UniSZA community on one single website which accessible

by anyone who wants to book. Some of the benefits of the automated online auditorium

booking process include the following:

 It is convenient for users as they do not have to actually visit the place.

 This system is effective and saves time and cost of the users.

 Easy registration.

6
2.3 SUMMARY OF LITERATURE REVIEW

These research papers generally focused on online booking system. Every author has

different solution in proposing their system which is using a web based or mobile application

as a platform in presenting the system to the user. Table below shows the summary of the

research papers referred in this project.

Author/Year Project Title Technique Description Advantages Disadvantages

Walek, Hosek, Proposal of Expert The article -The proposed The hotel must
Farana. (2016) Expert System System proposed an approach is pay for using a
for Hotel expert system based on hotel booking
Booking for a hotel evaluating website.
System booking hotel services
system. The for different
main aim of kinds of hotel
the proposed guests.
expert system
is to evaluate -The output of
and propose the expert
suitable hotel system is a
services and proposal of
suitable suitable hotel
activities and services for
events for hotel guests
hotel guests. during the
process of
hotel booking.

7
Sheelarani, Effective Car Internet of An effective This system If the particular
Anand, Parking Things parking can be used to vehicle does not
Shamili, Reservation reservation avoid heavy reach the
Sruthi, System Based system where traffic in the parking slot
(2016) On Internet Of the user can parking areas booked within
Things book their like shopping the grace time
Technologies particular slot malls, limit, the slot
using their theatres, will be made
android tourist spots available to the
application or and other busy others and the
with the help areas thereby payment will
of an reducing time not get reverted.
embedded and the
hardware. consumption
of the fuel and
pollution.

Rarh, Pojee, Restaurant Time-Series A new system The system Research is

Zulphekari, Table Prediction for restaurant will notify the focuses in the
Shah Reservation as well as customer if slum of India.
(2017) Using Time- users to there is a
Series conveniently delay for their
Prediction reserve table reservation by
at preferable the restaurant,
time over the it will help the
cloud. customer to
re-schedule
their
reservation.

Table 2.1 Summary of Literature Review

8
 CHAPTER 3

METHODOLOGY

3.1 INTRODUCTION

Methodology is the process, step or stages used to collect information and data for the

purpose of making decisions. The methodology is chosen from the software development life

cycle model. There are many models included in the software development life cycle. For this

project, iterative ad incremental model approach has been chosen.

3.2 ITERATIVE AND INCREMENTAL MODEL

Figure 3.1 Iterative and Incremental Model

9
 UniSZA Auditorium & Hall Management System is developed by using Iterative and

Incremental Model approach. By using this approach, it allows the developer to develop the

system phase by phase and it is also possible return the previous phase even though the

deliverables had been done. There are eight phases in this approach which are initial planning,

planning, requirements, analysis and design, implementation, testing, evaluation and

deployment phase. For each iterations, any additional features can be designed, developed,

implemented and tested until the system is fully functional and ready to be deployed.

3.2.1 Initial Planning Phase

In this phase, all the activities are plan according to a given period to complete the

system. This phase begins with brainstorming sessions with the supervisor to come up with

the idea and the title for the project. From the brainstorming session with the supervisor, the

project title have been decided which is, UniSZA Auditorium & Hall Management System.

3.2.2 Planning Phase

After deciding the title of the project, the discussions continue on defining the

problem statements, objectives and scope for the system. Besides that, author takes

opportunity to implement the priority scheduling approach in the system as the other similar

hall-kind booking system might not use it yet. Priority scheduling is capable in solving the

problem of students or staff that is reserving the auditorium or hall at UniSZA at the same

date and time. The system requirements are identified by direct observation in the existed

booking systems and research papers.

10
3.2.3 Requirement Phase

For requirement phase, existing systems are analysed and all the requirements that are

needed to develop the new system are identified. In this phase, the information regarding

UniSZA Auditorium & Hall Management System either in the form journal, articles or

research papers are gathered and studied. The information obtained about the auditorium and

hall booking system and priority scheduling method is crucial in producing the end product

and achieve the system objectives.

3.2.4 Analysis and Design

In this phase, the design of the system is created and the development of the prototype

based on the functionalities that will be built. The data or requirement obtained during the

requirement phase is transformed into a design. Examples of diagrams that will be builds are

Framework, Context Diagram (CD), Data Flow Diagram (DFD) level 0 and 1, Entity

Relationship Diagram (ERD), Database Design and Interface Design. All of these diagrams

are built as a guideline of the flow of the system.

3.2.5 Implementation and Testing

After designing the interfaces, the implementation phase is applied. In this phase,

author will make an overall improvement to the system modules. A discussion with the

supervisor is held to seek solution for any error or fixing bugs in the system. Unit testing and

integrated testing for the module is done to find errors and solutions to overcome the

problems. Then finally, the entire modules of the system will be combined and tested before

it is implemented.

11
3.2.6 Evaluation

During this phase, the system is evaluated before deploying it to end user. The system

must fulfil the entire system requirement before it is able to be deployed.

3.2.7 Deployment

Once the evaluation is done, the system is deployed in the environment so that the

targeted user can be use the system. The system will be in steady state which meets all the

objectives of the project.

12
3.3 SOFTWARE AND HARDWARE REQUIREMENT

In the making of this project, software and hardware tools are very important and

essential. The system cannot be developed successfully without these software and hardware

requirements.

3.3.1 Hardware Requirement

No. Hardware Description

1. Laptop Model: Lenovo G-50

CPU: Intel®Core™i3

OS: Windows 10 Pro

Function: To develop the system and make the

documentation.

2. Printer Function: To print all the needed document and report.

3. USB pen-drive Function: To store all the data and act as a backup for

the project.

Table 3.1 Hardware Requirement

13
3.3.2 Software Requirement

No. Software Description

1. Notepad++ Tools used for developing the code for function

and interface.

2. MySQL System database application.

3. phpMyAdmin Tools used for creating, modifying or deleting

databases, tables, fields or rows.

4. XAMPP Web Server Local server to run and test the system and the

database connection.

5. Google Chrome Tools used as a platform to run the system.

6. Adobe Reader Tools used to view documents, journal and

research papers.

7. Microsoft Office 2010 Tools used for documentation of the project,

creating report, presentation slide and draw

 Microsoft Word 2010
diagrams.
 Microsoft PowerPoint

2010

 Microsoft Visio 2013

Table 3.2 Software Requirement

14
3.4 FRAMEWORK AND SYSTEM DESIGN

The framework and design for UniSZA Auditorium & Hall Management System such

as framework, context diagram (CD), data flow diagram (DFD) level 0 and 1, entity

relationship diagram (ERD) and database design specification are explained in detailed. Data

modelling is required to facilitate the interaction between system designer, programmer and

end-user. Making an early modelling can help to identify the needs, problem and possible

solutions during the project.

3.4.1 Framework

Figure 3.2 Framework

15
 Framework is a layered structure indicating what kind of programs can or should be

built and how they would interrelate. In the figure 3.1, student or staffs needs to register first

in order to book. After the user makes the booking, they can view their own booking details.

The admin also able to retrieve the student/staff details including their booking. As an admin

of the system, he or she can manage the auditorium and hall as well as views the report of the

system that retrieves from database. The website act as an interface to the users of the system

which retrieves and sends the data to the system database through a web server.

16
3.4.2 Entity Relationship Diagram (ERD)

Figure 3.3 Entity Relationship Diagram

Entity relationship diagram (ERD) is data model representation for describing the data

or information involved in the system. It helps to organize the data in the system into entities

and relationships between the entities. This process has proved to enable the analyst to

produce a good database structure so that the data can be stored and retrieved in efficient

manner. From the figure 3.3, there are 6 tables which are User, Booking, Hall, Hall

Equipment, Equipment and Faculty in this system. Hall Equipment and Booking is a

composite entity. The relationship between the tables is connected by foreign key.

17
3.4.3 Context Diagram (CD)

Figure 3.4 Context Diagram

Figure 3.4 shows the context diagram for UniSZA Auditorium & Hall Management

System. It describes the main process for the system. There are 3 types of users involved in

this system which are Admin, Student and Staff. The context diagram will explain much

about the flow between the three users and what they are capable to do within their own

authorization.

18
3.4.4 Data Flow Diagram (DFD)

Figure 3.5 Data Flow Diagram

Process 1.0 Registration

This module allows student and staff to register themselves before able to use the

system. The student and staff have to enter several details about themselves and the details

will be stored in the D1 Student and D2 Staff data store.

19
Process 2.0 Login

This module allows student, staff and admin to login into the system and use the

system. The users need to enter their userID and password before using the system. The

system will use the D1 Student, D2 Staff and D3 Admin data store to verify the login details.

Process 3.0 Manage Profile

This module allows the student and staff to update and delete their profile. While

admin can only updates their data. All the changes to the profile will be saved in the D1

Student, D2 Staff and D3 Admin data store.

Process 4.0 Booking

This module allows student and staff to book auditorium or hall by select which

auditorium or hall are available for date and time that they want. It will retrieve the data from

D5 Auditorium & Hall data store and all the booking details will be stored in D4 Booking

data store.

Process 5.0 Manage Auditorium & Hall

This module can be access by the admin only. Admin can add new auditorium or hall

into the system if UniSZA has a new auditorium or hall, update the auditorium or hall if there

are any changes in the auditorium or hall and delete the auditorium or hall if UniSZA no

longer have the auditorium or hall. All the changes in the auditorium or hall will be saved in

the D5 Auditorium & Hall data store.

Process 6.0 Report

This module allows student, staff and admin to view report of the booking which

retrieves the data from D4 Booking data store.

20
3.4.5 Data Flow Diagram (Level 1)

3.4.5.1 Manage Profile

Figure 3.6 DFD Level 1 (Manage Profile)

21
3.4.5.2 Booking

Figure 3.7 DFD Level 1 (Booking)

22
3.4.5.3 Manage Audi & Hall

Figure 3.8 DFD Level 1 (Manage Audi & Hall)

23
3.4.6 Database Design Specification

Database is the main part to of the system development because it will store the data

that are used by the system. The database name is uahms_db where it contains 7 tables which

are Admin, User, Booking, Faculty, Hall, Equipment and Hall Equipment. The following is

in the list of the table.

Table 3.3 Admin

Table 3.4 User

Table 3.5 Booking

24
 Table 3.6 Faculty

Table 3.7 Hall

Table 3.8 Equipment

Table 3.9 Hall Equipment

25
3.5 PRIORITY SCHEDULING (ALGORITHM)

1. Start

2. Declare U1, U2

3. If (U1.date = = U2.date) //clash date

3.1 If (U1.capacity > U2.capacity)

3.1.1 Insert U1 data into database

3.1.2 Search (U2.capacity)

3.2 Else if (U1.capacity < U2.capacity)

3.2.1 Insert U2 data into database

3.2.2 Search (U1.capacity)

3.3 Else if (U1.capacity = = U2.capacity)

3.3.1 If (U1.serverTime > U2.serverTime)

3.3.1.1 U1 get insert

3.3.2 Else

3.3.2.1 U2 get insert

4. Else //FCFS

4.1 If (U1.date > U2.date)

4.1.1 U2 get insert

4.2 Else

4.2.1 U1 get insert

5. End

26
 REFERENCES

Walek, B., Hosek, O., & Farana, R. (2016, May). Proposal of expert system for hotel booking

system. In Carpathian Control Conference (ICCC), 2016 17th International (pp. 804-807).

IEEE.

Sheelarani, P., Anand, S. P., Shamili, S., & Sruthi, K. (2016, February). Effective car parking

reservation system based on internet of things technologies. In Futuristic Trends in Research

and Innovation for Social Welfare (Startup Conclave), World Conference on (pp. 1-4). IEEE.

Rarh, F., Pojee, D., Zulphekari, S., & Shah, V. (2017, October). Restaurant table reservation

using time-series prediction. In Communication and Electronics Systems (ICCES), 2017 2nd

International Conference on (pp. 153-155). IEEE.

27
 APPENDIX A

GANTT CHART

Activities Month

September October November December January February March April May

Phase: Initial Planning

a) Discuss a project title

b) Create an abstract

Phase: Planning

a) Create a project proposal

Phase: Requirement

a) Gather information

b) Proposal presentation

Phase: Analysis And Design

a) Construct CD, DFD, ERD

b) Create interface for the system

Phase: Implementation

a) Developing the system

Phase: Testing & Evaluation

a) Test the system

b) Correct bugs and error

Phase: Deployment

a) Final presentation

b) Provide system training and support

28