SATHYABAMA EMS

(EVENT MANAGEMENT SYSTEM)

Submitted in partial fulfillment of the requirements for the award of

Bachelor of Engineering degree in Computer Science and Engineering

By

BONAGIRI KEERTHI (Reg.No - 39110183)

PYDR PRIYANKA (Reg.No – 39110719)

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

SCHOOL OF COMPUTING

SATHYABAMA
INSTITUTE OF SCIENCE AND TECHNOLOGY
(DEEMED TO BE UNIVERSITY)
Accredited with Grade ―A‖ by NAAC | 12B Status by UGC | Approved by AICTE
JEPPIAAR NAGAR, RAJIV GANDHI SALAI,
CHENNAI - 600119

APRIL - 2023

i
 DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

BONAFIDE CERTIFICATE

This is to certify that this Project Report is the bonafide work of Bonagiri Keerthi
(Reg.No - 39110183) and PYDR Priyanka (Reg.No - 39110719) who carried out
the Project Phase-2 entitled ―SATHYABAMA EMS (EVENT MANAGEMENT
SYSTEM)‖ under my supervision from January 2023 to April 2023.

Internal Guide

DHANALAKSHMI K M.E.,

Head of the Department

Dr. L. LAKSHMANAN, M.E., Ph.D.

Submitted for Viva voce Examination held on 20.4.2023

Internal Examiner External Examiner

ii
 DECLARATION

I, BONAGIRI KEERTHI (Reg.No – 39110183), hereby declare that the Project

Phase-2 Report entitled ‖SATHYABAMA EMS (EVENT MANAGEMENT
SYSTEM)‖ done by me under the guidance of DHANALAKSHMI K is submitted in
partial fulfillment of the requirements for the award of Bachelor of Engineering
degree in Computer Science and Engineering.

DATE:20.4.2023

PLACE: Chennai SIGNATURE OF THE CANDIDATE

iii
 ACKNOWLEDGEMENT

I am pleased to acknowledge my sincere thanks to the Board of Management of

SATHYABAMA for their kind encouragement in doing this project and for
completing it successfully. I am grateful to them.

I convey my thanks to Dr. T.Sasikala M.E., Ph. D, Dean, School of Computing, and
Dr. L. Lakshmanan M.E., Ph.D., Head of the Department of Computer Science and
Engineering for providing me with necessary support and details at the right time
during the progressive reviews.

I would like to express my sincere and deep sense of gratitude to my Project Guide
DHANALAKSHMI K for her valuable guidance, suggestions, and constant
encouragement paved the way for the successful completion of my phase-1 project
work.

I wish to express my thanks to all Teaching and Non-teaching staff members of the
Department of Computer Science and Engineering who were helpful in many
ways for the completion of the project.

iv
 ABSTRACT

To assist faculty and students in managing college activities, a system known as the
Sathyabama Event Management System (SEMS) has been developed. For
instance, technical festivals and other events that necessitate web-based user
registration. This responsive and dynamic web application makes it simple for users
of the event management system to interact with and register for the events of their
choice. This will do away with the requirement for extra paperwork. The SEMS
application will be designed to be user-friendly and will cater to the needs of
students, faculty, and staff members. College activities play an important role in the
overall development of students. They help students build leadership skills,
socialize, and develop their interests and hobbies. However, managing college
activities can be a challenging task, especially when there are multiple events
happening simultaneously. To address this challenge, a SEMS application can be
developed to simplify the process of managing college activities.

v
 TABLE OF CONTENTS

Chapter
No
TITLE Page No.

ABSTRACT v

LIST OF FIGURES viii

1 INTRODUCTION 1

LITERATURE SURVEY
2 3
2.1 Inferences from Literature Survey

2.2 Open problems in Existing System 6

2.3 Proposed System 6

3 REQUIREMENTS ANALYSIS 8
3.1 Feasibility Studies/Risk Analysis of the Project 8
3.2 Software Requirements Specification Document 12
3.3 System Use case 20
4 DESCRIPTION OF PROPOSED SYSTEM 21

4.1 Selected Methodology or process model 21

4.2 Architecture / Overall Design of Proposed System 23

Description of Software for Implementation and Testing plan 33

4.3
of the Proposed Model/System
4.4 Project Management Plan 36

4.5 Financial report on estimated costing 37

4.6 Transition/ Software to Operations Plan 38

5 IMPLEMENTATION DETAILS 40

5.1 Development and Deployment Setup 40

5.2 Testing 43
6 RESULTS AND DISCUSSION 44
7 CONCLUSION 45

7.1 Conclusion 45

7.2 Future work 45

7.3 Research Issues 46

vi
 7.4 Implementation Issues 47

REFERENCES 49

APPENDIX 50

A. SOURCE CODE 50

B. SCREENSHOTS 61

C. RESEARCH PAPER 69

vii
 LIST OF FIGURES

FIGURE FIGURE NAME PAGE

NO. NO.
3.1 Php 15
3.2 Database 16
4.1 Process model 22
4.2 Waterfall model 22
4.3 Client-servermodel 23

4.4 Architecture 24
4.5 Er diagram 26
4.6 Use case diagram for student 27

4.7 Use case diagram for administrator 27

4.8 Data flow Diagram forlevel-1 28

4.9 Data flow diagram for level 1.1 30

adding events

4.10 Data flow Diagram forlevel 1.1.0 30

4.11 User login page(sequence Diagram 31

For students)

4.12 31
User with server

viii
 CHAPTER 1

INTRODUCTION

Sathyabama Event management system was web-based application that enhanced

project management to the creation and development of large scale events such as
festivals, conferences, formal parties, concerts, or conventions. The Sathyabama
Event management system (SEMS) enabled students/faculty view various details
about the event and make booking through the online platform. The management
of events must be seen as an interdisciplinary task field requiring effective and
efficient cooperation between diverse partners. The strategic preparation, as well as
the planning and coordination of the execution of an event require professional
handling in order to guarantee the optimal interplay between all participants. Due to
the two characteristics – time limitation (clearly defined start and finish points) and
singularity (often one-time initiative), events possess project character.

The process of planning and coordinating the event is usually referred to as event
planning and it included budgeting, scheduling, site selection, acquiring necessary
permits, coordinating transportation and parking, arranging for speakers or
entertainers, arranging decor, event security, catering, coordinating with third party
vendors, and emergency plans. Each event was different in its nature so process of
planning & execution of each event differed on basis of type of event. This software
is supported to eliminate and in some cases reduce the hardships faced by this
existing system. Moreover this system is designed for the particular need of the
college to carry out operations in a smooth and effective manner.

The application is reduced as much as possible to avoid errors while entering the
data. It also provides error message while entering invalid data. No formal
knowledge is needed for the user to use this system. Thus by this all it proves it is
user-friendly. Event Management System, as described above, can lead to error
free, secure, reliable and fast management system. It can assist the user to
concentrate on their other activities rather to concentrate on the record keeping.
Thus it will help organization in better utilization of resources.

1
PROBLEM STATEMENT

Event Management system is manual and only accessible to staff. The client has to
travel to the company offices in order to schedule, book and organize an event such
as paper presentation poster presentation etc. Clients pay cash to book for an event
which is inconveniencing when customers are many at the company. It takes lots of
time of customer because they have to search such event organizer and contact
them individually so an online event management system is needed which will
enable the customer make booking, schedule events online at any preferred time.

2
 CHAPTER 2

LITERATURE SURVEY

2.1 INFERENCES FROM LITREATURE SURVEY

Amite Sharma et al. / International Journal of Engineering Science and

Technology (IJEST)

Nowadays, the event industry has played a vital role in our society. People have
come up with a lot of occasions for organizing events such as educational events,
birthdays, international conferences, company parties etc. Generally speaking,
events are also a part of human beings' social life because they get to know and
talk with different people with different backgrounds. However, in order to organize
a good and successful event, it requires a thorough and detailed planning process.
Event managers and event coordinators need to collaborate in order to formulate
the most viable plan for events. In order to make events successful and well
organized, all of the stages in the entire planning process also need to be in harmony
and become related with one another. Risk management has been of great
importance during the entire planning process. Under no circumstances should risk
management be underestimated. Additionally, evaluation process helps event
organizers and event managers to realize which aspects should be improved and
need familiar development. (Bowdin, Glenn, 2010) The event management industry
is a dapper of a dandy. Due to the endless changes and sweeping improvements in
the current events technology, there's no place for stability.

Student Relationship Management: Concept, Practice and Technological

Support

Information systems used at higher education institution support essentially

academic management processes like student's registration, student's
management, student's marks, among others. These systems do not permit the
closely monitoring of student's academic activities, the evaluation of their academic
success and the support of academic activities concerning with teaching and
tutoring. On the other hand, it is largely accepted that there exists a strong
correlation between the closely monitoring of the students' activities and the scholar
success promotion. To support the teaching and tutoring processes it is essential to

3
acquire knowledge about the students. This knowledge will allow the adoption of
adequate and effective actions/decisions in order to closely follow the students'
activities. In order to be possible such procedures, this paper proposes a student
relationship management (SRM) system. This system will support the SRM concept
and the SRM practice and will be implemented using the concepts and the
technological infrastructure that supports the Business Intelligence systems. The
concept, practice and architecture of the SRM system are presented in this paper
and its main goal is to provide a technological tool that support higher education
institution in the acquisition of knowledge that is essential to the decision- making
process.

Requirements Analysis for a Student Relationship Management System--

