emanage event management system · purpose especially during my project presentation. all the...

EMANAGE

EVENT MANAGEMENT SYSTEM

SOLEHUDDIN BIN RAMLI

051675

Bachelor of Computer Science (Software Development) with Honours

Faculty of Informatics and Computing

University Sultan Zainal Abidin

2019

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 and other

institutions.

Signature :

Name : Solehuddin Bin Ramli

Date :

II

CONFIRMATION

This is to confirm that :

This research conducted and the writing of this report was under my supervision

Signature :

Name : Dr Wan Aezwani Binti Wan Abu Bakar

Date :

III

DEDICATION

In the name of Allah the most Gracious and the most Merciful.

Alhamdulillah, thankful to God for His permission I was able to complete the Bachelor

Degree Project entitled Event Management System along with the final report in due time.

As a token of appreciation, I would like to thank my supervisor for this Final Year Project,

Dr Wan Aezwani Binti Wan Abu Bakar for being a responsible and supporting lecturer to guide

and aid me towards the accomplishment of this project. Thank you for brainstorming the ideas

along the solution together for me illustrate the main idea and help in understanding my project

more.

Besides, thank you to my beloved family, especially to my mother, Wan Rohani Binti Wan

Abu Bakar and my father, Ramli Bin Deris who always giving me support and encouragement in

completing this project.

Last but not least, I would like to appreciate to the lecturer, member of panels, friends and

my senior for their valuable feedback and their comment on improving my project for better

purpose especially during my project presentation. All the comments and feedback help me

improve a lot of my presentation skills and my project progress. I hope that the completion of this

assignment will benefit the stakeholders.

IV

ABSTRACT

In university, there are many events that have been organized to the student. This event

helps the student to improve their knowledge and skill. By attending the event, student shows that

they are not only academically concerned but also curriculum-oriented. Mostly event are to be

done at university such as workshop, sport day, dinner and so on. To prepare such an event

requires a lot of works before and after program. All the events that were held have to be captured,

categorized and analyzed. Emanage is imperative for students because this system can help

make it easier for students or anyone to create the event and can encourage the student to make

any program. Easy for the user to find, view and join an upcoming event. The user can put all

program details into the system including tentative and so on. This system is able to make

certificate automatically which can facilitate the affairs of the organizer. The user can choose the

venue for the event using the Global Positioning System (GPS). However, if there are multiple

people to choose the same place at the same time. so here are a lot of things to consider in terms

of category, number of participants and more to determine the venue of the event. To solve this

problem, the priority techniques namely First Come First Serve (FCFS) and Preemptive

Schedulling (PS) will be applied in the proposed system. FSFC is used when there are 2 or more

parties from the same event category who book the same place. So according to this technique,

first-time booking will be possible. while PS, will be used when parties from different event

categories. This technique will evaluate in terms of priority category, number of participants and

booking time.

V

ABSTRAK

Di universiti, terdapat banyak acara yang telah dianjurkan kepada pelajar. Acara ini

membantu pelajar meningkatkan pengetahuan dan kemahiran mereka. Dengan menghadiri

acara itu, pelajar menunjukkan bahawa mereka bukan sahaja berminat secara akademik tetapi

juga berorientasikan kurikulum. Kebanyakan acara akan dilakukan di universiti seperti bengkel,

hari sukan, makan malam dan sebagainya. Untuk menyediakan acara sedemikian memerlukan

banyak kerja sebelum dan selepas program. Semua peristiwa yang perlu diambil, dikategorikan

dan dianalisis. Emanage adalah penting untuk pelajar kerana sistem ini dapat membantu

memudahkan pelajar atau sesiapa sahaja untuk membuat acara dan boleh menggalakkan pelajar

membuat sebarang program. Mudah untuk pengguna mencari, melihat dan menyertai acara yang

akan datang. Pengguna boleh meletakkan semua butiran program ke dalam sistem termasuk

tentatif dan sebagainya. Sistem ini dapat membuat sijil secara automatik yang dapat memfasilitasi

urusan penganjur. Pengguna boleh memilih tempat acara menggunakan Sistem Posisi Global

(GPS). Walau bagaimanapun, jika terdapat ramai orang untuk memilih tempat yang sama pada

