Upload
others
View
13
Download
3
Embed Size (px)
Citation preview
UNISZA SPORTS MANAGEMENT SYSTEM
(UNISZA-SMS)
SITI ZUBAIDAH BINTI SAAT
BACHELOR OF COMPUTER SCIENCE
(SOFTWARE DEVELOPMENT)
UNIVERSITI SULTAN ZAINAL ABIDIN
2017
UNISZA SPORTS MANAGEMENT SYSTEM
(UNISZA-SMS)
SITI ZUBAIDAH BINTI SAAT
Bachelor of Computer Science (Software Development)
Faculty of Informatics and Computing
Universiti Sultan Zainal Abidin, Terengganu, Malaysia
MAY 2017
i
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 Zubaidah Binti Saat
Date : 14th
May 2017
ii
CONFIRMATION
This is to confirm that:
The research conducted and the writing of this report was under my supervison.
________________________________
Name : Puan Hasni Binti Hassan
Date : ..................................................
iii
DEDICATION
In the name of Allah the most Gracious and the Merciful May His Blessing be upon
the prophet Muhammad s.a.w.
I would like to express gratitude to those who helped me either directly or indirectly.
Special thanks go to my dedicated supervisor, Puan Hasni Binti Hassan for her
considering, guidance, ideas, comments and encourage throughout the whole process
in completing this final year project in time that led me to produce better quality of the
project.
My personal gratitude goes to my parents and all my family members for all moral
support and tolerance that they give to me.
Thanks also go to all my friends who helped me and supported me in completing my
final project.
iv
ABSTRACT
Sports are part of students’ activities at university. This project is proposed to design
web based system that is Sports Management System. The system allows students and
citizens to book available sports equipments from sport management center in
University Sultan Zainal Abidin (UniSZA). In addition, this project also contains the
registration of sport facilities such as football field, badminton and tennis courts, gym
center and also basketball and netball center. The main concern from developing this
system is to provide an alternative to manual booking system where the students must
ask the staff personally about the availability of the equipments and sports facilities.
Sports Management System that proposed is using Priority-Queue algorithm. Priority-
Queue algorithm is where the highest type of user who booked the equipment or
facilities will be approved first. It is anticipated the proposed system will help making
the management of sports equipment and its facilities in UniSZA to be more efficient
in the future.
v
ABSTRAK
Sukan adalah sebahagian daripada aktiviti pelajar di universiti. Projek ini
dicadangkan untuk mereka bentuk sistem berasaskan web iaitu Sistem
Pengurusan Sukan. Sistem ini membolehkan pelajar dan rakyat untuk
menempah peralatan sukan boleh didapati dari pusat pengurusan sukan di
Universiti Sultan Zainal Abidin (UniSZA). Di samping itu, projek ini juga
mengandungi pendaftaran kemudahan sukan seperti padang bola sepak,
gelanggang badminton dan tenis, pusat gimnasium dan juga bola keranjang
dan pusat bola jaring. Kebimbangan utama daripada membangunkan sistem
ini adalah untuk menyediakan alternatif kepada sistem tempahan manual di
mana pelajar perlu bertanya kepada kakitangan secara peribadi mengenai
adanya peralatan dan kemudahan sukan. Sistem Pengurusan sukan yang
dicadangkan menggunakan algoritma Priority-Queue. algoritma Priority-
Queue adalah di mana jenis yang paling tinggi pengguna yang menempah
peralatan atau kemudahan itu akan diluluskan terlebih dahulu. Adalah
dijangkakan sistem yang dicadangkan akan membantu membuat pengurusan
peralatan sukan dan kemudahannya di UniSZA untuk menjadi lebih cekap
pada masa akan datang
vi
CONTENTS
PAGE
DECLARATION i
CONFIRMATION ii
DEDICATION iii
ABSTRACT iv
ABSTRAK v
CONTENTS vi
CHAPTER I INTRODUCTION
1.1 Project Background 1
1.2 Problem statement 2
1.3 Justification 3
1.4
1.5
Objective
Scope
3
3
1.6 Report Organization 4
CHAPTER II LITERATURE REVIEW
2.1 Introduction 5
2.2
Research Scheduling
2.2.1 Technique
5
5
2.3 Priority-Queue algorithm 6
2.4
2.5
Related System
Chapter Summary
7
7
CHAPTER III
METHODOLOGY
3.1
3.2
Introduction
System Development Life Cycle (SDLC)
11
11
3.2.1 Planning Phase 12
3.2.2 Analysis Phase 12
3.2.3 Design Phase 12
3.2.4 Implementation Phase
3.2.5 Maintenance (Support) Phase
12
13
vii
3.3
3.4
3.5
System Requirement
3.3.1 Software Requirement
3.3.2 Hardware Requirement
Summary
Requirement Analysis
13
13
14
14
15
3.5.1 Functional Requirement 15
3.5.2 Non-Functional Requirement
3.5.2.1 Security
3.5.2.2 Reliability
3.5.2.3 Availability
3.5.2.4 Performance
3.5.2.5 Portability
3.5.2.6 Maintainability
3.5.2.7 Flexibility
17
17
17
17
18
18
18
19
3.6 System Design
3.6.1 Introduction
19
19
3.6.2 System Framework 20
3.6.3 Context Diagram 22
3.6.4 Data Flow Diagram 23
3.6.5 Data Flow Diagram Level 1 27
3.3.6 Entity Relationship Diagram
3.6.7 Database design specification
3.6.8 Algorithm
32
33
39
\
Conclusion 40
Reference 41
viii
ix
LIST OF APPENDICES
APPENDIX TITLE PAGE
A Appendix 1 42
1
CHAPTER I
INTRODUCTION
This chapter presents an introduction of the project proposal; UniSZA Sport
Management System (UniSZA-SMS).It comprises five sections. The first section
describes background of the project. The second section identifies problem related to
this project. The next section contains the objectives of the system whereas the scopes
of the project will be presented in the fourth section. The fifth section presents
limitations of the project and finally,structure of the project will be outlined in the last
section. Last section is outlined about the structure of the project.
1.1 PROJECT BACKGROUND
This chapter introduces the project of system development for sports management
in University Sultan Zainal Abidin (UniSZA) to provide better management in
terms of booking management. This project will covered for UniSZA members
that are focus at Tembila Campus and Gong Badak Campus. Sports are physical
activities or games that always grab attention of people especially for students to
release tension and spend their time. Sport management include sports marketing,
event management, sport information, facilities and equipment management.
Examples the type of sport that famous in UniSZA are futsal, badminton,
basketball, archery, football and volleyball.
In this project, Priority-Queue concept is the type of scheduling algorithm
that will be implemented for the booking process. In the Priority-Queue concept,
the highest type of users who booked the equipments or facilities will get the
equipment or facilities first.
This system will focus more on UniSZA student’s for diploma and degree
students from all campus in UniSZA. This system also will cover equipment and
facilities booking from public where contain fees will be charged depending on the
type of equipment and facilities being booked.
For this proposed system,we would like to develop system that implimented
the Priority-Queue algorithm based on specific criteria that will be filtered by
2
system to make the valuable result. The specific criteria are chosen from data
collection that is interviewed a few staff that are incharge at the counter.
1.2 Problem Statement
Some problems highlighted in this project:
1) There is no exact information about the availability of the equipment and
facilities.
The main activities of students at college are sports where are activities that
make student relaxed and enjoy their free time. So, they need to know about
the availability of sports equipments and their facilities. Sadly, they need to
ask staff about the availability of the facilities. They have to ask the staffs
personally and if the facilities are not available, it wastes students’ time. In
addition, the staffs are only available during working hour.
2) Unsystematic booking system.
At UniSZA, students booked the equipment manually using matric card. If
students forgot to bring the card, they will not able to use or book the
equipments. Furthermore, sometime there are event of the sports so, the project
manager must discuss manually with the staff at counter about the availability
of facilities.
3) Waste of paper(manual process)
For recording the data about who’s booked the equipment and facilities, staffs
still using the paper .So, there are many people booked the equipment and
facilities, and more paper will be used. The data also easy to be loss if paper
used.
Here,the proposed system that we call ‘Unisza Sports Management System
(Unisza-SMS) to overcome these problems.
3
1.3 JUSTIFICATION
This system can reduce the use of the paper. It also help student to get information
quickly about the availability of the equipment and facilities. This system also
provides systematic booking system which is the highest priority will get the booking.
1.4 OBJECTIVES
Following are the objectives to overcome these problems:-
1) To design a web based system for sports management focusing on
equipment booking management.
2) To develop a web based sports management system based Priority-Queue
algorithm
3) To evaluate the performance of the system.
1.5 SCOPE
Sports Management System will help the staffs, students and public. This system
will be accessed by admin, staffs, students and public via the website.
a) Admin
1) Admin will register the account for Sport Management System for students
and staffs.
2) Admin can update their profile
3) Admin will add ,delete and view the users account
4) Admin can change the password
5) Admin will add criteria for priority queue.
b) Staff
1) Staff will update and view staff profile.
2) Staff will add, delete, update and view availability of equipments and
facilities.
3) Staff will view user details.
4) Staff will view and update payment details from public.
c) Student
1) Students will add, view and update student profile.
4
2) Students will add, update, cancel and view the equipment and facilities
booking detail
d) Public
1) Public need to register first as a user
2) Public will add, update and view their profile
3) Public will add, cancel, update and view booking details.
4) Public will view payment detail
1.6 LIMITATION OF WORK
The proposed system does not cover the transaction of payment from community.
They only have to upload proof of payment to the system. For payment using cash,
they need to pay manually at the staff’s counter.
1.7 REPORT ORGANIZATION
This report consists of three chapter.At early chapter is an introduction about this
system such as project introduction,problem statement about why this system is
developed ,justification,objective,scope,project planning and this report
organization.Second chapter is about literature review from the existing system,
techniques or previous journal and research.It consists of introduction, research and
analysis from existing system and research on technique,tool and technology that be
used to overcome the problem stated. Third chapter are about project methodology, it
will begin with introduction of project methodology, phases in development and
system requirement either from software or hardware. This chapter also will be
explained the detail about project design and model.This will include data modelling
design.,fuction design and interface design. Next chapter is about the system
algorithm and data flow diagram.Last part about conclusion.
5
CHAPTER 2
LITERATURE
2.1 INTRODUCTION
This chapter is to describe and explain the project and its related research. This
chapter focuses on the technique that will be used in this project. Besides, related
work or researches have been reviewed in order to guide and improve the quality of
the project. The important points from analysing other related projects are to describe
the possibility of the features that are lacking in other projects. This chapter also will
discuss the approach used in this project.
2.2 RESEARCH ABOUT SCHEDULING
2.2.1 TECHNIQUE
A scheduling algorithm is the algorithm which dictates how much CPU time is
allocated to Processes and Threads. Development of scheduling algorithms is directly
related with the development of operating system which brings difficulties in
implementation. Any modification on the scheduling algorithm will appear as
modification on the operating system kernel code. Processor is an important source of
cpu scheduling process, so it becomes very important on accomplishing of the
operating system design goals. A delicate problem of the well-functioning of SO is the
case when in CPU comes two or more processes which wants to be executed.
Scheduling includes a range of mechanisms and policies that SO has to follows in
order that all processes take the service .The goal of any scheduling algorithm is to
fulfill a number of criteria:
no task must be starved of resources - all tasks must get their chance at CPU time;
if using priorities, a low-priority task must not hold up a high-priority task;
the scheduler must scale well with a growing number of tasks, ideally being O(1).
This has been done, for example, in the Linux kernel.
There are six popular process scheduling algorithms:-
First-Come, First-Served (FCFS) Scheduling
Shortest-Job-Next (SJN) Scheduling
Priority-Queue Scheduling
6
Shortest Remaining Time
Round Robin(RR) Scheduling
Multiple-Level Queues Scheduling
These algorithms are either non-preemptive or preemptive. Non-preemptive
algorithms are designed so that once a process enters the running state; it cannot be
preempted until it completes its allotted time, whereas the pre-emptive scheduling is
based on priority where a scheduler may pre-empt a low priority running process
anytime when a high priority process enters into a ready state.There are many
software project that using scheduling algorithm to improve the these algorithms for
future work.
2.3 PRIORITY-QUEUE ALGORITHM
Priority queues have been used for applications such as branch-and-bound
algorithm[Mohan 1983;Rao et al. 1987], discrete-event simulation[fujimoto
1990],shortest path algorithm[Quinn and Deo 1984],multiprocessor scheduling and
sorting.A priority queue is an abstract data structure that allows deletion of the highest
priority item and insertion of new items.Generally,priority-queue based applications
consist of repeated cycles where an item of the highest priority is deleted from the
priority queue;some processing is done on that item,which leads to the creation of zero
or more new items ,which in turn are inserted into the priority queue and ths cycle
repeats.
Figure 2.3 Conceptual picture of a priority queue
Think of a priority queue as a kind of bag that holds priorities. You can put one in, and
you can take out the current highest priority
A priority queue is different from a "normal" queue, because instead of being a "first-
in-first-out" data structure, values come out in order by priority. A priority queue
7
might be used, for example, to handle the jobs sent to the Computer Science
Department's printer: Jobs sent by the department chair should be printed first, then
jobs sent by professors, then those sent by graduate students, and finally those sent by
undergraduates. The values put into the priority queue would be the priority and the
associated information would be the document to print. Each time the printer is free,
the job with the highest priority would be removed from the print queue, and printed.
The operations that need to be provided for a priority queue are shown in Table 2.3
below.
OPERATION DESCRIPTION
PriorityQ( ) (constructor) create an empty priority queue
boolean empty( ) Return true if the priority queue is empty
void insert(Comparable p) Add priority p to the priority queue
Comparable removeMax() Remove and return the highest priority from the priority
queue (error if the priority queue is empty)
A priority queue can be implemented using many of the data structures such as
array,linked list or binary search(BST). To ensure all of the operations run efficiently,
the data structure called a heap is used.
2.4 RELATED SYSTEM
For this project, some research has been done to understand about sport
management system:
Author/Journal/Year Description Advantageous Disadvantageous
Muhammad Shariffuddin
Bin Mazlan(Fakulti
Informatik &
Komputeran,UNISZA)
“Online Badminton
Courts Booking System
Using Priority-Queue
Technique.”(2016)
This project is
about system that
provides the
priority that those
users that do not
make payments
within time limits
the badminton
court booking s
will be cancelled
automatically.
The expected
outcome is users
can book the
badminton courts
that available at
their desired time
and date without
any problem.
The reservation that
make by those who
late come to the
court will be
cancelled, so it will
make users do not
satisfy with the
system.
8
Mahdi Hishamuddin
Abdul Aziz, Junaida
Sulaiman(Fakulti Sistem
Komputer & Kejuruteraan
Perisian,UPM).
“UPM Squash
Reservation System Using
Lighting Control.”(2016)
The UMP sports
center provides
two squash courts
to the student and
staff to use. They
must make a
reservation and
pay with
affordable price
to use the court.
Users must pay
for RM 1.00
(Student) and RM
5.00 (Staff) for
one hour. The
concept to make a
reservation is first
come, first serve
This system will
have the sound
beam that notifies
the user that the
time is running
out. Furthermore,
this system will
turn off the lamp
automatically
when the time is
running out to
avoid customer to
play ‘FREE’
games.
The implementation
of LED lightning
need high cost of the
system.
Lee,Elizabeth Cheah
Hui(UTEM).
“Venue And Equipment
Online Booking
System.”(2006)
VEOBS is a web-
based system that
integrates both
venue and
equipment
booking.
Capable of
keeping track of
the equipment
borrowed.VEOBS
will provide
automation in
aspects such as
email notification,
availability
checking of venue
and tracking of
equipments. The
goal of VEOBS is
to bring about
greater ease of
work for the
receptionist at
YES in terms of
venue and
All booking requests
are subjected to
manager’s approval
which might take
some time.
9
equipments
booking as well
as to enhance the
communication
among the
receptionist,
manager
Salmon,James
“Automated Sports Club
Booking and Enquiry
System.”(2002)
Produce an
effective and low
cost automated
booking solution
for a small to
medium sized
sports club.
Using ISP hosting
on the club’s pc
which are
reliable,require
less maintenance
and cheaper
hosting plan.
Hosting an ASP is
cost effective but at
that time it can be
only displayed in
Microsoft’s Internet
Explorer browser.
Hongchao Xu. Shandong
University of Finance and
Economics.
“The Research Sports
Management Monitoring
System Based on
WSN.”(2015)
This article is
about sports
management with
efficient and safe
operation, the
wireless sports
management
monitoring
management
system of a sports
management is
designed based
on using
MCP2515 driver
and Wireless
communication
message.
Systems design to
build a friendly
human-machine
realization of
construction site
acquisition and
local management
running the data
through GPRS
WEB server and
build to achieve a
fleet of remote
monitoring and
unified
management,
through on-site
commissioning,
the system is
stable and
Need high cost to
implement the
system.
10
reliable, and has
broad application
prospects.
2.5 CHAPTER SUMMARY
This chapter discussed about the technique and model used in the proposed system. Based
on the literature review, Sport Management System will be able to help student, staff and
another user in manage the sport efficiently. The management will be more flexible and
usability for sport management in UniSZA.
11
CHAPTER 3
METHODOLOGY
3.1 Introduction
In this chapter will describe the processes involved in completing this system.The
details of methodology being used in this project will be explained. The function
of project methodology is the guidelines to ensure the project is working well.
There are many types of methodology that can be applied in the development of
the system such as waterfall model, spiral model, and agile model. These
approaches should be choosing properly based on suitability of the system.
3.2 SYSTEM DEVELOPMENT LIFE CYCLE
For this project, system development life cycle has been chosen as the guideline
for the project. Each development process may change from time to time
according both user system requirements.
Figure 2: Show System Development Life Cycle(SDLC)
12
3.2.1 Planning
Planning is the first phase in system development life cycle which specific goals are
identified. The planning process discuss about the goals that want to be achieved in
limited time and cost.For this purpose,I started with conducting feasibility
study,getting the idea of project with supervisor and identifyng the objective,proble
statement and scope of this systeom. This phase need to check whether all gathering
information is satisfy to solve the state problem or not.In this project, the Priority-
Queue will be implemented where is this approach has been discussed in this phase.
3.2.2 Analysis
In analysis phase, the specification of requirements is analysing to understand the
problems. This task includes reviewing documents,reading books,papers and manual
related to the problems statement.The sources to be reviewed mostly were found from
the internet. During the information gathering,the requirement of this system needs to
meet user to achieve the objective of this system. The system requirement are studied
and structured for more understanding on booking approach and Priority-Queue
technique.
3.2.3 Design
The design for interface should cover some of basic features in sport portal of UniSZA
.The system is proposed to design a web based booking system that being able for user
to book equipment and facilities.
3.2.4 Implementation
The implementation phase is begins once the design is approved. This project is
develop using MySQL, PHP and XamppServer . Xamppserver is used as the
localhost server. The codes for staff,students and community pages will be
implemented carefully and ensure every process is working in one another in order to
make compilation is able to done without any warning or errors.
13
3.2.5 Maintenance (Support)
In maintenance phase,the system will be updates as necessary to keep up to date with
its environment.It focuses on change associated with error correction.
3.3 System Requirement
Based on techopedia.com, the implementation that the system needed to make sure
the hardware or software can be run smoothly. If not success in fulling the
requirement, the failure of performance and installation may occur.
3.3.1 Software Requirement
The software requirementare needed to build system are:
1) XAMP Server MySQL
Using this software to create database and manipulate database
and connect database with PHP.
2) Lucid Chart
Create and design Data Flow Diagram and Context Diagram
3) Dropbox
Save and update the document for this system and also as the
backup file.
4) Google Chrome
Medium to find reference to do system and as medium to
system be display and run.
5) Notepad++
As medium to write PHP coding to build system.
14
3.3.2 Hardware Requirement
The hardware requirement to build the system is:
1) Laptop ASUS X455L series
Have Intel i3 processor,4GB RAM,
Window 10 operating system
64 bit Operating system type
3.4 Summary
This chapter focused on the methodology of the software development,
requirements of software and hardware to achieve the objectives to build the system.
The project will be build need able to be run and display on the medium in web
browser such as Google Chrome and Mozilla Firefox. With the right methodology that
has been chosen, the phases will able to follow correctly. The explanation of
methodology, software and hardware requirement has been described in this chapter.
15
3.5 REQUIREMENT ANALYSIS
3.5.1 Functional Requirement
The Student will be able to:
FR-STUDENT-001 The system shall allow student to login to the Unisza Sports
Management System (Unisza-SMS) website (after has been registered to the website).
FR-STUDENT-002 The system shall allow student to logout to the Unisza-SMS
website
FR-STUDENT-003 The system shall allow student to browse equipment and
facilities.
FR-STUDENT-004 The system shall allow student to book equipment and facilities.
FR-STUDENT-005 The system shall allow student to check booking record.
FR-STUDENT-006 The system shall allow student to change booking date.
FR-STUDENT-007 The system shall allow student to cancel booking.
FR-STUDENT-008 The system shall allow student to manage user profile.
FR-STUDENT-009 The system shall allow student to change the password.
The Public will be able to:
FR-USER-001 The system shall allow public to register to become a member.
FR-PUBLIC-002 The system shall allow public to login to the Unisza Sports
Management System (Unisza-SMS) website (after has been registered to the website).
FR-PUBLIC-003 The system shall allow public to logout to the Unisza-SMS website
FR-PUBLIC-004 The system shall allow public to browse equipment and facilities.
FR-PUBLIC-005 The system shall allow public to book equipment and facilities.
FR-PUBLIC-006 The system shall allow public to check booking record.
FR-PUBLIC-007 The system shall allow public to change booking date.
16
FR-PUBLIC-008 The system shall allow public to cancel booking.
FR-PUBLIC-009 The system shall allow public to view payment.
FR-PUBLIC-010 The system shall allow public to manage user profile.
FR-PUBLIC-011 The system shall allow public to change the password.
The Staff will be able to:
FR-STAFF-001 The system shall allow staff to login to the Unisza Sports
Management System (Unisza-SMS) website (after has been registered to the website).
FR-STAFF-002 The system shall allow staff to logout to the Unisza-SMS website
FR-STAFF-003 The system shall allow staff to add details of equipment and
facilities.
FR-STAFF-004 The system shall allow staff to delete details of equipment and
facilities.
FR-STAFF-005The system shall allow staff to update details of equipment and
facilities.
FR-STAFF-006 The system shall allow staff to add booking details.
FR-STAFF-007 The system shall allow staff to delete booking details.
FR-STAFF-008 The system shall allow staff to update booking details.
FR-STAFF-009 The system shall allow staff to add payment details.
FR-STAFF-010 The system shall allow staff to delete payment details.
FR-STAFF-011 The system shall allow staff to update payment details.
FR-STAFF-012 The system shall allow staff to manage user profile.
FR-STAFF-013 The system shall allow staff to change the password.
17
The Admin will be able to:
FR-ADMIN-001 The system shall allow admin to register users to become a member.
FR-ADMIN-002 The system shall allow admin to login to the Unisza-SMS website.
FR-ADMIN-003 The system shall allow admin to logout to the Unisza-SMS website.
FR-ADMIN-004 The system shall allow admin to check booking record.
FR-ADMIN-005 The system shall allow admin to check payment record.
FR-ADMIN-007 The system shall allow admin to add specific criteria.
FR-ADMIN-008 The system shall allow admin to view user list.
FR-ADMIN-010 The system shall allow admin to change password.
3.5.2 Non-Functional Requirement
3.5.2.1 Security
NFR-SEC-001 Admin, Staff, Student and Public shall be required to login for all
operation. The password will be encrypted and store in the database.
3.5.2.2 Reliability
NFR-REL-001 The system shall have an availability of 99% which mean out of 100
requests, 99 must be satisfied.
NFR-REL-002 Initial data must be collected carefully and correctly.
NFR-REL-003 The database must be backed up regularly and can be recovered if
necessary.
3.5.2.3 Availability
NFR-AVA-001 The system should be available anytime when users want to use it.
NFR-AVA-002Level of availability is 24 hours * 7 days.
18
3.5.2.4 Performance
NFR-PER-001 Response to queries shall take no longer than 5 seconds to load onto
the screen after user submit the queries.
NFR-PER-002 The login information shall be verified within 5 seconds.
NFR-PER-003 The system shall accommodate 500 users at a time simultaneously.
3.5.2.5 Portability
NFR-POR-001The website can be used with any browser with an internet connection.
3.5.2.6 Maintainability
NFR-MAIN-001 The system shall provide capability to back up data
NFR-MAIN-002 The system shall keep a log of all errors.
NFR-MAIN-003 All actions in the system are logged and can be traced back to actor
if necessary.
3.5.2.7 Flexibility
NFR-FLEX-001 The system provides users to update and delete their profile.
NFR-FLEX-002The system provides staff to add, delete and update booking
information.
19
3.6 SYSTEM DESIGN
3.6.1 Introduction
In this section,system modelling is a method used to define and analyse data
requirements that are needed to support the software development.System modelling
able to assist analyst be capable in understanding functionality and models of their
system to present the system to stakeholders.The system modelling and design also
interrelated process to show how the system works and how the system will be
realized during the implementation process.
System are presented in different models which are created from different
perspectives. There are three perseptives such as external,behavior and structural.
Example of model are Framework, context diagram, Data Flow Diagrams (DFD) and
Entity Relationship Diagram (ERD). DFD are modelling the system from functional
aspects. It also can show the flow of data between systems.
While Entity Relationship Diagram are used to describe the relationship
between entities and attributes of entities. It widely available in database modelling.
Next, the another explaination will be available in this chapter.
20
3.6.2 System Framework
Framework is a structure that are needed to solve the complex problem or as known as
the tools and material or component. System Framework also includes actual
programs, specify programming interfaces, or offer programming tools for using
the frameworks. In the Unisza Sports Management System , there are four users that
we called it as admin, staff, student and public.
ADMIN:
They must register the users account for students and staff so that they can login into
the website.The user ID and password that registered by administrator is the user’s ID
when they registered in UniSZA and the password is their IC number.Admin can
delete the registered users.Admin also can view the list of users.Last is admin can
update their profile.
STAFF :
Staff must login first to using User ID and password that registered by Admin.After
successfully login,they can add the equipements and facilities details that will be
viewed by students. Staff will add the payments details so that public can view how
much they must pay for the equipments and facilities that they are booked at the
certain hour and day.Last is Staff can update their profile.
STUDENT:
Student must login first to using User ID and password that registered by
Admin.After successfully login,they can view the availability of eqipmens and
facilities status.They just have to click book button to reserve the facilities.They can
cancel the booking. Last is Student can update their profile.
21
PUBLIC:
Public must register their account first to login into the website.For public,they must
register by enter the username,password and email. After successfully login,they can
view the availability of eqipmens and facilities status.They just have to click book
button to reserve the facilities.They can cancel the booking. They must view the
payment list to pay at the counter later.Last is Public can update their profile.
Figure 3.6.2 :Framework for UNISZA Sport Management System.
22
3.6.3 CONTEXT DIAGRAM
Figure 3.6.3 show the Context Diagram for Unisza Sports Management
System There arefour actor are involved in this system ; Admin,Staff,Student and
Public. In context diagram, the flow of the actors are explained and their ability in this
system.
Figure 3.6.3: Context Diagram
Based on figure 3.6.3, the UNISZA SPORTS MANAGEMENT SYSTEM process at
the center of figure. There are four entities or actors are available are
ADMIN,STAFF,STUDENT and PUBLIC. There are twenty-two data flows in the
Context Diagram. For Admin, there are two ingoing data flow that is USER
DETAILS and ADMIN DETAILS. For Staff, there are five ingoing data flow that is
STAFF DETAILS, EQUIPMENT DETAILS, FACILITIES DETAILS, PAYMENT
DETAILS and BOOKING DETAILS.Staff have two outgoing dataflow that is
23
REPORT DETAILS and USER DETAILS. For Student, there are three ingoing and
two outgoing dataflow that is for ingoing dataflow is STUDENT DETAILS,
EQUIPMENT AND FACILITIES DETAILS and BOOKING STATUS. For outgoing
dataflow is BOOKING INFORMATION and FACILITIES AND EQUIPMENT
INFORMATION. Lastly for Public, there are six dataflow where are both ingoing and
outgoing are three. For outgoing is PAYMENT INFORMATION, BOOKING
INFORMATION and EQUIPMENT AND FACILITIES INFORMATION.Last for
ingoing dataflow is PUBLIC DETAILS, BOOKING DETAILS and EQUIPMENT
AND FACILITIES DETAILS.
3.6.4 Data Flow Diagram
Figure 3.6.4 show the Data Flow Diagram level 0 for the Unisza Sports
Management System. Since the figure 3.6.3 has been explained the flow of the actors;
User and Admin, in this chapter, the more details about the flow are explained with
DFD LEVEL 0 and following by DFD LEVEL 1. The functionality for each process
also will be described and able to help developer to understand their system.
24
Figure 3.3.4: Data Flow Diagram Level 0 for UNISZA-SMS
25
Description of Data Flow Diagram level 0
There are four entities which are ADMIN, STAFF ,STUDENT and PUBLIC.
While there seven process are identified such as MANAGE USER,MANAGE
PROFILE, MANAGE EQUIPMENT ,MANAGE FACILITIES , MANAGE
BOOKING, MANAGE PAYMENT and lastly, MANAGE REPORT. Next, USER,
ADMIN, STAFF, STUDENT, PUBLIC,EQUIPMENT,FACILITIES,BOOKING and
PAYMENT are the eight data stores for UNISZA-SMS.
1. ADMIN and PUBLIC input USER DETAILS into MANAGE USER which
output is USER DETAILS into USER data store.
2. ADMIN input ADMIN DETAILS into MANAGE ADMIN which output is
ADMIN DETAILS into ADMIN data store.
3. STAFF input STAFF DETAILS into MANAGE STAFF which output is
STAFF DETAILS into STAFF data store.
4. STUDENT input STUDENT DETAILS into MANAGE STUDENT which
output is STUDENT DETAILS into STUDENT data store.
5. PUBLIC input PUBLIC DETAILS into MANAGE PUBLIC which output is
PUBLIC DETAILS into PUBLIC data store.
6. STAFF input EQUIPMENT DETAILS into MANAGE EQUIPMENT which
output is EQUIPMENT DETAILS into EQUIPMENT data store, STAFF also
input FACILITIES DETAILS into MANAGE FACILITIES which output is
FACILITIES DETAILS into FACILITIES data store.
7. STUDENT and PUBLIC input BOOKING DETAILS into MANAGE
BOOKING which are the output is BOOKING DETAILS into BOOKING
data stores.
26
8. STAFF input the PAYMENT DETAILS into MANAGE PAYMENT which
the output PAYMENT DETAILS into PAYMENT data store.PUBLIC only
view the PAYMENT DETAILS from PAYMENT data store.
9. All entities and data stores will input the REPORT into MANAGE REPORT
which is output is REPORT.
27
3.6.5 DATA FLOW DIAGRAM LEVEL 1
3.6.5.1 Manage User
Figure 3.6.5.1: Data Flow Diagram Level 1 for Manage User
Description:
An ADMIN input user profile data into ADD NEW USER process and save in USER
data store. STAFF, STUDENTS, ADMIN and PUBLIC send user profile data to the
UPDATE USER PROFILE process and the updated user profile is save to USER data
store. Only ADMIN can DELETE USER PROFILE that retrieve from USER data
store.
28
3.6.5.2 Manage Profile
Figure 3.6.5.2: Data Flow Diagram Level 1 for Manage Admin
Description:
MANAGE PROFILE allows ADMIN and PUBLIC, to ADD PROFILE and save the
profile into ADMIN, STAFF, PUBLIC and STUDENT datastore. ADMIN, STAFF,
STUDENT and PUBLIC allowed to UPDATE PROFILE into their data store and
VIEW their PROFILE that invoke from ADMIN,STAFF ,STUDENT and PUBLIC
data store.
29
3.6.5.3 Manage Equipment
Figure 3.3.5.3: Data Flow Diagram Level 1 for Manage Equipment
Description: 1. MANAGE EQUIPMENT allows STAFF to ADD EQUIPMENT by input the
EQUIPMENT DETAILS into EQUIPMENT data store
2. STAFF can UPDATE EQUIPMENT and DELETE EQUIPMENT by enter the
EQUIPMENT DETAILS into EQUIPMENT data store.STAFF also can VIEW
EQUIPMENT by retrieve the EQUIPMENTS DETAILS from EQUIPMENT data store
3. They also can VIEW EQUIPMENT based on EQUIPMENT DETAILS from
EQUIPMENT data store
30
3.6.5.3 Manage Facilities
Figure 3.6.5.4: Data Flow Diagram Level 1 for Manage Facilities
Description: 1 MANAGE FACILITIES allows STAFF to ADD FACILITIES by input the FACILITIES
DETAILS into FACILITIES data store
2. STAFF can UPDATE FACILITIES and DELETE FACILITIES by enter the FACILITIES DETAILS
into FACILITIES data store. They also can VIEW FACILITIES by retrieve the FACILITIES
DETAILS from FACILITIES data store.
3. STUDENT and PUBLIC also can VIEW FACILITIES by retrieve the FACILITIES DETAILS
from FACILITIES data store.
31
3.6.5.5 Manage Booking
Figure 3.6.5.5: Data Flow Diagram Level 1 for Manage Booking
Description: 1. MANAGE BOOKING allows STAFF to ADD BOOKING by input the BOOKING
DETAILS intobBOOKING data store
2. STAFF can UPDATE BOOKING and DELETE BOOKING by enter the BOOKING
DETAILS into BOOKING data store. They also can VIEW BOOKING by retrieve
the BOOKING DETAILS from BOOKING data store.
3. STUDENT and PUBLIC are need to ADD about BOOKING INFORMATION that
they want to book.
4. STUDENT and PUBLIC can CANCEL or UPDATE the BOOKING STATUS
5. STUDENT and PUBLIC also can VIEW BOOKING by retrieve the BOOKING
DETAILS from BOOKING data store.
32
3.6.6 Entity Relationship Diagram
Figure 3.6.6 Entity relationship Diagram for Unisza-SMS
= One–to-Many relationship(strong entity)
= One-to-Many relationship (weak entity)
33
3.6.7 DATABASE DESIGN SPECIFICATION
Database is the main part of the system development because it will store the
data that are used by the system. The database name is sport where it contains nine
(9) tables which are user, staff, student, public, admin, booking, payment, facilities
and equipment. The following is the list of the table:
3.6.7.1 Introduction
This subchapter will be described into 5 categories which are user zone, admin zone,
staff zone, public zone and student zone. It purpose to make readers easy to read and
understand
3.6.7.2 User Zone
This category is discussed the details about database specification of user.
There are several tables that relate to user.
Table 3.6.7.2: Table user for login
Table 3.6.7.2 showed that data is retrieved from table’s user for user
authentication. There are five attributes which are username, password, typeuser,
34
newpass and email. Username,password and typeuser are used to user login
system.
3.6.7.3 Admin Zone
Table 3.6.7.3: Table Admin detail
Table 3.6.7.3 presented the detail of admin. These data will be inserted in table
of admin. There are 5 atrributes which is adminID as a primary key, adminName,
adminNo, adminemail and adminAddress. A adminNo is an attribute where admin
insert telephone number data.
3.6.7.4 Staff Zone
Table 3.6.7.4: Table staff detail
Table 3.6.7.4 presented the staff details. These data will be inserted in table of
staff. There are 7 atrributes which is staffID as a primary key, staff_FName,
staff_LName, staffNo, staffemail, staffAddress and staffIC.
35
3.6.7.5 Manage booking
Table 3.6.7.5 : Table Booking detail
Table 3.6.7.5 described as containing 11 attributes;bookingID as primary key
,book_date, book_time, book_type, book_status, equipID as a foreign key,faciID as
a foreign key, staffID as a foreign key, studentID as a foreign key,
book_deadline_date and book_deadline_time. book_date and book_time are date
and time that available date and time for students and public book the available
equipment and facilities. While book_type is a whether equipment or facilities.
Book status is such as available or not. These data will be inserted by staff so that
customer will know the schedule of booking.
3.6.7.6 Manage equipment
Table 3.6.7.6: Table Equipment detail
Table 3.6.7.6 described as containing 4 attributes;equipID as primary key
,equipName, equipstatus, PaymentID as a foreign key and staffID as a foreign key.
.Staff will insert these details and the details will be saved in equipment table.
36
3.6.7.7 Manage facilities
Table 3.6.7.7: Table facilities detail
Table 3.6.7.7 described as containing 4 attributes;faciID as primary key
,faciName, facistatus and staffID as a foreign key. .Staff will insert these details and
the details will be saved in facilities table.
3.6.7.8 Manage Payment
Table 3.6.7.8: Table payment detail
Table 3.6.7.8 described as containing 8 attributes;PaymentID as primary key
,paymentstatus, paymentdate, paymenttime, paymenttotal staffID as a foreign key,
publicIDl as a foreign key and studentID as a foreign key.Staff will insert these
details and the details will be saved in payment table.
37
3.6.7.9 Student Zone
Table 3.6.7.9: Table Student detail
Table 3.6.7.9 presented the student details. These data will be inserted in table of
student. There are 7 atrributes which is studentID as a primary key, stud_FName,
stud_LName, studphoneNo, studemail, studAddress and studIC.
3.6.8.0 Public Zone
Table 3.6.8.0: Table public detail
Table 3.6.8.0 presented the detail of public. These data will be inserted in table
of public. There are 6 atrributes which is publicID as a primary key, public_FName,
public_LName, publicNo, publicAddress and publicIC .
38
3.6.9 SUMMARY
In this chapter, a Context Diagram (CD) and Data Flow Diagram (DFD), Database
and Framework had been presented. From this work, the details of the function of the
project also been made. So, the flow of the function of this project will be crystal clear
and helped the development of the project become smooth, unambiguous and
appropriate. CD and Framework are general function while DFD is the very details
function
39
3.6.8 ALGORITHM (CRITERIA FOR PRIORITY-QUEUE)
40
CONCLUSION
This system will help student to book the equipment and facilities without any
problem. Students don’t have to ask about the availability to the staff manually. They
just have to access the website to gain the information. First thing first, the use of
Priority-Queue techniques helps sport management to be scheduled properly. For the
example, when one students book the equipment or facilities, the status of availability
of the equipment or facilities will be updated immediately. So, other students that
were late access to book the equipment will get information immediately and they can
move on to another facilities and equipment at another time and days. So, this makes
sport management at UniSZA more efficient and functionality especially for
students.Lastly,this system also provides the facilities and equipment for outsider.
They could also book the facilities in the system so that they don’t have to come to the
counter and book manually.
41
REFERENCES
[1]Woratschek, Herbert, Chris Horbel, and Bastian Popp. "The sport value
framework–a new fundamental logic for analyses in sport management." European
Sport Management Quarterly 14.1 (2014): 6-24.
[2]Tani, Hicham Gibet, and Chaker El Amrani. "Smarter. Round Robin Scheduling
Algorithm for Cloud Computing and Big Data." (2017).
[3] Dasgupta, Kousik, et al. "A genetic algorithm (ga) based load balancing strategy
for cloud computing." Procedia Technology 10 (2013): 340-347.
[4]Smith, Jed, and Peter Smolianov. "The High Performance Management Model:
From Olympic and Professional to University Sport in the United States." The Sport
Journal, the world’s largest online peer-reviewed scholarly journal of sport with more
than 500 (2016): 1-19.
[5]Muhammad Shariffuddin Bin Mazlan(Fakulti Informatik & Komputeran,UNISZA)
“Online Badminton Courts Booking System Using Priority-Queue Technique.”(2016)
[6]Mahdi Hishamuddin Abdul Aziz, Junaida Sulaiman(Fakulti Sistem Komputer &
Kejuruteraan Perisian,UPM).“UPM Squash Reservation System Using Lighting
Control.”(2016)
[7]Lee,Elizabeth Cheah Hui(UTEM).“Venue And Equipment Online Booking
System.”(2006)
[8]Salmon,James “Automated Sports Club Booking and Enquiry System.”(2002)
[9]Hongchao Xu. Shandong University of Finance and Economics.
“The Research Sports Management Monitoring System Based on WSN.”(2015)
42
APPENDIXES I