Results from an Empirical Study in Ivy League Universities
The higher education sector encounters increasing number of students with more
diverse attributes, expectations, and demands. In times of sinking budgets and
severe competition among universities, student relationship management (SRM)
has become a key instrument in attracting paying students and retaining a long-
lasting relationship, which in turn provides financial benefits and enhances the
reputation of the university. In this paper, a structured literature review revealed a
lack of requirement analysis for a student relationship management system (SRMS)
from the target group perspective. An online survey was conducted with students
and alumni from four Ivy League universities. The survey showed that university
administration needs to improve their relationship and communication habits with
the target groups. Because modern communication channels such as social
network, blogs and apps are not yet wide-spread in this context, SRMS need to be
further enhanced to include them.

Learning Analytics in Higher Education — The Path Toward Educational

Management Intelligent Systems
The rapid expansion of information and communication technologies in relation to
big data analysis generates the vital demand to gain the maximum benefit of the 'big
data'. Business intelligence and learning analytics are recently drawing considerable
attention in market and society being one of the most competitive and profitable
areas of interest to businesses and organizations, including higher education
institutions. Business intelligence systems have already demonstrated significant

4
impact on strategic decision making and trends forecasting. Learning analytics is
going to extend the value of business intelligence in the field of education and
training in proportion to retention, students' success and satisfaction. Hence, the
overall organization's performance and ranking -in a wider scope-will be
transformed toward informed, timelier, high-valued, evidenced and high-quality
decisions benefiting the students, and accordingly, achieving sustainable
organization's performance in a middle term, and society advancement in a longer
term. This paper focuses on investigating the potential of business intelligence
approaches toward a meaningful analysis of the organization's and student's
experience by making use of business intelligence enhanced learning analytics. It
provides valuable insights into the integration and use of business intelligence in the
learning analytics application area by highlighting recent research and
developments. Furthermore, it suggests paths to resolving current issues in the
interrelationship between higher education institutions' and learning performance by
designing a novel closed-loop feedback framework that aims at improving the
learning outcomes for the students, and the organization, and prepares for smart
educational management.

Based on a literature survey on event management systems, several key inferences

can be drawn:

1. Importance of technology: There is a growing importance of technology in

event management systems. Advancements in technology have enabled event
organizers to automate many aspects of event planning and execution, such as
registration, ticketing, and marketing.

2. Customizability: Event management systems are highly customizable to suit

the specific needs of different types of events and organizations. This includes
custom branding, ticketing options, and marketing tools.

3. User experience: The user experience of event management systems is

crucial to their success. Event organizers need to ensure that the system is easy to
use and navigate for both themselves and their attendees.

4. Integration: Integration with other systems, such as social media and email
marketing platforms, is important for maximizing the reach and impact of events.

5
5. Analytics: Event management systems are increasingly incorporating
analytics tools to help organizers measure the success of their events and identify
areas for improvement.

6. Mobile optimization: With the growing use of mobile devices, event

management systems need to be optimized for mobile devices to ensure that
attendees can easily access event information and registration.

7. Security: Event management systems must have robust security measures

in place to protect sensitive information, such as attendee data and financial
transactions.

Overall, event management systems are becoming more sophisticated and

specialized, with a focus on improving the user experience, customization, and
integration with other systems

2.2 OPEN PROBLEMS IN EXISTING SYSTEM

In the existing system customer contacts, the college for event management. He
provides the details of the event and its requirements. He explains its aims, how
long it will last, its format (Presentation/Workshop and/or Exhibition etc.), expected
number of delegates/guests, equipment and furniture required, whether any
delegate pack or promotional material is to be distributed, and other facilities
required. The Event Manager studies the requirements of the event carefully and
using the event management system. The company offers some readymade
packages to choose from. If the customer agrees, the event is booked and the
advance deposit is taken by the company. According to the requirements of the
event, different bookings are made. A strategic schedule is prepared for smooth
conduct of the event. The Event Management System helps the manager in different
tasks of planning, scheduling and conducting the event.

2.3 PROPOSED SYSTEM

The next phases in the development of this new system will try to automate the full
process while maintaining the database implementation strategy in view. The
student's name and mobile number are saved in this database. This system will
provide online search and assist functionalities. The application is user-friendly, with
a wide range of features provided via a system-rich user interface. This application

6
is only available to registered users. Event data files can be stored in a centralized
database managed by the system. The personnel can manage events methodically
thanks to this technology

7
 CHAPTER 3

REQUIREMENT ANALYSIS

3.1 FEASIBILITY STUDIES/RISK ANALYSIS OF THE PROJECT

SCOPE

It may help collecting perfect management in details. In a very short time, the
collection will be obvious, simple and sensible. It will help a person to know the
management of passed year perfectly and vividly. It also helps in current all works
relative to Event Management System. It will be also reduced the cost of collecting
the management & collection procedure will go on smoothly.

Our project aims at Business process automation, i.e. we have tried to

computerize various processes of Event Management System.

In computer system the person has to fill the various forms & number of copies of
the forms can be easily generated at a time.

 In computer system, it is not necessary to create the manifest but we can

directly print it, which saves our time.
 To assist the staff in capturing the effort spent on their respective working
areas
 To utilize resources in an efficient manner by increasing their productivity
through automation.
 The system generates types of information that can be used for various
purposes.
 It satisfy the user requirement.
 Be easy to understand by the user and operator
 Be easy to operate
 Have a good user interface
 Be expandable
 Delivered on schedule within the budget.

8
OBJECTIVE

The main objective of the Project on Event Management System is to manage the
details of Event, Activity, Organizers, Attendees, Conductors. It manages all the
information about Event, Payment, Conductors, Event. The project is totally built at
administrative end and thus only the administrator is guaranteed the access. The
purpose of the project is to build an application program to reduce the manual work
for managing the Event, Activity, Payment, Organizers. It tracks all the details about
the Organizers, Attendees, Conductors.

FEASIBILITY STUDY

After doing the project Event Management System, study and analyzing all the
existing or required functionalities of the system, the next task is to do the feasibility
study for the project. All projects are feasible given unlimited resources and infinite
time.

Feasibility study includes consideration of all the possible ways to provide a solution
to the given problem. The proposed solution should satisfy all the user requirements
and should be flexible enough so that future changes can be easily done based on
the future upcoming requirements.

Economical Feasibility

This is a very important aspect to be considered while developing a project. We

decided the technology based on minimum possible cost factor.

 All hardware and software cost has to be borne by the organization.

 Overall we have estimated that the benefits the organization is going to
receive from the proposed system will surely overcome the initial costs
and the later on running cost for system.

Technical Feasibility

This included the study of function, performance and constraints that may affect
theability to achieve an acceptable system. For this feasibility study, we studied
complete functionality to be provided in the system, as described in the System
Requirement Specification (SRS), and checked if everything was possible using
different type of frontend and backend plaformst.

9
 Operational Feasibility

No doubt the proposed system is fully GUI based that is very user friendly and all
inputs to be taken all self-explanatory even to a layman. Besides, a proper
training has been conducted to let know the essence of the system to the users
so that theyfeel comfortable with new system. As far our study is concerned the
clients are comfortable and happy as the system has cut down their loads and
doing.

SECURITY TESTING OF THE PROJECT

Testing is vital for the success of any software. no system design is ever perfect.
Testing is also camed in two phases. first phase is during the software engineering
that is during the module creation. second phase is after the completion of software.
this is system testing which verifies that the whole set of programs hanged together.

White Box Testing:

In this technique, the close examination of the logical parts through the software
are tested by cases that exercise species sets of conditions or loops all logical
parts of the software checked once errors that can be corrected using this
technique are typographical errors, logical expressions which should be executed
once may be getting executed more than once and error resulting by using wrong
controls and loops. When the box testing tests all the independent part within a
module a logicaldecisions on their true and the false side are exercised, all loops
and bounds within their operational bounds were exercised and internal data
structure to ensure their validity were exercised once.

Black Box Testing:

This method enables the software engineer to device sets of input techniques
that fully exercise all functional requirements for a program. black box testing
tests the input, the output and the external data. it checks whether the input data
is correct and whether we are getting the desired output.

Alpha Testing:

Acceptance testing is also sometimes called alpha testing. Be spoke systems are
developed for a single customer. The alpha testing proceeds until the
system

10
 developer and the customer agree that the provided system is an acceptable
implementation of the system requirements.

Beta Testing:

On the other hand, when a system isto be marked as a software product, another
process called beta testing is often conducted. During beta testing, a system is
delivered among a number of potential users who agree to use it. The customers
then report problems to the developers. This provides the product for real use
and detects errors which may not have been anticipated by the system
developers.

Unit Testing:

Each module is considered independently, it focuses on each unit of software as

implemented in the source code. it is white box testing.

Integration Testing:

Integration testing aims at constructing the program structure while at the same
constructing tests to uncover errors associated with interfacing the modules,
modules are integrated by using the top down approach.

Validation Testing:

Validation testing was performed to ensure that all the functional and
performance requirements are met.

System Testing:

It is executing programs to check logical changes made in it with intention of

finding errors a system is tested for online response, volume of transaction,
recovery from failure etc. System testing is done to ensure that the system
satisfies all the user requirements.

To conduct a feasibility study and risk analysis for an event management system,
the following steps can be taken:

 Identify the scope and objectives of the event management system.

11
  Determine the key features and functionalities of the event management
system, such as event registration, payment processing, ticketing, event
promotion, attendee management, and reporting.
 Conduct market research to determine the demand for the event
management system and identify potential competitors.
 Evaluate the technical feasibility of developing the event management
system, including the availability of the necessary hardware, software, and
infrastructure.
 Assess the financial feasibility of the event management system, including