masa yang sama. jadi inilah banyak perkara yang harus dipertimbangkan dari segi kategori,

bilangan peserta dan banyak lagi untuk menentukan tempat acara tersebut. Untuk menyelesaikan

masalah ini, teknik prioriti iaitu First Come First Serve (FCFS) dan Preemptive Schedulling (PS)

akan digunakan dalam sistem yang dicadangkan. FSFC digunakan apabila terdapat 2 atau lebih

pihak dari kategori acara yang sama yang menempah tempat yang sama. Jadi mengikut teknik

ini, tempahan kali pertama mungkin dilakukan. manakala PS, akan digunakan apabila pihak dari

kategori acara berbeza. Teknik ini akan menilai dari segi kategori keutamaan, bilangan peserta

dan masa tempahan.

VI

TABLE OF CONTENTS

CONTENT PAGE

DECLARATION

CONFIRMATION

DEDICATION

ABSTRACT

ABSTRAK

TABLE OF CONTENTS

LIST OF FIGURES

LIST OF TABLES

LIST OF ABBREVIATIONS / TERMS / SYMBOLS

LIST OF APPENDICES

I

II

III

IV

V

VI

VIII

IX

CHAPTER I

INTRODUCTION

1.1 Background

1.2 Problem Statement

1.3 Objectives

1.4 Scope

1.5 Limitation of Works

1.6 Expected Outcome

1

1

1

1

2

3

3

CHAPTER II

LITERATURE REVIEW

2.1 Introduction

2.2 System Problem

2.3 Table of Literature Review

2.4 Solution complexity

2.5 Conclusion

4

4

4

5

6

7

VII

CHAPTER III

METHODOLOGY

3.1 Introduction

3.2 Justification

3.3 Project Methodology

3.4 System Requirements

3.5 Logical Model

8

8

8

9

11

13

CHAPTER IV

IMPLEMENTATION AND RESULT -

CHAPTER V

CONCLUSION -

REFERENCES 24

VIII

LIST OF FIGURE

Content Page

Figure 3-1 : Iterative model and Incremental Development

Figure 3-2 : CD

Figure 3-3 : DFD Level 1

Figure 3-4 : DFD Level 2 Process 1.0







Figure 3-11 : ERD for Event Management System

9

13

15

16

17

18

19

20

21

22

23

IX

LIST OF TABLE

Content Page

Table 2-1 : Literature Review

Table 3-1 : Software Requirement

Table 3-2 : Hardware Requirement

5

12

12

1

CHAPTER 1

INTRODUCTION

1.1 Background

Emanage is a web-based system which will help to organizer to organize and

manage their event more efficiently and smoothly. It used to manage all the activity related

to event. Emanage is imperative for students because this system can help make it easier

for students or anyone to create the event and can encourage the student to make any

program. In the system, user can create event, add committee member, edit event

information and so on. It also can easy for the user to find, view and join an upcoming

event. Emanage will provide template for tentative. This system also provide notifications

to participants before the event as a reminder and will auto generate certificate for all

participants.

1.2 Problem Statement

● In present system, organizer has to do all management work manually.

● Organizer should always remember the event to participants

● Old system takes a lot of time and tiresome

1.3 Objectives

● To design the system that can make a certificate automatically and issue it/mail it for

any event. Also all participants will receive a notification to recall the event.

● To develop a platform for users that can manage the event and for users to find any

event they want to join.

● To test the functionalities of the developed system to meet the user requirement.

2

1.4 Scope

1.4.1 User Scope

I. Admin

● Login ad admin

● Create clubs / associations

● Register and manage all user

● View all event

II. Advisor

● Register student committee (committee member)

● View all event under the club

● Accept or reject any program

● Able to create event (personal or under club)

III. Lecturer

● Login as Lecturer

● Manage Profile

● Able to view upcoming event

● Confirm the signature

● Able to create event (personal or under club)

IV. Student

● Login as student

● Manage Profile

● Able to view and join upcoming event

● Able to create event (under club only)

● Able to view event (as a program director)

3

1.4.2 System Scope

● Log in / Log out for SuperAdmin, Admin, lecturer and student

● Update user information

● Recorded student attendance

● Able to generate certificate and tentative

● Automatically display the event approved

1.5 Limitation of Works