the cost of development, maintenance, and support, as well as the potential
revenue from the system.
 Identify potential risks associated with the event management system, such
as security risks, data breaches, system failures, and legal compliance
issues.
 Develop risk management strategies to mitigate the identified risks, such as
implementing security measures, conducting regular backups, and
complying with data privacy regulations.
 Evaluate the environmental and social feasibility of the event management
system, such as its impact on the environment, accessibility for people with
disabilities, and ethical considerations.

By conducting a thorough feasibility study and risk analysis, event management

system developers can identify potential challenges and opportunities associated
with the system, and develop effective strategies to ensure its success.

3.2 SYSTEM REQUIREMENTS SPECIFICATION

HARDWARE REQUIREMENTS:

 Processor -Pentium-IV
 Speed - 2.4GHZ
 Hard disk - 40GB
 Monitor - 15VGA color
 RAM - 512MB

12
 SOFTWARE REQUIREMENTS:
 Operating System - Windows XP
 Coding language - PHP
 Database - MYSQL
FUNCTIONAL REQUIREMENTS
 REGISTRATION :
Description: To enter into this site user has to register first. Requirements of
registration are first name, last name, user name, email id, password,confirm
password etc.
Processing: User details are checked with database.Password constraint as
per validation.
 User login:
Description: The System provides facility to login into the system. We should
enter username and password.
Processing: The sytem will check the input of user if valid then login is done.
Otherwise user will be asked to re enter the username and password.
 Select the event:
Description: The user can select the event and also select payment
method.In this we input event name, enrolment option, incase team event
option to add team member and so on.
Processing: The sytem will add selected data into database.
 Forgot password:
Description: The user can send reset link to the mail id to reset password.
Processing: By reset link we can easily change the password and update
store in database.
 Admin:
Description: The Admin can add manager, main event, sub events, details
etc.., successfully everything is added to database.
Processing: The system will add selected data into database.
 Manager:
Description: The manager can add volunteer, main event and sub event and
all.
Processing: The system will add selected data into database.

13
  Logout:
Description: The system provides the facility to logout from the site.
Processing: User will logout.
Non-Functional Requirements
 Security: Users of the app should visit the URL to evaluate the operation of
the secure shell. Before upgrading the Internet agent's plugins, you should
activate the program.
 Availability: It should be online at all times and should never go offline.
 Accuracy: The administrators or event organizers are responsible for
verifying the correctness of the event information shown in the application.
 Flexibility: It is adaptable to new models and upgrades.
 Maintainability: It is simple to manage, and any faults that emerge should
be simple to correct.
 Reliability: The application website ensures the data's integrity, so it should
be trustworthy.
SOFTWARE ENIVORNMENT
PHP

PHP is an open-source, interpreted, and object-oriented scripting language that can

be executed at the server-side. PHP is well suited for web development. Therefore,
it is used to develop web applications (an application that executes on the server
and generates the dynamic page.). Some important points need to be noticed about
PHP as followed:

o PHP stands for Hypertext Pre-processor.

o PHP is an interpreted language, i.e., there is no need for compilation.
o PHP is faster than other scripting languages, for example, ASP and JSP.
o PHP is a server-side scripting language, which is used to manage the
dynamic content of the website.

o PHP can be embedded into HTML.

o PHP is an object-oriented language.
o PHP is an open-source scripting language.
o PHP is a simple and easy-to-learn language.

14
 FIG 3.1 PHP
Why use PHP

PHP is a server-side scripting language, which is used to design the dynamic web
applications with MySQL database.

o It handles dynamic content, database as well as session tracking for the

website.

o You can create sessions in PHP.

o It can access cookies variable and also set cookies.
o It helps to encrypt the data and apply validation.
o PHP supports several protocols such as HTTP, POP3, SNMP, LDAP, IMAP,
and many more.

o Using PHP language, you can control the user to access some pages of your
website.

o As PHP is easy to install and set up, this is the main reason why PHP is the
best language to learn.

o PHP can handle the forms, such as - collect the data from users using forms,
save it into the database, and return useful information to the user. For
example - Registration form.

15
PROJECT CATEGORY

Relational Database Management System (RDBMS): This is an RDBMS based

project which is currently using MySQL for all the transaction statements. MySQL is
an opensource RDBMS System.

BRIEF INTRODUCTION ABOUT RDBMS:

A relational database management system (RDBMS) is a database management

system (DBMS) that is based on the relational model as invented by E. F. Codd, of
IBM's San Jose Research Laboratory, Many popular databases currently in use are
based on the relational database model.

RDBMS have become a predominant choice for the storage of information in new
databases used for financial records, manufacturing and logistical information,
personnel data, and much more since the 1980s. Relational databases have often
replaced legacy hierarchical databases and network databases because they are
easier to understand and use. However, relational databases have been challenged
by object databases, which were introduced in an attempt to address the object-
relational impedance mismatch in relational database, and XML databases.

FIG 3.2 DATABASE

16
MYSQL

MySQL, officially, but also called ―My Sequel‖ is the world most widely used open-
source relational database management system (RDBMS) that runs as a server
providing multi-user access to a number of databases, though SQLite probably has
more total embedded deployments. The SQL phrase stands for Structured Query
Language.
The MySQL development project has made its source code available under
the terms of the GNU General Public License, as well as under a variety of
proprietary agreements. MySQL was owned and sponsored by a single for-profit
firm, the Swedish company MySQL AB, now owned by Oracle Corporation.
MySQL is a popular choice of database for use in web applications, and is a central
component of the widely used LAMP open source web application software stack
(and other AMPstacks).
LAMP is an acronym for ―Linux, Apache, MySQL, Perl/PHP/Python.‖
Free software-open source projects that require a full-featured database
management system often use MySQL.
For commercial use, several paid editions are available, and offer additional
functionality. Applications which use MySQL databases include: TYPO3, MODx,
Joomla, WordPress, phpBB, MyBB, Drupal and other software. MySQL is also
used in many high-profile, large-scale websites, including Wikipedia, Google
(though not for searches), Facebook, Twitter, Flicker, and YouTube.

MODULES
The event Management System is divided into following modules:

 Landing module
 Events module
 Registration module
 Admin module

LANDING MODULE

This module is the entry point of the Event Management System. It is the home
page of the web application. It contains basic information of the Event being
conducted. For example, if a Tech fest is being conducted in a college, The

17
landing module can list information of the tech fest. Details such as name, posters,
possible dates of the event can be displayed in the Landing module.

EVENTS MODULE

Events module contains in detailed information of various events that are added to
the Database. Various categories or types of events such as the Technical, Non-
Technical events, Cultural events, etc. can be listed in the documentation module.
And the organized events can be listed under the type of events as per their
category. This module will contain names of the events, registration links, price of
registration (if applicable), posters of the events, and more information about each
of the events.

REGISTRATION MODULE

The registration module is aimed to help the users register to the events of their
choice. It is achieved by the help of a Registration form that asks users the

18
information such as their Name, Email, Mobile, Event to register, Class, Section
and Address. The user will submit the form after filling their details using the
submit button. The submit button will trigger the back-end code and will store the
user information in the user database. In this way, a user can successfully register
in the events if their choice.

ADMIN MODULE

The admin module is implemented by making use of the concept of abstraction.

The admin module will not be visible to the end users. It can only be accessed by
the admin and will contain information about the user analytics. The admin will be
able to add new events and modify or delete the existing events. These changes
will be reflected in the events module that is accessed by the end users. The
admin module is important to make overall changes to the events directly from the
web application and is used by the students or faculties who are in charge of
organizing the events.

19
3.3 SYSTEM USE CASE MODEL

The use case model for any system consists of "use cases". Use cases represent
different ways in which the system can be used by the user. A simple way to find all
the use case of a system is to ask the questions "What the user can do using the
system?" The use cases partition the system behavior into transactions such that
each transaction performs some useful action from the users' point of view.

The purpose of the use case to define a piece of coherent behavior without reveling
the internal structure of the system.An use case typically represents a sequence of
interaction between the user and the system. These interactions consists of one
main line sequence is represent the normal interaction between the user and the
system. The use case model is an important analysis and design artifact (task). Use
cases can be represented by drawing a use case diagram and writing an
accompany text elaborating the drawing In the use case diagram each use case is
represented by an ellipse with the name of use case written inside the ellipse. All
the ellipses of the system are enclosed with in a rectangle which represents the
system boundary. The name of the system being moulded appears inside the
rectangle. The different users of the system are represented by using stick person
icon. The stick person icon is normally referred to as an Actor. The line connecting
the actor and the use cases is called the communication relationship. When a stick
person icon represents an external system it is annotated by the stereo
type<<extemal system>>

20
 CHAPTER 4

DESCRIPTION OF PROPOSED SYSTEM

In proposed system, the college fest maintains the portal in that the events which
are conducted will be posted. The post will be visible for the users those who wants
to participate in the event they will register and they will know the event venue and
details of the event. Admin will post the ongoing events so that they can see the
ongoing events and participate. In this system mainly they will be admin module and
user module.

ADVANTAGES

 Easy communication between the users and admin.

 Easily accessible

4.1 SELECTED METHODOLOGY OR PROCESS MODEL

Model View Controller or MVC as it is popularly called, is a software design pattern

for developing web applications. A Model View Controller pattern is made up of the
following three parts:
 Model - The lowest level of the pattern which is responsible for maintaining
data.
 View - This is responsible for displaying all or a portion of the data to the user.
 Controller-Software Code that controls the interactions between the Model
and View
MVC is popular as it isolates the application logic from the user interface layer and
supports the separation of concerns. Here the Controller receives all requests for
the application and then works with the Model to prepare any data needed by the
View. The view then uses the data prepared by the Controller to generate a final
presentable response. The MVC abstraction can be graphically represented as
follows.

21
 FIG 4.1 PROCESS MODEL

Waterfall Model

The waterfall technique, which is based on the SDLC (the Software Development
Life Cycle) and system technical processes based on the participants, is the
solution for managing the workflow intelligently and digitally while taking into
account the essential demands of each module. - In-depth analysis of user
requirements. - Making plans to design modules. - The implementation of an
application. - Modules for testing that run the application.

FIG 4.2 WATERFALL MODEL

22
Client-Server Model

The "Client-Server" model is the concept of a client and server interacting through
a network. It enables the use of web programs like Google and the ability to see
web pages like this one. In a web application, the client-server model is only a
means of describing the give-and-take interaction between the client and server.

FIG 4.3 CLIENT SERVER MODEL

4.2 ARCHITECTURE / OVERALL DESIGN OF PROPOSED SYSTEM

This application's main benefit is connecting students, faculty, and administrators.

It provides the best interface for students to view event details. This application will
include options such as roll number, event name, event description, event venue,
location, and contact information. The framework can be signed in either
administrator or faculty mode. All framework options will be implemented in
administrator and faculty modes. This mode will be used for inserting, updating,
and removing event details. The framework provides options such as reviewing,
adding, finding, and generating an event. All event data, such as date, time, place,
location, and so on, is entered by the administrator or faculty. Students can search
the data by event title or description and by a particular department. Technologies
used in this framework are Front-end languages include HTML, CSS, and
JavaScript. PHP is the back-end language. MySQL is the database used.

23
 FIG 4.4 ARCHITECTURE

UML DIAGRAMS

UML is popular for its diagrammatic notations. We all know that UML is for
visualizing, specifying, constructing and documenting the components of software
and non-software systems. Hence, visualization is the most important part which
needs to be understood and remembered.
UML notations are the most important elements in modeling. Efficient and
appropriate use of notations is very important for making a complete and
meaningful model. The model is useless, unless its purpose is depicted properly.
ER DIAGRAM

E-R Model is a popular high level conceptual data model. This model and its
variations are frequently used for the conceptual design of database application
and many database design tools employ its concept.

A database that confirms to an E-R diagram can be represented by a collecton of

tables in the relational system. The mapping of E-R diagram to the entities are:

 Attributes
 Relations
 Many-to-Many

24
  Many-to-one
 One-to-Many
 One-to-One
 Weak entities
 Sub-type and super-type

The entities and their relationships between them are shown using the following
conventions.

 An entity is shown in a rectangle

 A diamond represents the relationship among a number of entities.
 The attributes shown as ovals are connected to the entities or
relationships by lines.
 Diamond, oval, and relationships are labelled.
 Model is an abstraction process that hides super details while highlighting
details relation to application at end.
 A data model is a mechanism that provides this abstraction for database
application.
 Data modeling is used for representing entities and their relationship in
the database.
 Entities are the basic units used in modeling database entities can have
concrete existence or constitute ideas or concepts.
 Entity type or entity set is a group of similar objects concern to an
organization for which it maintain data.
 Properties are characteristics of an entity also called as attributes.
 A key is a single attribute or combination of 2 or more attributes of an
entity set is used to identify one or more instances of the set.
 In relational model we represent the entity by a relation and use tuples to
represent an instance of the entity.
 Relationship is used in data modelling to represent in association between
an entity set.
 An association between two attributes indicate that the values of the
associated attributes are independent.

25
 FIG 4.5 ER DIAGRAM

USE CASE DIAGRAM

A use case diagram is used to represent the dynamic behavior of a system. It

encapsulates the system's functionality by incorporating use cases, actors, and their
relationships. It models the tasks, services, and functions required by a
system/subsystem of an application. It depicts the high-level functionality of a
system and also tells how the user handles a system.

The main purpose of a use case diagram is to portray the dynamic aspect of a
system. It accumulates the system's requirement, which includes both internal as
well as external influences. It invokes persons, use cases, and several things that
invoke the actors and elements accountable for the implementation of use case
diagrams. It represents how an entity from the external environment can interact
with a part of the system.

Following are the purposes of a use case diagram given below:

 It gathers the system's needs.

 It depicts the external view of the system.

26
 It recognizes the internal as well as external factors that influence the system.
 It represents the interaction between the actors.

STUDENT

FIG 4.6 Use Case diagram for

student

FIG 4.7 Use Case diagram for administrator

27
DATAFLOW DIAGRAM

Data flow diagram is the starting point of the design phase that functionally
decomposes the requirements specification. A DFD consists of a series of bubbles
joined by lines. The bubbles represent data transformation and the lines represent
data flows in the system. A DFD describes what data flow rather than how they are
processed, so it does not hardware, software and data structure,

A data-flow diagram (DFD) is a graphical representation of the "flow" of data

through an information system. DFDs can also be used for the visualization of data
processing (structured design). A data flow diagram (DFD) is a significant
modeling technique for analyzing and constructing information processes. DFD
literally means an illustration that explains the course or movement of information
in a process. DFD illustrates this flow of information in a process based on the
inputs and outputs. A DFD can be referred to as a Process Model.

The data flow diagram is a graphical description of a system's data and how to

Process transform the data is known as Data Flow Diagram (DFD).

Unlike details flow chart, DFDs don't supply detail descriptions of modules that
graphically describe a system's data and how the data interact with the system.
Data flow diagram number of symbols and the following symbols are of by
DeMarco.

There are seven rules for construct a data flow diagram.

28
  Arrows should not cross each other.
 Squares, circles and files must wears names.
 Decomposed data flows must be balanced.
 No two data flows, squares or circles can be the same names.
 Draw all data flows around the outside of the diagram.
 Choose meaningful names for data flows, processes & data stores.
 Control information such as record units, password and validation
requirements are not penitent to a data flow diagram.

Additionally, a DFD can be utilized to visualize data processing or a structured

design.This basic DFD can be then disintegrated to a lower level diagram
demonstrating smaller steps exhibiting details of the system that is being modeled