● There are no devices provided for this system (provide 1 platform only)

● This system only can be used for specific group of organization (eg : UniSZA)

1.6 Expected Outcome

● This system can help make it easier for any student to create the event

● User can easily to find, view and join upcoming event

● This system facilities the collection of the event data that has been implemented

● This system able to make certificate and tentative automatically

● Able to see where the program will be held using Global Positioning System (GPS)

4

CHAPTER 2

LITERATURE REVIEW

2.1 Introduction

This chapter discussed simple summary of the some sources, in which was

reviewed before developing a certain system. It gives me a new interpretation of old

materials related directly and indirectly to the Event Management System or it might trace

the intellectual progression of the field, including major debates. By the literature review, I

had summarized, compared and evaluated all those researches.

2.2 System Problem

Most universities still use the old method of managing programs. It is difficult to

manage using traditional system using spreadsheets, traditional database and more.

There are many systems that can be used.

The system problem is revealing the comparison between the existing system or

applications with its strength and limitation

There are already some existing related software in the market such as Eventbrite,

RegOnline and Peatix (Capterra, 2015). However, problems in existing systems are high

cost, complexity and incontinence. For Eventbrite, it is a good software but some of the

features are hidden. Users need to look at FAQ for certain problems. The software has

some problem with payment met

5

2.3 Table of Literature Review

Author / Year Project Name Description Advantages Disadvantages

R Deepika,

Gayathri2,

Saravanakumar,

Vigneshwaran, K

Vignesh

(2016)

Android

Application for

Event

Management

System

- The main is to

manage and

handle the

events of an

organization. It is

used to keep the

records of an

event in an

organization

- Register

anytime using

mobile

application

- Timely

updates of the

events can be

sent to the

participants

NA

Mr. Krunal

Maiske, Ms.

Pooja Neware,

Ms. Nikita

Jamgade, Ms.

Aishwarya

Jamgade, Ms.

Pooja Dubey

(2017)

Smart Event

Management

System

- This system

uses the modern

technology for

managing

various tasks

and planning

- Allow registered

user login and

new user are

allowed to

register

- Reduce

distance

between

customer and

management

team

- Cover large

scale events

NA

M.Mahalakshmi,

S.Gomathi,

S.Krithika

(2016)

Event

Management

System

- The main idea of

this project is to

sent the Student

Registration time

through sums

with verification

code to the

student using

- It reduces the

direct

communicatio

n to student

- Avoid the mall

function of the

student to

event join and

- Need

internet

connection

for some

applications

6

mobile

application

based on

Android App.

participating

for android to

android where

ever it is.

Table 2-1 : Literature Review

2.4 Solution complexity

Solution complexity part explained about the possible solution that will be applied in this system.

thus, the technique that we will be used is Priority Scheduling

2.4.1 Preemptive Priority Scheduling

The technique that will be used into the system is preemptive priority

scheduling. In Preemptive Priority Scheduling, at the time of arrival of a process in

the ready queue, its Priority is compared with the priority of the other processes

present in the ready queue as well as with the one which is being executed by the

CPU at that point of time. The One with the highest priority among all the available

processes will be given the CPU next. What to highlight here is in the preemptive

priority scheduling, the job which is being executed can be stopped at the arrival

of a higher priority job.

By looking from the perspective of Emanage, this technique will be

implemented to see who is more qualified to get a place to run the program based

on certain characteristics like categories, number of participants, booking time and

so on. Each characteristic has been assigned a priority value in the database. And

from this, this algorithm will calculate and average each priority value that is output

7

2.5 Conclusion

In this chapter, technique to be used is studied and a few collection of literature

review has been done. By this, knowledge have been gain to help to develop a good and

functioning system. By literature review also helps to gain knowledge about technique and

past systems that has been used in previous research.

8

CHAPTER 3

METHODOLOGY

3.1 Introduction

In this chapter, the methodology in this system development will be discussed.

Methodology is a defined combination of logically related practices, methods and

processes that determine how best to design, develop and deliver a project throughout

the continuous implementation process until successful completion and termination. It is

a scientifically proven, systematic and disciplined approach to project design, execution

and completion. The project methodology should be organized in a scientific investigation

to solve problems to make sure this project achieves the objective and target.