On a DFD, data items flow from an external data source or an internal data store
to an internal data store or an external data sink, via an internal process. It is
common practice to draw a context-level data flow diagram first, which shows the
interaction between the system and external agents, which act as data sources
and data sinks. On the context diagram (also known as the Level 0 DFD'), the
system's interactions with the outside world are modeled purely in terms of data
flows across the system boundary The context diagram shows the entire system
as a single process, and gives no clues as to its internal organization.

This context-level DFD is next "exploded", to produce a Level 1 DFD that shows
some of the detail of the system being modeled. The Level 1 DFD shows how the
system is divided into sub-systems (processes), each of which deals with one or
more of the data flows to or from an extemal agent, and which together provide all
of the functionality of the system as a whole. The level 1 DFD is further spreaded
and split into more descriptive and detailed description about the project as level 2
DFD. The level 2 DFD can be a number of data flows which will finally show the
entire description of the software project.

FIG 4.8 Data Flow Diagram for Level-1

29
 FIG 4.9 Data Flow Diagram for Level 1.1 Adding event

FIG 4.10 Data Flow Diagram for Level 1.1.0

SEQUENCE DIAGRAM

A sequence diagram is a type of interaction diagram because it describes how—

and in what order—a group of objects works together. These diagrams are used
by software developers and business professionals to understand requirements for
a new system or to document an existing process. Sequence diagrams are
sometimes known as event diagrams or event scenarios.

30
 FIG 4.11 User login page (sequence diagram for student)

FIG 4.12 USER WITH

SERVER

Tables

Booked events

31
Category

Events

Students

Teachers

Users

32
 Venue

4.3 DESCRIPTION OF SOFTWARE FOR IMPLEMENTATION AND TESTING

PLAN OF THE PROPOSED MODEL / SYSTEM

DETAILED DESIGN OF IMPLEMENTATION

This phase of the systems development life cycle refines hardware and software
specifications, establishes programming plans, trains users and implements
extensive testing procedures, to evaluate design and operating specifications
and/or provide the basis for further modification.

Technical Design

This activity builds upon specifications produced during new system

design,adding detailed technical specifications and documentation.

Test Specifications and Planning

This activity prepares detailed test specifications for individual modules

andprograms, job streams, subsystems, and for the system as a whole.

Programming and Testing

This activity encompasses actual development, writing, and testing of

programunits or modules.

User Training

This activity encompasses writing user procedure manuals, preparation of

usertraining materials, conducting training programs, and testing procedures.

33
 Acceptance Test

A final procedural review to demonstrate a system and secure user

approvalbefore a system becomes operational.

Installation Phase

In this phase the new Computerized system is installed, the conversion to

newprocedures is fully implemented, and the potential of the new system is
explored.

System Installation

The process of starting the actual use of a system and training user personnel
inits operation.

Review Phase

This phase evaluates the successes and failures during a systems development
project, and to measure the results of a new Computerized Transystem in terms
ofbenefits and savings projected at the start of the project.

Development Recap

A review of a project immediately after completion to find successes and

potentialproblems in future work.

Post-Implementation Review

A review, conducted after a new system has been in operation for some time, to
evaluate actual system performance against original expectations and
projections for cost-benefit improvements. Also identifies maintenance projects
to enhance orimprove the system.

THE STEPS IN THE SOFTWARE TESTING

The steps involved during Unit testing are as follows:

 Preparation of the test cases.

 Preparation of the possible test data with all the validation checks.
 Complete code review of the module.
 Actual testing is done manually.
 Modifications done for the errors found during testing.

34
  Prepared the test result scripts.

The unit testing done included the testing of the following items:

 Functionality of the entire module/forms.

 Validations for user input.
 Checking of the Coding standards to be maintained during coding.
 Testing the module with all the possible test data.
 Testing of the functionality involving all type of calculations etc.
 Commenting standard in the source files

After completing the Unit testing of all the modules, the whole system is integrated
with all its dependencies in that module. While System Integration. We integrated
the modules one by one and tested the system at each step. This helped in reduction
of errors at the time of the system testing.

The steps involved during System testing are as follows:

 Integration of all the modules/forms in the system.

 Preparation of the test cases.
 Preparation of the possible test data with all the validation checks.
 Actual testing done manually.
 Recording of all the reproduced errors
 Modifications done for the errors found during testing.
 Prepared the test result scripts after rectification of the errors.

The System Testing done included the testing of the following items:

 Functionality of the entire system as a whole.

 User Interface of the system.
 Testing the dependent modules together with all the possible test data
scripts.
 Verification and Validation testing.
 Testing the reports with all its functionality.

After the completion of system testing, the next following phase was the Acceptance
Testing Clients at their end did this and accepted the system with appreciation.
Thus, we reached the final phase of the project delivery.

35
There are other six tests, which fall under special category. They are described
below:

Peak Load Test:

It determines whether the system will handle the volume of activities that occur
when the system is at the peak of its processing demand. For example, test the
system by activating all terminals at the same time.

Storage Testing:

It determines the capacity of the system to store transaction data on a disk or in

other files.

Performance Time Testing:

it determines the length of time system used by the system to process

transaction data. This test is conducted prior to implementation to determine how
long it takes to get a response to an inquiry, make a backup copy of a file, or send
a transmissionand get a response.

Recovery Testing:

This testing determines the ability of user to recover data or re-start system after
failure. For example, load backup copy of data and resume processing without
dataor integrity loss.

Procedure Testing:

It determines the clarity of documentation on operation and uses of system by

having users do exactly what manuals request. For example, powering down
systemat the end of week or responding to paper-out light on printer.

Human Factors Testing:

It determines how users will use the system when processing data or preparing
reports.

4.4 PROJECT MANAGEMENT PLAN

PROJECT PLANNING

Software project plan can be viewed as the following:

36
  Within the organization: How the project is to be implemented? What are
various constraints (time, cost, staff)? What is market strategy?
 With respect to the customer: Weekly or timely meetings with the customer
with presentation on status reports. Customers feedback is also taken and
further modification and developments are done. Project milestones and
deliverables are also presented to the customer.

For Successful software project the following steps can be followed:

 Select a project
• Identifying project‘s aims and objectives
• Understanding requirements and specification
• Methods of analysis, design and implementation
• Testing techniques
• Documentation
 Project milestones and deliverables
 Budget allocation
• Exceeding limits within control
 Project Estimates
• Cost
• Time
• Size of code
• Duration
 Resource Allocation
• Hardware
• Software
• Previous relevant project information
• Digital Library
 Risk Management
• Risk avoidance
• Risk detection

4.5 FINANCIAL REPORT ON ESTIMATED COSTING

Software cost comprises a small percentage of overall computer-based system cost.

There are a number of factors, which are considered, that can affect the ultimate

37
cost of the software such as - human, technical, Hardware and Software availability
etc.

The main point that was considered during the cost estimation of project was its
sizing. In spite of complete software sizing, function point and approximate lines of
code were also used to "size" each element of the Software and their costing The
cost estimation done by me for Project also depend upon the baseline metrics
collected from past projects and these were used in conjunction with estimation
variables to develop cost and effort projections.

We have basically estimated this project mainly on two bases-

 Effort Estimation:

This refers to the total man-hours required for the development of the project. It
even includes the time required for doing documentation and the user manual.

 Hardware Required Estimation:

This includes the cost of the PCs and the hardware cost required for the
development of this project.

4.6 TRANSITION / SOFTWARE TO OPERATIONS PLAN

Transitioning a software system to operations requires careful planning and

coordination to ensure a smooth and successful transition. Here is a plan for
transitioning an event management system to operations:

 Scope: The scope of the project is to transition the event management

system from the development environment to the operational environment.
This includes migrating the system to the production servers, configuring
the necessary hardware and software, and ensuring that the system is fully
functional.
 Plan the Transition: The following steps will be taken to transition the
system to operations:
• Develop a transition plan, including timelines, roles and responsibilities,
communication protocols, and contingency plans.
• Acquire and configure the necessary hardware and software.

38
 • Test the system to ensure that it functions correctly in the operational
environment.
• Develop a training plan for users.
• Deploy the system to the production servers.
• Monitor the system to ensure that it is functioning correctly.
• Maintain the system to ensure that it remains secure and up-to-date.
 Testing: The system will undergo thorough testing to ensure that it meets
the requirements and specifications. This includes unit testing, integration
testing, and user acceptance testing.
 Training: A training plan will be developed to ensure that users are able to
use the system effectively. This may include providing training materials,
conducting training sessions, or providing online training resources.
 Deployment: The system will be deployed to the production servers
following the deployment plan. All necessary components will be installed
and configured correctly, and the system will be thoroughly tested before it
is made available to users.
 Monitoring: The system will be monitored after deployment to ensure that it
is functioning correctly. This includes monitoring system performance, user
feedback, and any issues that arise. Any issues will be addressed promptly
to ensure that the system continues to function correctly.
 Maintenance: A plan for ongoing maintenance of the system will be
developed, which includes software updates, hardware maintenance, and
data backups. Regular system maintenance will ensure that the system
remains secure and up-to-date.

By following this plan, the event management system can be successfully

transitioned to operations, ensuring that it meets the needs of the users and
functions correctly in the operational environment.

39
 CHAPTER 5

IMPLEMENTATION DETAILS

5.1 DEVELOPMENT AND DEPLOYMENT SETUP

To develop and deploy an event management system, you will need to follow
certain steps to ensure that the application is developed and deployed
successfully. Here are the key steps:

 Define the requirements: The first step is to define the requirements of the
event management system. This will help you understand what the system
should do, what features it should have, and what technologies should be
used.
Features are:
 Product and Component based
 Creating & Changing Issues at ease
 Query Issue List to any depth
 Reporting & Charting in more comprehensive way
 User Accounts to control the access and maintain security
 Simple Status & Resolutions
 Multi-level Priorities & Seventies.
 Targets & Milestones for guiding the programmers
 Attachments & Additional Comments for more information
 Robust database back-end
 Various level of reports available with a lot of filter criteria's
 It contain better storage capacity.
 Accuracy in work.
 Easy & fast retrieval of information
 Well designed reports
 Decrease the load of the person involve in existing manual system
 Access of any information individually
 Work becomes very speedy Easy to update information

Technologies used are:

 HTML

40
  CSS
 JAVASCRIPT
 PHP
 XAMPP APACHE SERVER
 MYSQL
 Choose a development framework: Once you have defined the requirements,
you can choose a development framework to use. There are many popular
frameworks available for developing web applications.
Here we use Php for developing web application.
 Select a database: You will need to select a database to store the data for
your application. Popular options include MySQL, PostgreSQL, and
MongoDB.
MySQL is being used. It is the world's most popular open-source database.
Despite its powerful features, MySQL is simple to set up and easy to use.

To build a web site that shows data from a database, you will need:

 An RDBMS database program (like MySQL)

 A server-side scripting language, like PHP
 To use SQL to get the data you want
 To use HTML / CSS to style the page

 Set up a development environment: You will need to set up a development

environment that includes all the necessary software and tools to develop
your application. This may include a code editor, a version control system,
and a local server.
XAMPP is a popular cross-platform web server that allows programmers to
write and test their code on a local webserver. It was created by Apache
Friends, and the public can revise or modify its native source code. It
includes MariaDB, Apache HTTP Server, and interpreters for PHP and Perl,
among other computer languages.
It is a simple, lightweight Apache distribution that makes it extremely easy
for developers to create a local web server for testing purposes.

 Develop the application: With the development environment set up, you can
begin developing the application. This will involve writing code for the
backend and frontend of the application.
 A backend programming language‘s work is to handle the ‗behind
the scenes‘ functionality of Web applications. Its code assists in
connecting the web to a database, offering virtual links, and

41
 powering the web app. The backend development works together
with the front-end to provide the finished product to the end-user.
 PHP (or you can say Hypertext Preprocessor) is a veteran player in
the web development world. This open-source server-side scripting
language is created in 1994 and is specifically used for web
development. As it is an interpreted language – it doesn‘t require a
compiler either and also it can run on almost every major operating
system like Windows, Linux, macOS, Unix, etc. Talking about the
enriching features of PHP, there are so many such as easy to learn
nature, cross-platform compatibility, OOPs features, support to
various standard databases like MySQL, SQLite, etc. huge
community support, and many others. Other than that, PHP is very
much secure as a server-side scripting language as there are
numerous hash functions available in PHP for the encryption of
user‘s data. In particular, if you‘re a beginner – you can opt to go with
PHP for backend web development.
 A website‘s or software program‘s front end is the interface through
which users perform key actions. A user who visits an app or
browser can access different sections and functionalities. The front
end of any website or application contains programming that makes
certain features available to users.
 All web pages across the Internet have been crafted by the use of
some form of HTML. It is an essential requirement for browsers to
learn how to display texts or perform the loading of different
elements.
 CSS is a programming language used for stating how documents are
offered to users in terms of layout and style. A document generally
refers to a text file structure utilizing a markup language such as the
widely used HTML. CSS is used for converting a document to a usable
form for audiences.
 JavaScript is a popularly used programming language that lets users
implement sophisticated features on web pages.It can be brought into
action anytime a page is performing a dynamic action, such as
showing periodic content updates, animated two-dimensional and
three-dimensional graphics, interactive maps, video boxes, and more.
 Test the application: Once the application is developed, it's important to test
it to ensure that it's functioning correctly. This may involve writing automated
tests, conducting manual testing, and fixing any bugs that are found.
 Deploy the application: With the application tested and ready to go, it's time
to deploy it to a production server. This may involve configuring the server,
setting up a database, and uploading the application files.
 Monitor and maintain the application: After the application is deployed, you
will need to monitor it to ensure that it's running smoothly. This may involve
setting up monitoring tools, responding to user feedback, and fixing any
issues that arise.

42
 Overall, developing and deploying an event management system involves a lot
of work and attention to detail. However, with the right tools and processes in
place, it's possible to create a reliable and effective system that meets the needs
of event organizers and attendees.
5.2 TESTING
Testing is an essential process in the development of any software system, including
event management systems. It ensures that the software meets the required
standards and specifications and performs as expected in various scenarios.
Testing is also necessary to identify and fix bugs and defects before the system is
released to end-users.
It's also important to have a well-defined testing strategy and plan in place, along
with appropriate tools and resources. The testing process should be conducted by
trained professionals with the necessary skills and expertise.
In conclusion, testing is an essential process in the development of event
management systems to ensure that they meet the required standards and
specifications and perform as expected in various scenarios. A comprehensive
testing strategy, plan, and team of professionals are essential to achieve this goal.

43
 CHAPTER 6
RESULTS AND DISCUSSION

The old manual system was suffering from a series of drawbacks. Since whole of
the system was to be maintained with hands the process of keeping, maintaining
and retrieving the information was very tedious and lengthy. The records were never
used to be in a systematic order, there used to be lots of difficulties in associating
any particular transaction with a particular context. If any information was to be
found it was required to go through the different registers, documents there would
never exist anything like report generation. There would always be unnecessary
consumption of time while entering records and retrieving records. One more
problem was that it was very difficult to find errors while entering the records. Once
the records were entered it was very difficult to update these records.

The reason behind it is that there is lot of information to be maintained and have to
be kept in mind while running the business For this reason we have provided
features Present system is partially automated (computerized), actually existing
system is quite laborious as one has to enter same information at three different
places.

POINTS TO CONSIDER

 Documents and reports that must be provided by the new system: there can
also be few reports, which can help management in decision-making and cost
controlling, but since these reports do not get required attention, such kind of
reports and information were also identified and given required attention.
 Details of the information needed for each document and report.
 The required frequency and distribution for each document. Probable
sources of information for each document and report.
 With the implementation of computerized system, the task of keeping records
in an organized manner will be solved. The greatest of all is the retrieval of
information, which will be at the click of the mouse. So the proposed system
helps in saving the time in different operations and making information flow
easy giving valuable reports.

44
 CHAPTER 7
CONCLUSION

7.1 CONCLUSION

The intended Sathyabama Event Management System (SEMS) application would

make organizing and monitoring college events easier. Students, lecturers, and
staff will all benefit from the SEMS application. The application will be simple to
use, permitting users to register and pay for events online. The SEMS application
can save effort and minimize risks in handling college events. The application can
provide several benefits, including improved communication, real-time updates,
and attendance tracking. Therefore, developing a SEMS application can be a
viable solution to manage college activities efficiently and effectively.

7.2 FUTURE WORK

In a nutshell, it can be summarized that the future scope of the project circles around
maintaining information regarding:

 We can add printer in future.

 We can give more advance software for Event Management System
including more facilities
 We will host the platform on online servers to make it accessible worldwide
 Integrate multiple load balancers to distribute the loads of the system .
 Create the master and slave database structure to reduce the overload of the
database queries.
 Implement the backup mechanism for taking backup of codebase and
database on regular basis on different servers.

The above mentioned points are the enhancements which can be done to increase
the applicability and usage of this project. Here we can maintain the records of Event
and Activity. Also, as it can be seen that now-a-days the players are versatile, i.e.
so there is a scope for introducing a method to maintain the Event Management
System Enhancements can be done to maintain all the Event, Activity. Organizers,
Attendees. Conductors.

45
We have left all the options open so that if there is any other future requirement in
the system by the user for the enhancement of the system then it is possible to
implement them in the last we would like to thanks all the persons involved in the
development of the system directly or indirectly. We hope that the project will serve
its purpose for which it is develop there by underlining success of process.

7.3 RESEARCH ISSUES

 User Experience: One of the most important research issues in event

management systems is user experience. The system should be designed in
such a way that it is easy to use, visually appealing, and meets the needs of
the users. Researchers need to study the user behavior, preferences, and
expectations to design systems that can offer the best experience.
 Data Analytics: Another important research issue is data analytics. The event
management system generates a large amount of data, which can be used
to improve the system's functionality and performance. Researchers need to
study the data generated by the system and use it to gain insights into the
users' behavior and preferences.
 Security and Privacy: Security and privacy are also critical research issues in
event management systems. As these systems involve the collection and
storage of personal and sensitive information, it is essential to ensure that
the system is secure and compliant with privacy laws and regulations.
Researchers need to study the latest security and privacy technologies and
implement them in the system.
 Social Media Integration: Social media has become an essential part of event
promotion and management. Researchers need to study the latest trends
and technologies in social media and integrate them into the event
management system. This will help to promote the event to a wider audience
and enhance the user experience.
 Sustainability: With increasing concerns about climate change and
environmental sustainability, researchers need to study the impact of event
management systems on the environment. The system should be designed
in such a way that it minimizes its carbon footprint and reduces waste.
 Artificial Intelligence and Machine Learning: Artificial intelligence and
machine learning have the potential to revolutionize event management

46
 systems. Researchers need to study the latest developments in these fields
and apply them to the event management system to enhance its functionality
and performance.

In conclusion, event management systems have several research issues that

need to be addressed to enhance their functionality, performance, and user
experience. Researchers need to study the latest trends and technologies and
apply them to the system to achieve these goals.

7.4 IMPLEMENTATION ISSUES

 Scalability: One of the main implementation issues in event management

systems is scalability. The system should be designed in such a way that it
can handle large volumes of data and users. This involves using scalable
technologies such as cloud computing, distributed systems, and load
balancing.
 Integration: Event management systems need to integrate with other
systems such as ticketing systems, payment gateways, social media
platforms, and marketing tools. This involves using APIs, web services, and
middleware to facilitate seamless integration.
 Customization: Another important implementation issue is customization.
Event management systems should be designed in such a way that they
can be customized to meet the specific needs of the users. This involves
using flexible architectures, modular designs, and customizable interfaces.
 Performance: Event management systems need to perform well under
various loads and stresses. This involves using performance tuning
techniques such as caching, compression, and database optimization.
 Security: Security is also a critical implementation issue in event
management systems. The system should be designed in such a way that it
is secure from external threats such as hacking, malware, and phishing
attacks. This involves using secure coding practices, encryption, and
access controls.
 Usability: The usability of the system is also an important implementation
issue. The system should be designed in such a way that it is easy to use

47
 and intuitive for the users. This involves using user-centered design
principles, usability testing, and user feedback.

In conclusion, event management systems have several implementation issues

that need to be addressed to ensure their functionality, performance, and
usability. These issues involve using scalable, flexible, secure, and
customizable technologies and techniques. It is essential to design and
implement the system in such a way that it meets the specific needs and
preferences of the users.

48
 REFERENCES

1] Hongqing Dou, Baisong Liu, Internet + Library: Elements, Models and Services,
J. Information and Documentation Services. 2017(03):93-97.

[2] Shiwei Wang, The Important Role of the "Internet+" Action Plan in the "Digital
Founding" Pattern, J. China Public Security. 2016(4):24-28.

[3] Kong Hao, Wang Lisha and Wan Pu, ―Research on University Student
Information Management System Based on UBOSS in Poor Areas of China‘s
Western Region‖, the 2nd International Conference on Computer Engineering and
Technology (ICCET), vol.7, pp.655-658, 2010.Y.L.

[4] Jiang, C.F. Xu, ―Advances in Set Pair Analysis Theory and its Applications,‖
Computer Science, vol. 33, issue 1, pp. 205-209, 2006.

[5] Zhai Qinfei, ―Effective Combination Between E-learning and KM in Higher

Education: By the Support of Information Technology‖, the 2nd IEEE International
Conference on Information Management and Engineering (ICIME), vol.1, pp.533-
536, 2010.

[6] Piedade M.B., Santos M.Y, ―Student Relationship Management: Concept,

Practice and Technological Support‖, 2008 International Engineering Management
Conference, vol.5, pp.1-5, 2008.

49
APPENDIX

A. SOURCE CODE

ADMIN HOMEPAGE

<?php include_once 'header.php'; ?>

<div class="jumbotron p-2 text-center mb-2 bg-dark text-white">

<h2>Admin Dashboard</h2>
</div>
<div class="row">
<div class="col-sm-3 text-white text-center">
<div class="card bg-primary p-3">
<h3><?= countrecords("students") ?></h3>
<h4>Students</h4>
</div>
</div>
<div class="col-sm-3 text-white text-center">
<div class="card bg-danger p-3">
<h3><?= countrecords("teachers") ?></h3>
<h4>Faculty</h4>
</div>
</div>
<div class="col-sm-3 text-white text-center">
<div class="card bg-secondary p-3">
<h3><?= countrecords("events") ?></h3>
<h4>Events</h4>
</div>
</div>
<div class="col-sm-3 text-white text-center">
<div class="card bg-info p-3">
<h3><?= countrecords("users") ?> </h3>
<h4>Users</h4>
</div>
</div>
</div>