3.2 Justification

I choose iterative and incremental development model as my methodology model

because it allows more flexibility to adapt to changes. This is because the system is open

to changes due to the modification of requirements from time to time. Even when the

changes occur in the middle of the system’s development, this methodology allows the

changes to take place.

9

3.3 Project Methodology

Figure 3-1: Iterative model and Incremental Development

Figure 3.3.1 shows the methodology that had been used from the beginning until the end

of this project. There are 8 phases in this methodology include Initial Planning, Planning,

Requirements, Analysis and Design, Implementation, Testing, Evaluation and Deployment. The

6 phases in the cyclic can be iterated from time to time in line with continuous user feedback and

incremental addition of new features.

3.3.1 Initial Planning Phase

This phase is where brainstorming for ideas to come up with a system takes

place. I had a brief discussion with my supervisor where I named a few systems

that I could come up with and had her recommend which system to proceed with.

10

3.3.2 Planning Phase

This phase involves the detailing of the selected system from the previous

phase. This is where I had to come up with the problem statement, objectives and

scope of the system. In order to have a wider understanding of the system, I had

conducted a few researches by reviewing works of literature related to the chosen

system. I also had to choose a technique to be implemented while developing the

system.

3.3.3 Requirement Phase

This phase is where user and system requirements are collected. The

requirements were gained by random interviews, a brief discussion with my

supervisor and the literature review carried out from the previous phase.

3.3.4 Analysis and Design Phase

During this phase, two main tasks are to be completed and it is data

analysis and system design. The requirements collected from the previous phase

were analyzed to see if they are fit for the system. As for the system design, it is

then divided into two parts - logical model and physical model. The logical model

consists of the Entity Relationship Diagram (ERD), Context Diagram (CD) and

Data Flow Diagram (DFD) while the physical model consists of the database

design and user interface or mock-up.

3.3.5 Implementation Phase

This phase simply refers to the development of the system by taking all

requirements and specifications collected from the above phases into

consideration

11

3.3.6 Testing Phase

During this phase, the system is tested to make sure that it fulfills all the

requirements listed and to test the completeness of it. There are a few software

testing types that can be implemented during this phase.

3.3.7 Evaluation Phase

This phase allows the system to be evaluated first before being introduced

to end users. Any best practices or techniques used in the previous iterations can

be used again in the upcoming iterations

3.3.8 Deployment Phase

This phase determines that the full system is ready to be delivered to end

users.

3.4 System Requirements

System requirement is needed to achieve this project and assist the development

of the project that involves system requirement in hardware and software. All of these

elements are important in the process of development of this project. List of hardware and

software are shown as below:

12

3.4.1 Software

No Software Description

1. Google Drive To backup all the document

2. Atom Cross-platform source code editor

3. Microsoft Word 2016 As a platform for documentation of the report

4. MySQL database Open source relational database management

system that uses structured Query Language

and store the data of the system.

5. Edraw Max As a tool to create and design CD, DFD and

ERD

6. XAMPP Server Act as a local server to run and test the system

Table 3-1 : Software Requirement

3.4.2 Hardware

No Hardware Description

1. Laptop Acer Aspire 14

2. Processor Intel(R) Core(TM) i5-6200 CPU @ 2.30GHz

2.40GHz

3. Memory DDR4 12GB RAM

4. Operating System Windows 10

5. System Type 64-bit Operating System

6. Thumb drive Apacer 32GB

Table 3-2 : Hardware Requirement

13

3.5 Logical Model

A logical model is used to evaluate the effectiveness of a program, can also be used during

planning and implementation. Logics model are usually a graphical depiction of the logical

relationship between the resources, activities, outputs and outcomes of a program.

3.5.1 Context Diagram

Figure 3-2 : Context Diagram (CD)

A context diagram is a diagram that represents the data flow of main

module. Event Management System process is at the center of the diagram. The

four actors (Admin, Advisor, Lecturer and Student) are each placed on around the

process.19 data flow are involved in the interaction between the central process

and the 4 actors.