<?php include_once 'footer.php'; ?>

50
BOOKED EVENTS

<?php include_once 'header.php'; ?>

<div class="jumbotron p-2 text-center mb-2 bg-primary text-white">

<h4>Booked Events</h4>
</div>
<table class="table table-bordered">
<thead>
<tr>
<th style="width:400px;">Event</th>
<th>Date</th>
<th>Time</th>
<th>Student Name</th>
<th>Class</th>
</tr>
</thead>
<tbody>
<?php
foreach(allrecords("events e join bookedevent be on be.eventid=e.eventid join students s
on be.id=s.rollno order by 1 desc") as $map) {
?>
<tr class="<?= $map["status"]==='cancelled' ? 'table-danger':'' ?>">
<td><?= $map["descr"]?></td>
<td><?= $map["startdate"]?> to <?= $map["endate"]?></td>
<td><?= $map["starttime"]?>-<?= $map["endtime"]?></td>
<td><?= $map["name"]?></td>
<td><?= $map["course"]?></td>
</tr>
<?php } ?>
</tbody>
</table>
<div class="modal fade" id="sadd">
<div class="modal-dialog">
<div class="modal-content">
<form method="post" action="save_event.php" enctype="multipart/form-data">
<div class="modal-header">
<h4>Add New Event</h4>
<button type="button" data-dismiss="modal" class="close">&times;</button>
</div>
<div class="modal-body">
<div class="form-group">
<select class="form-control" name="catid">
<option><-- Select Category --></option>
<?php
foreach (allrecords("category") as $map2) {
?>
<option value="<?= $map2["catid"]?>"><?= $map2["catname"]?></option>
<?php }?>
51
 </select>
</div>
<div class="form-group">
<textarea class="form-control" rows="4" name="descr"
placeholder="Description"></textarea>
</div>
<div class="form-group">
<input type="date" class="form-control" name="startdate" placeholder="Start Date">
</div>
<div class="form-group">
<input type="text" class="form-control" name="starttime" placeholder="Start Time">
</div>
<div class="form-group">
<input type="date" class="form-control" name="enddate" placeholder="End Date">
</div>
<div class="form-group">
<input type="text" class="form-control" name="endtime" placeholder="End Time">
</div>
<div class="form-group">
<input type="file" class="form-control" name="photo">
</div>
</div>
<div class="modal-footer">
<button class="btn btn-primary float-right">Save Event</button>
</div>
</form>
</div>
</div>
</div>
<?php include_once 'footer.php'; ?>

52
 CLUB NAMES

<?php include_once 'header.php'; ?>

<div class="jumbotron p-3 text-center mb-2 bg-primary text-white">

<h4>Categories</h4>
</div>
<div class="container">
<div class="row">
<div class="col-sm-8">
<table class="table table-bordered table-sm">
<thead class="table-dark">
<tr>
<th>Category ID</th>
<th>Category Name</th>
<th>Operation</th>
</tr>
</thead>
<tbody>
<?php
foreach (allrecords("category") as $map) {
?>
<tr>
<td><?= $map["catid"]?></td>
<td><?= $map["catname"]?></td>
<td><a href="delcat.php?catid=<?= $map["catid"] ?>"
onclick="return confirm('Are you sure to delete this category')"
class="btn btn-danger btn-sm">Delete</a></td>
</tr>
<?php }?>
</tbody>
</table>
</div>
<div class="col-sm-4">
<form method="post" action="savecat.php">
<div class="form-group">
<input type="text" placeholder="Category Name" class="form-control" name="cname">
</div>
<button class="btn btn-primary btn-block">Save Category</button>
</form>
</div>
</div>
</div>
<?php include_once 'footer.php'; ?>

53
DELETE CLUB

<?php
$eventid=$_GET["id"];
include_once 'dbfun.php';

$link= connect();
$query="delete from events where eventid='$eventid'";
mysqli_query($link, $query);

$query="delete from bookedevent where eventid='$eventid'";

mysqli_query($link, $query);

$_SESSION["msg"]="event deleted successfully";

header("location: events.php");

FACULTY HOMEPAGE

<?php include_once 'header.php'; ?>

<h2>Lecturer Dashboard</h2>
<?php
$id = $_SESSION["id"];
$map = single("teachers", "tid=$id");
?>
<div class="container">
<div class="row">
<div class="col-sm-7">
<table class="table table-bordered">
<tr>
<th style="width:200px;">Teacher ID</th>
<th><?= $map["tid"]?></th>
</tr>
<tr>
<th>Teacher Name</th>
<th><?= $map["name"]?></th>
</tr>
<tr>
<th>Designation</th>
<th><?= $map["designation"]?></th>
</tr>
<tr>
<th>Email ID</th>
<th><?= $map["email"]?></th>
</tr>
<tr>
<th>Contact Number</th>
54
 <th><?= $map["phone"]?></th>
</tr>
</table>
</div>
</div>
</div>
<?php include_once 'footer.php'; ?>

LOGIN PAGE

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Login Page</title>
<link href="css/bootstrap.min.css" rel="stylesheet" type="text/css"/>
<script src="js/jquery-3.4.1.js" type="text/javascript"></script>
<script src="js/popper.min.js" type="text/javascript"></script>
<script src="js/bootstrap.min.js" type="text/javascript"></script>
<script src="js/all.js" type="text/javascript"></script>
<style>
.toast{
background-color:white;
padding:15px;
border-radius:7px;
position: absolute;width:300px;
right:10px;top:10px;
}
</style>
<script>
$(function () {
$(".close").click(function () {
$(".toast").css({"display": "none"});
});
});
</script>
</head>
<body>
<?php
include_once 'dbfun.php';
include_once 'msg.php';
?>
<a href="index.php" class="btn btn-success btn-sm float-right m-2">Home</a>
<div class="jumbotron rounded-0 text-center p-5 bg-primary text-white">
<h4>Welcome to Sathyabama Event Management System</h4>
<h5>Login</h5>
</div>
55
 <div class="container">
<div class="row">
<div class="col-sm-5 mx-auto mt-5">
<div class="card p-3">
<form method="post" action="validate.php">
<div class="form-group">
<input type="text" class="form-control" required name="userid"
placeholder="User Name">
</div>
<div class="form-group">
<input type="password" class="form-control" required name="pwd"
placeholder="Password">
</div>
<div class="form-group">
<select class="form-control" required name="role">
<option value="">--- Select Role ---</option>
<option value="admin">Administrator</option>
<option value="lecturer">Faculty</option>
<option value="student">Student</option>
</select>
</div>
<button class="btn btn-primary btn-block">Login</button>
</form>
<p class="text-center mt-2">To register Click <a href="Register.php">here</a></p>
</div>

</div>
</div>
</div>
<div class="fixed-bottom jumbotron mb-0 p-1 text-center bg-success text-white">
<h6>Copyright Event Management System &copy; 2023</h6>
</div>
</body>
</html>

LOGOUT PAGE

<?php
session_start();
session_destroy();
header("location: index.php");

?>

56
STUDENT HOMEPAGE

<?php include_once 'mheader.php'; ?>

<div class="p-1"></div>
<div class="container-fluid">
<?php
$id = $_SESSION["id"];
$map = single("students", "rollno=$id");
?>
<h2>Student Dashboard</h2>
<div class="row">
<div class="col-sm-8">
<h4>Booked Event</h4>
<div class="row">
<?php
$list = findall("events", "eventid in(SELECT eventid from bookedevent WHERE
id='$id')");
foreach ($list as $map2) {
$map3 = single("category", "catid='{$map2["catid"]}'");
$cname = $map3["catname"];
?>
<div class="col-md-4">
<div class="card mb-4 box-shadow">
<img class="card-img-top" style="height:200px;" src="events/<?= $map2["photo"]?>"
data-holder-rendered="true">
<div class="card-body">
<h5><?= $cname?></h5>
<p class="my-0">Date : <?= $map2["startdate"]?> to <?= $map2["endate"]?></p>
<p>Time: <?= $map2["starttime"]?> to <?= $map2["endtime"]?></p>
<div class="d-flex justify-content-between align-items-center">
<?php if($map2["status"]=='cancelled') { ?>
<h5 class='text-danger'>This event has been cancelled</h5>
<?php } else { ?>
<div class="btn-group">
<a href="leaveevent.php?eventid=<?= $map2["eventid"]?>" class="btn btn-sm
btn-outline-danger">Leave Event</a>
</div>
<?php } ?>
</div>
</div>
</div>
</div>
<?php }
?>
</div>
</div>
<div class="col-sm-4">
<table class="table table-bordered">
<tr>
<th style="width:200px;">Roll no</th>
<th><?= $map["rollno"]?></th>
57
 </tr>
<tr>
<th>Student Name</th>
<th><?= $map["name"]?></th>
</tr>
<tr>
<th>Course</th>
<th><?= $map["course"]?></th>
</tr>
<tr>
<th>Email ID</th>
<th><?= $map["email"]?></th>
</tr>
<tr>
<th>Contact Number</th>
<th><?= $map["phone"]?></th>
</tr>
</table>
</div>
</div>
</div>
<?php include_once 'mfooter.php'; ?>

USERS

<?php include_once 'header.php'; ?>

<h2 class="text-center bg-primary text-white p-2">Users</h2>

<div class="container">
<table class="table table-bordered table-sm">
<thead class="table-primary">
<tr>
<th>User Id</th>
<th>User Name</th>
<th>Password</th>
<th>Role</th>
<th>ID</th>
</tr>
</thead>
<tbody>
<?php
foreach (allrecords("users") as $map) {
?>
<tr>
<td><?= $map["userid"]?></td>
<td><?= $map["uname"]?></td>
<td><?= $map["pwd"]?></td>
<td><?= $map["role"]?></td>
<td><?= $map["id"]?></td>
58
 </tr>
<?php }?>
</tbody>
</table>
</div>
<?php include_once 'footer.php'; ?>

VALIDATE

<?php

include_once 'dbfun.php';
extract($_POST);

$link= connect();

$query="SELECT * FROM users WHERE userid='$userid' and pwd='$pwd' and role='$role'";

$result=mysqli_query($link, $query) or die("Error ". mysqli_error($link));

if($row= mysqli_fetch_assoc($result)){
$_SESSION["uname"]=$row["uname"];
$_SESSION["userid"]=$row["userid"];
$_SESSION["role"]=$row["role"];
$_SESSION["id"]=$row["id"];
if($_SESSION["role"]=="admin"){
header("location: adminhome.php");
}
else if($_SESSION["role"]=="lecturer"){
header("location: lecturerhome.php");
}
else if($_SESSION["role"]=="student"){
header("location: studenthome.php");
}
}
else{
$_SESSION["error"]="Invalid username or password";
header("location: login.php");
}

59
VERIFY

<?php

extract($_POST);
include_once 'dbfun.php';

$link= connect();
if($role=="student"){
$query="SELECT name from students where rollno='$id'";
}
else if($role=="lecturer"){
$query="SELECT name from teachers where tid='$id'";
}

$result= mysqli_query($link, $query) or die("Error ". mysqli_error($link));

if($row= mysqli_fetch_assoc($result)){
echo $row["name"];
}
else{
echo "Invalid";
}

60
B. SCREENSHOTS

XAMPP SERVER

DATABASE

61
HOMEPAGE

ABOUT US AND EVENTS

62
LOGIN PAGE

REGISTER

63
ADMIN LOGIN

CLUBS

64
USERS

UPDATE PROFILE FOR ADMIN

65
CHANGE PASSWORD

STUDENT HOMEPAGE

66
EVENTS

EVENT REGISTER

67
FACULTY DASHBORD

FACULTY ADDING EVENTS

68
 C. RESEARCH PAPER

TIJER || ISSN 2349-9249 || © Month 20XX, Volume X, Issue X, || www.tijer.org

Sathyabama Ems
(Event Management System)
1
Bonagiri Keerthi, 2 PYDR Priyanka, 3 Dhanalakshmi K
1
Student,2 Student,3Assistant Professor
1
Cse,
1
SIST, Chennai, India
1
[email protected], [email protected], 3 [email protected]
_
Abstract - To assist faculty and students in managing college activities, a system known as the Sathyabama Event Management
System (SEMS) has been developed. For instance, technical festivals and other events that necessitate web-based user registration.
This responsive and dynamic web application makes it simple for users of the event management system to interact with and register
for the events of their choice. This will do away with the requirement for extra paperwork.

Index Terms - Event Management System, MySQL, PHP, Registration

I. INTRODUCTION
A web-based tool known as the sathyabama event management system (SEMS) improved project management for the planning and
execution of large-scale events like cultural fests, club events, workshops, and other activities. The goal is to have a consolidated
database of all event-related data. With several organizations heading their activities and celebrations online, it's important to have a
medium or platform to aid with event management. Students and professors could utilize this type of platform to learn about the
variety of upcoming events, permitting interested users to immediately enroll in the activity they've decided to attend. It is designed to
help with the accurate procedure. It is a web application that lets users log in to the application directly through a site without
requiring any mobile apps to be installed. The online application was developed with PHP, MySQL, HTML, and CSS. PHP is used
for backend scripting in web applications. It is deployed on Netlify.

PROBLEM STATEMENT

The intention behind this application is to create a system that reliably stores every detail of data regarding the various activities that
occur in the organization. The ultimate objective is to create an organized database including all event-related information. The goal is
to help with the numerous procedures and processes that are needed for good information management.

PURPOSE

The major goal of the event management system is to make it easier for faculty and students to manage events. Additionally, it can be
applied to: successfully managing college clubs, organizing fundraisers to support a cause, directing organizational activities, easy
registration for events, and creating reports on users who have signed up.

EXISTING SYSTEM

The current technology does not adequately handle user profiles or allow for the secure registration of users. Online assistance is not
offered by this system. The actions and progress of users are not tracked by this system. With this manual technique, we have very
little protection for data storage, and some data may be lost as a result of poor management. This system does not offer online event
management. This system is not delivering accurate information about the events. The event management executer is the method
through which the system provides manual information.

PROPOSED SYSTEM

The next phases in the development of this new system will try to automate the full process while maintaining the database
implementation strategy in view. The student's name and mobile number are saved in this database. This system will provide online
search and assist functionalities. The application is user-friendly, with a wide range of features provided via a system-rich user
TIJER - INTERNATIONAL RESEARCH JOURNAL www.tijer.org 1
 TIJER || ISSN 2349-9249 || © Month 20XX, Volume X, Issue X, || www.tijer.org

II. SPECIFIC PREREQUISITES

HARDWARE PREREQUISITES

Processor: Pentium-iv
RAM: 512MB
Hard disk: 40 GB
Speed: 2.4 GHZ
GPU: not necessary

SOFTWARE PREREQUISITES

OS: Windows
Browser: Chrome
Frontend: HTML, CSS
Backend: PHP
Scripting language: JavaScript
IDE: VS Code
Server: XAMPP
Database: MySQL
Cloud: Netlify
TABLE 1 REQUIREMENTS

FUNCTIONAL REQUIREMENTS

Registration: The user must correctly fill out the registration form.

Select the event: The user has the option to choose both the event and the payment method. We enter the event name, the enrollment
choice, the ability to add team members if the event is a team event, and so on.

Admin: The administrator can successfully add the manager, main event, sub-events, details, etc. to the database.

Faculty: The management can add volunteers, main events, sub-events, and everything else.

Logout: The system offers the option to log out of the website.

NON-FUNCTIONAL REQUIREMENTS

Security: Users of the app should visit the URL to evaluate the operation of the secure shell. Before upgrading the Internet agent's
plugins, you should activate the program.

Availability: It should be online at all times and should never go offline.

Accuracy: The administrators or event organizers are responsible for verifying the correctness of the event information shown in the
application.

Flexibility: It is adaptable to new models and upgrades.

Maintainability: It is simple to manage, and any faults that emerge should be simple to correct.

Reliability: The application website ensures the data's integrity, so it should be trustworthy.

TIJER - INTERNATIONAL RESEARCH JOURNAL www.tijer.org 2

 TIJER || ISSN 2349-9249 || © Month 20XX, Volume X, Issue X, || www.tijer.org

III. ARCHITECTURE

This application's main benefit is connecting students, faculty, and administrators. It provides the best interface for students to view
event details. This application will include options such as roll number, event name, event description, event venue, location, and
contact information.

The framework can be signed in either administrator or faculty mode. All framework options will be implemented in administrator
and faculty modes. This mode will be used for inserting, updating, and removing event details.

The framework provides options such as reviewing, adding, finding, and generating an event.

All event data, such as date, time, place, location, and so on, is entered by the administrator or faculty.

Students can search the data by event title or description and by a particular department.

Technologies used in this framework are

Front-end languages include HTML, CSS, and JavaScript.

PHP is the back-end language.

MySQL is the database used.

Fig.1 SYSTEM ARCHITECTURE

IV. WORKING MODEL OF THE SYSTEM

WATERFALL MODEL

The waterfall technique, which is based on the SDLC (the Software Development Life Cycle) and system technical processes based
on the participants, is the solution for managing the workflow intelligently and digitally while taking into account the essential
demands of each module.

- In-depth analysis of user requirements.

- Making plans to design modules.
- The implementation of an application.
- Modules for testing that run the application.

TIJER - INTERNATIONAL RESEARCH JOURNAL www.tijer.org 3

 TIJER || ISSN 2349-9249 || © Month 20XX, Volume X, Issue X, || www.tijer.org

CLIENT-SERVER MODEL

The "Client-Server" model is the concept of a client and server interacting through a network. It enables the use of web programs like
Google and the ability to see web pages like this one. In a web application, the client-server model is only a means of describing the
give-and-take interaction between the client and server.

V. CONCLUSION

The intended Sathyabama Event Management System (SEMS) application would make organizing and monitoring college events
easier. Students, lecturers, and staff will all benefit from the SEMS application. The application will be simple to use, permitting users
to register and pay for events online. In handling college events, the SEMS application can save effort and minimize risks.

VI. REFERENCES

[1] Internet Library Elements, Models, and Services by Hongqing Dou and Baisong Liu were published in. Information and
Documentation Services in 2017( 03) 93- 97.
[2] Advances in Set Brace Analysis proposition and its operations by Jiang, C.F. Xu, Computer Science, vol. 33,no. 1, 2006, pp. 205-
209.
[3] Student Relationship Management Concept, Practice, and Technological Support, International Engineering Management
Conference, 2008, vol. 5, pp. 1 – 5, Piedade, M.B., and Santos, M.Y.
[4] Presbury, R.; Edwards D. (2005), Incorporating Sustainability in Meetings and Event Management Education, International
Journal of Event Management Research, vol. 1, no. 1, pp. 30-45.

TIJER - INTERNATIONAL RESEARCH JOURNAL www.tijer.org 4