The Admin has 4 outgoing data flows (Club and Association info, Advisor

Info, Lecturer info and Student info) and one incoming data flows (view event

detail). The Advisor has 3 outgoing data flow (Event Info, Committee Info and

Update Advisor Info) and 3 incoming data flow (Advisor Info Record, Committee

14

Info Record and View Event Detail). The Student has 3 incoming data flow (View

Event Detail, Event Info and Student Info Record) but only has 1 outgoing data

flow (Update Student Info). Then, the Lecturer has 2 outgoing data flow (Event Info

and Update Lecturer Info) and also has 2 incoming data flow which is (Lecturer

Info Record and View Event Detail)

15

3.5.2 Data Flow Diagram (DFD) level 1

Figure 3-3 : Data Flow Diagram Level 1

Data Flow Diagram (DFD) is a graphical representation of the flow data

through an information system. It shows how a system’s environmental entities,

processes and data are interconnected and also the data is stored in the

databases. It also shows what kind of information will be input to and output from

the system, where the data will come from and go to and where the data will be

stored.

Figure 3-3 above shows the DFD that consist of 4 entities and 7 processes.

The 4 entities are Admin, Advisor, Lecturer and Student while the other 7

processes are Manage Club, Manage Lecturer, Manage Student, Assign Advisor,

Assign Committee, Manage Event and Generate Report. All processed data will

be stored in the provided data store which is Club and Association, Lecturer,

Student, Advisor, Committee and Event.

16

3.5.2.1 Data Flow Diagram Level 2

i) Manage Club and Association

Figure 3-4 : DFD level 2 Process 1.0

Figure 3-4 shows Data Flow Diagram Level 2 Process 1.0, this

process only involve by Admin, 1 data store and 3 process. In this process,

only Admin can register, update and delete Club and Association.

17

ii) Manage Lecturer



process involved by Admin and Lecturer, 1 data store and 4 process. In

this process, Admin can add, update and delete lecturer data. While for

lecturer, they can only update their profile and view information.

18

iii) Manage Student



process involved by Admin and Student, 1 data store and 4 process. In this

process, Admin can add, update and delete lecturer data. While for

lecturer, they can only update their profile and view information.

19

iii) Assign Advisor



process involved by 2 entity, 3 data store and 4 process. In this process,

Admin take lecturer data to assign advisor for club and association. Admin

also can update and remove advisor. Each record will be entered into the

data store (Advisor & Club and Association). While for Advisor, they can

only update their profile and view information.

20

iv) Assign Committee



process also involved by 2 entity, 3 data store and 4 process. In this

process, Advisor take student data to assign committee for club and

association. Advisor can update and remove committee. Each record will

be entered into the data store (Committee & Club and Association). While

for Student, they can only update their profile of committee and view

information.

21

v) Manage Event




Advisor, Lecturer and Student can create, update and delete their own

event. After that, they can get their event information. While the admin can

view all event that exists

22

vi) Generate Report




admin can view all report. But for Advisor, they can view the report involved

only.

23

3.5.3 Entity Relationship Diagram (ERD)

Figure 3-11 : ERD for Event Management System

An Entity Relationship Diagram (ERD), also known as an entity relationship

model, is a graphical representation of an information system that shows the

relationship among people. Objects, places, concepts or events within that system.

24

REFERENCE

1) M.Mahalakshmi, S.Gomathi and S.Krithika, (2016), Event Management System.

International Journal of Trend in Research and Development, Volume 3(2), ISSN: 2394-

9333

2) Mr. Krunal Maiske, Ms. Pooja Neware, Ms. Nikita Jamgade, Ms. Aishwarya Jamgade, Ms.

Pooja Dubey, (2017), Review Paper on Event Management System.

International Journal for Research in Applied Science & Engineering Technology

(IJRASET) ISSN: 2321-9653; IC Value: 45.98;

3) Deepika, R Gayathri, T Saravanakumar, K Vigneshwaran, K Vignesh, (2016), Android

Application for Event Management System.

International Conference on Systems, Science, Control, Communication, Engineering

and Technology 2016: ISSN: 328-330.

4) https://www.javatpoint.com/os-preemptive-priority-scheduling

5) Nurul Najwa Binti Awang Harun, (2018), Event Planning Suggestion System Using Rule

Based, University Sultan Zainal Abidin.

https://www.javatpoint.com/os-preemptive-priority-scheduling

emanage event management system · purpose especially during my project presentation. all the...

Documents